EAR 9.2 - Direct Journal Deposit Status Remains At N Even After Journals Are Posted
(Doc ID 2320882.1)
Last updated on OCTOBER 24, 2017
Applies to:
PeopleSoft Enterprise FIN Receivables - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
On : 9.2 version, Direct Journal
When attempting to post direct journals,
the following error occurs.
ERROR
-----------------------
Direct Journals are not going to completed status even after journals are generated
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create regular deposits and mark them direct journals
2. Create accounting entries and put them complete status
3. Run the journal generator process
4. Run a query for deposit status for that deposit id, it should be 'C' but its coming as 'N'
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use bank reconciliation process as it looks for deposits in complete status.
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 |