Results for “mtl_uom_classes_tl”

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

Overview

MTL_UOM_CLASSES_TL is the translation (TL) table for unit of measure classes in Oracle E-Business Suite Inventory (INV). It stores the language-specific, descriptive attributes of unit of measure classes, while its base counterpart MTL_UOM_CLASSES holds the language-independent definition. In Oracle EBS 12.1.1 and 12.2.2, unit of measure classes provide the top-level grouping for related units of measure — for example, Quantity, Weight, Volume, or Time — and are referenced throughout purchasing, order management, shipping, manufacturing, and inventory transactions. The _TL table exists primarily to support Oracle's Multi-Language Support (MLS) architecture, allowing each UOM class definition to carry translated names and descriptions in every installed language.

From a heuristic Data Vault modeling perspective, MTL_UOM_CLASSES_TL can be classified as a satellite. It does not represent an independent business entity; instead it hangs off the same business key (UOM_CLASS) as the base classes table and adds descriptive, language-dependent context. The documented physical schema confirms this role: the primary key is composite and the columns are largely descriptive plus standard Oracle audit attributes.

Key Information Stored

The table is defined in the INV schema and contains 32 documented columns. The most significant are:

• UOM_CLASS — the base unit of measure class identifier and the leading column of the primary key. Together with LANGUAGE it forms MTL_UOM_CLASSES_TL_PK.
• LANGUAGE — the language code for the row, the second component of the primary key. It determines which translation this record represents.
• UOM_CLASS_TL — the translated name of the unit of measure class in the specified language.
• SOURCE_LANG — the language in which the source (base) text was originally entered; the language of the originating row.
• DESCRIPTION — the translated descriptive text for the class.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle flexfield (descriptive) columns available for extending the record without schema changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle who-audit columns tracking record creation and modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit context captured when the row was inserted or updated by a request.
• DISABLE_DATE — indicates when a translation row is no longer active.
• ZD_EDITION_NAME — the editioning column used by Oracle's Online Patching/edition-based redefinition framework in 12.2. The unique index MTL_UOM_CLASSES_TL_U1 (UOM_CLASS, LANGUAGE, ZD_EDITION_NAME) reflects this edition-aware business key.

Note the distinction between the physical primary key (UOM_CLASS, LANGUAGE) and the business-key candidate expressed by the unique index (UOM_CLASS, LANGUAGE, ZD_EDITION_NAME), the latter required because the editioning column participates in uniqueness during patching.

Common Use Cases and Queries

The most frequent requirement is retrieving a translated unit of measure class name for a given language. Queries typically join the translation to the base table on UOM_CLASS, filtering by LANGUAGE or using the language validation functions to fall back to the base-language row when a translation is missing. A representative pattern selects UOM_CLASS_TL and DESCRIPTION by joining MTL_UOM_CLASSES_TL to MTL_UOM_CLASSES on UOM_CLASS and equating LANGUAGE to the session or report language, or to USERENV('LANG').

Reporting use cases include multilingual pick lists for UOM setup forms, inventory valuation reports grouped by class, purchasing and receiving documentation generated in the user's language, and data migration scripts that load translations alongside base class definitions. Because the table is edition-aware in 12.2, queries against it should respect the editioning column when run under Online Patching contexts, and DBA-style extraction should include ZD_EDITION_NAME to avoid duplicate rows. Developers frequently use this table when building custom concurrent programs that generate UOM class terminology in locale-specific output.

Related Objects

The metadata classifies this table heuristically as standalone, meaning no explicit foreign keys are mined; the relationships that matter are functional and store-based. The most significant related objects are:

• MTL_UOM_CLASSES — the base-language parent table; join on UOM_CLASS to obtain the underlying class definition and to enforce consistency.
• MTL_UNITS_OF_MEASURE — units grouped by UOM_CLASS, the primary consumer of UOM class definitions.
• MTL_UOM_CONVERSIONS — conversion relationships defined within a UOM class; class context comes from the classes table.
• MTL_SYSTEM_ITEMCATEGORIES / inventory item tables — items reference units of measure that ultimately resolve to a class, connecting the translation table to item reporting.
• FND_LANGUAGES — the language master validated by the LANGUAGE and SOURCE_LANG columns.
• FND_APPLICATION / FND_CONCURRENT_PROGRAMS — referenced by PROGRAM_APPLICATION_ID and PROGRAM_ID for the concurrent audit columns.

Because the table is a translation satellite, most application logic and forms read it indirectly through the base MTL_UOM_CLASSES view logic rather than through direct DML; writes are governed by the MLS API mechanisms and the Who columns.