Order Mod Edit Shipment Agent Action Fails with "java.lang.NullPointerException" Error When Replacing an Existing Ship Unit

(Doc ID 2310049.1)

Last updated on SEPTEMBER 22, 2017

Applies to:

Oracle Transportation Management - Version 6.4.2 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
An order release is planned onto a shipment. An inbound Release XML is sent to change the order using RC transaction code. The change is essentially a replacement of the OR Line / Ship Unit on the existing order release. An existing OMD agent is configured with the "Order Release - Mod - Edit
Shipment" action. This action is failing with the following exception:

ERROR
---------------

EXPECTED BEHAVIOR
-----------------------
It is expected for the order release modification XML to be processed successfully with no errors.

 

STEPS
-----------------------
The issue can be reproduced with the following steps:

1. Upload to create an order
2. Bulk plan the order onto a shipment
3. Upload an order modification XML with transaction code of RC. The modification XML should have reference to a new ship unit GID which will essentially is deleting the existing ship unit on the order and updating the existing order release with the new ship unit.
4. At this point, an existing Order Mod agent should be triggered. The agent will fail on the Mod Edit Shipment action with above exception.

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