Deletion of Reversal Journal Does Not Remove ACCRUAL_REV_PERIOD_NAME Information From the Original Journal
(Doc ID 1510469.1)
Last updated on FEBRUARY 19, 2020
Applies to:Oracle General Ledger - Version 220.127.116.11 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
GLXJEENT, Journal Entry form
The users have described the following situation, described step by step:
1)Created manual journal.
Autoreversal is set for the category but it won’t pick the journal as it has set No Default for the category and No reversal period entered on journal creation.
2)Posted the created journal
3)Reversed it. Here the user is asked to enter a reversal period.
4)Reversal entry got created.
5)Checked original journal. Status has become 'Reversed'
6)Deleted the reversal entry
8)Opened original journal
9)Note that the Status has become 'Not Reversed' automatically. But the Reversal Period entered in step 3 is not erased. ACCRUAL_REV_PERIOD_NAME is still there saved hence the original journal is no longer intact.
Due to this issue, as the reversal period is saved for original journal, the Autoreverse process picks the original batch reversing it into the wrong period.
The user creates journals with no reversal info on purpose. If they incorrectly reverse to the wrong period, then deleting the reversal is expected to cause no harm to the original journal. The user expects to reverse again in another period, but finds out the journal is already picked and reversed/posted due to Autoreversal process which now picks this journal, which did not happen in step 1.
Is this intended design?
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