Search Results create_preconfig_item_ml




Overview
Explore in AI Chat

Overview

APPS.CZ_BOM_CONFIG_EXPLOSIONS_PKG is an Oracle E-Business Suite PL/SQL package that supports Configure-to-Order (CTO) and Assemble-to-Order (ATO) manufacturing flows. Its core business function is to insert mandatory and optional components of a selected configuration into the Oracle Bills of Material tables, effectively exploding a configured model into its constituent inventory items and operation sequences. The package header identifies it as part of the BOM application, and its source file (BOMCZCBB.pls) has been maintained since 1999. A significant functional enhancement was delivered in August 2001 (BUG #1957336) to support "pre-configure BOM" functionality, which introduced the use of the BOM_CTO_ORDER_LINES (BCOL) table and a dedicated negative-number sequence, BOM_CTO_ORDER_LINES_S1, so that generated line identifiers would not converge with existing positive line_id values. The package also depends on the bmobmsc.odf version 115.37 execution layer for proper sequencing.

Key Procedures and Functions

  • INSERT_ROW — The fundamental insertion routine used internally to write configuration component rows into BOM structures. It abstracts the row-level insert logic for the various BOM tables manipulated by the package.
  • BOM_INS_MODEL_AND_MANDATORY — Inserts both mandatory items and the option items selected for a given configuration. Historic modification notes indicate this procedure was changed to inherit operation sequences based on a profile option, making op-seq inheritance configurable per environment.
  • CREATE_PRECONFIG_ITEM_ML — Creates the master-level (multi-lingual) definition of a pre-configured item. This is the procedure referenced by the search term "create_preconfig_item_ml" and is central to the pre-configure BOM capability introduced for CTO/ATO pre-configuration scenarios. It registers the pre-configured item in the items master so that downstream BOM explosions and order line processing can reference it.

Two additional documented procedures are present in the metadata; the total documented procedure/function count is five.

Tables Accessed

The package reads from and writes to the following tables (via APPS synonyms): BOM_CTO_ORDER_LINES and its global temporary counterpart BOM_CTO_ORDER_LINES_GT record configured order line data used in the pre-configure flow. BOM_CTO_ORDER_LINES_S1 supplies the negative sequence values described above. BOM_CTO_SRC_ORGS_B identifies source organizations for CTO processing. BOM_ATO_CONFIGURATIONS stores the selected configuration and its options. BOM_CONFIG_EXPLOSIONS, BOM_EXPLOSIONS, and BOM_EXPLOSION_TEMP hold the exploded component hierarchy resulting from the configuration. BOM_INVENTORY_COMPONENTS_S provides component surrogate keys. BOM_OPERATIONAL_ROUTINGS supplies routing and operation-sequence information inherited during explosion. MTL_SYSTEM_ITEMS is consulted for item validation and master item attributes. DUAL and PLITBLM are supporting references (the latter for the BOM item-layer translation table).

Usage Notes

CZ_BOM_CONFIG_EXPLOSIONS_PKG is invoked primarily by the Oracle Order Management and Bills of Material configuration engines when a user configures a model on an order or in a pre-configure BOM scenario. It is not documented as being referenced by other PL/SQL packages (0 referencing packages per ETRM metadata), indicating it is called from higher-level application logic such as CTO form handlers and concurrent configuration programs rather than exposed as a public API. The ETRM classification is OTHER, so it should be treated as an internal implementation package rather than a formally published API. Customizations that call CREATE_PRECONFIG_ITEM_ML directly should account for the multi-lingual item creation behavior and should avoid conflicts with the negative-number sequence convention applied to BOM_CTO_ORDER_LINES. The package is applicable to both Oracle EBS 12.1.1 and 12.2.2; the source header reflects a 2009 revision, and behavior remains consistent across both releases for the documented procedures.