EGL 9.0: POPOST Entry Event Not Clearing Out The Temp Table Causes Unique Constraint Error at AE step (FS_EVENTGEN.E07395A3.GetPOstp) (SQL)
Last updated on MARCH 14, 2017
Applies to:PeopleSoft Enterprise FIN General Ledger - Version 9 to 9 [Release 9]
Information in this document applies to any platform.
Entry events not clearing out the temp table between records causes unique constraint error at AE step (FS_EVENTGEN.E07395A3.GetPOstp) (SQL)
-- 15.43.57 .......(FS_EVENTGEN.E07395A3.GetPOstp) (SQL)
UPDATE PS_EE_PO_TMP4 SET EE_EVENT_STEP='POPOST' WHERE BUSINESS_UNIT = 'US001'
AND PO_ID = 'P22' AND EE_SEQ_NUM = 1 AND SCHED_NBR = 1 AND DISTRIB_LINE_NUM =
1 AND UNPOST_SEQ = 0 AND EE_EVENT_STEP='PODN' AND RVRSL_FLG <> 'Y'
-- Row(s) affected: 0
-- 15.43.58 Process 9029 ABENDED at Step FS_EVENTGEN.E07395A3.GetPOstp (Action SQL) -- RC = 805
-- 15.43.58 SQL Error: ORA-00001: unique constraint (EMDBO.PS_EE_PO_TMP4) violated
1. Enter a PO with current year funding. Run budget checking and entry events.
2. Within the same accounting period, zero out the PO. Run budget checking and entry events.
3. Then change the accounting date and budget date, moving the dates into the next FY (The fund code is now expired year funding).
4. Then change a chartfield and run budget checking and entry events. Entry Events will fail with a unique constraint error.
Basically, FS_EVENTGEN is not clearing out the temp table if the monetary amount is zero. This is in the POUP/PODN CF change logic.
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