SAP / SAP Beginner (0 to 2 yrs) Interview questions
What is the difference between a static breakpoint (BREAK-POINT statement) and a dynamic breakpoint?
A static breakpoint is the BREAK-POINT statement written directly into the ABAP source code
— it's part of the program itself, so it pauses execution for every user running that program
until a developer removes the line and re-releases the code. A dynamic breakpoint (session or external) is set
outside the source code entirely, through the editor or debugger UI, and doesn't modify the program at all.
| Static (BREAK-POINT) | Dynamic (session/external) |
| Written into the source code itself. | Set externally, without touching the code. |
| Affects every user running the program. | Typically scoped to your session (or configured users). |
| Requires a code change (and transport) to remove. | Cleared automatically when the session ends, or manually removed anytime. |
Because a forgotten BREAK-POINT statement left in production code would pause the program for
every user hitting that line, dynamic breakpoints are generally the safer, preferred choice for day-to-day
debugging, reserving static breakpoints mainly for code you're actively developing and about to remove before
release.
Who is affected by a static BREAK-POINT statement left in a program?
Why are dynamic breakpoints generally preferred for day-to-day debugging?
More Related questions...
