R12.1.3: Reversal period manually populated in secondary ledger journal is overwritten by period populated in primary journal.
(Doc ID 1560521.1)
Last updated on FEBRUARY 04, 2025
Applies to:
Oracle General Ledger - Version 12.1.3 and laterInformation in this document applies to any platform.
Synchronize reversals between primary and secondary ledger done at ASM.
First, customer enters a journal in primary ledger in period say, May-13, populates reversal period as Jun-13 in reversal section and posts the journal.
Posting will replicate the same journal in secondary ledger in May-13. Reversal period is blank in secondary ledger journal.
Customer then populates the reversal period as May-13 in secondary ledger journal header manually. Posts the secondary ledger journal.
When customer clicks on 'reverse' button on the primary journal, the primary ledger journal is reversed in Jun-13(correct behavior) , but, the replicated reversal in secondary journal is in Jun-13
(incorrect behavior because user has manually set reversal period on the sec journal header as May-13).
This means that, even if we have manually populated reversal period in secondary ledger journal, when reversal happens through primary ledger journal, primary ledger
journal's reversal period over-writes the the reversal period manually populated in secondary ledger journal.
Goal
When 'Synchronize Reversals between primary ledger and secondary ledger' is checked at ASM level, when customer has manually updated different reversal periods in primary and secondary ledger journal, customer expects the reversals to happen in those respective periods. But the actual behavior is that, the primary ledger journal's reversal period is over-riding secondary ledger journal's reversal period.
Solution
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
| Goal |
| Solution |
| References |