Search Results cz_all_ui_components_v




Overview
Explore in AI Chat

Overview

CZ_ALL_UI_COMPONENTS_V is an APPS-owned database view within the Oracle E-Business Suite Configurator (CZ) product family. It presents a consolidated, hierarchical representation of the user interface components that make up Configurator models, including UI definitions, pages, page sets, references, and their associated model reference explosion nodes. The view is designed to flatten the relationships between UI metadata and the underlying model structure so that UI elements can be traversed and reported alongside their parent model nodes.

Because Configurator runtime behavior depends on the linkage between UI definitions and model reference explosion records, this view plays a critical role in both reporting and integration. It is typically consumed during diagnostics, migration, and custom reporting where developers and administrators need to interrogate how a given Configurator model maps its UI tree to the underlying persistent nodes. The view abstracts several base tables into a uniform shape with columns such as OBJECT_TYPE, PARENT_OBJECT_TYPE, and TREE_SEQ, making it suitable for driving recursive or tree-walking queries.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, the view is defined over the following base objects, all resolved through synonyms in the APPS schema unless otherwise noted:

  • CZ_UI_DEFS (synonym) – the core UI definitions used to build Configurator screens.
  • CZ_MODEL_REF_EXPLS (synonym) – model reference explosion records that connect a model to its exploded node structure.
  • CZ_PS_NODES (synonym) – persistent node records representing the model hierarchy.
  • CZ_UICOMPONENTS_LKV (view) – the lookup view supplying UI component types such as list-based value sets.
  • CZ_UI_PAGES (synonym) – page definitions belonging to UI definitions.
  • CZ_UI_PAGE_SETS (synonym) – groupings of UI pages.
  • CZ_UI_REFS (synonym) – UI reference records tying definitions together.
  • CZ_UTILS (package) – a utility package used within the SQL text, specifically CZ_UTILS.CONV_NUM, to convert UI style values into numeric object type codes.

The SQL text is constructed as a series of UNION ALL branches, each producing rows for a particular component type (UDF, list components, PAG, and so on). Each branch joins CZ_UI_DEFS to CZ_MODEL_REF_EXPLS on the development project ID, filters on DELETED_FLAG = '0' and MASTER_TEMPLATE_FLAG = '0' where applicable, and joins to CZ_PS_NODES to obtain the persistent node identifier.

Key Columns

The view exposes a stable set of columns that describe each UI component in relation to its parent and its model context:

  • LOCAL_UI_DEF_ID – the UI definition identifier local to the component.
  • DEVL_PROJECT_ID – the development project (model) identifier.
  • OBJECT_TYPE / OBJECT_TYPE_CODE – the type of the component (for example 'UDF', 'PAG', or a component list value), with a numeric code derived via CZ_UTILS.CONV_NUM.
  • OBJECT_ID – the identifier of the component itself.
  • PARENT_OBJECT_TYPE / PARENT_OBJECT_ID / PARENT_UI_DEF_ID – the parent linkage, used to reconstruct the hierarchy.
  • TREE_SEQ – ordering sequence within the UI tree.
  • LOCAL_EXPL_NODE_ID / LEAF_EXPL_NODE_ID – both mapped to CZ_MODEL_REF_EXPLS.MODEL_REF_EXPL_ID, identifying the associated model reference explosion node. The LEAF_EXPL_NODE_ID is the column most relevant to leaf-node traversal queries.
  • PS_NODE_ID / PERSISTENT_NODE_ID – the persistent node identity from CZ_PS_NODES, linking the UI component to runtime model storage.
  • NAME / DESCRIPTION – descriptive attributes, either from CZ_UI_DEFS or, for list components, from CZ_UICOMPONENTS_LKV.
  • ROOT_UI_MARKER – indicates whether the row represents a root UI definition.

Common Use Cases and Queries

The view is frequently used to trace how UI components map to model reference explosion nodes. A typical query retrieving leaf node associations is:

  • SELECT LOCAL_UI_DEF_ID, OBJECT_TYPE, OBJECT_ID, LEAF_EXPL_NODE_ID, NAME FROM CZ_ALL_UI_COMPONENTS_V WHERE DEVL_PROJECT_ID = :project_id ORDER BY TREE_SEQ;
  • SELECT OBJECT_TYPE, COUNT(*) FROM CZ_ALL_UI_COMPONENTS_V GROUP BY OBJECT_TYPE; to summarize component composition.
  • Joining back to CZ_PS_NODES or CZ_MODEL_REF_EXPLS on PERSISTENT_NODE_ID or LEAF_EXPL_NODE_ID to reconcile UI metadata with model storage.

Because the view already filters out deleted records and master templates, it is a convenient foundation for custom Configurator reporting, upgrade validation, and troubleshooting scenarios where the relationship between a UI definition and its exploded leaf node must be confirmed.