Results for “model_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CZ_MODEL_PROP_ENGTYP_COMPAT_V view is a Configurator (CZ) object owned by the APPS schema in Oracle E-Business Suite. It resolves the runtime configuration engine type associated with a given Oracle Configurator development model (project). In Oracle Configurator, an engine type determines which rule-processing engine a model uses — for example, the Java-based engine versus a legacy engine — and the valid combinations of model, property, and engine type are governed by data held in the Configurator lookup and relationship tables.

The view is most frequently referenced in the context of the profile option CZ_DEV_ENABLE_CONFIG_ENGINE and the column CONFIG_ENGINE_TYPE on the development project. When a user searches for the term sysprop_engine_type, they are looking for the mechanism by which EBS determines which engine type a model's system property should report. This view is the documented query artifact that answers that question: it returns one row per development project (or per model identifier), exposing the effective engine type as the column SYSPROP_ENGINE_TYPE. It is therefore used in reporting, diagnostics, and integration logic that must confirm, audit, or default the engine assignment for a Configurator model.

Underlying Base Objects

The view is defined over four documented base objects, referenced through APPS synonyms, plus one PL/SQL package:

• CZ_DEVL_PROJECTS — the development project (model) records. Source of DEVL_PROJECT_ID (exposed as MODEL_ID) and CONFIG_ENGINE_TYPE.
• CZ_LOOKUP_VALUES — referenced twice in the definition, once as the PROPTYPES alias and once as the ENGTYPES alias. Both are restricted to LIST_NAME = 'CZ_ENGINE_TYPES', providing the data value and numeric identifier for engine types.
• CZ_TYPE_RELATIONSHIPS — holds the model-property/engine-type compatibility relationships, filtered by REL_TYPE_CODE = 'ETY', joining subject and object type identifiers.
• FND_PROFILE — the profile option package, invoked through FND_PROFILE.VALUE_WNPS('CZ_DEV_ENABLE_CONFIG_ENGINE') to supply the default engine type when the project identifier resolves to zero.

The joins stitch a project to its compatible engine type entries through the type-relationship table, with the two lookup aliases acting as the static lists of valid engine type values.

Key Columns

• MODEL_ID — aliases CZ_DEVL_PROJECTS.DEVL_PROJECT_ID. Identifies the Configurator development project/model. A value of 0 is a special case handled by the profile option decode.
• SYSPROP_ENGINE_TYPE — aliases CZ_LOOKUP_VALUES.DATA_VALUE from the PROPTYPES alias (restricted to CZ_ENGINE_TYPES). Represents the system property engine type that applies to the model. It is derived so that the effective value is:
  DECODE(MODEL_ID, 0, FND_PROFILE.VALUE_WNPS('CZ_DEV_ENABLE_CONFIG_ENGINE'), NVL(CONFIG_ENGINE_TYPE, 'L')), meaning model 0 falls back to the profile option, while a real model falls back to 'L' when CONFIG_ENGINE_TYPE is null.

Common Use Cases and Queries

Typical scenarios include auditing which engine type each model resolves to, diagnosing discrepancies between a model's stored CONFIG_ENGINE_TYPE and the valid engine list, and confirming the global engine setting for the shared (zero) model.

Retrieve the effective engine type for every model:

SELECT model_id, sysprop_engine_type
FROM   cz_model_prop_engtyp_compat_v
ORDER BY model_id;

Look up a specific model's engine type:

SELECT model_id, sysprop_engine_type
FROM   cz_model_prop_engtyp_compat_v
WHERE  model_id = :p_model_id;

List only models not using the default engine:

SELECT model_id, sysprop_engine_type
FROM   cz_model_prop_engtyp_compat_v
WHERE  sysprop_engine_type != 'L';

Because the effective value depends in part on FND_PROFILE.VALUE_WNPS, results reflect the current session's profile setting for CZ_DEV_ENABLE_CONFIG_ENGINE, making the view suitable for session-context-aware reporting and integration checks.