Search Results oe_config




Overview
Explore in AI Chat

Overview

OE_CONFIG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM documentation as an "OTHER" API rather than a public, supported interface. Its documented status is VALID in both Oracle EBS 12.1.1 and 12.2.2. Despite the "OE" prefix, which normally associates an object with the Order Management (OM) product family, the procedures documented for this package carry a "CZ" prefix that is characteristic of Oracle Configurator (CZ) and Advanced Pricing integration logic. OE_CONFIG therefore functions as a backend utility package that bridges the Order Management pricing and configuration flow with Oracle Configurator's rule evaluation engine.

The package supports the runtime behavior of the Configurator user interface during order entry, serving as a compact repository of flag-setting and status-counting routines that the configuration UI uses to determine the state of a configured item. It is not a general-purpose public API and is not referenced by any other documented package, indicating that its consumers are Oracle Forms, Java-based Configurator runtime components, or internal product code rather than customer-built PL/SQL.

Key Procedures and Functions

ETRM documents nine procedures or functions within OE_CONFIG, all sharing the CZ naming convention:

  • CZ_BCE_DETAILS_FLAG — Manages a flag that controls whether Bill of Configuration details are surfaced during configuration processing.
  • CZ_GET_LIST_PRICE — Retrieves the list price for a configurable item or option, drawing from the pricing tables accessed by the package.
  • CZ_ERROR_COUNT — Returns the count of hard errors generated during a configuration session or rule evaluation pass.
  • CZ_MESSAGE_COUNT — Returns the total number of messages raised, providing an overall indicator of configuration activity.
  • CZ_AUTOSELECT_COUNT — Reports the number of options automatically selected by the Configurator's autoselect logic.
  • CZ_OVERRIDE_ERROR_COUNT — Counts errors associated with user overrides applied to configuration selections.
  • CZ_OVERRIDEN_COUNT — Counts the total number of options that have been overridden by the user.
  • CZ_WARN_COUNT — Returns the count of warnings raised during rule evaluation.
  • CZ_SUGGEST_COUNT — Reports the number of suggested selections offered by the Configurator engine.

The count-based functions form a coherent diagnostic family used to summarize the outcome of a configuration pass: errors, warnings, overrides, autoselections, and suggestions. The precise parameter lists are not exposed in the available metadata and should not be assumed.

Tables Accessed

The package reads from three documented base objects through APPS synonyms:

  • MTL_SYSTEM_ITEMS_KFV — the key flexfield view over inventory items, used to resolve item descriptions, attributes, and configuration status for the item being priced or configured.
  • SO_PRICE_LISTS — the pricing header table, used by CZ_GET_LIST_PRICE to identify the applicable price list and its currency and effective dates.
  • SO_PRICE_LIST_LINES — the pricing line table, from which the actual list price for the configurable item or option is derived.

Together these accessed tables indicate that OE_CONFIG's pricing function is limited to list price lookup, not the full pricing engine's modifier or qualifier logic.

Usage Notes

OE_CONFIG is invoked implicitly by Oracle Configurator runtime components and Order Management configuration flows, typically during order line entry when a model or option is selected and its price and rule-validation status must be reported. Because it is referenced by no other documented package and is classified as OTHER rather than as a public API, it should be treated as an internal Oracle implementation detail. Oracle ETRM does not list OE_CONFIG as a supported extension point, and its procedures are not intended for direct invocation from customer-written forms, concurrent programs, or custom PL/SQL. Customers requiring configuration or pricing integration should use the supported Configurator and Advanced Pricing APIs instead. Any direct dependency on OE_CONFIG risks breakage during patching or upgrade between 12.1.1 and 12.2.2, since internal package signatures may change without notice.