Search Results RA_CUSTOMER_TRX_LINES_ALL




Overview
Explore in AI Chat

Overview

The RA_CUSTOMER_TRX_LINES_ALL table is a core transaction line-level table within Oracle E-Business Suite Receivables (AR). It stores detailed line information for all customer transaction documents, including invoices, debit memos, chargebacks, credit memos, and commitments. Each record in this table represents a single line item on a transaction header stored in RA_CUSTOMER_TRX_ALL. Its primary role is to capture the specific goods, services, adjustments, or financial details that constitute the total amount of a transaction, enabling detailed accounting, reporting, and tax calculation at the line level. The table is multi-organization enabled, as indicated by the '_ALL' suffix, meaning it stores data for all operating units with appropriate security via the MOAC (Multi-Org Access Control) architecture in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which delineate its critical relationships and data points. The primary identifier is CUSTOMER_TRX_LINE_ID. Each line is uniquely tied to a transaction header via the CUSTOMER_TRX_ID foreign key to RA_CUSTOMER_TRX_ALL and is sequentially ordered by LINE_NUMBER. Key descriptive and financial columns include quantities, unit prices, extended amounts, and line types. The table also stores references to related entities through numerous foreign keys, such as MEMO_LINE_ID for descriptive text, VAT_TAX_ID for tax rules, and CONTRACT_LINE_ID for integration with Oracle Contracts. Critical columns for adjustments and billing revenue management include LINK_TO_CUST_TRX_LINE_ID and INITIAL_CUSTOMER_TRX_LINE_ID, which track line-level relationships for credit memos and revenue scheduling. Ship-to customer and contact details are stored via SHIP_TO_CUSTOMER_ID and SHIP_TO_CONTACT_ID.

Common Use Cases and Queries

This table is central to any reporting or data extraction involving transactional line details. Common use cases include detailed invoice line reporting, revenue recognition analysis, tax reporting at the line level, and tracing the lifecycle of a line item through credits and adjustments. A fundamental query joins the line table to its header and other key descriptive tables:

  • Sample Query for Invoice Lines: SELECT ctl.line_number, ctl.extended_amount, ml.name memo_line, ct.trx_number FROM ra_customer_trx_lines_all ctl JOIN ra_customer_trx_all ct ON ct.customer_trx_id = ctl.customer_trx_id LEFT JOIN ar_memo_lines_all_b ml ON ml.memo_line_id = ctl.memo_line_id WHERE ct.trx_number = 'INV12345' ORDER BY ctl.line_number;
  • Linking Credits to Original Invoices: Queries often use LINK_TO_CUST_TRX_LINE_ID to find which original invoice line a credit memo line is reversing.
  • Revenue Recognition Reporting: Lines are analyzed alongside the RA_CUSTOMER_TRX_LINES_ALL table itself via the INITIAL_CUSTOMER_TRX_LINE_ID to follow revenue schedules back to their source line.

Related Objects

As evidenced by its extensive foreign key relationships, RA_CUSTOMER_TRX_LINES_ALL is a central hub connected to numerous critical Receivables and cross-application objects. The primary relationship is with the transaction header, RA_CUSTOMER_TRX_ALL. It is directly referenced by adjustment and payment schedule tables like AR_ADJUSTMENTS_ALL and AR_PAYMENT_SCHEDULES_ALL for billing revenue (BR) processes. For descriptive content, it links to AR_MEMO_LINES_ALL_B. Tax-related links include RA_TAX_EXEMPTIONS_ALL and AR_VAT_TAX_ALL_B. Integration with other EBS modules is shown via foreign keys to OKC_K_LINES_B (Contracts), HZ_CUST_ACCOUNTS (Trading Community), and IBY_FNDCPT_TX_EXTENSIONS (Payments). Importantly, the table has a recursive relationship with itself to manage line-level crediting and revenue scheduling hierarchies.