ABAP Developmentintermediate

Session vs External Breakpoints

When to use each, and how to debug update tasks.

Explanation

Session breakpoints affect only your GUI session — the standard for interactive debugging. External breakpoints (based on user or terminal ID) catch RFC/OData/HTTP calls originating outside your session. Update-task debugging requires enabling 'Update Debugging' via /h and completing the dialog step; then the debugger opens in the V1 work process.

Code example

ABAP Code

BREAK-POINT ID 'ZDEBUG_ORDERS'." Toggled via SAAB (Checkpoint Groups)

Real project scenario

An RFC-triggered enhancement mysteriously did nothing. Setting an external breakpoint on the target user quickly showed a filter mismatch.

Common mistakes

Forgetting to enable Update Debugging before COMMIT WORK; leaving external breakpoints and blocking others' sessions.

Best practices

Use checkpoint groups (SAAB) for reusable diagnostic breakpoints; remove external breakpoints when done.

Interview angle

How do you debug a background job that already ran?