Use the Import Batch to TCA Registry program to import a batch from the interface tables into the TCA Registry. The program provides optional preimport processes you can perform on the data before the actual import into TCA:

• Batch de-duplication: Identify and resolve duplicates within the batch that you are importing from the interface tables.

  Note: The Import Batch to TCA Registry program identifies only duplicates with respect to the batch that you are importing. You cannot check for duplicates between batches in the interface tables.

  You can run the Import Batch De-Duplication report to view results. See Import Batch De-Duplication Report.

• Address validation: See: Import Address Validation.

• Registry de-duplication: Identify duplicates between the interface tables and the Registry.

Prerequisites

• The data you want to import must be loaded into the interface tables. See: Loading Data into the Interface Tables.

• Optionally check that the D&B Import Adapter request set is not currently running. If it is and you submit the Import Batch to TCA Registry program, the program will be pending until the request set is complete. See: Import Batches.

• If you are running the Import Batch to TCA Registry program for an import batch that was not loaded into the interface tables using File Load in Oracle Customers Online or Oracle Customer Data Librarian, optionally check that another non-File Load batch is not currently being loaded into the TCA Registry. If it is, and you submit the program for a non-File Load batch, the program will be pending until the process for the other batch is complete. See: File Loads Overview.

Program Parameters

Use the following parameters to submit the Import Batch to TCA Registry program.

Batch ID

Enter the batch to import.

Import Run Option

Specify whether to run both preimport and import processes, or only the preimport processes.

If you plan to run batch de-duplication, you can run only preimport processes and then run the Import Batch De-Duplication report to preview batch de-duplication results.

Run Batch De-Duplication

Specify whether you want to run de-duplication on the batch or not.

Batch De-Duplication Match Rule

If you select to run batch de-duplication, you must enter the match rule to use. Only match rules of type Bulk Duplicate Identification are used for batch de-duplication.

Action to Take on Duplicates

Specify how to resolve duplicates found with batch de-duplication. The specified action would be taken on the batch before the data is imported into the TCA Registry.

Run Address Validation

Specify whether you want to run address validation on the batch or not.

Run Registry De-Duplication

Specify whether or not you want to run de-duplication between the batch and the TCA Registry.

Registry De-Duplication Match Rule

If you select to run Registry de-duplication, you must enter the match rule to use. Only match rules of type Bulk Duplicate Identification are used for Registry de-duplication. You can select the same match rule as for batch de-duplication.

If the specified match rule is designated for Automerge, then potential duplicates that reach or exceed the match rule's:

• Match threshold, but not the automatic merge threshold, are included in System Duplicate Identification (SDI) batches for merge consideration in Oracle Customer Data Librarian.

• Automatic merge threshold are automatically merged after the import.

If the match rule is not enabled for Automerge, then all potential duplicates that reach or exceed the match threshold are included in SDI batches.

All records that do not reach the match threshold are considered not duplicates and inserted as new parties. All potential duplicates are also inserted into the TCA Registry as new parties, but then accordingly included in SDI batches or automatically merged.

Generate Fuzzy Key During Post Processing

Specify whether or not to generate fuzzy keys as part of the postimport processes.

See: Postimport Processes.