EGL 8.4: Budget Check (FS_BP) Abends at Step FS_BP_PEOD.ActLog.iActiLOg with Unique Constraint When Inserting Into PS_KK_ACTIVITY_LOG.
(Doc ID 865706.1)
Last updated on JANUARY 03, 2020
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 8.4 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Sep-2012**
Budget was not working for one particular account. The budget check status was staying at 'N' when budget checking a Purchase Order.
Also found that the account does not work when budget checking from any other transaction types such as Voucher and General Ledger Journal.
When running budget check using that same account in Journal entry, get unique constraint violation error in PS_KK_ACTIVITY_LOG.
When using the particular expense account, budget fails with error: Cannot insert duplicate key row in object PS_KK_ACTIVITY_LOG.
SPECIFIC ERROR MESSAGE (if applicable)
SQL error. Stmt #:1603 Error Position: 0 Return: 805 Cannot insert duplicate key row in object 'dbo.PS_KK_ACTIVITY_LOG' with unique index 'PS_KK_ACTIVITY_LOG'.
ABENDED at Step FS_BP_PEOD.ActLog.iActiLOg(SQL)—RC = 805 (108,524)]
STEPS (Sequence of Events)
By following these steps the issue can be reproduced:
1. Create Transaction such as General Ledger Journal.
2. Use the specific account in transaction that will be budget check.
3. Run Edit and Budget check online or via the Batch process.
4. Process will error with Unique Constraint violation in KK_ACTIVITY_LOG.
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