TCA Bulk Import allows for importing batches of data from external sources into the TCA Registry.

Procedure

• Define and map legacy and other source systems to entities in the TCA Registry. Perform this step for all source systems you plan to import from. See: Administering Source Systems.

• You can provide the option of resolving duplicates for import:

  • Batch de-duplication: Resolving duplicates within the interface tables.

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

  Import de-duplication involves Data Quality Management (DQM) bulk duplicate identification. See: Bulk Import De-Duplication Processes.

  1. Administer Data Quality Management.

     You must define and designate attributes and transformations for bulk duplicate identification acquisition.

  2. Optionally create match rules for import de-duplication, which must have the Bulk Duplicate Identification purpose.

     For match rules you create for Registry de-duplication, allow for Automerge if you want to automatically merge parties with the highest probability of being duplicates.

     When you create the match rules, take note of the match and automatic merge thresholds. If a record:

     • Does not exceed the match threshold, then it is not a duplicate. In Registry de-duplication, the record is inserted as a new party into the TCA Registry.

     • Reaches or exceeds the match threshold but not the automatic merge threshold, then it is a potential duplicate.

       In batch de-duplication, based on the action that the user specifies for duplicates, the record is dealt with in the interface tables, before import.

       In Registry de-duplication, the record is inserted as a new party, but is also included in a System Duplicate Identification batch in Oracle Customer Data Librarian for further evaluation. See: System Duplicate Identification.

     • Reaches or exceeds the automatic merge threshold, then it is inserted as a new party and then automatically merged with its duplicates. This threshold applies only to Registry de-duplication, and only if the match rule is allowed for Automerge.

• For providing the option of validating addresses before importing them into the TCA Registry, use or create adapters that can provide address validation services, and define the adapter configurations. See: Configuring Adapters.

• For providing the option of applying Data Sharing and Security to the import process:

  1. Administer Data Sharing and Security.

  2. Set the HZ: Use Data Sharing and Security During Import profile option.

• Set these profile options:

  • HZ: Allow Import of Records with Disabled Lookups

  • HZ: Allow Updates of Address Records During Import

  • HZ: Character Value to Indicate NULL During Import

  • HZ: Date Value (DD-MM-YYYY) to Indicate NULL During Import

  • HZ: Error Limit for Import

  • HZ: Import Batch De-Duplication Match Rule

  • HZ: Import Registry De-Duplication Match Rule

  • HZ: Number of Workers for Import

  • HZ: Numeric Value to Indicate NULL During Import

  • HZ: Use HR Security During Import

  • HZ: Validate Flexfields During Import

  • HZ: Work Unit Size for Import

  See: Profile Options and Profile Option Categories Overview.