CALL_FUNCTION_SEND_ERROR : RFC Calling Function Termination

Updated May 18, 2018

Hello Experts,

I am getting the run-time error CALL_FUNCTION_SEND_ERROR on the receiving side of the RFC communication when the connection to the program that is calling the function is interrupted.

Thanks in advance.

Comments

26 Apr 2016 5:27 pm Abhijeet Mudgal Best Answer

There could be several reasons behind the error; here are a few common ones:
1. When the calling program does not receive the responses of all of the pending RFCs during an asynchronous RFC with response, said runtime error can be triggered. When the program is terminated, a background job that lists the status of the operation is set to “finished” and all asynchronous response sessions that were still open at that point lead to the CALL_FUNCTION_SEND_ERROR.
answer: To solve this problem, simply make sure that the calling program does not terminate before ALL of the asynchronous RFCs that are pending have been retrieved by the program
2. The error can be caused when the program that is calling the RFC is a SAP Java Connector Jco Version 2.x. When, in the RFC function module that has been called, there is a call back to the java connector, a problem occurs because in 2.x, call back is not supported. This leads to the error.
answer: To solve this problem, refer to 1290320 and 1352265. In the section on “communication to an external program to ABAP” there is a set of instructions for setting the BACK destination for call backs properly in these cases.
3.Thirdly, when there is an RFC client communicating with the ABAP server, said run time error might be caused when the client system terminates the “receive” status while data is being sent to the client.
answer: To solve this problem, see 1352265 which lists a series of scenarios where the error can be caused. Once again, answers can be found in the section titled “communication from an external program to ABAP”.