Incorrect Order Movement Total Weight,if An Order Movement Got Split During Bulkplan of Order Movements and Unassign the Related Order Release Gives 'java.lang.NullPointerException' Error (Doc ID 1989682.1)

Last updated on NOVEMBER 24, 2015

Applies to:

Oracle Transportation Operational Planning - Version 6.3.4 to 6.4 [Release 6.3 to 6.4]
Information in this document applies to any platform.

Symptoms

Bulk plan OMs (Order Movements) causes data corruption while consolidating multiple OMs into one shipment, it makes one OM has more ship unit count than its order has. After this data corruption, unassign order release is giving the below NPE error.


Example:
--------------------------

1. Create Order Release: My_Order

Total Weight
20000.00 KG

Ship Units
My_Order-001
My_Order-002

Ship Unit Count: 1000
Total Gross Weight: 10000.00 KG

2. Select the order > actions > Manage Buy Order Movement > Show Itineraries > select an itinerary to create an Order Movement with. with an equipment group that cannot carry the whole order to force the .

Order Movement created
My_Order-001

Total Weight
20,000.00 KG

Ship Unit ID Ship Unit Count Weight Volume Transport Handling Unit
My_Order-002-001 1000 10.00 KG 10.00 CUMTR THU1
My_Order-001-001 1000 10.00 KG THU1

3. Query and select the order movement > actions > bulk plan - buy > using the default planning parameter set. (Please use an itinerary with an equipment group that cannot carry the whole order to force the Order Movement splitting)

Two shipments created

New Order Movements

My_Order-001
Total Weight
10000.00 KG

My_Order-002-001 THU1 1000 10.00 KG 10.00 CUMTR

My_Order-002
Total Weight
30000.00 KG

My_Order-001-001 THU1 1000 10.00 KG CUMTR

4.Unassign Order movement/Release action failing due to the NPE.

Changes

 Order movement data is getting corrupted if an order movement got split during bulk plan of order movements.
If building only order movement firstly and do bulk plan from the movement, planned movement's total weight / ship unit is not re-built even splitting the movement due to the weight and equipment capacity.
 
This is explained in the following bug:
<Bug 19452433> BULK PLAN ORDER MOVEMENTS CAUSES DATA CORRUPTION

Cause

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