Search Results ar_payment_schedules_v




Overview
Explore in AI Chat

Overview

AR_PAYMENT_SCHEDULES_V is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes one row per payment schedule line — the installments generated for transactions and receipts — joining the AR_PAYMENT_SCHEDULES base table to customer, site, transaction-type, collector, and batch descriptive data. Because it flattens these lookups into a single query block, the view is the standard reporting and integration entry point for receivables balances, aging, collections, and cash application inquiries in both release 12.1.1 and 12.2.2.

The view is not a maintenance object. Inserts, updates, and deletes against transactions remain the responsibility of the Receivables forms and AutoInvoice; AR_PAYMENT_SCHEDULES_V is consumed read-only by reports, Discoverer workbooks, OBIEE extracts, and custom interfaces.

Underlying Base Objects

The documented ETRM 12.2.2 metadata lists the following referenced objects: ARPT_SQL_FUNC_UTIL (package), ARP_VIEW_CONSTANTS (package), AR_BATCHES_ALL, AR_BATCH_SOURCES_ALL, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_CONS_INV_ALL, AR_LOOKUPS, AR_PAYMENT_SCHEDULES, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, FND_CURRENCIES, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, RA_BATCH_SOURCES_ALL, RA_CUSTOMER_TRX_ALL, and RA_CUST_TRX_TYPES_ALL — most accessed via APPS synonyms.

The primary driver is AR_PAYMENT_SCHEDULES (aliased PS in the view text). Descriptive enrichment comes from HZ_PARTIES (PARTY_NAME), HZ_CUST_ACCOUNTS (ACCOUNT_NUMBER), HZ_CUST_SITE_USES_ALL (SU.LOCATION), RA_CUSTOMER_TRX_ALL and RA_CUST_TRX_TYPES_ALL (CTT.NAME, DOC_SEQUENCE_VALUE, PURCHASE_ORDER), plus AR_LOOKUPS for translated meanings. The ARPT_SQL_FUNC_UTIL package supplies lookup translation through GET_LOOKUP_MEANING and supplies the CLASS and STATUS decode logic.

Key Columns

Common Use Cases and Queries

Typical scenarios include open receivables aging, collections worklists, cash application reconciliation, and feeding a custom extract or data warehouse. SAMPLE:

  • Open invoice listing: SELECT trx_number, customer_id, due_date, amount_due_remaining FROM ar_payment_schedules_v WHERE class = 'INV' AND status = 'OP' AND amount_due_remaining > 0;
  • Aging buckets: group by due_date relative to SYSDATE, using amount_due_remaining summed by customer_id or account_number.
  • Receipt linkage: join CASH_RECEIPT_ID to AR_CASH_RECEIPTS_ALL to trace applied receipts.
  • Collections: filter on COLLECTOR_LAST and FOLLOW_UP_CODE_LAST to build follow-up queues.

Because the view resolves lookup meanings via ARPT_SQL_FUNC_UTIL per row, heavy reports should filter aggressively on CLASS, STATUS, and TRX_DATE to avoid full scans of AR_PAYMENT_SCHEDULES.