Skip to main content

I am coming across an issue with IFS Cloud 24R1 where a Request for Order Quotation has been raised from a Purchase Requisition in error and the RFQ then fully deleted. Raising the RFQ changes the Request Type to Quotation Request, which sticks, even when the RFQ is deleted. If the Purchase Requisition Line is authorised, the Request Type cannot then be changed back to Purchase Request, and this forces the User to create and process a Request for Order Quotation through to approval. This feels like a bug and the current process is not user friendly leaving the User with an authorised Purchase Requisition Line that they cannot convert to a Purchase Order without going through the lengthy RFQ process to approval.  

Hi ​@CooAlastL  - ive tested this in 23R2 and 24R2 and after deleting (or cancelling) the RFQ, im still able to edit the request type on the req line and change it back to Purchase Request. Are you receiving an error message, or when you click the edit button on the Req line is it just greyed out? Unfortunately I dont have access to a 24R1 environment, but thought it would be worthwhile checking if the behaviour is similar in others.

Hi ​@WyrJamesG. Hope you are well. It seems more restrictive if the PR Line has been Authorised, and then does not allow any changes to the Request Type. Another frustrating thing is that if the Request Type is changed back to Purchase Request, the price reverts back to the original price prior to Update Price Manually being selected and a different price entered. Thanks for checking and responding. 

Hi ​@CooAlastL ,

I did a quick test in a Core environment with 24R1 version and you are totally right, i.e. there is a validation implemented when trying to change the Request Type in an already authorized line from Quotation Request to Purchase Request:
 

 

But I’m not sure if this kind of change in Request Type should raise this error. Also, considering that you have also this problem of price changed back when price had been updated manually before, I would recommend to create a support case, so this can be reviewed internally and consult with R&D, if needed.

Regards,

Pilar

​@Pilar Franco Many thanks for confirming. I will try and arrange a case to be raised. 

 

Kind regards,

 

Alastair

Reply


Terms & ConditionsCookie settings