Skip to content
EBS Reference

AR_CASH_RECEIPTS_ALL

Schema: ARtransactionOU-striped (ORG_ID)

Cash receipts — one row per customer or miscellaneous receipt with amount, date, status, and reversal detail; application detail against invoices lives in companion tables

Module: FinancialsOperating-unit striped (ORG_ID)
Notes

Exclude TYPE = 'MISC' rows from customer-cash analytics. RECEIPT_NUMBER is not unique. The receipt-level STATUS lags the application detail, which lives in the receivable-applications table (not yet cataloged). PAY_FROM_CUSTOMER holds the customer account id, despite the name.

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.

Fields

14 fields · 1 key

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1CASH_RECEIPT_IDSurrogate key of the receiptNUMBER
Key
2ORG_IDOperating unitNUMBER
3RECEIPT_NUMBERThe receipt number users see — not uniqueVARCHAR2
4AMOUNTReceipt amountNUMBER
5RECEIPT_DATEWhen the receipt was taken — the primary analysis dateDATE
Filter date
6PAY_FROM_CUSTOMERThe paying customer ACCOUNT id — despite the nameNUMBER
7CUSTOMER_SITE_USE_IDThe customer site useNUMBER
8STATUSAPP, UNAPP, UNID, NSF, REV, or STOP (per the data dictionary's comment) — receipt-level state that lags application detailVARCHAR2
9TYPECASH or MISC — exclude MISC from customer-cash analyticsVARCHAR2
10CURRENCY_CODEReceipt currencyVARCHAR2
11EXCHANGE_RATECurrency conversion rateNUMBER
12RECEIPT_METHOD_IDThe receipt methodNUMBER
13REVERSAL_DATEWhen the receipt was reversed — NULL if neverDATE
14REVERSAL_CATEGORYWhy the receipt was reversedVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading AR_CASH_RECEIPTS_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  : AR_CASH_RECEIPTS_ALL — Cash receipts — one row per customer or miscellaneous receipt with amount, date, status, and reversal detail; application detail against invoices lives in companion tables
-- Purpose: Column-selected read of AR_CASH_RECEIPTS_ALL — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + CASH_RECEIPT_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.CASH_RECEIPT_ID AS "Surrogate key of the receipt",
  t.ORG_ID AS "Operating unit",
  t.RECEIPT_NUMBER AS "The receipt number users see — not unique",
  t.AMOUNT AS "Receipt amount",
  t.RECEIPT_DATE AS "When the receipt was taken — the primary analysis date",
  t.PAY_FROM_CUSTOMER AS "The paying customer ACCOUNT id — despite the name",
  t.CUSTOMER_SITE_USE_ID AS "The customer site use",
  t.STATUS AS "APP, UNAPP, UNID, NSF, REV, or STOP (per the data dictionary's comment) — receipt-level state that lags application detail",
  t.TYPE AS "CASH or MISC — exclude MISC from customer-cash analytics",
  t.CURRENCY_CODE AS "Receipt currency",
  t.EXCHANGE_RATE AS "Currency conversion rate",
  t.RECEIPT_METHOD_ID AS "The receipt method",
  t.REVERSAL_DATE AS "When the receipt was reversed — NULL if never",
  t.REVERSAL_CATEGORY AS "Why the receipt was reversed"
FROM <catalog>.<schema>.AR_CASH_RECEIPTS_ALL t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- AND t.CASH_RECEIPT_ID = <CASH_RECEIPT_ID>
  -- AND t.RECEIPT_DATE >= DATE '<DATE_FROM>'
  -- AND t.RECEIPT_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.CASH_RECEIPT_ID;

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

  • AR_PAYMENT_SCHEDULES_ALLAR_CASH_RECEIPTS_ALLforeign key · N:1
    ON AR_PAYMENT_SCHEDULES_ALL.CASH_RECEIPT_ID = AR_CASH_RECEIPTS_ALL.CASH_RECEIPT_ID AND AR_PAYMENT_SCHEDULES_ALL.ORG_ID = AR_CASH_RECEIPTS_ALL.ORG_ID
  • AR_CASH_RECEIPTS_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON AR_CASH_RECEIPTS_ALL.PAY_FROM_CUSTOMER = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_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.