Search Results ar_inv_api_headers_gt




Overview
Explore in AI Chat

Overview

AR_INV_API_HEADERS_GT is a global temporary table in the Oracle Receivables (AR) schema. It serves as the inbound staging area for the public AutoInvoice interface. External feeder systems, legacy conversions, and subledger integrations populate this table with invoice header records, which the AutoInvoice Import program subsequently validates, derives, and transfers into the base transaction tables.

The table acts as the header-level counterpart to the AutoInvoice line and distribution staging tables. Each row carries the transactional attributes required to construct a single Receivables invoice, debit memo, credit memo, chargeback, or on-account credit. Data is typically inserted by custom PL/SQL or loader scripts, then consumed by the AutoInvoice execution, which reads the staging rows, applies grouping rules, and generates the corresponding transaction header record.

The table's structure is transient: rows are inserted by a feeder process and removed after AutoInvoice completes. Because it holds descriptive attributes tied to a business transaction identified by a natural number (TRX_NUMBER), the Data Vault classification heuristic suggests treating it as a satellite-like staging object — a transient attribute carrier keyed on business identifiers rather than a persistent hub. This classification is a modeling suggestion only, provided by the mined FK data vault heuristic.

Key Information Stored

The documented physical schema exposes 47 columns. The most operationally significant include:

The surrogate primary key is TRX_HEADER_ID. Business-key candidates include TRX_NUMBER, typically combined with ORG_ID and TRX_CLASS to scope uniqueness during staging.

Common Use Cases and Queries

Typical scenarios include populating invoices from external order management or billing engines, migrating historical transactions, and generating chargebacks or on-account credits programmatically. A common query validates staging row completeness before invoking AutoInvoice:

  • SELECT trx_number, trx_class, cust_trx_type_id, bill_to_customer_id, gl_date FROM ar_inv_api_headers_gt WHERE org_id = :org_id AND trx_number IS NOT NULL;
  • Reconciling staging against created transactions using TRX_HEADER_ID or TRX_NUMBER.
  • Diagnosing AutoInvoice rejects by joining staged headers to line and distribution staging tables.
  • Auditing LEGAL_ENTITY_ID and ORG_ID to confirm correct operating unit context.

Reporting use cases focus on interface volume, reject analysis, and pre-posting validation rather than steady-state reporting, since rows are purged after import.

Related Objects

  • PN_VAR_TRX_HEADERS_ALL — joined via TRX_HEADER_ID; holds the base transaction header.
  • RA_CUST_TRX_TYPES_ALL — joined via CUST_TRX_TYPE_ID; defines transaction types.
  • AR_RECEIPT_METHODS — joined via RECEIPT_METHOD_ID; payment receipt method.
  • FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID; legal entity context.
  • RA_CUSTOMER_TRX_ALL — receives the generated transaction after AutoInvoice processing.
  • AR_INV_API_LINES_GT — companion line-level staging table.
  • RA_INTERFACE_LINES_ALL — alternate interface for high-volume AutoInvoice loads.
  • AR_AUTOINVOICE — the public API / concurrent program that consumes these staging rows.