Search Results value_wnps

Overview

APPS.OE_SYS_PARAMETERS is a central utility package within the Oracle Order Management (OM) module of Oracle E-Business Suite. Its purpose is to provide runtime access to Order Management system parameters — the configurable values that govern order entry, pricing, shipping, and fulfillment behavior across operating units and inventory organizations. Rather than requiring each form, concurrent program, or dependent PL/SQL unit to query the underlying parameter storage tables directly, OE_SYS_PARAMETERS exposes a stable, packaged interface that resolves a parameter name and an optional organization context into the effective parameter value. Because the package is owned by APPS and declared with AUTHID CURRENT_USER, it executes under the privileges of the calling session, allowing it to be invoked broadly across the OM code base and from customer extensions without elevated grants. The documented metadata records that the package is referenced by 214 other packages, confirming its role as a low-level dependency that many higher-level Order Management APIs and validation routines rely upon for consistent parameter resolution. This broad reuse makes the package a suitable focal point when diagnosing order-management configuration discrepancies between environments.

Key Procedures and Functions

The documented interface comprises two functions, VALUE and VALUE_WNPS. Both return VARCHAR2 and resolve the current value of a named Order Management system parameter, accepting a parameter name together with an optional organization identifier. The distinction between them is a PL/SQL purity concern: VALUE_WNPS carries a WNPS (Write No Package State) pragma, which permits the function to be referenced from the WHERE clause of a SQL statement, whereas VALUE has no such pragma and is intended for PL/SQL contexts. The source excerpt further shows that the pragma restriction originally applied to VALUE_WNPS was removed to address defects 1632598 and 1715969, after which the packaged declaration retains only the AUTHID CURRENT_USER clause. The two functions are therefore functionally equivalent in purpose but differ in whether the database can safely inline them into SQL predicates.

Tables Accessed

The documented ETRM metadata does not enumerate the tables referenced by OE_SYS_PARAMETERS. In practice, the package resolves parameter values from Order Management's system-parameter storage, which holds parameter definitions and their organization-specific overrides. The absence of a documented table list means that direct dependencies on base tables should not be assumed; consumers should treat the package as the authoritative access path and avoid duplicating its lookups in custom SQL.

Usage Notes

OE_SYS_PARAMETERS is typically invoked from Order Management forms, from concurrent programs, and from custom PL/SQL that must honor the same configuration as standard OM behavior. Because VALUE_WNPS tolerates SQL invocation, it is the preferred choice within SELECT statements and views; VALUE is appropriate when the call occurs purely in PL/SQL. Callers operating in a multi-organization context should pass the organization identifier so that organization-specific overrides are respected. In 12.1.1 and 12.2.2 installations the package is a shared component, so any changes to its signature or behavior can affect hundreds of dependent objects; customizations should consume the package rather than modify it.