Search Results ar_trx_header_gt




Overview
Explore in AI Chat

Overview

AR_TRX_HEADER_GT is a Receivables (AR) module table owned by the AR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix "GT" designates a global temporary table, indicating that rows are session-scoped and typically persist for the duration of a transaction or concurrent program run rather than as permanent application data. In practice, AR_TRX_HEADER_GT functions as a transient staging and workspace structure used by AutoInvoice, transaction copy, printing, and posting processes to hold receivables transaction header information before it is validated, defaulted, and committed to the permanent transaction tables.

The table is documented with 200 columns, mirroring the column set of the production transaction header entity (RA_CUSTOMER_TRX_ALL and its interface counterpart RA_INTERFACE_LINES_ALL). Under the heuristic Data Vault classification mined from its foreign-key structure, AR_TRX_HEADER_GT is assessed as a standalone object. As a modeling suggestion, this reflects that the table carries no dependent child objects of its own and primarily serves as a staging satellite feeding transactional hub and link structures elsewhere; it is not itself a canonical hub, link, or satellite in the warehouse sense.

Key Information Stored

The single documented unique index, AR_TRX_HEADER_GT_U1, is defined on TRX_HEADER_ID, making that column the business-key candidate for the staging row. The surrogate primary key relationship is expressed through the foreign key TRX_HEADER_ID → PN_VAR_TRX_HEADERS_ALL. The most functionally significant columns include:

Common Use Cases and Queries

Because the table is a temporary workspace, queries are ordinarily run within the same session or concurrent request that populated it. Common scenarios include debugging AutoInvoice validation failures, inspecting defaulted values before commit, and reconciling staged headers against production transactions.

  • Inspect rows staged for a specific batch source or request: 
    SELECT trx_header_id, trx_number, trx_date, trx_class, complete_flag
FROM   ar.ar_trx_header_gt
WHERE  request_id = :request_id;
  • Identify incomplete or unposted headers prior to commit: 
    SELECT trx_header_id, trx_number, status_trx, posting_control_id
FROM   ar.ar_trx_header_gt
WHERE  complete_flag = 'N';
  • Compare staged headers with their production counterparts using the business key: 
    SELECT g.trx_header_id, g.trx_number, a.customer_trx_id
FROM   ar.ar_trx_header_gt g, ar.ra_customer_trx_all a
WHERE  g.customer_trx_id = a.customer_trx_id (+);

Related Objects

The documented foreign keys establish the following significant relationships:

These relationships confirm the table's role as a transient header staging structure whose foreign keys point to the master reference data required to validate and post receivables transactions.