Search Results ra_customer_trx_lines_u1




Overview

RA_CUSTOMER_TRX_LINES_ALL is the core transaction line table in the Oracle Receivables (AR) module of Oracle E-Business Suite, holding every invoice, debit memo, credit memo, chargeback, deposit, and guarantee line generated during the order-to-cash cycle. Each row represents a single line belonging to a transaction header stored in RA_CUSTOMER_TRX_ALL, and the table is exposed through a multi-org view (RA_CUSTOMER_TRX_LINES) that filters data by the current operating unit via ORG_ID. In Release 12.1.1 and 12.2.2 the physical table resides in the APPS_TS_TX_DATA tablespace with 158 documented columns.

Because of the heavy inbound and outbound referential traffic documented in the ETRM metadata — 23 outgoing foreign keys and more than 30 dependent child tables — the object behaves as a hub in the AR transaction sub-model. A Data Vault modeling suggestion consistent with the FK structure is hub-leaning: the natural business key is CUSTOMER_TRX_LINE_ID, with headers, distributions, sales credits, and adjustments acting as satellites or links around it.

Key Information Stored

The surrogate primary key is CUSTOMER_TRX_LINE_ID, enforced by the unique index RA_CUSTOMER_TRX_LINES_U1 (CUSTOMER_TRX_LINE_ID) in APPS_TS_TX_IDX. This is the documented unique business-key candidate; the user query "ra_customer_trx_lines_u1" refers precisely to this index. Other important columns include:

Common Use Cases and Queries

Typical reporting joins the header and line into a single view of invoice detail:

  • Invoice line detail: select from RA_CUSTOMER_TRX_LINES_ALL l join RA_CUSTOMER_TRX_ALL h on h.CUSTOMER_TRX_ID = l.CUSTOMER_TRX_ID where h.TRX_NUMBER = :p_trx.
  • Revenue by line: aggregate EXTENDED_AMOUNT or REVENUE_AMOUNT by SET_OF_BOOKS_ID and accounting period.
  • Tax reconciliation: filter TAXABLE_FLAG = 'Y' and sum TAXABLE_AMOUNT, joining to ZX_LINES via TAX_LINE_ID.
  • Credit memo tracing: follow LINK_TO_CUST_TRX_LINE_ID back to the original invoice line, or use PREVIOUS_CUSTOMER_TRX_LINE_ID.
  • SLA accounting: join CUSTOMER_TRX_LINE_ID to RA_CUST_TRX_LINE_GL_DIST_ALL for distribution reporting.

Beware that the view filters by ORG_ID, so cross-operating-unit queries must query the _ALL table directly or set the correct org context in FND_CLIENT_INFO.

Related Objects

Together these relationships make RA_CUSTOMER_TRX_LINES_ALL the central fact-bearing table for AR reporting, tax, accounting, and revenue recognition extraction.