Question

Requisition to $0 Purchase Order

  • 7 December 2021
  • 4 replies
  • 209 views

Userlevel 3
Badge +3

We recently upgraded from APPS8 to APPS10 and the business has found that we can no longer convert $0.00 No Part Purchase Requisitions to a PO with right click → Requisition to Order... due to the error “Field [Price/Base] is mandatory for Purchase Order Line Nopart and requires a value”. 

The business reports that they used to be able to do this in APPS8. They are working around it by updating the Requisition to $1.00, converting it, and updating the price on the PO to 0.

In the initial case reported to IT they were sending a part out for warranty repair at no cost, and needed a PO in order to receive it back in. Is there a recommended alternative to process no cost warranty repairs? Or other recommend process to convert $0 no part PR lines to a PO? 


This topic has been closed for comments

4 replies

Userlevel 4
Badge +7

Hi @jenotto,

 

In APP10 also you should able to save and convert Purchase Requisition to a PO with 0 value. Usually the application prompt an information message when you are saving a No part Requisition line without a price (Price/Curr is set to zero).

Let us know the UPD version which you are using now?

 

Regards,

Harsha

Userlevel 3
Badge +3

Hi Harsha, thank you for responding.

We are on UPD10. The pop-up message does say Error and does not allow the conversion to a PO to take place. We do have a variety of customizations in place so we might be doing this to ourselves. 

 

Userlevel 4
Badge +7

Hi @jenotto,

 

If you have implemented any customization related to this functionality, it might require a technical investigation to identify the root cause. Therefore, I would suggest you to raise a support case if you can do so.

 

Regards,

Harsha

Userlevel 5
Badge +7

Hi @jenotto,

 

Usually, when it comes to App 10 functionalities, it should be similar to its previous versions in functionalities except in special conditions. If functionality worked well under App 8 and the current issue might be caused due to an issue in the migration of customization ( most probably ) from App 8 to App 10. Therefore I believe it is best to create a case for IFS Support for further technical investigations

 

Best Regards,

Vindya.