RA_CUSTOMER_TRX_ALL
Product: RAtransactionBU-striped (ORG_ID)Receivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
The EBS name and shape survive; ORG_ID is documented as the business unit. Fusion-isms: the type and batch-source FKs are *_SEQ_ID columns (CUST_TRX_TYPE_SEQ_ID — not the EBS CUST_TRX_TYPE_ID), and the salesrep column points at the resource model, not RA salesreps. A credit memo points at the transaction it credits through PREVIOUS_CUSTOMER_TRX_ID. Filter COMPLETE_FLAG for finalized transactions.
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_ALL is the header for its lines in RA_CUSTOMER_TRX_LINES_ALL.
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.TransactionHeaderExtractPVOOTBI: Receivables - Transactions Real Time
Transaction Header data store — keyed on RaCustomerTrxCustomerTrxId, mirroring CUSTOMER_TRX_ID.
Oracle data-store documentation →
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CUSTOMER_TRX_ID | Surrogate key of the transaction | NUMBER | Key |
| 2 | ORG_ID | The business unit owning the transaction — Fusion's BU stripe, not the EBS operating unit | NUMBER | |
| 3 | TRX_NUMBER | Transaction number — repeats across BUs and sources; join on the id | VARCHAR2 | |
| 4 | TRX_DATE | Transaction date | DATE | Filter date |
| 5 | TRX_CLASS | Class of the document (invoice, credit memo, debit memo, bill receivable) | VARCHAR2 | |
| 6 | STATUS_TRX | Transaction status | VARCHAR2 | |
| 7 | COMPLETE_FLAG | Whether the transaction is complete — filter it for finalized documents | VARCHAR2 | |
| 8 | CUST_TRX_TYPE_SEQ_ID | Transaction type — a Fusion _SEQ_ID column, not the EBS CUST_TRX_TYPE_ID; the type table is not cataloged | NUMBER | |
| 9 | BILL_TO_CUSTOMER_ID | Bill-to customer account | NUMBER | |
| 10 | SHIP_TO_CUSTOMER_ID | Ship-to customer account | NUMBER | |
| 11 | BILL_TO_SITE_USE_ID | Bill-to site use — the TCA bottom layer the invoice addresses through | NUMBER | |
| 12 | SHIP_TO_SITE_USE_ID | Ship-to site use | NUMBER | |
| 13 | TERM_ID | Payment terms | NUMBER | |
| 14 | INVOICE_CURRENCY_CODE | Transaction currency | VARCHAR2 | |
| 15 | EXCHANGE_RATE | Conversion rate to the ledger currency | NUMBER | |
| 16 | PREVIOUS_CUSTOMER_TRX_ID | For a credit memo, the transaction it credits (self-referencing) | NUMBER | |
| 17 | PURCHASE_ORDER | The customer's PO number as text | VARCHAR2 | |
| 18 | LEGAL_ENTITY_ID | Legal entity of the transaction | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of RA_CUSTOMER_TRX_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_ALL — Receivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
-- Purpose: Column-selected read of RA_CUSTOMER_TRX_ALL — auto-generated from field metadata
-- Grain : One row per business unit (ORG_ID) + CUSTOMER_TRX_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_ID AS "Surrogate key of the transaction",
t.ORG_ID AS "The business unit owning the transaction — Fusion's BU stripe, not the EBS operating unit",
t.TRX_NUMBER AS "Transaction number — repeats across BUs and sources; join on the id",
t.TRX_DATE AS "Transaction date",
t.TRX_CLASS AS "Class of the document (invoice, credit memo, debit memo, bill receivable)",
t.STATUS_TRX AS "Transaction status",
t.COMPLETE_FLAG AS "Whether the transaction is complete — filter it for finalized documents",
t.CUST_TRX_TYPE_SEQ_ID AS "Transaction type — a Fusion _SEQ_ID column, not the EBS CUST_TRX_TYPE_ID; the type table is not cataloged",
t.BILL_TO_CUSTOMER_ID AS "Bill-to customer account",
t.SHIP_TO_CUSTOMER_ID AS "Ship-to customer account",
t.BILL_TO_SITE_USE_ID AS "Bill-to site use — the TCA bottom layer the invoice addresses through",
t.SHIP_TO_SITE_USE_ID AS "Ship-to site use",
t.TERM_ID AS "Payment terms",
t.INVOICE_CURRENCY_CODE AS "Transaction currency",
t.EXCHANGE_RATE AS "Conversion rate to the ledger currency",
t.PREVIOUS_CUSTOMER_TRX_ID AS "For a credit memo, the transaction it credits (self-referencing)",
t.PURCHASE_ORDER AS "The customer's PO number as text",
t.LEGAL_ENTITY_ID AS "Legal entity of the transaction"
FROM <catalog>.<schema>.RA_CUSTOMER_TRX_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_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>' -- the column incremental BICC extracts key on
ORDER BY t.CUSTOMER_TRX_ID;7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <CUSTOMER_TRX_ID>, <DATE_FROM>, <DATE_TO>, <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_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_IDON RA_CUSTOMER_TRX_ALL.SHIP_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID- RA_CUSTOMER_TRX_ALLRA_CUSTOMER_TRX_ALLforeign key · N:1
ON RA_CUSTOMER_TRX_ALL1.PREVIOUS_CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL2.CUSTOMER_TRX_ID AND RA_CUSTOMER_TRX_ALL1.ORG_ID = RA_CUSTOMER_TRX_ALL2.ORG_ID ON RA_CUSTOMER_TRX_ALL.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_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