ETL Re-run Deletes All the Shipment Stops But Re-inserts the Stop That Has Been Updated in OTM Since the Last ETL Run (Doc ID 2028157.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

When a change to a shipment stop is made on OTM (OLTP DB) after the shipment has been moved to FTI (HD DB), when ETL runs, it delete all the shipment stops but only re-inserts the stop with the latest change since the last ETL run (this can be seen in F_SHIPMENT_STOP_D table in FTI comparing to SHIPMENT_STOP table in OTM). This results in a shipment with only one stop rather than two.

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