Search Results oe_sys_parameters_pvt




Overview
Explore in AI Chat

Overview

OE_SYS_PARAMETERS_PVT is a private PL/SQL package in the APPS schema of Oracle E-Business Suite Release 12.1.1 and 12.2.2. As the "PVT" suffix indicates, this is an internal helper package belonging to Order Management (OE) rather than a public API intended for direct customer invocation. Its principal business function is to provide centralized, cached access to Order Management system parameter values and to the associated Oracle Receivables system parameters that govern order-entry behavior. Order Management relies on a large body of setup attributes — tax calculation method, defaulting rules, pricing and fulfillment flags, currency precision, and accounting context — and these values are stored in OE_SYS_PARAMETERS_ALL and related setup tables. OE_SYS_PARAMETERS_PVT shields the rest of the OE code base from the physical storage details of that configuration data by exposing a single point of retrieval that other OE packages can depend upon consistently.

Key Procedures and Functions

The ETRM metadata documents two program units in this package, both of which are concerned with parameter retrieval:

  • VALUE — The general-purpose accessor used by OE code to obtain a named Order Management system parameter. Rather than each caller querying the OE system parameters table directly, callers invoke this function to resolve a parameter by its identity and receive the configured value. This encapsulation ensures that any change to how parameters are stored or defaulted is made in one place.
  • GET_AR_SYS_PARAMS — A retrieval routine that returns Receivables system parameters as needed by Order Management. Because order transactions flow into Oracle Receivables and interact with tax and accounting rules owned by AR, OE code periodically needs the effective AR system parameter values; this function supplies them. The metadata does not document the parameter list, and the exact PL/SQL signature is not reproduced here.

The package body is listed as valid in the documented environment, confirming that both program units resolve against their dependencies without error.

Tables Accessed

Three tables are documented as referenced through APPS synonyms:

  • OE_SYS_PARAMETERS_ALL — The Order Management system parameters table. This is the primary source of the values returned by the VALUE function, holding configuration choices such as tax method and order-entry defaults.
  • AR_SYSTEM_PARAMETERS_ALL — The Oracle Receivables system parameters table. It supplies the data returned by GET_AR_SYS_PARAMS, giving OE visibility into AR-level settings such as tax engine configuration and accounting conventions.
  • PLITBLM — The Oracle Forms PL/SQL table-of-varchar2 utility type, an internal dependency associated with the Forms-based implementation that surrounds Order Management's setup screens. It is referenced as infrastructure rather than as application data.

The ETRM dependency listing also shows a reference to SYS and STANDARD, which are generic Oracle RDBMS catalog dependencies rather than application objects.

Usage Notes

OE_SYS_PARAMETERS_PVT is referenced by eleven other PL/SQL packages, which defines its practical role: it is consumed rather than called directly. The most significant callers include OE_INVOICE_PUB, OE_INLINE_CUSTOMER_PUB, OE_INLINE_FLEX, OE_BULK_TAX_UTIL, OM_TAX_UTIL, OM_SETUP_VALID_PKG, OE_OE_FORM_HEADER, OE_UPGRADE_MISC and OE_UPGRADE_MISC_NEW, and the public OE_SYS_PARAMETERS package itself. The presence of OE_UPGRADE_MISC and OE_UPGRADE_MISC_NEW among the dependents indicates that the package is also used during upgrade processing to read parameter values while migrating or validating setup data.

Because it is a PVT-classified package, Oracle does not publish it as a supported integration point and does not guarantee signature stability across patches or releases. Customers and partners who require Order Management system parameter values from custom code should invoke the public API layer rather than calling OE_SYS_PARAMETERS_PVT directly. The package is expected to be invoked in the context of Order Management forms activity, pricing and tax computation, customer and invoice processing, and concurrent setup-validation programs, and it depends on the standard OE and AR setup tables being populated and valid for the operating unit in question. If those setup rows are missing or the AR system parameters are undefined, callers can expect retrieval to fail or return null, which is a common root cause when Order Management transactions raise unexpected setup-related errors.