Skip to main content
Question

Change Work Task status from Work Started to Released (282)

  • May 20, 2026
  • 1 reply
  • 20 views

Forum|alt.badge.img+7

Our company uses work order and work task processes. We typically use one work order with one work task. A user has changed the work task status to Work Started and is now unable to change back to Released (it was changed in error and for our flow needs to be in Released status and update a value in the Work Stage which is how we’ve overcome the lack of work task status). The work task in question has a connected Maintenance Purchase Requisition which is Closed Status. This was used to create a part requisition line for an external service purchase order which is in released status. This error message is received when attempting to change the status back on the Work Task or Work Order. 

ERROR: It is not possible to initiate a Tender flow when one of more connected Work Tasks are in status Released or above.

Turned on debug console and found the error is due to WORK_ORDER_REQUIS_HEADER_API starting at line 1379 where it’s attempting to use Get_Create_Rfq. Reviewed this function and searched the work_order_requis_header_tab for the work order. The requisition_no value matches the maintenance purchase requisition. The value in Create_rfq and release_wo are both FALSE. 

The tender process is not something we are familiar with. We do not see this same error if we have a work task that does not have a connected maintenance purchase requisition. How can we overcome this issue? It is causing a problem as this work task is now in the incorrect status for our workflow. 

1 reply

Forum|alt.badge.img+12
  • Hero (Partner)
  • May 26, 2026

Hi,
Is there any possibility of cancelling this purchase order?

If so, this will cancel the customer order that was created to send the item to the supplier AND will ask you if you want to reopen the purchase requisition.

After reopening the PR, you can revert the requisition to “Planned,” remove the ESO requisition line, and then remove the Maintenance Purchase Requisition as well.

You will then be able to return your work task to “Released.”

I tested this in 25R1.

------------------
Regarding the error (noting that the wording is somewhat different to what we usually see in IFS), the “tendering process” it refers to relates to requisitions (which lead to quotations), as you have correctly identified. 

This is the only reason I can think of for why this error appears:

When a work task has progressed beyond “Released,” IFS assumes that all financial decisions have already been made for the maintenance purchase requisition you created and processed. Therefore, it blocks any actions that could reinitiate or re-evaluate those decisions and return to the RFQ (tender) process.
Why this happens, is something we can ask IFS. There may have been an error coming up in the process when they did not restrict reversing the status of WT.

However, there is nothing preventing you from creating a new requisition and initiating an RFQ process from it.

Hope this helps
Asanka