What To Do When Manual Merge Fails For the First of Two Shipments
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Transportation Management - Version: 5.0
This problem can occur on any platform.
The problem occurs when two order movements are created from two order releases with different
source locations and subsequently shipments are created from these two order movements.
When trying to manually force merge the shipments and selecting the first of the two shipments as the one both shipments to be merged onto, an error message like this is thrown:
Forced merge failed - The planned time interval [2006-10-24 12:23:20
Europe/Berlin, 2006-10-24 13:23:20 Europe/Berlin] of stop 1 at location
CPAMP.CDP_LAGER_MUENCHEN_II on secondary shipment CPAMP.01464 overlaps with
the planned time interval [2006-10-24 12:23:08 Europe/Berlin, 2006-10-24
13:23:08 Europe/Berlin] of stop 1 at location CPAMP.CDP_LAGER_MUENCHEN on
primary shipment clone: CPAMP.01463.
If the second shipment is selected as the one both shipments to be merged on, the merge works perfectly fine.
The expected behavior is, that the merge can be carried out either way and only the shipment number would be different depending on which one is selected.
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