Search Results oe_sys_parameters




Overview

OE_SYS_PARAMETERS is a foundational PL/SQL package body in the Oracle E-Business Suite Order Management (OM) module, owned by the APPS schema. Its primary purpose is to centralize the retrieval, caching, and management of Order Management system-level parameters — the profile-driven and setup-driven configuration values that govern how order entry, pricing, scheduling, shipping, and returns behavior operate across the enterprise. In EBS 12.1.1 and 12.2.2, almost every major OM workflow depends on this package to resolve runtime configuration such as default operating units, order numbering rules, negative pricing controls, freight charge behaviors, and return processing options. Rather than each module querying the underlying setup tables independently, OE_SYS_PARAMETERS provides a single, validated access point that ensures consistent interpretation of OM system parameters across forms, concurrent programs, and the public APIs.

Key Procedures and Functions

The documented public interface exposes two program units:

  • VALUE — Returns the value of a specified Order Management system parameter. This is the primary accessor used throughout OM code to retrieve a configuration setting by its parameter identifier, applying whatever default or override logic is appropriate for the current context.
  • VALUE_WNPS — A variant of the value accessor that supports parameter retrieval where a naming or context qualifier (suffix/namespace) distinguishes the requested parameter. It allows callers to obtain a parameter value when the standard single-argument retrieval is insufficient to disambiguate the setting.

Both functions are designed for high-frequency invocation and typically rely on package-level caching to avoid repeated hits against the base setup tables during a single session or transaction.

Tables Accessed

The package resolves parameter values from the Order Management setup tables that underpin system parameters — most notably the OE_SYSTEM_PARAMETERS_ALL table together with associated lookup and profile option sources accessed through APPS synonyms. These tables store the configuration values defined during OM implementation setup. The referenced dependency metadata also shows the package depends on FND_API for standardized error handling and on OE_DEBUG_PUB for diagnostic logging, indicating that failures and debug traces are routed through the standard EBS API and debugging framework rather than raised ad hoc.

Usage Notes

OE_SYS_PARAMETERS is invoked broadly rather than being user-facing directly. It is called from Order Management forms, from concurrent programs such as order import and scheduling processes, and from the family of public OM APIs. With 214 documented dependent packages, it is one of the most widely referenced utilities in the OM schema, and it is not itself dependent on any higher-level object. Because it encapsulates parameter resolution and caching, customizations and extensions that need to read OM system parameters should call VALUE or VALUE_WNPS rather than querying OE_SYSTEM_PARAMETERS_ALL directly, ensuring consistent defaulting and error handling. Debug output can be enabled through OE_DEBUG_PUB when diagnosing unexpected parameter-driven behavior.