Use de-duplication to:
Merge duplicate parties in the Oracle Trading Community Architecture (TCA) Registry.
Cleanse a specific party so that it does not have any duplicate information.
The TCA Registry is the single source of party information for all Oracle E-Business Suite applications. These applications provide user interfaces, batch data entry functionality, and other features for you to enter party information. Multiple points of data entry can result in duplicate and inaccurate information.
Each application must quickly, accurately, and consistently retrieve information from the TCA Registry for transaction processing. Duplicate data in the Registry can reduce the efficiency and accuracy of party processing and reports.
De-duplication provides functionality for the entire process of resolving duplicate parties and information in the TCA Registry:
Identify duplicates: Create merge requests, which contain information about the duplicate parties that you want to merge or the party that you want to cleanse.
Automatically merge duplicates: Optionally run Automerge to automatically merge parties identified as definite duplicates. Automerge bypasses manually creating, mapping, and submitting merge requests.
Manage merge requests: Review, assign, and reject specific requests.
Map merge requests: Determine the results of the merge by specifying the information that remains after the merge. You map the duplicate information to merge either among parties or within the party that you are cleansing.
Submit merge requests: Run the Party Merge process to perform the actual merge, either for duplicate parties or within a party to cleanse it.
Note: If you have source system information in the TCA Registry, de-duplication uses the Single Source of Truth record. See: Single Source of Truth Overview.