FS_EVENTGEN: Incorrect PODN Entry is Created when Fund Code (Expired Chartfield) Changes from Value that is Not Expired to Value that IS Expired.
(Doc ID 2125379.1)
Last updated on NOVEMBER 23, 2019
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.
A Purchase Order (PO) was created with unexpired funding in the current fiscal year. The fund code was then changed to expired fund. Entry Events then reversed the original obligation with a PODN on the unexpired fund code, which is unexpected.
The issue can be reproduced at will with the following steps:
1) Create and budget check a PO for $xxxxin FY16 with FY16 funding
2) Entry Event the PO
2A) POPOST is created
3) Change the fund code to expired funding (ie. FY15 funding)
3A) Change can occur in the same accounting period or across accounting period, results are the same
4) Budget check and Entry Event the PO
4A) Entry Events reverses the original obligation with a PODN entry with the unexpired fund code. This is incorrect.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document