Search Results sys_prop_name




Overview
Explore in AI Chat

Overview

APPS.CZ_NODETYPE_PROPERTIES_V is a reporting and integration view in the Oracle E-Business Suite configuration/constraint engine (CZ schema surfaced through the APPS synonym layer). It presents the cross-product relationship between node types, system properties, and the property-to-node attachments defined in the rules model. In practical terms, the view answers the question: "For a given node type, which system properties are attached, and under what system property type, data type, and mutability?" This makes it the canonical row source for introspection of the configuration model, replacement of ad-hoc joins across the three underlying views, and any integration that must enumerate or filter system properties by node type.

The view is exposed in both EBS 12.1.1 and 12.2.2 through the APPS schema, and the underlying CZ objects are consistent with the 12.2.2 ETRM metadata documented for this object. Because APPS is the publishing schema, the view is available to any responsibility or custom code with APPS execute/select privileges, avoiding the need to grant directly on the CZ views.

Underlying Base Objects

The view is defined over three views from the CZ schema:

The joins are equality-based: NODEREL.SUBJECT_TYPE = PROPREL.SUBJECT_TYPE and PROPREL.OBJECT_TYPE = SYSPROP.RULE_ID. A DISTINCT is applied to the projection, which collapses duplicate rows that arise when multiple relationship paths resolve to the same node type/property pairing.

Key Columns

  • PROP_ID — SYSPROP.RULE_ID; the internal identifier of the system property rule.
  • NAME — CONCAT(SYSPROP.NAME, '()'); the display form with parentheses, suitable for UI or reporting labels.
  • SYS_PROP_NAME — the raw system property name; this is the column users search on when looking up "sys_prop_name".
  • NODE_TYPE — NODEREL.OBJECT_TYPE; the node type to which the property applies.
  • ATTACHED_TO_NODE_TYPE — PROPREL.SUBJECT_TYPE; the node type recorded on the property relationship.
  • DATA_TYPE — the property's data type (e.g., string, number, boolean, collection).
  • MUTABLE_FLAG — indicates whether the property value may be modified at runtime.
  • COLLECTION_FLAG — indicates whether the property holds a collection rather than a scalar.
  • SEQ_NBR — ordering sequence for display or processing.
  • SYSTEM_PROPERTY_TYPE — PROPREL.REL_TYPE_CODE; classifies the relationship type.
  • CONFIG_ENGINE_TYPE — identifies the configuration engine context for the property.

Common Use Cases and Queries

Typical uses include generating metadata reports of which properties are attached to a node type, filtering properties by data type or mutability for validation tooling, and driving integration or UI generation from the model. A basic enumeration by name:

  • SELECT node_type, sys_prop_name, data_type, mutable_flag, collection_flag, seq_nbr FROM apps.cz_nodetype_properties_v WHERE sys_prop_name = :p_name ORDER BY node_type, seq_nbr;
  • SELECT DISTINCT node_type, sys_prop_name FROM apps.cz_nodetype_properties_v WHERE node_type = :p_node_type ORDER BY sys_prop_name;
  • SELECT sys_prop_name, system_property_type, config_engine_type FROM apps.cz_nodetype_properties_v WHERE mutable_flag = 'Y' AND collection_flag = 'N';

Because the view is built on three views and applies DISTINCT, queries that filter on a small number of columns perform best; avoid selecting all columns when only a subset is required. The view is read-only and should not be used as a target for DML; property definitions and relationships must be maintained through the supported configuration engine APIs.