0045 - Creating Activatable Breakpoints

Moderators: Snowy, thx4allthefish, Rich, ilya

Post Reply
Posts: 7116
Joined: Thu Oct 31, 2002 4:47 pm
Location: Liverpool

0045 - Creating Activatable Breakpoints

Post by Rich » Sat Mar 28, 2009 8:51 am

Creating Activatable Breakpoints and Assertions.

You can now create (de)activable breakpoints in your programs. You can release these breakpoints in production and a customer will have the opportunity to activate and debug your code more easily.
The following is an activable break-point : BREAK-POINT ID dany.

The checkpoint group is defined by double clicking on the checkpoint group in the editor OR directly via transaction SAAB.

Below is the SAAB screen. In the breakpoints part of the screen, you can set it to "inactive" or "break". All breakpoint groups will be shipped inactive by default.



An assertion is a condition which must be true during program execution. By using asserts in your program, you can find cause of error in shorter time. The reaction when violating an assertion depend on a customizing and could be :
  1. Start the debugger from this assert
  2. Do nothing, ignore the assert
  3. Log the assertion in a log
  4. Terminate the program with runtime error ASSERTION_FAILED
The assertions are defined in SAAB (exactly like the breakpoints, see screen above).Here is an example of a use for an assertion :

Code: Select all

METHOD sort_by_name.
DATA: l_f1 TYPE i VALUE 2,
      l_f2 TYPE c LENGTH 10 VALUE 'test',
      l_t1 TYPE TABLE OF sflight.
   ASSERT ID        dany
          SUBKEY    'danysub1'
          FIELDS    l_f1 l_f2 l_t1
          CONDITION itab->is_sorted_by_name( ) <> ' '.                

This will ensure that the table is sorted. Below is the result of the log for this assert


(Courtesy Dany Charbonneau)


Abap KC:http://www.richard-harper.me.uk/Kb

Post Reply