Results for “cz_common_childnd_props_v”

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

Overview

CZ_COMMON_CHILDND_PROPS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered under the CZ (Configurator) product family. Its name reflects its purpose: it consolidates the properties (attributes) associated with common nodes and their child nodes within a Configurator model structure. In Oracle Configurator, a "PS node" represents a node in a model's property structure, and each node can expose one or more configurable properties (such as a feature, option, or numeric attribute). This view flattens the relationships between a parent node, its child nodes, and the properties each child carries, so that reporting, integration, and extension logic can retrieve node-level property metadata without navigating the underlying normalized Configurator tables directly.

The view is designed primarily for reporting and integration rather than transactional processing. Because it aggregates properties from multiple lineage paths — including reference nodes, item-type-driven properties, and direct property-value assignments — it serves as a single source for consumer applications that need to enumerate the properties a parent node's descendants expose. Given the user search term "property_name," the PROPERTY_NAME column is the central projection of the view, carrying the human-readable identifier of each configurable property.

Underlying Base Objects

The view is defined over five documented base objects, all referenced as APPS synonyms:

• CZ_PROPERTIES — the master definition of each property, supplying PROPERTY_ID, NAME (surfaced as PROPERTY_NAME), and DATA_TYPE. Only rows with DELETED_FLAG = '0' are eligible.
• CZ_PS_NODES — the property-structure nodes forming the model hierarchy, providing PARENT_ID, PS_NODE_ID, PS_NODE_TYPE, REFERENCE_ID, and ITEM_ID.
• CZ_PS_PROP_VALS — the assignment of property values to specific nodes, linking properties to nodes.
• CZ_ITEM_MASTERS — the item master references that connect item types to model nodes.
• CZ_ITEM_TYPE_PROPERTIES — the mapping of properties to item types, enabling item-driven property inheritance.

Internally, the view is a four-branch UNION of these tables. Each branch applies DELETED_FLAG = '0' filters to its contributing tables and joins properties to nodes either directly (via CZ_PS_PROP_VALS), through reference nodes where PS_NODE_TYPE = 263, or through item types. The outer query applies a GROUP BY PARENT_ID, PROPERTY_ID, PROPERTY_NAME, DATA_TYPE, which de-duplicates properties that reach the same parent through multiple paths.

Key Columns

• PARENT_ID — the identifier of the parent node under which the child property is organized; the primary grouping key for hierarchical reporting.
• PROPERTY_ID — the unique numeric identifier of the configurable property.
• PROPERTY_NAME — the descriptive name of the property (sourced from CZ_PROPERTIES.NAME); this is the column users most commonly search for when locating a specific attribute.
• DATA_TYPE — the data type of the property (e.g., numeric, text, boolean), indicating how the property value should be interpreted by the Configurator runtime or by downstream reporting.

Common Use Cases and Queries

Typical uses include auditing which properties are exposed beneath a given parent node, verifying property definitions across model versions, and feeding integration routines that must map Configurator properties to external systems. A query to locate a property by name follows:

SELECT parent_id, property_id, property_name, data_type
FROM apps.cz_common_childnd_props_v
WHERE property_name LIKE '%COLOR%';

To enumerate all properties for a specific parent node:

SELECT property_name, data_type
FROM apps.cz_common_childnd_props_v
WHERE parent_id = :parent_id
ORDER BY property_name;

Because the view is read-only and de-duplicated, it is safe for ad hoc reporting but is not intended for DML. Analysts should note that it reflects only non-deleted records across all contributing tables.