CALL_FUNCTION_NO_LB_DEST SAP ABAP Runtime Error call function no lb dest

CALL_FUNCTION_NO_LB_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: I - Internal Kernel 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_NO_LB_DEST ABAP Runtime Error

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.

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 internal error for more details about the possible cause of this runtime error and how it could be avoided.

Please see rfc 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. This destination has been interpreted syntactically as a 'load balancing' destination.
The syntax for this type of destination is as follows: Normal case: A_B[C] where A = name of the messager server, hs0311 for example B = system name, BIN for example
C = group, PUBLIC for example
(if C is left empty, it is interpreted as PUBLIC)

Special destination: NONE[C] is interpreted as a local 'load balancing' destination (C = group, PUBLIC for example, see the explanation above).

You can use transaction SM59 to display all RFC destinations in the system and to create new ones. Please see rfc internal error for more details about the possible cause of this runtime error and how it could be avoided.

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