Working with Static Breakpoints 

Use

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

If you do not remove static breakpoints from your program, they are transported to your production system, which could cause problems.

Procedure

...

       1.      To set a static breakpoint in the ABAP Editor, go to the line where you want to interrupt the program and perform one of the following:

○       If you want the breakpoint to apply to all users, type the ABAP keyword BREAK-POINT.

The runtime processor interrupts the program execution when the breakpoint is reached.

You can number your breakpoints to make them easier to identify. For example, type in BREAK-POINT 1,BREAK-POINT 2, and so on.

○       If you want the breakpoint to apply only to a specific user, type BREAK <USERNAME>.

Although user-specific breakpoints appear in the program source code, they are not active when other users run the program. The program execution stops only when the specified user runs it.

       2.      To remove a static breakpoint, go to the source code and delete the keyword.

Static breakpoints apply to all users, you must remove them from the program once you have finished testing it

Example

The following report demonstrates the use of a user-independent and a user-specific breakpoint.

REPORT  break_point.
IF sy-subrc <> 0.
  BREAK-POINT.
ELSE.
  BREAK SMITH.
ENDIF.