Skip to content
Fusion Reference

RA_CUSTOMER_TRX_LINES_ALL

Product: RAtransactionBU-striped (ORG_ID)

Receivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacks

Grain note

Mixed line kinds share the table — filter LINE_TYPE = 'LINE' before summing revenue, or tax and freight inflate it; TAX/FREIGHT rows point at their parent via LINK_TO_CUST_TRX_LINE_ID

Notes

The item reference (INVENTORY_ITEM_ID + WAREHOUSE_ID) is description-only in the dictionary — no formal FK, so no item edge ships (verify-before-joining). The sales-order references are text columns with no FK — the AR → OM linkage is configuration-defined, same verdict as the EBS reference. Tax detail lives in the Fusion tax-engine tables, not on TAX rows alone.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Header & line

RA_CUSTOMER_TRX_LINES_ALL lines join back to their header RA_CUSTOMER_TRX_ALL — and the org column — so a line never fans out.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

Fields

17 fields · 1 key

17 fields.

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1CUSTOMER_TRX_LINE_IDSurrogate key of the lineNUMBER
Key
2CUSTOMER_TRX_IDThe transaction headerNUMBER
3ORG_IDThe business unit owning the lineNUMBER
4LINE_NUMBERLine number within the transactionNUMBER
5LINE_TYPERow kind — LINE rows carry the goods/services amounts; TAX, FREIGHT, and CB rows share the tableVARCHAR2
STD_LINE_TYPE
6LINK_TO_CUST_TRX_LINE_IDFor TAX and FREIGHT rows, the LINE row they attach to (self-referencing)NUMBER
7INVENTORY_ITEM_IDItem on the line — description-only in the dictionary, no formal FK; mutually exclusive with the memo lineNUMBER
8WAREHOUSE_IDShip-from organization for taxation — description-only, no formal FKNUMBER
9MEMO_LINE_SEQ_IDStandard memo line, for non-item linesNUMBER
10QUANTITY_INVOICEDQuantity invoicedNUMBER
11QUANTITY_CREDITEDQuantity credited (credit memo lines)NUMBER
12UNIT_SELLING_PRICESelling price per unitNUMBER
13EXTENDED_AMOUNTLine amountNUMBER
14REVENUE_AMOUNTLine revenue amountNUMBER
15UOM_CODEUnit of measureVARCHAR2
16SALES_ORDEROriginating sales order reference — text, no FK; the AR → OM link is configuration-definedVARCHAR2
17SALES_ORDER_LINEOriginating sales order line reference — text, no FKVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of RA_CUSTOMER_TRX_LINES_ALL on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

5 parameters not filled: <catalog>, <schema>, <business_unit_id>, <CUSTOMER_TRX_LINE_ID>, <watermark>

-- ============================================================
-- Table  : RA_CUSTOMER_TRX_LINES_ALL — Receivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacks
-- Purpose: Column-selected read of RA_CUSTOMER_TRX_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per business unit (ORG_ID) + CUSTOMER_TRX_LINE_ID
-- Caution: Mixed line kinds share the table — filter LINE_TYPE = 'LINE' before summing revenue, or tax and freight inflate it; TAX/FREIGHT rows point at their parent via LINK_TO_CUST_TRX_LINE_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.CUSTOMER_TRX_LINE_ID AS "Surrogate key of the line",
  t.CUSTOMER_TRX_ID AS "The transaction header",
  t.ORG_ID AS "The business unit owning the line",
  t.LINE_NUMBER AS "Line number within the transaction",
  CASE t.LINE_TYPE WHEN 'LINE' THEN 'Standard line' WHEN 'TAX' THEN 'Tax line' WHEN 'FREIGHT' THEN 'Freight line' WHEN 'CB' THEN 'Chargeback line' ELSE t.LINE_TYPE END AS "Row kind — LINE rows carry the goods/services amounts; TAX, FREIGHT, and CB rows share the table",  -- lookup: STD_LINE_TYPE
  t.LINK_TO_CUST_TRX_LINE_ID AS "For TAX and FREIGHT rows, the LINE row they attach to (self-referencing)",
  t.INVENTORY_ITEM_ID AS "Item on the line — description-only in the dictionary, no formal FK; mutually exclusive with the memo line",
  t.WAREHOUSE_ID AS "Ship-from organization for taxation — description-only, no formal FK",
  t.MEMO_LINE_SEQ_ID AS "Standard memo line, for non-item lines",
  t.QUANTITY_INVOICED AS "Quantity invoiced",
  t.QUANTITY_CREDITED AS "Quantity credited (credit memo lines)",
  t.UNIT_SELLING_PRICE AS "Selling price per unit",
  t.EXTENDED_AMOUNT AS "Line amount",
  t.REVENUE_AMOUNT AS "Line revenue amount",
  t.UOM_CODE AS "Unit of measure",
  t.SALES_ORDER AS "Originating sales order reference — text, no FK; the AR → OM link is configuration-defined",
  t.SALES_ORDER_LINE AS "Originating sales order line reference — text, no FK"
FROM <catalog>.<schema>.RA_CUSTOMER_TRX_LINES_ALL t
WHERE
  t.ORG_ID = <business_unit_id>  -- business unit — Fusion _ALL means BU, not the EBS operating unit; see quirks guide #all-means-bu
  -- AND t.CUSTOMER_TRX_LINE_ID = <CUSTOMER_TRX_LINE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.CUSTOMER_TRX_LINE_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • RA_CUSTOMER_TRX_ALLRA_CUSTOMER_TRX_LINES_ALLheader line · 1:N
    ON RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_LINES_ALL.CUSTOMER_TRX_ID AND RA_CUSTOMER_TRX_ALL.ORG_ID = RA_CUSTOMER_TRX_LINES_ALL.ORG_ID
  • RA_CUSTOMER_TRX_LINES_ALLRA_CUSTOMER_TRX_LINES_ALLforeign key · N:1
    ON RA_CUSTOMER_TRX_LINES_ALL1.LINK_TO_CUST_TRX_LINE_ID = RA_CUSTOMER_TRX_LINES_ALL2.CUSTOMER_TRX_LINE_ID AND RA_CUSTOMER_TRX_LINES_ALL1.ORG_ID = RA_CUSTOMER_TRX_LINES_ALL2.ORG_ID
  • RA_CUSTOMER_TRX_LINES_ALLFND_LOOKUP_VALUESFND lookup decode · N:1
    ON RA_CUSTOMER_TRX_LINES_ALL.LINE_TYPE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'STD_LINE_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'

Browse more Financials tables

More Financials tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.