Search Results mtl_desc_elem_val_interface_pk

Overview

MTL_DESC_ELEM_VAL_INTERFACE is an Inventory (INV) module table in the Oracle E-Business Suite database, valid in both 12.1.1 and 12.2.2. The ETRM documentation states explicitly that the object is "Not used currently," meaning it is a legacy or reserved interface table that no longer carries an active functional role in the standard Inventory application flow. Its descriptive name suggests it was originally intended as a staging or interface structure for descriptive element values associated with inventory items, a pattern historically used by the descriptive flexfield and item cataloging infrastructure. Because the table is documented as unused, it should be regarded as a residual schema object rather than an integration point for current development.

Under the heuristic Data Vault classification supplied in the metadata, the table is identified as standalone. In modeling terms, this suggests it is neither a true hub nor a link nor a satellite tied to a shared business key, but rather an isolated staging entity whose primary key combines an item identifier with an element name. Any Data Vault design would therefore treat it as a transient or source-aligned structure rather than a durable modeled component.

Key Information Stored

The documented physical schema contains 18 columns in the INV schema. The primary key, MTL_DESC_ELEM_VAL_INTERFACE_PK, is a composite of INVENTORY_ITEM_ID and ELEMENT_NAME. That composite is the only documented uniqueness constraint, so both columns serve simultaneously as the surrogate composite key and the business-key candidates in this staging context.

• INVENTORY_ITEM_ID — identifier of the inventory item to which the descriptive element value applies; first component of the composite primary key.
• ELEMENT_NAME — name of the descriptive element being staged; second component of the composite primary key.
• ELEMENT_VALUE — the value assigned to the descriptive element for the referenced item.
• DEFAULT_ELEMENT_FLAG — indicates whether the element value represents the default for the item.
• ELEMENT_SEQUENCE — ordering attribute for the element value within its item context.
• ITEM_NUMBER — denormalized item number accompanying the item identifier.
• PROCESS_FLAG — status indicator used by interface processing routines.
• SET_PROCESS_ID — identifier grouping records processed together in a single run.
• TRANSACTION_ID — transaction reference associated with the staged record.
• REQUEST_ID — concurrent request that created or last processed the row.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard concurrent program context columns.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Who columns present on essentially all INV transactional and interface tables, supporting audit and multi-user change tracking.

Common Use Cases and Queries

Because the table is documented as not currently used, it is not a recommended target for new integrations. Practical activity centers on verification, cleanup, and data migration audits. A typical check confirms whether any rows remain from earlier patch levels or customizations:

• SELECT COUNT(*) FROM inv.mtl_desc_elem_val_interface; — confirms whether the table holds residual data in a given instance.
• SELECT inventory_item_id, element_name, element_value FROM inv.mtl_desc_elem_val_interface WHERE process_flag IS NULL; — identifies records never processed by the legacy interface routine.
• SELECT request_id, program_id, COUNT(*) FROM inv.mtl_desc_elem_val_interface GROUP BY request_id, program_id; — attributes historical rows to the concurrent programs that populated them.
• Post-upgrade reconciliation before archiving the table in 12.2.2 environments.
• Impact analysis when developers discover the table by name and mistakenly assume it is an active interface.

Sample join pattern for validation against the item master would be through INVENTORY_ITEM_ID to MTL_SYSTEM_ITEMS_B, although no foreign key is documented.

Related Objects

The metadata classifies this object as standalone, and no formal foreign keys are documented. The most significant logical relationships are:

• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID; the authoritative item definition.
• MTL_SYSTEM_ITEMS_TL — joined on INVENTORY_ITEM_ID and the language columns for translated item descriptions.
• MTL_ITEM_ATTRIBUTES — additional item-level attribute storage keyed by INVENTORY_ITEM_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to resolve the programs that processed the interface rows.
• FND_APPLICATION — joined on PROGRAM_APPLICATION_ID for program context.
• MTL_DESCRIPTIVE_ELEMENTS and related descriptive element definition tables — logical counterparts that define ELEMENT_NAME semantics.
• MTL_INTERFACE_ERRORS — analogous interface error repository for Inventory item interfaces.

Developers should confirm current usage against the specific instance, since custom extensions occasionally repurpose dormant interface tables.