RA_CUSTOMER_TRX_ALL
Schema: ARtransactionOU-striped (ORG_ID)Receivables transaction headers — invoices, credit and debit memos, chargebacks, and deposits share the table, classified by transaction type; the revenue-document anchor of order-to-cash
TRX_NUMBER is unique only per batch source — join on CUSTOMER_TRX_ID. Incomplete documents (COMPLETE_FLAG = 'N') must be filtered out of revenue. The tie back to order lines rides text-typed interface columns whose meaning is source-configuration-defined — disclosed on the lines table, no edge drawn.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Header & line
RA_CUSTOMER_TRX_ALL is the header for its lines in RA_CUSTOMER_TRX_LINES_ALL.
Fields
18 fields · 1 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CUSTOMER_TRX_ID | Surrogate key of the transaction — the join key; the display number is not unique alone | NUMBER | Primary-key field |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | TRX_NUMBER | The document number users see — unique only per batch source | VARCHAR2 | |
| 4 | TRX_DATE | The invoice date — the primary analysis date | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 5 | CUST_TRX_TYPE_ID | The transaction type — invoice vs credit memo vs debit memo classification (type table not cataloged) | NUMBER | |
| 6 | BATCH_SOURCE_ID | The batch source the document arrived through | NUMBER | |
| 7 | COMPLETE_FLAG | Y once the document is complete — filter incomplete documents out of revenue | VARCHAR2 | |
| 8 | BILL_TO_CUSTOMER_ID | The bill-to customer ACCOUNT (TCA id) | NUMBER | |
| 9 | BILL_TO_SITE_USE_ID | The bill-to site use | NUMBER | |
| 10 | SHIP_TO_CUSTOMER_ID | The ship-to customer account | NUMBER | |
| 11 | SHIP_TO_SITE_USE_ID | The ship-to site use | NUMBER | |
| 12 | INVOICE_CURRENCY_CODE | Document currency | VARCHAR2 | |
| 13 | EXCHANGE_RATE | Currency conversion rate | NUMBER | |
| 14 | TERM_ID | Payment terms on the document | NUMBER | |
| 15 | TERM_DUE_DATE | Due date from the terms | DATE | |
| 16 | PURCHASE_ORDER | The customer's PO reference — free text | VARCHAR2 | |
| 17 | PREVIOUS_CUSTOMER_TRX_ID | For credit memos, the credited transaction | NUMBER | |
| 18 | INTERFACE_HEADER_CONTEXT | AutoInvoice source context — which feeder wrote the document; attribute semantics are source-defined | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading RA_CUSTOMER_TRX_ALL on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <CUSTOMER_TRX_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : RA_CUSTOMER_TRX_ALL — Receivables transaction headers — invoices, credit and debit memos, chargebacks, and deposits share the table, classified by transaction type; the revenue-document anchor of order-to-cash
-- Purpose: Column-selected read of RA_CUSTOMER_TRX_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + CUSTOMER_TRX_ID
-- 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_ID AS "Surrogate key of the transaction — the join key; the display number is not unique alone",
t.ORG_ID AS "Operating unit",
t.TRX_NUMBER AS "The document number users see — unique only per batch source",
t.TRX_DATE AS "The invoice date — the primary analysis date",
t.CUST_TRX_TYPE_ID AS "The transaction type — invoice vs credit memo vs debit memo classification (type table not cataloged)",
t.BATCH_SOURCE_ID AS "The batch source the document arrived through",
t.COMPLETE_FLAG AS "Y once the document is complete — filter incomplete documents out of revenue",
t.BILL_TO_CUSTOMER_ID AS "The bill-to customer ACCOUNT (TCA id)",
t.BILL_TO_SITE_USE_ID AS "The bill-to site use",
t.SHIP_TO_CUSTOMER_ID AS "The ship-to customer account",
t.SHIP_TO_SITE_USE_ID AS "The ship-to site use",
t.INVOICE_CURRENCY_CODE AS "Document currency",
t.EXCHANGE_RATE AS "Currency conversion rate",
t.TERM_ID AS "Payment terms on the document",
t.TERM_DUE_DATE AS "Due date from the terms",
t.PURCHASE_ORDER AS "The customer's PO reference — free text",
t.PREVIOUS_CUSTOMER_TRX_ID AS "For credit memos, the credited transaction",
t.INTERFACE_HEADER_CONTEXT AS "AutoInvoice source context — which feeder wrote the document; attribute semantics are source-defined"
FROM <catalog>.<schema>.RA_CUSTOMER_TRX_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.CUSTOMER_TRX_ID = <CUSTOMER_TRX_ID>
-- AND t.TRX_DATE >= DATE '<DATE_FROM>'
-- AND t.TRX_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.CUSTOMER_TRX_ID;Verified September 2026
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
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_IDON RA_CUSTOMER_TRX_ALL.BILL_TO_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_IDON RA_CUSTOMER_TRX_ALL.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID AND RA_CUSTOMER_TRX_ALL.ORG_ID = HZ_CUST_SITE_USES_ALL.ORG_IDON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID AND AR_PAYMENT_SCHEDULES_ALL.ORG_ID = RA_CUSTOMER_TRX_ALL.ORG_ID
More Financials tables
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — product lines, tax, and freight share the table by line type, with quantities, selling price, and the extended amount revenue analytics sum
- AP_INVOICE_DISTRIBUTIONS_ALLSupplier invoice distributions — one row per GL-account allocation of an invoice line; the spend-to-account grain payables accounting posts from
- AP_INVOICE_LINES_ALLSupplier invoice lines — the R12-new layer between header and distributions, carrying line type, amount, and the purchase-order and receipt matching references
- AP_INVOICES_ALLSupplier invoice headers — standard invoices, credit/debit memos, prepayments, and expense reports share the table by type, with amounts, payment status, and the liability account
- AR_CASH_RECEIPTS_ALLCash receipts — one row per customer or miscellaneous receipt with amount, date, status, and reversal detail; application detail against invoices lives in companion tables
- AR_PAYMENT_SCHEDULES_ALLThe open-receivables engine — one row per transaction installment AND one row per receipt, carrying original and remaining amounts, due date, and closure state; what aging, DSO, and collections analytics read