ABAP Runtime Errors

CALL_FUNCTION_ILLEGAL_LEAVE SAP ABAP Runtime Error call function illegal leave







CALL_FUNCTION_ILLEGAL_LEAVE 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_ILLEGAL_LEAVE ABAP Runtime Error

None of the above-mentioned LEAVE variants should normally be used in an RFC-compatible function module, as they cause a serious RFC error that is hard to track down.
To find out where exactly the LEAVE is called up, it is now possible to trigger an ABAP runtime error with parameter rfc/option_list. This can be usd to find out where the LEAVE statement is used.

Check the source code for the function module you have called with RFC. If a Leave transaction is executed there, modify the source code accordingly. Error: <runtime parameter> Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

One of the following actions was carried out on the RFC server:

Leave to transaction Space
Leave to transaction ...
Leave to last mode

and the client- or server instance was configured in such a way that an ABAP runtime error should be triggered. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Leave to transaction Space
Leave to transaction ...
Leave to last mode

and the client or server instance were configured in such a way that a RABAX should be triggered.