Shipment Unassign Shipment Stop Refnum Data Consistency Issues
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version 6.2.0 to 6.2.8 [Release 6.2]
Information in this document applies to any platform.
The SHIPMENT_STOP_INV_PARTY and SHIPMENT_STOP_REFNUM data is corrupted for Multistop shipments when an order from a stop in the middle of the shipment is unassigned.
Steps to Replicate:
1. Create a Multi Stop Shipment (at least 4 stops)
2. For each shipment stop, add a REFNUM and update INVOLVEDPARTY contact
(Make Sure this are different values to see the difference in results)
3. Unassign orders related to any stop other than the very last stop (select all the orders for a stop)
4. Verify the REFNUM and INV PARTY on the remaining stops after unassignment
You will notice that there are still three Remarks and "STOP 4 is repeated. There should only be two remarks. Note: repeating the same test case using a Reference Number instead of Remark, works fine.
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