Automerge automatically merges records that exceed a specified threshold during duplicate identification. The Automerge program only runs if the match rule specified for the duplicate identification process is designated for Automerge.
Note: Automerge is always implemented as part of a duplicate identification process. You can manually run Automerge only to resubmit an automatic run that resulted in error.
The Automerge program evaluates records against the match and automatic merge thresholds set in that match rule. The program:
Automatically merges records that meet or exceed the automatic merge threshold.
Creates a System Duplicate Identification (SDI) batch containing records that exceed the match threshold but not the automatic merge threshold. The SDI batch is available in Oracle Customer Data Librarian for merge consideration.
If a party is to be automatically merged, but already exists in a merge request in Oracle Customer Data Librarian, then an error is recorded in the Automerge log, and that party is not merged with its duplicates. The program continues and merges other parties that do not incur errors. See: De-Duplication Overview.
In each duplicate set, two or more duplicate candidates are automatically merged into one merge master record. You can control aspects of the merge through profile options.
The HZ: Merge Master Party Defaulting profile option setting determines which party in each duplicate set is the master.
The HZ: Default Profile Attributes for Merge Mapping and HZ: Default Secondary Profile Attributes for Merge Mapping profile option settings determine which party profile attributes remain after the merge.
The HZ: Use DQM Suggested Groupings for Automerge profile option determines if addresses and relationships are merged based on DQM suggestions, or are just transferred from duplicate candidates to the master.
See: DQM Deployment Category.
Other rules of Automerge are:
For attributes other than party profile attributes, if the master already has a value, then that value survives the merge. If not, then the value is transferred from the duplicate candidate with the latest creation date and an attribute value.
For relationships, If the subject party Registry ID for the merge master and duplicate candidates are the same, and the relationship type is the same, then Automerge merges the relationship records. See: Relationships Overview.
If the party sites for the merge master and duplicate candidates have the same location ID, then the party sites are merged instead of transferred.
All transactions and accounts are transferred from the duplicate candidates to the merge master.
Run this program from Standard Request Submission only to resubmit an Automerge that resulted in error.
Batch: Enter the batch number to rerun Automerge for. Only previously failed batches are available.
Number of Workers: Enter the number of workers for the process. The recommended number is four, and the maximum number is ten.