Search Results lock_cash_receipt

Overview

ARP_PROCESS_RCTS is a public PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Receivables (AR) module and encapsulates the core processing logic used to manipulate cash receipts — locking, deleting, and posting them — along with the associated accounting and reconciliation side effects. The package is classified as an API of type OTHER in the ETRM metadata. Its header comment identifies the source file as ARRERGWB.pls, with the current revision at the time of the documented shipment being 120.26.12000000.2 (last modified 12-OCT-2007). The presence of a REVISION function is a standard Oracle EBS convention that allows callers to interrogate the package version at runtime. Although the package body is relatively small in terms of documented entry points (six), the procedures it exposes touch a broad range of Receivables and Cash Management tables, reflecting the fact that cash receipt processing is inherently cross-functional.

Key Procedures and Functions

The package exposes six documented procedures and functions:

• REVISION — a function that returns the package revision string, used for version tracking and diagnostics.
• LOCK_CASH_RECEIPT — locks a cash receipt record so that concurrent updates cannot proceed against the same receipt. The historical modification log shows this procedure has been extended over time to accommodate CashBook float support (anticipated clearing date), the Japan localization (customer bank branch), global flexfield attributes, and, per Bug 2688648, an additional receipt status parameter.
• DELETE_CASH_RECEIPT — removes a cash receipt, presumably together with its dependent history, distribution, and application rows, subject to Receivables' integrity rules.
• POST_QUERY_LOGIC — the entry point relevant to the user's search. It encapsulates the logic that must be executed after a receipt is queried (for example, re-derivation of displayed attributes or status), and is typically invoked from Forms or post-query triggers rather than from batch jobs.
• SET_POSTED_FLAG — sets the posted indicator on a receipt or related transaction, marking it as accounted and preventing re-posting.
• DELETE_TRANSACTION_EXTENSION — removes transaction extension data associated with a receipt, supporting cleanup of supplementary or descriptive flexfield data.

Tables Accessed

The package reads and writes through APPS synonyms. Receipt-centric tables include AR_CASH_RECEIPTS (the master receipt row), AR_CASH_RECEIPT_HISTORY (status and workflow history), AR_DISTRIBUTIONS (accounting distributions) and AR_TRX_SUMMARY_HIST. Application and adjustment activity touches AR_RECEIVABLE_APPLICATIONS, AR_ADJUSTMENTS and AR_PAYMENT_SCHEDULES. Batch and setup context is drawn from AR_BATCHES and AR_SYSTEM_PARAMETERS, while AR_CUSTOMER_TRX supplies transaction information. Cash Management integration is handled through CE_STATEMENT_HEADERS, CE_STATEMENT_LINES and CE_STATEMENT_RECONCILS_OU, and payment-side data comes from AP_CHECKS and AP_INVOICE_SELECTION_CRITERIA. This table list confirms that the package participates in both receipt maintenance and bank reconciliation workflows.

Usage Notes

ARP_PROCESS_RCTS is not referenced by any other documented package, so it is intended to be called directly — typically from the Receivables Cash Receipts form, from concurrent programs that post or delete receipts, or from custom extensions that need to lock or manipulate a receipt. Because POST_QUERY_LOGIC and LOCK_CASH_RECEIPT are UI-oriented, they are most often invoked interactively; DELETE_CASH_RECEIPT, SET_POSTED_FLAG and DELETE_TRANSACTION_EXTENSION are more commonly reached through batch processing or corrective data-fix scripts. Custom callers should treat the package as a supported API, respect the locking semantics of LOCK_CASH_RECEIPT before any update, and verify package version via REVISION when validating behavior across 12.1.1 and 12.2.2 environments.