Search Results clone_it
Overview
APPS.CZ_UI_GENERATOR is a PL/SQL package in the Oracle E-Business Suite Oracle Configurator (CZ) schema that produces runtime user interface definitions from configured product models. Its principal responsibility is the generation and regeneration of the HTML user interface presented to end users during a configuration session. When a model is published for runtime use, this package translates the model's node hierarchy and expression structure into a persisted UI definition that the Configurator runtime engine renders in the browser.
Within ETRM, the package is classified under the API classification OTHER and is owned by APPS. The 12.2.2 metadata records six documented procedures and a substantial set of referenced tables that hold model structure, nodes, properties, expressions, item master data, and localized text. The header of the package shows an AUTHID CURRENT_USER declaration and an associated revision string dating to the 11i/12.0 era, indicating the object has been stable across the 12.1.1 and 12.2.2 releases with minimal structural change. The package also maintains internal associative array types and public variables such as UIS, MUID, InterfaceName, MODE_REFRESH, and the NO_FLAG / YES_FLAG constants used to interpret option flags.
Key Procedures and Functions
The package exposes two generation entry points and a set of maintenance routines:
- CREATEUI — the full generation procedure. It accepts a product/model identifier, returns the new UI definition identifier and a run identifier, and additionally accepts style, frame allocation, width, height, node display, label usage, look-and-feel, BOM-per-page, and wizard style options controlling the generated interface.
- CREATE_UI — an alternate overload of the generation procedure that takes the same style and layout options but does not return the created UI definition and run identifiers. It is used when the caller does not need to capture the resulting IDs.
- REFRESHUI — regenerates an existing UI definition in place, taking the UI definition identifier as an IN OUT parameter and returning the run identifier for the regeneration.
- REFRESH_UI — a simpler refresh variant that takes the UI definition identifier and performs regeneration without returning a run identifier.
- CLONE_IT — copies an existing UI definition to a new definition identifier, scoped to a development project, with a flag allowing replacement of the target definition.
- UPDATE_LABELS — adjusts the label display setting for an individual UI node, taking the node identifier and a label usage flag.
Tables Accessed
The package operates against a broad set of CZ tables accessed through APPS synonyms:
- Model and node structure: CZ_PS_NODES, CZ_PS_PROP_VALS, CZ_PROPERTIES, CZ_EXPRESSION_NODES, CZ_MODEL_REF_EXPLS — the source hierarchy and expression graph transformed into UI nodes.
- Item and property data: CZ_ITEM_MASTERS, CZ_ITEM_TYPE_PROPERTIES, CZ_ITEM_PROPERTY_VALUES — item definitions and property values surfaced in the generated interface.
- Text and localization: CZ_INTL_TEXTS, CZ_INTL_TEXTS_S, CZ_LOCALIZED_TEXTS — multilingual node labels and descriptions.
- Functional component specifications: CZ_FUNC_COMP_SPECS — component specifications mapped into the UI.
- Infrastructure and project data: CZ_DB_LOGS, CZ_DB_SETTINGS, CZ_DEVL_PROJECTS — logging, generator settings, and the development project scope used by cloning.
Usage Notes
CZ_UI_GENERATOR is invoked primarily from the Oracle Configurator Developer user interface when publishing or refreshing a model, and from the runtime infrastructure that materializes UI definitions for a configuration session. The CREATEUI and CREATE_UI procedures are the standard generation calls; REFRESHUI and REFRESH_UI are used when an existing definition must be regenerated after model changes. CLONE_IT supports copying a published definition into a development project for further editing. Because it is an internal Configurator component rather than a public interface, direct invocation from custom forms or concurrent programs is uncommon and should be approached with care; the documented metadata lists two other packages that reference it. Customizations should rely on supported Configurator APIs and preserve the option flag conventions encoded by NO_FLAG and YES_FLAG.