EGL9.2: For Journal With Reversal, Unpost Fails To Liquidate Reversal Journal Expense From Commitment Control Budget
(Doc ID 2456273.1)
Last updated on APRIL 20, 2023
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Given a journal with reversal at start of next period is posted, with reversal journal getting journal edited and thus budget checked but not posted.
Then when the original journal is unposted and the post process is run, the post process creates the unpost seq no 1 journal and updates reversal journal to deleted.
The unpost seq no 1 journal gets budget checked and posts an offsetting line to kk_activity_log, however, the reversal journal that gets updated to deleted does not also get budget checked and thus no offsetting line to kk_activity_log is generated - causing commitment control to be overstated.
Replication Steps:
1. Create a journal (Jan 2018) with a reversal in next period (Feb 2018).
2. Edit and budget check the original (Jan) journal
3. Post the original (Jan) journal
4. Next unpost the original (Jan) journal. Click OK at the message "Unpost period should be open with related journals. etc"
5. Review results. The reversal (Feb) journal that had not yet been posted, has been updated to deleted but the budget header status remains V. Consequently it will not be re-budget checked to update commitment control.
JRNL_HEADER, JRNL_LN
Journal ID Journal Date Unpost Seq FY Period Journal Status Budget Status Amount
0000239991 01/22/2018 0 2018 7 U V 87.00 << unposted Jan journal, seq 0
0000239991 01/22/2018 1 2018 7 P V < 87.00 > << unposted Jan journal, seq 1
0000239991 02/01/2018 0 2018 8 D V < 87.00 > << journal edited, not posted Feb journal
6. Review Commitment Control
KK_ACTIVITY_LOG
Journal ID Budget Period FY Period Amount
0000239991 2018 2018 7 87.00
0000239991 2018 2018 8 < 87.00 > << should be an add'l line for Period 8 to offset this line since reversal journal to Period 8 has been deleted
0000239991 2018 2018 7 < 87.00 >
Note: Data provided above is for demonstration purpose only .
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 |