Search Results bom_ins_model_and_mandatory

Overview

The APPS.CZ_BOM_CONFIG_EXPLOSIONS_PKG package is a configuration management utility within Oracle E-Business Suite that supports the Bill of Materials (BOM) configuration explosion process for Configure-to-Order (CTO) environments. Its primary responsibility is to evaluate and expand configured bills of material for ordered assemblies, producing the derived component and routing structures needed for downstream manufacturing, costing, and order fulfillment activities. The package resides in the APPS schema and is classified as an "OTHER" API, indicating it is designed primarily for internal use by Oracle's CTO and BOM processing rather than as a public integration interface. It interacts closely with the CTO configuration model, including the CTO_CONFIG_BOM_PK dependency, and operates against live order line data to determine which components and operations must be generated for a configured item. In Oracle EBS 12.1.1 and 12.2.2 the package remains VALID, and it is documented in the ETRM repository as a direct dependency of other BOM configuration logic, though it is referenced by zero other packages, meaning it is normally invoked directly by the configuration explosion engine rather than through an inter-package hierarchy.

Key Procedures and Functions

The documented program units include the following:

• INSERT_ROW — Inserts a new record into the appropriate configuration explosion staging or result structure. It is used to persist individual explosion results as the package walks the configuration hierarchy.
• BOM_INS_MODEL_AND_MANDATORY — Handles insertion of the configured model item and its mandatory components. This routine ensures that model-level and mandatory option classes are represented in the exploded structure, which is essential to producing a complete and valid configuration.
• CREATE_PRECONFIG_ITEM_ML — Creates multilingual (ML) descriptive data for preconfigured items, enabling the configured item description to be stored and translated across supported languages. The "_ML" suffix reflects interaction with the MTL_SYSTEM_ITEMS_TL style translation structures.

Additional documented procedures bring the total to five; the remaining units perform supporting explosion and configuration validation work. Parameter lists are not enumerated in the metadata and are not reproduced here.

Tables Accessed

The package reads and writes a broad set of BOM and order management tables through APPS synonyms:

• BOM_CTO_ORDER_LINES, BOM_CTO_ORDER_LINES_GT, and BOM_CTO_ORDER_LINES_S1 — Source order line data for the configured item and its options, including global temporary and sequence-backed staging variants used during explosion.
• BOM_ATO_CONFIGURATIONS — Assemble-to-Order configuration definitions that map selections to components.
• BOM_CONFIG_EXPLOSIONS, BOM_EXPLOSIONS, and BOM_EXPLOSION_TEMP — Core and temporary explosion result structures where expanded configuration output is accumulated.
• BOM_INVENTORY_COMPONENTS_S — Component definitions used to build the exploded bill.
• BOM_OPERATIONAL_ROUTINGS — Routing information associated with the configured assembly.
• BOM_CTO_SRC_ORGS_B — Source organization definitions for multi-organization explosion.
• MTL_SYSTEM_ITEMS — Item master validation and description data.
• DUAL and PLITBLM — Utility references for single-row queries and PL/SQL table handling.

Usage Notes

CZ_BOM_CONFIG_EXPLOSIONS_PKG is typically invoked during CTO order processing, when a configured item is entered or booked and the system must explode its configuration into concrete components and operations. It supports the AutoCreate configuration and BOM explosion flows and may be called from Oracle Configurator integration points, order management concurrent programs, or custom CTO extensions. Because it is an internal API, direct calls from custom code should be limited and tested carefully against patches, as its signature is not guaranteed by Oracle as a public interface. In both 12.1.1 and 12.2.2, the OAF-based and forms-based order entry paths rely on this package indirectly through the configuration explosion framework.