EGL9.2.Journal Source Security By Role Is Ignored By Journal Copy Process
(Doc ID 2972756.1)
Last updated on SEPTEMBER 06, 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
After setting Journal Source Security by Role in order to restrict access to source "ACC" , the user that doesn’t have access to this source is able to use the Journal Copy process and copy an existing journal with this source and create a new journal , which is incorrect.
Issue can be replicated using the following steps :
1.Go to Journal Source Security by BU ( Setup Fin>Security> Journal Source Security by BU) and add bu US003. For this BU , add the sources ACC and CFO.
2.Go to Journal Source Security by Role (Setup Fin>Security> Journal Source Security by Role) and for the role VICE PRESIDENT check the 2 sources.
3.Create a new role “vice president1” by copying the existing role VICE PRESIDENT. ( PeopleTools >Security>Permissions and roles>Copy roles)
4.For the role “vice president1” add the same sources ACC and CFO to US003 but don’t give any access.
5.Add the role “vice president1” to user VP2 (PeopleTools >Security>User Profile )
6.Create a journal with user VP1 and BU =US003 and source = ACC and post it ( General Ledger>Journals>Create/Update Journal entries)
7.Login with VP2 and go to Journal Copy process and notice that journal created by user VP1 is available for copying – even though user VP2 doesn’t have access to source ACC.
More information can be found in the replication document attached.
Any similarity to actual companies or actual persons, living or dead, is purely coincidental and is in no way intentional on the part of Oracle.
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 |