Search Results wip_preference_values

Overview

WIP_PREFERENCE_VALUES is a Work in Process (WIP) module table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. As its name implies, the table stores the discrete preference values that are associated with WIP preference definitions. WIP preferences drive the configurable behaviour of the shop floor — controlling how transactions, backflush operations, scheduling, and move/complete activities are processed for a given level or context within the manufacturing organisation. Rather than hard-coding these behaviours, Oracle WIP externalises them into preferences, and the actual value assigned to each preference is held in this table. The object is owned by the WIP schema and is classified as VALID in the ETRM repository, with a documented physical schema of 13 columns in release 12.2.2.

From a data-modelling perspective, the ETRM metadata returns a heuristic Data Vault classification of standalone for this table, with no downstream foreign keys mined from the schema. In Data Vault terms this suggests the table behaves primarily as a satellite or reference-attribute store, capturing descriptive preference-value detail that hangs off the parent preference and level entities rather than acting as a hub or a link between business keys. This classification should be treated as a modelling suggestion, not a documented fact, since it is derived heuristically from the FK structure.

Key Information Stored

The table's documented columns capture the identity, context, and value of each preference entry. The most operationally significant columns are:

• PREFERENCE_VALUE_ID — the surrogate primary key for each preference value row, and a component of the unique index WIP_PREFERENCE_VALUES_U1.
• PREFERENCE_ID — foreign reference to the parent preference definition; identifies which preference this value belongs to.
• LEVEL_ID — foreign key to MSD_LEVELS, defining the organisational level (for example, a specific level within the MSD level hierarchy) at which the preference value applies.
• SEQUENCE_NUMBER — ordering attribute controlling the evaluation or presentation sequence of the value within its preference.
• ATTRIBUTE_NAME — the name of the attribute whose value is being set, allowing a preference to carry multiple named attribute-value pairs.
• ATTRIBUTE_VALUE_CODE — the actual coded value assigned to the named attribute.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit (WHO) columns tracking record creation and modification.
• ZD_EDITION_NAME — the editioning column supporting Online Patching in 12.2.x, and a component of the unique index WIP_PREFERENCE_VALUES_U1.

The unique index WIP_PREFERENCE_VALUES_U1 on (PREFERENCE_VALUE_ID, ZD_EDITION_NAME) is the business-key candidate: PREFERENCE_VALUE_ID is unique within an edition, which is the standard EBS 12.2 editioning pattern. The audit columns are informational rather than key-bearing.

Common Use Cases and Queries

This table is primarily queried to determine which preference values are in effect for a given preference and level, and to audit changes to shop-floor configuration. Typical reporting and diagnostic scenarios include:

• Listing all values for a specific preference and level:

SELECT pv.preference_value_id, pv.preference_id, pv.level_id,
       pv.sequence_number, pv.attribute_name, pv.attribute_value_code
FROM   wip.wip_preference_values pv
WHERE  pv.preference_id = :preference_id
AND    pv.level_id      = :level_id
ORDER BY pv.sequence_number;

• Joining to MSD_LEVELS to resolve the level name for each value: joining on pv.level_id = l.level_id exposes the human-readable level in preference reports.
• Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who altered a preference value.
• Reconciling preferences across editions in 12.2.x by filtering on ZD_EDITION_NAME.

Related Objects

The following objects are most significant in relation to WIP_PREFERENCE_VALUES:

• MSD_LEVELS — referenced by the documented foreign key WIP_PREFERENCE_VALUES.LEVEL_ID → MSD_LEVELS.LEVEL_ID; resolves the level context of each value.
• WIP_PREFERENCES — the parent preference definition table; joined via PREFERENCE_ID to obtain the preference name and description.
• WIP_PARAMETERS — parameters associated with WIP preferences and their values.
• WIP_DISCRETE_JOBS — job records whose processing behaviour is governed by the effective preference values.
• WIP_ENTITIES — the base WIP entity table whose shop-floor transactions consume preference settings.
• WIP_TRANSACTIONS — transaction records influenced by preference configuration such as backflush and move rules.
• FND_LOOKUP_VALUES — often the source of the coded values stored in ATTRIBUTE_VALUE_CODE.

Together these objects form the configuration and execution layer through which WIP preferences are defined, valued at specific levels, and then applied during manufacturing transactions.