AI agents working with SAP ABAP have always hit the wall - they can do whatever the ADT interface allows, and nothing more. Need to create a view, a transaction, or an IMG customizing entry? ADT has no endpoint for it, so the agent stops and you do it by hand.
Fluid API in Abapsmith removes that wall. When the agent lacks a tool, it creates one inside your SAP system, uses it right away, and moves on.
What it looks like in practice
You ask: "Create a BAdI spot for our pricing enhancement in package ZDEMO."
The agent creates a small utility class in the S4 system in local package, and call this new tool to create a BAdI spot.
Why it matters
- Fewer dead ends. Work that used to need manual steps in SAP GUI (views, search helps, transport entries, IMG settings, Floorplan Manager configuration, authorization traces) can now be done by the agent.
- A clean system. Nothing is pre-installed. Small helper classes are deployed only when a task needs them. They live in one dedicated local package, $ABAPSMITH_FLUID_API, so they are easy to find and never end up in a transport.
- Controlled by design. Every action is classified as read, change or execute. Changing actions state which object, package and transport they touch, and Abapsmith checks that before anything runs.
- Extensible. Missing something that isn't built in? Your agent can write a plugin for it using skill. The plugin then works like any built-in tool and goes through the same safety checks.
What's included today
| Things ADT has no write endpoint for: views, transactions, search helps, indexes, packages, transport entries, transports of copies. Also reads transport logs and import queues. |
| Table rows, function module interfaces, SAP documentation, change documents and enqueue locks. Can also call any function module ( |
| Enhancement spots, BAdI definitions, filters and implementations. |
| IMG customizing: preview the rows, create the request, write the change. |
| Floorplan Manager configuration: find an app, read its outline, resolve it, list its events. |
| Classic screens: fields, flow logic and function codes. |
| Authorization trace: status, switch on and off, read the result, SU53. |
| Application log (SLG1) messages. |
| Run a classic report and capture its output. |
| Search source text across a package or a set of objects. |
| Self-test of the runtime. |
Summary
The agent is no longer limited to what the ADT API offers. If a tool is missing, it builds one inside SAP, safely and on demand.
Want to know more? Please check the project itself, it is open-source: https://github.com/Freight-Art/abapsmith
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.