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.