Requisition Still Shows Encumbrance Even Though PO Has Been Created And Received (Doc ID 1614517.1)

Last updated on FEBRUARY 05, 2015

Applies to:

Oracle Purchasing - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.

Symptoms

You have observed that an encumbrance was not relieved when :

  - a requisition was withdrawn by a user
  - the requisition was then resubmitted and a Purchase Order created.

Encumbrances now exist for both the PO and the Requisition, which is incorrect.

It is possible to work around the problem by doing an encumbrance journal, but is there a long-term fix?

 

Example:
1) reserve requisition for account 53013 originally -->
Req DR 45073 for account X

2) Withdraw requisition -->
Req CR 45073 for account X

3) make change, budget account set to Y from X, reserve requisition again.
Req DR 45073 for account Y

4) Create requisition into PO.
PO  DR 45073 for account Y
Req CR 45073 for account Y

Expected/ Correct Summary:
Req DR 45073 for account X
Req CR 45073 for account X
Req DR 45073 for account Y
PO  DR 45073 for account Y
Req CR 45073 for account Y

Issue/ incorrect Summary
Req DR 45073 for account X
Req CR 45073 for account X
PO  CR 45073 for account X (?) <-- how is this line created?
Req DR 45073 for account Y
PO  DR 45073 for account Y
Req CR 45073 for account Y <--- missing

 

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