Search Results check_unique_media_ref

Overview

The ARP_RW_BATCHES_CHECK_PKG package body in the APPS schema provides server-side validation and maintenance logic for Automatic Receipt batch processing within Oracle Receivables. Its principal responsibility is enforcing uniqueness and data-integrity constraints on the AR_BATCHES table before inserts or updates are committed. Batches represent groupings of automatic receipts created through batch sources, and the package ensures that attributes such as batch name, media reference, and GL date do not conflict with existing records. The package is classified as OTHER in the ETRM repository, indicating it is an internal supporting package rather than a formally published public API, although several of its procedures are callable from the Receivables forms and concurrent processing framework. The header comment identifies revision 120.9.12010000.2 and describes the primary workhorse, UPDATE_MANUAL_BATCH, as updating a row in AR_BATCHES after checking for uniqueness of items such as NAME, MEDIA_REFERENCE, and GL_DATE.

Key Procedures and Functions

• CHECK_UNIQUE_MEDIA_REF — The procedure most directly associated with the user's search term. It validates that a media reference (for example, a bank deposit or lockbox reference) supplied for a batch is unique, preventing duplicate media references across automatic receipt batches.
• CHECK_UNIQUE_BATCH_NAME — Verifies that a proposed batch name does not already exist, either globally or within the relevant batch source, guarding against ambiguous batch identification.
• UPDATE_MANUAL_BATCH — Updates an AR_BATCHES row after uniqueness checks on name, media reference, and GL date. Invoked when a user manually edits a batch through the Receivables interface.
• UPDATE_REMIT_BATCH — Performs the analogous update path for remittance-related batches, applying the same uniqueness discipline for the remittance workflow.
• UPDATE_AUTO_BATCH — Applies the update and uniqueness logic for automatically generated batches.
• UPDATE_BATCH_STATUS — Transitions the status of a batch, coordinating state changes with dependent receipt records.
• POST_BATCH_CONC_REQ — Submits or manages the concurrent request that posts a batch, linking this validation package to the concurrent manager infrastructure.
• GET_QUICK_AMOUNT_TOTALS — Returns aggregate amount totals used for quick-entry or summary display of batch contents.
• GET_REG_AMOUNT_TOTALS — Returns regular (non-quick) amount totals for a batch, supporting reconciliation and display.

Tables Accessed

The package reads and writes AR_BATCHES as its central table, and validates batch source identifiers against AR_BATCH_SOURCES. It references AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_INTERIM_CASH_RECEIPTS, and AR_INTERIM_CASH_RECEIPT_LINES to reconcile batch contents with the receipts they contain, and AR_RECEIVABLE_APPLICATIONS to account for applied amounts. AR_SYSTEM_PARAMETERS supplies Receivables system options that govern validation behavior. All access is performed through APPS synonyms.

Usage Notes

The package is invoked primarily from the Oracle Receivables batch entry forms during manual batch creation, modification, and status changes. Concurrent programs that post or remit automatic receipt batches call POST_BATCH_CONC_REQ. Because the uniqueness checks are exposed as separate procedures, custom code and other Receivables packages can call CHECK_UNIQUE_MEDIA_REF and CHECK_UNIQUE_BATCH_NAME directly before inserting into AR_BATCHES. ETRM records the package as referenced by nine other packages, confirming its role as a shared validation utility. Callers should note that the uniqueness assertions raise errors rather than returning Boolean status, so exception handling is required.