Question

Purchase Requisition to Purchase Order have a bug?

  • 19 July 2021
  • 5 replies
  • 408 views

Userlevel 2
Badge +4

We are having some purchase requisition line status not changing to “PO CREATED” after it is released and PO is created.  Sometimes we need to change the  Supplier then the requisition  will go into “ Authorization Required” status.  For some reason, when that Approval of the requisition is done again, the requisition header will move back into “Authorized” status. That is when the planner doesn’t have the ability to re-Release the requisition.   Is this the reason the line status hangs in status “ Released” forever even if a PO is created?  

 

IFS help notes:

  • The selected purchase requisition lines are converted into a purchase order. The requisition lines are added to an existing purchase order, or a new purchase order is created. The status on the requisition header is updated from Released or Authorized to Closed when all the requisition lines are converted. The requisition line status is updated to PO Created.

 

 


This topic has been closed for comments

5 replies

Userlevel 7
Badge +19

@Sunnie90 , IFS which version you are using?

Userlevel 2
Badge +4

Version 9

Userlevel 3
Badge +6

Hi, 

Do you have any customization done on PR or PO Process? 

Thanks 

L P Reddy 

Userlevel 7
Badge +19

@Sunnie90 , we use App10 only, I couldn’t recreate there the scenario you explained, sorry. Perhaps someone with App9 access can try. 

Based on what you explained, did you try the ‘authorized’ requisition line ‘Requisition to Order’ through right mouse button on the line(s)? 

 

Help Text on the line status says

Authorized: All lines requiring authorization have been authorized and can be converted into purchase orders. No new requisition lines can be added to the requisition.

Userlevel 2
Badge +4

@EnzoFerrari , Yes, we did create by RMB “ requisition to order”  but the line did not change status to say it.  So we put a note on line with PO number.  This company has many customizations and most likely it could be the Authorization process steps taken that stops the line from showing a PO was created.

 

Thank you for the reply!