CALL_FUNCTION_TASK_YET_OPEN SAP ABAP Runtime Error call function task yet open

CALL_FUNCTION_TASK_YET_OPEN is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: A - ABAP Programming Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

CALL_FUNCTION_TASK_YET_OPEN ABAP Runtime Error

For more information about task names in asynchronous RFCs, see SAP Note 1060205. Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

RFC task <runtime parameter> already open. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

The application program is trying to make an asynchronous RFC call using CALL FUNCTION ... STARTING NEW TASK <runtime parameter>. This action has been carried out several times in succession (in parallel). This means that the same task name was used in parallel in multiple RFC calls, which makes it difficult to assign the RFC responses.
To allow unique assignment of asynchronous RFC calls to their response FORM routines, no more than one asynchronous RFC call should be made at any one time with a given destination and task name. No parallel calls should be executed for a task name. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.