ETL Updates Only Modified Shipments At The Second Run In F_SHIPMENT_ORDER_RELEASE_COST table, Rather Than All The Order Release Related Shipment
(Doc ID 2195366.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Fusion Transportation Intelligence - Version 6.3.6 to 6.4.3 [Release 6.3 to 6.4]Information in this document applies to any platform.
Symptoms
When updating the shipments start time, after running ETL, shipments stops which are not updated are getting removed from F_SHIPMENT_ORDER_RELEASE_COST
It is expected to have all the Order Release related shipment stops in F_SHIPMENT_ORDER_RELEASE_COST.
The issue can be reproduced at will with the following steps:
1.Select different shipments related to the same Order_releases which have already been passed to FTI.
2.Update any shipment's START_TIME
3.Run the ETL
4.After running ETL, the shipments which are not updated within SHIPMENT table in OTM will be deleted from F_SHIPMENT_ORDER_RELEASE_COST
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |