Skip to content
Fusion Reference

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

Identity
Module: FinancialsBU-striped (ORG_ID)
Notes

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
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_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.

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1CUSTOMER_TRX_IDSurrogate key of the transactionNUMBER
Key
2ORG_IDThe business unit owning the transaction — Fusion's BU stripe, not the EBS operating unitNUMBER
3TRX_NUMBERTransaction number — repeats across BUs and sources; join on the idVARCHAR2
4TRX_DATETransaction dateDATE
Filter date
5TRX_CLASSClass of the document (invoice, credit memo, debit memo, bill receivable)VARCHAR2
6STATUS_TRXTransaction statusVARCHAR2
7COMPLETE_FLAGWhether the transaction is complete — filter it for finalized documentsVARCHAR2
8CUST_TRX_TYPE_SEQ_IDTransaction type — a Fusion _SEQ_ID column, not the EBS CUST_TRX_TYPE_ID; the type table is not catalogedNUMBER
9BILL_TO_CUSTOMER_IDBill-to customer accountNUMBER
10SHIP_TO_CUSTOMER_IDShip-to customer accountNUMBER
11BILL_TO_SITE_USE_IDBill-to site use — the TCA bottom layer the invoice addresses throughNUMBER
12SHIP_TO_SITE_USE_IDShip-to site useNUMBER
13TERM_IDPayment termsNUMBER
14INVOICE_CURRENCY_CODETransaction currencyVARCHAR2
15EXCHANGE_RATEConversion rate to the ledger currencyNUMBER
16PREVIOUS_CUSTOMER_TRX_IDFor a credit memo, the transaction it credits (self-referencing)NUMBER
17PURCHASE_ORDERThe customer's PO number as textVARCHAR2
18LEGAL_ENTITY_IDLegal entity of the transactionNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of RA_CUSTOMER_TRX_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

7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <CUSTOMER_TRX_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- 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;

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.

Loading relationship diagram…

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_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.BILL_TO_CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • RA_CUSTOMER_TRX_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.BILL_TO_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
  • RA_CUSTOMER_TRX_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON 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
  • RA_CUSTOMER_TRX_ALLFUN_ALL_BUSINESS_UNITS_Vforeign key · N:1
    ON RA_CUSTOMER_TRX_ALL.ORG_ID = FUN_ALL_BUSINESS_UNITS_V.BU_ID
  • AR_PAYMENT_SCHEDULES_ALLRA_CUSTOMER_TRX_ALLforeign key · N:1
    ON 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

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.