Outstanding Requisition Demand in MTL_SUPPLY is Not Relieved When Requisition Withdrawn, Canceled or Deleted (Doc ID 1501479.1)

Last updated on JUNE 08, 2017

Applies to:

Oracle iProcurement - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

Withdraw, Cancel, or Delete a requisition in iProcurement and see that the demand previously consumed per MTL_SUPPLY by the requisition is still the same.  Users expect the demand to be relieved - available for other use - but instead it is still tied up by the requisition.

STEPS TO REPRODUCE

1.  Create a requisition in iProcurement for items in master items
2.  Verify that the MTL_SUPPLY reflects the items requested on the requisition, so that there are fewer items available than before the requisition was created
3.  Withdraw, Cancel, or Delete the requisition or requisition lines
4.  Verify that the MTL_SUPPLY still reflects the items requested on the requisition.
Users expected that the MTL_SUPPLY should be updated since the requisition was withdrawn, canceled, or deleted, but no change occurs in MTL_SUPPLY

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