A new merge request contains information about the included parties to merge or the party to cleanse, but you can map the request to determine the results of the merge. For all aspects of the merge result, de-duplication provides defaults which you can review and modify as needed.
Set the profile option HZ: Enable DQM Merge Suggestion to 'No' to disable DQM suggestion. This will reduce time lag and improve performance during the during the Create Merge Batch process.
Note: You cannot update the mapping of requests that are already submitted for the Party Merge process.
As you go through the mapping process, you can:
Save your work at any time: When you navigate out of a mapping step, your work for that step is automatically saved. For substeps with an Apply or Save Note button, you must click that button to save your work.
Cancel your work at any time: When you click the Cancel button, you discard all mapping for the merge request, and mapping defaults are regenerated.
Record cumulative notes: You record comments for any step of the mapping process. These notes are cumulative and displayed in each subsequent step.
Note: The notes are available only if the IMC: Display Notes for Merge Request Mapping profile option is set to Yes.
For Single type requests, you map sets of duplicate addresses and relationships for the party and determine the master address or relationship that remains after the merge for each set.
For Multiple type merge requests, you map sets of duplicate addresses and relationships among the parties and determine the master address or relationship that remain for each set. The master address or relationship does not need to come from the master party.
Party profile attributes, such as First and Last Names, SIC Code, and CEO Name, describe the parties in the TCA Registry. Each party can have attribute values for any of the attributes, for example a number for the D-U-N-S Number attribute.
For Multiple type requests, you map each attribute to determine which value remains after the merge. For example, if the request contains five duplicates, each with a D-U-N-S Number, you specify the number that remains after the merge. That number does not need to come from the master party. Party profile attribute mapping does not apply to Single type requests.
Addresses, relationships, and party profile attributes can be mapped in any sequence, at different times, and by different data librarians. For Multiple type requests, the request summary should be reviewed first to confirm the master party, which affects defaults for the other mapping steps.
If the HZ: Data Sharing and Security Rules for Data Librarians profile option is set to Apply Rules at Merge Submission, then you can submit the request for merge only if the Data Sharing and Security (DSS) rules assigned to your user ID allow you to update all the parties in the merge request. See: Data Sharing and Security Overview.
Suggestion: After you submit a merge request, you can access details of the Party Merge process in the Merge Request Queue page. See: Reviewing Merge Requests.
Review and submit the request for the Party Merge process.
Review and submit the request for the Party Merge process.