Search Results child_model_id




Overview
Explore in AI Chat

Overview

CZ_UIEXPL_HGRID is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CZ (Configurator) product family and is catalogued with a status of VALID. The view exposes a hierarchical, grid-oriented projection of Configurator user-interface definitions together with their associated model reference explosion nodes. Its purpose is to flatten the parent/child relationships that exist between root UI definitions, model reference explosion records, and the constituent UI components into a single, query-friendly result set suitable for reporting, diagnostics, and integration.

The view is particularly relevant to consumers searching for leaf_persistent_node_id. That identifier is surfaced by this view as the alias LEAF_PERSISTENT_NODE_ID, derived from ALLUI.PERSISTENT_NODE_ID in the underlying CZ_ALL_UI_COMPONENTS_V view. It allows callers to correlate a UI component instance with its persistent configuration node without traversing the Configurator PL/SQL APIs directly.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

The view employs an inline TABLE(CAST(...)) construct over the CZ_EXPL_PAIR_TBL collection type, which means the parallel explosion pairs are materialised at runtime rather than persisted. Deletion is filtered through DELETED_FLAG = '0' predicates on the model reference explosion and UI definition records.

Key Columns

  • ROOT_UI_DEF_ID, ROOT_UI_NAME, ROOT_UI_DESCRIPTION, ROOT_UI_STYLE — identity and display attributes of the root UI definition.
  • MODEL_ID — the development project/model associated with the root UI definition.
  • LEAF_EXPL_NODE_ID and LEAF_PERSISTENT_NODE_ID — the explosion node and its persistent counterpart for the leaf component; the latter is the column most commonly sought when tracing runtime configuration persistence.
  • PERSISTENT_NODE_ID, PS_NODE_ID — additional persistent node references exposed directly from the component view.
  • OBJECT_TYPE, OBJECT_TYPE_CODE, OBJECT_ID — classification and identity of the underlying Configurator object.
  • TREE_SEQ — ordering sequence used to reconstruct the hierarchical grid.
  • EXPL_NODE_DEPTH, VIRTUAL_FLAG, NODE_DEPTH-derived values — structural attributes of the explosion node.
  • UICOMP_PARENT_UI_DEF_ID, EXPL_PARENT_UI_DEF_ID — parent linkage columns for reconstructing hierarchy.

Common Use Cases and Queries

The view is typically queried to reconcile UI configuration hierarchy with persistent node storage, for example when investigating why a configured option fails to reappear in a subsequent session.

  • Locating the persistent node for a given leaf explosion node.
  • Reconstructing the full UI tree for a model.
  • Auditing UI definitions across development projects.

Illustrative SQL:

SELECT ROOT_UI_NAME, MODEL_ID, LEAF_EXPL_NODE_ID, LEAF_PERSISTENT_NODE_ID
FROM   APPS.CZ_UIEXPL_HGRID
WHERE  LEAF_PERSISTENT_NODE_ID IS NOT NULL;

SELECT MODEL_ID, ROOT_UI_NAME, NAME AS CHILD_COMPONENT_NAME,
       OBJECT_TYPE, EXPL_NODE_DEPTH
FROM   APPS.CZ_UIEXPL_HGRID
WHERE  ROOT_UI_DEF_ID = :p_ui_def_id
ORDER  BY TREE_SEQ;

Because the view invokes a PL/SQL package during execution, queries should be restricted with selective predicates to avoid performance degradation on large Configurator models.