Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 6.2.3 and later
Information in this document applies to any platform.
***Checked for relevance on 26-Dec-2013***
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:
UOMs Used on OB:
UOMs expected on OR in the DB:
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
ORDER_RELEASE_GID TOTAL_WEIGHT_UOM_CODE TOTAL_VOLUME_UOM_CODE
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms