Search Results hz_imp_finnumbers_sg




Overview

HZ_IMP_FINNUMBERS_SG is an internal staging table owned by the AR (Receivables) schema in Oracle E-Business Suite, introduced within the Trading Community Architecture (TCA) import framework. It is the "SG" (staging) companion to HZ_IMP_FINNUMBERS_INT, the interface table into which external data is first loaded. Both tables are part of the bulk import pipeline used to bring third-party financial-report and financial-number information for parties (customers, suppliers, organizations) into the TCA registry. The table is documented as VALID in both EBS 12.1.1 and 12.2.2 and is not intended for direct end-user maintenance; it is populated and consumed by concurrent programs and the TCA import APIs.

From the mined foreign-key structure, HZ_IMP_FINNUMBERS_SG presents itself as a standalone staging object. In Data Vault modeling terms, it is best characterized as a satellite-style staging table: it carries descriptive attributes (dates, report types, issued periods, document references) alongside the business keys and the BATCH_ID/INT_ROW_ID correlation keys, without itself acting as a persistent hub or link. This classification is a heuristic modeling suggestion, not a documented Oracle designation.

Key Information Stored

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

The documented relationships show FINANCIAL_REPORT_ID and FINANCIAL_NUMBER_ID acting as business-key candidates against their respective parent tables; INT_ROW_ID and BATCH_ID function as the pipeline surrogate keys.

Common Use Cases and Queries

The primary use case is diagnostic: monitoring an import batch and extracting failed rows. A typical pattern filters on batch and error status:

  • SELECT BATCH_ID, INT_ROW_ID, PARTY_ID, ERROR_FLAG FROM HZ_IMP_FINNUMBERS_SG WHERE BATCH_ID = :batch AND ERROR_FLAG = 'Y';
  • Tracing a staged row back to its source interface record via INT_ROW_ID.
  • Reconciling counts between HZ_IMP_FINNUMBERS_INT and the staging table across a run.
  • Reporting on imported financial numbers joined to HZ_FINANCIAL_REPORTS and HZ_FINANCIAL_NUMBERS for audit of party financial data.

Because the table is transient, queries should always be scoped by BATCH_ID to avoid full scans on a table that can hold many historical runs.

Related Objects

The most significant related objects are the interface table HZ_IMP_FINNUMBERS_INT, which feeds this staging table, and the two referenced parents, HZ_FINANCIAL_REPORTS (joined on FINANCIAL_REPORT_ID) and HZ_FINANCIAL_NUMBERS (joined on FINANCIAL_NUMBER_ID). The party resolution path relies on HZ_PARTIES and the HZ_ORIG_SYSTEMS_B reference set via PARTY_ORIG_SYSTEM and PARTY_ID. The TCA import is driven by concurrent programs and the party import APIs (such as the HZ_IMP_* package family) that orchestrate staging, validation, and commit of financial-number records into the TCA registry.