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
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.
Fields
14 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CASH_RECEIPT_ID | Surrogate key of the receipt | NUMBER | Key |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | RECEIPT_NUMBER | The receipt number users see — not unique | VARCHAR2 | |
| 4 | AMOUNT | Receipt amount | NUMBER | |
| 5 | RECEIPT_DATE | When the receipt was taken — the primary analysis date | DATE | Filter date |
| 6 | PAY_FROM_CUSTOMER | The paying customer ACCOUNT id — despite the name | NUMBER | |
| 7 | CUSTOMER_SITE_USE_ID | The customer site use | NUMBER | |
| 8 | STATUS | APP, UNAPP, UNID, NSF, REV, or STOP (per the data dictionary's comment) — receipt-level state that lags application detail | VARCHAR2 | |
| 9 | TYPE | CASH or MISC — exclude MISC from customer-cash analytics | VARCHAR2 | |
| 10 | CURRENCY_CODE | Receipt currency | VARCHAR2 | |
| 11 | EXCHANGE_RATE | Currency conversion rate | NUMBER | |
| 12 | RECEIPT_METHOD_ID | The receipt method | NUMBER | |
| 13 | REVERSAL_DATE | When the receipt was reversed — NULL if never | DATE | |
| 14 | REVERSAL_CATEGORY | Why the receipt was reversed | VARCHAR2 |
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.
-- ============================================================
-- 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
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_IDON AR_CASH_RECEIPTS_ALL.PAY_FROM_CUSTOMER = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID