Results for “lock_f_batch_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ARP_CR_HISTORY_PKG is a core Oracle Receivables server-side PL/SQL package that encapsulates the business logic governing the AR_CASH_RECEIPT_HISTORY and AR_CASH_RECEIPT_HISTORY_S tables. These tables hold the status-transition audit trail for every cash receipt processed in Oracle E-Business Suite. Each time a receipt moves between states — for example from Unconfirmed to Confirmed, Confirmed to Remitted, Cleared, Reversed, or Applied — a new history row is written and an old history row is closed. The package in schema APPS provides the insert, update, delete, locking, and query services that other Receivables routines rely on to keep this chronological record consistent across 12.1.1 and 12.2.2.

The ETRM repository documents the package as VALID and classifies it as an OTHER API. It exposes no formally published public API contract in the manner of AR_RECEIPT_API_PUB, but it is heavily reused internally: the metadata records that it is referenced by fourteen other database objects, none of which it depends upon in return.

Key Procedures and Functions

Twenty documented procedures comprise the package interface. They follow a consistent naming convention:

• SET_TO_DUMMY — initialises or nulls package-level variables and cursor state.
• INSERT_P, UPDATE_P, DELETE_P, DELETE_P_CR — the core DML primitives that create, amend, remove, or purge history rows associated with a given cash receipt.
• LOCK_P, NOWAITLOCK_P — acquire row-level locks on history records, the NO_WAIT variants failing fast when the row is already locked.
• LOCK_F_BATCH_ID, NOWAITLOCK_F_BATCH_ID — lock and fetch by batch identifier.
• LOCK_FETCH_P, NOWAITLOCK_FETCH_P — combined lock-and-retrieve operations.
• FETCH_P, FETCH_F_CRID, FETCH_F_CR_ID — cursor-driven retrieval of history rows, by generic criteria or by cash receipt identifier.
• LOCK_F_CR_ID, NOWAITLOCK_F_CR_ID, LOCK_FETCH_F_CR_ID, NOWAITLOCK_FETCH_F_CR_ID — receipt-ID-specific locking and fetch variants.
• LOCK_HIST_COMPARE_P — locks a history row and compares its attributes against supplied values, supporting optimistic concurrency checks before an update.

Tables Accessed

The package references six application tables via APPS synonyms, together with DUAL:

• AR_CASH_RECEIPT_HISTORY — the primary target for insert, update, delete, and fetch activity.
• AR_CASH_RECEIPT_HISTORY_S — the corresponding audit/shadow table populated by Oracle Forms and concurrent programs for row-version tracking.
• AR_CASH_RECEIPTS — the parent receipt record; read to validate the receipt a history row belongs to and to confirm its current status.
• AR_BATCHES — read to validate batch context when history locking or fetching is driven by batch identifier.
• AR_SYSTEM_PARAMETERS — supplies Receivables system-level options, such as the multiple reporting currencies (MRC) setting and other defaults that affect history processing.
• DUAL — used for single-row lookups and function return values.

The package also calls supporting utilities: ARP_GLOBAL, ARP_STANDARD, ARP_UTIL, AR_MRC_ENGINE (for multiple reporting currency propagation), FND_PROFILE, and GL_CA_UTILITY_PKG.

Usage Notes

ARP_CR_HISTORY_PKG is an internal infrastructure package, not a public extension API. It is invoked indirectly whenever a receipt status transition is committed — from the Receipts workbench form, from Automatic Receipts processing, from Remittance and Automatic Clearing concurrent programs, and from reversal and unapplied-receipt routines. The presence of paired LOCK and NOWAITLOCK procedures indicates that the standard transactional pattern is to lock the current active history row, verify it via LOCK_HIST_COMPARE_P, close it with UPDATE_P, and open the next state with INSERT_P. Customisations should not call these procedures directly; developers should instead use the supported AR_RECEIPT_API_PUB interfaces, which perform the appropriate history maintenance through this package on the caller's behalf. Because the package holds no dependencies on other ARPL routines, it can be safely treated as a leaf-level utility within the Receivables dependency graph.