Search Results cz_ui_page_sets_pk




Overview
Explore in AI Chat

Overview

The CZ_UI_PAGE_SETS table is a Configurator (CZ) module data object in Oracle EBS 12.1.1 and 12.2.2 that defines a UI menu or page flow within the Configurator user interface framework. It stores the metadata that governs how Configurator pages are grouped, navigated, and rendered for end users configuring complex products. The table is owned by the CZ schema and is documented as a VALID object within the ETRM 12.2.2 physical schema, where it exposes 16 columns.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests the object is best modeled as a standalone entity rather than as a hub, link, or satellite within a Data Vault architecture, since the documented relationship data does not reveal dependent foreign key paths into other tables. Analysts designing warehouse or reporting layers should therefore treat CZ_UI_PAGE_SETS as an independent dimension or reference table rather than as a bridge between two business entities.

Key Information Stored

The table's surrogate primary key is defined by the CZ_UI_PAGE_SETS_PK constraint, composed of the composite columns PAGE_SET_ID and UI_DEF_ID. This composite key is also the documented unique index and business-key candidate, meaning a given page set is uniquely identified within the context of a specific UI definition.

  • PAGE_SET_ID — identifies the page set; part of the composite primary key.
  • UI_DEF_ID — identifies the parent UI definition; part of the composite primary key.
  • PAGE_SET_TYPE — categorizes the page set (for example, menu versus page flow).
  • NAME — the user-facing label for the page set.
  • DESCRIPTION — free-text explanation of the page set's purpose.
  • SUPPRESS_REFRESH_FLAG — controls whether UI refresh behavior is suppressed.
  • TRAIN_JRAD_DOC — relates to training documentation references for the page set.
  • DELETED_FLAG — soft-delete indicator for logical removal of the record.
  • SIDE_NAV_WIDTH — controls the rendered width of the side navigation panel.
  • PERSISTENT_NODE_ID — identifies a node that persists across page transitions.
  • PAGEBASE_EXPL_NODE_ID — identifies the exploration node used as the page base.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying all page sets defined for a given UI definition, auditing soft-deleted page sets, and analyzing page set types across configurations. A representative query retrieves active page sets for a UI definition:

  • SELECT PAGE_SET_ID, UI_DEF_ID, NAME, PAGE_SET_TYPE FROM CZ_UI_PAGE_SETS WHERE UI_DEF_ID = :ui_def_id AND NVL(DELETED_FLAG,'N') = 'N';
  • SELECT PAGE_SET_TYPE, COUNT(*) FROM CZ_UI_PAGE_SETS WHERE NVL(DELETED_FLAG,'N') = 'N' GROUP BY PAGE_SET_TYPE;
  • SELECT p.NAME, p.SIDE_NAV_WIDTH FROM CZ_UI_PAGE_SETS p WHERE p.PERSISTENT_NODE_ID IS NOT NULL;

These patterns support impact analysis before UI configuration changes, migration validation between environments, and audit reporting on who created or last modified each page set.

Related Objects

The table participates in the broader Configurator UI model. Based on the composite primary key and Configurator conventions, the most significant related objects include:

  • CZ_UI_DEFINITIONS — joined on UI_DEF_ID; provides the parent UI definition context.
  • CZ_UI_PAGE_SET_NODES — child table linking page sets to their ordered nodes.
  • CZ_UI_NODES — referenced via PERSISTENT_NODE_ID and PAGEBASE_EXPL_NODE_ID.
  • CZ_UI_DEFINITIONS_VL / _TL — descriptive translations of the parent UI definitions.
  • CZ_UI_PAGE_SETS_TL — translated NAME and DESCRIPTION values, where implemented.
  • CZ_CONFIG_HDRS — configuration headers that ultimately drive the rendered UI experience.

Because the Data Vault classification is standalone, analysts should verify actual referential integrity at the instance level, as the documented FK metadata does not expose explicit constraint paths beyond the primary key.