Search Results mtl_units_of_measure_vl




Overview
Explore in AI Chat

Overview

MTL_UNITS_OF_MEASURE_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite, classified under the INV (Inventory) product family and reported as VALID in both release 12.1.1 and 12.2.2. The view presents the translatable columns of the Units of Measure entity for the language currently in session, resolving the base multilingual table MTL_UNITS_OF_MEASURE_TL through a language filter. In Oracle EBS the "_VL" suffix designates a "view language" object: a view that combines language-independent data with the single translation row matching the user's runtime language rather than exposing every installed translation.

Because it is defined over the translation table only, MTL_UNITS_OF_MEASURE_VL behaves as a language-filtered projection, not a master-detail join. It exposes both technical attributes (UOM_CODE, UOM_CLASS, BASE_UOM_FLAG) and descriptive attributes (UNIT_OF_MEASURE_TL, DESCRIPTION) for the units of measure defined in the Inventory application. This makes it the conventional reporting and integration access point for UOM lookups, since a join to the underlying _TL table would otherwise require handling multiple language rows per UOM.

Underlying Base Objects

The ETRM metadata records a single referenced base object: the synonym MTL_UNITS_OF_MEASURE_TL, which resolves to the APPS-owned table of the same name. The view is defined with a predicate of the form WHERE LANGUAGE = USERENV('LANG'), so it returns only those translation rows whose LANGUAGE matches the language environment of the database session at query time. Unlike many _VL views in EBS, this view does not join back to a language-independent base table; the translation table itself carries the UOM_CODE, UOM_CLASS, BASE_UOM_FLAG and the descriptive flexfield attribute columns, so the view can be used standalone.

Key Columns

  • UOM_CODE — the internal, language-independent primary key for a unit of measure; this is the value stored on transactional tables such as MTL_TRANSACTIONS and MTL_SYSTEM_ITEMS.
  • UNIT_OF_MEASURE_TL — the translated unit of measure name as displayed to the user in the current session language.
  • UNIT_OF_MEASURE — the base unit of measure designation associated with the record.
  • UOM_CLASS — the class to which the UOM belongs (for example Quantity, Weight, Volume, Time), used in UOM conversions to ensure like-for-like conversion.
  • BASE_UOM_FLAG — indicates whether the unit is the base unit for its class.
  • DESCRIPTION — the translated descriptive text for the unit of measure.
  • DISABLE_DATE — the date the unit of measure was disabled, allowing filters to exclude obsolete UOMs.
  • LANGUAGE / SOURCE_LANG — the installed language of the returned translation row and the source language of the entity.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN; plus REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID and PROGRAM_UPDATE_DATE for concurrent program auditability.

Common Use Cases and Queries

The view is used to present UOM descriptions alongside transactional or item data, to validate that a UOM code exists, and to filter UOMs by class in reporting and interfaces. A typical lookup follows.

  • List all enabled UOMs by class:
    SELECT uom_code, unit_of_measure_tl, uom_class FROM mtl_units_of_measure_vl WHERE uom_class = 'Quantity' AND (disable_date IS NULL OR disable_date > SYSDATE);
  • Resolve a UOM code to its translated name:
    SELECT unit_of_measure_tl FROM mtl_units_of_measure_vl WHERE uom_code = :p_uom_code;
  • Report item transactions with UOM description:
    SELECT t.transaction_id, t.inventory_item_id, t.transaction_uom, v.unit_of_measure_tl FROM mtl_material_transactions t, mtl_units_of_measure_vl v WHERE v.uom_code = t.transaction_uom;

Because results depend on USERENV('LANG'), reports and interfaces should be run in a language environment consistent with the expected output, and any programmatic extraction intended to be language-neutral should reference UOM_CODE rather than the translated name.