Search Results oe_order_lines_s




Overview

OE_PROCESS_OPTIONS_PVT is a private (PVT) PL/SQL package body in the APPS schema that supports Oracle Order Management's configurator processing logic. Its primary business function is to derive, validate, and apply the "process options" associated with configured items on an order line — that is, the runtime behavior that governs how a model, kit, or configuration is exploded, matched, and cascaded during order entry. The package bridges the order capture layer (OE_ORDER_PUB, OE_ORDER_LINES) with the configuration engine (OE_CONFIG_PVT, OE_CONFIG_UTIL, OE_CONFIG_VALIDATION_PVT) and the bill-of-material and item master data (BOM_EXPLOSIONS, MTL_SYSTEM_ITEMS_KFV). Because it is classified as a private API, it is intended for internal use by other Order Management packages rather than as a public integration surface. The ETRM metadata records the object as VALID and notes that it is referenced by two other packages while itself referencing only Oracle-owned dependencies plus DUAL and PLITBLM.

Key Procedures and Functions

The package body exposes seven documented units. Their names and purposes are as follows:

  • PROCESS_CONFIG_OPTIONS — the main driver that evaluates the process options applicable to a configured line and applies the resulting behavior during order processing.
  • USE_CONFIGURATOR — determines whether the configurator should be invoked for the item or line in question, based on item attributes and profile settings.
  • GET_OPTIONS_FROM_DB — retrieves the stored process option values (for example, from OE_SYS_PARAMETERS and related setup) so downstream logic can act on the persisted configuration.
  • FIND_MATCHING_COMP_INDEX — locates the matching component index within a configuration, supporting component-level matching against configured structures.
  • PREPARE_CASCADE_TABLES — populates and prepares the cascade (PL/SQL) tables used to propagate option changes across the model and its components.
  • HANDLE_RET_STATUS — normalizes and interprets the return status from called APIs, typically routing messages through FND_MESSAGE and OE_MSG_PUB and honoring the FND_API error-handling convention.
  • PRINT_TIME — a debug/timing utility that emits elapsed-time diagnostics, gated by OE_DEBUG_PUB.

Tables Accessed

The package operates against a focused set of objects, all referenced through APPS synonyms:

  • OE_ORDER_LINES and OE_ORDER_LINES_S — the order line base table and its sequence. This is the central context for the package: configured options are read from and written back to order lines. The presence of OE_ORDER_LINES_S in the dependency list is the direct reason a search for "oe_order_lines_s" surfaces this package; the sequence is referenced implicitly through inserts and lock/version handling on OE_ORDER_LINES.
  • BOM_EXPLOSIONS — supplies the bill-of-material explosion used to identify components belonging to a configured model.
  • MTL_SYSTEM_ITEMS_KFV — provides item master descriptive attributes (the key flexfield view) needed to evaluate item-level process options and configurator eligibility.
  • DUAL — used for single-row scalar evaluations and constant retrieval.
  • PLITBLM — the PL/SQL index-by table of long values, typically employed to buffer option/cascade data within session memory.

Usage Notes

OE_PROCESS_OPTIONS_PVT is invoked internally by Order Management during order entry and configuration processing, most commonly from the Order Management (OEXOEORD) sales order form and from the public order APIs where a configured line is added or changed. It is not a standalone concurrent program and has no report or form of its own; it is called by its two referencing packages and by OE_ORDER_PUB and OE_LINE_UTIL. Because it is a private API, customers and partners should not call it directly — custom code that needs configurator behavior should use the supported public APIs (OE_ORDER_PUB and OE_CONFIG_PUB) instead. Debug output is controlled through OE_DEBUG_PUB and FND_PROFILE settings, which is useful when troubleshooting configuration cascade or component-matching issues in a 12.1.1 or 12.2.2 environment.