Search Results desc_expl_reference_depth

Overview

APP.CZ_UICOMPONENT_HGRID_V is a read-only database view in the Oracle EBS Applications schema that exposes hierarchical grid (HGrid) UI component metadata for the Oracle Configurator / Configuration Framework UI layer. It is one of the CZ_% component views used by the Configurator user interface to resolve the structure, ordering, and persistence identity of nodes displayed in a hierarchical grid control. Rather than storing data itself, the view assembles a flattened, denormalised projection of UI definition records, model reference explanation nodes, and persistent node identifiers, allowing callers to traverse the UI hierarchy in a single SELECT.

As part of the Applications data model, the view is registered in FND Design Data under the internal name CZ.CZ_UICOMPONENT_HGRID_V and carries a status of VALID in both 12.1.1 and 12.2.2. Its primary role is supporting reporting and integration queries that need to understand how Configurator HGrid components are composed, without replicating the proprietary PL/SQL logic used to build the hierarchy at runtime.

Underlying Base Objects

The view is defined over a combination of stored tables and programmatic constructs. The documented base objects are:

• CZ_UI_DEFS (synonym) — UI definition master rows supplying root UI identifiers, names, descriptions, list sequence, and style attributes.
• CZ_UI_COMPONENTS_V (view) — the parent UI component view that supplies child component attributes such as OBJECT_TYPE, OBJECT_ID, and descriptive text.
• CZ_MODEL_REF_EXPLS (synonym) — model reference explanation nodes, contributing the explanation node identifiers (ROOT_MODEL_EXPL_ID, REF_EXPL_NODE_ID, LEAF_EXPL_NODE_ID) and reference depth values.
• CZ_PS_NODES (synonym) — persistent structure nodes, providing LEAF_PS_NODE_ID and related persistence coordinates.
• CZ_MODEL_UTIL_PVT (package) — supplies model and hierarchy utility logic invoked as part of the view definition.
• CZ_UTILS (package) — general utility functions used for identifier resolution.
• CZ_EXPL_PAIR_TBL (type) — a PL/SQL collection type used to aggregate explanation node pairs during hierarchy assembly.

The presence of package and collection-type references indicates the view is not a simple join; its query text employs pipelined or table-function style resolution via CZ_MODEL_UTIL_PVT and CZ_EXPL_PAIR_TBL to build the explanation-node relationships exposed as columns.

Key Columns

The view exposes approximately forty columns. The most significant include:

• AMNNAME — the application module name context for the component.
• ROOT_UI_DEF_ID / ROOT_UI_NAME / ROOT_UI_DESCRIPTION / ROOT_UI_STYLE / ROOT_UI_LIST_SEQ — identity and presentation attributes of the top-level UI definition.
• MODEL_ID / CHILD_MODEL_ID — the model bound to the root and child nodes respectively.
• ROOT_MODEL_EXPL_ID / ROOT_MDL_PARNT_EXPL_ID / REF_EXPL_NODE_ID / LEAF_EXPL_NODE_ID / LEAF_PERSISTENT_NODE_ID — explanation-node coordinates that anchor the hierarchy within the configuration model.
• LEAF_PS_NODE_ID — the persistent structure node identifier for the leaf of the hierarchy branch. This column is the target of the user's search term and is the key join point back to CZ_PS_NODES for persistence-aware queries.
• XPL_NODE_DEPTH / MODEL_REFERENCE_DEPTH / DESC_EXPL_REFERENCE_DEPTH — depth indicators used to order and indent nodes in the grid.
• VIRTUAL_FLAG — indicates whether the node is virtual (rendered only) or backed by persisted data.
• OBJECT_TYPE / OBJECT_TYPE_CODE / OBJECT_ID / NAME / DESCRIPTION — generic attributes describing the underlying component object.
• PARENT_OBJECT_TYPE / PARENT_OBJECT_ID / EXPL_PARENT_UI_DEF_ID / UICOMP_PARENT_UI_DEF_ID — parent linkage columns used to rebuild the tree.
• TREE_SEQ / LOCAL_UI_DEF_ID / LOCAL_UI_PAGE_SET_ID / UI_DEVL_PROJECT_ID / VIEWREV — ordering, localisation, development-project, and revision metadata.

Common Use Cases and Queries

Typical scenarios include auditing the composition of a Configurator hierarchical grid, tracing which persistent structure node backs a displayed leaf, and integrating Configurator UI metadata into custom reports or middleware extracts. A representative query returning the grid hierarchy for a given UI definition is:

• SELECT ROOT_UI_DEF_ID, ROOT_UI_NAME, OBJECT_TYPE, OBJECT_ID, LEAF_PS_NODE_ID, XPL_NODE_DEPTH, TREE_SEQ FROM APPS.CZ_UICOMPONENT_HGRID_V WHERE ROOT_UI_DEF_ID = :p_ui_def_id AND VIRTUAL_FLAG = 'N' ORDER BY TREE_SEQ;
• Searches on the leaf persistent-structure node are expressed as WHERE LEAF_PS_NODE_ID = :p_ps_node_id, which links HGrid components to their CZ_PS_NODES rows for further persistence analysis.
• Because the view is read-only, it is safe to use in ad-hoc SQL*Plus, BI Publisher data models, and OAF/ADF BC view objects, provided the CZ packages it depends on remain compiled and valid.

Note that the view is internal to Configurator and is not documented for direct customer modification; consumers should treat its column semantics as stable within a patch level.