Results for “parent_persistent_node_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_UI_PAGE_ELEMENTS is a Configurator (CZ) module table in the Oracle E-Business Suite database, owned by the CZ schema. It stores the individual UI page components — that is, the discrete elements that make up a Configurator user-interface page definition. Each row describes one element placed on a page within a UI definition, capturing its placement, parent/child relationships, control template binding, sequencing, and lifecycle flags. In EBS 12.1.1 and 12.2.2 the table is documented as VALID with a physical schema of 26 columns.

From a data-modeling perspective, the ETRM relationship metadata classifies this object as satellite-leaning. This is a heuristic suggestion: the table carries descriptive and structural attributes (element type, name, sequence, flags) that hang off the identifying keys of a UI definition and page, which behave like parent hub/link keys. The primary key CZ_UI_PAGE_ELEMENTS_PK is a composite of UI_DEF_ID, PAGE_ID, and ELEMENT_ID, confirming that an element is only meaningful within the context of its owning UI definition and page.

Key Information Stored

The composite primary key consists of UI_DEF_ID (the owning UI definition), PAGE_ID (the page within that definition), and ELEMENT_ID (the element itself). This composite is also the unique business-key candidate. Among the most significant non-key columns:

• PERSISTENT_NODE_ID — the stable node identity for the element across UI definition versions.
• PARENT_PERSISTENT_NODE_ID and PARENT_ELEMENT_ID — establish the parent/child hierarchy of elements.
• REGION_PERSISTENT_NODE_ID and PAGEBASE_PERSISTENT_NODE_ID — anchor the element to its region and page base node.
• CTRL_TEMPLATE_ID plus CTRL_TEMPLATE_UI_DEF_ID — the control template binding (foreign key to CZ_UI_TEMPLATES).
• ELEMENT_TYPE, NAME, SEQ_NBR — element classification, display name, and ordering.
• ELEMENT_SIGNATURE_ID and MODEL_REF_EXPL_ID — signature and model-reference linkage.
• TARGET_PAGE_UI_DEF_ID and TARGET_PAGE_ID — navigation targets for the element.
• BASE_PAGE_FLAG, INSTANTIABLE_FLAG, SUPPRESS_REFRESH_FLAG, DELETED_FLAG — behavioral and lifecycle flags.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on inspecting or reconstructing Configurator UI definitions: enumerating the elements on a page, walking the parent/child element tree, or finding which elements bind a given control template. A reporting query might list elements for a UI definition ordered by sequence:

• SELECT ELEMENT_ID, NAME, ELEMENT_TYPE, SEQ_NBR FROM CZ.CZ_UI_PAGE_ELEMENTS WHERE UI_DEF_ID = :p_def AND PAGE_ID = :p_page AND NVL(DELETED_FLAG,'N') = 'N' ORDER BY SEQ_NBR;
• Join to CZ_UI_TEMPLATES on CTRL_TEMPLATE_ID = TEMPLATE_ID (and CTRL_TEMPLATE_UI_DEF_ID) to resolve the control template used by each element.
• Filter on INSTANTIABLE_FLAG or BASE_PAGE_FLAG to isolate effective versus template/base elements.

Active elements are generally those where DELETED_FLAG is null or 'N'; stale or removed elements are retained with DELETED_FLAG set.

Related Objects

The dominant relationship is to the control template table, which this table references:

• CZ_UI_TEMPLATES — referenced via CZ_UI_PAGE_ELEMENTS.CTRL_TEMPLATE_ID (and CTRL_TEMPLATE_UI_DEF_ID).

By its columns and keys, CZ_UI_PAGE_ELEMENTS also relates to the UI definition, page, region, and node structures within the CZ Configurator schema (UI_DEF_ID, PAGE_ID, PERSISTENT_NODE_ID, REGION_PERSISTENT_NODE_ID), and is typically queried alongside the CZ UI definition and template objects. These associated pages, regions, and node tables form the broader Configurator UI metadata model in which this satellite-leaning table participates.