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
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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.
- FscmTopModelAM.FinExtractAM.ArBiccExtractAM.TransactionLineExtractPVOOTBI: Receivables - Transactions Real Time
Transaction Line data store — keyed on RaCustomerTrxLineCustomerTrxLineId.
Oracle data-store documentation →
Fields
17 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CUSTOMER_TRX_LINE_ID | Surrogate key of the line | NUMBER | Key |
| 2 | CUSTOMER_TRX_ID | The transaction header | NUMBER | |
| 3 | ORG_ID | The business unit owning the line | NUMBER | |
| 4 | LINE_NUMBER | Line number within the transaction | NUMBER | |
| 5 | LINE_TYPE | Row kind — LINE rows carry the goods/services amounts; TAX, FREIGHT, and CB rows share the table | VARCHAR2 | STD_LINE_TYPE |
| 6 | LINK_TO_CUST_TRX_LINE_ID | For TAX and FREIGHT rows, the LINE row they attach to (self-referencing) | NUMBER | |
| 7 | INVENTORY_ITEM_ID | Item on the line — description-only in the dictionary, no formal FK; mutually exclusive with the memo line | NUMBER | |
| 8 | WAREHOUSE_ID | Ship-from organization for taxation — description-only, no formal FK | NUMBER | |
| 9 | MEMO_LINE_SEQ_ID | Standard memo line, for non-item lines | NUMBER | |
| 10 | QUANTITY_INVOICED | Quantity invoiced | NUMBER | |
| 11 | QUANTITY_CREDITED | Quantity credited (credit memo lines) | NUMBER | |
| 12 | UNIT_SELLING_PRICE | Selling price per unit | NUMBER | |
| 13 | EXTENDED_AMOUNT | Line amount | NUMBER | |
| 14 | REVENUE_AMOUNT | Line revenue amount | NUMBER | |
| 15 | UOM_CODE | Unit of measure | VARCHAR2 | |
| 16 | SALES_ORDER | Originating sales order reference — text, no FK; the AR → OM link is configuration-defined | VARCHAR2 | |
| 17 | SALES_ORDER_LINE | Originating sales order line reference — text, no FK | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of RA_CUSTOMER_TRX_LINES_ALLon 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.
-- ============================================================
-- 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;5 parameters not filled: <catalog>, <schema>, <business_unit_id>, <CUSTOMER_TRX_LINE_ID>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
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 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>'