UCMBatchProcess Execution Of SDH Data With Suspect Match Enabled Always Results In Newest Record As The Driver/Survivor Record In The Existing Duplicates View
(Doc ID 1591979.1)
Last updated on AUGUST 01, 2016
Applies to:Siebel Universal Customer Master - Version 126.96.36.199 SIA  and later
Information in this document applies to any platform.
*** Checked for currency AUG-01-2016 ***
1. What is difference between Master and History for Survivorship comparison methods?
2. What do External and Slave do as well for Survivorship comparison methods?
3. Why is it that whenever UCMBatchProcess executes on SDH data with Suspect Match enabled, it always results in newest record as the driver/survivor record in the Existing Duplicates View (top applet)?
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