Search Results get_quick_amount_totals

Overview

ARP_RW_BATCHES_CHECK_PKG is an Oracle Receivables (AR) PL/SQL package owned by the APPS schema. It provides a centralized validation and maintenance layer for receivable batches, which are the grouping mechanism by which receipt, remittance, and miscellaneous receipt activity is collected before posting to the general ledger. The package is classified as OTHER under the ETRM API classification scheme, indicating that it is an internal utility rather than a public, supported application programming interface. In Oracle EBS 12.1.1 and 12.2.2, the package is a VALID, compiled object within the APPS schema. Its primary purpose is to enforce business rules on batch attributes — name uniqueness, media reference uniqueness, status transitions, and monetary totals — before and during batch processing. It is invoked at multiple points in the receipts workflow, including automatic receipt creation, remittance batch creation, manual batch maintenance, and the various receipt processing engines.

Key Procedures and Functions

The documented program units within the package are:

• UPDATE_MANUAL_BATCH — Performs the update logic for manually entered receipt batches, applying header-level changes to batch records.
• UPDATE_REMIT_BATCH — Maintains remittance batches created through the automatic remittance programs.
• UPDATE_AUTO_BATCH — Handles updates to batches created automatically by AutoReceipts and related automated receipt generation flows.
• UPDATE_BATCH_STATUS — Drives the batch status state machine, moving batches between states such as unposted, posted, and out-of-balance.
• CHECK_UNIQUE_BATCH_NAME — Validates that a proposed batch name does not already exist, preventing duplicate batch identifiers.
• CHECK_UNIQUE_MEDIA_REF — Validates that a media reference (for example, a remittance or lockbox reference) is unique within the applicable batch source context.
• POST_BATCH_CONC_REQ — Submits the concurrent request that posts batches, providing the programmatic entry point for batch posting from within the package layer.
• GET_QUICK_AMOUNT_TOTALS — Returns aggregated monetary totals for quick (single-currency, simple) receipt batches.
• GET_REG_AMOUNT_TOTALS — Returns aggregated monetary totals for regular (multi-line, multi-currency) receipt batches.

The tenth documented unit, referenced in the dependency metadata as ARP_RW_BATCHES_CHECK_PKG itself, reflects the package specification re-referencing the body.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• AR_BATCHES — the master batch table, central to every procedure in the package.
• AR_BATCH_SOURCES — provides batch source definitions and validation rules.
• AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY — used to confirm receipt activity and status history for batches under review.
• AR_INTERIM_CASH_RECEIPTS and AR_INTERIM_CASH_RECEIPT_LINES — access receipt data before it is fully posted into the receipts tables.
• AR_RECEIVABLE_APPLICATIONS — confirms application activity associated with batches.
• AR_SYSTEM_PARAMETERS — supplies system-level settings that govern batch processing behavior.

Usage Notes

ARP_RW_BATCHES_CHECK_PKG is an internal, unsupported utility and should not be called directly by custom code. It is referenced by nine other APPS packages in the receipts processing family, including ARP_BR_REMIT_BATCHES, ARP_PROCESS_APPLICATION, ARP_PROCESS_MISC_RECEIPTS, ARP_PROCESS_MISC_RECEIPTS2, ARP_PROCESS_RCTS, ARP_PROCESS_WRITEOFF, ARP_PROC_RECEIPTS2, ARP_RW_BATCHES_PKG, and ARP_RW_ICR_PKG. These packages are invoked by the Receivables forms and concurrent programs that manage batches, including AutoReceipts, Automatic Remittance, Receipt Posting, and Miscellaneous Receipts processing. Typical invocation points are batch creation, batch header update, batch posting validation, and concurrent request submission for posting. Because the package is proprietary and internal, any modifications or direct calls should be avoided; customers requiring batch validation logic should use supported Receipts APIs or user exits instead.