EEX 9.2: Approve Button Gets Grayed Out After Accounting Date Change Even If Commitment Control Is Not Required Before Approvals At Expenses Options Level
Last updated on SEPTEMBER 12, 2017
Applies to:PeopleSoft Enterprise FIN Expenses - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
An inconsistency has been detected at the time of trying to approve a submitted Expense Report that has been previously budget checked successfully, but that its Accounting Date value got modified right before clicking on the Approve button. The system is then performing the proper validations, and due to the fact that the Accounting Date has changed, the Budget Status of the transaction is correctly being reset from 'Valid' to 'Not Budget Checked'. However, it throws an Error Message when trying to subsequently approve the transaction right away.
If at the Expenses Options level for the Set ID used in the involved Business Unit, the 'Budget Checking Required Before EX Approval' flag is un-selected, then it is expected that no matter what changes are done at the transaction header or line level, that approvals should still be allowed no matter the Budget Status of the Expense Report.
The Approver is unable to successfully approve the Expense Report if the Accounting Date has been modified. The system validations reset the Budget Status from Valid to Not Budget Checked, which is correct, but is requiring a new Budget Check run before any approval, and that is not the expected behavior. The Users need to Save Changes, get out of the Component, search for the transaction back in the Approvals Console, re-open it, and only then the Approve button will be available again.
1.- Enable Commitment Control at Installed products level for General Ledger, and Expenses
2.- At the Expenses Business Unit Options, the requirement to budget check Expense Reports before approval has not been selected
3.- Create a new Expense Report, and submitted it for approval
4.- Confirmed that the Expense Report has been successfully routed for approval
5.- Launch the Budget Checking process for the transaction
6.- Open the Expense Report as an Approver, and confirm that the Budget Status is VALID
7.- Change the Accounting Date of the Expense Report
8.- Click on APPROVE button
9.- The system throws an Error Message, and the APPROVE button becomes grayed out
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.
" The Accounting Date was modified.
Please Budget Check again before approving the report. "
The system should not require the transaction to be Budget Checked again before approving it, as per specified in the Expenses Options level, where the requirement of commitment control budget checking before any approval for Expense Report transactions has been de-activated.
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