Search Results link_to_trx_line_id

Overview

AR.AR_INV_API_LINES_GT is a global temporary table (GTT) in the Oracle E-Business Suite Receivables (AR) schema. It serves as the line-level staging interface for the AutoInvoice process, which imports and validates transaction data originating from external systems — most notably order management, order fulfillment, and legacy billing feeds — before that data is persisted into the permanent Receivables transaction tables. Because it is defined with a data duration of SYS$TRANSACTION, rows placed in the table are visible only to the inserting session and are removed at transaction commit or rollback, making it unsuitable for permanent storage but ideal for transient, session-scoped data transformation.

In ETRM terms, the object is documented as a standalone entity with no dependencies on other database objects, though it carries foreign key relationships to PN_VAR_TRX_HEADERS_ALL (via TRX_HEADER_ID) and CN_TRX_LINES_ALL (via TRX_LINE_ID). Applying a Data Vault heuristic, this table functions as a link-style staging construct: it records associative relationships between header-level and line-level transaction data rather than acting as a durable hub or satellite. This classification is a modeling suggestion only; the physical table remains a classical EBS interface GTT.

Key Information Stored

The table contains seventeen documented columns, of which the following are most significant for processing and integration:

• TRX_HEADER_ID — Numeric identifier of the parent transaction header; joins to PN_VAR_TRX_HEADERS_ALL. This is the principal grouping key for all lines belonging to one transaction.
• TRX_LINE_ID — Numeric identifier of the transaction line; joins to CN_TRX_LINES_ALL. Acts as the primary line reference for downstream AutoInvoice processing.
• LINK_TO_TRX_LINE_ID — The user's search term. This column links a line to a related or parent transaction line, supporting credit memo, adjustment, and line-reversal scenarios where one line must reference another.
• LINE_NUMBER — Sequential display and ordering position of the line within the transaction.
• INVENTORY_ITEM_ID and DESCRIPTION — The item and descriptive text for the invoiced line.
• QUANTITY_ORDERED and QUANTITY_INVOICED — Ordered versus billed quantities used for reconciliation and validation.
• UNIT_STANDARD_PRICE and UNIT_SELLING_PRICE — Cost-basis and revenue pricing for the line.
• AMOUNT and LINE_TYPE — Extended line value and classification (for example, LINE or TAX), which drive accounting rule application.
• ACCOUNTING_RULE_ID — Reference to the revenue recognition rule governing the line.
• SALES_ORDER, SALES_ORDER_LINE, and SALES_ORDER_DATE — Originating order reference data carried through the interface.
• REASON_CODE — Code explaining adjustments or returns.

No unique index or surrogate primary key is documented in the ETRM metadata; TRX_LINE_ID and the composite of TRX_HEADER_ID plus LINE_NUMBER serve as practical business-key candidates for de-duplication and reconciliation.

Common Use Cases and Queries

The primary use case is populating and validating AutoInvoice interface data prior to submission. A typical verification query retrieves all staged lines for a given header:

• SELECT TRX_LINE_ID, LINE_NUMBER, LINK_TO_TRX_LINE_ID, LINE_TYPE, AMOUNT FROM AR.AR_INV_API_LINES_GT WHERE TRX_HEADER_ID = :p_header_id ORDER BY LINE_NUMBER;

Analysts commonly inspect the LINK_TO_TRX_LINE_ID column to confirm that adjustments or credit lines correctly reference their originating invoice lines, detecting orphaned or misaligned links before AutoInvoice runs. Reconciliation reports compare QUANTITY_ORDERED against QUANTITY_INVOICED and UNIT_STANDARD_PRICE against UNIT_SELLING_PRICE to flag pricing or quantity discrepancies. Because the table is session-scoped, all queries must be executed from the session that performed the insert; cross-session access is not possible by design.

Related Objects

The documented foreign key relationships and dependency data identify the following significant related objects:

• PN_VAR_TRX_HEADERS_ALL — referenced via TRX_HEADER_ID; the header-level interface partner table.
• CN_TRX_LINES_ALL — referenced via TRX_LINE_ID; the permanent transaction line store.
• AR.AR_INV_API_LINES_GT itself is referenced by the APPS synonym of the same name, through which applications and concurrent programs access the GTT.
• The AutoInvoice execution program (RAXTRX) and its validation routines consume this staging data, along with the broader AR interface tables that complete the transaction load.

Together these objects form the inbound pipeline through which external billing and order data enters Receivables.