The new developer toolchain

Two years ago, "AI for ABAP" meant pasting code into a chat window and hoping. In 2026 SAP ships a real toolchain. Some of it lives inside the IDE, some runs side by side on SAP's cloud, and some is an open protocol that lets coding agents from other vendors work on ABAP systems. This lesson maps the pieces so the rest of the track has a shared vocabulary. Everything here was checked against SAP's own pages on 17 October 2026, and anything that is only planned is labeled that way.

The pieces, one sentence each

• SAP Joule for Developers, ABAP AI capabilities: SAP's AI assistance inside ABAP Development Tools (ADT). It includes Joule chat, documentation chat, predictive code completion, Explain, ABAP Unit and CDS test generation, CDS annotation generation, the OData UI Service from Scratch wizard and RAP business logic prediction. Since June 2026 it runs as a side-by-side service on SAP's cloud, licensed in AI Units; the free promotion ended on 30 September 2026, so it has needed AI Units since 1 October 2026.
• SAP-ABAP-1: SAP's first ABAP-specialized foundation model. SAP's product page says the first release focuses on code explanation, and that the same specialized AI powers SAP Joule for Consultants and SAP Joule for Developers.
• ABAP Development Tools for Eclipse: the established ABAP IDE. SAP says it remains the recommended IDE for full-featured ABAP work until the VS Code extension reaches parity.
• ABAP Development Tools for VS Code: SAP's official VS Code extension, published on the VS Code Marketplace on 1 June 2026. Version 1.1 (July 2026) added classic object types such as programs, function groups, tables and structures, and version 1.2 appeared on 16 October 2026.
• ADT MCP server: a local server, shipped inside ADT for Eclipse and ADT for VS Code, that exposes ABAP development tasks as tools a coding agent can call: search, read, create, activate, run ABAP Unit, run ATC, work with transports.
• SAP's MCP servers for CAP, UI5, Fiori and MDK: open-source servers SAP publishes on GitHub for side-by-side development. SAP News announced them at SAP TechEd 2025 as working with Claude Code, Cursor, Cline, Windsurf and OpenAI Codex.
• Coding agents: tools such as GitHub Copilot, Amazon Q or Anthropic's Claude Code that plan a task, call tools and edit code in a loop. SAP's own ABAP documentation names GitHub Copilot as the primary tested agent.

How the pieces fit

The key design choice is the ABAP language server. SAP rebuilt the client side of ADT so that one Java-based core serves both Eclipse and VS Code. SAP's FAQ for the VS Code extension explains that this is why the extension supports the same backend releases as Eclipse, and why the MCP server offers the same tools in both IDEs. The MCP server runs in that shared core.

So a coding agent working on ABAP has a clear path: it talks to the MCP server on your machine, which uses your existing IDE logon to reach the ABAP system. For AI-heavy actions, such as AI-based ATC quick fixes or the documentation search, the MCP server calls the Joule for Developers service, which consumes AI Units. Many tools, such as activation or running ABAP Unit, need no AI tokens at all.

What is GA, what is planned

The other direction: ABAP calling AI

Everything above is about AI helping developers write ABAP. There is a second, separate direction: ABAP applications that call a language model at runtime, for example to summarize a long service note. SAP's tool for that is the ABAP AI SDK powered by Intelligent Scenario Lifecycle Management, which reaches models through the generative AI hub in SAP AI Core. SAP's availability page lists it for the ABAP environment, Public Edition, Private Edition and SAP S/4HANA. It is a product feature you build and test like any other, with its own costs and data questions, and it is out of scope for this track's developer-tooling courses. Keep the two directions apart in conversations with security and procurement: "we use AI to write code" and "our code uses AI" need different approvals.