Search Results ar_doc_seq_gen_level

Overview

APPS.AR_SETUP is a foundational configuration package in the Oracle Receivables (AR) module of Oracle E-Business Suite, delivered in both 12.1.1 and 12.2.2. Its purpose is to expose the key System Options settings defined in Receivables to other components of the application through a lightweight, programmatic interface. Rather than requiring each dependent program to query the underlying setup tables directly, AR_SETUP provides centralized accessor routines that return the current runtime values of selected Receivables system parameters, most notably the AR: Show Billing Number profile option.

In the standard FND profile model, Receivables configuration values are frequently exposed through the FND_PROFILE API. AR_SETUP serves as an abstraction layer over this mechanism: the internal logic retrieves values from the PL/SQL global package ARP_GLOBAL.SYSPARAM, which is itself populated from the AR_SYSTEM_PARAMETERS table at session startup. This design reflects the historical migration of these settings from FND profile storage into Receivables system parameters, and the package preserves backward compatibility for callers that continue to request values by name.

Key Procedures and Functions

The ETRM metadata documents two callable units, both bearing the "OTHER" API classification.

• GET — A public procedure that accepts a profile/setup name and returns the corresponding value in an output parameter. It also accepts an optional organization identifier. Internally, the procedure normalizes the supplied name and branches on recognized values: AR_SHOW_BILLING_NUMBER, AR_CROSS_CURRENCY_RATE_TYPE, and AR_DOC_SEQ_GEN_LEVEL. For each recognized name, the value is read from the corresponding field in ARP_GLOBAL.SYSPARAM. If the supplied name is not recognized, the procedure raises the AR_INVALID_INTEROP_PROFILE exception, allowing callers to detect an unsupported configuration request.
• VALUE — A public function that mirrors the GET procedure, returning the configuration value directly as its function result. It recognizes the same three setup names and applies identical lookup logic through ARP_GLOBAL.SYSPARAM, raising AR_INVALID_INTEROP_PROFILE for unrecognized names. The function form is convenient for callers that need the value inline within expressions, SQL statements, or conditional logic.

Tables Accessed

The documented underlying table is AR_SYSTEM_PARAMETERS, accessed via an APPS synonym. This table stores the System Options configuration for each operating unit in Receivables, including the flag controlling display of the billing number, the cross-currency rate type, and the document sequence generation level. AR_SETUP does not query AR_SYSTEM_PARAMETERS directly on each call; instead it relies on the cached session-level values held in ARP_GLOBAL.SYSPARAM, which is initialized from this table. Consequently, AR_SETUP inherits the performance characteristics and initialization timing of ARP_GLOBAL, and its returned values reflect the system parameters loaded for the current session and organization.

Usage Notes

AR_SETUP is an internal utility package intended to be invoked by other Receivables packages and by inbound interoperability processing. The ETRM metadata records that it is referenced by eleven other packages, indicating wide internal reuse across the module. Custom code and extensions should call GET or VALUE when they need to honor the same setup decisions applied by standard Receivables functionality — for example, to determine whether a billing number should be displayed, which cross-currency rate type to apply, or how document sequences are generated.

Because the package raises AR_INVALID_INTEROP_PROFILE for unrecognized names, callers should guard against passing unsupported values. The optional organization identifier parameter permits values to be resolved in an organization-specific context. In upgraded environments, developers should note that the implementation sources values from ARP_GLOBAL.SYSPARAM rather than through direct FND_PROFILE.GET or FND_PROFILE.VALUE calls, as the commented-out legacy lines in the source indicate.