Static Breakpoints 

You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.

Setting Breakpoints

To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the statement in the line at which you want to interrupt the program.

REPORT RSDEBUG1.
...
IF SY-SUBRC <> 0.
BREAK-POINT.
ENDIF.
...

When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 …)

Static breakpoints are not normally user-specific. The program is interrupted regardless of the user who executes it.

However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program.

Deleting Breakpoints

Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In extensive programs, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.

If you do not remove static breakpoints from your program, they will be transported into your production system. This could cause serious problems in the production system.