My Oracle Support Banner

Incoming SDH Value Is Not Updated To Base Table Record Using UCM Survivorship Rule With Recent Comparison Method (Doc ID 2193214.1)

Last updated on OCTOBER 28, 2016

Applies to:

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


On : [IP2014] version, Client Functionality

Updation of survivor record is not happening after Survivorship Rules are evaluated.

Survivor record should get updated based on the comparison rule mentioned in the Survivorship rule

The issue can be reproduced at will with the following steps:

1. Create records from external system X which is having source confidence set as 80, and processed two records and make sure that these records falls in existing duplicates.
2. Try to merge records from Existing duplicates view
3. Now fire an update on Survivor (in this case Cross reference Match will happen on survivor).
4. Not able to see the updated values pushed to the record (expected it should update the record, but not the case).

The issue has the following business impact:
Due to this issue, users cannot have the updated value taken into the Best Version of the record causing inconsistencies in the final record.


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.