Appearance
AI-Driven ABAP (RAP)
When the backend must run on the ABAP digital core, the AI-Driven Development Model uses the ABAP RESTful Application Programming Model (RAP) — developed AI-driven through ARC-1, which connects the AI agent to the ABAP system.
When to choose RAP over CAP
Use RAP when extending SAP S/4HANA / ABAP Cloud directly, or when tight integration with the ABAP digital core outweighs the cloud-native flexibility of Domain-Driven CAP.
ARC-1 — the AI-to-ABAP bridge
ARC-1 (ABAP Relay Connector) is an open-source MCP server by Marian Zeis that lets AI assistants interact with SAP ABAP systems through ADT (ABAP Development Tools). It is the bridge that makes the same spec-driven, agent-assisted flow used on the CAP side possible for ABAP: the AI agent (Claude Code, Copilot, or other MCP clients) reads and writes RAP artifacts via ARC-1's standardized ADT access.
- Central deployment — runs on company servers, Docker, or SAP BTP rather than only on developer laptops.
- Secure by default — read-only mode, SQL blocking, and package restrictions out of the box; operation allow/deny lists and safety profiles for granular control.
- Separate auth layers — client-to-server access control distinct from server-to-SAP identity, with per-user identity via Principal Propagation for audit trails.
- BTP integration — XSUAA, Destination Service, Cloud Connector, and audit logging.
- Multi-client — supports Claude, GitHub Copilot, and IDE clients.
Tools
ARC-1 exposes 12 intent-based tools (full reference) that the agent uses to drive ADT:
| Tool | Group | Purpose |
|---|---|---|
SAPRead | Read | Read ABAP source, method bodies, grep matches, table data, CDS views, access controls, KTD docs |
SAPSearch | Read | Object search + full-text source search across the system |
SAPContext | Read | Dependencies, reverse lookups, CDS impact analysis |
SAPWrite | Write | Create/update/delete source & metadata with auto lock/unlock; class-section surgery, RAP scaffolding |
SAPActivate | Write | Activate objects (single/batch); publish/unpublish OData service bindings |
SAPNavigate | Dev | Go-to-definition, find references, code completion |
SAPLint | Dev | System-aware linting, auto-fix, server-side formatting |
SAPDiagnose | Dev | Syntax check, unit tests, ATC checks, quickfixes, profiler traces |
SAPQuery | Data | Run ABAP SQL with table suggestions and auto-chunking of large IN (...) lists |
SAPTransport | Process | CTS transport create/release/delete/history |
SAPGit | Process | gCTS / abapGit workflows with safety gating |
SAPManage | Process | Feature probing, cache stats, package lifecycle, FLP helpers |
Community tool
ARC-1 is a community project. SAP has announced an official ABAP MCP server (planned Q2 2026) that may eventually supersede it — track this before committing long-term.
ABAP Development Tools for VS Code
While ARC-1 gives the AI agent programmatic ADT access, the developer gets first-class ABAP tooling in the same IDE via ABAP Development Tools for VS Code — SAP's official ADT extension, published to the VS Code Marketplace as SAPSE.adt-vscode.
- ABAP Cloud in VS Code — create, edit, debug, and manage ABAP artifacts directly in VS Code for the ABAP Cloud development model, without Eclipse.
- RAP UI services first — the initial scope centers on RAP UI service development, so the frontend and backend of a Fiori/UI5 app can be built in one tool.
- AI-native — designed for AI agent support (e.g. GitHub Copilot) inside the editor — the same VS Code where Claude Code and ARC-1 run.
One IDE, two ABAP paths
The developer uses ADT for VS Code for hands-on ABAP work; the AI agent uses ARC-1 (MCP) for automated, spec-driven generation — both in the same VS Code instance against the same ABAP system.
Early version
ADT for VS Code is an evolving first release — its feature scope still trails the mature Eclipse-based ADT. Check current coverage before relying on it for a given RAP artifact type.
References: Marketplace · SAP Help · Announcement (SAP Community)
RAP building blocks
- Domain model — CDS in ABAP (data definitions).
- Behavior — Behavior Definitions & Implementations.
- Service — Service Definition + Service Binding exposing OData v4.
Consuming from the frontend
Like CAP, RAP exposes OData v4, so the React frontend consumes it through the same typed data-access layer — no frontend changes depend on the backend programming model.
See also the RAP programming model reference.