First UserKey Reused For All Root Component Instances In IO Processed By EAI Siebel Adapter (Doc ID 1532372.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.0 SIA [20405] and later
Information in this document applies to any platform.

Symptoms

When sending a SiebelMessage with several records as input of the EAI Siebel Adapter, the Upsert method uses the User Key of the first record for all remaining records.
 
If you send two records on the SiebelMessage and they have different fields, which in turn require the use of different User Keys, an error will be raised for the second record (or the first record that uses a different user key):

ERROR:

EAISiebAdpt EAISiebAdptErr 1 000000025122087c:0 2013-02-18 03:36:17 [0] Multiple matches found for instance of integration component 'Account' using search specification '' in the business component 'Account', based on user key 'V77 Wizard-Generated User Key:1'.(SBL-EAI-04390) (IDS_ERR_EAI_SA_MULTIPLE_MATCH)

STEPS TO REPRODUCE:

1) Create a sample SiebelMessage to update two records that already exist on the DB. Use the EAI Account IO as it is one of the standard IOs present on Siebel.

2) Make the first record use the “Id” user key to identify the record and add the field “Alias” to be updated.

3) Make the second record use “Name” and “Location” fields as user key (do not provide the field “Id” on the input). Also update the field “Alias”.

4) Execute the Upsert method of the EAI Siebel Adapter and the error message will be thrown and the records will not be updated.

Cause

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