Search Results arp_cr_batches_pkg




Overview

ARP_CR_BATCHES_PKG is a PL/SQL package in the APPS schema of Oracle E-Business Suite Release 12.1.1 and 12.2.2 that encapsulates the core data-access and lifecycle management logic for Accounts Receivable receipt batches. The package name reflects its association with the AR "CR" batch processing path, and it operates over the AR_BATCHES and AR_BATCHES_S tables, which store the batch header records used to group and control automatic and manual receipt entry in Oracle Receivables. It provides a standardized, reusable layer of procedures for inserting, updating, deleting, locking, and fetching batch rows, insulating callers from direct SQL against the underlying tables and enforcing consistent row-locking and concurrency behavior. The package is classified as OTHER in ETRM, indicating that it is an internal infrastructure package rather than a public, formally documented API. It occupies a central position in the receipt batch dependency graph: it references AR_BATCHES directly, and it is referenced by nine other packages, including ARP_BR_REMIT_BATCHES, ARP_PROCESS_BOE, ARP_PROCESS_BR_REMIT, ARP_PROGRAM_BR_REMIT, ARP_REVERSE_RECEIPT, ARP_RW_BATCHES_CHECK_PKG, ARP_RW_BATCHES_PKG, AR_BILLS_MAINTAIN_LIB_PVT, and AR_BILLS_MAINTAIN_PUB. This dependency footprint demonstrates that the package is a foundational building block for receipt batch processing across remittance, reversal, bills receivable, and batch maintenance flows.

Key Procedures and Functions

The documented interface exposes eleven procedures and functions that together form a complete CRUD and concurrency-control surface for receipt batches. Note that the following descriptions reflect purpose only; parameter lists are not published in the metadata.

  • SET_TO_DUMMY — Initializes or resets a batch record structure to dummy/default values, typically used to prepare a record variable before a query or insert.
  • INSERT_P — Inserts a new row into the receipt batch tables, creating a batch definition.
  • UPDATE_P — Updates an existing batch row, applying modified batch attributes.
  • DELETE_P — Removes a batch row from the underlying tables.
  • LOCK_P — Acquires a row-level lock on a batch record, blocking until the lock is available.
  • NOWAITLOCK_P — Attempts to lock a batch row without waiting, returning immediately if the row is already locked.
  • FETCH_P — Retrieves a batch row into a record structure without locking it.
  • LOCK_FETCH_P — Fetches a batch row while simultaneously acquiring an exclusive lock (SELECT FOR UPDATE behavior).
  • NOWAITLOCK_FETCH_P — Fetches and locks a batch row without waiting for a competing lock.

The consistent "_P" suffix indicates procedure-based implementations, and the complementary LOCK versus NOWAITLOCK pairs give callers explicit control over blocking semantics during concurrent batch operations.

Tables Accessed

The package references the following objects through APPS synonyms:

  • AR_BATCHES — The primary receipt batch table; read and written by the insert, update, delete, and fetch procedures.
  • AR_BATCHES_S — The batch sequence or secondary batch table that supports batch numbering and related batch attributes.
  • AR_SYSTEM_PARAMETERS — Consulted for Receivables system-level settings that govern batch behavior and defaults.
  • DBMS_SQL — Oracle's dynamic SQL package, indicating runtime-constructed SQL for flexible query or update logic.
  • DUAL — The standard single-row utility table, used for trivial lookups or value evaluation.

Usage Notes

ARP_CR_BATCHES_PKG is an internal package and is not intended for direct invocation by end users or external integrations. It is typically called from within Oracle Receivables forms and concurrent programs, and is invoked by higher-level packages such as ARP_RW_BATCHES_PKG, ARP_BR_REMIT_BATCHES, ARP_PROCESS_BR_REMIT, ARP_REVERSE_RECEIPT, and the AR_BILLS_MAINTAIN_PUB/LIB_PVT family. Custom code should normally use the public Receivables APIs rather than this package, because its interface is not a supported public contract and may change between releases. When referenced in troubleshooting, it appears in dependency chains for receipt batch creation, remittance batch processing, batch reversal, and bills receivable maintenance.