A merge request contains all the information for a specific merge process, including:
The party or parties involved in the merge
The intended results of the merge
For an overview of the entire merge process, see: De-Duplication Overview.
A merge request of type Multiple contains a set of duplicate parties to merge. Each Multiple type request has a designated master party that remains after the other duplicates merge into it. A request of type Single involves cleansing one party.
When you create or update a merge request, the Create Merge Batch process runs to create or re-create the request, including generating the suggested mapping defaults. For example, if you remove a duplicate from the request, the process runs to regenerate the merge request. Running the Create Merge Batch process is called preprocessing in de-duplication.
After you map the merge request to determine the results of the merge, you submit the request for the actual Party Merge process.
Caution: You cannot undo a merge. Use only match rules that provide exact matches.
Start at the Merge Request Queue page to:
Create Request or Create Merge Request: See: Creating Merge Requests.
Merge Request Name: See: Reviewing Merge Requests.
Assign: Assign and unassign merge requests of any phase, no matter whom the request is currently assigned to or who created the request.
Suggestion: You can click Remove from Set to remove any merge request from the assignment. You are not deleting or rejecting the request.
Reprocess: Reprocess selected merge requests to regenerate default master records, as well as default profile attributes and default relationship and address groupings for mapping. You might want to reprocess, for example, if you change profile option settings or match rules that affect merge requests.
Map: Map and submit merge requests, or reject the request. See: Mapping Merge Requests.
If the HZ: Data Sharing and Security Rules for Data profile option is set to:
Apply Rules at Mapping and Do Not Show Access Column: Then Data Sharing and Security (DSS) rules determine mapping access. You can map a merge request only if the DSS rules assigned to your user ID allow you to update all the parties in the request.
Apply Rules at Mapping and Show Access Column: Then, in addition, the Access column is displayed to indicate your access status.
Status: If the request has a status of Submitted for Merge, Completed, or Error, you can see details of the Party Merge process, for example the error log.
Resubmit Requests: Rerun processes that originally resulted in error. See: Resubmitting Requests.
The Merge Request Queue page shows all merge requests. To restrict the list, you can search for requests by:
Merge ID: The merge request ID.
Name: The master party of Multiple type requests or the party to cleanse in Single type requests.
Note: Merge request names with the SUGG: prefix are for suggested merge requests that the system creates after merging parties. These requests contain parties related to the originally merged parties. If the HZ: Submit Suggested Person Merge Request profile option is set to Yes, then the suggested person merge request is automatically submitted after the related organization parties are merged. See: Relationships.
Source: The method used to create the merge request.
Import: Manually from a System Duplicate Identification batch that import Registry de-duplication created. If Automerge was part of the de-duplication, then the merge request was automatically created to contain a duplicate set that was automatically merged.
Import AM: Manually from a SDI batch that resulted from import Registry de-duplication with Automerge. The batch contains the duplicate sets that were not automatically merged.
See: Registry De-Duplication.
System AM: Manually from a SDI batch that resulted from creating a batch with Automerge. The batch that contains only parties that were not automatically merged was used to create this merge request.
System: Manually from a SDI batch that was also manually created. If Automerge was part of the batch creation, then the merge request was automatically created to contain a duplicate set that was automatically merged.
User: Using Smart Search, Registry ID selection, or other manual user selection.
Phase: The mapping phase of the request, which corresponds to the Status column in the table.
AM Queue: Request is in the queue to be automatically merged by the Automerge program.
Completed: Party Merge process successfully completed.
Error: Party Merge process resulted in error.
Mapping: Request has been modified since creation.
Preprocess: Create Merge Batch process is running to create or regenerate the request, which is not yet ready for mapping.
Rejected: Request has been rejected.
New: Create Merge Batch process has successfully completed, and the request has not been modified since but is ready for mapping.
Submitted: Request has been submitted for the Party Merge process.
Suggestion: Refresh the status to see the latest values.
Assignment: The user assigned to the request, or Unassigned.
From the Resubmit Requests bin on the Merge Request Queue page, you can resubmit preprocessing, the Create Merge Batch process, or the Party Merge process for appropriate merge requests. If either process previously resulted in an error, you resubmit the process for that merge request after you fix the problem.
For merge requests that are automatically created and then merged, as part of System Duplicate Identification batch creation, you can also resubmit Automerge processes that resulted in error. For the Batch parameter, select the SDI batch ID that the merge request originates from. See: Automerge in System Duplicate Identification and Automerge.