Search Results ahl_item_class_uom_v




Overview
Explore in AI Chat

Overview

The AHL_ITEM_CLASS_UOM_V view is an Oracle E-Business Suite database object owned by the APPS schema. It belongs to the AHL product family, Complex Maintenance Repair and Overhaul (CMRO), and carries a VALID status in both EBS 12.1.1 and 12.2.2. The view serves a specific reporting and integration purpose: for any inventory item, it returns the item's base (primary) unit of measure together with every other unit of measure that belongs to the same UOM class as that base UOM. This effectively exposes the full set of alternative units in which an item's quantity can be expressed or converted, which is essential for maintenance, repair, and overhaul transactions where the same physical material may be issued, received, or planned in differing units.

Because the view is keyed on both inventory item and organization, it is well suited for multi-organization reporting and for feeding downstream applications that must present a consistent, class-validated list of allowable units per item.

Underlying Base Objects

The view is defined over four documented references: MTL_SYSTEM_ITEMS_KFV, MTL_UNITS_OF_MEASURE_VL (referenced twice as UOM1 and UOM2), and FND_LOOKUP_VALUES_VL. The join logic is:

  • MTL_SYSTEM_ITEMS_KFV supplies the item, its organization, and the PRIMARY_UOM_CODE (the base UOM).
  • MTL_UNITS_OF_MEASURE_VL UOM1 resolves the base UOM's UOM_CLASS.
  • MTL_UNITS_OF_MEASURE_VL UOM2 returns all units sharing that same UOM_CLASS, filtered so that only non-expired units (or those with no disable date) remain.
  • FND_LOOKUP_VALUES_VL joins on lookup type AHL_YES_NO_TYPE via BASE_UOM_FLAG, tagging each returned unit with a yes/no BASE_UOM meaning so consumers can identify the item's actual base UOM within the expanded list.

Key Columns

  • UNIT_OF_MEASURE — the descriptive name of the unit of measure.
  • UOM_CODE — the unique code for the unit, used in conversions.
  • UOM_CLASS — the class shared by the base UOM and all returned alternative UOMs.
  • UOM_DESCRIPTION — description text for the unit.
  • BASE_UOM — a yes/no meaning flag indicating whether this row corresponds to the item's base UOM.
  • INVENTORY_ITEM_ID — the item identifier.
  • INVENTORY_ORG_ID — the owning inventory organization.
  • CONCATENATED_SEGMENTS — the item's concatenated (flexfield) segment description.

Common Use Cases and Queries

A frequent pattern is retrieving all valid alternative units for a single item and organization, filtering out the base UOM itself.

  • List alternative UOMs for an item: 
    SELECT uom_code, unit_of_measure, uom_class
FROM   apps.ahl_item_class_uom_v
WHERE  inventory_item_id = :item_id
AND    inventory_org_id  = :org_id
AND    base_uom = 'N';
  • Identify the base UOM row: 
    SELECT uom_code, unit_of_measure
FROM   apps.ahl_item_class_uom_v
WHERE  inventory_item_id = :item_id
AND    base_uom = 'Y';
  • Show item context with its units: 
    SELECT concatenated_segments, inventory_org_id,
       uom_code, base_uom
FROM   apps.ahl_item_class_uom_v
WHERE  inventory_org_id = :org_id;

These queries support LOV construction, CMRO maintenance work-order entry, and validation logic ensuring that only class-compatible units are selected for an item.