Search Results flm_ekb_preference_values




Overview
Explore in AI Chat

Overview

FLM_EKB_PREFERENCE_VALUES is a configuration table in the Oracle Flow Manufacturing (FLM) module. It stores the individual preference values that belong to a preference definition, providing the mechanism by which Flow Manufacturing captures, hierarchical, and evaluates user-defined selection criteria during manufacturing execution. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the FLM schema and is exposed through the Flow Manufacturing responsibility and through the Oracle E-Business Suite Integrated SOA Gateway when external systems must read preference configuration.

From a Data Vault modeling perspective, the documented heuristic classification is standalone. This is a modeling suggestion only: the table carries its own unique key and a foreign key to MSD_LEVELS, but the mined metadata does not identify a parent-link or satellite dependency within the FLM preference hierarchy, so it can be treated as an independent reference dimension rather than as a link or satellite.

Key Information Stored

  • PREFERENCE_VALUE_ID — surrogate primary key for each preference value row. Combined with ZD_EDITION_NAME it forms the unique index FLM_EKB_PREFERENCE_VALUES_U1, which is the business-key candidate documented for the table.
  • PREFERENCE_ID — identifies the parent preference to which the value belongs, linking the value back to its governing preference definition.
  • LEVEL_ID — foreign key to MSD_LEVELS. It anchors the preference value to a specific level in the level hierarchy, determining where the value applies.
  • SEQUENCE_NUMBER — ordering attribute used to evaluate or display multiple values in a deterministic sequence.
  • ATTRIBUTE_NAME and ATTRIBUTE_VALUE_CODE — the attribute being constrained and the coded value assigned to it; together they define the actual selection content of the preference value.
  • USAGE_LEVEL — indicates the usage context in which the value is honored.
  • ATTRIBUTE_ENABLE_FLAG — enables or disables the attribute value without deleting the row.
  • ZD_EDITION_NAME — the editioning discriminator introduced with the 12.2 online patching architecture; it participates in the unique key and supports edition-based redefinition.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide standard who-column auditing and optimistic locking.

Common Use Cases and Queries

Typical use cases include resolving which preference values apply to a given level, validating that no duplicate sequence exists within a preference, and providing configuration data to reports or interfaces that drive Flow Manufacturing selection logic.

  • Retrieve all values for a preference, ordered for evaluation: SELECT preference_value_id, level_id, sequence_number, attribute_name, attribute_value_code FROM flm_ekb_preference_values WHERE preference_id = :p_pref ORDER BY sequence_number;
  • Join to MSD_LEVELS to obtain level context: SELECT pv.preference_value_id, ml.level_name, pv.attribute_name, pv.attribute_value_code FROM flm_ekb_preference_values pv, msd_levels ml WHERE pv.level_id = ml.level_id AND pv.usage_level = :usage;
  • Validate sequencing and uniqueness per preference before deployment of a configuration change.
  • Extract enabled attribute values only, using ATTRIBUTE_ENABLE_FLAG, for downstream integration or SOA services.

Related Objects

  • MSD_LEVELS — directly referenced via the foreign key FLM_EKB_PREFERENCE_VALUES.LEVEL_ID → MSD_LEVELS; the primary external join.
  • FLM_EKB_PREFERENCES — the parent preference definition table referenced through PREFERENCE_ID; although the FK is not enumerated in the mined metadata, it is the natural parent for the value rows.
  • FLM_EKB_PREFERENCE_VALUE_TL — translation table, where present, supplying language-specific descriptive text for preference values.
  • FLM_EKB_PREFERENCE_VALUES_U1 — the unique index on (PREFERENCE_VALUE_ID, ZD_EDITION_NAME) that enforces the business key and must be accounted for in any concurrent load or purge operation.
  • FND_APPLICATION / FND_LOOKUP_VALUES — frequently joined when resolving lookup-backed ATTRIBUTE_VALUE_CODE values for reporting.

Because the table is classified as standalone, no cascading delete or link resolution is implied by the FK structure; purging preference values should be handled through the parent preference lifecycle rather than through the child row directly.