My Oracle Support Banner

UCM SDH Address Update error: Unique constraint S_ADDR_PER_U1 violation / SBL-DAT-00381: A record that contains identical values to the record you have created already exists. (Doc ID 2065646.1)

Last updated on MAY 13, 2021

Applies to:

Siebel Universal Customer Master - Version 8.1.1 [21112] and later
Information in this document applies to any platform.


Updating of primary data (account, contact) address information from incoming messages from edge application such as (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.

For example:

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

The expected behavior is that 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:





To view full details, 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 a vibrant support community of peers and Oracle experts.