Super User Getting Budget "Security Error" When Overriding a Budget Transfer Journal That is Already in Budget Security Error (Doc ID 2931809.1)

Last updated on MARCH 01, 2023

Applies to:

Symptoms

A Super User is getting a Budget "Security Error" when overriding a Budget Transfer Journal that is already in Budget Security Error.
This was encountered after applying fix for <Bug 33903641> - EGL 9.2: BUDGET TRANSFER JOURNAL DOES NOT TRANSFER TO PROCESS MONITOR

Note: A super user cannot override a budget transfer journal that has a Security Error without completely going out of the page and coming back in; then must click Save to get the budget status to go from 'Security Error' to 'None' before being allowed to click Process to trigger budget checking and complete the budget security override. Only occurs for override of security error with budget transfer journal and not for override of security error for regular budget journal.

The customer’s issue is that prior to applying the POC for Bug 33903641 the Superuser did not have to click Save before budget checking. After applying the POC the Superuser gets stuck not knowing s/he has to click Save before budget checking because that’s the way it worked before the POC. So the Superuser calls the helpdesk to report this, thinking they cannot proceed with budget checking. With multiple Superusers the customer does not want each Superuser calling the helpdesk thinking they are stuck.

Error Message:
Security Error (1802,998)

Steps:
1.Set up Budget Security for budget journal entry and budget transfer

--assigned only to userid GLS1, not assigned to userid GLS2

2.Login as GLS1, can enter and post budget journal

3.Login as GLS2, after enter budget journal when click Save get Status 'Security Error'

4.Log back in as GLS1, open above budget journal, can click on Process button to override security error which then triggers budget checking and status goes to Posted

5.Still logged in as GLS1, can enter and post budget transfer journal

6.Log back in as GLS2, after enter a budget transfer journal when click Save get Status 'Security Error'

7.Log back in as GLS1, open above budget transfer journal, click on Process button to override security error, however get popup page with 'Security Error' and cannot proceed further

8.Developer troubleshooting found that due to attached codeline for budget transfer journal the Super User GLS1 must go out of page and come back in, then first click Save which changes Status from ‘Security Error’ to ‘None’ and only then able to click Process button to override security error which then triggers budget checking and status goes to Posted [Note: issue only with override of budget transfer journals]

Changes

Cause

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