Search Results ar_date_dummy

Overview

ARP_SELECTION_CRITERIA_PKG is an internal PL/SQL package in the Oracle Receivables (AR) module that encapsulates all data manipulation logic for the AR_SELECTION_CRITERIA entity. Selection criteria records define the filtering rules used by Receivables processes — most notably the Automatic Remittance, AutoInvoice, and various customer and transaction query processes — to select the set of records a given run will operate against. By centralizing insert, update, delete, fetch, and locking behavior in a single package body, Oracle ensures that concurrency handling, WHO-column maintenance (created_by, last_updated_by, last_update_date), and referential integrity are applied consistently regardless of the calling form, concurrent program, or dependent API.

The package is classified as OTHER in the ETRM metadata for 12.1.1 and 12.2.2, indicating that it is a supporting implementation unit rather than a public, declaratively registered API. The header revision string indicates the file has been stable since release 12.0-era development, and the logic carries forward unchanged into 12.1.1 and 12.2.2. The user search term ar_date_dummy corresponds directly to the AR_DATE_DUMMY package constant declared in the specification and body, defined as to_date(1,'J') — the Julian day 1 sentinel value.

Key Procedures and Functions

The package exposes eleven documented program units:

• INSERT_P — Inserts a new row into AR_SELECTION_CRITERIA, populating surrogate key and WHO columns from the caller-supplied record and package globals.
• UPDATE_P — Updates an existing selection criteria row, applying optimistic concurrency checks against last_update_date.
• DELETE_P — Removes a selection criteria row, typically invoked after a user deletes a saved query or criteria set in the Receivables UI.
• FETCH_P — Retrieves a single selection criteria row into a %ROWTYPE record for display or downstream processing.
• LOCK_P — Issues a SELECT ... FOR UPDATE to serialize access to a row prior to modification.
• LOCK_FETCH_P — Combines locking and fetching into one operation, returning the locked record.
• LOCK_COMPARE_P — Locks a row and compares the caller's copy against the database copy to detect concurrent modification.
• LOCK_COMPARE_COVER — A helper used by the lock-compare path to perform the comparison work.
• SET_TO_DUMMY — Assigns sentinel constants, including AR_DATE_DUMMY, to columns that must be nulled or masked during update operations.
• DISPLAY_SELECTION — Debugging entry point that dumps selection criteria via arp_util.debug.
• DISPLAY_SELECTION_REC — Private debugging routine that dumps a single AR_SELECTION_CRITERIA %ROWTYPE, excluding creation_date and last_update_date.

Tables Accessed

The package operates against AR_SELECTION_CRITERIA (the base table holding criteria header rows) and its companion AR_SELECTION_CRITERIA_S (the sequence-backed surrogate-key table that supplies selection_criteria_id values). DUAL is used solely to satisfy SELECT INTO syntax for constant and sequence evaluation. Access is through APPS synonyms.

Usage Notes

ARP_SELECTION_CRITERIA_PKG is invoked primarily from the Receivables selection criteria and saved-query forms, but it may also be called by concurrent programs and custom extensions that programmatically maintain criteria records. The dummy constants — AR_TEXT_DUMMY, AR_NUMBER_DUMMY, and AR_DATE_DUMMY — exist because Oracle Forms-based code cannot bind NULL values directly into certain update statements; assigning these sentinels allows the SET_TO_DUMMY logic to detect and translate them into NULLs. One other package in Receivables references this package, indicating a layered dependency within the AR processing stack. Custom code should prefer the documented public entry points and avoid calling private procedures directly.