Purchase Order(PO) Liquidates Pre-Encumbrance In Wrong Budget Period
(Doc ID 856321.1)
Last updated on NOVEMBER 05, 2019
Applies to:PeopleSoft Enterprise SCM Purchasing - Version 8.9 to 9.1 [Release 8.9 to 9]
Information in this document applies to any platform.
Why does a PO liquidate the pre-encumbrance in the year the PO is created instead of the year when the req was created? And what can be done to correct this?
1) Our budget periods match our fiscal year calendar (July->June)
2) Requisitions created in June (fiscal year 2009).
3) Purchase Orders were created after July first (fiscal/budget year 2010)
We observe that the PO liquidates the linked pre-encumbrance, but does so in 2010 so we now have a negative pre-encumbrance in 2010 while orphaning the one in 2009.
Is there a way after the Purchase Order has been created to eliminate the pre-encumbrance in 2009 and restate the error liquidation in 2010? We can create GL Journals against our KK ledgers, however these do not post. Is there a better way?
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