How to make EAI Siebel Adapter Upsert use different user keys on child Component instances of input Integration Object instance?
(Doc ID 1622290.1)
Last updated on APRIL 30, 2018
Applies to:Siebel CRM - Version 7.5.2  and later
Information in this document applies to any platform.
Is it possible to configure EAI Siebel Adapter, that user key to be picked per child instance is not not based on the first child instance?
- - - - - - - -
Siebel CRM is receiving and upsert (using EAI Siebel Adapter) messages from a Customer Hub, containing data on an Account with belonging Addresses.
In some cases, new addresses will be created in the Customer Hub, and synced in to Siebel. We would like to use "Siebel Row Id" as user key on the addresses already existing in Siebel,
and an external id as user key on the new addresses (only to identify that the addresses do not already exist in Siebel).
The external id cannot be used as a user key on the existing addresses, as it is not constant, and may change.
The Siebel EAI Bookshelf (Integration Platform Technologies: Siebel Enterprise Application Integration > Integration Objects > About Integration Component Keys > User Keys) stays that:
A new user key is picked for each integration object instance (root component instance).
However, for the child component instances, the user key is picked based on the first child instance, and then used for matching all instances of that integration component within the parent integration component instance.
Is it possible to override the behaver?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!