Results for “parse_output_xml”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OE_CONFIG_UTIL is a utility package within the Oracle E-Business Suite Order Management (ONT) module that centralizes the PL/SQL logic used to manage configured items throughout the order lifecycle. Configured items, such as assemble-to-order (ATO) and pick-to-order (PTO) models, require specialized processing that differs substantially from standard inventory items: configurations must be validated, completed, exploded into their component hierarchies, linked or delinked from existing order lines, and reserved against supply. OE_CONFIG_UTIL encapsulates this logic so that the Order Management forms, public APIs, and concurrent programs can share a single, consistent implementation.

The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking user rather than the defining schema. Its declaration block defines numerous constants that govern the behavior of the configuration engine, including exploder parameters (operation sequence, engineering change order handling, implementation status, current revision flags), component selection modes (included components only, all components, or orderable optional components), a maximum explosion depth of sixty levels, and flags such as CASCADE_CHANGES_FLAG and G_CONFIG_UI_USED that track cascading recursion and whether the user invoked the configurator interface. Profile values retrieved through FND_PROFILE, such as the included-item freeze method and the model DFF copy behavior, are cached in package globals.

The package is referenced by thirty-four other packages, confirming its role as a foundational library for configuration processing rather than an entry point invoked directly by end users.

Key Procedures and Functions

The documented API surface contains forty-nine procedures and functions. The most prominent are summarized below; parameter signatures are omitted deliberately, as the metadata does not document them in full.

• Config_Exists — a boolean function that determines whether a given order line represents a configuration.
• Complete_Config — the procedure most closely associated with the user's search term. It finalizes a configuration by completing the top model line passed to it. Because it is a public entry point, it is the routine custom code would call to programmatically complete a configuration.
• Cascade_Changes — propagates modifications made to a parent line down to its configuration children, honoring the CASCADE_CHANGES_FLAG to prevent recursive re-entry.
• Change_Configuration — applies a configuration change request against an order line.
• Query_Config_Line — retrieves the line record associated with a parent configuration line.
• Validate_Configuration, Validate_Cfgs_In_Order, Validate_Configuration_Upg — validate configurations, including a variant used during upgrade processing.
• Explode — performs the Bill of Materials explosion for a model, using the BMX constants and the sixty-level depth limit defined in the specification.
• Link_Config, Delink_Config, Delink_Config_Batch — associate or disassociate configuration components with order lines, in single and batch modes.
• Match_And_Reserve, Supply_Reserved — handle supply matching and reservation for configured lines.
• Query_Options, Query_Ato_Options, Query_Included_Items — return option and included-item detail for a configuration.
• Freeze_Included_Items, Freeze_Inc_Items_For_Order, Process_Included_Items — apply freeze logic and process included-item behavior, governed by the ONT_INCLUDED_ITEM_FREEZE_METHOD profile.

Tables Accessed

The documented table references reflect the package's dual role of reading configuration structure and writing order data. Order data is read and written through OE_ORDER_HEADERS, OE_ORDER_LINES, OE_ORDER_LINES_ALL, OE_ORDER_LINES_HISTORY, and OE_ORDER_LINES_S. Configuration structure and messages are obtained from BOM_EXPLOSIONS (the explosion results for models) and CZ_CONFIG_MESSAGES (validation messages produced by Oracle Configurator). Item attributes come from MTL_SYSTEM_ITEMS and the key-flexfield view MTL_SYSTEM_ITEMS_KFV. Sourcing information is available via OE_DROP_SHIP_SOURCES. Utility dependencies include DUAL, DBMS_TRANSACTION (for savepoint or commit control), PLITBLM (the PL/SQL table-to-BLOB helper), and UTL_HTTP, which supports integration calls associated with configuration processing.

Usage Notes

OE_CONFIG_UTIL is typically invoked indirectly. The Order Management Sales Orders window and its configuration-related subprograms call these routines when a user selects, changes, or completes a configuration. Concurrent programs that process or validate configurations also drive the package, as do upgrade scripts, as evidenced by Validate_Configuration_Upg. Custom PL/SQL should call the public entry points — Complete_Config, Cascade_Changes, Change_Configuration, Explode, and the link and delink procedures — rather than manipulating OE_ORDER_LINES directly, because the package encapsulates the required freeze logic, profile checks, and cascading safeguards. The ONT_INCLUDED_ITEM_FREEZE_METHOD and ONT_COPY_MODEL_DFF profile options materially alter runtime behavior and should be reviewed before relying on any of the freeze or included-item procedures.