AR_PAYMENT_SCHEDULES_ALL
Product: ARtransactionBU-striped (ORG_ID)The open-receivables ledger — one row per installment of every transaction and receipt, restated as amounts due, applied, and remaining; the table AR aging actually reads
Open items carry a 31-DEC-4712 sentinel in GL_DATE_CLOSED/ACTUAL_DATE_CLOSED, not NULL — the "still open" filter is the 4712 date
CLASS separates the row kinds (INV/DM/CM/CB/PMT/BR, page-enumerated but with no named lookup type — no ladder ships): transaction rows point at CUSTOMER_TRX_ID, receipt (PMT) rows at CASH_RECEIPT_ID. AMOUNT_DUE_ORIGINAL vs AMOUNT_DUE_REMAINING is the aging arithmetic; the ACCTD_ twin restates remaining in ledger currency. TRX_NUMBER and TRX_DATE are denormalized copies.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.PaymentScheduleExtractPVOOTBI: Receivables - Payment Schedules Real Time
Payment Schedule data store — keyed on ArPaymentSchedulePaymentScheduleId. No "Aging" subject area exists in the 26B book — aging reporting rides payment schedules.
Oracle data-store documentation (opens in new tab)
Fields
18 fields · 1 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | PAYMENT_SCHEDULE_ID | Surrogate key of the installment | NUMBER | Key |
| 2 | ORG_ID | The business unit owning the row | NUMBER | |
| 3 | CLASS | Row kind — INV, DM, CM, CB, PMT (receipts), or BR; page-enumerated but no named lookup type | VARCHAR2 | |
| 4 | STATUS | Open or closed | VARCHAR2 | |
| 5 | CUSTOMER_TRX_ID | The transaction, for non-receipt rows | NUMBER | |
| 6 | CASH_RECEIPT_ID | The receipt, for PMT rows | NUMBER | |
| 7 | CUSTOMER_ID | Customer account of the installment | NUMBER | |
| 8 | CUSTOMER_SITE_USE_ID | Bill-to site use of the installment | NUMBER | |
| 9 | TRX_NUMBER | Denormalized transaction number | VARCHAR2 | |
| 10 | TRX_DATE | Denormalized transaction date | DATE | |
| 11 | DUE_DATE | Installment due date — the aging bucket driver | DATE | Filter date |
| 12 | GL_DATE | Accounting date | DATE | |
| 13 | GL_DATE_CLOSED | Accounting close date — 31-DEC-4712 while the installment is open, not NULL | DATE | |
| 14 | AMOUNT_DUE_ORIGINAL | Original amount due | NUMBER | |
| 15 | AMOUNT_DUE_REMAINING | Open balance still due — the aging amount | NUMBER | |
| 16 | ACCTD_AMOUNT_DUE_REMAINING | Open balance restated in ledger currency | NUMBER | |
| 17 | AMOUNT_APPLIED | Amount applied against the installment | NUMBER | |
| 18 | INVOICE_CURRENCY_CODE | Transaction currency | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of AR_PAYMENT_SCHEDULES_ALL on 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.
7 parameters not filled: <catalog>, <schema>, <business_unit_id>, <PAYMENT_SCHEDULE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : AR_PAYMENT_SCHEDULES_ALL — The open-receivables ledger — one row per installment of every transaction and receipt, restated as amounts due, applied, and remaining; the table AR aging actually reads
-- Purpose: Column-selected read of AR_PAYMENT_SCHEDULES_ALL — auto-generated from field metadata
-- Grain : One row per business unit (ORG_ID) + PAYMENT_SCHEDULE_ID
-- Caution: Open items carry a 31-DEC-4712 sentinel in GL_DATE_CLOSED/ACTUAL_DATE_CLOSED, not NULL — the "still open" filter is the 4712 date
-- 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.PAYMENT_SCHEDULE_ID AS "Surrogate key of the installment",
t.ORG_ID AS "The business unit owning the row",
t.CLASS AS "Row kind — INV, DM, CM, CB, PMT (receipts), or BR; page-enumerated but no named lookup type",
t.STATUS AS "Open or closed",
t.CUSTOMER_TRX_ID AS "The transaction, for non-receipt rows",
t.CASH_RECEIPT_ID AS "The receipt, for PMT rows",
t.CUSTOMER_ID AS "Customer account of the installment",
t.CUSTOMER_SITE_USE_ID AS "Bill-to site use of the installment",
t.TRX_NUMBER AS "Denormalized transaction number",
t.TRX_DATE AS "Denormalized transaction date",
t.DUE_DATE AS "Installment due date — the aging bucket driver",
t.GL_DATE AS "Accounting date",
t.GL_DATE_CLOSED AS "Accounting close date — 31-DEC-4712 while the installment is open, not NULL",
t.AMOUNT_DUE_ORIGINAL AS "Original amount due",
t.AMOUNT_DUE_REMAINING AS "Open balance still due — the aging amount",
t.ACCTD_AMOUNT_DUE_REMAINING AS "Open balance restated in ledger currency",
t.AMOUNT_APPLIED AS "Amount applied against the installment",
t.INVOICE_CURRENCY_CODE AS "Transaction currency"
FROM <catalog>.<schema>.AR_PAYMENT_SCHEDULES_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.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>' -- the column incremental BICC extracts key on
ORDER BY t.PAYMENT_SCHEDULE_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. 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_IDON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID
More Financials tables
- GL_JE_HEADERSGeneral ledger journal headers — one row per journal within a batch, with the ledger, category, source, period, currency, posting status, and running debit/credit totals
- GL_JE_LINESGeneral ledger journal lines — the debit/credit grain: one row per line with the account combination, entered and accounted amounts, effective date, and the drill-back link to subledger accounting
- RA_CUSTOMER_TRX_ALLReceivables transaction headers — one row per invoice, credit memo, debit memo, or bill receivable, with the transaction number, type, dates, customer account and site-use pointers, and currency; business-unit striped
- RA_CUSTOMER_TRX_LINES_ALLReceivables transaction lines — mixed row kinds under each transaction: LINE rows carry the goods/services amounts, TAX and FREIGHT rows attach to their parent line, CB rows carry chargebacks
- AP_INVOICE_DISTRIBUTIONS_ALLPayables invoice distributions — the accounting grain under each line: one row per charged GL account with the amount, accounting date, period, and posted state; where AP spend meets the ledger
- AP_INVOICE_LINES_ALLPayables invoice lines — the goods/services, freight, tax, and prepayment rows under each invoice, carrying the amount, quantity, and the PO/receipt match pointers