Results for “ar_trx_header_gt_n1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR.AR_TRX_HEADER_GT is a global temporary table in the Oracle Receivables (AR) schema that serves as a session-scoped staging structure for transaction header data during concurrent processing and interface programs. As documented in the ETRM 12.2.2 physical schema, the object is registered under FND Design Data AR.AR_TRX_HEADER_GT and holds a status of VALID. Its defining characteristic is its temporary nature: the table is defined as a Global Temporary Table with a data duration of SYS$SESSION, meaning the current session can see only the rows it has inserted, and those rows are removed at the end of the session. Other concurrent sessions cannot observe the contents, which makes the object well suited to batch jobs that assemble and validate header records before committing them to permanent Receivables tables.

The table is physically defined with PCT Free 10 and PCT Used 40. The documented schema carries 200 columns, reflecting the broad attribute surface of an AutoInvoice-style transaction header record. From a Data Vault modeling perspective, the metadata heuristically classifies this table as standalone — it is not modelled as a hub, link, or satellite in the mined dependency graph, which is consistent with a transient staging object whose contents are promoted to persistent entities such as RA_CUSTOMER_TRX_ALL.

Key Information Stored

The table stores the full set of attributes required to describe a Receivables transaction header during import or posting activity. The most significant columns include:

• TRX_HEADER_ID — NUMBER(15); the surrogate primary key of the staging row and the column behind the unique index AR_TRX_HEADER_GT_U1.
• CUSTOMER_TRX_ID — NUMBER(15); the permanent transaction identifier once the header has been created.
• TRX_NUMBER — VARCHAR2(20); the business-facing transaction number, indexed by AR_TRX_HEADER_GT_N1 alongside BATCH_SOURCE_ID.
• TRX_DATE, TRX_CURRENCY, TRX_CLASS — the transaction date, currency, and class that govern posting and accounting behaviour.
• BATCH_SOURCE_ID, BATCH_ID — the batch source and batch grouping used to drive AutoInvoice processing.
• SET_OF_BOOKS_ID, GL_DATE, POSTING_CONTROL_ID — accounting context and posting control for the transaction.
• CUST_TRX_TYPE_ID, CUST_TRX_TYPE_NAME — the transaction type that determines accounting rules.
• BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, SOLD_TO_CUSTOMER_ID and the corresponding account, location, contact, and site-use columns.
• TERM_ID, TERM_DUE_DATE, PRIMARY_SALESREP_ID — payment terms and salesperson attribution.
• EXCHANGE_RATE_TYPE, EXCHANGE_DATE, EXCHANGE_RATE — currency conversion inputs.
• ORG_ID — the operating unit that owns the transaction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard descriptive flexfield context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard WHO audit columns.

The unique index AR_TRX_HEADER_GT_U1 on TRX_HEADER_ID is the documented business-key candidate; AR_TRX_HEADER_GT_N1 on TRX_NUMBER and BATCH_SOURCE_ID supports lookup by number within a batch source.

Common Use Cases and Queries

This table is normally populated by AutoInvoice or a custom interface program, then joined back to validated master data before insertion into the permanent transaction tables. Typical patterns include counting staged headers for a batch, identifying headers that lack a transaction type or currency, and joining to reference tables to enrich the payload.

A representative query counting staged rows is:

• SELECT COUNT(*) FROM ar.ar_trx_header_gt;
• SELECT trx_header_id, trx_number, trx_date, trx_currency FROM ar.ar_trx_header_gt WHERE batch_source_id = :p_source;
• SELECT h.trx_header_id, h.trx_number, t.name FROM ar.ar_trx_header_gt h, ra_cust_trx_types_all t WHERE h.cust_trx_type_id = t.cust_trx_type_id;

Because the table is session-scoped, the data is available only to the session that inserted it, so extraction and reporting must occur within the same database session or concurrent request that loaded it.

Related Objects

The ETRM dependency data documents several foreign-key relationships that anchor the staging rows to persistent entities:

• RA_CUST_TRX_TYPES_ALL — joined on CUST_TRX_TYPE_ID.
• AR_POSTING_CONTROL — joined on POSTING_CONTROL_ID.
• AR_RECEIPT_METHODS — joined on RECEIPT_METHOD_ID.
• AR_INTEREST_HEADERS_ALL — joined on INTEREST_HEADER_ID.
• FND_DOCUMENT_SEQUENCES — joined on DOC_SEQUENCE_ID.
• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID.
• ASO_SHIPMENTS — joined on SHIPMENT_ID.
• PN_VAR_TRX_HEADERS_ALL — joined on TRX_HEADER_ID.

Together these relationships illustrate the table's role as a transient staging repository whose validated contents are ultimately transferred to the core Receivables transaction tables during the AutoInvoice lifecycle.