Results for “cz_uitempls_for_psnodes_v”

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

Overview

CZ_UITEMPLS_FOR_PSNODES_V is an Oracle E-Business Suite Configurator (CZ) view owned by the APPS schema. It joins product structure UI nodes with the UI templates and UI definition records that govern their presentation in the Configurator user interface. The view combines a broad projection of the CZ_UI node columns with template metadata drawn from the UI template and UI definition objects, plus derived values such as UIDEF_MODEL_ID and UIDEF_NAME resolved through subqueries against CZ_UI_DEFS.

Its principal role is reporting and integration: it exposes, in a single denormalized result set, which UI template applies to a given product structure node, how that template is typed, and where the node sits in the containment hierarchy. The presence of the PARENT_CONTAINER_TYPE column, which originates from the template source rather than from the node table itself, is significant: it describes the type of the container that parents a template's root region, allowing developers and integrators to determine the expected host context for a template-driven UI element.

Underlying Base Objects

The documented dependencies for this view are:

• CZ_UI_DEFS — supplies the UI definition identity, including UI_DEF_ID and related values surfaced through scalar subqueries.
• CZ_UI_TEMPLATES — provides TEMPLATE_ID, TEMPLATE_NAME, TEMPLATE_TYPE, JRAD_DOC, ROOT_REGION_TYPE, LAYOUT_UI_STYLE, and PARENT_CONTAINER_TYPE.
• CZ_UI_CONT_TYPE_TEMPLS — associates UI container types with templates.
• CZ_UIDEF_SIGNATURE_TEMPLS_V — a supporting view linking UI definitions, signatures, and templates.
• CZ_UI_TYPEDPSN_V — a typed product structure node view supplying node-level data.
• CZ_TYPE_RELATIONSHIPS — defines relationships among Configurator node and feature types.
• CZ_TYPES — the package that encapsulates type-handling logic referenced by the surrounding model.

The view text projects columns from an aliased source C (the node/UI definition side), joined to aliases B (UI definition) and D (template). Two inline scalar subqueries resolve UIDEF_MODEL_ID and UIDEF_NAME from CZ_UI_DEFS using B.UI_DEF_ID, confirming that template metadata and node metadata are correlated through the UI definition.

Key Columns

• PS_NODE_ID, PARENT_ID, PERSISTENT_NODE_ID, PARENT_PERSISTENT_NODE_ID — identify the node and its hierarchical position.
• PS_NODE_TYPE, FEATURE_TYPE, DETAILED_TYPE_ID — describe the node's structural and feature classification.
• UI_DEF_ID, UIDEF_MODEL_ID, UIDEF_NAME, TEMPLATE_ID, TEMPLATE_UI_DEF_ID — tie the node to its UI definition and template.
• TEMPLATE_NAME, TEMPLATE_TYPE, TEMPLATE_DESC, JRAD_DOC — template identity and rendering document reference.
• PARENT_CONTAINER_TYPE — the container type expected to parent the template's root region; the search term for this object.
• ROOT_REGION_TYPE, ROOT_ELEMENT_SIGNATURE_ID, LAYOUT_UI_STYLE — template layout and root region characteristics.
• UI_SECTION, UI_OMIT, REGION_FLAG, COMPONENT_SEQUENCE_PATH — UI placement and rendering controls.
• EFFECTIVE_FROM, EFFECTIVE_UNTIL, EFFECTIVE_USAGE_MASK, EFFECTIVITY_SET_ID — effectivity handling.
• QUOTEABLE_FLAG, ORDER_SEQ_FLAG, BOM_TREATMENT, BOM_REQUIRED_FLAG — order and BOM integration attributes.

Common Use Cases and Queries

Typical reporting asks which template drives a node and under what parent container it must be rendered. For example:

• List nodes whose template expects a specific parent container type: SELECT PS_NODE_ID, NAME, TEMPLATE_NAME, PARENT_CONTAINER_TYPE FROM CZ_UITEMPLS_FOR_PSNODES_V WHERE PARENT_CONTAINER_TYPE = :p_container_type;
• Trace a model's UI composition: SELECT UIDEF_NAME, TEMPLATE_NAME, PS_NODE_TYPE, TREE_SEQ FROM CZ_UITEMPLS_FOR_PSNODES_V WHERE UIDEF_MODEL_ID = :p_model_id ORDER BY TREE_SEQ;
• Identify nodes bypassing the UI: SELECT PS_NODE_ID, NAME FROM CZ_UITEMPLS_FOR_PSNODES_V WHERE UI_OMIT = 'Y';

These queries support template validation, migration audits, and diagnostic review of Configurator user interface behavior.