Search Results cz_common_childnd_sysprops_v




Overview
Explore in AI Chat

Overview

APPS.CZ_COMMON_CHILDND_SYSPROPS_V is a Configurator (CZ) reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates child node system properties originating from the Configurator runtime model, allowing callers to resolve which system properties apply to a given node in the configuration hierarchy alongside its parent context. The view is registered in the ETRM as VALID under the APPS schema.

The view is especially relevant when querying configuration metadata by development project. Its definition includes the DEVL_PROJECT_ID column from CZ_PS_NODES, and the join predicates correlate child nodes to typed detailed signatures using PARENT.CHILD_DEVL_PROJECT_ID = PSNRTY1.DEVL_PROJECT_ID. Consequently, filtering or searching on devl_project_id is a natural and supported access path, linking a user's search term directly to the view's core join logic.

Underlying Base Objects

  • CZ_PS_NODES (SYNONYM) — the model/property-set node table. A derived inline subquery (aliased PARENT) selects PS_NODE_ID, INSTANTIABLE_FLAG, PS_NODE_TYPE, REFERENCE_ID, DEVL_PROJECT_ID, PARENT_ID, and DELETED_FLAG, filtering DELETED_FLAG = '0' and restricting INSTANTIABLE_FLAG to NULL, '2', or '3'.
  • CZ_RUL_TYPEDPSN_V (VIEW, aliased PSNRTY1/PSNRTY2) — supplies typed detailed signatures, PARENT_ID, and DEVL_PROJECT_ID used to correlate nodes to signature definitions.
  • CZ_SIGNATURE_SYSPROPS_V (VIEW, aliased NTSYS/INTSYS) — supplies system property definitions, rule types, sequence numbers, return types, and INSTANCE_SET_FLAG.
  • CZ_TYPES (PACKAGE) and FND_PROFILE (PACKAGE) — referenced for type and profile resolution used during view evaluation.

The first UNION ALL branch joins these objects on detailed type, development project, and parent node identity, grouping and applying a HAVING COUNT(*) check against the active child count in CZ_PS_NODES.

Key Columns

Common Use Cases and Queries

A frequent scenario is retrieving the system properties applicable to children of a specific development project, e.g. when resolving configurable attributes during a model build or when auditing property-set completeness. Because the view derives PARENT_ID from both top-level and child context, it supports both hierarchy traversal and flat property enumeration.

Example: list system properties for a given development project.

  • SELECT PARENT_ID, SYS_PROP_NAME, RULE_TYPE_LABEL, SYS_PROP_DATA_TYPE_NAME, SYS_PROP_SEQ_NBR, INSTANCE_SET_FLAG FROM APPS.CZ_COMMON_CHILDND_SYSPROPS_V ORDER BY PARENT_ID, SYS_PROP_SEQ_NBR;

Example: filter to a specific project context (using the underlying node join on DEVL_PROJECT_ID) and rule type:

  • SELECT v.PARENT_ID, v.SYS_PROP_RULE_ID, v.SYS_PROP_NAME, v.RULE_TYPE_CODE FROM APPS.CZ_COMMON_CHILDND_SYSPROPS_V v, APPS.CZ_PS_NODES n WHERE v.PARENT_ID = n.PS_NODE_ID AND n.DEVL_PROJECT_ID = :devl_project_id AND n.DELETED_FLAG = '0' ORDER BY v.SYS_PROP_SEQ_NBR;

Integration use: the view is well suited to concurrent programs, BI Publisher extracts, and OAF/Forms lookup layers that must present child-node system properties grouped by parent, since its aggregation and HAVING logic already eliminate orphaned or incomplete property sets.