Search Results payment_schedules

Overview

ARI_DEF_HOOKS_PVT is a private PL/SQL package owned by APPS in the Oracle E-Business Suite Receivables/Advanced Collections (iReceivables) schema. Its documented purpose is to supply the default (seeded) implementations of certain validation "hooks" used by the iReceivables self-service dispute, payment, and print flows. Internally the package declares the module with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling schema rather than as definer-rights code, and it is explicitly annotated in the source header as a package that "should not be modified by customer." This makes it the sealed, Oracle-delivered counterpart to the customer-extensible hook implementations that iReceivables can substitute at runtime.

The unifying thread across the package—and the reason it surfaces in searches for payment_schedules—is that each hook validates a PAYMENT_SCHEDULE_ID belonging to a receivables transaction. The package provides the baseline algorithm by which a payment schedule on a transaction is deemed eligible for a given downstream action (disputing, paying, or printing).

Key Procedures and Functions

• VALIDATE_DISPUTE — Implements the default algorithm for validating a PAYMENT_SCHEDULE_ID for dispute purposes. Per the documented pseudo code, all payment schedules are validated to the status 'S' (success). It accepts the customer account, site use, session, and payment schedule identifiers, and returns a return status plus a message buffer via its OUT parameters.
• VALIDATE_PAYMENT — Implements the default algorithm for validating a PAYMENT_SCHEDULE_ID for payment. Like VALIDATE_DISPUTE it is a seeded default that customers must not modify, and it follows the same return-status/message-buffer convention.
• VALIDATE_PRINT — The third documented procedure; it applies the corresponding default validation logic for the print path, again keyed on the payment schedule identifier.

All three procedures share the same parameter signature documented for VALIDATE_DISPUTE (customer account, site use, session, payment schedule, and the two OUT parameters); no departure from that signature is asserted here beyond what the metadata records.

Tables Accessed

The ETRM metadata lists no directly referenced base tables for this package via APPS synonyms, and no other packages are documented as referencing it (referenced by 0). The session parameter is described as originating from AR_IREC_USER_ACCT_SITES_ALL, which is consistent with the calling context rather than a table this package itself queries. Because the default implementations simply return success (validating all schedules to 'S'), the procedures are largely algorithmic and do not require independent data access; downstream processing of the payment schedule itself is performed by the calling iReceivables code.

Usage Notes

ARI_DEF_HOOKS_PVT is internal plumbing invoked by the iReceivables Accounts Receivable self-service application when a customer views transaction payment schedules and attempts to dispute, pay, or print them. It is not a public API and should not be called or modified by customer code. The "DEF" in its name denotes that it holds the default hook implementations; Oracle's extensibility model allows an alternate customer-authored hook package to be registered so that the default logic here is bypassed without editing this package. In Oracle EBS 12.1.1 and 12.2.2 the package remains classified as PVT (private) and, per the ETRM record, is not depended upon by any other packaged code, confirming its role as a leaf-level, Oracle-maintained default provider rather than a reusable API surface.