My Oracle Support Banner

OMD Agent Errors with "Exception ship_unit xxx does not exist it was likely removed by another user" When an Release Update Using New Ship Unit ID That References Existing Line (Doc ID 1997537.1)

Last updated on JULY 06, 2020

Applies to:

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


An OMD (Order Mod) Agent is configured with the Agent Action: ORDER RELEASE - MOD - EDIT SHIPMENT

An Order Release is created and planned onto a shipment. Then a Release XML is uploaded to update that order where a new Ship Unit is being created that still references the existing Line. (i.e. the Line ID is re-used, but the Ship Unit ID is new).

When this XML is processed, it trigges the OMD Agent that eventually fails with:

Example Steps:

1. Create an OMD Agent with action: ORDER RELEASE - MOD - EDIT SHIPMENT
2. Create an Order Release with Ship Unit ID "A"and Line Item "A"
3. Plan the Order Release onto a Shipment
4. Upload a Release XML that has NEW Ship Unit ID "B" but still references Line Item "A"




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

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