ABAP Runtime Errors

CALL_FUNCTION_NOT_REMOTE SAP ABAP Runtime Error call function not remote







CALL_FUNCTION_NOT_REMOTE 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: F - Installation Errors

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_NOT_REMOTE ABAP Runtime Error

If function module "<runtime parameter>" is one of your own, release it in the function library for RFC calls by setting it so that it can be called remotely. Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

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

Parameter........: <runtime parameter>, <runtime parameter>, <runtime parameter>
Other parameters: <runtime parameter>, <runtime parameter> Function module "<runtime parameter>" cannot be used for 'remote' calls. Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to call function module "<runtime parameter>" via RFC, but this function module has not been released for 'remote' calls.

For the following call types, a module must be released for 'remote' calls:

a) Call Function '<runtime parameter>' Destination ....
b) Call Function '<runtime parameter>' In Background Task ...
c) Call Function '<runtime parameter>' Starting New Task ...

For further information, see SAP Note 725951. Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.

It has been flagged as capable of being called remotely however. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.