Search Results arp_view_constants




Overview
Explore in AI Chat

Overview

ARP_VIEW_CONSTANTS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is classified as an OTHER-type API within the Receivables (AR) module. The package functions as a session-level state and parameter repository for the Oracle Receivables user interface, most notably the Receipts workbench. Rather than carrying out heavy transactional processing itself, ARP_VIEW_CONSTANTS centralizes the storage and retrieval of runtime context — the currently selected customer, the apply date, receipt GL date, receipt currency, sales order reference, and various processing flags — so that multiple Receivables forms and subordinate packages can share a consistent set of values during an interactive session. Its status is VALID, and in the documented 12.2.2 metadata it exposes nineteen procedures and functions and is referenced by nine other packages, confirming its role as a shared utility layer.

Key Procedures and Functions

The documented interface consists of paired setter and getter routines that maintain package-level (session globals) state:

Tables Accessed

ARP_VIEW_CONSTANTS reads two documented tables through APPS synonyms. AR_SYSTEM_PARAMETERS supplies Receivables system-level defaults — accounting flexfield and period-related settings — that underpin default GL date derivation and validation. GL_PERIOD_STATUSES provides the open/closed status of General Ledger periods, which IS_GL_DATE_VALID and the default GL date routines rely upon to determine whether a proposed accounting date is permissible. The package also references FND_PROFILE (profile option values) and SYS.STANDARD per the dependency listing, indicating use of profile-driven defaults and standard Oracle built-ins. The package is not referenced by any database object, so its dependencies are inbound only.

Usage Notes

ARP_VIEW_CONSTANTS is invoked primarily from Oracle Receivables forms and from the nine Receivables packages that depend on it. The typical pattern is that a form initializes context by calling the SET_* routines when a user opens a Receipts or application window, and downstream logic calls the GET_* routines to read the shared values without re-querying the database. Because the state is held in package globals, values persist for the duration of a database session, making the package unsuitable for concurrent multiuser state within a single session and requiring care in custom code to reinitialize values between unrelated operations. Use in custom extensions should call the getters to honor the same defaults the standard Receipts forms apply, rather than hard-coding GL dates or currencies. The package should not be modified, as it is a standard, VALID Oracle-delivered object.