v0.1.0 now public on GitHub · GPL-3.0 · Open source
An AI ABAP developer agent backed by 47 Claude Code skills — turns design specs into deployed, ATC-clean ABAP, driving SAP GUI and live RFC validation from one conversation.
47 skills · 1 ABAP agent · 3 plugins · ECC + S/4HANA
Three commands inside Claude Code — no signup, no setup wizard.
# 1. Add the marketplace
/plugin marketplace add https://github.com/sapdev-ai/sap-dev
# 2. Install the core plugin
/plugin install sap-dev-core@sap-dev
# 3. Login + bootstrap
/sap-login → /sap-dev-init
Optional add-ons:
/plugin install sap-gen-code@sap-dev — spec → ABAP pipeline /plugin install sap-tcd@sap-dev — BP / MM01 / VA01 automation Six pain points every team recognises
SE11 → SE38 → SE37 → SE16N for every fix. Context switching kills focus and steals hours per day.
Manual TR creation, mis-assignment, and the dreaded "object locked" error after a typo.
Excel and PDF specs are hand-translated to ABAP. Field length, type, and key flags drift on every revision.
Naming, type, SQL field, and FM-argument issues found at review. Each round costs half a day.
"Save before check, then activate." Hidden rules live only in senior heads. New hires take weeks to ramp up.
Every project rewrites GUI scripts that nobody maintains. No reuse, no standards, no tests.
A real spec, parsed → generated → checked → deployed — all driven by natural language.
AI-orchestrated ABAP development on top of SAP GUI Scripting + RFC
Excel / PDF specs become DDIC objects, programs, FMs, classes, RFC wrappers, and ABAP Unit scaffolds.
Naming, types, SQL fields, FM args, ATC quality gate — all checked against the live SAP system.
SE01 / SE11 / SE16N / SE37 / SE38 / SE24 / SE91 / CMOD / SNRO / MM01 / BP / VA01 driven by natural language.
New
A senior ABAP developer that reads your Customer Brief on every run
The abap-developer agent is your end-to-end SAP delivery partner. It reads your Customer Brief, sets MODE flags (modern ABAP, OOP, unit tests, performance band, authorisation strictness), and orchestrates the right skills for the job — never bypasses ATC, never deploys without confirmation.
"Build a program from this Excel spec." Reads brief, validates DDIC, generates ABAP, runs ATC, deploys.
"Fix Z<PROG>." Opens the program, runs syntax + naming + type checks, patches, re-activates.
"Deploy this .abap file." Resolves TR, deploys DDIC dependencies first, activates, gates on ATC.
# abap-developer agent
name: abap-developer
modes:
- BUILD # spec → deployed code
- FIX # repair existing object
- DEPLOY # push .abap with TR + ATC
reads: customer_brief.md
sets: MODE_OOP
MODE_UNIT_TESTS
MODE_PERF_BAND_HIGH
MODE_AUTHZ_STRICT
guards: never bypasses ATC
always asks before deploy3 plugins · 47 skills · 1 agent · production-tested
34 skills + 1 agent · The foundation
10 skills · Spec → ABAP
3 skills · Business transactions
Each capability shaped by an actual SAP delivery pain — not a toy demo
Single TR resolution entry-point. Three policies: DEFAULT, ASK, CREATE_NEW.
ATC / Code Inspector quality gate. Severity threshold blocks risky deploys.
One-shot bootstrap, sub-second health check, conservative reverse-dependency cleanup.
When a script gets stuck, captures every visible window so the AI can see and recover.
"Who uses this?" check plus SAP spool download — usage analysis end-to-end.
Number Range Object lifecycle: create, maintain, intervals — TR popups handled.
Live RFC fetch of FM interfaces kills the most common AI hallucination class.
One-page project profile applied across every skill, with MODE flags for the agent.
Customer Brief, spec template, and parser rules ship in EN and JA out of the box.
Works under EN / JA / DE / ZH SAP logon. Identifies controls by ID + DDIC, never translated text.
Every skill emits start/step/stop. Run-id propagation across PS1 + VBS. Audit-ready.
Plain Markdown + VBS + PowerShell. Read it, fork it, replace anything. No lock-in.
Customer Brief
Every SAP shop runs differently — namespace, packages, message class, naming rules, quality bar, performance gates, authorisation handling. The Customer Brief captures all of it in one Markdown file. The abap-developer agent reads it on every run; every skill respects it; every generated artefact follows it. No more "the senior dev does it differently" — your standards become the engine.
Want help authoring yours? That is exactly what onboarding is for.
# customer_brief.md
project: HK-Manufacturing
abap_release: 7.57
namespace: ZHK
packages:
- ZHK_MM
- ZHK_SD
message_class: ZHK
naming_overrides:
custom_url: \\share\sap-dev\hk\
quality_bar:
atc_max_priority: 2
unit_test_min: 80%Pilot programme
We are running a heavily-discounted pilot programme to build production case studies
Every engagement is a quotation — these are the shapes most projects take
1 week, 1 add-on, before/after metrics. Heavily discounted for early reference customers.
Author your project profile, install the toolkit, train your team. 2-3 weeks.
Your MM02 has 6 custom screens. Your BP has unique role logic. We extend the toolkit.
1-2 day workshops. Hands-on with your real codebase, not generic demos.
For teams who deploy to production. SLA-backed help when things break.
Every engagement is by quotation. Tell us about your project →
Yes. The toolkit is GPL-3.0 open source on GitHub. We earn money helping you deploy, customise, and operate it.
Encrypted with Windows DPAPI on the developer's machine. They never leave your network. The Claude API call is the only outbound traffic.
Yes. We detect Unicode vs non-Unicode and convert CJK source via ADODB so uploads never garble.
Yes — custom screens are exactly what custom skills are for. We extend the toolkit per customer landscape.
Everything runs on your developer workstation. The Claude API is the only outbound call (and you control which model and key).
So you can audit it, fork it, never be held hostage. Your operational dependency is on your team, not on us.
SAP GUI Scripting enabled (server + client). Optional: SAP NCo 3.1 for RFC features.
It reads your Customer Brief and runs in three modes: BUILD (spec → deployed code), FIX (open + repair an existing object), DEPLOY (push a .abap file with TR + DDIC + ATC handled). It always asks before deploying and never bypasses ATC findings.
Driven by paying customers' needs. Recent additions include the abap-developer agent, /sap-gui-diagnose, and per-system FM-signature caching. Next sprints add deeper SD/MM coverage.
No. sapdev.ai uses your developer's own SAP Dialog license through the standard GUI Scripting and RFC interfaces — exactly the same way the developer would interact with SAP manually. The plugin is just a faster keyboard. No service accounts, no cloud-side caching, no aggregated indirect access. We recommend confirming this with your SAP licensing team before formal engagements.
Tell us about your project. We respond within one business day.
or email directly: hello@sapdev.ai