ABAP Runtime Errors

RAISE_EVENT_NESTING_LIMIT SAP ABAP Runtime Error raise event nesting limit







RAISE_EVENT_NESTING_LIMIT 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.


RAISE_EVENT_NESTING_LIMIT ABAP Runtime Error

General notes on error correction: Please see program correction for more details about the possible cause of this runtime error and how it could be avoided.

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.

The current recursion depth was <runtime parameter>,
The maximum allowed is <runtime parameter>. RAISE EVENT statements nested too deeply. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

The maximum RAISE EVENT recursion depth (<runtime parameter>) has been exceeded.

If there is a further RAISE EVENT statement during processing of a RAISE EVENT statement - in a handler method called by RAISE EVENT - this is known as RAISE EVENT nesting. If both RAISE EVENT statements are in the same triggering object, a recursion arises for the handler method call. This often results in endless recursions. This is what has happened here.

Nested/recursive RAISE EVENT statements have complicated runtime behaviour and can easily result in endless recursions.
Constructs of this kind should be avoided if possible. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.