In iProcurement, Duplicate Requisition Number Exists With the Same Requisition Number Except It is Prefaced With Two Hashes ## Which Prevents Buyer From Creating a Purchase Order For this Requisition (Doc ID 2959147.1)

Last updated on DECEMBER 17, 2024

Applies to:

Symptoms

One Requisition appears to have been duplicated and the business cannot create a PO due to the duplicate requisition numbers.      The duplicate Requisitions have the same Requisition Number except one of them has two hash tags before the Requisition Number. 

Here is the example scenario to help explain the issue.  In this example the Requisition Number is 12345

1) An initial Requisition 12345 was created and was been Rejected by Approver because it did not have  the correct order quantities on the requisition lines and is no longer needed by the business.

2) It is not known how exactly but a duplicate Requisition ##12345 with the correct line quantities exists and has since been Approved since it does have the correct data on the Requisition.   

Now the business needs to place the Requisition items onto a Purchase Order (PO) but while in Oracle Purchasing > Autocreate the Requisition Number is not available in the Requisition number field.  It cannot be found for the Buyer to be able to create a PO.  
 

Changes

Cause

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