Results for “ar_trx_lines_tmp_gt”

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

Overview

AR_TRX_LINES_TMP_GT is a global temporary table (GTT) owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified in the ETRM repository as a VALID table object whose role is to stage transactional line data prior to persistent insert into the core AutoInvoice and Receivables transaction line tables. As the _TMP_GT suffix indicates, the object supports session- or transaction-scoped working sets that hold intermediate rows — typically before validation, tax derivation, or defaulting rules complete — and is not intended to retain data permanently.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the FK structure is standalone. That is, the table carries its own primary-key candidate columns and does not function as a pure hub, link, or satellite in the canonical Data Vault sense; it is a transient staging construct rather than a reference dimension or join entity. Treating it as a standalone staging table is the appropriate modeling suggestion.

Key Information Stored

The documented physical schema contains 119 columns; the most operationally significant are the identifiers and financial attributes below.

• TRX_HEADER_ID — foreign key to PN_VAR_TRX_HEADERS_ALL; identifies the parent transaction header.
• TRX_LINE_ID — foreign key to CN_TRX_LINES_ALL; links to the persistent transaction line.
• LINE_NUMBER — sequence of the line within the transaction.
• LINE_TYPE — categorizes the line (e.g., LINE, TAX, FREIGHT).
• INVENTORY_ITEM_ID, DESCRIPTION, UOM_CODE, QUANTITY_ORDERED, QUANTITY_INVOICED — inventory and quantity detail.
• UNIT_SELLING_PRICE, UNIT_STANDARD_PRICE, AMOUNT — pricing and financial basis.
• TAX, TAX_RATE, TAXABLE_FLAG, TAX_EXEMPT_FLAG, TAX_REGIME_CODE, TAX_JURISDICTION_CODE, TAX_CLASSIFICATION_CODE — tax determination attributes.
• ACCOUNTING_RULE_ID with RULE_START_DATE and RULE_END_DATE — revenue recognition scheduling.
• INTERFACE_LINE_CONTEXT, INTERFACE_LINE_ATTRIBUTE1 … INTERFACE_LINE_ATTRIBUTE15 — AutoInvoice descriptive flexfield mapping.
• ATTRIBUTE1 … ATTRIBUTE15 and GLOBAL_ATTRIBUTE1 … GLOBAL_ATTRIBUTE20 — extensibility columns.
• SOURCE_APPLICATION_ID, SOURCE_ENTITY_CODE, SOURCE_TRX_ID, SOURCE_TRX_LINE_ID — origin lineage for the transaction.

The surrogate primary key of the persistent counterpart is TRX_LINE_ID; business-key candidates include LINE_NUMBER in combination with TRX_HEADER_ID.

Common Use Cases and Queries

The table is primarily exercised by batch AutoInvoice and Receivables posting programs. Typical scenarios include reconciling staged lines to their source order before posting, diagnosing tax derivation failures, and reporting on lines pending acceptance into the core tables.

• Pre-post validation: count staged lines per header.
• Tax reconciliation: compare staged TAX against persisted tax lines.
• Origin tracing: filter by SOURCE_APPLICATION_ID to identify the feeder system.

A representative query pattern joining the staging table to the persistent header:

SELECT t.TRX_HEADER_ID, t.LINE_NUMBER, t.AMOUNT, t.TAX
FROM AR_TRX_LINES_TMP_GT t
WHERE t.TRX_HEADER_ID = :p_header_id
ORDER BY t.LINE_NUMBER;

Related Objects

The table relates to the following significant objects through the documented FK relationships:

• PN_VAR_TRX_HEADERS_ALL via TRX_HEADER_ID.
• CN_TRX_LINES_ALL via TRX_LINE_ID.
• AR_MEMO_LINES_ALL_B via MEMO_LINE_ID.
• MTL_MOVEMENT_STATISTICS via MOVEMENT_ID.
• IGI_DOS_TRX_SOURCES via SOURCE_TRX_ID.
• AR_INTEREST_LINES_ALL via INTEREST_LINE_ID.

These joins establish the principal lineage paths used by AutoInvoice and Receivables reporting.