Skip to content
EBS Reference

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

Module: FinancialsOperating-unit striped (ORG_ID)
Notes

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
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_ALL is the header for its lines in RA_CUSTOMER_TRX_LINES_ALL.

Fields

18 fields · 1 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1CUSTOMER_TRX_IDSurrogate key of the transaction — the join key; the display number is not unique aloneNUMBER
Key
2ORG_IDOperating unitNUMBER
3TRX_NUMBERThe document number users see — unique only per batch sourceVARCHAR2
4TRX_DATEThe invoice date — the primary analysis dateDATE
Filter date
5CUST_TRX_TYPE_IDThe transaction type — invoice vs credit memo vs debit memo classification (type table not cataloged)NUMBER
6BATCH_SOURCE_IDThe batch source the document arrived throughNUMBER
7COMPLETE_FLAGY once the document is complete — filter incomplete documents out of revenueVARCHAR2
8BILL_TO_CUSTOMER_IDThe bill-to customer ACCOUNT (TCA id)NUMBER
9BILL_TO_SITE_USE_IDThe bill-to site useNUMBER
10SHIP_TO_CUSTOMER_IDThe ship-to customer accountNUMBER
11SHIP_TO_SITE_USE_IDThe ship-to site useNUMBER
12INVOICE_CURRENCY_CODEDocument currencyVARCHAR2
13EXCHANGE_RATECurrency conversion rateNUMBER
14TERM_IDPayment terms on the documentNUMBER
15TERM_DUE_DATEDue date from the termsDATE
16PURCHASE_ORDERThe customer's PO reference — free textVARCHAR2
17PREVIOUS_CUSTOMER_TRX_IDFor credit memos, the credited transactionNUMBER
18INTERFACE_HEADER_CONTEXTAutoInvoice source context — which feeder wrote the document; attribute semantics are source-definedVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading RA_CUSTOMER_TRX_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_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;

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

  • 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 AND RA_CUSTOMER_TRX_ALL.ORG_ID = HZ_CUST_SITE_USES_ALL.ORG_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 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.