Last updated on JUNE 01, 2017
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Transactions that had budget errors are not being cleared from the online inquiries and are still coming up under commitment control.
Example: A particular voucher that had the budget exception error of "No Budget Exists", this was later fixed and the voucher ran through budget checking again
and status of the voucher changed to valid. However in Commitment Control (page: KK_XCP_HDR_AP1), looking up the voucher still shows an exception error.
Another scenario was tested where a voucher was created to exceed the budget so a budget exception error would come up. Looking in Commitment Control,
there was a budget exception error, which is expected. Later the amount of the voucher changed so it did not exceed the budget.
In this scenario looking at the Budget Check Exceptions page for this particular voucher did not show any results.
In Commitment Control (page: KK_XCP_HDR_AP1), looking up the voucher still shows an exception error.
Expect the exception not to be available since it was fixed
The issue can be reproduced at will with the following steps:
1. Create and budget check voucher with budget exceptions
2. Run budget checking
3. Resolve the exception
4. Navigate to Commitment Control > Review Budget Check Exceptions > Accounts Payable > Voucher
AP <Bug 24811520> - AP: BUDGET EXCEPTIONS NOT CLEARED FROM PS_KK_EXCPTN_TBL WHEN VOUCHER IS DELETE
was where issue was originally observed. When deleting a voucher with budget exceptions, the voucher is deleted but
the record remains on the PS_KK_EXCPTN_TBL table. The record should be deleted from the PS_KK_EXCPTN_TBL when the voucher gets deleted.
GL was impacted hence the creation of <Bug 23064598> - GL:DELETING PO WITH BUDGET EXCEPTION DOES NOT REMOVE ROWS FROM KK_EXCPTN_TBL
Development eventually rolled back the code changes of <Bug 23064598> and created <Bug 24837014> - GL: BUDGET EXCEPTIONS NOT CLEARED FROM PS_KK_EXCPTN_TBL WHEN TRANSACTION IS DELE
to deliver a new fix. They moved the new SQL to a do-when step. After the change, the delete KK_EXCPTN_TBL will go to different step based on the value of KK_PROCESS_TYPE.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms