Search Results cz_engine_types




Overview
Explore in AI Chat

Overview

APPS.CZ_MODEL_PROP_ENGTYP_COMPAT_V is a configuration and compatibility view within the Oracle E-Business Suite (EBS) Advanced Product Catalog / Configurator foundation, part of the CZ schema family that supports Oracle's Configurator (also referred to as Oracle Configurator Developer and the underlying ETRM / CZ model repository). The view exposes, for each development project (model), the set of system property engine types that are compatible with the configuration engine assigned to that project. In practical terms, it answers the question: "Given this model and its selected configuration engine type, which engine-type system properties may legitimately be used?"

The view is defined across the CZ_LOOKUP_VALUES, CZ_TYPE_RELATIONSHIPS, and CZ_DEVL_PROJECTS objects, joined with the FND_PROFILE package. Within Oracle EBS reporting and integration scenarios, this view serves as a read-only reconciliation surface that allows developers, implementers, and custom reports to verify engine-type-to-model compatibility without navigating the underlying relationship tables directly. Because it abstracts the multi-table relationship between engine-type lookups, type relationships, and development projects, it is commonly referenced when diagnosing configuration engine behavior, validating model setup, or building compatibility extracts.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is owned by APPS and references the following base objects (all exposed as synonyms):

  • CZ_DEVL_PROJECTS (SYNONYM) — Provides the development project identifier and the configured engine type for each model.
  • CZ_LOOKUP_VALUES (SYNONYM) — Supplies lookup rows where LIST_NAME = 'CZ_ENGINE_TYPES'; used twice in the definition (aliased as PROPTYPES and ENGTYPES) to represent both the property side and the engine-type side of the relationship.
  • CZ_TYPE_RELATIONSHIPS (SYNONYM) — Bridges engine types (as SUBJECT_TYPE) to property types (as OBJECT_TYPE) via REL_TYPE_CODE = 'ETY'.
  • FND_PROFILE (PACKAGE) — Invoked through FND_PROFILE.VALUE_WNPS('CZ_DEV_ENABLE_CONFIG_ENGINE') to derive the default engine type when DEVl_PROJECT_ID = 0.

The join logic links three lookup/relationship inputs (PROPTYPES, ENGTYPES, TYPRELS) to the project row in CZ_DEVL_PROJECTS, using the engine-type data value as the compatibility matching key.

Key Columns

  • MODEL_ID — Derived from PROJ.DEVL_PROJECT_ID. The development project identifier, which uniquely identifies the model. A value of 0 signals the "global" or profile-driven case.
  • SYSPROP_ENGINE_TYPE — Derived from PROPTYPES.DATA_VALUE. The system property engine type value matched as compatible with the model's engine type.

The compatibility condition relies on the DECODE expression: when DEVl_PROJECT_ID equals 0, the effective engine type is taken from the FND_PROFILE value 'CZ_DEV_ENABLE_CONFIG_ENGINE'; otherwise, NVL(PROJ.CONFIG_ENGINE_TYPE, 'L') is used. This means a NULL project engine type defaults to 'L'. Matching then occurs against ENGTYPES.DATA_VALUE.

Common Use Cases and Queries

Typical uses include engine-type compatibility validation, migration preparation, and troubleshooting of configurator model behavior across EBS 12.1.1 and 12.2.2. A representative query listing compatible engine types per model follows:

  • Enumerate all models and their compatible engine types: 
    SELECT model_id, sysprop_engine_type
FROM   apps.cz_model_prop_engtyp_compat_v
ORDER BY model_id, sysprop_engine_type;
  • Restrict output to a single development project: 
    SELECT sysprop_engine_type
FROM   apps.cz_model_prop_engtyp_compat_v
WHERE  model_id = :p_model_id;
  • Identify duplicated compatibility entries or unusual mappings using GROUP BY on both columns.

Because the view draws on profile-driven defaults, reports executing it should be aware that the result for MODEL_ID = 0 depends on the runtime value of CZ_DEV_ENABLE_CONFIG_ENGINE, which may vary by and across sessions.