Skip to content
EBS Reference

RA_CUSTOMER_TRX_LINES_ALL

Schema: ARtransactionOU-striped (ORG_ID)

Receivables transaction lines — product lines, tax, and freight share the table by line type, with quantities, selling price, and the extended amount revenue analytics sum

Module: FinancialsOperating-unit striped (ORG_ID)Header: RA_CUSTOMER_TRX_ALL
Grain note

LINE, TAX, and FREIGHT rows share this table — filter LINE_TYPE before summing or tax and freight inflate product revenue

Notes

The order-management linkage columns (SALES_ORDER, SALES_ORDER_LINE, the interface attributes) are TEXT, and which attribute holds the order line id is transaction-source configuration — treat any join through them as environment-verified convention, which is why this catalog draws no edge. TAX and FREIGHT rows point at their parent product line through LINK_TO_CUST_TRX_LINE_ID.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

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.

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1CUSTOMER_TRX_LINE_IDSurrogate key of the lineNUMBER
Key
2CUSTOMER_TRX_IDThe parent transactionNUMBER
3ORG_IDOperating unitNUMBER
4LINE_NUMBERLine number within the documentNUMBER
5LINE_TYPELINE, TAX, FREIGHT, or CHARGES (per the line-type lookup) — filter to LINE for product revenueVARCHAR2
6LINK_TO_CUST_TRX_LINE_IDTies tax and freight rows to their parent product lineNUMBER
7INVENTORY_ITEM_IDThe invoiced item, when item-basedNUMBER
8WAREHOUSE_IDThe ship-from inventory org — the org half of this table's item joinNUMBER
9DESCRIPTIONLine descriptionVARCHAR2
10QUANTITY_ORDEREDQuantity orderedNUMBER
11QUANTITY_INVOICEDQuantity invoicedNUMBER
12QUANTITY_CREDITEDQuantity credited by memosNUMBER
13UOM_CODEUOM of the quantitiesVARCHAR2
14UNIT_SELLING_PRICESelling price per unitNUMBER
15EXTENDED_AMOUNTThe line amount — SUM only after filtering LINE_TYPENUMBER
16REVENUE_AMOUNTThe revenue portion of the lineNUMBER
17SALES_ORDERThe originating sales order number — TEXT, not an id; a display reference onlyVARCHAR2
18INTERFACE_LINE_CONTEXTAutoInvoice line context — which attribute holds the order line id is source configuration; no reliable typed join existsVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading RA_CUSTOMER_TRX_LINES_ALLon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark 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
-- ============================================================
-- Table  : RA_CUSTOMER_TRX_LINES_ALL — Receivables transaction lines — product lines, tax, and freight share the table by line type, with quantities, selling price, and the extended amount revenue analytics sum
-- Purpose: Column-selected read of RA_CUSTOMER_TRX_LINES_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + CUSTOMER_TRX_LINE_ID
-- Caution: LINE, TAX, and FREIGHT rows share this table — filter LINE_TYPE before summing or tax and freight inflate product revenue
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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 parent transaction",
  t.ORG_ID AS "Operating unit",
  t.LINE_NUMBER AS "Line number within the document",
  t.LINE_TYPE AS "LINE, TAX, FREIGHT, or CHARGES (per the line-type lookup) — filter to LINE for product revenue",
  t.LINK_TO_CUST_TRX_LINE_ID AS "Ties tax and freight rows to their parent product line",
  t.INVENTORY_ITEM_ID AS "The invoiced item, when item-based",
  t.WAREHOUSE_ID AS "The ship-from inventory org — the org half of this table's item join",
  t.DESCRIPTION AS "Line description",
  t.QUANTITY_ORDERED AS "Quantity ordered",
  t.QUANTITY_INVOICED AS "Quantity invoiced",
  t.QUANTITY_CREDITED AS "Quantity credited by memos",
  t.UOM_CODE AS "UOM of the quantities",
  t.UNIT_SELLING_PRICE AS "Selling price per unit",
  t.EXTENDED_AMOUNT AS "The line amount — SUM only after filtering LINE_TYPE",
  t.REVENUE_AMOUNT AS "The revenue portion of the line",
  t.SALES_ORDER AS "The originating sales order number — TEXT, not an id; a display reference only",
  t.INTERFACE_LINE_CONTEXT AS "AutoInvoice line context — which attribute holds the order line id is source configuration; no reliable typed join exists"
FROM <catalog>.<schema>.RA_CUSTOMER_TRX_LINES_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- AND t.CUSTOMER_TRX_LINE_ID = <CUSTOMER_TRX_LINE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CUSTOMER_TRX_LINE_ID;

5 parameters not filled: <catalog>, <schema>, <operating_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

  • 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_ALLMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON RA_CUSTOMER_TRX_LINES_ALL.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND RA_CUSTOMER_TRX_LINES_ALL.WAREHOUSE_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Financialstables →

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.