Search Results cz_model_ref_expls_s

Overview

APPS.CZ_UPGRADE is a VALID PL/SQL package body within the Oracle E-Business Suite (EBS) configuration management infrastructure, part of the CZ (Oracle Configurator / ETRM) schema. Its business purpose is to manage the upgrade, verification, and publication lifecycle of configuration models stored in the Configurator repository. The package provides the utility routines that migrate legacy logic files to newer format revisions, verify the structural and logical integrity of rules and expressions, generate model and component hierarchy trees, and publish configuration models into the runtime environment. In effect, CZ_UPGRADE acts as the maintenance and migration layer that ensures configuration models authored in an earlier release remain valid and deployable after an EBS upgrade to 12.1.1 or 12.2.2. The package is documented with an API classification of OTHER and is not referenced by any other database object, indicating it is an entry-point package typically invoked directly by concurrent programs, upgrade scripts, or administrative forms rather than being called from dependent application code.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, each addressing a discrete maintenance concern:

• VERIFY_RULES and VERIFY_LOGIC — validate rule definitions and generated logic files, confirming that model logic is internally consistent and compiles correctly.
• AUTO_PUBLISH — automates publication of models into the runtime repository without manual intervention.
• CZBOMSORT and CZNATIVEBOMSORT — perform bill-of-material ordering of configuration components, including the native (configurator-native) sort variant.
• GENERATE_MODEL_TREE — builds the hierarchical model tree structure for a configuration model.
• GENERATE_COMPONENT_TREE — constructs the component-level tree representation used for navigation and UI rendering.
• GENERATE_EXPLOSION — generates the configuration explosion, expanding model structures into their constituent items.
• CZ_POPULATE_LCE_LOAD_SPECS — populates load specification records in the LCE (logic compilation/execution) subsystem.
• UPGRADE_LOGIC_FILES_TO_18 — migrates logic files to revision 18 format, a key upgrade routine for older model logic.
• PUBLISH_VISION_MODELS — publishes models associated with the Vision demonstration/demo environment.

No parameter signatures are documented; each routine should be treated as an administrative utility invoked with context supplied by the calling program unit.

Tables Accessed

CZ_UPGRADE reads and writes through APPS synonyms across the core Configurator data model. Model definition and publication metadata reside in CZ_MODEL_PUBLICATIONS, CZ_MODEL_PUBLICATIONS_S, CZ_MODEL_REF_EXPLS, and CZ_MODEL_REF_EXPLS_S (the sequence-backed variants). Rule and logic structures are held in CZ_RULES, CZ_RULE_FOLDERS, CZ_RULE_FOLDERS_S, CZ_EXPRESSIONS, and CZ_EXPRESSION_NODES. Component and structure data is stored in CZ_CONFIG_ITEMS, CZ_COMBO_FEATURES, CZ_FUNC_COMP_SPECS, CZ_GRID_CELLS, CZ_DES_CHART_CELLS, CZ_DES_CHART_FEATURES, CZ_PS_NODES, CZ_PS_NODES_S, CZ_EFFECTIVITY_SETS, and CZ_DEVL_PROJECTS. Load and header information for logic compilation is kept in CZ_LCE_HEADERS and CZ_LCE_LOAD_SPECS. Diagnostic and configuration settings are logged to CZ_DB_LOGS and CZ_DB_SETTINGS. Additional lookups reference FND_APPLICATION and FND_LANGUAGES for application registration and language handling, with auxiliary use of DUAL and PLITBLM.

Usage Notes

Because CZ_UPGRADE is not referenced by any other database object, it is characteristically invoked as a top-level entry point. Typical invocation paths include Oracle Configurator administrative forms and concurrent programs executed during an EBS upgrade or patching cycle, where UPGRADE_LOGIC_FILES_TO_18 and the VERIFY routines are run to migrate and validate pre-existing model logic. The AUTO_PUBLISH and PUBLISH_VISION_MODELS routines support controlled republication after migration, while the tree-generation and explosion routines rebuild derived structures required for runtime navigation. Custom code should invoke these procedures only under the guidance of Oracle ETRM upgrade documentation, since direct manipulation of the underlying CZ tables without the accompanying logic regeneration can leave models in an inconsistent published state.