Search Results hz_imp_finreports_int




Overview
Explore in AI Chat

Overview

HZ_IMP_FINREPORTS_INT is a TCA (Trading Community Architecture) interface table owned by the AR schema in Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It serves as the staging area for inbound financial report data that is ultimately loaded into the base table HZ_FINANCIAL_REPORTS. Records are inserted into this interface table by external systems, batch loaders, or custom integration programs, then processed by the TCA import concurrent programs that validate, transform, and migrate the data into the production financial reports entity.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The table carries a foreign key to HZ_IMP_BATCH_SUMMARY via BATCH_ID, indicating it is functionally dependent on and descriptive of a parent batch context rather than acting as a standalone hub of business keys. This makes it most naturally modeled as a satellite attached to the batch (and, transitively, party) hub.

Key Information Stored

The table comprises 37 documented columns. The BATCH_ID column is a foreign key referencing HZ_IMP_BATCH_SUMMARY, grouping interface rows into import batches and serving as the primary operational grouping key. PARTY_ORIG_SYSTEM and PARTY_ORIG_SYSTEM_REFERENCE together form the business-key candidate identifying the originating party record, while PARTY_ID stores the resolved internal party identifier. TYPE_OF_FINANCIAL_REPORT and DOCUMENT_REFERENCE describe the report itself, with DATE_REPORT_ISSUED, ISSUED_PERIOD, REPORT_START_DATE, and REPORT_END_DATE capturing the temporal scope. Numerous indicator columns — INSERT_UPDATE_FLAG, AUDIT_IND, CONSOLIDATED_IND, ESTIMATED_IND, FINAL_IND, FISCAL_IND, FORECAST_IND, OPENING_IND, PROFORMA_IND, QUALIFIED_IND, RESTATED_IND, SIGNED_BY_PRINCIPALS_IND, TRIAL_BALANCE_IND, and UNBALANCED_IND — flag report characteristics. INTERFACE_STATUS and ERROR_ID drive processing state and error diagnostics. The WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), the request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), and CREATED_BY_MODULE provide audit and concurrent program traceability.

Common Use Cases and Queries

Typical scenarios include monitoring import batch status, diagnosing rejected rows, and reconciling staged versus loaded records. A common diagnostic query joins the interface table to the batch summary:

  • SELECT i.batch_id, i.interface_status, i.error_id FROM hz_imp_finreports_int i WHERE i.interface_status = 'ERROR';
  • SELECT i.party_orig_system_reference, i.type_of_financial_report, i.date_report_issued FROM hz_imp_finreports_int i WHERE i.batch_id = :batch_id;
  • Reconciliation queries match interface rows against HZ_FINANCIAL_REPORTS by party and document reference to confirm successful load.
  • Batch throughput reporting groups counts by BATCH_ID and INTERFACE_STATUS to track import performance.

Related Objects

The most significant related objects are HZ_IMP_BATCH_SUMMARY, the parent batch table joined on BATCH_ID, and HZ_FINANCIAL_REPORTS, the target base table populated during import. The TCA import concurrent programs and the HZ party import APIs (such as the party/account import routines) drive processing from this staging table. Related staging and validation tables in the HZ_IMP_* family follow the same interface pattern, and error diagnostics reference ERROR_ID values surfaced through import error reporting. These relationships should be validated against the specific patch level, as TCA import table structures can vary across releases.