Entry Event Failure Due To Unique Constraint With Multiple PO Closures/re-opens (Doc ID 2148782.1)

Last updated on JANUARY 13, 2017

Applies to:

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

Symptoms

Entry Event failure due to unique constraint with multiple PO closures/re-opens

This scenario is related to when a PO is closed and re-opened multiple times in the same fiscal year. If the PO is opened, the amount is changed, the PO is partially sourced to a voucher, closed and reopened on the same day, closed, and then reopened again, entry events will fail with a unique constraint when ran for the most recent reopen.

Replication Steps:
1) Enter a PO for $100 with an accounting date of 10/16/2015. Run budget check and entry events (creates POPOST).
2) Change the PO amount from $100 to $200 with an accounting date of 11/16/2015. Run budget check and entry events (creates reversal and restatement of POPOST).
3) Enter a voucher for $75 against the PO. Run doc tolerance, budget check, and post. Run entry events for the PO (Creates a POREVERSAL).
4) Close the PO with an accounting date of 12/09/2015. Run budget check and entry events (creates a POCLOSE).
5) Reopen the PO with an accounting date of 12/09/2015. Run budget check and entry events (reverses the POCLOSE and reverses and restates the POPOST).
6) Close the PO with an accounting date of 01/12/2016. Run budget check and entry events (creates a POCLOSE).
7) Reopen the PO with an accounting date of 01/19/2016. Run budget check and entry events. FS_EVENTGEN fails with a unique constraint at step FS_EVENTGEN.E07396E3.7396E-20.

Cause

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