Search Results ar_trx_dist_gt




Overview
Explore in AI Chat

Overview

AR_TRX_DIST_GT is a Receivables (AR) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2. The suffix GT identifies it as a global temporary table. In the context of Receivables, it functions as a transient staging and processing structure used during transaction distribution generation — specifically, during the accounting distribution workflow for invoices, credit memos, debit memos, chargebacks, and on-account credits. Rows are populated and consumed within a single session or processing run and are not intended for persistent storage.

The table is owned by the AR schema and contains 101 documented columns in the 12.2.2 physical schema. Its FK relationships indicate that rows are keyed against transaction headers, transaction lines, and line-level salesperson assignments. Given the presence of TRX_DIST_ID alongside foreign keys to header, line, and salesrep entities, the heuristic Data Vault classification for this object is a link, bridging three business entities — transaction header, transaction line, and salesrep — at the grain of an accounting distribution. The structure also carries satellite-like descriptive and measure attributes, but the identifying relationship pattern points primarily to a link. This classification should be treated as a modeling suggestion rather than a documented designation.

Key Information Stored

The most significant columns captured by this table include:

  • TRX_DIST_ID — the distribution identifier. In the context of this table's usage, this is the primary business key; it uniquely distinguishes each distribution row within a processing run.
  • TRX_HEADER_ID and TRX_LINE_ID — foreign references to the transaction header and transaction line, defining the distribution's source.
  • CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID — the corresponding customer transaction and line identifiers, allowing joins directly to RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL without traversing the internal header/line keys.
  • CUST_TRX_LINE_SALESREP_ID — reference to the line-level salesperson, used to attribute revenue to a rep.
  • ACCOUNT_CLASS — the receivables account class (for example, REC, REV, TAX, FREIGHT, UNBILL, SUSPENSE) that determines the accounting rule applied to the distribution.
  • AMOUNT and ACCTD_AMOUNT — the entered and accounted distribution amounts.
  • PERCENT — the allocation percentage applied to the distribution.
  • CODE_COMBINATION_ID — the General Ledger account combination the distribution posts to.
  • GL_DATE and GL_POSTED_DATE — the accounting date and the date the distribution was posted to GL.
  • SET_OF_BOOKS_ID and ORG_ID — the ledger and operating unit context, essential for multi-org and multi-ledger reporting.
  • REQUEST_ID — the concurrent request that generated the row, useful for tracing and diagnostics.
  • SEGMENT1 through SEGMENT30 — denormalized key flexfield segments corresponding to the account combination.
  • PROCESS_FLAG and ACCOUNT_SET_FLAG — control flags used by the processing program to track whether the distribution has been validated and accounted.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE and GLOBAL_ATTRIBUTE descriptor flexfields are also present. No distinct unique index on TRX_DIST_ID alone is asserted in the provided metadata; TRX_DIST_ID should be regarded as the practical business-key candidate in combination with the request context.

Common Use Cases and Queries

Because the table is a global temporary table, queries are typically executed inside the session that populated it, most often within the Receivables distribution and accounting concurrent programs. Typical diagnostic and reporting patterns include inspecting the distributions generated for a specific transaction or concurrent request, and validating account-class breakdowns before posting.

  • Trace all distributions for a given concurrent run: SELECT * FROM ar.ar_trx_dist_gt WHERE request_id = :request_id;
  • Inspect distribution amounts by account class for a customer transaction: SELECT account_class, SUM(amount) FROM ar.ar_trx_dist_gt WHERE customer_trx_id = :trx_id GROUP BY account_class;
  • Reconcile to General Ledger by account combination and GL date: join CODE_COMBINATION_ID to GL_CODE_COMBINATIONS and GL_DATE to the intended accounting period.
  • Validate revenue attribution by salesperson using CUST_TRX_LINE_SALESREP_ID aggregated against AMOUNT.
  • Detect incomplete processing by filtering on PROCESS_FLAG or rows where GL_POSTED_DATE is null.

Reports that require persistence of distribution data should read from the permanent distribution tables (for example, RA_CUST_TRX_LINE_GL_DIST_ALL) rather than from this temporary structure.

Related Objects

The following objects are most closely related, based on documented foreign keys and standard Receivables structure:

  • RA_CUSTOMER_TRX_ALL — joined on CUSTOMER_TRX_ID, the invoice or credit memo header.
  • RA_CUSTOMER_TRX_LINES_ALL — joined on CUSTOMER_TRX_LINE_ID, the transaction line.
  • RA_CUST_TRX_LINE_SALESREPS_ALL — joined on CUST_TRX_LINE_SALESREP_ID, the line salesperson assignment.
  • PN_VAR_TRX_HEADERS_ALL and CN_TRX_LINES_ALL — the header and line tables referenced by TRX_HEADER_ID and TRX_LINE_ID.
  • RA_CUST_TRX_LINE_GL_DIST_ALL — the persistent distribution table containing the committed accounting distributions.
  • GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve the account.
  • AR_GL_INTERFACE / GL_INTERFACE — the interface through which these distributions are ultimately transferred to General Ledger.

These relationships establish AR_TRX_DIST_GT as a processing intermediary between transaction capture, distribution generation, and General Ledger transfer within Receivables.