Search Results sys_prop_data_type_id

Overview

APPS.CZ_COMMON_CHILDND_SYSPROPS_V is a configuration-oriented view within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 Oracle Configurator and ETRM (Enterprise Territory and Rules Management / Configurator runtime) schema. It exposes the set of system property rules (system properties) that are applicable to child nodes of a configuration model hierarchy, resolved through the parent-child node relationships held in CZ_PS_NODES. In practical terms, the view answers the question: "For a given parent configuration node and its child development project, which system property rules — including their rule identifiers, data types, sequence, and instantiation behavior — are inherited or applied?"

The view plays a supporting role in reporting, diagnostics, and integration work. Consultants commonly query it to trace how SYS_PROP_RULE_ID values are associated with a parent node, to verify property propagation through the model tree, and to audit the instance-set flags that govern runtime behavior. Because it consolidates node, signature, and rule metadata into a single flattened projection, it is useful where a direct join across CZ_PS_NODES, CZ_RUL_TYPEDPSN_V, and CZ_SIGNATURE_SYSPROPS_V would otherwise be required.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over the following objects:

• CZ_PS_NODES (referenced via SYNONYM) — supplies the parent/child node hierarchy (parent_node_id, parent_instantiable_flag, ps_node_type, reference_id, devl_project_id, deleted_flag).
• CZ_RUL_TYPEDPSN_V (VIEW) — supplies the detailed type / devl_project association used for rule typing (psnrty1).
• CZ_SIGNATURE_SYSPROPS_V (VIEW) — supplies the system property definitions (SYS_PROP_RULE_ID, SYS_PROP_NAME, rule_type, RETTYPE, sequence, instance_set_flag).
• CZ_TYPES (PACKAGE) — supplies type decoding / data type resolution.
• FND_PROFILE (PACKAGE) — used for profile-based context resolution during execution.

The view text joins the parent subquery (derived from CZ_PS_NODES) to CZ_RUL_TYPEDPSN_V on devl_project_id, then to CZ_SIGNATURE_SYSPROPS_V on detailed_type_id = DETAILED_signature_ID and devl_project_id = p_model_id. A HAVING clause restricts rows to parents whose child count matches the full child population, and a UNION ALL combines a second branch driven by intsys property rules.

Key Columns

• parent_id — the parent node identifier (parent_node_id or ps_node_id depending on branch).
• sysprop_rule_id — the system property rule identifier; this is the column users search for and the primary linkage to rule configuration.
• SYS_PROP_NAME — human-readable name of the system property.
• rule_type / RULE_TYPE_CODE / rule_type_label — classify the rule and provide code and display label.
• SYS_PROP_DATA_TYPE_ID / SYS_PROP_DATA_TYPE_NAME — the return/data type of the property (aliased from SYS_PROP_RETTYPE_ID / SYS_PROP_RETTYPE_NAME).
• SYS_PROP_SEQ_NBR — ordering sequence for property evaluation.
• instance_set_flag — indicates instancing behavior; the query filters instance_set_flag IN (2,3).
• parent_instantiable_flag — indicates whether the parent node is instantiable.

Common Use Cases and Queries

Typical uses include auditing which system property rules apply to a parent node, investigating propagation of properties to children, and reconciling configured rules against runtime behavior.

• Locate a specific rule by its identifier:
  SELECT parent_id, sysprop_rule_id, SYS_PROP_NAME, RULE_TYPE_CODE
FROM APPS.CZ_COMMON_CHILDND_SYSPROPS_V
WHERE sysprop_rule_id = :rule_id;
• List all properties for a parent node, ordered by sequence:
  SELECT sysprop_rule_id, SYS_PROP_NAME, SYS_PROP_SEQ_NBR, instance_set_flag
FROM APPS.CZ_COMMON_CHILDND_SYSPROPS_V
WHERE parent_id = :parent_id
ORDER BY SYS_PROP_SEQ_NBR;
• Inspect instancing and data type attributes:
  SELECT parent_id, sysprop_rule_id, SYS_PROP_DATA_TYPE_NAME, instance_set_flag, parent_instantiable_flag
FROM APPS.CZ_COMMON_CHILDND_SYSPROPS_V;

Because the view is a read-only projection over configurator model metadata, it should be used for inquiry and reporting only; modifications to system property rules must be performed through the supported Configurator setup forms and concurrent programs.