Build on ABAP
Before you build, check what is there. If you find something close, think about contributing to it. If you find nothing, start building.
Check what is there
Search by the use case, not by a package name: the same need often sits under a capability you would not guess. The capability map and Browse hold everything in ABAP.
What gets built on ABAP
Found something? Contribute
Where an artifact does most of what you need, a fix, a test or a page of documentation reaches everyone who already uses it. Read where it stops and its open and closed issues first: someone may have asked already. Then contribute to a project. These are the places where evidence or a second hand counts most.
Not known yet
- Let an agent change ABAP in an on-premise system
Not known yet for ADT MCP Server, 6 of 7 artifacts cover it
- Work on ABAP with an agent and no system connection
Not known yet for sapskills, 5 of 7 artifacts cover it
One artifact stands
- Agent evalsDanKromp/skillOverflow
- Analytic modellingbw-modeling-mcp
- Async processingABAP-PRC
- Code metricsabap-metrics
- Data modellingcdsanalyser
- Data privacyDST
- Database connectorsSAP HANA
- DebuggingSmart Debugger
- Encryption and signinghhelibeb/blowfish-abap
- Error handlingABAP-PRC
- Event MeshMQBA
- ExtensibilityZABAP_SAP_ENHANCEMENTS
- Feature togglesFeaturetoggle
- Finding a transaction codesapgui
- Fiori annotationsrap-ext
- Generatorsabap2UI5 Layout Editor
- Input validationabapDomCheck
- Key-user adaptationonurakca/SAPUI5-Adaptation-Project-Downloader
- Launchpad pluginsgenerator-ui5-ts-flp-plugin
- Loading a warehousebw-modeling-mcp
- Model visualisationSAP2Moose
- OpenAPIABAP OpenAPI UI
- Parallel processingABAPParallelizationService
- Retrieval-augmented generationSAP AI Core
- Telemetryadmin-cockpit
Nothing there? Build
Use cases no recorded artifact covers, and capabilities with no artifact in ABAP. Unmapped means the atlas holds nothing, not that nothing exists: search once more, then build an abapgit project.
Use cases nothing covers
Every assessed use case in ABAP has an artifact that covers it.
Capabilities with no artifact
Read in the atlas
- Patterns for using LLMs in ABAP developmentPatterns for using LLMs in ABAP developmentLars Hvam compares eight ABAP development setups: assistance in SE80 or Eclipse, virtual files and MCP over ADT, a centrally managed MCP service, sandboxes, local Git, Git with read-only system context, and temporary ABAP systems for development and CI. The overview describes where source changes, review and system access happen, including abapGit synchronization and abaplint checks. It is dated March 2026; its risk, cost and autonomy ratings are the writer’s assessments.