Search Results root_ui_description




Overview
Explore in AI Chat

Overview

CZ_EXPLODED_UI_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the CZ (Configurator) product family. Its purpose is to present a flattened, hierarchical representation of every UI definition (UI model) and its child UI references — i.e., the exploded reference tree beneath each root UI model. Rather than requiring a caller to walk the recursive containment relationships manually, the view precomputes and exposes one row per referencing/exploded node, giving report writers and integrators a single queryable source for the full dependency structure of Configurator UI models.

In the context of a search for persistent_ui_def_id, this view is significant because it surfaces that column directly at the top level (as PERSISTENT_UI_DEF_ID), together with the related leaf-level identifier LEAF_PERSISTENT_NODE_ID. Together these columns allow consumers to trace the persistent identity of a UI definition as well as the persistent node that terminates a given exploded branch. The view therefore bridges transient runtime model references and their persisted counterparts.

Underlying Base Objects

The documented base objects referenced by the view are CZ_UI_DEFS (a synonym, ultimately backed by the CZ_UI_DEFS table), the PL/SQL package CZ_MODEL_UTIL_PVT, and the collection type CZ_UIREFS_INMODEL_TBL_TYPE.

The query joins the root UI record from CZ_UI_DEFS (aliased RUDF) against a pipelined/table function result produced by CZ_MODEL_UTIL_PVT.GET_UI_REFS_UNDER_MODEL(RUDF.UI_DEF_ID, TO_NUMBER(NULL)), cast to the collection type CZ_UIREFS_INMODEL_TBL_TYPE (aliased UIXPL). In other words, for each root UI model the function dynamically computes the set of UI references beneath it, and the view projects that set alongside the root definition attributes. The WHERE clause restricts output to records where DELETED_FLAG = '0' and MASTER_TEMPLATE_FLAG = '0', so deleted records and master templates are excluded from the exploded result.

Key Columns

Common Use Cases and Queries

Typical scenarios include generating model-dependency reports, auditing persistent versus transient UI references, and feeding downstream integration that needs a denormalized hierarchy. A representative query locates a UI model by its persistent identifier and enumerates its exploded children:

  • Find a root model by persistent id: SELECT ROOT_UI_DEF_ID, ROOT_UI_NAME FROM CZ_EXPLODED_UI_V WHERE PERSISTENT_UI_DEF_ID = :p_id;
  • List exploded nodes for a named root, ordered by depth: SELECT ROOT_UI_NAME, CHILD_UI_DEF_ID, EXPL_NODE_DEPTH, VIRTUAL_FLAG FROM CZ_EXPLODED_UI_V WHERE ROOT_UI_NAME = :name ORDER BY EXPL_NODE_DEPTH;
  • Trace leaf persistence: SELECT ROOT_UI_DEF_ID, LEAF_EXPL_NODE_ID, LEAF_PERSISTENT_NODE_ID FROM CZ_EXPLODED_UI_V;
  • Identify virtual references only: SELECT * FROM CZ_EXPLODED_UI_V WHERE VIRTUAL_FLAG = '1';

Because the view filters out deleted and master-template records, it is a ready-made source for operational reporting without additional exclusion logic.