This section provides a list of exceptions that occur during RFC calls and that cannot be handled.
Exceptions That Cannot Be Handled
Runtime Error |
Cause |
CALL_BACK_ENTRY_NOT_FOUND |
The called function module is not released for RFC. |
CALL_FUNCTION_DEST_TYPE |
The destination type is not allowed. |
CALL_FUNCTION_NO_SENDER |
The function cannot be executed remotely. |
CALL_FUNCTION_DESTINATION_NO_T |
Missing communication type (I for internal
connection, 3 for ABAP) when performing an asynchronous RFC. |
CALL_FUNCTION_NO_DEST |
The specified destination does not exist. |
CALL_FUNCTION_OPTION_OVERFLOW |
Maximum length of options for the destination exceeded. |
CALL_FUNCTION_NO_LB_DEST |
The specified destination (in load distribution mode) does not exist. |
CALL_FUNCTION_NO_RECEIVER |
Data received for unknown CPI-C connection. |
CALL_FUNCTION_NOT_REMOTE |
The function module being called is not flagged as "remotely" callable. |
CALL_FUNCTION_REMOTE_ERROR |
While performing an RFC, an error occurred that has been logged in the calling system. |
CALL_FUNCTION_SIGNON_INCOMPL |
The user’s logon data is incomplete. |
CALL_FUNCTION_SIGNON_INTRUDER |
Logon attempt not allowed as internal call in a target system. |
CALL_FUNCTION_SIGNON_INVALID |
RFC from external program without valid user ID.
|
CALL_FUNCTION_SIGNON_REJECTED |
Logon attempt in target system without valid user ID. This
error codes may have any of the following meanings: |
CALL_FUNCTION_SINGLE_LOGIN_REJ |
No authorization to log on as Trusted System. The
error code may have any of the following meanings: |
CALL_FUNCTION_SYSCALL_ONLY |
RFC without valid user ID only allowed when calling a system function module. The meaning of the error codes is the same as for CALL_FUNCTION_SINGLE_LOGIN_REJ. |
CALL_FUNCTION_TABINFO |
Data error (info internal table) during a Remote Function Call. |
CALL_FUNCTION_TABLE_NO_MEMORY |
No memory available to import table. |
CALL_FUNCTION_TASK_IN_USE |
For asynchronous RFC only: The task name is already being used.
|
CALL_FUNCTION_TASK_YET_OPEN |
For asynchronous RFC only: The specified task is already open. |
CALL_FUNCTION_NO_AUTH |
No
RFC authorization. |
CALL_RPERF_SLOGIN_AUTH_ERROR |
No trusted authorization for RFC caller and trusted system. |
CALL_RPERF_SLOGIN_READ_ERROR |
No valid trusted entry for the calling system. |
● RFC_NO_AUTHORITY
|
Destination
“BACK” is not allowed in the current system. |
CALL_FUNCTION_BACK_REJECTE CALL_XMLRFC_BACK_REJECTED |
No RFC authorization for user. |
● CALL_FUNCTION_DEST_SCAN
|
Error while evaluating the RFC destination. |
CALL_FUNCTION_DEST_SCAN |
Error while evaluating the RFC destination.
|
CALL_FUNCTION_CONFLICT_TAB_TYP |
Type conflict while transferring a table. |
CALL_FUNCTION_CREATE_TABLE |
No memory available for creating a local internal table. |
CALL_FUNCTION_UC_STRUCT ● CALL_FUNCTION_DEEP_MISMATCH
|
Type conflict while transferring a structure. |
CALL_FUNCTION_WRONG_VALUE_LENG CALL_FUNCTION_PARAMETER_TYPE CALL_FUNCTION_ILLEGAL_DATA_TYP |
Invalid data type during parameter transfer. |
CALL_FUNCTION_ILLEGAL_INT_LEN CALL_FUNCTION_ILL_INT2_LENG |
Type conflict while transferring an integer. |
CALL_FUNCTION_ILL_FLOAT_FORMAT CALL_FUNCTION_ILL_FLOAT_LENG |
Type conflict while transferring a floating point number. |
CALL_FUNCTION_ILLEGAL_LEAVE |
Invalid LEAVE statement on RFC server. |
CALL_FUNCTION_OBJECT_SIZE CALL_FUNCTION_ROT_REGISTER |
Type conflict while transferring a reference. |