Siebel 8.1x Default Organization Is Being Used When Creating SR For Inbound Email in Multi -Org environment
Last updated on MARCH 02, 2017
Applies to:Siebel Email Response - Version 22.214.171.124  and later
Information in this document applies to any platform.
When an Inbound Email is recieved, we create an SR and tie the Email Activity to the SR. However, when that SR is created, the Organization is always set to Default Organization. Even when we provide a different Org when creating the SR. Here are the items we have tried:
- Set the Primary Organization Id to a different value, but when SR is created it only has Default Organization.
- Change the Username for Communications Inbound Receiver to a differnt ID than SADMIN, one tied to a different Organization than Default Org.
Customer workflow picks the correct Org - Primary Organization , but still it uses Default Org when it does the Insert Operation for the SR.
Below is the step customer was referring to, when they were passing in the Org Id: Create SR. See below lines from the log:
StpExec Task 4 0000000b52781c60:0 2013-11-05 15:18:07 Invoking method 'InsertRecord' on business service 'Inbound E-mail Database Operations'.
StpExec TaskArg 4 0000000b52781c60:0 2013-11-05 15:18:07 Input: @0*0*9*0*0*0*17*Field: Contact Id7*1-1RHHT18*Field: Description8*Test
17*Field: Account Id0*6*BusObj15*Service Request30*Field: Primary Organization Id6*1-JW0O13*Field: Source5*Email18*Field: Owned By Id7*1-3S89O7*BusComp15*Service Request16*Field: Abstract22*RE: Test SR 11_05_2013
So we are passing in the Primary Organization Id, but it still uses Default Org when it does the insert for Service Request Organization.
Change the Responsiblity.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms