Results for “cz_node_no_properties_v”

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

Overview

CZ_NODE_NO_PROPERTIES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Configurator (CZ) product family. It is available in both the 12.1.1 and 12.2.2 release streams and is documented in the E-Business Suite Technical Reference Manual (ETRM) with a status of VALID. The view exposes a synthetic, placeholder property row for configuration model nodes that are associated with a node type but carry no user-defined properties. Instead of returning actual attribute definitions, the view manufactures a single constant row per qualifying node, which allows downstream configuration logic, reporting, and integration layers to treat "no properties" as an explicit, queryable condition rather than an absence of data.

The view is therefore best understood as a catalog of property-bearing node types rather than a property catalog itself. It is commonly consumed by Configurator runtime components and by custom extensions that need to iterate over all model nodes—including those with no declared properties—without breaking joins or aggregations.

Underlying Base Objects

Per the documented ETRM metadata, CZ_NODE_NO_PROPERTIES_V is defined over three referenced base objects:

• CZ_CONVERSION_RELS_V (VIEW) — a conversion-relationship view that maps object types to their internal type identifiers and supplies the DATA_TYPE value via CNV.SUBJECT_TYPE.
• CZ_RUL_TYPEDPSN_V (VIEW) — a typed property-subject-node view that contributes the PS_NODE_ID column via PSN.PS_NODE_ID and the DETAILED_TYPE_ID used in the join predicate.
• CZ_TYPES (PACKAGE) — the Configurator PL/SQL package that encapsulates type resolution and validation logic invoked by the underlying views.

The join condition is CNV.OBJECT_TYPE = PSN.DETAILED_TYPE_ID, which correlates each node's detailed type with a conversion relationship row. The view text uses a SELECT list of literal expressions combined with these two joined views, so it inherits no base tables directly and remains a purely derived construct.

Key Columns

• PROP_ID — a literal -1, signalling "no property." This sentinel value distinguishes placeholder rows from real property identifiers.
• NAME — a literal single space (' '), used because Configurator consumers expect a non-null name field.
• PS_NODE_ID — the property-subject node identifier sourced from CZ_RUL_TYPEDPSN_V; this is the meaningful join key to model structure tables.
• DATA_TYPE — derived from CNV.SUBJECT_TYPE, indicating the type classification of the associated conversion relationship.
• MUTABLE_FLAG — a literal '1', indicating the placeholder is treated as mutable by consuming logic.
• COLLECTION_FLAG — a literal '0', indicating the entry does not represent a collection.
• PROPERTY_TYPE — a literal '-1', another sentinel confirming no concrete property type applies.

Common Use Cases and Queries

Typical usage centers on identifying nodes that have a recognized type but no declared properties, or on padding property unions so that every node yields at least one row.

• Auditing model nodes with no properties for data-quality review.
• Driving Configurator list-of-values and UI screens that require a non-empty property set.
• Supporting custom integration extracts where property joins would otherwise drop typed nodes.

Representative query:

SELECT ps_node_id, data_type, property_type
FROM   apps.cz_node_no_properties_v;

To combine placeholders with actual properties, union the view with the standard property views on PS_NODE_ID, filtering on PROP_ID to separate the sentinel rows from real definitions. Because the view is owned by APPS and joins other APPS views, all references should be fully qualified and access grants limited to authorized reporting roles.