Last updated on MARCH 08, 2017

Applies to:

Symptoms

When viewing the Order Base Unit of Measure, notice that it has different Units Of Measure (UOM) than Order Release.

The DB has the following values:
IS_STORAGE_DEFAULT Y
VOLUME CUFT
WEIGHT LB

UOMs Used on OB:
CUMTR
KG

UOMs expected on OR in the DB:
OR
CUFT
LB

When one of the lines has 0 volume and 0 weight.

Order Base: IBAHGAT.LH_BAD_VOL-01

DEFAULT BDP-EG BDP-US KG KG 0.00 CUMTR CUMTR 1
DEFAULT BDP-EG BDP-US 39.70 KG KG 0.40 CUMTR CUMTR 1

Order Release: IBAHGAT.LH_BAD_VOL-01-001

LH_BAD_VOL-01-001-001 DEFAULT 1 1 0.00 KG 0.00 CUMTR
LH_BAD_VOL-01-001-002 DEFAULT 1 1 39.70 KG 0.40 CUMTR

select ORDER_RELEASE_GID,
TOTAL_WEIGHT_UOM_CODE,
TOTAL_VOLUME_UOM_CODE,
TOTAL_NET_WEIGHT_UOM_CODE,
TOTAL_NET_VOLUME_UOM_CODE
from ORDER_RELEASE
where ORDER_RELEASE_GID='IBAHGAT.LH_BAD_VOL-01-001'

ORDER_RELEASE_GID TOTAL_WEIGHT_UOM_CODE TOTAL_VOLUME_UOM_CODE
TOTAL_NET_WEIGHT_UOM_CODE TOTAL_NET_VOLUME_UOM_CODEIBAHGAT.LH_BAD_VOL-01-001
LB CUFT LB CUFT

You expect the OB's UOMs get maintained on the DB for the Releases, but what happens is that the releases uses the Units of Measure stored as the system default in the database. Orders should be released in non base UOM. The behavior is not consistent.

Cause