Search Results nowaitlock_fetch_p

Overview

ARP_MISC_CASH_DIST_PKG is an Oracle Receivables (AR) PL/SQL package owned by the APPS schema that encapsulates the core database operations for the AR_MISC_CASH_DISTRIBUTIONS entity, which stores miscellaneous cash distribution records used during cash receipt processing. The package provides a standardized, encapsulated API surface—an INSERT/UPDATE/DELETE/LOCK/FETCH pattern typical of Oracle EBS table-handler packages—that allows forms, concurrent programs, and other PL/SQL routines to manipulate miscellaneous cash distribution rows without issuing direct DML against the underlying table. The header comment identifies the source file as ARRIMCDS.pls, version 120.4, last shipped in 2005; the package therefore represents a long-stable interface present in both EBS 12.1.1 and 12.2.2. It is classified in ETRM as an "OTHER" API rather than a formally published open interface, meaning it is intended primarily for internal Oracle Receivables use rather than as a documented external integration point. Because the package maintains the transaction-level consistency of miscellaneous cash distribution data, it plays a supporting role in the accurate recording and application of miscellaneous cash receipts against customer accounts.

Key Procedures and Functions

ETRM documents six public procedures in the package specification:

• INSERT_P — Inserts a new miscellaneous cash distribution row. It accepts the full record from AR_MISC_CASH_DISTRIBUTIONS and returns the generated primary key value (misc_cash_distribution_id) to the caller.
• UPDATE_P — Updates an existing miscellaneous cash distribution row, accepting the modified record and applying the changes to the stored data.
• DELETE_P — Removes a miscellaneous cash distribution row identified by its primary key.
• LOCK_P — Acquires a lock on the specified distribution record, used to serialize concurrent updates during a transaction.
• FETCH_P — Retrieves a distribution record by primary key. This variant performs a locking fetch (SELECT ... FOR UPDATE), so the returned record is locked for the duration of the transaction.
• NOWAITLOCK_FETCH_P — Performs the same retrieval as FETCH_P but uses a NOWAIT locking mode. If the row is already locked by another session, the call fails immediately rather than waiting, allowing the caller to detect contention. This is the procedure referenced in the user's search.

No parameter lists beyond those shown in the package specification excerpt should be assumed; all procedures follow the single-record or single-key signature conventions shown.

Tables Accessed

The package references the following tables through APPS synonyms:

• AR_MISC_CASH_DISTRIBUTIONS — The primary base table holding miscellaneous cash distribution records; the target of INSERT_P, UPDATE_P, DELETE_P, and the source for FETCH_P and NOWAITLOCK_FETCH_P.
• AR_MISC_CASH_DISTRIBUTIONS_S — The corresponding DFF/sequence-support or audit shadow table associated with the base entity.
• AR_CASH_RECEIPT_HISTORY — Cash receipt history records, referenced to maintain consistency with the originating receipt activity.
• AR_SYSTEM_PARAMETERS — System-level Receivables setup values that influence package behavior (for example, organizational or security defaults).
• DUAL — Used for single-row utility queries such as sequence value retrieval.

Usage Notes

ARP_MISC_CASH_DIST_PKG is typically invoked from Oracle Receivables forms and from other PL/SQL packages rather than directly by end users. ETRM records that it is referenced by three other packages, confirming it functions as a lower-level table-handler dependency. Developers writing custom code against AR_MISC_CASH_DISTRIBUTIONS should prefer these packaged procedures over direct DML to preserve locking and validation behavior. In particular, NOWAITLOCK_FETCH_P is appropriate where the caller must detect and handle row-level contention without blocking—such as interactive forms that require responsive feedback—whereas FETCH_P is used when waiting on the lock is acceptable. The package's stable version history indicates its interface has not materially changed across 12.1.1 and 12.2.2.