Search Results num_value_flag

Overview

APPS.CZ_MODEL_LOGICSTATE_PROPS_LKV is a configuration-management view within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It exposes the set of property definitions that apply to the logic-state node of a configuration model, joining the lookup values that carry the SYSPROPVALS_LOGIC_STATE list to the configuration engine type associated with each development project. The view is a key component of the Oracle Configurator / CZ development schema, where the configuration engine interprets a model's logic state and the values that constrain it at runtime.

The view's name reflects its purpose: it presents logic-state properties ("LKV" denoting a lookup-value-derived key view) scoped per model. Notably, the alias NUM_VALUE_FLAG is assigned to the base column NULL_VALUE_FLAG, which is the column a user would encounter when searching for "num_value_flag." This aliasing is significant because consumers of the view reference the flag by the alias, not the underlying column name. The view is defined with a UNION ALL of two branches: one returning properties for each development project in CZ_DEVL_PROJECTS, and a second branch returning a synthetic model with p_model_id = -1, representing a default or system-level logic-state property set.

Underlying Base Objects

The view is defined over five documented base objects. CZ_LOOKUP_VALUES_VL is the primary source of lookup rows, restricted to list_name = 'SYSPROPVALS_LOGIC_STATE' via the LSPTYPES alias, and it also supplies the engine-type rows via the ENGTYPES alias (list_name = 'CZ_ENGINE_TYPES'). CZ_TYPE_RELATIONSHIPS links the logic-state property type to its owning subject type through rel_type_code = 'LSP', with object_type matched to the property's numeric_id_value and subject_type matched to the engine type's numeric_id_value. CZ_DEVL_PROJECTS supplies the model identity and the engine-type configuration. The FND_PROFILE package is invoked through fnd_profile.value_wnps('CZ_DEV_ENABLE_CONFIG_ENGINE') to resolve the engine type for the system default project (id 0) when no explicit configuration engine type is set.

Surrogate synonyms (CZ_LOOKUP_VALUES, CZ_TYPE_RELATIONSHIPS, CZ_DEVL_PROJECTS) resolve to the same underlying CZ tables. Deleted rows are excluded in both CZ_TYPE_RELATIONSHIPS and the engine-type lookup through deleted_flag = '0'.

Key Columns

• P_MODEL_ID — Derived from CZ_DEVL_PROJECTS.DEVL_PROJECT_ID; identifies the configuration model to which the property applies. The second UNION ALL branch emits -1 for the default property set.
• LIST_NAME — Constant 'SYSPROPVALS_LOGIC_STATE', the lookup list that supplies logic-state property values.
• DATA_VALUE — The property value's coded representation.
• VALUE_SEQ — Display/processing sequence of the value.
• DATA_TYPE_ID — Reference to the data type of the property value.
• NUM_VALUE_FLAG — Aliased from LSPTYPES.NULL_VALUE_FLAG; indicates whether a null numeric value is permitted for the property. This is the column most commonly referenced by the alias when the view is queried.
• VALUE_LABEL — User-facing label for the property value.
• VALUE_DESCRIPTION — Descriptive text for the property value.
• NUMERIC_ID_VALUE — Internal numeric identifier used to join to CZ_TYPE_RELATIONSHIPS.OBJECT_TYPE.

Common Use Cases and Queries

The view is typically used to enumerate the logic-state properties available to a given configuration model, to drive pick lists or validation logic, or to audit engine-type configuration across projects. A representative query filtering on the aliased flag is:

SELECT p_model_id, list_name, data_value, value_seq,
       data_type_id, num_value_flag, value_label, value_description
  FROM apps.cz_model_logicstate_props_lkv
 WHERE num_value_flag = 'N'
 ORDER BY p_model_id, value_seq;

To inspect the properties assigned to a specific model, constrain by p_model_id. To compare project-specific properties against the system default (id -1), aggregate by p_model_id. Because the view resolves engine types through FND_PROFILE and the CZ type-relationship tables, results reflect the configuration engine enabled for each project at query time, making the view appropriate for diagnostics of configuration engine behavior.