Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 2 of 5

Tools: ABAP development tools and friends

10 min

Listen to this lesson

0:00 / 18:35

For two decades ABAP developers lived in SAP GUI transactions such as SE80, SE38 and SE24. Those still exist in classic systems, but they are no longer where modern ABAP is written. SAP describes ABAP development tools for Eclipse (ADT) as the integrated development environment for all standard ABAP development, quality assurance and supportability tasks in ABAP Cloud. CDS, RAP behavior definitions and service bindings can only be edited there. In the cloud products there is no SAP GUI access for developers at all.

  1. InstallEclipse plus the ADT plug-ins from SAP’s development tools site
  2. ConnectCreate an ABAP project for CMD (or an ABAP Cloud project for a BTP or Public Edition system)
  3. FindProject Explorer, ABAP repository trees, Open ABAP Development Object
  4. Edit and activateSource editors with code completion, quick fixes and syntax check
  5. Check and testRun ABAP Unit and ATC from the editor; results appear in their own views
  6. ReleaseAssign changes to a transport request and release it
A developer’s day in ADT, from setup to release.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-101

What you work with in ADT

An ABAP project is your connection to one system and client, for example CMD client 100 for Kenji's team. Inside it, the Project Explorer shows packages and objects, and the Released Objects tree lists what SAP has released for ABAP Cloud development. The Properties view shows an object's ABAP language version and, under API State, whether it is released and under which release contract. Views such as ABAP Unit, ATC Problems, Transport Organizer and the debugger complete the picture.

One ABAP project connects ADT to one system and client; from there, a handful of views answer what an object is, what it may use and whether it is ready.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-101
Editor or viewWhat it is forClassic SAP GUI equivalent
Class editorGlobal classes, local test classes, behavior poolsSE24 (for classic classes)
CDS data definition editorCDS view entities, projections, access controlsNone: CDS is ADT only
Behavior definition editorRAP behavior (create, update, validations)None: RAP is ADT only
Service binding editorPublish an OData service and open a previewNone for RAP services
ATC Problems and ABAP Unit viewsStatic check findings and unit test resultsATC and SE80 test runs
Transport Organizer viewRequests and tasks for your changesSE09 / SE10

Core ADT editors and views for a new ABAP developer or technical tester.

Visual Studio Code and other tools

SAP made ABAP development tools for Visual Studio Code generally available in May 2026. The first release targets ABAP Cloud and RAP (CDS, behavior definitions, classes, service bindings, the debugger, ABAP Unit, ATC and transports), and later versions added classic object types such as programs and function modules. It connects to the SAP BTP ABAP environment and to SAP S/4HANA systems on release 2025 or higher. SAP still recommends Eclipse for full-featured work until the VS Code tools reach parity, so check SAP's tools overview before you standardize a team on one IDE. For key users, SAP provides browser-based key user tools (custom fields, custom logic, form adaptations) that need no IDE. Administrators use Fiori apps for identity and access, communication management and technical monitoring.

PersonaPrimary toolWhat they build or check
Developer (Kenji)ADT in Eclipse (or VS Code where supported)Classes, CDS, RAP, unit tests, ATC fixes
Key user (Maria)Key user apps in the Fiori launchpadCustom fields and small logic adaptations
Administrator (Sam)Fiori admin apps and SAP GUI in Private EditionUsers, communication, monitoring, transports
Technical tester (Priya’s team)ADT views and SAP Cloud ALMReads unit test and ATC results as evidence
Each persona gets its own tool set.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-101

A short word on the debugger and runtime errors. ADT includes the ABAP debugger and access to runtime error analysis, so when a unit test fails with an exception you can set a breakpoint by double-clicking the ruler next to a line, rerun the test and step through. Testers do not need to debug, but they benefit from knowing that a short dump in CMQ has a named error and a call stack that a developer can open in ADT. Attaching that information to a defect saves a round trip.

A failing unit test, a breakpoint and a rerun: the debugger lives in the same IDE as the code and the tests.
The Sign-Off Table · thesignofftable.com/academy/sap-abp-101

What would you do?

A new developer on Kenji's team cannot find the CDS view behind a Fiori app in SE80 and asks whether CDS is broken in CMD. What should Kenji tell them?

Key points
  • ADT in Eclipse is SAP’s IDE for modern ABAP; CDS and RAP can only be edited there.
  • An ABAP project connects ADT to one system and client.
  • Properties shows an object’s language version and API state.
  • ADT for VS Code has been generally available since May 2026; Eclipse remains the full-featured option.
  • Key users and administrators have their own browser-based tools.

Check your understanding · not graded

Lesson check

  1. 1. Where do you edit a RAP behavior definition?

  2. 2. In ADT, where do you see whether an SAP object is released and under which contract?

  3. 3. What does an ABAP project in ADT represent?

  4. 4. Which three items should a tester see before a custom-code change moves to CMQ?