CALL_FUNCTION_NO_DEST 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.
The function module call was
CALL FUNCTION .... DESTINATION <runtime parameter>.
Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.
RFC destination <runtime parameter> does not exist.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.
Destination <runtime parameter> for a Remote Function Call is not known in the system.
You can use transaction SM59 to display all RFC destinations in the
system and to create new ones.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_FUNCTION_NO_DEST - call function no dest CALL_FUNCTION_NO_AUTH - call function no auth CALL_FUNCTION_NOT_REMOTE - call function not remote CALL_FUNCTION_NOT_FOUND - call function not found CALL_FUNCTION_NOT_ACTIVE - call function not active CALL_FUNCTION_LZ_WRONG_LENGTH - call function lz wrong length