Import Batches Overview

After data from a source file is successfully loaded into the import interface tables, that set of data is automatically included in a new import batch. The import batch name is the same as the file load name, and the batch ID is automatically generated if the batch comes from File Load.

Aside from import batches that contain data loaded using the File Load feature, import batches with data from other methods, such as D&B Load and SQL/ETL Load, are also displayed. See: Loading Data into the Interface Tables.

Note: Data must be loaded into the interface tables in the context of a batch. If using File Load, a batch is automatically generated. For any other loading tool, create a new batch with a new unique batch ID, which is required for loading into the interface tables. See: Generating Batches.

An import batch contains information about transferring a set of records from the interface tables into the TCA Registry, including settings for optional data quality preimport processes that you can perform on the batch.

If automatic import after file load is implemented, then import batches are created with the import processes already running. If not, you must manually define the import and submit the batch for the import process. See: Setting Up Import, Oracle Customers Online Implementation Guide.

All import batches are considered active, with any import or batch status, until they are purged. See: Purging Import Batches.

Searching for Import Batches

You can search for active import batches, and purged batches in the batch import history, by:

Managing Import Batches

In the Batch Import History page, you view the purged batches in the search results. See: Viewing Batch Import History.

In the Import Batches page, after you view the search results, you can:

Related Topics