Search Results cz_nodes_for_uielems_eff_cv




Overview
Explore in AI Chat

Overview

CZ_NODES_FOR_UIELEMS_EFF_CV is an APPS-owned database view within the Oracle Configurator (CZ) module. It exposes configuration model nodes that are relevant to user interface elements, filtered by effectivity, so that the Configurator runtime and its integration points can render the correct set of UI components for a given configuration session. In Oracle EBS 12.1.1 and 12.2.2, the Configurator relies on a metadata-driven model: nodes, features, options, and their relationships are persisted across several CZ tables, and effective dating governs which versions of a model are valid at a point in time. This view consolidates the node data from the effective image of the model (CZ_EXPLNODES_IMAGE_EFF_V) with UI-signature resolution logic supplied by the CZ_TYPES package.

The suffix conventions are meaningful: "EFF" denotes effectivity-aware content, "CV" denotes a view intended for the Configurator user interface. The view therefore sits in the presentation and integration layer rather than the base persistence layer, and it is most likely referenced by Configurator runtime code, extensibility hooks, or custom reports that need to enumerate UI-visible nodes.

Underlying Base Objects

The view is defined over a mixture of views, packages, and synonyms. Documented base objects include:

  • CZ_EXPLNODES_IMAGE_EFF_V (VIEW) — the primary source of node rows. It provides the effective-dated node image used to populate nearly every column in the outer view.
  • CZ_TYPES (PACKAGE) — supplies CZ_TYPES.GET_UI_SIGNATURE_ID, called to derive a UI signature identifier from node attributes such as instantiable flag, feature type, counted-options flag, maximum/minimum, node type, reference ID, and maximum selected.
  • CZ_TYPE_RELATIONSHIPS (SYNONYM) and CZ_PDT_2_PGE_RELS_V (VIEW) — joined through an EXISTS subquery to determine whether a node is disabled for the UI, based on conversion relationship type ('CNV') and page-element mappings.
  • CZ_SIGNATURES (SYNONYM) — used to resolve the page element type signature.
  • CZ_DEVELOPER_UTILS_PVT and CZ_UTILS (PACKAGES) — supporting utility logic.
  • DUAL (SYNONYM) — used in the scalar subquery that computes NODE_DISABLED_FLAG.

Key Columns

The view selects a broad projection of node attributes. Notable columns include:

Common Use Cases and Queries

Typical uses include diagnosing why a node does not appear in the Configurator UI, validating effectivity windows, and building custom reports of UI-visible nodes. The following sample retrieves active, UI-visible nodes for a given model:

SELECT ps_node_id, name, feature_type, effective_from, effective_until, node_disabled_flag
FROM   apps.cz_nodes_for_uielems_eff_cv
WHERE  model_id = :p_model_id
AND    node_disabled_flag = 0
AND    ui_omit = '0'
ORDER BY node_depth, tree_seq;

A second pattern identifies nodes disabled by conversion relationships:

SELECT ps_node_id, name, p_page_element_type
FROM   apps.cz_nodes_for_uielems_eff_cv
WHERE  node_disabled_flag = 1;

Because the view calls CZ_TYPES.GET_UI_SIGNATURE_ID per row, queries returning large node sets should be filtered by model or effectivity set to limit package invocation overhead. Where persistence of results is required, materializing the filtered set into a staging table is preferable to repeated direct queries.