Search Results java_sys_prop_name

Overview

CZ_NODETYPE_JAVASYSPROPS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the CZ (Configurator) product family. Its documented status is VALID, and its internal view revision marker is dated 2004-08-03, indicating that the definition has remained stable across the 12.1.1 and 12.2.2 releases. The view exposes the association between Configurator node types and the Java system property rules that are attached to them. In the Configurator runtime model, Java system properties are rule-driven tokens that supply values to the Java-based configuration engine and to the resulting generated configuration model. This view flattens that relationship into a single denormalised result set, which makes it suitable for reporting, diagnostics, and integration extracts where a developer or analyst has identified the column JAVA_SYS_PROP_NAME and needs to trace it back to the node types that consume it.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms: CZ_RULES, CZ_SIGNATURES, and CZ_TYPE_RELATIONSHIPS. Although only three base objects are documented, the view text references these tables multiple times with distinct aliases, because the Configurator data model stores node types, property attachments, and rule signatures as rows within the same generic tables. CZ_TYPE_RELATIONSHIPS appears as JSYSP (the Java system property attachment), SUBND (the node type containment), and within the correlated NOT EXISTS subquery as CHKSYSPR, CHKSUBND, and CHK2SUBND. CZ_RULES appears as PRRUL for the property rule itself and as CHKPRRUL in the duplicate-detection subquery. CZ_SIGNATURES appears as NODSIG, SBNTY, RULSIG, and RULRET, supplying the node type signature, the signature name, the rule's data type binding, and the return signature respectively.

Key Columns

• DETAILED_NODE_TYPE_ID — sourced from SUBND.OBJECT_TYPE; the signature identifier of the node type to which the property applies.
• DETAILED_NODE_TYPE_NAME — sourced from SBNTY.NAME; the human-readable node type name.
• JAVA_SYS_PROP_RULE_ID — sourced from PRRUL.RULE_ID; the rule identifier representing the Java system property.
• JAVA_SYS_PROP_NAME — sourced from PRRUL.NAME; the property name, the value most commonly searched for.
• TEMPLATE_TOKEN — the rule's template token, used when the property is emitted into generated configuration output.
• PROPATTACH_SIGNATURE_ID — sourced from JSYSP.SUBJECT_TYPE; identifies the property attachment signature.
• JAVA_SYS_PROP_TYPE_ID and JAVA_SYS_PROP_DATA_TYPE — sourced from RULRET.SIGNATURE_ID and RULRET.JAVA_DATA_TYPE; the expected Java return signature and data type of the property.
• VIEWREV — a constant literal, '2004-08-03', identifying the view revision.

Common Use Cases and Queries

Typical uses include identifying which node types reference a given Java system property, validating that property names and template tokens are not duplicated across node types, and auditing the Java data type expected for each property. The view deliberately suppresses duplicates: the NOT EXISTS clause filters out any row where another active property rule (same NAME or same TEMPLATE_TOKEN) is attached to a related node type through the CNV and JSY relationship codes.

To find all node types consuming a specific property:

SELECT DETAILED_NODE_TYPE_NAME,
       JAVA_SYS_PROP_NAME,
       TEMPLATE_TOKEN,
       JAVA_SYS_PROP_DATA_TYPE
  FROM APPS.CZ_NODETYPE_JAVASYSPROPS_V
 WHERE JAVA_SYS_PROP_NAME = :property_name
 ORDER BY DETAILED_NODE_TYPE_NAME;

To list every Java system property defined for a single node type:

SELECT JAVA_SYS_PROP_NAME,
       JAVA_SYS_PROP_RULE_ID,
       JAVA_SYS_PROP_TYPE_ID
  FROM APPS.CZ_NODETYPE_JAVASYSPROPS_V
 WHERE DETAILED_NODE_TYPE_ID = :node_type_id;

Because the view joins CZ_SIGNATURES and CZ_RULES — high-volume Configurator metadata tables — queries should always be constrained by property name or node type. Unrestricted full scans are not advisable in production, and joins back to CZ_RULES on JAVA_SYS_PROP_RULE_ID should be performed only when additional rule attributes beyond those exposed here are required.