Last updated on MARCH 02, 2017
Applies to:Siebel Assignment Manager - Version 7.0.1 [10746-5] to 220.127.116.11 SIA  [Release V7 to V8]
**checked for currency 25-JUNE-2013**
Customer created an assignment rule that looks at the primary position id of an account to see if matches a managers position. If it does it should assign the account to a custom organization and assign 4 positions to the sales team. When it assigns the primary position id it violates the policy and is placed in the s_escl_req table. When it clears the table it only assigns sadmin to the account team. SADMIN was not one of the positions to be assigned. Has this behavior been seen before?
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