EGL9.2: User Can Submit Or Approve Budget Journal in Header Status 'Security Error' Although This is Not Expected And Should Not To Be Allowed.

(Doc ID 2084878.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

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


On :  9.2 version, KK-Security/Notification/WF

- Image 9.2.009
- Product Version 9.2
- PeopleTools 8.53.23

Set budget security for budget period 2015 so that user A can only create budget journal in period 2015.
When user A creates budget journal in period 2014 and save it,  the system throws a Budget Header Status 'Security Error'.
Despite this 'Security Error', user A can still submit this budget journal for approval and approver user B can approve it.
However, user A cannot post this journal nor approver user B can deny it.

Expect that when a Budget Header Status is 'Security Error', user is not allowed to submit a journal for approval.

The issue can be reproduced at will with the following steps:
1. Set up rule definitions only create budget journal and adjustment in period 2015.
2. Assign rule for permission list BA_OF then run Request build rule
3. Assign permission list to user.
4. Create a budget journal in period 2014, then click save, the system alerts security error. This is expected because budget is only allowed to enter in period 2015.
5. Send journal for approval. Even with security error, the system allows to proceed.
6. Approver is able to approve this budget journal.
7. However, user cannot post this budget journal due to this security error.

The issue has the following business impact:
Due to this issue, this journal is stuck in the system. It cannot be posted or denied and then modified.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms