Search Results persistent_node_id




Overview
Explore in AI Chat

Overview

CZ_UICOMPONENT_HGRID_V is a Configurator (CZ) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a hierarchical, grid-oriented projection of Configurator user interface (UI) component definitions, flattening the recursive relationships between UI definitions, model reference explosion nodes, and persistent nodes into a single queryable structure. The view's name reflects its purpose: it presents UI components in a hierarchical grid ("HGRID") suitable for reporting, integration, and downstream UI rendering logic.

The view is significant because it surfaces the PERSISTENT_NODE_ID attribute. Users searching for this term are typically tracing how Configurator assigns a persistent identifier to UI nodes so that component selections and configurations survive across sessions, model instantiations, and order capture. The view bridges the transient runtime node model (CZ_PS_NODES) and the persistent configuration store by carrying both the volatile PS_NODE_ID and the stable PERSISTENT_NODE_ID through its column list.

Underlying Base Objects

The documented base objects underlying this view are:

  • CZ_UI_COMPONENTS_V (VIEW) — the primary source of UI component rows (aliased ALLUI), supplying local/parent UI definition IDs, object type, object ID, name, description, tree sequence, and PERSISTENT_NODE_ID.
  • CZ_PS_NODES (SYNONYM) — the persistent node store, joined via PS_NODE_ID to resolve page names and to return PERSISTENT_NODE_ID for the referring node.
  • CZ_UI_DEFS (SYNONYM) — UI definition header data (name, description, tree sequence, UI style).
  • CZ_MODEL_REF_EXPLS (SYNONYM) — model reference explosion nodes providing model IDs, parent explosion node IDs, node depth, and virtual flags.
  • CZ_MODEL_UTIL_PVT (PACKAGE) and CZ_UTILS (PACKAGE) — PL/SQL utility APIs referenced indirectly for derived attributes.
  • CZ_EXPL_PAIR_TBL (TYPE) — a collection type used in the view's hierarchical traversal logic.

The view correlates these objects through UI definition IDs (LOCAL_UI_DEF_ID, PARENT_UI_DEF_ID) and explosion node identifiers, producing a denormalized row per UI component within its hierarchical context.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which UI components map to persistent nodes, tracing hierarchy depth for a configured model, and reporting root-to-leaf configuration trees for integration with order management or quoting.

SELECT ROOT_UI_NAME, NAME, OBJECT_TYPE, LEAF_PERSISTENT_NODE_ID, EXPL_NODE_DEPTH
FROM   APPS.CZ_UICOMPONENT_HGRID_V
WHERE  LEAF_PERSISTENT_NODE_ID IS NOT NULL
ORDER BY ROOT_UI_DEF_ID, TREE_SEQ;

To locate rows tied to a specific persistent node:

SELECT ROOT_UI_NAME, NAME, LEAF_PS_NODE_ID, ROOT_REFING_NODE_PERSIST_ID
FROM   APPS.CZ_UICOMPONENT_HGRID_V
WHERE  LEAF_PERSISTENT_NODE_ID = :p_persistent_node_id;

Because the view joins multiple synonym-backed Configurator objects, queries should be filtered on the root UI or model ID to constrain cost, and any integration layer should treat PERSISTENT_NODE_ID as the stable key across sessions.