Skip to content
Fusion Reference

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

Identity
Module: FinancialsBU-striped (ORG_ID)
Grain note

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

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.PaymentScheduleExtractPVO
    OTBI: 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.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1PAYMENT_SCHEDULE_IDSurrogate key of the installmentNUMBER
Key
2ORG_IDThe business unit owning the rowNUMBER
3CLASSRow kind — INV, DM, CM, CB, PMT (receipts), or BR; page-enumerated but no named lookup typeVARCHAR2
4STATUSOpen or closedVARCHAR2
5CUSTOMER_TRX_IDThe transaction, for non-receipt rowsNUMBER
6CASH_RECEIPT_IDThe receipt, for PMT rowsNUMBER
7CUSTOMER_IDCustomer account of the installmentNUMBER
8CUSTOMER_SITE_USE_IDBill-to site use of the installmentNUMBER
9TRX_NUMBERDenormalized transaction numberVARCHAR2
10TRX_DATEDenormalized transaction dateDATE
11DUE_DATEInstallment due date — the aging bucket driverDATE
Filter date
12GL_DATEAccounting dateDATE
13GL_DATE_CLOSEDAccounting close date — 31-DEC-4712 while the installment is open, not NULLDATE
14AMOUNT_DUE_ORIGINALOriginal amount dueNUMBER
15AMOUNT_DUE_REMAININGOpen balance still due — the aging amountNUMBER
16ACCTD_AMOUNT_DUE_REMAININGOpen balance restated in ledger currencyNUMBER
17AMOUNT_APPLIEDAmount applied against the installmentNUMBER
18INVOICE_CURRENCY_CODETransaction currencyVARCHAR2

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.

Query parameters

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

  • AR_PAYMENT_SCHEDULES_ALLRA_CUSTOMER_TRX_ALLforeign key · N:1
    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_ID
  • 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_PAYMENT_SCHEDULES_ALLHZ_CUST_ACCOUNTSforeign key · N:1
    ON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID
  • AR_PAYMENT_SCHEDULES_ALLHZ_CUST_SITE_USES_ALLforeign key · N:1
    ON AR_PAYMENT_SCHEDULES_ALL.CUSTOMER_SITE_USE_ID = HZ_CUST_SITE_USES_ALL.SITE_USE_ID

Browse more Financials tables

More Financials tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.