Results for “uom_code”

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

Overview

ASO_I_ITEM_UOMS_V is a public APPS-schema view in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2) belonging to the ASO - Order Capture product family. Its documented purpose is to expose the valid units of measure for inventory items, taking into account the UOM conversions that are defined in the system. Rather than requiring callers to resolve which UOMs are legitimately applicable to a given item, the view surfaces that resolved set directly.

Functionally, the view is a thin projection over the Inventory object MTL_ITEM_UOMS_VIEW: it re-exposes the same columns without adding filters, joins, or derived expressions. Its value therefore lies in the ASO namespace — it gives Order Capture, iStore, and quoting components a stable, product-owned handle on item/UOM data without those components referencing the MTL view directly. For reporting and integration, this makes ASO_I_ITEM_UOMS_V the natural source when an item must be presented alongside its permissible UOM codes, descriptions, and UOM classes — for example, on a sales order line entry form or in an Order Capture extension. Because the view text is an unfiltered SELECT from the base view, it is equally usable in ad hoc SQL, BI Publisher data templates, and inbound/outbound interface logic, provided the querying user has execute privileges on the APPS synonym.

Underlying Base Objects

ETRM documentation lists exactly one referenced base object: MTL_ITEM_UOMS_VIEW (VIEW), owned by Inventory. No tables in the FROM clause other than this view are documented. The definition supplied is:

• SELECT ORGANIZATION_ID, INVENTORY_ITEM_ID, UOM_TYPE, UOM_CODE, UNIT_OF_MEASURE, DESCRIPTION, UOM_CLASS FROM MTL_ITEM_UOMS_VIEW

Consequently, ASO_I_ITEM_UOMS_V inherits all of its column semantics, grain, and row-level logic from MTL_ITEM_UOMS_VIEW. The base view is itself responsible for deriving the valid UOM set per item by evaluating the conversion relationships defined in Inventory (typically involving MTL_UNITS_OF_MEASURE and the UOM conversion tables). Because ASO_I_ITEM_UOMS_V applies no additional predicates, the two views are row-for-row identical for a given organization and item. Any change Oracle applies to the MTL view — additional columns, revised conversion logic, or new join criteria — propagates automatically into the ASO view, which is why it is described as a pass-through convenience layer rather than an independent data source. Note the distinction from a similarly named catalog object, MTL_ITEM_UOMS_V: the documented base here is MTL_ITEM_UOMS_VIEW, and users searching under the term "mtl_item_uoms_view" should confirm which Inventory view exists and is valid in their instance before substituting names.

Key Columns

• ORGANIZATION_ID — Identifies the inventory organization in which the item and its UOM applicability are evaluated. Since UOM validity can vary by organization, this column is part of the effective key for most queries.
• INVENTORY_ITEM_ID — The internal surrogate key of the item in MTL_SYSTEM_ITEMS_B. Together with ORGANIZATION_ID it scopes the returned UOM rows.
• UOM_TYPE — Classifies the UOM in the context of the item, indicating how the unit relates to the item's primary or secondary stocking unit.
• UOM_CODE — The internal code of the unit of measure (the stored key value used in transactional tables).
• UNIT_OF_MEASURE — The user-facing name or short form of the UOM, suitable for display in lists of values and reports.
• DESCRIPTION — The descriptive text of the unit of measure, useful in print output and self-service pages.
• UOM_CLASS — The class to which the UOM belongs (for example quantity, weight, or volume), enabling class-based filtering or grouping.

Common Use Cases and Queries

The principal use case is populating the UOM list of values on Order Capture and order-entry screens, and validating a user-entered UOM against the item at the time a sales order line is created or modified. Secondary uses include reporting on item/UOM coverage and feeding integration programs that must translate quantities into an acceptable unit of measure.

List valid UOMs for one item in one organization:

• SELECT uom_code, unit_of_measure, description, uom_class, uom_type
• FROM   aso_i_item_uoms_v
• WHERE  organization_id = :p_org_id
• AND    inventory_item_id = :p_item_id
• ORDER BY unit_of_measure;

Validate or translate a specified UOM for an item:

• SELECT COUNT(*)
• FROM   aso_i_item_uoms_v
• WHERE  organization_id = :p_org_id
• AND    inventory_item_id = :p_item_id
• AND    uom_code = :p_uom_code;

Because rows are returned only for UOMs supported by a defined conversion, the existence of a matching row constitutes successful validation. A COUNT of zero indicates the requested UOM is not permissible for that item and organization.