Search Results expl_node_depth




Overview
Explore in AI Chat

Overview

CZ_UIEXPL_HGRID is an APPS-owned, VALID database view within the Oracle Configurator (CZ) product family. It exposes a hierarchical, flattened projection of Oracle Configurator user-interface (UI) definitions together with their associated model-explosion nodes. The name combines "HGRID" (hierarchical grid) with the UI-explosion concept, indicating that the view is designed to present model structure and UI component data in a form suitable for grid-style reporting or downstream programmatic consumption.

For users who encounter the term expl_node_depth in ETRM searches, this view is directly relevant: it surfaces an EXPL_NODE_DEPTH column (aliased from RTDOWNX.NODE_DEPTH) that records the depth of a node within the exploded model reference hierarchy. This makes the view a natural starting point for analyses of configuration model depth, nesting levels, and the relationship between UI presentation structure and underlying model explosion structure in Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a combination of base tables, synonyms, and packaged PL/SQL, per the documented ETRM metadata:

  • CZ_MODEL_REF_EXPLS (SYNONYM) — the core model reference explosion table; joined multiple times (as ROOTXP, DESCXP, and RTDOWNX) to establish root, descendant, and node-depth information.
  • CZ_UI_DEFS (SYNONYM) — the root UI definition source, supplying UI name, description, list sequence, and style.
  • CZ_ALL_UI_COMPONENTS_V (VIEW) — the consolidated UI component view contributing child UI definitions, object types, persistent node identifiers, and parent relationships.
  • CZ_MODEL_UTIL_PVT (PACKAGE) — invoked via GET_PARALLEL_EXPLS, which returns a table of explosion pairs used to correlate enclosing and descendant explosion nodes.
  • CZ_UTILS (PACKAGE) — supporting utility package referenced in the Configurator schema.
  • CZ_EXPL_PAIR_TBL (TYPE) — a collection type used to CAST the pipelined result of CZ_MODEL_UTIL_PVT.GET_PARALLEL_EXPLS, enabling the table-function join in the WHERE clause.

The joins require DELETED_FLAG = '0' on RTDOWNX, RUDF, ROOTXP, and DESCXP, filtering out logically deleted records, and correlate ALLUI.LOCAL_EXPL_NODE_ID to PARLEL.DESCENDANT_EXPL_ID.

Key Columns

Common Use Cases and Queries

Because the view flattens a multi-level model explosion into a single rowset, it supports depth analysis, hierarchy validation, and UI-to-model traceability. A typical query to inspect node depths for a given model is:

  • SELECT ROOT_UI_NAME, MODEL_ID, EXPL_NODE_DEPTH, OBJECT_TYPE, NAME FROM APPS.CZ_UIEXPL_HGRID WHERE MODEL_ID = :model_id ORDER BY EXPL_NODE_DEPTH, TREE_SEQ; — returns UI components ordered by explosion depth for a specific model.
  • SELECT MODEL_ID, MAX(EXPL_NODE_DEPTH) FROM APPS.CZ_UIEXPL_HGRID GROUP BY MODEL_ID; — computes the maximum nesting depth per model, useful for performance or complexity assessments.
  • SELECT ROOT_UI_DEF_ID, CHILD_UI_DEF_ID, EXPL_PARENT_UI_DEF_ID FROM APPS.CZ_UIEXPL_HGRID WHERE VIRTUAL_FLAG = '1'; — isolates virtual nodes within the UI hierarchy.

These queries are commonly used during Configurator diagnostics and upgrade validation in EBS 12.1.1 and 12.2.2, where verifying explosion depth and UI component linkage is essential to confirming model integrity.