Search Results hz_imp_batch_details_pk

Overview

The HZ_IMP_BATCH_DETAILS table is an Oracle Receivables (AR) transactional table that stores detail-level information about imports of records from the interface tables into the TCA (Trading Community Architecture) Registry. It is a component of the customer data import infrastructure, which moves staged party, account, and location data from staging/interface tables into the production HZ_ and related TCA tables. The table is owned by the AR schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Each row in HZ_IMP_BATCH_DETAILS captures one execution (run) of an import batch, including the number of times the batch has run, its import status, and the concurrent request identifier associated with the run. The batch is defined at the summary level in HZ_IMP_BATCH_SUMMARY, and HZ_IMP_BATCH_DETAILS records the individual run-level outcomes for that batch. From a heuristic Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning — it stores descriptive, run-specific attributes that depend on a parent batch entity (the hub/link), which is consistent with its role as a detail companion to HZ_IMP_BATCH_SUMMARY.

Key Information Stored

The table contains 15 documented columns. The composite primary key, enforced by HZ_IMP_BATCH_DETAILS_PK, consists of BATCH_ID and RUN_NUMBER. A unique index, HZ_IMP_BATCH_DETAILS_U1, also covers (BATCH_ID, RUN_NUMBER), making this pair the business-key candidate that uniquely identifies a single batch run.

• BATCH_ID — Identifies the parent import batch; also the foreign key to HZ_IMP_BATCH_SUMMARY.BATCH_ID.
• RUN_NUMBER — Sequence number of the batch execution, distinguishing multiple runs of the same batch.
• IMPORT_REQ_ID — Import request identifier associated with this detail run, linking to the concurrent request that performed the import.
• IMPORT_STATUS — Status of the import for this run (for example, the outcome of moving records into the TCA Registry).
• DUP_BATCH_ID — Reference to a duplicate batch, used when a batch is identified as a duplicate of an earlier import.
• MAIN_CONC_REQ_ID — Identifier of the main concurrent request managing the overall import job.
• REQUEST_ID — Concurrent request identifier for the run, tied to FND_CONCURRENT_REQUESTS for audit and diagnostics.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard concurrent program context columns identifying the program that created or updated the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata.

The surrogate primary key is the composite (BATCH_ID, RUN_NUMBER); the business-key candidate is the same pair surfaced through the unique index HZ_IMP_BATCH_DETAILS_U1.

Common Use Cases and Queries

The primary use case is monitoring and troubleshooting TCA import jobs. Administrators query run-level statuses to determine how many times a batch executed and whether each run completed successfully. A typical query retrieves the latest run for a given batch, for example joining HZ_IMP_BATCH_DETAILS to HZ_IMP_BATCH_SUMMARY on BATCH_ID and filtering by IMPORT_STATUS or RUN_NUMBER.

• Import status reporting — List all runs for a batch with their IMPORT_STATUS, ordered by RUN_NUMBER, to trace the import lifecycle.
• Concurrent request reconciliation — Join IMPORT_REQ_ID, MAIN_CONC_REQ_ID, or REQUEST_ID to FND_CONCURRENT_REQUESTS to correlate import outcomes with concurrent program logs.
• Duplicate detection — Query DUP_BATCH_ID to identify batches flagged as duplicates and to understand re-import behavior.
• Audit and history — Use CREATION_DATE and LAST_UPDATE_DATE to establish when imports were executed and last modified.

A representative pattern identifies failed imports: select from HZ_IMP_BATCH_DETAILS where IMPORT_STATUS indicates failure and join to HZ_IMP_BATCH_SUMMARY for batch-level context.

Related Objects

• HZ_IMP_BATCH_SUMMARY — Parent batch table joined on BATCH_ID; HZ_IMP_BATCH_DETAILS.BATCH_ID is the documented foreign key to HZ_IMP_BATCH_SUMMARY. This is the principal dependency.
• FND_CONCURRENT_REQUESTS — Referenced through REQUEST_ID, IMPORT_REQ_ID, and MAIN_CONC_REQ_ID to retrieve concurrent program execution details.
• FND_CONCURRENT_PROGRAMS — Referenced indirectly via PROGRAM_ID and PROGRAM_APPLICATION_ID to identify the import program.
• HZ_IMP_BATCH_DETAILS_U1 / HZ_IMP_BATCH_DETAILS_PK — The unique index and primary key constraints that enforce uniqueness on (BATCH_ID, RUN_NUMBER).
• TCA Registry tables (HZ_PARTIES, HZ_LOCATIONS, HZ_CUST_ACCOUNTS) — The destination objects into which the import process loads records and where IMPORT_STATUS outcomes ultimately apply.

As a satellite-leaning detail table, HZ_IMP_BATCH_DETAILS should be queried alongside its parent HZ_IMP_BATCH_SUMMARY to obtain complete import batch context.