Search Results mtl_descr_element_values




Overview
Explore in AI Chat

Overview

MTL_DESCR_ELEMENT_VALUES is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the descriptive element values assigned to a particular inventory item. In EBS, descriptive elements provide the mechanism by which flexible, user-defined item attributes — commonly known as item descriptive flexfields and, more broadly, the "Item Attributes" descriptive framework — are captured and persisted at the item level. Each row represents a single element value for a single item, making the table the authoritative store for the descriptive element layer of the item master.

The documented primary key is MTL_DESCR_ELEMENT_VALUES_PK, defined on the column pair (INVENTORY_ITEM_ID, ELEMENT_NAME). A matching unique index, MTL_DESCR_ELEMENT_VALUES_U1, exists on the same two columns. From a Data Vault modeling perspective, the metadata suggests a standalone classification. In practice, the (INVENTORY_ITEM_ID, ELEMENT_NAME) key structure and the presence of CREATED_BY/LAST_UPDATED_BY audit columns make this table a natural satellite candidate keyed to an inventory item hub, with ELEMENT_NAME acting as a partial descriptive discriminator rather than a purely technical hub key. The schema is owned by INV and contains 14 documented columns.

Key Information Stored

The table's identity is anchored by two business-meaningful key columns. INVENTORY_ITEM_ID identifies the item to which the descriptive element belongs and aligns with the surrogate item key used throughout the Inventory schema. ELEMENT_NAME identifies the specific descriptive element being valued, functioning together with INVENTORY_ITEM_ID as the composite primary key and unique business key.

  • INVENTORY_ITEM_ID — the item identifier; part of the composite primary key and unique index.
  • ELEMENT_NAME — the descriptive element name; the second component of the primary key.
  • ELEMENT_VALUE — the actual value stored for the named element for that item.
  • DEFAULT_ELEMENT_FLAG — indicates whether the element value is the default for the item.
  • ELEMENT_SEQUENCE — controls display or processing order of the element.
  • CREATED_BY, CREATION_DATE — standard Who column audit of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Who column audit of the last modification.
  • LAST_UPDATE_LOGIN — login context of the last update.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context capturing which request and program last touched the row.

The primary key is documented as a composite business key on (INVENTORY_ITEM_ID, ELEMENT_NAME); there is no separate surrogate ID column documented, and MTL_DESCR_ELEMENT_VALUES_U1 enforces its uniqueness.

Common Use Cases and Queries

Typical usage retrieves the descriptive element values for reporting, interface extraction, and validation of item descriptive data. A representative query joining to the item master to surface element values by item number follows.

  • Retrieve all element values for a given item: SELECT element_name, element_value FROM mtl_descr_element_values WHERE inventory_item_id = :item_id;
  • Find items carrying a specific element value: SELECT inventory_item_id FROM mtl_descr_element_values WHERE element_name = :name AND element_value = :value;
  • Join to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID to report descriptive values alongside segment1 item numbers.
  • Identify default element values using DEFAULT_ELEMENT_FLAG in configuration audits.
  • Trace concurrent program changes via REQUEST_ID and PROGRAM_ID for reconciliation.

Related Objects

The table is documented as standalone with no enforced foreign-key relationships in the metadata, but it participates logically with the following objects.

  • MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID; the item master defining each item.
  • MTL_SYSTEM_ITEMS_TL — item descriptions and translated names keyed by INVENTORY_ITEM_ID.
  • MTL_DESCR_ELEMENTS — defines the ELEMENT_NAME values that this table instantiates per item.
  • MTL_ITEM_ATTRIBUTES — complements descriptive element storage with attribute-level item data.
  • MTL_ITEM_CATEGORIES and MTL_ITEM_LOCATIONS — commonly reported alongside descriptive element values for item context.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — where descriptive elements are backed by value sets for validation.
  • INV_ITEM_API (PL/SQL) — item maintenance interface that can populate descriptive element values.