Search Results current_record




Overview
Explore in AI Chat

Overview

AR_PAYMENT_SCHEDULES_PMT_V is a Receivables (AR) view owned by the APPS schema in Oracle E-Business Suite. The ETRM metadata describes it as "Release 115 Only," indicating that it originated as a compatibility construct in an early 11i release and has been retained, in VALID status, through EBS 12.1.1 and 12.2.2. Its central purpose is to expose payment schedule records enriched with the related party, customer account, site use, receipt, receipt method, batch, and currency context needed for collection and payment-oriented reporting. The view is a reporting and integration surface: it flattens joins across the AR transaction, customer, and receipt model into one denormalized result set, which makes it convenient for concurrent programs, custom reports, and inbound/outbound interfaces that need both schedule-level amounts and descriptive party attributes in a single query.

Underlying Base Objects

The documented base objects span several schemas and object types. The core driver is the synonym AR_PAYMENT_SCHEDULES, aliased PS in the view text, which supplies the schedule identity columns and the original/remaining amount columns. Transaction and batch context come from AR_BATCHES_ALL, AR_BATCH_SOURCES_ALL, AR_CONS_INV_ALL, and the AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY_ALL synonyms, with the latter providing the current receipt status (CRH_CURRENT). Supporting lookups are resolved from AR_LOOKUPS (via AL_RISK_RECEIPT) and through the APPS package ARPT_SQL_FUNC_UTIL, whose GET_LOOKUP_MEANING function converts stored codes into descriptive meanings for CLASS and RECEIPT_CREATION_STATUS. Customer and party data arrive through HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, and the AR_VIEW_CONSTANTS package. Receipt method and currency details are drawn from AR_RECEIPT_METHODS and FND_CURRENCIES (aliased CR and FC). The view therefore sits at the intersection of the AR transaction tables and the Trading Community Architecture (HZ) party model.

Key Columns

Common Use Cases and Queries

The view is typically queried for open receivables aging, collection worklists, and payment schedule reconciliation. A representative query for outstanding balances by customer is:

SELECT payment_schedule_id, trx_number, due_date, status,
       amount_due_original, amount_due_remaining,
       account_number, party_name, class
FROM   apps.ar_payment_schedules_pmt_v
WHERE  amount_due_remaining <> 0
ORDER  BY due_date;

Collection analysts join it to receipt history through CASH_RECEIPT_ID to reconcile applied receipts, while integration programs extract it to feed downstream cash-application systems using TRX_NUMBER and GL_DATE as natural keys. Because the view applies function calls and decode logic at runtime, queries should be filtered as tightly as possible on CUSTOMER_ID, TRX_DATE, or STATUS to limit the volume of rows processed.