Search Results update_batch

Overview

ARP_PROCESS_BR_BATCHES is an Oracle Receivables package body owned by APPS that provides the core processing logic for Bills Receivable batches. Bills Receivable are negotiable instruments (drafts) drawn on customers, and their lifecycle is managed in batches that must be created, maintained, and ultimately submitted for printing and remittance processing. This package encapsulates the batch-level data manipulation required by those workflows: inserting new batches, updating existing ones, deleting batches that are no longer required, performing concurrency-safe comparison of batch records, and orchestrating the submission of batches for printing.

The package is classified as OTHER in the documented API metadata, meaning it is an internal processing package rather than a formally published open interface. It is referenced by one other package, indicating it forms a supporting layer beneath higher-level Bills Receivable processing routines. It additionally supplies validation helpers, exemplified by Validate_GL_Date, which enforces that the accounting (GL) date for a batch falls within an open or future period and is not earlier than the issue date, and Validate_Maturity_Date, which enforces that the maturity date is on or after the issue date. These validations protect the integrity of draft data before it reaches accounting and printing.

Key Procedures and Functions

• INSERT_BATCH — Creates a new Bills Receivable batch record, establishing the batch header and its associated attributes so that drafts can subsequently be assigned to it.
• UPDATE_BATCH — Modifies an existing batch record. This is the procedure most commonly targeted by callers searching for "update_batch," and it applies changes to batch attributes while preserving the validations and locking expectations of the batch lifecycle.
• DELETE_BATCH — Removes a batch and its associated processing context, typically invoked when a batch is abandoned or created in error before submission.
• LOCK_COMPARE_BATCH — Performs a locking read of the batch record and compares its current state against an expected state. This supports optimistic concurrency control, guarding against lost updates when multiple sessions act on the same batch.
• SUBMIT_PRINT — Initiates the printing workflow for a batch, handing the batch to the printing process by which draft documents are generated for the customer.
• BR_CREATE — Serves as the driving creation routine that assembles and persists batch content, working in conjunction with the insert and update procedures to produce a complete, valid Bills Receivable batch.

Tables Accessed

The package reads and writes several Receivables and Trading Community tables through APPS synonyms. RA_BATCHES and RA_BATCH_SOURCES / RA_BATCH_SOURCES_ALL store the batch header and the source definition that controls numbering and batch behavior. AR_PAYMENT_SCHEDULES, RA_CUSTOMER_TRX, and RA_CUST_TRX_TYPES hold the transactions and installment lines to which drafts relate. AR_RECEIPT_METHODS and AR_SELECTION_CRITERIA provide the receipt method and selection rules that govern draft generation. HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES supply customer and site information used to identify the drawee and remit-to parties. These tables are accessed to validate, insert, update, or delete batch content and to resolve the reference data required for printing.

Usage Notes

ARP_PROCESS_BR_BATCHES is ordinarily invoked indirectly. In the Oracle Receivables Bills Receivable workbench, form-level actions such as creating, updating, or deleting a batch, and submitting a batch for printing, call into this package. Concurrent programs that build or print Bills Receivable batches similarly rely on it. Because the metadata classifies the package as OTHER rather than as a published API, custom code should avoid calling its procedures directly where a supported interface exists; where direct invocation is unavoidable, callers must supply a valid, open GL date and a maturity date no earlier than the issue date, and should respect the locking semantics provided by LOCK_COMPARE_BATCH. Debug output is gated by the AFLOG_ENABLED profile option, enabling tracing of each procedure during troubleshooting in EBS 12.1.1 and 12.2.2.