EGL 9.0: When A POPOST Entry Event, FS_EVENTGEN Is Not Clearing Out The Temp Table If The Monetary Amount Is Zero Leads To Incorrect PODN Entry Event (Doc ID 1675817.1)

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.

Symptoms

When a POPOST Entry Event is posted in the current fiscal year, but the PO is zeroed out and a PODN adjustment is made in the following FY, the PODN entry correctly decreases the PO amount to $0, zeroing out the document.

However, if the PO is then adjusted back to its original amount or any amount other than $0, entry events creates an incorrect PODN adjustment and essentially doubles the PODN entry event amount.

Replication steps:
1. Enter a PO with current year funding of $300. Run Budget check and entry events.
2. Enter a PODN adjustment in the following FY, changing the price to $0. Run Budget check and entry events. The PODN entry correctly decrease the PO amount to $0.
3. Within the same accounting period and fiscal year, change the PO back to its original amount or any amount other than $0. In this case, entry events will create an incorrect PODN adjustment and essentially doubles the PODN entry event.

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.

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