My Oracle Support Banner

Budget Checking Process(FS_BP) Abended at Step FS_BP_STAO.GetPrior.GetPrior With Cannot Insert Duplicate Key Error When Budget Checking Purchase Order(PO) Linked to a Procurement Contract (Doc ID 3001035.1)

Last updated on APRIL 25, 2024

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Budget Checking Process(FS_BP) runs to no success with below error when Budget Checking an existing already budget-checked PO after adding a PO line linked to a procurement contract, due to multiple rows on PO_LINE_DISTRIB with EE_SEQ_NUM = 1.

Note: Issue does not occur if when adding a PO line to existing PO, do "not" reference an existing PO Contract.

 

Error:

Cannot insert duplicate key row in object 'dbo.PS_KK_ACTIVITY_LOG' with unique index 'PS_KK_ACTIVITY_LOG'

Process ####### ABENDED at Step FS_BP_PEOD.ActLogC.iActLog (SQL) -- RC = 805 (108,524)

 

Steps:

1.For existing PO that has already been budget checked, query PO_LINE_DISTRIB for existing PO line and see that EE_SEQ_NUM = '1'
2.Add a PO line to existing PO, referencing an existing PO Contract, save the PO [Navigation: Purchasing > Purchase Orders > Add/Update POs]
3.query PO_LINE_DISTRIB for both existing and new PO lines and see that both rows have EE_SEQ_NUM = '1'
4.Approve the PO
5.Budget check the PO
6.Get duplicate insert error upon trying to insert new row to KK_ACTIVITY_LOG since a row already exists for the PO_LINE_DISTRIB with EE_SEQ_NUM = '1'
 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.