GL Entry Event 9.0: Incorrect PODN For Expired/Unexpired Funding. (Doc ID 1927428.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

PeopleSoft Enterprise FIN General Ledger - Version 9 and later
Information in this document applies to any platform.

Symptoms

On : PeopleSoft FSCM 9.0, Bundle 43

ACTUAL BEHAVIOR
---------------
Entry events in producing an incorrect PODN transaction when a PO is processed initially as expired funding.

EXPECTED BEHAVIOR
-----------------------
PO Entry Event should not create a new PODN entry

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

0. Verify you are on Bundle 43; open accounting periods, etc.
1. Enter a PO for $100 with FY13 funding, an accounting date of 9/1/2013, and budget date of 10/1/2013. Run budget checking (override expired funding as necessary) and entry events. Entry events create POUP transactions.
2. Change the budget date on the PO entered in Step 1 to 9/1/2013. Run budget checking and entry events. Entry events produces a PODN (to reverse the POUP) and a POPOST, correctly.
3. Change the accounting date to 10/1/2013 leaving the budget date as 9/1/2013. Run budget checking and entry events. Entry events reverses and restates the POPOST correctly, but incorrectly produces a PODN for $100.


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