One atlas across
SAP development ecosystems.
Find and compare tools, libraries and services from SAP and the community through a connected graph and a semantic map of ecosystems and capabilities. Every entry links to its sources, its crawled readings and the posts, talks and samples that explain it, so you can see where SAP's own answer ends and what others have built around it.
What the atlas is →161 capabilities1,312 artifacts1,116 content2,440 people
Find what fits. Compare artifacts.
Start with an ecosystem or capability
Follow the graph from a capability or task to the artifacts that serve it. Compare what they cover, their limitations, and dated evidence from their documentation and repositories.
Articles
The atlas is now in betaonedevatlas is open for browsing. Find tools for SAP development, compare their documented capabilities, ask your AI assistant, and join a flight during TechEd week.Building onedevatlasBuilding onedevatlas: the idea, the back-and-forth with AI, the wrong turns, and an orb who lost his permanent spot in the atlas.
2 topics, 2 editions, 2 of them current
What an entry carries
Who is present
SAP ships the answer101
Both are present157
Only the community25
Nobody credible yet8
Crawled and written, kept apart
- What it does and what it solves
- The capabilities it provides, what it requires and what it connects to
- Activity, releases and compatibility
- When not to use it, and what to consider
- Its README, release notes and weekly downloads
- And more on every artifact's page
Written for a version, read against now
- What the piece covers
- The capabilities and artifacts it explains
- The version it was written for
- What changed in those since it was published
- Its author, and the series it belongs to
Something you may not have seen
Retrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt.SAP and communityui5-tcode-finderA browser page that searches SAP transaction codes by code, title or description and hands one over on a click: copied plain, copied with an /n or /o prefix, or opened in SAP GUI for HTML.no release dataA 25x faster mta.yaml build for SAP CAP Node.js projectsOne change to the build descriptor, arrived at after discarding the obvious alternatives — the author reports trying shell scripts, npm caching and offline installs, swapping npm for pnpm, and cds build --no-clean, all of which helped and none of which was this.
Prompt managementKeeping the prompts an application sends to a model as templates with placeholders, stored and versioned apart from the code that calls them, so a change of wording is not a deployment.SAP onlycapire/incidents-appThe Incident Management reference application — the one SAP's own tutorial paths build, step by step, and the model cds add incidents-sample drops into a project.no release dataIntegrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPA concrete regulatory deadline rather than a demo topic: every Polish invoice has to pass through KSeF, the national e-invoice platform, and this proposes the route — S/4HANA business events onto Event Mesh, a CAP application consuming them and talking to KSeF.
Agent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server.SAP and community@cap-js/cds-testTest support for CAP Node.js, installed as a dev dependency: it starts the project's server for the test, hands the test an HTTP client bound to it, and carries the assertions.3 months since releaseExtend SAP SuccessFactors on SAP BTP with CAP - Deploy to SAP HANA CloudThe deployment instalment of the author's SuccessFactors extension series — the project already exists and the imported service is already modelled, so this is only the move onto HANA Cloud.
AccessibilityMaking a UI usable with a screen reader, with a keyboard alone and without seeing the layout: accessible names on controls, a heading order, landmarks, focus handling and announcements.SAP and communitypyrfc-mcpAn MCP server for calling an SAP system's RFC-enabled function modules from an agent, built so that discovering a function does not authorise calling it: a read or a write is denied unless t…no release dataDynamic OData from "any" API through SAP BTP KymaPutting an OData face on a third-party API by way of Kyma, so the SAP side of a landscape can consume something that was never built for it.
Server-side renderingRendering a UI on the server before it reaches the browser — first paint without waiting for a client framework to boot, and markup a crawler can read.Community onlySAP-samples/abap-cheat-sheetsA collection of ABAP syntax cheat sheets, from internal tables to RAP's Entity Manipulation Language, each backed by an executable demo class you import into an ABAP system with abapGit.no release data[Blog Post] SAP Event Mesh – CAP based implementation of SAP Event Mesh in a Single-Tenant ScenarioThe instalment of the Deep Dive series where the framework arrives.
Vulnerability scanningFinding known vulnerabilities in the open-source components an application depends on, in the project's dependency tree before it is deployed and in the application once it runs, and following each one until it is fixed.SAP onlyui5-middleware-livereloadA dev-server middleware that adds live reload to the UI5 dev server, reloading the page when the sources in the app's webapp folder change.3 months since releaseSAP BDC in Business AI Platform: Contextualize and ReasonA Devtoberfest 2026 session (DAT-31) that places SAP Business Data Cloud as the contextualise-and-reason pillar of the SAP Business AI Platform, between the build pillar of Joule Studio and Integration Suite and the govern pillar of AI Agent Hub.
Who builds it
New in the atlas
Lessons from Building an SAP RAP Application with AI and SAP MCP Servers: An Experiment entered the atlasSurviving and Thriving with the SAP Cloud Application Programming Model: Types & Tools entered the atlasUsing the TCP Protocol for Node.js Cloud Applications entered the atlasConnecting UI5 TypeScript Components locally entered the atlasEmbracing TypeScript in SAPUI5 Development entered the atlas
Machines are a first-class audience
An agent arrives two ways: configured on purpose, or having simply fetched a URL. Both are served. Every page is complete without JavaScript, and there is a static file beside each one.
Static JSON beside every page
A prebuilt file per entry and one for the whole graph. No protocol to speak, no rate limit, CDN cached.
llms.txt at the root
A plain-text map of the atlas, generated from the same graph. The only thing that helps a fetcher which configured nothing.
MCP over HTTP
The tools that match, compare and check, over streamable HTTP. Stateless: a request is answered from the bundled graph and nothing of it is kept.