My Oracle Support Banner

Shipment Actuals Stops Types Are Incorrect (Doc ID 2489983.1)

Last updated on MAY 08, 2020

Applies to:

Oracle Transportation Operational Planning - Version 6.4.1 and later
Information in this document applies to any platform.

Symptoms

Shipment Actuals stops types are incorrect.

OTM does not set the shipment stops types correctly during shipment actual upload via integration with the existence of a Shipment agent action 'Assign Rate'.

EXAMPLE:
-------------

Agent ID: XXX
Agent Type: SHIPMENT
Agent Event: SHIPMENT - ACTUAL RECEIVED
Agent Action: ASSIGN RATE

01. Create the following Orders

OR1 (SRC1 -> DEST1)

OR2(SRC2 -> DEST2)

02. Create a Shipment via upload a Shipment Actuals XML, includes the above orders stops

SH1

Stops:

P SRC1
P SRC2
D DEST2
D DEST1

03. Update Order (OR2) with a new Source Location (Same Source of OR1)

OR2 (SRC1 > DEST2)

04. Update the shipment via upload a Shipment Actuals XML to reflect the Order's source change.

SH1

Expected Stops:

P SRC1
D DEST2
D DEST1

Actual Stops:

P SRC1
P DEST2 (The Stop Type should be D not P)
D DEST1

NOTE: The issue only happens when the "Assign Rate" action executed on the shipment after the update.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.