Overview of Duplicate Resolution Setup

Duplicate resolution is a set of processes that you can use, after duplicate records are identified, to consolidate those records. You can resolve duplicates in two ways, either by linking them or by merging them. Linking involves associating the duplicate records.

The linked records are treated as unique records in the data registry, and have their own unique identifiers. Merging involves combining duplicate records into one new master record.

The duplicate resolution functionality comes with tools and rules that you can use to determine whether to merge records or not. These rules can also help determine the record that should be kept as the golden master (the surviving record) and the record that should be deleted (the non-master record).

You can setup linking by configuring a couple of profile options discussed in the topic Duplicate Resolution Simplified Profile Options. However, the setup for merging is a bit more elaborate. It consists of configuring logic to:

Determine which record from a set of identified duplicates should be designated as the master record. You can set this up by configuring Set Master Record Rules.
Determine which attribute value instances from across the set of duplicates the master record should have. You can set this up by configuring Set Attribute Value Rules. The Set Master Record Rules and Set Attribute Value Rules are collectively called Survivorship Rules.
Determine whether the merge is violating any of the conditions under which a merge should be prohibited. You can set this up by configuring Agreement Rules.

You can easily setup survivorship and agreement rules in Application Composer using Groovy Script.

An alternative to using Groovy Scripts based survivorship and agreement rules is to configure them using Oracle Business Rules. You can do this configuration in the Setup and Maintenance work area using the Manage Survivorship Rules and Manage Agreement Rules setup tasks.

Note that if you're already using Oracle Business Rules, you can migrate from Oracle Business Rules to Groovy Script incrementally. For example, you could continue to use Oracle Business Rules to define agreement rules while using Groovy Script for your set master rules.

You can setup duplicate resolution by configuring the tasks listed in the following table.

Step	Description	Task Name	Where to Get More Details
Setup Source Systems	Set up source systems to import data into the application and identify the source of the data that you're importing. You can select multiple source references in the Manage Source System Entities task to allow multiple source system records to map to a single record. You must setup source systems before importing your organization (account) and person (contact) data	Manage Trading Community Source Systems Manage Source System Entities	See the topic: Setup Source Systems
Manage Source System Confidence	Source system confidence levels or scores are used as criteria in survivorship rules for: Comparing the reliability of information from different source systems Preserving the data from the most reliable source in the master record during merge operations You can set the source confidence score per source system for attributes in the organization (account) and person (contact) objects.	Manage Source System Confidence	See the topic: Manage Source System Confidence
Enable Groovy Script-based Survivorship and Agreement Rules	You must enable groovy scripting, before you can start using groovy scripts to configure survivorship and agreement rules. You can do so in the in Setup and Maintenance work area by setting the appropriate profile options.	Manage Customer Data Management Options	See the topic: How You Enable Groovy Script-based Survivorship and Agreement Rules
Create an Application Composer Sandbox	Create a separate, dedicated sandbox for survivorship and agreement rules. This approach gives you the greatest flexibility for iterative design, testing, and deployment of your survivorship and agreement rules.	N/A	See the topic: Create an Application Composer Sandbox
Configure Predefined Data Quality Rules to Your Requirements	Customer data management comes with six predefined data quality merge event points, three for the Account (Organization) entity and three for the Contact (Person) entity. You must configure these predefined rules to your unique business requirements.	N/A	See the topics: Configure Predefined Data Quality Rules to Your Requirements in Application Composer Configure Groovy Script Based Set Master Record Rules Configure Groovy Script Based Set Attribute Value Rules Configure Groovy Script Based Agreement Rules
Test Your Survivorship and Agreement Rules Configuration	Create a Test Merge Request in the Duplicate Resolution work area to test your groovy script-based survivorship and agreement rules configuration in real time.	N/A	See the topic: Test the Survivorship and Agreement Rules Configuration
Deploy Your Survivorship and Agreement Rules Configuration	You must publish your dedicated Application Composer sandbox for survivorship and agreement rules to deploy the configuration.	N/A	See the topic: Deploy the Survivorship and Agreement Rules Configuration
(Applicable only if you're using Oracle Business Rules) Manage Oracle Business Rules Based Survivorship Rules	Survivorship rules determine the master or surviving customer record and its attributes during the merge operations for duplicate resolution. You can enable survivorship rules by setting the ZCH_ENABLE_SURVIVORSHIP profile option to Yes	Manage Survivorship Rules Manage Customer Hub Profile Options	See the topics: How You Enable and Manage Survivorship Rules Define Survivorship Rules Define Set Master Record Rules Define Set Attribute Value Rules
(Applicable only if you're using Oracle Business Rules) Manage Oracle Business Rules Based Agreement Rules	Agreement rules determine whether a merge request should be vetoed by the application or not. Merge requests that violate agreement rules don't complete successfully	Manage Agreement Rules	See the topics: How You Manage Agreement Rules Define Agreement Rules
Run Request Dispatch Job	Run this process to manage and monitor resolution requests in pending or submitted statuses	Run Request Dispatch Job	See the topic: Run the Request Dispatch Job

Note:

In case of Accounts, Customer Profile Quality Scoring is an additional method to resolve duplicates. This method helps in assigning scores to records and identifying a record with the highest score. This record with the highest score can be used as the single account record, instead of multiple duplicate records. For more information about Customer Profile Quality Scoring, see the Implementing Customer Data Management guide.