CALL_FUNCTION_NOT_FOUND SAP ABAP Runtime Error call function not found

CALL_FUNCTION_NOT_FOUND 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_NOT_FOUND ABAP Runtime Error

Check the most recent transports to the SAP System.
Is a change currently being made to program <runtime parameter>? If the module is an enqueue/dequeue module:
Has the lock object not been activated in the Data Dictionary? Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Function modules with names similar to "<runtime parameter>":: <runtime parameter>RFORM EXIT_SHOW_TFDIR Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Function module "<runtime parameter>" not found. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to execute the CALL FUNCTION statement in program <runtime parameter>. The name of the function module to be called is "<runtime parameter>".

No function module can be found named "<runtime parameter>" however. All function modules are listed in the Function Library (SE37).

Possible causes:
a) Wrong name specified. Pay particular attention to upper/lower case and to underscores ("_").
or
b) Transport error
c) If the module is an enqueue/dequeue module, the lock object might not have been activated (Data Dictionary). An attempt was made to call function module "<runtime parameter>".
This cannot be found in the library though. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.