You can create merge requests:
Registry ID: By selecting specific parties. See: Registry ID.
From a Registry ID list of values, you select at least one party to include in your new merge request.
Smart Search: Using Smart Search to find potential duplicates. See: Smart Search.
Smart Search provides a list of parties based on your criteria. You select at least one party to include in a new merge request.
System Duplicates: From duplicate sets in a System Duplicate Identification (SDI) batch. See: System Duplicates.
A SDI batch contains sets of duplicates that de-duplication identifies based on your criteria for the batch. You select duplicate sets from any batch to create one or more merge requests. See: System Duplicate Identification.
Note: To create a merge request of type Single, use any of the methods to create a request with only the party that you want to cleanse.
In your new merge request, you cannot include parties that already belong to either another merge request or a merge batch in Oracle Trading Community Architecture Party Merge. A message would inform you if you select such a party. See: Creating Merge Batches.
Before you submit the new request for creation with the System Duplicates or Registry ID method, you can still remove parties from Multiple type requests. You do not delete the party from the TCA Registry, and the party is available to be included in other SDI batches, duplicate sets, or merge requests.
After you submit a new merge request, the Create Merge Batch process runs to create the merge request. Depending on the request type, the name of your new merge request is:
Multiple: The name of the master party.
Single: The name of the one party in the request.
For merge requests of type Multiple, the HZ: Merge Master Party Defaulting profile option determines the master party, which remains after the merge. You can change the master party when you map the merge request. See: Request Summary.