Search Results invfv_units_of_measure

Overview

INVFV_UNITS_OF_MEASURE is an Oracle E-Business Suite view owned by the APPS schema and registered to the Inventory (INV) product family. The object is documented in ETRM as status VALID and is explicitly classified as "Retrofitted," identifying it as a compatibility artifact carried forward to preserve the column and object naming conventions of earlier forms-based interfaces within the 12.1.1 and 12.2.2 code lines. It is defined with the READ ONLY clause, so it is intended exclusively for query and reporting access rather than DML.

The view presents the master list of units of measure (UOM) maintained in Inventory, combining each UOM with its governing UOM class. It serves as a reporting and integration surface for UOM lookups, validation lists, and cross-module references, including subinventory, item, and transaction-related reporting where a unit of measure must be resolved to its code, class, and descriptive attributes.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both accessed through synonyms, consistent with the APPS schema's standard synonym-based access pattern:

• MTL_UNITS_OF_MEASURE (SYNONYM) — aliased as UN; supplies the unit of measure records, the UOM code, class assignment, description, and audit columns.
• MTL_UOM_CLASSES (SYNONYM) — aliased as UO; supplies the UOM class definition and participates in the join condition UN.UOM_CLASS = UO.UOM_CLASS.

Because the join is written against the class column, only UOM records whose class exists in MTL_UOM_CLASSES are returned; orphaned or misclassified UOM rows are excluded.

Key Columns

The view exposes the following columns, with several presented through names that embed Oracle Forms/ETRM lookup directives:

• UNIT_OF_MEASURE_NAME — the unit of measure name, derived from MTL_UNITS_OF_MEASURE.UNIT_OF_MEASURE.
• UOM_CODE — the unique code identifying the unit of measure.
• UOM_CLASS — the class to which the UOM belongs.
• "_LA:BASE_UNIT_FLAG" — a Forms lookup-generated column sourced from UN.BASE_UOM_FLAG and resolved against the FND_LOOKUPS YES_NO lookup type, returning the meaning (Yes/No) indicating whether the UOM is the base unit of its class.
• END_EFFECTIVE_DATE — the disable date of the UOM, drawn from UN.DISABLE_DATE; a null value indicates the UOM remains active.
• DESCRIPTION — the descriptive text for the unit of measure.
• "_DF" — a descriptive flexfield placeholder column, derived from the INV:MTL_UNITS_OF_MEASURE context and associated with UN, exposing UOM descriptive flexfield segments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns inherited from MTL_UNITS_OF_MEASURE.

Common Use Cases and Queries

Typical uses include populating LOVs in custom concurrent programs, resolving UOM codes in extract files, and validating that a UOM is active before it is referenced in a transaction load. Because the view is READ ONLY, it is safe for ad hoc reporting and read-only integration layers.

Listing all active units of measure with their class and base-unit indicator:

• SELECT uom_code, unit_of_measure_name, uom_class, "_LA:BASE_UNIT_FLAG" base_uom_flag FROM apps.invfv_units_of_measure WHERE end_effective_date IS NULL ORDER BY uom_class, uom_code;

Filtering to the base units of each class, which is useful when defaulting transaction UOMs:

• SELECT uom_code, unit_of_measure_name, uom_class FROM apps.invfv_units_of_measure WHERE "_LA:BASE_UNIT_FLAG" = 'Yes' AND end_effective_date IS NULL;

Joining to item master data to display the primary UOM description requires selecting from the view into MTL_SYSTEM_ITEMS, matching on the UOM code. When referencing the directive-named columns, enclose the column name in double quotation marks exactly as shown, since the identifiers contain colons and prefix characters that would otherwise be parsed incorrectly.