Search Results flm_ekb_preference_values_u1

Overview

FLM.FLM_EKB_PREFERENCE_VALUES is a transactional configuration table in the Oracle E-Business Suite Flow Manufacturing (FLM) schema that stores the individual attribute values associated with eKanban preferences. In the Oracle EBS 12.1.1 and 12.2.2 environments, eKanban (electronic Kanban) drives pull-based replenishment signals across the shop floor, and this table serves as the value-level detail layer that defines how each configured preference behaves at a given organizational or inventory level. One row represents a single preference attribute value, identified by a surrogate key and scoped to a preference, a level, and an edition.

From a data modeling perspective, the heuristic Data Vault classification for this object is satellite. Although the mined relationship data labels it as standalone because it carries no outgoing foreign keys other than the LEVEL_ID reference to MSD_LEVELS, the table's structure — descriptive attribute columns keyed to parent entities through PREFERENCE_ID and LEVEL_ID — is characteristic of a satellite attached to a preference hub. This classification should be treated as a modeling suggestion rather than a documented constraint.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• PREFERENCE_VALUE_ID — The surrogate primary key. It is the sole column of the unique index FLM_EKB_PREFERENCE_VALUES_U1, which is documented as (PREFERENCE_VALUE_ID, ZD_EDITION_NAME), making the pairing of identifier and edition name the effective business-key candidate.
• PREFERENCE_ID — The parent preference identifier. Together with LEVEL_ID it forms the leading columns of nonunique index FLM_EKB_PREFERENCE_VALUES_N1.
• LEVEL_ID — The level identifier scoping the value to an organizational or planning level; documented as a foreign key to MSD_LEVELS.
• SEQUENCE_NUMBER — Ordering control for how values are presented or evaluated.
• ATTRIBUTE_NAME — The name of the eKanban preference attribute being configured (VARCHAR2(30)).
• ATTRIBUTE_VALUE_CODE — The coded value assigned to that attribute (VARCHAR2(80)).
• ATTRIBUTE_ENABLE_FLAG — Numeric flag indicating whether the attribute is active.
• USAGE_LEVEL — Numeric indicator of the level at which the value applies.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) and PL/SQL APIs to detect concurrent updates.
• ZD_EDITION_NAME — Editioning discriminator (VARCHAR2(30)) supporting the 12.2 online patching (edition-based redefinition) architecture.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for audit and concurrency tracking.

Common Use Cases and Queries

Typical uses include auditing eKanban parameter configuration, replicating preference setups between environments, and diagnosing replenishment behavior when a Kanban signal does not fire as expected. A common reporting pattern joins values to their preferences and levels:

• List all values for a preference: SELECT ATTRIBUTE_NAME, ATTRIBUTE_VALUE_CODE, SEQUENCE_NUMBER FROM FLM.FLM_EKB_PREFERENCE_VALUES WHERE PREFERENCE_ID = :p_pref_id ORDER BY SEQUENCE_NUMBER;
• Resolve level context by joining LEVEL_ID to MSD_LEVELS.
• Correlate the N1 index columns (PREFERENCE_ID, LEVEL_ID) for efficient lookups by preference and level.
• Filter by ZD_EDITION_NAME when querying under online patching in 12.2.2.

Related Objects

Documented relationships and dependent objects include:

• FLM.FLM_EKB_PREFERENCE_VALUES# — The editioning view over the base table, referenced in dependencies.
• MSD_LEVELS — Referenced via LEVEL_ID, supplying the level definition used to scope preference values.
• FLM_EKB_PREFERENCE_VALUES_U1 — Unique index on PREFERENCE_VALUE_ID and ZD_EDITION_NAME.
• FLM_EKB_PREFERENCE_VALUES_N1 — Nonunique index on PREFERENCE_ID and LEVEL_ID.
• Parent eKanban preference definition tables in the FLM schema that supply PREFERENCE_ID, joined on that column.

The table does not reference any other database object beyond the documented LEVEL_ID association, and its physical storage resides in the APPS_TS_TX_DATA tablespace with indexes in APPS_TS_TX_IDX.