Search Results ar_trx_header_tmp_gt

Overview

AR_TRX_HEADER_TMP_GT is a transient staging (global temporary) table in the Oracle Receivables (AR) schema. The "TMP_GT" suffix indicates that it is a Global Temporary Table: rows are visible only to the session that inserts them and are typically purged on commit or session termination, depending on the ON COMMIT clause defined for the table. It is used by Autoinvoice and related transaction-processing programs to hold header-level invoice, debit memo, credit memo, chargeback, and deposit information in a pre-validated, pre-insert form before the data is transferred to permanent Receivables transaction tables.

The table carries a complete mirror of the header attributes required to create a transaction in AR, including bill-to, ship-to, sold-to, and paying customer references, currency and exchange-rate information, salesperson and territory assignments, payment terms, receipt method, purchase order details, and the full set of descriptive flexfield and global descriptive flexfield columns. Because it is populated and consumed within a single processing run, it is not part of the permanent analytical data model.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone, meaning the object does not cleanly resolve to a hub, link, or satellite. This is consistent with its role as a temporary work table rather than a persistent modeled entity; if it were modeled, its distinct business keys (TRX_NUMBER, TRX_HEADER_ID) and its many foreign-key references to customer, type, and legal entity dimensions would suggest link or satellite treatment, but the temporary nature of the data makes such classification impractical.

Key Information Stored

The table contains 123 documented columns in the 12.2.2 schema. The most operationally significant are:

• TRX_HEADER_ID — Surrogate identifier for the transaction header; the primary correlation key used to join against permanent transaction headers (for example PN_VAR_TRX_HEADERS_ALL) during the staging-to-permanent transfer.
• TRX_NUMBER — The business-facing transaction number; a primary business-key candidate and the value end users and reports key on.
• TRX_DATE, GL_DATE, BILLING_DATE — Transaction, accounting, and billing dates that control period assignment and revenue recognition.
• TRX_CLASS — Identifies the transaction class (invoice, debit memo, credit memo, chargeback, deposit).
• CUST_TRX_TYPE_ID — Foreign key to RA_CUST_TRX_TYPES_ALL, defining the transaction type and its accounting rules.
• TRX_CURRENCY, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, EXCHANGE_RATE — Currency and conversion attributes applied when the transaction is created.
• BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, SOLD_TO_CUSTOMER_ID, PAYING_CUSTOMER_ID — The customer parties associated with the transaction.
• BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID, PAYING_SITE_USE_ID, REMIT_TO_ADDRESS_ID — Site-use and address references that determine tax and remittance behavior.
• TERM_ID, RECEIPT_METHOD_ID — Payment terms and the receipt method (foreign key to AR_RECEIPT_METHODS) expected for the transaction.
• PRIMARY_SALESREP_ID, TERRITORY_ID — Sales credit and territory assignment information.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES, establishing the legal entity context for the transaction.
• INTEREST_HEADER_ID — Foreign key to AR_INTEREST_HEADERS_ALL, linking late-charge assessment to the transaction.
• ORG_ID — Operating unit identifier, essential for multi-org security and reporting.
• STATUS_TRX — Staging status used to track the record through validation and transfer.
• ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–30 — Descriptive flexfield and global descriptive flexfield segments carried forward from the interface.

Because the table is temporary, no permanent unique index is typically defined on TRX_NUMBER; uniqueness is enforced when the row is written to the permanent AR_TRX_HEADERS_ALL table.

Common Use Cases and Queries

The primary use case is debugging and monitoring Autoinvoice and transaction import runs. A developer or functional analyst inspects the table within the same session that populated it to determine why a header failed validation or why bill-to information was not derived correctly.

• Auditing a loaded batch: SELECT trx_number, trx_class, cust_trx_type_id, bill_to_customer_id, status_trx FROM ar.ar_trx_header_tmp_gt WHERE org_id = :org_id;
• Diagnosing missing bill-to data: comparing BILL_TO_CUSTOMER_ID against SOLD_TO_CUSTOMER_ID and PAYING_CUSTOMER_ID to detect defaulting errors.
• Validating currency conversion: reviewing TRX_CURRENCY, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, and EXCHANGE_RATE for consistency before posting.
• Reconciling legal entity and operating unit: joining LEGAL_ENTITY_ID and ORG_ID against FV_LEGAL_ENTITIES and operating unit definitions to confirm the transaction is booked in the correct entity.
• Checking late-charge linkage: verifying that INTEREST_HEADER_ID and LATE_CHARGES_ASSESSED are populated where finance charges are expected.

Because rows are session-scoped, queries against this table are only meaningful during or immediately after the concurrent request that uses it. Persistent troubleshooting should target the corresponding interface or permanent transaction tables.

Related Objects

The foreign keys documented for this table identify the principal related objects:

• PN_VAR_TRX_HEADERS_ALL — joined on TRX_HEADER_ID; the header-level view used in the staging flow.
• RA_CUST_TRX_TYPES_ALL — joined on CUST_TRX_TYPE_ID; defines transaction type and accounting rules.
• AR_RECEIPT_METHODS — joined on RECEIPT_METHOD_ID; determines the expected payment method.
• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID; supplies legal entity context.
• AR_INTEREST_HEADERS_ALL — joined on INTEREST_HEADER_ID; supports late-charge processing.
• RA_CUSTOMERS / HZ_CUST_ACCOUNTS — implicitly related through BILL_TO_CUSTOMER_ID, SHIP_TO_CUSTOMER_ID, SOLD_TO_CUSTOMER_ID, and PAYING_CUSTOMER_ID.
• AR_TRX_HEADERS_ALL / RA_CUSTOMER_TRX_ALL — the permanent transaction header tables to which staged rows are ultimately transferred.

Together these objects form the header-level portion of the Receivables transaction import pipeline, with AR_TRX_HEADER_TMP_GT serving strictly as the transient holding area for validated header data.