Extracting Incremental Changes Using Subledger Journal Header And Line PVOs Do Not Generate Consistent Data
(Doc ID 2962010.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Fusion General Ledger Cloud Service - Version 11.13.23.04.0 and laterInformation in this document applies to any platform.
Symptoms
When exporting data using the Subledger Journal Header and Subledger Journal Line PVOs, the data seems inconsistent as the last_update_date field does not have the same value. The customer is using the last_update_date field as an incremental filter to identify the changed records, but it doesn't seem functioning correctly as the last_update_date field is not in sync between the header and the lines.
For example, there are posted Headers with latest last update date correctly set, but the same date is not updated in the journal lines or the same happens when the gl_transfer_status_code is set to Y in the header, the last_update_date field is updated at the header level but not at the line level.
This causes the the extracts between header and lines are not consistent, as we may get headers with NO lines or lines with no headers. What is expected is that if a header is extracted then all lines for that header are also extracted.
PVO Names:
FscmTopModelAM.FinExtractAM.XlaBiccExtractAM.SubledgerJournalLineExtractPVO
FscmTopModelAM.FinExtractAM.XlaBiccExtractAM.SubledgerJournalHeaderExtractPVO
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 |