Results for “user_attribute_name_gui”

8 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MTL_ITEM_ATTR_FIELDS_V view is an Oracle E-Business Suite Inventory (INV) dictionary object owned by the APPS schema. ETRM documentation classifies this object with the description "10SC ONLY," indicating that its purpose is tightly coupled to a specific form or functional context rather than to general-purpose item reporting. The view exposes a mapping between GUI-facing user attribute names and the underlying database attribute names used on the item master, allowing forms and interfaces to translate the friendly label seen by a user into the internal column reference used to store the value.

In the Oracle EBS 12.1.1 and 12.2.2 environments, this view is not a general item data source. It does not return item attribute values themselves; rather, it returns metadata that describes which user attribute corresponds to which internal attribute identifier. Its structure is therefore best understood as a lookup or reference view sitting alongside item attribute definition logic.

Underlying Base Objects

The documented base object referenced by this view is MTL_ITEM_ATTRIBUTES, accessed through a synonym. MTL_ITEM_ATTRIBUTES is the core item attribute table in the Inventory module, storing attribute values at the organization-item level and forming the backbone of item master attribute storage. Because MTL_ITEM_ATTR_FIELDS_V is defined over this table through a synonym, it inherits the attribute naming conventions that Oracle applies to item attributes.

The view text confirms this relationship by selecting USER_ATTRIBUTE_NAME_GUI and ATTRIBUTE_NAME and then applying a large DECODE statement. The DECODE transforms raw ATTRIBUTE_NAME values such as MTL_SYSTEM_ITEMS.PRIMARY_UOM_CODE into the corresponding GUI-oriented internal names, for example MTL_SYSTEM_ITEMS.PRIMARY_UNIT_OF_MEASURE. The view is therefore a presentation mapping layered on top of the attribute definitions stored beneath MTL_ITEM_ATTRIBUTES.

Key Columns

  • USER_ATTRIBUTE_NAME_GUI — The GUI-facing name of the user attribute. This is the column most directly associated with the search term user_attribute_name_gui and is the primary output consumers retrieve when matching display labels to attributes.
  • ATTRIBUTE_NAME — The internal attribute identifier, decoded by the view into the alternate form used by the application where a GUI-specific name differs from the base column name.
  • Decoded attribute values — The DECODE expression maps numerous attribute names, including unit-of-measure attributes (PRIMARY_UOM_CODE, SECONDARY_UOM_CODE, WEIGHT_UOM_CODE, VOLUME_UOM_CODE, DIMENSION_UOM_CODE), descriptive flexfield references (DESC_FLEX to DF), and key foreign-key attributes such as BUYER_ID, HAZARD_CLASS_ID, ASSET_CATEGORY_ID, UN_NUMBER_ID, PICKING_RULE_ID, and ATP_RULE_ID. These mappings align internal column references with the descriptive names expected by the item definition GUI.

Common Use Cases and Queries

Because of its "10SC ONLY" designation, this view should be treated as a limited-purpose object. Typical uses include resolving GUI attribute labels to internal attribute identifiers during form personalization, conversion, or interface development, and troubleshooting discrepancies between what a user sees on the item master form and the underlying attribute name.

A basic query retrieves the GUI-to-internal mapping:

  • SELECT user_attribute_name_gui, attribute_name FROM apps.mtl_item_attr_fields_v;
  • SELECT user_attribute_name_gui, attribute_name FROM apps.mtl_item_attr_fields_v WHERE attribute_name LIKE 'MTL_SYSTEM_ITEMS.%UOM%';
  • SELECT user_attribute_name_gui, attribute_name FROM apps.mtl_item_attr_fields_v WHERE user_attribute_name_gui = :gui_label;

These queries are appropriate for metadata reconciliation and diagnostic purposes. They should not be relied upon as a substitute for querying actual item attribute values from MTL_SYSTEM_ITEMS or MTL_ITEM_ATTRIBUTES, since the view exposes field-name metadata rather than stored data.