Lesson 1 of 5
ADT for VS Code
9 min
Listen to this lesson
For fourteen years, ABAP development outside SAP GUI meant ABAP Development Tools for Eclipse. On 1 June 2026 SAP published ABAP Development Tools for VS Code on the Visual Studio Code Marketplace. SAP's FAQ explains why: in surveys from 2023 and 2025, VS Code was the most-requested IDE in the ABAP community. It also explains what the extension is not: it isn't a replacement for Eclipse, and Eclipse remains the recommended IDE for full-featured ABAP work until VS Code catches up.
Versions so far
- 1 Jun 2026Version 1.0First release on the Marketplace; RAP UI service development; RFC only with SNC and single sign-on; ADT MCP server included
- Jun 2026Patch 1.0.1RFC logon with user and password
- Jul 2026Version 1.1Classic ABAP: programs, includes, function groups and modules, tables, structures, type groups, lock objects; MCP tools for ATC and transport diffs
- Jul to Aug 20261.1.1 and 1.1.2Patch releases
- 16 Oct 2026Version 1.2MCP read and edit file tools, MCP access restrictions, Transport Organizer, ATC exemptions, SQL Notebook, ABAP Feeds and more
How it works
The extension is a thin layer over the ABAP language server, a Java-based component that contains the same client code that powers ADT for Eclipse. SAP compares it with the VS Code Java extension, which is essentially Eclipse JDT running as a language server. Three consequences follow, all from SAP's FAQ: Eclipse and VS Code stay in sync, every backend release Eclipse supports also works in VS Code, and new object types arrive faster because two generic rendering engines (forms and source) cover them.
Because ABAP lives on the server, the extension uses a virtual file system: each object appears as a file in your workspace, using the ABAP file format, but nothing is saved to your local disk. SAP calls this the only viable approach for ABAP and points out the benefit for AI tools: everything is file based and diff friendly, which is how coding agents expect to work.
Install and connect
- Install VS Code, then install ABAP Development Tools for VS Code (publisher SAP SE) from the Marketplace. It is free, under the SAP Developer License Agreement.
- Open the Command Palette and run ABAP: New Destination.
- Choose RFC for on-premise and SAP S/4HANA Cloud Private Edition systems, or HTTP for the ABAP environment and SAP S/4HANA Cloud Public Edition.
- Complete the destination details. Version 1.2 also lets you connect to a user-specified system without SAP Logon.
- Add what you work on to the Explorer with ABAP: Add Package as Folder to Workspace or ABAP: Add Destination as Folder to Workspace. Use Log on to Destination (added in 1.1) to log on from the keyboard.
If you already use ADT for Eclipse against a system, SAP says no backend changes are needed. Otherwise, follow SAP's admin guide to configure the system for ADT client access. On the backend side, SAP's FAQ says the extension supports on-premise systems down to SAP NetWeaver 7.3 EHP1 SP04.
Your first hour
- Install the extension and create one destination to the development system (for Contoso, CMD client 100).
- Add one package as a workspace folder rather than the whole destination; large trees are slow to browse and hard to read.
- Open a class you know well, change a comment, activate it, and run its ABAP Unit tests from the editor to confirm the round trip.
- Open the ABAP Timeline view on that class (version 1.2) to see its version history.
- Run ATC on the class and look at the result; then decide whether you are ready to try the MCP server.
Save the workspace as a file once it works. SAP's own product lead suggests VS Code workspaces as a way to keep a favorite list of packages and destinations, and a saved workspace makes it easy to share the same layout across a team.
What you get in the editor
| Area | Available in VS Code (1.2) | Still Eclipse or SAP GUI |
|---|---|---|
| Objects | Classes, interfaces, programs, function groups, DDIC tables and structures, CDS, RAP, service bindings, message classes, BAdI implementations | Dynpro and Web Dynpro UI programming; SAP GUI integration is not planned |
| Quality | ABAP Unit, ATC runs and exemptions, ABAP Feeds, ABAP Timeline | Some Eclipse quick fixes (users asked for them in Community threads) |
| Debugging | Breakpoints, stepping, variables, call stack, multiple servers | Check your system: Community users reported on-premise debugging gaps in July 2026 |
| Transports | Search, create, assign; Transport Organizer view with release (1.2) | Advanced transport tools in SE09/SE10 and Cloud ALM |
| AI | ADT MCP server; predictive code completion | Custom code migration agent (Eclipse only for now) |
Scope moves every release; confirm against SAP's "Supported Object Types" page before you plan work in VS Code.
What would you do?
Contoso wants three developers to try ADT for VS Code against CMD, the Private Edition development system. Sam (Basis) asks what backend work is needed. The developers already use ADT for Eclipse against CMD. What's the accurate answer?
- ADT for VS Code reached the Marketplace on 1 June 2026; version 1.2 followed on 16 October 2026.
- It runs on the same ABAP language server as Eclipse, so it supports the same backends.
- RFC for on-premise and Private Edition; HTTP for the ABAP environment and Public Edition.
- Objects live in a virtual file system, which suits file-based AI tools.
- Eclipse stays the recommended IDE for full-featured work; dynpro and SAP GUI integration aren't in VS Code.
Check your understanding · not graded
Lesson check
1. Which connection type does ADT for VS Code use for SAP S/4HANA Cloud Private Edition?
2. Why does ADT for VS Code use a virtual file system?
3. What did patch 1.0.1 of ADT for VS Code add?
4. Which UI programming models does SAP say are out of scope for ADT for VS Code?