2. BREAK-POINT f.
The BREAK-POINT statement interrupts the
processing and diverts the system to debugging mode. You can then
display the contents of all the fields at runtime and also control the
subsequent program flow.
If the system is unable to branch to debugging for some reason (due to
a background job or update), it generates a system log message.
After the BREAK-POINT , the system automatically
performs any restart in the database, if no COMMIT WORK was
executed. Since debugging sometimes switches off COMMIT WORK ,
you should not place a BREAK-POINT statement in a SELECT
In the editor, you can also set a breakpoint dynamically without
making any changes to the ABAP/4 program. These dynamic
breakpoints are valid only for the current user in the current session.
EffectBehaves like variation 1, except that the field contents of
f remain in the event of any system log messages.
© SAP AG 1996