AR_PAYMENT_SCHEDULES_ALL
Schema: ARtransactionOU-striped (ORG_ID)The open-receivables engine — one row per transaction installment AND one row per receipt, carrying original and remaining amounts, due date, and closure state; what aging, DSO, and collections analytics read
Transactions AND receipts both write rows here, with opposite signs (debits positive, credits and receipts negative), and split terms produce several installments per transaction — filter CLASS before aging AR
CLASS separates the row kinds (invoice, credit memo, receipt…) per the data dictionary's own enumeration; STATUS moves OP to CL when the remaining amount reaches zero. Open AR is the STORED remaining amount — the deliberate contrast with the quantity side, where open is always arithmetic.
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
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PAYMENT_SCHEDULE_ID | Surrogate key of the schedule row | NUMBER | Key |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | CUSTOMER_TRX_ID | The transaction — populated on transaction rows, NULL on receipt rows | NUMBER | |
| 4 | CASH_RECEIPT_ID | The receipt — populated on receipt rows | NUMBER | |
| 5 | CUSTOMER_ID | The customer account | NUMBER | |
| 6 | CUSTOMER_SITE_USE_ID | The bill-to site use | NUMBER | |
| 7 | CLASS | Row kind — INV, DM, GUAR, CM, DEP, CB, PMT, BR (per the data dictionary's enumeration); PMT rows are receipts | VARCHAR2 | |
| 8 | STATUS | OP while open, CL once the remaining amount reaches zero | VARCHAR2 | |
| 9 | DUE_DATE | When the installment falls due — the aging date | DATE | Filter date |
| 10 | TRX_DATE | The transaction date, denormalized | DATE | |
| 11 | TRX_NUMBER | The document number, denormalized | VARCHAR2 | |
| 12 | AMOUNT_DUE_ORIGINAL | Original amount — debits positive, credits and receipts NEGATIVE (the sign convention) | NUMBER | |
| 13 | AMOUNT_DUE_REMAINING | The open amount — stored, not arithmetic; what aging sums | NUMBER | |
| 14 | AMOUNT_APPLIED | Amount applied to date | NUMBER | |
| 15 | TERMS_SEQUENCE_NUMBER | The installment number — split terms produce several rows per transaction | NUMBER | |
| 16 | INVOICE_CURRENCY_CODE | Currency of the amounts | VARCHAR2 | |
| 17 | GL_DATE | The accounting date | DATE | |
| 18 | ACTUAL_DATE_CLOSED | When the row actually closed | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading AR_PAYMENT_SCHEDULES_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_PAYMENT_SCHEDULES_ALL — The open-receivables engine — one row per transaction installment AND one row per receipt, carrying original and remaining amounts, due date, and closure state; what aging, DSO, and collections analytics read
-- Purpose: Column-selected read of AR_PAYMENT_SCHEDULES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + PAYMENT_SCHEDULE_ID
-- Caution: Transactions AND receipts both write rows here, with opposite signs (debits positive, credits and receipts negative), and split terms produce several installments per transaction — filter CLASS before aging AR
-- 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.PAYMENT_SCHEDULE_ID AS "Surrogate key of the schedule row",
t.ORG_ID AS "Operating unit",
t.CUSTOMER_TRX_ID AS "The transaction — populated on transaction rows, NULL on receipt rows",
t.CASH_RECEIPT_ID AS "The receipt — populated on receipt rows",
t.CUSTOMER_ID AS "The customer account",
t.CUSTOMER_SITE_USE_ID AS "The bill-to site use",
t.CLASS AS "Row kind — INV, DM, GUAR, CM, DEP, CB, PMT, BR (per the data dictionary's enumeration); PMT rows are receipts",
t.STATUS AS "OP while open, CL once the remaining amount reaches zero",
t.DUE_DATE AS "When the installment falls due — the aging date",
t.TRX_DATE AS "The transaction date, denormalized",
t.TRX_NUMBER AS "The document number, denormalized",
t.AMOUNT_DUE_ORIGINAL AS "Original amount — debits positive, credits and receipts NEGATIVE (the sign convention)",
t.AMOUNT_DUE_REMAINING AS "The open amount — stored, not arithmetic; what aging sums",
t.AMOUNT_APPLIED AS "Amount applied to date",
t.TERMS_SEQUENCE_NUMBER AS "The installment number — split terms produce several rows per transaction",
t.INVOICE_CURRENCY_CODE AS "Currency of the amounts",
t.GL_DATE AS "The accounting date",
t.ACTUAL_DATE_CLOSED AS "When the row actually closed"
FROM <catalog>.<schema>.AR_PAYMENT_SCHEDULES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.PAYMENT_SCHEDULE_ID = <PAYMENT_SCHEDULE_ID>
-- AND t.DUE_DATE >= DATE '<DATE_FROM>'
-- AND t.DUE_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.PAYMENT_SCHEDULE_ID;7 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <PAYMENT_SCHEDULE_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.CUSTOMER_TRX_ID = RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID AND AR_PAYMENT_SCHEDULES_ALL.ORG_ID = RA_CUSTOMER_TRX_ALL.ORG_IDON 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_PAYMENT_SCHEDULES_ALL.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID