Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 8.1.1  and later
Information in this document applies to any platform.
The AllowMultipleAssociations is documented here :-
Integration Platform Technologies: Siebel Enterprise Application Integration > Integration Objects > About the Structure of Integration Objects > Integration Components and Associations
NOTE: When building an integration object, if an integration component is an association based on an intersection table, then the user key for this integration component can contain fields based on the same intersection table only if the integration component has an AllowMultipleAssociations integration component user property set to Y in Siebel Tools.
This was being used with Contacts and CUT Address, where the address can have multiple associations to the Contact (through Addressee field on the intersection, S_CON_ADDR).
The incoming message has Addressee in the user key for CUT Address, along with Address Name, and this worked for most cases. For example, if there is an existing address "Main Street" for an Addressee, a new incoming message with the same Addressee and “Dark Street”, allows a new association to be created, and the database updates are as expected. But if the new Address has "Main Street 2" (i.e. includes the ‘Main Street’ as a substring), then this error is reported :-
 No rows retrieved corresponding to the business component 'CUT Address'(SBL-EAI-04378) (IDS_ERR_EAI_SA_BC_NO_DATA)
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