Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

A breakpoint pauses program execution so a developer can inspect it. Session breakpoints and external breakpoints apply to different execution contexts, such as SAP GUI work and incoming web requests.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

ABAP is SAP’s programming language for business applications. A program reads data, applies rules and produces a result. Start with the objects involved before investigating code.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for ABAP session versus external breakpoints: Why your HTTP request does not stop
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

ABAP session and external debugging for supported HTTP/RFC contexts; authorization, matching and load-distribution details require release-specific documentation.

Primary documentation reviewed on 14 November 2026 using official indexed excerpts. Documentation review only; authored examples were not compiled or executed in an SAP system.

A MANUFACTURING EXAMPLE

Debug the request used by a plant app

Follow the request context

Test A: SAP GUI dialog. Test B: Browser HTTP request. Backend user: Confirm actual identity. Breakpoint: Match execution context
What to notice: A browser request does not necessarily run in the SAP GUI session containing your session breakpoint.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Test A
SAP GUI dialog
Test B
Browser HTTP request
Backend user
Confirm actual identity
Breakpoint
Match execution context
Words you’ll meet in this guide
Program
A set of instructions executed by a computer.
Class
A reusable unit that groups data with operations called methods.
Database
Organized information kept beyond one program execution.
Internal table
A list of rows held temporarily in an ABAP program’s memory.
Key
One or more fields used to identify or find a record.
ABAP
SAP’s programming language for business applications.
RFC
Remote Function Call: a way for one system to call functions in another.
GUI
Graphical user interface. SAP GUI is a desktop interface used for many classic SAP tasks.
HTTP
The request-and-response protocol used by web applications and APIs.
CSRF
Cross-Site Request Forgery. A CSRF token helps a service reject unwanted cross-site write requests.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Request channel → Execution user → Applicable breakpoint. Conceptual diagram for ABAP session versus external breakpoints: Why your HTTP request does not stop.
Apply the idea: A developer sets a breakpoint while a manufacturer's browser application sends its order request through a different execution context.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Debug the request used by a plant app

    A developer sets a breakpoint while a manufacturer's browser application sends its order request through a different execution context.

  2. A session breakpoint does not cover a separate HTTP or RFC session

    If an ABAP breakpoint works in a SAP GUI dialog test but does not stop an HTTP request, first check the execution session.

  3. Scope and prerequisites

    This guide covers ABAP debugging concepts for SAP GUI, HTTP and RFC execution.

  4. Separate frontend identity, backend identity and session

    A browser user can authenticate through a launchpad, application router, proxy or another integration layer before ABAP runs.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.