Search Results hz_imp_batch_summary_pk

Overview

HZ_IMP_BATCH_SUMMARY is a transactional control and statistics table owned by the AR schema in Oracle E-Business Suite, positioned within the Receivables (AR) product family and the Trading Community Architecture (TCA) bulk import framework. Its documented purpose is to store information about import batches — each row represents a single bulk import run through which parties, addresses, contacts, contact points, relationships, classifications, credit ratings, financial reports, and financial numbers are loaded into the TCA registry from external sources or interface staging tables. It is the master header record that governs the lifecycle and outcome of one import batch.

From a modeling perspective, the documented foreign-key structure supports a hub-leaning classification: the table is referenced by a broad set of interface and error tables through the shared BATCH_ID column, functioning as the central parent key around which the import detail tables revolve. It should be treated as a hub-style entity rather than a satellite, since dependent staging and error tables carry foreign keys to it rather than the reverse.

Key Information Stored

The table contains 158 documented columns. The surrogate primary key is BATCH_ID, enforced by HZ_IMP_BATCH_SUMMARY_PK and also carried by the unique index HZ_IMP_BATCH_SUMMARY_U1, making it the single documented business-key candidate. The most operationally significant columns fall into several groups:

• Identification and source: BATCH_NAME, DESCRIPTION, ORIGINAL_SYSTEM, LOAD_TYPE, and EST_NO_OF_RECORDS.
• Status and processing control: BATCH_STATUS, IMPORT_STATUS, CSV_STATUS, BATCH_DEDUP_STATUS, ADDR_VAL_STATUS, and MAIN_CONC_STATUS.
• Concurrent program tracking: BATCH_DEDUP_REQ_ID, ADDR_VAL_REQ_ID, IMPORT_REQ_ID, CSV_LOAD_REQ_ID, and MAIN_CONC_REQ_ID.
• Behavioral flags: BATCH_DEDUP_FLAG, REGISTRY_DEDUP_FLAG, REMOVE_DUPS_FLAG, VALIDATE_FLEXFIELD_FLAG, WHAT_IF_FLAG, and AUTOMERGE_FLAG. These drive duplicate resolution and validation behavior during import.
• Volume and outcome counters: TOTAL_BATCH_RECORDS, TOTAL_RECORDS_FOR_IMPORT, TOTAL_RECORDS_IMPORTED, TOTAL_ERRORS, TOTAL_INSERTS, TOTAL_UPDATES, TOTAL_MERGE_REQUESTS, and TOTAL_AUTO_MERGED.
• Per-entity tallies: counts such as PARTIES_IN_BATCH, ADDRESSES_IN_BATCH, CONTACTS_IN_BATCH, NEW_UNIQUE_PARTIES, POTENTIAL_DUP_PARTIES, and EXISTING_PARTIES, with parallel columns for addresses, contacts, contact points, and relationships.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and REQUEST_ID.
• Purge tracking: PURGE_DATE, PURGED_BY_USER_ID, and REMOVED_BY_USER.

Common Use Cases and Queries

The table is most frequently queried to monitor the progress and success of TCA bulk imports, to reconcile error counts against loaded volumes, and to identify batches eligible for purge.

To retrieve the current status and outcome of a specific batch:

SELECT batch_id, batch_name, batch_status, import_status,
       total_records_imported, total_errors
FROM   hz_imp_batch_summary
WHERE  batch_id = :p_batch_id;

To find recent batches that completed with errors:

SELECT batch_id, batch_name, creation_date, total_errors
FROM   hz_imp_batch_summary
WHERE  total_errors > 0
AND    creation_date > SYSDATE - 30
ORDER BY creation_date DESC;

A typical reconciliation joins the summary to the interface tables on BATCH_ID to compare staged rows against reported totals. Reporting use cases include import throughput dashboards, duplicate-handling effectiveness (comparing potential versus auto-merged counts), and purge candidate identification using PURGE_DATE.

Related Objects

The following objects reference HZ_IMP_BATCH_SUMMARY through the shared BATCH_ID column and represent the most significant dependencies:

• HZ_IMP_BATCH_DETAILS — holds per-record detail for the batch (BATCH_ID).
• HZ_IMP_ERRORS — stores import errors associated with the batch (BATCH_ID).
• HZ_IMP_ADDRESSES_INT — staged address records for the batch (BATCH_ID).
• HZ_IMP_CONTACTS_INT — staged contact records (BATCH_ID).
• HZ_IMP_CONTACTPTS_INT — staged contact point records (BATCH_ID).
• HZ_IMP_RELSHIPS_INT — staged relationship records (BATCH_ID).
• HZ_IMP_FINNUMBERS_INT and HZ_IMP_FINREPORTS_INT — staged financial numbers and reports (BATCH_ID).
• HZ_IMP_CLASSIFICS_INT and HZ_IMP_CREDITRTNGS_INT — staged classifications and credit ratings (BATCH_ID).

These dependencies confirm the table's role as the controlling parent for the TCA bulk import staging and error infrastructure.