The ETL Load of the F_SHIPMENT_ORD_REL_COST_D Table Removes the Shipment Allocation Record from Table
(Doc ID 2576328.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Fusion Transportation Intelligence - Version 6.4.2 and laterInformation in this document applies to any platform.
Symptoms
The initial ETL run correctly creates a row for each shipment allocation into the table: F_SHIPMENT_ORD_REL_COST_D. After an invoice is created for shipments and it has been vouchered and allocated; the ETL is run again.
During the second ETL run, the previous shipment allocation is deleted from the F_SHIPMENT_ORD_REL_COST_D table and a new row is added for the voucher allocation.
It was expected that both allocation records remain in table F_SHIPMENT_ORD_REL_COST_D.
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 |