AR_CASH_RECEIPTS_ALL
Product: ARtransactionBU-striped (ORG_ID)Cash receipts — one row per receipt entered, with receipt number, date, amount, status, and the paying customer account; the cash side that payment schedules apply against
STATUS values are page-enumerated (APP/UNAPP/UNID/NSF/REV/STOP) but carry no named lookup type — shipped undecoded. The paying customer is PAY_FROM_CUSTOMER — an account id without the _ID suffix. TYPE splits CASH from MISC receipts (the dictionary itself says filter on MISC, not CASH). There is NO GL_DATE here — receipt accounting dates live in the receipt-history table (not cataloged).
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.ReceiptHeaderExtractPVOOTBI: Receivables - Receipts Details Real Time
Receipt Header data store — keyed on ArCashReceiptCashReceiptId.
Oracle data-store documentation →
Fields
15 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | CASH_RECEIPT_ID | Surrogate key of the receipt | NUMBER | Key |
| 2 | ORG_ID | The business unit owning the receipt | NUMBER | |
| 3 | RECEIPT_NUMBER | Receipt number | VARCHAR2 | |
| 4 | RECEIPT_DATE | Receipt date | DATE | Filter date |
| 5 | AMOUNT | Receipt amount — denormalized here for query convenience | NUMBER | |
| 6 | CURRENCY_CODE | Receipt currency | VARCHAR2 | |
| 7 | STATUS | APP, UNAPP, UNID, NSF, REV, or STOP — page-enumerated, no named lookup type | VARCHAR2 | |
| 8 | TYPE | CASH or MISC — the dictionary itself says filter on MISC, not CASH | VARCHAR2 | |
| 9 | PAY_FROM_CUSTOMER | The paying customer account — an id column without the _ID suffix | NUMBER | |
| 10 | CUSTOMER_SITE_USE_ID | The customer site use the receipt is tied to | NUMBER | |
| 11 | RECEIPT_METHOD_ID | Receipt method | NUMBER | |
| 12 | EXCHANGE_RATE | Conversion rate to the ledger currency | NUMBER | |
| 13 | REVERSAL_DATE | When the receipt was reversed | DATE | |
| 14 | REVERSAL_CATEGORY | System category of the reversal | VARCHAR2 | |
| 15 | LEGAL_ENTITY_ID | Legal entity receiving the receipt | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of AR_CASH_RECEIPTS_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 : AR_CASH_RECEIPTS_ALL — Cash receipts — one row per receipt entered, with receipt number, date, amount, status, and the paying customer account; the cash side that payment schedules apply against
-- Purpose: Column-selected read of AR_CASH_RECEIPTS_ALL — auto-generated from field metadata
-- Grain : One row per business unit (ORG_ID) + CASH_RECEIPT_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.CASH_RECEIPT_ID AS "Surrogate key of the receipt",
t.ORG_ID AS "The business unit owning the receipt",
t.RECEIPT_NUMBER AS "Receipt number",
t.RECEIPT_DATE AS "Receipt date",
t.AMOUNT AS "Receipt amount — denormalized here for query convenience",
t.CURRENCY_CODE AS "Receipt currency",
t.STATUS AS "APP, UNAPP, UNID, NSF, REV, or STOP — page-enumerated, no named lookup type",
t.TYPE AS "CASH or MISC — the dictionary itself says filter on MISC, not CASH",
t.PAY_FROM_CUSTOMER AS "The paying customer account — an id column without the _ID suffix",
t.CUSTOMER_SITE_USE_ID AS "The customer site use the receipt is tied to",
t.RECEIPT_METHOD_ID AS "Receipt method",
t.EXCHANGE_RATE AS "Conversion rate to the ledger currency",
t.REVERSAL_DATE AS "When the receipt was reversed",
t.REVERSAL_CATEGORY AS "System category of the reversal",
t.LEGAL_ENTITY_ID AS "Legal entity receiving the receipt"
FROM <catalog>.<schema>.AR_CASH_RECEIPTS_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.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>' -- the column incremental BICC extracts key on
ORDER BY t.CASH_RECEIPT_ID;7 parameters not filled: <catalog>, <schema>, <business_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_IDON AR_CASH_RECEIPTS_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID