Last updated on MARCH 02, 2017
Applies to:Siebel Universal Customer Master - Version 8.1.1  and later
Information in this document applies to any platform.
Siebel Universal Customer Master (UCM) : updating of master data (account, contact) address information from incoming messages from edge aplication.
Updating address of a customer (contact) record with address details (Country, Poistal Code, City, Street Address etc)
that are all equal to some existing address of another contact causes Siebel application failure on the address unique name violation.
if Account: C1 had address A1 (considering address elements. Street Address, City, Postal Code, State, Country etc) and account C2 had address A2,
then the error occurs, when SDH message for account C1 delivers address change for address A1 to have same address elements as the address A2
2 different address of same address details, associated to different contacts should co-exist.
So amending address of one contact would not impact or propagate address change for another contact.
SAMPLE use case.
The data were processed by EAI Siebel Adpater Upsert method using the "SwiOrganizationIO" Integration Object
based on the "Account" Business Object. processing was triggered by the "UCM Transaction Manager" step
of the "UCM Organization Customer Profile Integration SOAP Process" standard workflow process.
This process implements the "createOrganization" operation of the standard Siebel UCM Inbound Web Service.
Sample EAI Object Manager log:
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