EAR 9.2:Duplicate Journals Created In GL If Complete Flag Unchecked on Direct Journal Deposit After Running ARUPDATE
(Doc ID 2237485.1)
Last updated on JULY 04, 2023
Applies to:
PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
On 9.2 version, the user is able to uncheck the Complete box on the Direct Journal Deposit page after having ran the AR Update. After making modification and checking back the flag and running again the AR Update, the system creates the second GL journal corresponding to the Direct Journal Deposit
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- Add a new regular deposit and select Journal Directly
- Create accounting entries for previously created deposit
- Accounting entries are created with GL_DISTRIB_STATUS=I as accounting entries are not marked as complete
- Mark accounting entries as complete; GL_DISTRIB_STATUS=N on PAY_MISC_DST
- Run Journal Generator
- After the journal is created the GL_DISTRIB_STATUS=D (Distributed) on PAY_MISC_DST
- Uncheck the Complete flag then delete the accounting entries
- GL_DISTRIB_STATUS is updated to I after disabling the Complete flag and deleting the accounting entries on the deposit
- Recreate accounting entries
- GL_DISTRIB_STATUS remains I
- Do not Mark accounting entries as complete yet
- GL _DISTRIB_STATUS remains I
- Mark accounting entries as complete
- GL _DISTRIB_STATUS is updated to N
- Run Journal generate
- After running the journal generator we have a new journal ID and GL_DISTRIB_STATUS updated to D
- As of now we have 2 journal created for our deposit ID
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 |