Results for “as_inv_uom_v”

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

Overview

AS_INV_UOM_V is a view owned by the APPS schema in Oracle E-Business Suite, defined under the AS - Sales Foundation product family. Its stated purpose is to provide the Inventory Item identifier together with its corresponding unit of measure. The view is classified with a status of VALID in the documented metadata, confirming that it compiles successfully and can be relied upon by dependent reports, concurrent programs, and integrations.

Because Inventory item and UOM relationships are stored across multiple normalized tables in Oracle Inventory, AS_INV_UOM_V serves as a lightweight, purpose-built presentation layer. Rather than requiring report authors or interface developers to join MTL_SYSTEM_ITEMS_B to MTL_UNITS_OF_MEASURE_VL manually, the view centralizes the join and exposes a clean, denormalized result set. This makes it particularly useful in the Sales Foundation context, where item-to-UOM resolution is frequently required for quoting, order capture, and pricing logic. In Oracle EBS 12.1.1 and 12.2.2 alike, the view behaves consistently since it is a static SQL definition over core Inventory tables.

Underlying Base Objects

The view is defined over two referenced base objects, both documented in the ETRM metadata:

• MTL_SYSTEM_ITEMS_B (SYNONYM) — The Inventory item master base table. It holds the item definition keyed by INVENTORY_ITEM_ID and ORGANIZATION_ID, and stores the PRIORARY_UOM_CODE (primary unit of measure) for each item.
• MTL_UNITS_OF_MEASURE_VL (VIEW) — The Units of Measure validation view, which exposes UOM_CODE and its translated DESCRIPTION.

The join predicate links items to their unit of measure on the equality ITEMS.PRIMARY_UOM_CODE = UOM.UOM_CODE. The view therefore returns one row per inventory item per matching UOM record, effectively resolving each item's primary UOM code and its descriptive text.

Key Columns

The view exposes four columns, as documented:

• ORGANIZATION_ID — The inventory organization to which the item belongs. Important for multi-org environments, since the same item number may exist across organizations.
• INVENTORY_ITEM_ID — The internal unique identifier for the item. This is the primary key used across EBS tables and APIs, preferable to the user-facing item number for joins and integrations.
• UOM_CODE — The unit of measure code associated with the item, derived from the item's primary UOM.
• UOM_DESCRIPTION — The descriptive, translated name of the unit of measure, sourced from MTL_UNITS_OF_MEASURE_VL.

Common Use Cases and Queries

The view is typically used in reports and integrations that need to display or validate item UOM information without joining underlying Inventory tables directly. A simple lookup by organization and item is common:

• Item UOM validation — Confirm the UOM assigned to a given item during order or quote entry.
• Reporting — Present item identifiers alongside readable UOM descriptions in Sales Foundation reports.
• Integration mapping — Supply UOM codes to external systems during item interface loads.

Sample query:

• SELECT organization_id, inventory_item_id, uom_code, uom_description FROM apps.as_inv_uom_v WHERE organization_id = :p_org_id AND inventory_item_id = :p_item_id;

Because the view relies on the item's primary UOM only, it does not expose secondary or alternate units of measure; for those scenarios, queries must target MTL_ITEM_UOM_CONVERSIONS or related Inventory tables. For primary-UOM resolution, AS_INV_UOM_V remains a concise and dependable reference.