1. Online Help
  2. Enhance Warehouse Efficiency with Item-Specific UOM Conversions

Enhance Warehouse Efficiency with Item-Specific UOM Conversions

Item-Specific UOM Conversions allow receiving and storing inventories with one UOM class while fulfilling orders or handling corresponding billings in another UOM class. This functionality enables processing of purchase orders, inbound shipments, and sales orders using UOMs different from an item’s primary UOM.

The system tracks inventory in the Primary UOM while allowing customers and external systems to interact with UOMs more relevant to their operations. The Item-Specific UOM Conversion UI defines conversion factors between the base UOM of the item’s primary UOM class and the base UOM of the target UOM class.

UOM Conversion

An item-specific conversion record is interpreted as: Target Base UOM = Conversion Factor × Item Primary Base UOM

You can interface JSON, Item-Specific UOM Conversion to enable the creation of UOM conversion records using the following API:

POST .../wms/lgfapi/v10/stage/item_specific_uom_conversion/

Item-specific conversion records apply to individual items. If an item-specific conversion record already exists for an item, a new record with the same item, primary base UOM, and target base UOM combination cannot be created. Once a transaction occurs using an item-specific UOM conversion record (such as a purchase order, inbound shipment, or sales order), the conversion record cannot be deleted or modified.

The item-specific UOM conversion supports interfacing with purchase orders, inbound shipments, and sales orders.

Note:
  • You can define conversion factors between base UOMs of different UOM classes. When defining a SKU's facility UOM, the conversion factor is automatically handled at the Base UOM level, eliminating the need for separate conversion definitions.
  • In case of partial receipts or ASN updates, the shipped/ordered UOM quantity will be shown in proportion to the primary UOM. The conversion between primary UOM and ordered UOM ensures accurate quantity tracking post-receiving. Modifications in received LPN quantities will also update the corresponding IB Shipment.
  • When interfacing a PO with a different UOM class than the item's primary UOM, ASNs can be automatically created (if CREATE_ASN_FOR_EACH_PO is set to "yes"). The ASN will inherit the shipped UOM as per the PO’s ordered UOM.

Inbound Shipments

Inbound shipments can include expected quantities in the shipped UOM. The following fields are available in XML and PSV formats for inbound shipment verification:

  • shipped_uom
  • shipped_uom_qty
  • shipped_uom_received_qty (calculated from primary UOM)

Example:

A conversion record is required between the Base UOM of the Primary UOM class and the Base UOM of the target UOM class for SKU01.

IB Shipment Expected Quantity Received Quantity Primary UOM SKU Shipped UOM Quantity Shipped UOM Status
ASN01 250 0 Each SKU01 5 Kgs In-Transit

After Partial Receiving (200 Eaches received):

IB Shipment Expected Quantity Received Quantity Primary UOM SKU Shipped UOM Quantity Shipped UOM Shipped UOM Received Quantity
ASN01 250 200 Each SKU01 5 Kgs 4

Sales Orders and Shipping

Sales orders can be processed and tracked in the ordered UOM, even when it differs from the item’s primary UOM.

Fields in XML, PSV, and JSON formats are available for OBLPN and Pallet shipping info:

  • ordered_uom
  • ordered_uom_qty
  • ordered_uom_shipped_qty (calculated from primary UOM)

OBLPN Shipping Info (OLO) and Pallet Shipping Info (PLO) files reflect these fields.

The following are supported file format to enable the HOST to have the Interclass UOM:

  • Container Shipped Load - LLS
  • Outbound Load/Parcel - SLS
  • ORDER_OUTBOUND_LOAD_EXPORT - PLS
  • SHIPMENT_VERIFICATION - SVS

Updated/Modify Item-Specific UOM Conversions

To modify an existing UOM conversion:

  1. Navigate to the Item UOM Conversion screen.
  2. Select an item and update the necessary fields.
  3. Click Save to confirm the changes.
Note:
  • If no conversion exists and the ordered UOM belongs to a different class than the primary UOM, the system will fail the interface.
  • Existing same-class UOM conversions remain unchanged.
    • To Create Item-Specific UOM Conversion:
  1. Go to the Item UOM Conversion screen.
  2. Click Create and populate the necessary fields:
Field Description Required
Item Select the item for which the conversion is defined. Yes
Target Base UOM Specify the target base unit of measure. Yes
Target UOM Class Choose the appropriate UOM class. No
Conversion Factor Enter the conversion factor between UOMs. Yes
Item Primary Base UOM Displays the item’s primary base unit of measure. Yes
Item Primary UOM Class Displays the item’s primary UOM class. No
  1. Click Save to store the UOM conversion.
Note:

To proceed with creating an Item-Specific UOM Conversion, ensure the appropriate group permissions are set:

  • Item Specific UOM Conversion / Can Configure Item Specific UOM Conversion
  • Item Specific UOM Conversion / Can Delete Item Specific UOM Conversion
  • Item Specific UOM Conversion / Can Edit Item Specific UOM Conversion

Without the necessary group permissions, attempts to process UOM conversions for purchase orders, inbound shipments, or sales orders will fail. Ensure the correct setup before initiating these transactions.

Item-Specific UOM Conversions Across Interfaces

Item-Specific UOM Conversions allow receiving and storing inventory using one unit of measure (UOM) class while fulfilling orders or managing billing with a different UOM class. This supports accurate processing of purchase orders, inbound shipments, sales orders, work orders, and movement requests, even when the involved UOMs differ from the item's primary UOM class.

The system tracks inventory in the Primary UOM while enabling external systems and customers to use UOMs more relevant to their operations.

Interface for Creating Item-Specific UOM Conversions

You can use the following API to define conversion records between UOM classes:

POST .../wms/lgfapi/v10/stage/item_specific_uom_conversion/

For more information, please refer to Interface spec file - Oracle WMS Cloud Information Center > Documentation tab > click the link under Current Documentation > refer to the WMS Interface Specifications document

Each record defines a conversion between an item’s primary base UOM and a target base UOM from another class.

Input Interface Support

  • Work Order and Planned Load Interfaces
  • Support UOMs from different classes.
  • The system applies item-specific UOM conversions when available.
  • If no item-specific conversion exists, the system defaults to standard conversions within the same UOM class.
  • If no valid conversion is available, the interface transaction fails.
  • Movement Request Interface
  • Supports processing with UOMs from different classes.
  • Two additional fields are available in the Movement Request Detail screen:
Field Description
ordered_uom UOM in which the order was placed
ordered_uom_qty Quantity as per the ordered UOM

These fields help track movement requests accurately when ordered in a different UOM class.

Output Interface Support

  • OBLPN and Pallet Shipping Info Files

The system includes the following fields in XML, PSV, and JSON formats:

Field Description
ordered_uom Ordered unit of measure
ordered_uom_qty Ordered quantity in the specified UOM
ordered_uom_alloc_qty Allocated quantity in the ordered UOM
ordered_uom_packed_qty Packed quantity in the ordered UOM
Additional JSON Fields
  • curr_qty_in_ordered_uom: Current inventory quantity in the ordered UOM (Inventory List)
  • ordered_uom_code: Code for the ordered UOM
  • shipped_qty_in_ordered_uom: Quantity shipped in the ordered UOM (Order Detail List)