Search Results arfv_ar_payment_schedules




Overview
Explore in AI Chat

Overview

ARFV_AR_PAYMENT_SCHEDULES is an APPS-owned database view in the Oracle Receivables (AR) module, valid in both EBS 12.1.1 and 12.2.2. It exposes information about entries posted against accounts receivable transactions, covering both debit and credit activity. Per the ETRM documentation, the view deliberately excludes adjustments and miscellaneous cash, so it represents the transactional payment schedule layer rather than the full receivables accounting picture. The view is a read-only, denormalized projection of AR_PAYMENT_SCHEDULES joined to several descriptive tables, and it is intended primarily for reporting, ad hoc querying, and integration extracts. Because it carries WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY), it can be used for incremental extraction and audit-style reporting. Its naming prefix (ARFV) follows the Oracle convention for a Receivables view with descriptive flexfield and lookup translation handling built into the SQL.

Underlying Base Objects

The view is defined over the following documented base objects: AR_PAYMENT_SCHEDULES (the primary table, aliased PS), joined to AR_CONS_INV, AR_COLLECTORS, FND_CURRENCIES_VL, RA_CUSTOMER_TRX, AR_CASH_RECEIPTS, HZ_PARTIES, HZ_CUST_ACCOUNTS, HR_ALL_ORGANIZATION_UNITS, and RA_TERMS. AR_PAYMENT_SCHEDULES supplies the core payment schedule rows and most of the displayed columns; it is the central transactional table. RA_CUSTOMER_TRX provides the transaction number, AR_CASH_RECEIPTS provides the receipt number for receipt-linked schedules, and AR_CONS_INV supplies the consolidated billing number. AR_COLLECTORS resolves collector names, RA_TERMS resolves payment term names, and FND_CURRENCIES_VL supplies currency descriptions. HZ_PARTIES and HZ_CUST_ACCOUNTS resolve the customer and party identity, while HR_ALL_ORGANIZATION_UNITS resolves the operating unit name. The SQL embeds lookup translation expressions (for CLASS, STATUS, IN_COLLECTION, FOLLOW_UP_CODE_LAST, and EXCLUDE_FROM_DUNNING_FLAG) against AR_LOOKUPS, and a descriptive flexfield reference for the payment schedule context, so values appear as user-facing meanings rather than codes.

Key Columns

Common Use Cases and Queries

Typical uses include open receivables aging, collections workload analysis, dispute and dunning reporting, and integration extracts feeding data warehouses. A representative aging query:

SELECT PS.TRX_NUMBER, PS.DUE_DATE, PS.AMOUNT_DUE_REMAINING, PS.INVOICE_CURRENCY_CODE
FROM APPS.ARFV_AR_PAYMENT_SCHEDULES PS
WHERE PS.ORG_ID = :p_org_id
AND PS.AMOUNT_DUE_REMAINING > 0
AND PS.DUE_DATE < SYSDATE;

A collector workload query groups by collector name and open balance, while a dispute report filters on DISPUTE_DATE and AMOUNT_IN_DISPUTE. Because lookups are already translated, status and class columns can be filtered or displayed directly without a secondary join to AR_LOOKUPS.