Upon Primary Position Changes (Siebel), Account Team In Crm Desktop Is Wrong.
Last updated on JULY 03, 2016
Applies to:Siebel CRM Desktop - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
***Checked for relevance on 22 July 2013***
Customer is checking where CRMDesktop user gets the position from? Does it get the position from the current windows user that is logged in or is it the position of the user which connects to eaiobjmgr_enu?Why do the position change of the primary position in the siebel application, doesn't affect the contacts/accounts team in crm desktop, but affect the visibility rules on which data is synchronized?
Say User has 2 positions. This user has primary "positionA" set and makes an initial synchronisation in CRM Desktop. After this happened the primary position "positionA"is set in CRM Desktop in the "Account Team" Field or the "Contact Team" Field.
We now change the primary position in Siebel to "positionB" and synchronise again with CRM Desktop.
What happen is the following: All Data (Account,Contacts, Opportunities, Activities) from "positionB" is synced (not an initial sync) correctly, but the old primary position "positionA" remains in the Account Team" Field or the "Contact Team" Field.
So the problem is, that while creating new data, the old primary position "Position A" is written in the Account Team and Contact Team field. This happens if you create "new data", this means a new account, new contacts, ... which doesn't exist in siebel
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms