Search Results ra_cust_trx_line_gl_dist_all

Overview

The RA_CUST_TRX_LINE_GL_DIST_ALL table is a core accounting table within the Oracle E-Business Suite Receivables (AR) module. It serves as the definitive repository for the General Ledger (GL) distribution records generated from transaction lines. Its primary role is to store the detailed accounting entries for revenue, unearned revenue, and unbilled receivables arising from customer transactions, such as invoices, debit memos, and credit memos. This table is central to the financial posting process, ensuring that every monetary line on a transaction creates the appropriate accounting distributions that will ultimately be transferred to the General Ledger. It operates at the "All" organization level, meaning it stores data across all operating units in a multi-org environment.

Key Information Stored

The table's structure is designed to link transactional data with its corresponding accounting impact. The primary key is the unique identifier CUST_TRX_LINE_GL_DIST_ID. The most critical foreign keys define its relationships: CUSTOMER_TRX_ID and CUSTOMER_TRX_LINE_ID link to the parent transaction and its specific line, CODE_COMBINATION_ID points to the GL account charged, and SET_OF_BOOKS_ID identifies the accounting context. Other essential columns include the ACCOUNT_CLASS, which categorizes the distribution type (e.g., REV, UNBILLED_RECEIVABLES, UNEARNED), and the accounted amounts (AMOUNT, ACCTD_AMOUNT). The POSTING_CONTROL_ID is a vital operational column used to track the status of GL transfer, indicating whether the distribution is posted, unposted, or in error.

Common Use Cases and Queries

This table is fundamental for reconciliation, audit, and custom reporting. A common use case is reconciling the AR subledger detail to the GL balances. Analysts query this table to verify the accounting entries created for a specific invoice or for a period. Troubleshooting posting failures also requires examining records where the POSTING_CONTROL_ID indicates an error state. A typical query pattern involves joining to transaction headers and lines, and GL code combinations to produce a readable audit trail.

• Sample Query for Invoice Accounting:
  SELECT d.account_class, d.amount, g.segment1, g.segment2
FROM ra_cust_trx_line_gl_dist_all d,
gl_code_combinations g,
ra_customer_trx_all t
WHERE d.code_combination_id = g.code_combination_id
AND d.customer_trx_id = t.customer_trx_id
AND t.trx_number = 'INV-12345';
• Reporting Use Case: Generating a report of all unposted distributions (POSTING_CONTROL_ID = -3) for a given set of books to identify transactions pending GL transfer.

Related Objects

As indicated by its foreign keys, RA_CUST_TRX_LINE_GL_DIST_ALL is a central hub connected to several key tables. Its most direct parent is RA_CUSTOMER_TRX_LINES_ALL, from which the transactional line details originate. It also references RA_CUSTOMER_TRX_ALL for header-level information. For accounting context, it joins to GL_CODE_COMBINATIONS (for the natural account) and historically to GL_SETS_OF_BOOKS_11I. The link to RA_CUST_TRX_LINE_SALESREPS_ALL allows for sales credit assignment tracking. Crucially, its relationship with AR_POSTING_CONTROL manages the lifecycle of the GL journal entry creation process. This table is also a primary source for the subledger accounting (SLA) and XLA (eXtensible Ledger Accounting) infrastructure in later versions of EBS.