Search Results cz_node_java_properties_v

Overview

The APPS.CZ_NODE_JAVA_PROPERTIES_V view is a Configurator (CZ) dictionary object that presents a consolidated, ordered list of the Java properties available on configuration model nodes. It exists to give both the runtime Configurator engine and any external reporting or integration layer a single, uniform source of property metadata, regardless of whether a given property originates as a "no" property, a system (rule-derived) property, or a user-defined property. The view is defined with Status VALID in the APPS schema and is shipped as part of the Oracle Configurator module in Oracle E-Business Suite 12.1.1 and 12.2.2.

Its principal reporting value is normalization. Rather than requiring a caller to query three separate property sources and reconcile their attributes, the view unions those sources and tags each row with a PROPERTY_TYPE discriminator and an internal SEQ ordering key. The presence of the MUTABLE_FLAG column is significant for any consumer that needs to know whether a property value may be changed after node instantiation: this is the attribute most commonly used to filter editable versus read-only properties during configuration and import/export processing.

Underlying Base Objects

The view text is a UNION ALL of three branches, each drawn from a dedicated property view, with an additional join path for rule-derived system properties:

• CZ_NODE_NO_PROPERTIES_V — the first branch (SEQ = 0), supplying non-selectable / "no" properties associated with a PS node.
• CZ_NODE_USER_PROPERTIES_V — the third branch (SEQ = 3), supplying user-defined properties.
• CZ_RUL_TYPEDPSN_V, CZ_CONVERSION_RELS_V, CZ_SYSTEM_PROPERTY_RELS_V, CZ_SYSTEM_PROPERTIES_V — the second branch (SEQ = 1), which resolves rule-based system properties. The join requires REL_TYPE_CODE = 'JSY' and matches SOURCE OBJECT_TYPE to the detailed type and the subject type to the system property's RULE_ID.
• CZ_TYPES (PACKAGE) — a documented referenced object, typically used for type conversion/attribute handling in the Configurator data model.

All branches are enclosed in an inline view and the result is ordered by SEQ and NAME, so non-selectable properties appear first, rule-derived system properties second, and user properties last.

Key Columns

• PROP_ID — identifier of the property; for system properties this is populated from SYS.RULE_ID.
• NAME — the property name. Rule-derived system properties are concatenated with '()' to signal their invocable nature.
• PS_NODE_ID — the configuration node (PS node) to which the property is bound. This is the effective join key for node-level reporting.
• DATA_TYPE — the declared type of the property. For system properties it is derived as CNV2.SUBJECT_TYPE.
• MUTABLE_FLAG — indicates whether the property value can be modified. Essential for distinguishing configurable inputs from fixed or derived values.
• COLLECTION_FLAG — indicates whether the property represents a collection (multi-valued) rather than a scalar.
• PROPERTY_TYPE — discriminator for the property category; system properties are hard-coded as '1'.

Common Use Cases and Queries

The view supports node-property audits, Configurator migration checks, and UI/reporting extracts that must display all properties for a node in a stable order.

• List all properties for a specific node, with mutability:

SELECT PROP_ID, NAME, DATA_TYPE, MUTABLE_FLAG, COLLECTION_FLAG, PROPERTY_TYPE FROM APPS.CZ_NODE_JAVA_PROPERTIES_V WHERE PS_NODE_ID = :p_node_id ORDER BY NAME;

• Isolate editable (mutable) properties only:

SELECT NAME, PS_NODE_ID, DATA_TYPE FROM APPS.CZ_NODE_JAVA_PROPERTIES_V WHERE MUTABLE_FLAG = 'Y';

• Separate user-defined from system and non-selectable properties:

SELECT PROPERTY_TYPE, COUNT(*) FROM APPS.CZ_NODE_JAVA_PROPERTIES_V GROUP BY PROPERTY_TYPE;

Because the UNION ALL can produce duplicate property names across sources, queries intended for cross-reference should include PROP_ID, PS_NODE_ID, and PROPERTY_TYPE in the projection to keep rows uniquely identifiable.