FS_EVENTGEN goes to No Success for Expired Year and Entry Event Change. Abended at STEP FS_EVENTGEN.E07395A7.STEP02 (ACTION SQL) -- RC = 805 (Doc ID 1947055.1)

Last updated on AUGUST 10, 2015

Applies to:

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


When attempting to Entry Event a purchase order after making various changes, the FS_EVENTGEN process errors with the following.


The issue can be reproduced at will with the following steps:
1) Verify you are on bundle 43, open period, etc.
2) Enter a PO in FY14 with a single line for $100, run budget checking and entry events (creates POPOST)
3) In FY 15, reduce the line to $0, change the entry event code, and update the budget/accounting dates to FY15, run budget checking and entry events (creates PODN with new entry event).
4) Update the accounting date, re-budget check and run evener events. FS_EVENTGEN fails at E07395A7.Step2 with a unique constraint on the temp table.

SQL Error: ORA-000001: unique constraint (sysadm.ps_ee_po4_tmp5) violated.


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