Search Results num_value_flag

Overview

CZ_MODEL_LOGICSTATE_PROPS_LKV is a read-only configuration view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CZ (Configurator) product family and exposes the property values that are valid for a given logic state within a Configurator development model. The "_LKV" suffix denotes a lookup value view, indicating that the underlying data originates from the Configurator lookup framework rather than from a dedicated transactional table.

The view plays a supporting role in Configurator modeling, reporting, and integration interfaces. It resolves the cross-reference between development projects, engine types, and the lookup list identified as SYSPROPVALS_LOGIC_STATE. Because Configurator models are frequently queried by external tools, extensions, and custom reports, this view provides a denormalized, query-optimized access path that shields consumers from the multi-table joins and decode logic embedded in the view definition.

Underlying Base Objects

The view is defined over the following documented base objects:

• CZ_DEVL_PROJECTS (SYNONYM) — supplies the development project identifier and the configuration engine type associated with each model.
• CZ_LOOKUP_VALUES_VL (VIEW) — the primary lookup value source aliased as LSPTYPES, joined on the list name SYSPROPVALS_LOGIC_STATE.
• CZ_LOOKUP_VALUES (SYNONYM) — aliased as ENGTYPES, providing engine types filtered by the CZ_ENGINE_TYPES list and DELETED_FLAG = '0'.
• CZ_TYPE_RELATIONSHIPS (SYNONYM) — aliased as TYPRELS, linking subject types to object types through the REL_TYPE_CODE 'LSP' relationship.
• FND_PROFILE (PACKAGE) — invoked via FND_PROFILE.VALUE_WNPS to supply the profile value CZ_DEV_ENABLE_CONFIG_ENGINE when the project identifier is zero.

The definition is a UNION ALL of two branches. The first branch joins lookup values to type relationships and development projects, using a DECODE against PROJ.DEVL_PROJECT_ID to determine the engine type: when the project ID is 0, the profile value is used; otherwise the project's CONFIG_ENGINE_TYPE is used, defaulting to 'L'. The second branch returns a synthetic P_MODEL_ID of -1 and links lookup values directly to type relationships where SUBJECT_TYPE = 1.

Key Columns

• P_MODEL_ID — the development project identifier; the second UNION branch emits -1 to represent a default or generic scope.
• LIST_NAME — always 'SYSPROPVALS_LOGIC_STATE' in this view, identifying the lookup list being exposed.
• DATA_VALUE — the stored data value of the lookup entry.
• VALUE_SEQ — the sequence number that orders values within the lookup list; this is the column most commonly searched by users querying on "value_seq".
• DATA_TYPE_ID — the data type classification for the value.
• NULL_VALUE_FLAG — aliased as NUM_VALUE_FLAG, indicating whether a null value is permitted.
• VALUE_LABEL and VALUE_DESCRIPTION — the display label and descriptive text for the value.
• NUMERIC_ID_VALUE — the numeric surrogate identifier used in the type relationship joins.

Common Use Cases and Queries

Typical uses include validating which property values are permitted for a logic state, ordering lookup values by sequence, and driving selection lists in custom Configurator extensions. A representative query that surfaces values ordered by the sequence column is:

SELECT P_MODEL_ID, DATA_VALUE, VALUE_SEQ, VALUE_LABEL
FROM   APPS.CZ_MODEL_LOGICSTATE_PROPS_LKV
WHERE  VALUE_SEQ IS NOT NULL
ORDER  BY P_MODEL_ID, VALUE_SEQ;

Analysts restricting output to a single model use:

SELECT * FROM APPS.CZ_MODEL_LOGICSTATE_PROPS_LKV
WHERE  P_MODEL_ID = :model_id;

Because the view is a UNION ALL over lookup and relationship data, queries should filter on P_MODEL_ID or VALUE_SEQ to limit row volume. The view is read-only; no DML should be issued against it. Access is governed by the standard APPS schema privileges granted through Configurator responsibility menus, and Oracle proprietary and confidential notice applies to the underlying metadata.