EGL9.2.Post Journal Process (GL_JP) Is Bypassing Journal Source Security By Role Configuration And Journal Can Be Posted Even If the Cutoff Period Is Past Due
(Doc ID 2809210.1)
Last updated on SEPTEMBER 23, 2021
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
When setting the Journal Source Security by Role, the Post Journal (GL_JP) program is ignoring this restriction and journals can be posted even if the Cuttoff period is past due.It is only validating the Journal for Posting by Journal Source User.
While trying to post the journal from Online , the user cannot post the journal.
The issue can be reproduced at will with the following steps:
1 .Add a journal source security by Setid using the navigation path : Set Up Financials/Supply Chain> Security>Journal Source Security SetID
2. Add the BU US004 to Journal Source Security Bu and associate all the journal sources by using the navigation Set Up Financials/Supply Chain> Security >Journal Source Security BU
3. Create a new role jss_role and add it to the user VP2 by using the navigation (Ptools>security >permission and roles>roles). Go to Ptools> Security>User profiles>User profiles and choose VP2.
4.Setup Journal Source Security by Role for Bu US004 and add “Allow access” for all sources and deselect the other options for all. Navigation: Set Up Financials/Supply Chain> Security >Journal Source Security BU
5.From Setup Fin > Business Unit related>General Ledger>Ledgers for a unit >for the bu US004 and ledger group RECORDING go to “Period end cutoff Definition” and add the period for ledger RECORDING And fiscal year 2021
6.For source ACC add the Cutoff Days 7.
7.Sign in using user VP2
8.Create a new journal with journal date 30/04/2021. Journal Date is 30/04/2021, which is in period 4. Today's date is 18/05/2021, which is past the cutoff date. Use Navigation: General Ledger>Journals> Journal Entry> CreateUpdate Journal Entry
9.Go to General Ledger>Journals>Process journals>Post journals and notice that both source ACC and the journal id is available to be selected, while it should not be. The process runs in success and the journal is posted not
taking into consideration the journal source security by role.
10.Notice that the journal source security by user is not setup .
Check the replication document attached.
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