Everything in ABAP
Type: 3
Domain
Origin
Signals
More
Group by: Capability
Distributed through
Generates
Run with
Generates ABAP client classes and server stubs from OpenAPI
Generator of ABAP type definitions from JSON structures
Generates singleton ABAP cache classes from a macro call
No published releases; repository quiet for 26 months.
Modelling layer of ABAP Cloud above database tables
Nothing to choose here and nothing to install: it is what an ABAP Cloud system gives you. It shares a name and a lineage with CAP's CDS but is a different language in a different runtime, and a model does not move between them.
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
Claude Code plugin adding Custom_* tools to arc-1
Not for S/4HANA Public Cloud or [the BTP ABAP environment](artifact:btp-abap-environment), where the README states there is no `SUBMIT`, NAST or SOAP-RFC; the floor elsewhere is SAP_BASIS 7.50, the `/sap/bc/soap/rfc` service active, and an SAP user with `S_RFC` on the kit's function group as well as the authorizations for the reports and the spool. Print output is NAST messages only, so S/4 Output Management through BRF+ or APOC is outside it, and editing covers SmartForms alone, with Adobe Forms and SAPscript previewable but not editable. A report that opens a popup, calls a screen or is a dialog transaction cannot be run at all.
Collection of 41 agent skills, 37 for SAP development tasks
Agent skill for off-stack ABAP Unit tests and an abaplint gate
Not a substitute for testing in a system: the README states that any class calling the database, classic BAPIs or HTTP is shimmed out and stays an on-stack ATC and ABAP Unit concern, and that an off-stack green is CI-grade provenance rather than an in-system pass. It also assumes a particular shape of project. The ABAP has to be abapGit-serialised into a Git repository, Node.js 22 or later has to be available locally and in CI, and the CI has to be GitHub Actions.
Seventeen agent skills for ABAP development
Twenty-two agent skills shipped with arc-1
Every skill that touches ABAP needs [arc-1](artifact:arc-mcp-arc-1) itself connected to a real system; nothing else is universal. `modernize-ui5-app` and `convert-ui5-to-fiori-elements` specifically need [the UI5 MCP server](artifact:ui5-mcp-server) for TypeScript conversion guidance and the linter, `convert-ui5-to-fiori-elements` also needs [the Fiori MCP server](artifact:sap-ux-fiori-mcp-server) for its LROP scaffold, and `modernize-ui5-app` needs a browser MCP (Claude in Chrome or Claude's own Preview) for its final render-verification step, since an HTTP 200 alone does not catch a blank page. A skill file alone, without the servers a given skill needs, has nothing to act on.
Five ABAP workflows for Claude Code on existing MCP servers
Claude Code plugins with Clean ABAP rules and templates
Knowledge with no reach: without an MCP server connected it can tell an agent what to write and cannot let it read or run anything. The rules target the ABAP Cloud development model, so a classic on-premise codebase is not what they are written against.
Claude Code plugin adding Custom_* tools to arc-1
Not for S/4HANA Public Cloud or [the BTP ABAP environment](artifact:btp-abap-environment), where the README states there is no `SUBMIT`, NAST or SOAP-RFC; the floor elsewhere is SAP_BASIS 7.50, the `/sap/bc/soap/rfc` service active, and an SAP user with `S_RFC` on the kit's function group as well as the authorizations for the reports and the spool. Print output is NAST messages only, so S/4 Output Management through BRF+ or APOC is outside it, and editing covers SmartForms alone, with Adobe Forms and SAPscript previewable but not editable. A report that opens a popup, calls a screen or is a dialog transaction cannot be run at all.
Collection of 41 agent skills, 37 for SAP development tasks
RAP skills delivered branch-per-target for each deployment
Neither the package manifest nor the repository tree declares a licence.
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Runbook skills for Basis operations at the OS and database layer
The commands it writes stop production systems, delete data and import transports, which is why execution is deliberately somebody else's decision. BTP and cloud operations are explicitly out of scope and planned as a separate plugin.
Agents and skills that drive sapcli instead of ADT
Neither the package manifest nor the repository tree declares a licence.
Agent skills for Clean ABAP, ADT in VS Code and guardrails
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
Claude Code plugin with an ABAP MCP server and write guards
It is a plugin for one server — its own — so it is a stack rather than a component. And the guard is only as good as the profile labels: a production system registered as `DEV` is a production system with the safety off.
SAP reuse library for calling large language models from ABAP
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
Claude Code plugin with an ABAP MCP server and write guards
It is a plugin for one server — its own — so it is a stack rather than a component. And the guard is only as good as the profile labels: a production system registered as `DEV` is a production system with the safety off.
Debugger script generating a VALUE statement for a variable
No published releases; repository quiet for 57 months.
ABAP transaction generating an MVC-style project from a template
No published releases; repository quiet for 48 months.
Easy-UI5 generator for a TypeScript Fiori launchpad plugin
Visual designer generating ABAP code for classic SAP GUI screens
No published releases; repository quiet for 93 months.
Generates local classes from FORM-based ABAP programs
No published releases; repository quiet for 67 months.
HTTP endpoint under /sap/bc/adt exposing ABAP development objects
A client that cannot reach the adt ICF service over HTTP has nothing to call.