Search Results root_ui_description




Overview
Explore in AI Chat

Overview

APPS.CZ_EXPLODED_UI_V is an Oracle E-Business Suite configuration and integration view belonging to the ETRM (Enterprise Transaction and Repository Model) component of the Oracle Applications technology stack. It exposes a flattened, hierarchical representation of the user interface definitions stored within the CZ_UI_DEFS repository, presenting each UI definition together with the set of UI references and model dependencies nested beneath it. The view derives its name from the fact that it "explodes" a root UI definition into its constituent reference tree, returning one row for every node discovered by traversing the references under the root model. Because the view surfaces the DESC_TEXT column under the alias ROOT_UI_DESCRIPTION, it is frequently located by users searching for "root_ui_description" while identifying the descriptive text associated with a root UI definition.

The view is used primarily for reporting, diagnostics, and integration work involving the EBS user interface metadata model. Rather than forcing consumers to invoke the underlying PL/SQL utility package directly, the view presents the exploded result set in relational form, suitable for SQL joins, ad-hoc queries, and downstream extracts.

Underlying Base Objects

The view is defined over three documented objects, all owned by APPS:

  • CZ_UI_DEFS (referenced through a synonym) — the master repository of UI definitions. The view selects root-level definitions from this source, applying filters for DELETED_FLAG = '0' and MASTER_TEMPLATE_FLAG = '0', which restrict the result to active, non-template UI definitions.
  • CZ_MODEL_UTIL_PVT (PL/SQL package) — the utility package supplying the GET_UI_REFS_UNDER_MODEL pipelined function. This function accepts a UI definition identifier and performs the recursive traversal that yields the reference rows.
  • CZ_UIREFS_INMODEL_TBL_TYPE (collection type) — the nested table type whose rows are cast and expanded in the FROM clause via the TABLE(CAST(...)) construct, producing the exploded rows.

Because the view invokes a pipelined PL/SQL function, its performance characteristics depend on the efficiency of GET_UI_REFS_UNDER_MODEL and the depth of the underlying reference hierarchy.

Key Columns

The columns exposed by the view fall into two logical groups. The first group originates from the root UI definition row in CZ_UI_DEFS:

The second group originates from the exploded reference rows returned by the pipelined function:

Common Use Cases and Queries

A typical diagnostic query lists the exploded reference tree for a named root UI definition, joining description and depth information:

  • Inventory of root UIs with descriptions: SELECT DISTINCT root_ui_def_id, root_ui_name, root_ui_description FROM cz_exploded_ui_v ORDER BY root_ui_name;
  • Locate a definition by description: SELECT root_ui_def_id, root_ui_name FROM cz_exploded_ui_v WHERE root_ui_description LIKE '%Order%';
  • Reference depth analysis: SELECT root_ui_name, child_ui_def_id, expl_node_depth FROM cz_exploded_ui_v WHERE root_ui_def_id = :ui_def_id ORDER BY expl_node_depth;
  • Find parents of a referenced node: SELECT root_ui_name, parent_ui_def_id, referring_node_id FROM cz_exploded_ui_v WHERE child_ui_def_id = :child_id;

These patterns support impact analysis before changing or migrating UI definitions, tracing the influence of master templates, and building integration extracts that require the fully expanded reference topology rather than the top-level definition alone.