My Oracle Support Banner

OMD Agent Leaves Secondary Charge Shipments Corrupted (Doc ID 1365567.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Transportation Management - Version: 6.1.2 and later   [Release: 6.1 and later ]
Information in this document applies to any platform.

Symptoms

Changes on an order are not correctly propagated to the secondary charge shipment despite an OMD agent has been created for this.

Agent Event = ORDER - MODIFIED USER,ORDER - QUANTITIES MODIFIED, before persist is ticked.
Actions = ORDER RELEASE - MOD – EDIT SHIPMENT.

To reproduce:

- Bulk plan an order (buy), as a result, a secondary charge shipment is created.
- Look at the secondary charge shipment (edit mode), the total weight/volume is populated on the first tab and the stop tab shows the ship unit count as well
- Edit the order and change the ship unit count
- Agent is triggered and the change is propagated

On the secondary charge shipment, the weight/volume/ship unit data is set to 0 on the main tab. Ship unit data is gone from the stops. Shipment Equipment data is correct.

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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