Search Results cz_ui_components_v




Overview
Explore in AI Chat

Overview

CZ_UI_COMPONENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CZ (Configurator) product family. Its purpose is to expose a flattened, hierarchical representation of the user interface elements that make up Configurator user interface definitions. The view consolidates UI definition headers, model reference explosion nodes, persistent structure nodes, page sets, pages, UI references, and lookup-driven component types into a single queryable result set.

Because Configurator is metadata-driven, the UI artifacts that drive runtime configuration screens are stored across several normalized tables. CZ_UI_COMPONENTS_V abstracts that normalization, presenting each UI element as a row with a consistent set of identity, parentage, ordering, and descriptive columns. This makes it suitable for diagnostic queries, migration analysis, custom reporting, and integration extracts where a direct join across the base tables would be impractical. The view is defined in the ETRM repository as VALID in both EBS 12.1.1 and 12.2.2.

For users searching on page_set_id, the view is notable because it explicitly projects a PAGE_SET_ID column. In the visible portion of the view text, PAGE_SET_ID is populated as TO_NUMBER(NULL) in the branches covering UI definitions and list-type components, with the actual page set values supplied by the branch that joins CZ_UI_PAGE_SETS and CZ_UI_PAGES. This design preserves a uniform column list across all UNION ALL branches while allowing page set context to appear only for page-level rows.

Underlying Base Objects

The documented base objects referenced by CZ_UI_COMPONENTS_V are:

Several of these appear in the metadata as synonyms rather than base tables, reflecting the standard APPS synonym layer. The view applies consistent deletion filtering (DELETED_FLAG = '0') and restricts root nodes via PARENT_EXPL_NODE_ID IS NULL and MASTER_TEMPLATE_FLAG = '0'.

Key Columns

  • LOCAL_UI_DEF_ID / OBJECT_ID — the UI definition identifier associated with the row.
  • DEV_PROJECT_ID / PS_NODE_ID — the development project and persistent structure node context.
  • OBJECT_TYPE — discriminator indicating the row category, such as 'UDF' for UI definitions or a lookup DATA_VALUE ending in 'LIST' for list components.
  • OBJECT_TYPE_CODE — numeric code derived from UI_STYLE via CZ_UTILS.CONV_NUM.
  • PARENT_OBJECT_TYPE / PARENT_OBJECT_ID / PARENT_UI_DEF_ID — parentage columns used to reconstruct hierarchy.
  • TREE_SEQ — ordering sequence within the tree.
  • LOCAL_EXPL_NODE_ID / LEAF_EXPL_NODE_ID — model reference explosion node identifiers.
  • PERSISTENT_NODE_ID — stable node identifier from CZ_PS_NODES.
  • ROOT_UI_MARKER — marks root UI definitions.
  • PAGE_SET_ID — the page set identifier, populated for page-level rows and NULL elsewhere.
  • NAME / DESCRIPTION — display labels, taken from UI_DEFS or from lookup label and description columns.

Common Use Cases and Queries

Typical scenarios include auditing which UI definitions belong to a given development project, tracing page set membership, and extracting component inventories for migration or documentation. A representative query filters on page set context:

  • SELECT LOCAL_UI_DEF_ID, OBJECT_TYPE, NAME, PAGE_SET_ID FROM CZ_UI_COMPONENTS_V WHERE PAGE_SET_ID = :page_set_id;
  • SELECT OBJECT_TYPE, COUNT(*) FROM CZ_UI_COMPONENTS_V GROUP BY OBJECT_TYPE;
  • SELECT DEV_PROJECT_ID, NAME, TREE_SEQ FROM CZ_UI_COMPONENTS_V WHERE ROOT_UI_MARKER IS NOT NULL ORDER BY DEV_PROJECT_ID, TREE_SEQ;

Because PAGE_SET_ID is NULL for non-page rows, queries that filter on it should account for that behavior. All access should be performed through the APPS schema.