Search Results unit_of_measure_name




Overview
Explore in AI Chat

Overview

APPS.INVFV_UNITS_OF_MEASURE is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered in Oracle Application Object Library design data under the identifier INV.INVFV_UNITS_OF_MEASURE and holds a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes the definitions of units of measure (UOM) maintained within Oracle Inventory, presenting each unit of measure alongside its class, base-unit designation, description, effective end date, and standard audit columns.

Because it is a view rather than a table, INVFV_UNITS_OF_MEASURE provides a read-only, denormalized presentation layer over the Oracle Inventory unit-of-measure setup. It is intended primarily for reporting, business intelligence extraction, and integration scenarios where an external system or a custom report needs a stable, queryable interface to UOM definitions without navigating the underlying Inventory tables and their foreign-key relationships directly. The view is particularly relevant to searches for unit_of_measure_name, since UNIT_OF_MEASURE_NAME is the primary descriptive column exposed.

Underlying Base Objects

The ETRM metadata documents that APPS.INVFV_UNITS_OF_MEASURE references the following objects in the APPS schema:

  • MTL_UNITS_OF_MEASURE (referenced through a synonym) — the base table storing unit-of-measure records, including the UOM name, code, and class assignment.
  • MTL_UOM_CLASSES (referenced through a synonym) — the base table storing unit-of-measure class definitions, used to classify units (for example, quantity, weight, volume, or time).

The view joins these two objects to combine the individual unit-of-measure record with its class information. The metadata further states that APPS.INVFV_UNITS_OF_MEASURE is not referenced by any other database object, confirming that it functions strictly as a consumer of base data rather than as a dependency for other views or packages. This dependency direction means changes to the base tables propagate into the view, while no downstream object is affected if the view is modified.

Key Columns

The view exposes the following columns, as documented in the ETRM metadata:

  • UNIT_OF_MEASURE_NAME (VARCHAR2, 25) — the descriptive name of the unit of measure, such as Each, Dozen, Kilogram, or Liter. This is the column most commonly targeted when searching for a unit of measure by name.
  • UOM_CODE (VARCHAR2) — the short code uniquely identifying the unit of measure within Oracle Inventory.
  • UOM_CLASS (VARCHAR2, 10) — the class to which the unit of measure belongs, derived from MTL_UOM_CLASSES.
  • _LA:BASE_UNIT_FLAG (CHAR, 47) — a flexfield-style descriptive segment indicating whether the unit is the base unit for its class. The _LA: prefix denotes a descriptive flexfield attribute exposed through the BIS view.
  • _DF (CHAR, 31) — a descriptive flexfield context column surfaced by the view.
  • END_EFFECTIVE_DATE (DATE) — the date on which the unit-of-measure definition ceases to be effective.
  • DESCRIPTION (VARCHAR2, 50) — free-text description of the unit of measure.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard Oracle EBS audit columns recording who created and last modified the record and when.

Common Use Cases and Queries

Typical uses of this view include validating UOM setup during data conversion, building listings of active units of measure for reporting, and joining unit-of-measure names to transactional data for readability. A straightforward query to retrieve all unit-of-measure definitions is:

SELECT UNIT_OF_MEASURE_NAME, UOM_CODE, UOM_CLASS, DESCRIPTION FROM APPS.INVFV_UNITS_OF_MEASURE;

To locate a specific unit by name, as prompted by the search term, a filtered query may be used:

SELECT UNIT_OF_MEASURE_NAME, UOM_CODE, UOM_CLASS FROM APPS.INVFV_UNITS_OF_MEASURE WHERE UNIT_OF_MEASURE_NAME = 'EACH';

Because the view does not expose organizational or inventory-specific attributes, it is best suited to setup-level reporting rather than on-hand or transaction-level analysis. For transactional reporting, the underlying MTL_UNITS_OF_MEASURE table is typically joined directly, while INVFV_UNITS_OF_MEASURE remains the preferred reference for unit-of-measure master data.