Verification error for <xxx> of shipment <xxx>: expected <Pickup Order Movement>, but was <Not Pickup Order Movement>

(Doc ID 2338091.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle Transportation Management - Version 6.3.7 to 6.4.3 [Release 6.3 to 6.4]
Information in this document applies to any platform.

Symptoms

Shipment agent fails to rerate and redrive the shipment while processing Shipment Status XML, after a Shipment Actuals XMl is received, the following error occurs.

ERROR
-----------------------
Verification error for <xxx> of shipment <xxx>: expected <Pickup Order Movement>, but was <Not Pickup Order Movement>

Scenario explanation:
---------------------------
01. Two orders each has two shipments

Order#1: SH1 & SH2

A - B B - C

Order#2: SH3 & SH4

A- B B- D

02. You send in the Shipments Actuals includes (SH1 with RC transaction code) & (SH3 with D transaction code). The purpose is to delete SH3 and update SH1 to include Order1 and Order2 from the first leg.

So the following are how the orders and shipments looks like after the Shipments Actuals.

Order#1: SH1 SH2

A - B B - C

Note: SH1 has Order 1 & 2 first legs

Order#2: SH4

B - D

03. You send in Shipment Status

04. Agent triggers that does Rerate and redrive

SHIPMENT STATUS - RECEIVED: ARRIVED
RERATE AND REDRIVE: Rerate Current Shipment, Do not Redrive Current Shipment, Do not Redrive Downstream Shipments, Do not Redrive Upstream Shipments

05. Error
Verification error for <xxx> of shipment <xxx>: expected <Pickup Order Movement>, but was <Not Pickup Order Movement>

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