Search Results validate_amount

Overview

AR_RECEIPT_VAL_PVT is a private validation package body in the Oracle E-Business Suite Receivables (AR) module. Its header comment, "$Header: ARXPREVB.pls," identifies it as the compiled implementation of the receipt validation logic used throughout the Automatic Receipts and manual receipt entry flows. The package contains only validation procedures; it does not perform inserts, updates, or deletions. Each procedure accepts input values, evaluates them against business rules, and returns a status code via a p_return_status OUT parameter, conforming to the standard Oracle Application Object Library API conventions (FND_API.G_RET_STS_SUCCESS, FND_API.G_RET_STS_ERROR). Errors are signaled by registering messages through FND_MESSAGE and FND_MSG_PUB rather than by raising exceptions, allowing callers to accumulate multiple validation failures in a single pass. Debug tracing is conditional on the AFLOG_ENABLED profile option. The private ("PVT") classification means the package is intended for internal consumption by other Receivables packages rather than by external integrators.

Key Procedures and Functions

The ETRM metadata documents seventeen procedures covering the major receipt validation scenarios:

• VALIDATE_CASH_RECEIPT — overarching validation of a cash receipt record.
• VALIDATE_APPLICATION_INFO — validates application details for a receipt.
• VALIDATE_UNAPP_INFO — validates unapplied receipt information.
• VALIDATE_REVERSE_INFO — validates reversal criteria.
• CHECK_STD_REVERSIBLE — determines whether a standard reversal is permitted.
• VALIDATE_ON_AC_APP — validates on-account application entries.
• VALIDATE_UNAPP_ON_AC_ACT_INFO — validates unapplied/on-account activity data.
• VALIDATE_ACTIVITY_APP — validates activity applications.
• VALIDATE_APPLICATION_REF — validates application reference values.
• VALIDATE_MISC_RECEIPT — validates miscellaneous receipt data.
• VALIDATE_PREPAY_AMOUNT — validates prepayment amounts.
• VALIDATE_PAYMENT_TYPE — validates the payment type attribute.
• VALIDATE_CLAIM_UNAPPLY — validates claim unapply requests.
• VALIDATE_OPEN_RECEIPT_INFO — validates open receipt details.
• VALIDATE_UNAPP_OPEN_RECEIPT — validates unapplied open receipt records.
• VALIDATE_LLCA_INSERT_AD — validates adjusted detail rows for the LLCA (Lockbox/Low-Value) insert flow.
• VALIDATE_LLCA_INSERT_APP — validates application rows for the LLCA insert flow.

The excerpt additionally shows auxiliary routines Validate_Receipt_Date, Validate_Gl_Date, and Validate_Deposit_Date, which enforce GL date validity via arp_util.is_gl_date_valid.

Tables Accessed

The package reads configuration and transactional data through APPS synonyms. AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY supply receipt header and lifecycle context. AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, and AR_RECEIPT_METHOD_ACCOUNTS provide receipt classification, payment method, and account derivation rules. CE_BANK_ACCOUNTS and HZ_CUST_SITE_USES validate bank and customer site information. AP_CHECKS and AP_INVOICE_SELECTION_CRITERIA support supplier-related receipt validation. AR_ACTIVITY_DETAILS, AR_ADJUSTMENTS, AR_PAYMENT_SCHEDULES, and AR_BATCHES support application and adjustment checks. AR_APPROVAL_USER_LIMITS enforces approval authority rules, and AR_LLCA_TRX_LINES_GT is the global temporary table used by the LLCA insert validation routines.

Usage Notes

AR_RECEIPT_VAL_PVT is invoked by higher-level Receivables APIs and forms before committing receipt data — typically from receipt entry forms, the Automatic Receipts concurrent programs, and Lockbox processing. ETRM indicates it is referenced by three other packages, confirming its role as a shared internal service. Because the package is classified PVT and is not a public API, customizations should call the supported public Receivables APIs (for example AR_RECEIPT_API_PUB) rather than this package directly. When invoked, callers must inspect p_return_status and the FND message stack, since the procedures do not raise exceptions on validation failure. All logic is subject to the standard Receivables date and currency validation rules in effect for the 12.1.1 and 12.2.2 releases.