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 APRIL 03, 2025

Applies to:

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

Goal

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)?

Solution

	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

Goal

Solution

References

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

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)

Applies to:

Goal

Solution

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

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