RFC termination with the error message CALL_FUNCTION_OBJECT_ID

Cause and conditions

The error message CALL_FUNCTION_OBJECT_ID is triggered whenever the RFC delta manager has problems coordinating the table parameter names between the sender and receiver in an RFC communication when internal tables are passed.

One of the table parameter names is either wrong or the receiving side no longer supports that table parameter. A typical example is the function module RFC_PING that from Release 3.0B no longer supports table parameters with the name RFCTAB. If you use this function module to test the connection, you must either adjust the passing of the table parameter accordingly or remove the call from the program.

Solution

• Check the names of the tables that you want to pass and correct their names if necessary. Check the table parameters to see if they are implemented as parameters on the receiving side. Note that the table parameter for the function module RFC_PING has been changed and that it now no longer expects any table parameters. You may need to adjust the function module or remove the call for RFC_PING.

• Switch off the delta manager function for the RFC communication. There are two ways of doing this:

• On the sending side, by calling the function module RFC_CONNECTION_CLOSE for the RFC destination that is causing problems. This closes the RFC connection.

• On the receiving side, by executing one of the ABAP statements SORT itab or REFRESH itab in the called function module for all table parameters.
  Notes:
  The function module 'RFC_CONNECTION_CLOSE' has existed only since Release 3.0.