EGL:9.2 SQL Deadlock In FS_BP Inserting Into Ledger_KK (Doc ID 2115743.1)

Last updated on MARCH 14, 2016

Applies to:

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


On : 9.2 version, KK-Budget Checking


When budget checking multiple transactions with many transaction lines at the same time LEDGER_KK and KK_ACTIVITY_LOG can get out of balance. The problem we see is that when inserting into LEDGER_KK in FS_BP_POST.InsertKK.InsLedg.SQL there can be a SQL deadlock error (return code 60) which is not handled like the duplicate insert SQL error (return code 805). If the deadlock occurs during the update to LEDGER_KK the SQL error is not ignored and the process aborts so LEDGER_KK and KK_ACTIVITY_LOG do not get out of balance.


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