My Oracle Support Banner

UCM Survivorship Is Not Updating Contact Email Address When Values Are Processed Through UCM Batch Mode (Doc ID 2560665.1)

Last updated on MARCH 12, 2021

Applies to:

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


SIEBEL VERSION:     Siebel [IP2013] version, Universal Customer Master
SIEBEL APP O/S:      Microsoft Windows x64 (64-bit)


UCM Survivorship is not working when records are processed via UCM Batch Process.

For example:

Day 1 - SourceA (Score=80), SOurceDat = 06/08/2019 , FN, LN, +44123111,

Day 2 - SourceA (Score=80), SOurceDat = 06/10/2019 , FN, LN, +44123111,

Result :

Base record is updated, but the email address from the incoming latest message is not updated to new value.
The issue can be reproduced at will with the following steps:

1. Send an initial first message into the UCM system to insert a new record, the record is inserted with the incomingg values, such as:

SourceA (Score=80), SOurceDat = 06/08/2019 , FN, LN, +44123111,

2. Send another message into UCM system to update the existing record with new values, new values coming in are:

SourceA (Score=80), SOurceDat = 06/10/2019 , FN, LN, +44123111,

3. The result of the second transaction is that the record is updated, but the record's email address field is not updated with the email address from the second message, the email address field on the record remains unchanged.


Due to the issue, the record in the Siebel application does not accurately reflect the latest/correct values that it should have from the external system.

Additionally, the issue impacts critical production go-live deadline that is coming up.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.