Last updated on FEBRUARY 26, 2016
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 8.9 to 9.2 [Release 8.9 to 9]
Information in this document applies to any platform.
When a purchase order that has been created from a requisition is cancelled and the cancellation specifies that the requisition will not be resourced, a REQ row remains in Project Costing that will not be offset although Commitment Control correctly shows that the pre-encumbrance generated by the requisition has been removed. Why is this happening? Shouldn't PC_POADJUST remove it?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms