Search Results generate_model_tree

Overview

APPS.CZ_UPGRADE is a maintenance and migration package within the Oracle E-Business Suite Configure-to-Order (CTO) and Oracle Configurator schema. Its primary business function is to upgrade, validate, and publish configuration model data across releases, ensuring that legacy configuration structures—models, option classes, features, BOM nodes, and expressions—remain consistent when the application is upgraded from earlier versions to Oracle EBS 12.1.1 or 12.2.2.

The package header defines an extensive set of constants that map the internal node identifiers used by the Configurator engine, including node types for products, components, references, connectors, features, options, totals, resources, and BOM variants (model, option class, standard). It also defines explosion node types (undefined, optional, mandatory, connector, instantiable), feature data types (option, integer, float, boolean, string), and expression node types (node, feature property, operator, punctuation). These constants provide the vocabulary the upgrade routines use to interpret and rewrite configuration data.

The presence of a PATH_DELIMITER and a NEVER_EXISTS_ID sentinel constant indicates that the package manipulates hierarchical paths and performs existence checks during data transformation.

Key Procedures and Functions

• AUTO_PUBLISH — Automates the publication of configuration models, writing publication records so that released model definitions become available for runtime configuration. This is the procedure most closely associated with the user's search term.
• PUBLISH_VISION_MODELS — Publishes model definitions specifically prepared for the Vision demonstration database, providing a controlled path for seeding published models.
• VERIFY_RULES — Validates configuration rules and expressions after upgrade, confirming that rule logic remains intact and consistent with the new schema.
• VERIFY_LOGIC — Performs logic-level verification of configuration logic files or expression trees.
• UPGRADE_LOGIC_FILES_TO_18 — Migrates configuration logic files to the version 18 format used by current Configurator releases.
• GENERATE_MODEL_TREE — Builds the hierarchical tree representation of a configuration model.
• GENERATE_COMPONENT_TREE — Builds the component-level tree used during model structure regeneration.
• GENERATE_EXPLOSION — Produces the model explosion structure, applying explosion node type semantics (optional, mandatory, connector, instantiable) to the generated hierarchy.
• CZBOMSORT — Sorts BOM-related configuration nodes as part of the upgrade of model structures.
• CZNATIVEBOMSORT — Performs native BOM sorting, complementing CZBOMSORT for the native BOM representation.
• CZ_POPULATE_LCE_LOAD_SPECS — Populates Lead Competitive Enterprise (LCE) load specification records used when loading configuration data.

Tables Accessed

The package reads and writes a focused set of Configurator tables through APPS synonyms. CZ_DB_SETTINGS and CZ_DB_LOGS provide environment configuration and upgrade logging. CZ_EXPRESSIONS and CZ_EXPRESSION_NODES hold the rule expression trees manipulated by the logic verification and upgrade routines. CZ_COMBO_FEATURES, CZ_CONFIG_ITEMS, CZ_FUNC_COMP_SPECS, CZ_DES_CHART_CELLS, CZ_DES_CHART_FEATURES, and CZ_GRID_CELLS store model structure, feature combinations, and UI layout data. CZ_DEVL_PROJECTS identifies development projects, while CZ_EFFECTIVITY_SETS governs date-effectivity. CZ_LCE_HEADERS and CZ_LCE_LOAD_SPECS support LCE load processing, and CZ_MODEL_PUBLICATIONS records published model versions written by AUTO_PUBLISH and PUBLISH_VISION_MODELS.

Usage Notes

CZ_UPGRADE is an internal upgrade and administration package, not a runtime API. It is typically invoked from concurrent programs, upgrade driver scripts, or AD patch routines during the transition to 12.1.1 or 12.2.2, and from administrative forms used to publish and verify configuration models. Because the package is referenced by zero other packages, it is not a shared dependency; invocation is direct rather than nested. The AUTO_PUBLISH procedure is commonly called when administrators need to republish models in bulk after an upgrade or data correction. The verify procedures should be run after upgrade logic completes to confirm rule integrity, and the generate procedures are used when model trees or explosion structures must be regenerated.