RPERF_TOO_MANY_CALLS SAP ABAP Runtime Error rperf too many calls

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

RPERF_TOO_MANY_CALLS ABAP Runtime Error

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.

Too many recursive subroutine calls Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

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

An ABAP subroutine has been called recursively too many times. This is probably due to a conversion exit or a user exit triggering the same exit again and again. These exits are implemented by function modules with the names CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or USER_EXIT_xxxxx_INPUT.
You can find out which ABAP routine is affected by consulting "Active Calls/Events". Conversion exits are triggered during screen field transports or WRITE statements. Field exits are triggered during field transports from the screen to the ABAP program, meaning that they are not called directly by an ABAP program. The most likely scenario here is the implementation of a conversion exit containing a WRITE statement for a field that the same conversion exit is assigned to in its Dictionary domain. As a result, the exit is triggered recursively.

A maximum of <runtime parameter> of these ABAP subroutine calls can be made. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.