Search Results item_attribute_validation

Overview

APPS.MTL_ITEM_ATTRIBUTES_V is a supplementary Oracle E-Business Suite view defined over the item attribute framework in Oracle Inventory. It is registered in FND Design Data as INV.MTL_ITEM_ATTRIBUTES_V and carries a status of VALID in both 12.1.1 and 12.2.2. Oracle classifies it explicitly as a "supplementary view used to simplify forms coding," and the documented metadata includes the standing warning that Oracle does not recommend querying or altering data through this view because its definition may change dramatically in subsequent minor or major releases.

The view presents descriptive metadata about the configurable item attributes themselves rather than transactional item data. Each row describes a single attribute descriptor — its internal name, the user-facing prompt, the attribute group it belongs to, its control level, validation behavior, and up to four associated lookup definitions. This makes the view a catalog of the attribute model used by the item master and item attribute forms, and it is the object that surfaces columns such as ENABLED_FLAG4.

Underlying Base Objects

The documented base objects for this view are MFG_LOOKUPS (a view) and MTL_ITEM_ATTRIBUTES (referenced through a synonym). MTL_ITEM_ATTRIBUTES is the core repository of item attribute definitions and values in Oracle Inventory; MFG_LOOKUPS supplies the lookup type and code semantics used by the LOOKUP_TYPE1–4, LOOKUP_CODE1–4, MEANING1–4, and ENABLED_FLAG1–4 column families. The view joins or projects these sources to produce a form-friendly shape that concatenates attribute descriptor data with resolved lookup information, avoiding the need for the form layer to join the base objects directly.

Key Columns

• ROW_ID — ROWID pseudo-column identifying the row.
• ATTRIBUTE_NAME / USER_ATTRIBUTE_NAME / USER_ATTRIBUTE_NAME_GUI — the internal attribute name and its user-facing prompt variants.
• ATTRIBUTE_GROUP_ID / ATTRIBUTE_GROUP_ID_GUI — grouping of attributes for display on the item form.
• CONTROL_LEVEL — the level at which the attribute is controlled (for example master item versus organization).
• DATA_TYPE, SEQUENCE, SEQUENCE_GUI — value type and display ordering.
• LEVEL_UPDATEABLE_FLAG, STATUS_CONTROL_CODE — whether the attribute can be updated at its level and its status control behavior.
• MANDATORY_FLAG, PREFIELD_FLAG, POST_CHANGE_FLAG, POST_FIELD_FLAG — form behavior flags.
• VALIDATION_CODE, UPDATE_MESSAGE_NAME, REQUIRED_MESSAGE_NAME — validation logic and the messages raised on update or when required.
• LOOKUP_TYPE1–4, LOOKUP_CODE1–4, MEANING1–4, ENABLED_FLAG1–4 — up to four lookup associations per attribute. ENABLED_FLAG4 is the enablement flag for the fourth lookup slot; a value of Y indicates the associated lookup code is active and selectable, while N or null indicates it is not enabled.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Because the view resolves attribute descriptors and lookup enablement in a single object, it is frequently used to audit which attributes are exposed and which lookup values are currently enabled on the item form.

• Listing all attributes where the fourth lookup slot is enabled:
  SELECT attribute_name, user_attribute_name, lookup_type4, enabled_flag4 FROM apps.mtl_item_attributes_v WHERE enabled_flag4 = 'Y';
• Auditing attribute group membership and control level for a specific group:
  SELECT attribute_name, control_level, mandatory_flag FROM apps.mtl_item_attributes_v WHERE attribute_group_id = :group_id;
• Reviewing validation and mandatory message configuration across all attributes.

Given Oracle's explicit warning, this view is best treated as a read-only reference for diagnostics and analysis rather than as a supported integration interface. For production integrations, the documented base objects MTL_ITEM_ATTRIBUTES and MFG_LOOKUPS should be used directly, since the column set and shape of MTL_ITEM_ATTRIBUTES_V may change between releases.