Search Results java_sys_prop_name

Overview

The view APPS.CZ_NODETYPE_JAVASYSPROPS_V is a configuration-centric reporting view within the Oracle E-Business Suite (EBS) Oracle Configurator module. It exposes the relationship between Configurator node types and the Java system property rules that govern runtime behavior for those node types. In EBS 12.1.1 and 12.2.2, Oracle Configurator relies on a metadata-driven model in which nodes, properties, and rules are stored in the CZ schema and attached to UI or runtime rendering components. This view consolidates that metadata into a single, denormalized read interface suitable for administrative reporting, migration validation, and diagnostic queries.

The object is owned by the APPS schema and is designated VALID, with an FND Design Data identifier of CZ.CZ_NODETYPE_JAVASYSPROPS_V. It is a query-only construct: no database object references it, meaning it exists for reporting and integration consumption rather than as a dependency of other compiled code. The presence of the TEMPLATE_TOKEN column, which is the term driving the current search, indicates that the view surfaces the substitution token used when Configurator generates or validates Java system property expressions at runtime.

Underlying Base Objects

Per the ETRM dependency metadata, CZ_NODETYPE_JAVASYSPROPS_V is defined over three base objects accessed through APPS synonyms:

• CZ_RULES — stores the rule definitions that bind node types to Java system property behavior.
• CZ_SIGNATURES — holds signature information associated with property attachments, referenced via PROPATTACH_SIGNATURE_ID.
• CZ_TYPE_RELATIONSHIPS — defines the hierarchy and relationships among Configurator node types, supplying DETAILED_NODE_TYPE_ID and DETAILED_NODE_TYPE_NAME.

The view acts as a join surface that resolves rule and signature identifiers into human-readable node type names and template tokens, removing the need for callers to reconstruct the CZ model manually. Because these underlying objects are core Configurator metadata tables, the view inherits the same security context and should be treated as read-only.

Key Columns

• DETAILED_NODE_TYPE_ID / DETAILED_NODE_TYPE_NAME — the numeric key and display name (30 characters) of the Configurator node type.
• JAVA_SYS_PROP_RULE_ID — foreign reference to the governing rule in CZ_RULES.
• JAVA_SYS_PROP_NAME — the name of the Java system property (up to 255 characters).
• TEMPLATE_TOKEN — the substitution token (30 characters) used in template expansion for the property; central to template-driven configuration.
• PROPATTACH_SIGNATURE_ID — the property attachment signature, joined to CZ_SIGNATURES.
• JAVA_SYS_PROP_TYPE_ID — identifier of the property type.
• JAVA_SYS_PROP_DATA_TYPE — the declared data type of the property (up to 2000 characters).
• VIEWREV — a revision marker (CHAR 10) indicating the metadata version of the view row.

Common Use Cases and Queries

Administrators and integrators use this view to audit which node types emit Java system properties, to verify that template tokens are correctly assigned, and to compare property attachments across environments. A typical query lists all properties and tokens for a node type:

• SELECT DETAILED_NODE_TYPE_NAME, JAVA_SYS_PROP_NAME, TEMPLATE_TOKEN, JAVA_SYS_PROP_DATA_TYPE FROM APPS.CZ_NODETYPE_JAVASYSPROPS_V WHERE DETAILED_NODE_TYPE_NAME = :node_name;
• SELECT TEMPLATE_TOKEN, COUNT(*) FROM APPS.CZ_NODETYPE_JAVASYSPROPS_V GROUP BY TEMPLATE_TOKEN ORDER BY 2 DESC; — detects duplicated or reused tokens.
• SELECT * FROM APPS.CZ_NODETYPE_JAVASYSPROPS_V WHERE JAVA_SYS_PROP_RULE_ID = :rule_id; — traces all node types affected by a rule change.

These queries support impact analysis during configuration migrations and troubleshooting of runtime property resolution.