Release Transaction Fires OR MOD EDIT SHIPMENT Action Causing Order To Lose Link To 2nd Leg Shipment

(Doc ID 1583674.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Transportation Management - Version 6.2.5 to 6.2.10 [Release 6.2]
Information in this document applies to any platform.

Symptoms

On OTM version 6.2.5

ACTUAL BEHAVIOR
---------------
When LTL Shipments are force merged and the related TL shipments have Shipment Actual XMLs sent in, sometimes the Orders are removed from the associated LTL shipment.

EXPECTED BEHAVIOR
-----------------------
Expect all Orders to remain on the Shipments as they were.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:


1 - Two LTLs into a crossdock have been created, each with a different source location, the times on both are the same.
(Two out of crossdock TLs have also been made.)

2 - A single LTL has been created by a 'force merge' of the two LTLs into the cross dock - carrying 3 orders.

3 - TL ending 13 starts at 13:00 on the 8th Jan - this carries two of the orders.

4 - TL ending 15 starts at 03:00 on the 8th Jan - this carries one of the orders.

5 - Sending in the load confirmation for TL 15 updates that TL and the orders remain OK on the related LTL.

6 - Sending in the load confirmation for TL 13 caused its two orders to be removed from the related LTL.


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