My Oracle Support Banner

Shipment ShipUnit Refnums Do Not Get Propagated On The Second Leg When Propagation Elements Are Sent Via Integration (Doc ID 2084590.1)

Last updated on DECEMBER 02, 2015

Applies to:

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

Symptoms


When updating s_ship_unit refnums on a two leg itinerary shipments via integration, the second leg itinerary shipment is not getting updated with the s_ship_unit refnums that get inserted.


It is expected when updating s_ship_unit refnums on a two leg itinerary shipments via integration, to have the second leg itinerary shipment updated.


The issue can be reproduced at will with the following steps:

1. Having an order planned on a multi-leg itinerary
2. Update the S_ship_unit refnums via integration by inserting a new S_Ship_unit.
3. Notice the second leg shipment is not getting updated.


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!


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