CALL_FUNCTION_NO_RECEIVER SAP ABAP Runtime Error call function no receiver

CALL_FUNCTION_NO_RECEIVER 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_NO_RECEIVER ABAP Runtime Error

The calling program, which has started an asynchronous RFC with the PERFORMING form ON END OF TASK addition, is not allowed to switch to a new internal session. Otherwise the reply to the call from an asynchronous function module cannot be forwarded to the related program context. A new internal session would be triggered by the keywords SUBMIT or CALL TRANSACTION for example.
Before an internal session can be built, all replies to the asynchronous RFCs must have been collected and processed, using ABAP keyword WAIT for example. Please see rfc error for more details about the possible cause of this runtime error and how it could be avoided.

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

Data received for unknown CPI-C connection <runtime parameter>. The calling program, which has started an asynchronous RFC with the PERFORMING form ON END OF TASK addition, is not allowed to switch to a new internal session. Otherwise the reply to the call from an asynchronous function module cannot be forwarded to the related program context. A new internal session would be triggered by the keywords SUBMIT or CALL TRANSACTION for example.
Before an internal session can be built, all replies to the asynchronous RFCs must have been collected and processed, using ABAP keyword WAIT for example. Please see rfc error for more details about the possible cause of this runtime error and how it could be avoided.

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

An error occurred because the reply to an asynchronous function module call was received (via CPIC protocol) and could not be forwarded to the related program context. This situation occurs if a SUBMIT or CALL TRANSACTION command is used after the asynchronous function module call using the PERFORMING form ON END OF TASK addition. The SUBMIT command generates an internal session that might prevent the reply to the asynchronous function module call from being forwarded to the session above it. Please see rfc error for more details about the possible cause of this runtime error and how it could be avoided.

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

In the main program, asynchronous RFCs with reply were made (CALL FUNCTION func STARTING NEW TASK taskname with addition RECEIVE RESULTS ...), and the program then switched sessions. This can happen when internal sessions are created in the main program, using the keywords SUBMIT or CALL TRANSACTION for example. The replies to the asynchronous RFCs therefore cannot be forwarded to the main program.