The System Duplicate Identification (SDI) feature lets you create SDI batches that contain potential sets of duplicates. De-duplication runs a program to identify duplicates based on criteria that you specify. You can use any duplicate set in a batch as the basis for a new merge request.
You can run Automerge as part of creating SDI batches to automatically merge definite duplicates. This process bypasses manually creating, mapping, and submitting merge requests for obvious duplicates. Parties in the SDI batch that are not merged are included in a new batch, for manual review at a later time.
You can create two types of merge requests:
Multiple: Contains a duplicate set of two or more parties to merge.
Single: Contains a single party to cleanse.
De-duplication provides three methods for creating merge requests. Each Multiple type request must contain parties of the same type, such as Person or Organization.
Aside from reviewing merge requests, you can:
Assign requests to specific users
Unassign requests
Reject requests
For each merge request, you map the duplicate information to determine the results of the merge. For both Single and Multiple type requests, you map address and relationship information. De-duplication can provide default suggestions for either mapping. Set the HZ: Submit Suggested Person Merge Request profile option to Yes to automatically submit the suggested person merge request after the related organization parties are merged.
For Multiple type requests, you also map party profile attributes, which describe the party. For example, for the D-U-N-S Number attribute, you specify which number from the duplicate set should remain after the merge.
After reviewing your mapping, you can submit the merge request for the Party Merge process.