When the Import Batch to TCA Registry program is submitted, this process follows:
The batch de-duplication and address validation runs, if selected.
Duplicates found through batch de-duplication are resolved as you specified in the Action to Take on Duplicates parameter, for example, to keep the records that are last updated.
If you chose to run preimport processes only so that you can preview preimport results, then address validation includes all records. If not, then address validation includes only records that batch de-duplication determines as not duplicates.
The data in the interface tables are matched against source system mappings to determine if imported records are inserted as new parties or to update existing parties. See: Matching Records with Source System Management.
For performance reasons, the records are populated into staging tables for processing before loading into the TCA tables.
If you have selected the optional Registry de-duplication, then duplicates are identified between the batch that you are importing and the TCA Registry. All parties are to be inserted as new parties, but then the duplicates are resolved as described in step 7.
After any selected preimport processes finish, depending on your choice, either:
The actual import into TCA starts immediately.
You start the actual import by rerunning the program, after you optionally:
Review preimport process statistics from the program output.
Run the Import Batch De-Duplication report for this import batch, if batch de-duplication was run. The report output provides a preview of the de-duplication results.
Mandatory validations are performed on all data, and records that pass all validations are loaded into the TCA Registry. Records that fail are marked with error and not imported. See: Import Validations.
If Registry de-duplication was run, then:
System Duplicate Identification batches are created with potential duplicates for merge consideration in Oracle Customer Data Librarian. See: System Duplicate Identification.
Duplicates are automatically merged through Automerge, if applicable. See: Automerge.
Records that are not duplicates are inserted as new parties.
Postimport processes automatically run. See: Postimport Processes.
If you ran batch de-duplication, optionally run the Import Batch De-Duplication report for this batch. The report output provides the de-duplication results.