ABAP Development Tools For Visual Studio Code Is N...

Introduction

On behalf of the ABAP development tools team, I am pleased to announce that the first version of the ADT for VS Code extension is available on the VS Code marketplace! Go ahead, install the extension and use it against any ABAP system that supports the ABAP development tools for Eclipse today.

How to install and use the extension?

Simple.

1. Install VS Code: https://code.visualstudio.com/

2. Open the extension page on the VS Code marketplace and click the Install button: extension page

3. Refer to the official getting started guide for guidance on how to set up your ABAP system connection. If you are already using ADT for Eclipse no ABAP system changes are needed. Otherwise, use our admin guide to configure the system for client access.

How can I use the built-in MCP server?

The extension comes with a first version of the ADT MCP server. For security reasons, the server is disabled by default. It needs to be enabled via the extension settings by checking the checkbox (see screenshot). Once enabled, the server will start automatically. The documentation how to configure the MCP server can be found here.

Regardless the chat agent solution you use, we recommend defining ABAP related rules via a custom AGENTS.md file. Our documentation provides a template which you can use as a starting point.

What can you expect?

The first version represents roughly 11 months of core development time. The main focus was on designing and implementing the foundational architecture for the extension and the feature scope for RAP UI service development. Developers primarily working on RAP UI services can now develop the frontend and backend parts of their SAP Fiori/SAPUI5 app in the same tool. The extension also includes development support from AI agents such as Microsoft Copilot. This was one of the most requested features from the ABAP developer community.

In short, how useful the extension is for you will depend on your most common ABAP-related development tasks. A list of key features can be found here.

What comes next?

With most of the foundational work done, the focus is now on adding missing features.

Here are some planned highlights for the next release:

Support for RFC logon via password
Support of more core development object types: RAP behavior extensions, DDIC tables, DDIC structures, DDIC enqueue objects, DDIC type groups, CDS entity buffers, programs/includes, function groups and modules, …
MCP tools: Universal diff tool for transports, ABAP test cockpit tools, …

Follow the ABAP Cloud Roadmap if you are interested in knowing what comes next.

Provide feedback and influence our product backlog!

We welcome your feedback! Feel free to use the comment section to let us know which features you are missing the most. Your input will help us prioritize the feature backlog for the next releases.

Still some questions left?

Take a look at FAQ document.

Source link