Search Results root_ui_list_seq




Overview
Explore in AI Chat

Overview

The view APPS.CZ_EXPLODED_UI_V is a dictionary-managed reporting object within the Oracle E-Business Suite (EBS) configuration and setup framework, exposed under the APPS schema in both 12.1.1 and 12.2.2 environments. It presents a fully exploded, hierarchical representation of user interface (UI) definition nodes and the model references nested beneath them. Unlike a conventional relational join across fixed tables, this view is constructed using a correlated table function invocation that dynamically materializes the reference tree for every root UI definition. As a result, the view exposes the complete expansion of each UI model — root nodes, child nodes, depth indicators, and leaf-level navigation targets — in a single flattened relational result set suitable for SQL-based reporting, diagnostics, and integration extracts. The view is intended for read-only consumption and is not a transactional entity.

Underlying Base Objects

The view is defined over three documented base objects:

The join is executed through a TABLE ( CAST ( ... ) ) construct, meaning the view performs a nested expansion per qualifying root row. The driving query filters on DELETED_FLAG = '0' and MASTER_TEMPLATE_FLAG = '0', so soft-deleted definitions and master templates are excluded from the result set.

Key Columns

Common Use Cases and Queries

Typical uses include auditing UI hierarchy depth, tracing which child models hang beneath a given root definition, and reconciling TREE_SEQ ordering values across configurations.

List root UI definitions by sequence:

  • SELECT DISTINCT root_ui_def_id, root_ui_name, root_ui_list_seq FROM apps.cz_exploded_ui_v ORDER BY root_ui_list_seq;

Inspect exploded children and depth for one root:

  • SELECT root_ui_name, child_ui_def_id, child_model_id, expl_node_depth, virtual_flag FROM apps.cz_exploded_ui_v WHERE root_ui_def_id = :p_id ORDER BY expl_node_depth, root_ui_list_seq;

Trace leaf navigation targets:

  • SELECT root_ui_name, leaf_expl_node_id, leaf_persistent_node_id, model_reference_depth FROM apps.cz_exploded_ui_v WHERE leaf_expl_node_id IS NOT NULL;

Because the view invokes a PL/SQL table function per root row, queries should be constrained where possible to limit expansion cost. The root_ui_list_seq column is commonly used as the primary sort key when presenting UI definitions in their intended order.