EGL9.2:Cancelled Requisition Lines Cause Unique Constraint On Entry Event Execution

(Doc ID 2340076.1)

Last updated on JANUARY 03, 2018

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]
PeopleSoft Enterprise SCM eProcurement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.



Cancelled Requisition Lines cause unique constraint on Entry Event Execution

If a requisition line is cancelled, a unique constraint results when attempting to run the entry event process. It appears that the SEQNUM field is not getting correctly incremented, causing duplicate rows to be inserted into PS_EE_REQ_ACCTG_LN.

This has already been fixed in version 9.1. The same fix should be applied to 9.2. Please see <Document 1671901.1>.


08:56:57.757 Process 159707 ABENDED at Step FS_EVENTGEN.E07420.Step03 (Action SQL) -- RC = 805
-- 08:56:57.789 SQL Error: ORA-00001: unique constraint (SYSADM.PS_EE_REQ_ACCTG_LN) violated


The issue can be reproduced at will with the following steps:
1) Create a requisition. Budget check and Entry Event.
2) Source req to a purchase order. Budget check. Run PO EE and Req EE.
3) Change one or more chartfields on the PO. Budget check. Run PO EE and Req EE.
4) Cancel one of the requisition lines, budget check. Run Req EE

Replication screenshots attached: 


Due to this issue, users cannot cancel a requisition line


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