Search Results hz_imp_finnumbers_int




Overview
Explore in AI Chat

Overview

HZ_IMP_FINNUMBERS_INT is the TCA (Trading Community Architecture) interface table that stages inbound financial-number data before it is validated and loaded into the base table HZ_FINANCIAL_NUMBERS. It resides in the AR schema (Oracle Receivables) and is registered as a VALID object in EBS 12.1.1 and 12.2.2. The table serves as the landing zone for the TCA Import batch process, which reads staged rows, applies validation rules, resolves party references, and either promotes each record to HZ_FINANCIAL_NUMBERS or flags it with an error.

The object is tightly coupled to a batch-processing model: every staged row carries a BATCH_ID that groups it with a parent run record in HZ_IMP_BATCH_SUMMARY. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning — the table describes descriptive attributes of a party's financial identifiers and depends on a single documented foreign key (to the batch summary) rather than acting as a standalone hub or associative link. This classification is a modeling suggestion based on FK structure, not an enforced design constraint.

Key Information Stored

The table contains 28 documented columns. The most operationally significant are:

The schema does not expose a single-column surrogate primary key in the documented metadata; identity is derived from BATCH_ID plus party/source-system elements. Standard TCA audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY_MODULE) are also present.

Common Use Cases and Queries

Typical scenarios include pre-load validation reporting, interface error triage, and batch reconciliation.

  • Batch status review: count rows per batch and status. 
    SELECT batch_id, interface_status, COUNT(*)
FROM   ar.hz_imp_finnumbers_int
GROUP  BY batch_id, interface_status;
  • Error investigation: join to HZ_IMP_BATCH_SUMMARY and filter on ERROR_ID to identify failed rows and their owning run.
  • Party resolution audit: confirm that either PARTY_ID or the PARTY_ORIG_SYSTEM/PARTY_ORIG_SYSTEM_REFERENCE pair is populated before promotion to HZ_FINANCIAL_NUMBERS.
  • Insert-vs-update planning: group by INSERT_UPDATE_FLAG to forecast loader behavior.
  • Reconciliation reporting: compare staged rows to the target base table after the import program completes.

Related Objects

  • HZ_IMP_BATCH_SUMMARY — Parent batch record; join on BATCH_ID.
  • HZ_FINANCIAL_NUMBERS — Target base table populated by the TCA Import process.
  • HZ_PARTIES — Party master resolved via PARTY_ID or the original-system pair.
  • HZ_IMP_ERRORS_INT (or equivalent TCA error staging) — Referenced through ERROR_ID.
  • TCA Import concurrent programs (e.g., HZCPIMP family) and the HZ_IMP_*_INT staging family, which share the BATCH_ID convention.