KK Tables Exist After Failing Budget Check and Canceling Requisition (KK_SOURCE_HDR, KK_SHDR_REQ, KK_SOURCE_LN and KK_EXCPTN_TBL)
(Doc ID 2562233.1)
Last updated on DECEMBER 09, 2019
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 9.2 and later
Information in this document applies to any platform.
When a Requisiton which has never successfully been budget checked is canceled and the accounting date is in a closed period requiring the accounting date be changed the commitment control tables are not cleaned up.
So this Requisition still shows as a budget exception even though it is canceled. Still showing data in (KK_SOURCE_HDR, KK_SHDR_REQ, KK_SOURCE_LN, KK_EXCPTN_TBL).
The issue can be reproduced at will with the following steps:
1. Create Requisition with amount 1,200,000.00 in an open accounting period.
2. Budget Check Requisition. Getting Budget Status = 'Error'
3. Close the requisition accounting period (Navigation: Set Up Financials/Supply Chain > Business Unit Related > General Ledger > Open Periods > Open Periods)
4. Execute queries: There are data in: PS_KK_SHDR_REQ, PS_KK_SOURCE_HDR, PS_KK_SOURCE_LN and PS_KK_EXCPTN_TBL)
5. Cancel the requisition. Got the messages:
"Cancelling a requisition will commit any changes made and prefent further changes. Continue? (10100,7)" 'Yes'
"The Accounting Date XXXX-XX-XX is not open. The Open period for 'XXXXX' is... (10200,373)" 'OK'
6. Change the accounting date to be within the open periods. Save
7. Requisition cancelled.
8. Execute queries: There are still data in: PS_KK_SHDR_REQ, PS_KK_SOURCE_HDR, PS_KK_SOURCE_LN and PS_KK_EXCPTN_TBL) and should not.
9. Go to Commitment Control Exceptions Page and the Requisition Exceptions still appearing.
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