Search Results ar_trx_lines_gt




Overview
Explore in AI Chat

Overview

AR_TRX_LINES_GT is a global temporary table in the Oracle Receivables (AR) module of Oracle E-Business Suite, owned by the AR schema. In releases 12.1.1 and 12.2.2 it carries a documented physical definition of 148 columns and is catalogued as VALID within the Receivables product. The suffix "GT" identifies it as a transient, session-scoped work structure rather than a permanent transactional store; rows are typically visible only to the session that inserts them and are cleared at transaction or session end depending on the ON COMMIT clause defined at creation.

The table functions as an intermediate collection point for transaction line data during Receivables processing. It holds line-level attributes that mirror the structure of the permanent transaction line entities, allowing concurrent programs, AutoInvoice-style flows, and custom extensions to stage, transform, and validate line records before they are committed to the base transaction tables. Because it is a temporary structure, it is not a candidate for long-term retention or audit, and its contents should never be treated as authoritative.

The provided metadata classifies the object heuristically as standalone within a Data Vault model. Under that suggested reading, the table behaves as an independent staging area rather than a true hub, link, or satellite; it references multiple parent entities through foreign keys but is not itself a durable integration point.

Key Information Stored

The physical schema documents a surrogate primary key and business-key candidate through the unique index AR_TRX_LINES_GT_U1 on TRX_LINE_ID, which uniquely identifies each staged line.

Common Use Cases and Queries

Typical usage centers on populating the table from a source query and then validating or transferring the staged lines.

  • Inserting lines collected from an external interface and validating them before loading permanent transaction lines.
  • Joining back to PN_VAR_TRX_HEADERS_ALL to reconcile line counts and amounts per header.
  • Reporting on tax and revenue attributes for a request, using REQUEST_ID to isolate a single concurrent run.
  • Detecting duplicate or orphaned lines by comparing TRX_LINE_ID values against the permanent AR tables.

A representative query pattern is:

SELECT l.trx_line_id, l.trx_header_id, l.line_number,
       l.extended_amount, l.currency_code
FROM   ar.ar_trx_lines_gt l
WHERE  l.request_id = :p_request_id
ORDER  BY l.trx_header_id, l.line_number;

Because rows are session-scoped, any diagnostic query must run within the same session or concurrent request that populated the table.

Related Objects

The documented foreign keys identify the principal objects that the staged data references:

These relationships confirm that AR_TRX_LINES_GT aggregates attributes drawn from transaction, memo, interest, inventory, and tax source entities, positioning it as a convergence point for staged Receivables line data rather than a system of record.