Batch Loading

Use the batch load process to update D&B information for a large number of parties on a regular schedule or whenever you need. You can update all parties, gather data only for new parties, or update parties that have not been updated since a specified date. Batch retrieval and loading of D&B information is usually a regularly scheduled, automated process that you set up and run.

When you obtain D&B information about a company that does not exist in the TCA Registry, a new party is created using the D&B data. See: Details on Creating Parties with D&B Information.

If you are batch loading to update parties that already have D&B data, only the records with a mapped D-U-N-S Number are updated. See: Source System Management Impact.

Related Topics

Process Overview

The batch loading process you use depends on the database version you are on.

Procedure for Oracle9i and Above

  1. Run the Generate Request List for DNB Batch Load program to generate a list of parties that you want to request D&B data for.

  2. Transfer the file containing the request list to D&B.

  3. Receive a properly formatted file, ready for loading, from D&B.

  4. Create a batch ID using the Create Import Batch API.

  5. Run the D&B Import Adapter request set to load D&B information into the interface tables.

    Note: If you use a method other than the D&B Import Adapter, then you must pass a valid D&B value in the CONTENT_SOURCE_TYPE column to make the information from D&B available for the Single Source of Truth record. See: Single Source of Truth Overview.

  6. Optionally verify that the D&B information is loaded into the interface tables as expected.

  7. Review the settings for import profile options and modify if needed. See: Bulk Import Deployment Category.

  8. Run the Import Batch to TCA Registry program to load D&B information from the interface tables into the appropriate HZ tables. For the Import Run Options parameter, select to run both the preimport and import processes.

  9. Correct errors, if any. Most errors occur due to changes in information codes that D&B provides for the data elements.

Procedure for Oracle8i and Below

  1. Run the Generate Request List for DNB Batch Load program to generate a list of parties that you want to request D&B data for.

  2. Transfer the file containing the request list to D&B.

  3. Receive a properly formatted file, ready for loading, from D&B.

  4. Run the SQL*Loader utility to load the provided D&B file into the HZ_PARTY_INTERFACE table. The SQL*Loader command is:

    Sqlldr userid=<User Name>/<Password>@<Database Name> control=ARHDNBGX.ctl data=<Data File Name>

    The data file name is the name of the flat file from D&B. You must pass a valid D&B value in the CONTENT_SOURCE_TYPE column to make the information from D&B available for the Single Source of Truth record.

    Each newly loaded record in the interface table has a null GROUP_ID column. If you want to import only a subset of records from the interface table into the TCA tables, you can manually populate that column with the same value for all records in the subset. You can then specify that group ID to transfer the subset of records from the interface table into TCA tables. See: Load D&B Data.

  5. Run the Load D&B Data program to load D&B information from the interface table into the appropriate TCA tables.

    Leave the Group ID parameter blank to process all records without a group ID in the interface table. By default, the records that you batch load into the HZ_PARTY_INTERFACE table from the D&B file have no group ID.

    If you do assign a group ID to any of the records, you can:

  6. Correct errors, if any.