Breakpoints 
Setting and editing breakpoints, too, in the new Debugger is almost identical to the classic Debugger. However, several breakpoints can be set simultaneously in the new Debugger if you choose the path Breakpoint ® Create Breakpoint. Afterwards, the system displays a window in which the following options are available.
Here it is obvious that, in contrast to the classic Debugger, all the input fields – with the exception of those in the ABAP Command tab – have a search help function (function key F4). For example, under the Method tab you enter a certain class. Then, in the search help, all the methods that belong to this class are proposed.
There are also certain differences when setting and deleting breakpoints. A double-click within a source code line creates a breakpoint in this line in both Debugger types, provided the cursor was not positioned on an ABAP keyword. A second double-click in the same line deletes this breakpoint in the classic Debugger, while it is only deactivated in the new Debugger.
Remember: The classic Debugger makes a distinction
between saved breakpoints and breakpoints that are not saved. Breakpoints can be saved by setting a
breakpoint in the Editor or by triggering the Save function.
The saved breakpoints apply
for the current logon session and are seen by all external modes that belong
to the current user session.
Non-saved breakpoints arise when you set a breakpoint in the classic Debugger and then do not save it. In the classic Debugger, breakpoints that are not saved apply only to the current roll area. They no longer exist, for example, after execution of the statements SUBMIT or CALL TRANSACTION.
The new Debugger makes no difference between saved and non-saved breakpoints. All the breakpoints in the new Debugger are valid for the entire Debugger session. Saved breakpoints – that is, breakpoints that were saved in the Editor, for example – are adopted only at the beginning of the debugging session. Note that saved breakpoints cannot be changed by the new Debugger.