Expand Receiving in terms of Interclass UOM

Today, when receiving inventory (whether via RF or API), if the ordered UOM belongs to a different UOM class than the item’s primary UOM, the system blocks receiving with an error: “UOM classes do not match with Item's Primary UOM, %UOM”.

This enhancement allows inter-class UOM conversions during receiving in RF and API transactions.

The following has been expanded for receiving in terms of Interclass Ordered UOM:

RF Receiving Shipment
RF Receiving Load
RF Receiving Single SKU
RF Sort & Receive
PO Based Receiving
Manufacturing Transaction API
Receive IBLPN API

The system allows receiving in a different UOM class and displays quantity in received UOM during receiving. You can convert and track inventory in item’s primary UOM. Also, update shipment, PO records, manufacturing transactions, and inventory history accordingly.

EXAMPLE CONVERSION MAPPING

SKU	UOM Class	Base UOM	Target UOM Class	Target Base UOM	Conversion Factor	Comments
SKU01	Quantity	Each	Weight	Gms	20	1 Gm = 0.05 Each

Example 1: ASN Based Receiving (RF / API) - Receiving 5 Kgs of SKU01 (Primary UOM: Each).

BEFORE RECEIVING

ASN	Shipped Qty (EA)	Shipped UOM Qty	UOM	SKU
ASN-01	250(5000x0.05)	5 Kgs	Each	SKU01

AFTER RECEIVING 1 Kg

ASN	Shipped Qty (EA)	Shipped UOM Qty	Received Qty (EA)	LPN Nbr	UOM	SKU
ASN - 01	50 EA	1 Kgs	50 EA	LPN-001	Each	SKU01
ASN - 01	200 EA	4 kgs	0 EA	-	Each	SKU01

INVENTORY HISTORY UPDATES

IHT-1 Ref Value 17 (Kgs): 1
IHT-1 Ref Value 18 (EA): 50

MANUFACTURING TRANSACTION API

We now support Inter Class UOM conversions when transactions are received via the Manufacturing API.

Example 2: Manufacturing transaction sends 5 Kgs of SKU01 (Primary UOM: Each)

MANUFACTURING REQUEST

Manufacturing Transaction ID	Qty (Kgs)	SKU	UOM Code	LPN Nbr	Location	Updated Qty (EA)
MFTN-01	5	SKU01	Kgs	LPN-001	RESV-01	250 EA

INVENTORY HISTORY UPDATES

IHT-1 Ref Value 17 (Kgs): 5
IHT-1 Ref Value 18 (EA): 250

Steps to Enable

You don't need to do anything to enable this feature.