EGL: 9+ Ledger_KK Out Of Sync With Activity Log Because Header Is Not Locked During Budget Checking And Another User Changes or Deletes The Transaction (Doc ID 1576799.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9 and later
Information in this document applies to any platform.

Symptoms

Customer Environment
===================
Application Release 9.0
Bundle level 18


Issue
====
Several batch processes run for budget checking throughout the day. If a new transaction gets created and picked up by the budget check and while running, but the user goes back to delete or cancel the transaction while the transaction is being processed at the same time the Commitment control tables can get out of sync with the transactional tables. It appears to be an issue for AP, AR, EX, Cost and PO.

Here is example of one such test

Replication steps from GSC:
--------------------------------------
1. Enable Commitment Control(KK)
2. Create a voucher with 30 Distrib Lines. Save it. Budget_hdr_status is set to 'N'
3. Create run control to run Budget checking.
4. Open new window to delete the Voucher
  Do NOT click on OK button yet
  While FS_BP is processing in Step AP_BP_EDIT.OpenPer.GetFlg, delete the Voucher (PS: Step FS_BP_SHDR.iSrcTAO.iSrcTAO has already executed).
  Voucher is deleted
5. FP_BP finished with success (See details about the Steps/trace on screenshots)
6. Check Budget Active Log.
 ERROR: FS_BP has produced KK entries for deleted Voucher (PS_VOUCHER.ENTRY_STATUS = X).

OR

Replication steps from customer:
---------------------------------------------
1. Create a voucher. Save it. Budget_hdr_status is set to 'N'
2. Open a second window where the voucher can be budget checked.
3. Have the third Window ready for the Voucher deletion. The voucher is not budget checked yet nor deleted.
4. Run the FS_BP processor for the voucher. wait till the process goes from queued to processing. Refresh every second.
5. when the FS_BP shows processing, on the third window where the delete voucher is ready, press the delete button.
6. Voucher is successfully deleted (entry_status marked as 'X') and the FS_BP has produced KK entries.


BUSINESS IMPACT
-----------------------
Transaction in commitment control out of sync with LEDGER_KK

Cause

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