CALL_FUNCTION_TASK_EMPTY 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.
Do not use empty task names for aynchronous connections.
For more information about task names in asynchronous RFCs, see SAP
Note 1060205.
Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.
The task name cannot be empty when using asynchronous RFC.
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.
An asynchronous RFC was called with an empty task name.
CALL_FUNCTION_TASK_EMPTY - call function task empty CALL_FUNCTION_TABLE_NO_MEMORY - call function table no memory CALL_FUNCTION_TABINFO - call function tabinfo CALL_FUNCTION_SYSCALL_ONLY - call function syscall only CALL_FUNCTION_SYNTAX_ERROR - call function syntax error CALL_FUNCTION_SNC_REQUIRED - call function snc required