My Oracle Support Banner

Why Is A Remaining REQ Encumbrance In Project Costing Not Released When The Requisition is Closed? (Doc ID 1666442.1)

Last updated on JULY 21, 2020

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.

Goal

Qn1:We have a scenario where we create a requisition and from that a purchase order in Purchasing. The purchase order is fully received, matched and closed. However, the pre-encumbrance of the REQ row in Project Costing does not released if the requisition was not fully used. Commitment Control closes everything out correctly but Project Costing does not release the unused requisition amounts. This is also happening if the requisition is never used to generate a purchase order. Why is that pre-encumbrance not reversed?
 
Qn2:Since commitment control does release the remaining encumbrance for requisitions, how can we report on this discrepancy and show the correct encumbrance amounts in Project Costing?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.