Search Results wip_preference_values_u1

Overview

WIP.WIP_PREFERENCE_VALUES is a Work in Process (WIP) schema table that stores the individual attribute values belonging to WIP preference definitions. In Oracle EBS 12.1.1 and 12.2.2, WIP preferences drive defaulting, validation, and behavioral rules across discrete manufacturing transactions such as work order creation, material issue, move, and completion. A single preference header is decomposed into one or more rows in WIP_PREFERENCE_VALUES, each carrying a named attribute and its coded value, optionally scoped by level and ordered by sequence.

Under heuristic Data Vault modeling, this table is classified as standalone. Although it participates in a foreign key relationship to MSD_LEVELS on LEVEL_ID, it does not itself function as a hub, link, or satellite in the mined dependency graph. Modelers should therefore treat it as a standalone descriptive entity rather than a core integration point.

Per Oracle's standard notice, this object is designated for internal use only and is not supported for direct access except through standard Oracle Applications programs. It resides in the APPS_TS_TX_DATA tablespace, reflecting its transactional data storage role.

Key Information Stored

The table comprises 13 documented columns. The most significant are summarized below:

• PREFERENCE_VALUE_ID — Surrogate primary key. It is the leading column of the unique index WIP_PREFERENCE_VALUES_U1 and uniquely identifies each preference value row.
• PREFERENCE_ID — Identifier of the parent preference header. Together with LEVEL_ID, ATTRIBUTE_NAME, and SEQUENCE_NUMBER, it forms the nonunique index WIP_PREFERENCE_VALUES_N1, which supports retrieval of all values for a given preference.
• LEVEL_ID — Level identifier scoping the preference value. This column participates in the documented foreign key to MSD_LEVELS.
• SEQUENCE_NUMBER — Ordering value that governs the sequence in which multiple values are applied or evaluated.
• ATTRIBUTE_NAME — The named attribute (VARCHAR2(30)) for which a value is being supplied.
• ATTRIBUTE_VALUE_CODE — The coded value (VARCHAR2(80)) assigned to the attribute.
• OBJECT_VERSION_NUMBER — 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 — Standard Who columns that capture audit ownership and timestamps.
• ZD_EDITION_NAME — Editioning column documented in the 12.2.2 physical schema. It participates in the business-key unique index WIP_PREFERENCE_VALUES_U1 alongside PREFERENCE_VALUE_ID, supporting the Edition-Based Redefinition (EBR) architecture introduced in 12.2.

Note that the business-key candidate is the composite WIP_PREFERENCE_VALUES_U1 (PREFERENCE_VALUE_ID, ZD_EDITION_NAME), while PREFERENCE_VALUE_ID remains the surrogate primary key.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include:

• Listing all attribute values for a specific preference header to audit configuration or compare environments.
• Joining to MSD_LEVELS to translate LEVEL_ID into a human-readable level name.
• Extracting the current effective value for a given attribute name, ordered by SEQUENCE_NUMBER.

Representative query patterns follow:

• SELECT PREFERENCE_VALUE_ID, PREFERENCE_ID, LEVEL_ID, SEQUENCE_NUMBER, ATTRIBUTE_NAME, ATTRIBUTE_VALUE_CODE FROM WIP.WIP_PREFERENCE_VALUES WHERE PREFERENCE_ID = :preference_id ORDER BY SEQUENCE_NUMBER;
• SELECT v.ATTRIBUTE_NAME, v.ATTRIBUTE_VALUE_CODE, l.LEVEL_NAME FROM WIP.WIP_PREFERENCE_VALUES v, MSD.MSD_LEVELS l WHERE v.LEVEL_ID = l.LEVEL_ID AND v.PREFERENCE_ID = :preference_id;
• SELECT ATTRIBUTE_VALUE_CODE FROM WIP.WIP_PREFERENCE_VALUES WHERE PREFERENCE_ID = :preference_id AND ATTRIBUTE_NAME = :attr ORDER BY SEQUENCE_NUMBER;

Because the table is flagged Oracle Internal Use Only, queries should be treated as read-only investigative or reporting activity rather than a supported integration surface.

Related Objects

The most significant related objects, based on the documented dependencies, include:

• MSD_LEVELS — Referenced via the foreign key WIP_PREFERENCE_VALUES.LEVEL_ID → MSD_LEVELS.LEVEL_ID, providing level definition context.
• WIP_PREFERENCE_VALUES (synonym/view in APPS) — The APPS schema synonym exposes the WIP base table for application-level access.
• WIP preference header tables — The parent preference definition table joined on PREFERENCE_ID, providing the header context for each value.
• WIP discrete manufacturing transaction APIs — Standard WIP programs that read preference values to drive defaulting and validation during work order processing.
• FND Design Data objects — Metadata registrations under WIP.WIP_PREFERENCE_VALUES that govern application framework behavior.

These relationships position WIP_PREFERENCE_VALUES as a configuration-supporting table rather than a transactional hub, consistent with its standalone Data Vault classification.