Search Results cz_system_property_rels_v




Overview
Explore in AI Chat

Overview

CZ_SYSTEM_PROPERTY_RELS_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Configurator (CZ) product module. It exposes a filtered subset of the configuration type relationship data maintained in the Configurator data model, specifically the relationships that define how system properties and related configuration types are associated with one another. In EBS 12.1.1 and 12.2.2, the view is registered in the ETRM repository as a VALID object and carries the status of a documented, supported access point for configuration relationship metadata.

The view is designed to isolate active, non-deleted system relationships from the broader population held in the base table. Its role in reporting and integration is to provide a stable, denormalized projection of relationship rows where the relationship type code falls into the set 'SYS', 'JSY', or 'CAP', and where the record has not been logically deleted. Oracle Configurator and dependent Oracle applications such as Oracle Order Management and Oracle Configure-to-Order use this relationship information to resolve which system properties apply to a given configuration model. Because it is a view rather than a table, no direct DML is permitted against it; consumers treat it purely as a query surface.

Underlying Base Objects

The view is defined exclusively over a single base object, CZ_TYPE_RELATIONSHIPS, which is referenced through a synonym and resides in the APPS schema. The definition is a straightforward projection:

  • The view selects ROWID from CZ_TYPE_RELATIONSHIPS, aliased as REL_ID.
  • It restricts the result set with the predicate REL_TYPE_CODE IN ('SYS', 'JSY', 'CAP').
  • It further restricts the result set with the predicate DELETED_FLAG = '0'.

No joins, unions, or additional base objects participate in the definition, so the view's cardinality is always less than or equal to that of the underlying table. The dependency on CZ_TYPE_RELATIONSHIPS means that any invalidation or recompilation of that base object can affect the validity of the view, although the ETRM metadata records the view as VALID at the time of documentation. Because the REL_ID column is derived from ROWID rather than a persistent surrogate key, the value is physical and can change if rows are migrated or reorganized by maintenance operations.

Key Columns

The view exposes six columns, each carrying specific semantics for configuration relationship reporting:

  • REL_ID — The ROWID of the source row in CZ_TYPE_RELATIONSHIPS, presented as a unique identifier for the relationship within the view. It is suitable for row identification but should not be treated as a durable business key.
  • SUBJECT_TYPE — Identifies the configuration entity type acting as the subject (source) of the relationship.
  • OBJECT_TYPE — Identifies the configuration entity type acting as the object (target) of the relationship.
  • REL_TYPE_CODE — The relationship classification. Within this view the value is constrained to 'SYS' (system), 'JSY' (joint system), or 'CAP' (capability) relationships.
  • DELETED_FLAG — Logical deletion indicator. By definition of the view this column is always '0', confirming that only active rows are returned.
  • SEEDED_FLAG — Indicates whether the relationship was delivered as seeded Oracle data or created by a customer during implementation.

Common Use Cases and Queries

The view is typically queried when implementers or support analysts need to enumerate the system-level relationships between configuration types without retrieving the full, unfiltered contents of CZ_TYPE_RELATIONSHIPS. A common pattern is to list all relationships involving a particular type:

  • SELECT rel_id, subject_type, object_type, rel_type_code, seeded_flag FROM cz_system_property_rels_v WHERE subject_type = :type_name;
  • SELECT object_type, rel_type_code FROM cz_system_property_rels_v WHERE rel_type_code = 'CAP';
  • SELECT seeded_flag, COUNT(*) FROM cz_system_property_rels_v GROUP BY seeded_flag;

These queries support impact analysis before modifying configuration models, verification of seeded versus customer-defined relationships after an upgrade from 12.1.1 to 12.2.2, and diagnostic investigation when Configurator fails to resolve expected system properties during runtime. Because the view already enforces the deleted and relationship-type filters, consumers do not need to repeat those predicates, although adding further restrictive conditions on SUBJECT_TYPE or OBJECT_TYPE generally improves performance.