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
- Get RAP patterns that match the target system
Not known yet for abap-skills, 3 of 4 artifacts cover it
- Work on ABAP with an agent and no system connection
Not known yet for sapskills, 4 of 6 artifacts cover it
One artifact stands
- Agent evalsDanKromp/skillOverflow
- Analytic modellingbw-modeling-mcp
- Async processingABAP-PRC
- Transport managementSAP Cloud Transport Management
- Clean code conventionscode pal for ABAP — Cloud Edition
- Configurationabap-dynamic-assignment
- Data modellingSAP Table to CDS Mapper
- Database connectorsSAP HANA
- Error handlingABAP-PRC
- Extensibilityabap-point-gate
- Fiori annotationsrap-ext
- Generatorsabap2UI5 Layout Editor
- HTTP clientscross-http-client
- Launchpad pluginsgenerator-ui5-ts-flp-plugin
- Loading a warehousebw-modeling-mcp
- NotificationsABAP-PRC
- Retrieval-augmented generationSAP AI Core
- RFC connectivityCloud Connector
- Searching code in a systemABAP Code Search
- Serve your application over MCPabap-agent-runtime
- 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.