Search Results update_receipt_related_columns




Overview

ARP_PS_UTIL is a utility package in the APPS schema of Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) module and operates on the payment schedule layer of the AR data model. Payment schedules are the installment records that link a transaction to its due dates, amounts, and open balances; they are central to collections, aging, credit exposure, and cash application.

The package consolidates maintenance logic that is shared by many Receivables programs. Its primary responsibility is to synchronize denormalized columns on payment schedule rows and on related transaction, adjustment, and receivable application rows whenever those source records change. By centralizing this logic, Receivables ensures that concurrent processes such as receipt application, adjustment creation, chargeback processing, and receipt reversal all update payment schedules consistently. The package is classified as a utility, meaning it is not a public API and is not intended to be called directly by external integrations.

Key Procedures and Functions

The documented interface exposes nine procedures and functions. The update-oriented routines perform targeted refreshes of payment schedule and related entity columns:

The metadata lists nine documented routines in total; these seven are explicitly named. The remaining entries should be treated as internal helpers invoked by the routines above.

Tables Accessed

The package reads and writes the core Receivables payment schedule and application tables through APPS synonyms:

Usage Notes

ARP_PS_UTIL is invoked from Receivables processing packages, not from Oracle Forms or standard concurrent programs. ETRM lists nine dependent packages that call into it, including ARP_PROCESS_APPLICATION, ARP_PROCESS_ADJUSTMENT, ARP_PROCESS_CHARGEBACK, ARP_PROC_RECEIPTS1, ARP_REVERSE_RECEIPT, ARP_CONFIRMATION, ARP_ETAX_UTIL, ARP_PROCESS_DET_PKG, and AR_BILLS_MAINTAIN_PUB. These are the receipt application, adjustment, and chargeback engines that modify open balances.

Because the package recursively references itself, some routines are called from within others to keep logic layered. Custom code should not call these procedures directly; extending or bypassing them risks invalidating payment schedule balances and breaking aging, collections, and reconciliation reports. Use supported Receivables APIs instead.