My Oracle Support Banner

EAR 9.2: Direct Journal Payment Complete Flag (PS_PAY_MISC_WRK.JOURNAL_COMPLETE) Becomes Editable Even If Accounting Entries Have Already Been Journalled Into General Ledger Module (Doc ID 2250487.1)

Last updated on OCTOBER 02, 2023

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.



A problem has been detected in the Directly Journalled Payments tab (Page PAYMENT_MISC_DST_I), from the Modify Accounting Entries functionality for Direct Journal Payment transactions. The Complete flag should always be grayed out (Record Field PS_PAY_MISC_WRK.JOURNAL_COMPLETE) if the Accounting Entries stored into Table PS_PAY_MISC_DST have already been interfaced into FMS General Ledger module (PS_PAY_MISC_DST.GL_DISTRIB_STATUS = 'D').

However, if a series of steps are followed in the proper order, the Complete flag, although initially grayed out, becomes editable for the Users, which is wrong, and can lead to further problems if the flag is un-selected, and additional changes on the existing Accounting Entries are performed.


     1.- Log into the FSCM Online Application as User ID VP1
     2.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
     3.- Create a new Deposit Group under Business Unit US001, and define on single Payment, marked as Journal Directly
     4.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Create Accounting Entries
     5.- Open the recently created Deposit/Payment, and create the needed User Accounting Entries, generate the balancing Cash AR lines, and mark the transaction as Complete
     6.- Navigate to: General ledger > Journals > Subsystem Journals > Generate Journals
     7.- Create a new Run Control ID, with Business Unit US001, and Accounting Definition Name ARDIRJRNL
     8.- Launch the Journal Generator (AE Program FS_JGEN)
     9.- Navigate to: General Ledger > Journals > Journal Entry > Create/Update Journal Entries
     10.- Find the newly created Journal, and launch Journal Edit, and Journal Post
     11.- Navigate to: Accounts Receivable > Payments > Direct Journal Payments > Modify Accounting Entries
     12.- Open the Deposit/Payment at hand, and notice how the Complete flag is selected, and grayed out, in the 'Directly Journalled Payments' tab
     13.- Click on the 'Deposit Control' tab
     14.- Click on the 'Return To Search' button at the bottom of the page
     15.- From the search page, click on the Deposit ID of the transaction in question
     16.- Note that upon returning into the component, the default page is again 'Deposit Control' tab, which is correct, as it was the last visited
     17.- Click now on the 'Directly Journalled Payments' tab
     18.- Notice that the Complete flag is now editable, and user can un-select it
     19.- The system throws a Warning Message
     20.- Click OK, and save the changes

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps Word Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.


     " Warning -- Please use Direct Journal Entry panel to update the incomplete accounting entries. (6040,727)
       Incomplete direct Journal accounting entries can be updated in the Direct Journal Entry panel. Direct Journal Review panel is used for reviewing complete accounting entries only. "


As the Complete flag is un-grayed, the user can un-select it, and save the changes, which opens the door for further Accounting Entries modifications for the affected Direct Journal Payment. The existing Accounting Entries can be deleted, new ones be created, and once again Journal Generator executed to create new Journals for the same transaction. This can create duplicates in General Ledger module.


If the Direct Journal Payment Accounting Entries have been journalled into General Ledger module, and further edited, and posted, the Direct Journal Payment should be kept as Complete, and not allow to edit this flag anymore.


NOTE: In the  attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.