rdisp/wpdbug_max_no is a SAP Parameter attribute which is used to control Max. number of work processes in SAP debug mode information. This is available within R/3 SAP systems depending on the version and release level.
Below is the standard documentation available and a few details of the attributes values .
There are two different debugging modes.
In the first case there is no detach of the ABAP sessions between two
debugger actions. This avoids implicit DB commits. This mode is also
called "SAP Debug Mode".
In the second case, the debuggee session is detached normally after a
debugger action. Implicit DB commits (which would not be executed as
part of a normal execution) are created this way. This can cause changes
to the database. This mode is called "Normal Debug Mode".
The whole number of possible dialog process in SAP Debug Mode depends on
whether you are in the productive client or not:
If you try to start a work process in SAP Debug Mode on the productive
client then an error message is returned when the number of available
SAP Debug Modes exceeds rdisp/wp_no_dia / 2. It is therefore only
possible to debug on the productive client in SAP Debug Mode. (=> No
inconsistency on the database in the productive client)
SAP Debug Mode is used in the other clients when the number of processes
to be debugged is lower than rdisp/wpdbug_max_no. Otherwise the process
to be debugged is started in the normal debug mode.
The default value of the parameter is 'default'. In this case the
parameter is set on half of the dialog work processes.
See SAP Parameter Documentation for full SAP documentation for this profile parameter.