Use the Merge Request Queue or System Duplicate Identification Batches page to start the process of creating a merge request from a duplicate set in a System Duplicate Identification batch.
You can also use the party merge request Web service to create a party merge request for duplicate party IDs and/or a combination of the source system and the source system IDs. See: Web Services Implementation Overview, Oracle Trading Community Architecture Administration Guide.
Merge Request Queue: Select the System Duplicates method for the Create Request field. Search for and select the SDI batch to use.
System Duplicate Identification Batches: Review the batch that you want to use. See: Reviewing System Duplicate Identification Batches.
Suggestion: You can also click System Duplicates in the Create Merge Request bin, and select the batch to use.
Subset for Identifying Duplicates specifies filtering criteria used to create the SDI batch, if any. See: Creating System Duplicate Identification Batches.
Select at least one duplicate set from the batch.
Suggestion: Select multiple duplicate sets to create separate merge requests with each set, at the same time.
Alternatively, click Details to view and update a duplicate set, and optionally use that as the set to create a merge request. Duplicate sets already used to create merge requests are not available. You can update duplicate sets without creating merge requests with them.
View all parties in the duplicate set that are designated for merge. If the match rule used to create the SDI batch has an automatic merge threshold, parties with scores that exceed the threshold are marked as Automerge candidates.
Note: Automerge candidates would have been automatically merged as part of creating the SDI batch if the option was selected. See: Automerge in System Duplicate Identification.
Certification levels indicate the quality of records, and the meaning of each level is based on your organization's business needs. See: Assigning Certifications.
To update duplicate sets with multiple parties, you can:
Remove From Set: Remove any party from the duplicate set so that it is not part of the merge request.
Attention: Any party that you remove from a set cannot be selected for a merge request again using this duplicate set.
Edit Removed Parties:
Restore parties to include in the merge request.
Mark any removed party as not a duplicate of the parties that remain in the created merge request. The nonduplicate mapping ensures that the parties are not selected as duplicate candidates in the future. You define a date range for this mapping to be active, and can leave the end date blank for the mapping to always be active.
After you create the merge request, you can still update the end date for nonduplicate mappings. See: Administering Nonduplicate Mappings
Match Details: View details about how a specific duplicate was identified, based on the DQM match rule used to create the System Duplicate Identification batch. The party marked as the master is the input record that DQM used to identify the other duplicates in the set.
For each attribute that is a match between the master and the duplicate, you can see the attribute value from both parties, and the match score for that attribute. The total score is used to compare against the thresholds in the match rule used to create the SDI batch.
Match Threshold: The duplicate is selected for the duplicate set because the total match score between that party and the master party meets or exceeds the match threshold.
Automerge Threshold: The duplicate is an Automerge candidate if the total match score meets or exceeds the Automerge threshold.