Shipmentmodviaorderline Does Not Remove Order From Shipment as Expected
(Doc ID 1384411.1)
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 6.2.3 to 6.2.5 - Release: 6.2 to 6.2
Information in this document applies to any platform.
When sending a ShipmentActual using the Transaction Code D with the ShipmentModViaOrderLine element as an IU, only the order release line under the ship unit is removed from the shipment. The client is expecting both the shipment ship unit line and shipment ship unit to be removed from the shipment. In Addition, it is expected that if there was only one ship unit on the shipment, the shipment should also be deleted which is the case in this example.
As a note, this worked as expected in 5.5 CU5.
The issue can be reproduced at will with the following steps:
Order Base: EDDY_OB6
Order Base Line ID on Order: EDDY_OB6-001
Order Release: EDDY_OB6-001
Created Direct Shipment Using the DEFAULT planning parameter set (not the one set as domain default): 01007
1. Log into OTM 6.2.
2. View Shipment 01007 and note that there is only 1 ship unit/line on the shipment - EDDY_OB6-001-001-007
3. Upload delshipunit.xml.
4. Note Transmission 729728 was created.
5. Go Back to search for the shipment 01007.
6. If you look at my shipment 01007 in view mode, under ship unit EDDY_OB6-001-001-007, the order release has been removed from the ship unit (altho the order release itself still exists). The client expects the entire ship unit and shipment to be removed in this case.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|