onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewABAP, RAP and ABAP Cloud

New in ABAP

7 days30 days90 daysAll time
In the last 30 days
12releases373added to the atlas192revisions
Change
Kind: 3
Origin
Domain
Clear all
577 changes
DayCapability
Kind ArtifactsKind PeopleKind Capabilities

Today
59 changes
Cloud ALM Link for ADTadded to the atlasEclipse plugin linking ABAP transports to SAP Cloud ALM featuresIDE extension,
SAP TCode Runneradded to the atlasVS Code sidebar that opens SAP transactions through WebGUIIDE extension,
ZASISadded to the atlasRegex RuleSets that read barcode strings into named fieldsPackage,
ABAP Cloud readinesscore coverage revisedReassessed against the graph (check:capabilities): the state changed, so the block now says what the added providers do, as kinds with the defining ones linked.Capability,
Show 55 more
Agent access to your codecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something.Capability,
Agent evalscore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): albertmink-agentic-abap-evals, an independent set of ABAP tasks and a grader for coding agents, was entered after the block was written; the count is dropped and the second kind named. State unchanged.Capability,
Agent guidancecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field.Capability,
Attachmentscoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): drops a count-like contrast with a plugin the flavor does not have.Capability,
Authenticationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no community artifact on the UI5 door provides this capability by an edge; the middlewares the text named provide ui5-build-tooling, and the only sample on the door is not a presence. what_core_does stays, so the core remains present.Capability,
Authorizationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed every provider behind the door is an SAP service, a statement about the corpus that goes stale, and did not name the fresh btp-oauth provider. Coverage state unchanged: only SAP-official services count behind this door.Capability,
Browsing table datacore coverage revisedReassessed against the graph (check:capabilities): the note described the providers as SAP GUI programs only, and browser apps, an IDE extension and a desktop editor have arrived; the state stays core-and-community.Capability,
Calling a service by handcore coverage revisedReassessed against the graph (check:capabilities): abap-odata-test arrived after the block was assessed and changes the kinds of community answer; the state stays core-and-community.Capability,
Certificate managementcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the note was an absence claim about providers; the new SAP provider btp-custom-domain is sap-official, so core-only still holds.Capability,
Change promotioncore coverage, id, ecosystems, name revisedPublic feedback issue #9. The ABAP name is kept in framing_by_ecosystem.abap; the default name and description now state the cross-door concern.Capability,
Change trackingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): removed a count, and linked the entry the graph holds instead of its repository.Capability,
Clean code conventionscore coverage revisedReassessed against the graph (check:capabilities): FORMfactor, an independent ABAP generator, provides this capability, so the community is present on the door.Capability,
Code formattingcore coverage revisedReassessed against the graph (check:capabilities): the abap2UI5 playground provides this capability and the text never named it; ABAP FS named for the kind of VS Code integration.Capability,
Code reviewcore coverage revisedReassessed against the graph (check:capabilities): providers that arrived after the 2026-09-13 assessment (abapTimeMachine, abapOpenReview, a transport review app) shape the answer; state unchanged, core-and-community.Capability,
Configurationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): config-management arrived as a provider after the block was last looked at; the state stays core-and-community.Capability,
Data modellingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): independent ABAP providers (CDS Analyser, CDS field mapping, acds) now provide this capability on the ABAP door.Capability,
Database connectorscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note counted one entry behind the door; it now names the driver and SAP HANA, which now provides the capability on this door. State unchanged.Capability,
Debuggingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): seven ABAP providers newer than the block were never named. State stays core-and-community.Capability,
Document outputcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the service is a provider on this door and the text named it without the link. Wording otherwise unchanged; the state stays core-only.Capability,
Documentationcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): absence claims about providers go stale as providers arrive. The flavor states are unchanged.Capability,
Driving the SAP GUIcore coverage revisedReassessed against the graph (check:capabilities): removed the count and the popularity wording, and named the kinds, including batch input (jrgkraus-tool-bi) and SAP's sample, which the text never named.Capability,
Editor supportcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the providers behind the UI5 door are SAP's (UI5 Language Assistant, and SAP Build Code and SAP Web IDE Full-Stack, which serve ui5). The community SAPUI5 Extension is an entry in the graph but has no provides edge to this capability.Capability,
Error handlingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): brandeis-consulting-abap-prc arrived after the block was last looked at, and the block named no community kinds.Capability,
Event Meshcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note made a claim about every provider and named none, and the SAP services that arrived since the block was assessed (Advanced Event Mesh, the Integration Suite event broker, Cloud Application Event Hub) shape the answer. The state stays core-only, since every provider counting for the door is sap-official.Capability,
Extensibilitycore coverage revisedReassessed against the graph (check:capabilities): a provider of a second kind, a discovery report for existing enhancement points, arrived after the block was last assessed and the text never named it. State unchanged (core-and-community).Capability,
Finding a transaction codecore coverage revisedReassessed against the graph (check:capabilities): sapgui arrived as a second kind, one that reads the system's own menu, and the prose counted entries.Capability,
Generatorscore coverage, coverage by ecosystem, framing by ecosystem revisedReassessed against the graph (check:capabilities): the atlas holds these entries, so the links point at them and not at their repositories (docs/WRITING.md section 4).Capability,
HTTP clientscore coverage revisedReassessed against the graph (check:capabilities): two providers added since 2026-09-14 that the text never named; the singular "one client interface" also read as a count.Capability,
IDE provisioningcore coverage revisedReassessed against the graph (check:capabilities): eclipsadt-o-mat arrived after the last look and the text never named it; state unchanged.Capability,
Importing and exporting table datacore coverage revisedReassessed against the graph (check:capabilities): the count of sample repositories goes stale as providers arrive, and the ABAP backend importer and the Excel add-in change the shape of the answer, so the note names those kinds. The ABAP state stays core-and-community.Capability,
Input validationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact carries a provides edge to this capability for the UI5 door, because openui5-validator provides ui5-data-binding. The state follows the edges, and the core stays present through the block's sourced what_core_does.Capability,
Knowing the maintenance status of a releasecore coverage, coverage by ecosystem revisedui5-task-check-eocp, from public feedback issue #6, is the first independent provider on the UI5 door, beside SAP's SAPUI5 version overview.Capability,
Launchpad pluginscore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed an absence claim and a count of providers (WRITING §3); the flavor states are unchanged.Capability,
LLM integrationcoverage by ecosystem, core coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note claimed who provides the capability behind this flavor, which moves with the corpus. The flavor state is unchanged.Capability,
Loading a warehousecore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): ERPL is a provider the text never named, and it loads from ABAP systems outside BW routines. State unchanged.Capability,
Local developmentcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted providers and claimed an absence about who has built something, which goes stale as providers arrive.Capability,
Localizationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): providers arrived after the block was last looked at, an XLIFF editor and an MCP server among them, and the text named none of the kinds.Capability,
Loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the state is now community-only and the block needed to say what the community adds.Capability,
Maintaining table entriescore coverage revisedReassessed against the graph (check:capabilities): open-abap-open-table-maintenance, a community-org package served from an HTTP handler for one table named in its code, was not named; the browser editor is now linked. State unchanged.Capability,
Model visualisationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): abapGraph and abap-search-tools-ui arrived after the ABAP block was last looked at and the text never named them. No state changed.Capability,
Notificationscore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed every provider is independent, a statement about who has built something; it now names the kinds, including the process framework that mails about failed objects.Capability,
ODatacoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note counted the repositories and named none of the kinds that arrived since the block was assessed; it now names the kinds and links the ones that define them. State unchanged.Capability,
Retrieval-augmented generationcoverage by ecosystem, core coverage revisedReassessed against the graph (check:capabilities): a CAP-door provider reaches Document Grounding through the LangChain vector store interface, a shape the two plugins do not cover.Capability,
RFC connectivitycore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): erpl-node-rfc, pyrfc-mcp, rfc-connector and Cloud Connector reached this door after the block was written and change its shape from callee only to callee and caller.Capability,
Searchcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the only independent provider behind the ABAP door is ZC8A_001, an artifact of type sample, which is not a presence; the core stays because what_core_does is sourced.Capability,
Searching code in a systemcore coverage revisedReassessed against the graph (check:capabilities): the note named no kind of provider, and five providers newer than the 2026-09-14 assessment shape the answer. State unchanged.Capability,
Seed datacore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact provides seed-data for the UI5 door; the two tools the sentence named provide ui5-testing. The core stays present on the sourced what_core_does. The tools stay on the graph under ui5-testing.Capability,
Serialisationcore coverage revisedReassessed against the graph (check:capabilities): abap-architect, an ide-extension that provides this capability, was not named; ajson linked as the defining parser.Capability,
Serve your application over MCPcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted providers, and sap-security-mcp no longer provides this capability. The unmapped state is unchanged.Capability,
Source controlcore coverage revisedReassessed against the graph (check:capabilities): providers added since 2026-08-31 change the kinds the community adds beyond the in-system git client; the state stays core-and-community.Capability,
Static analysiscore coverage revisedReassessed against the graph (check:capabilities): the block named none of the providers that arrived after 2026-08-31. State unchanged, core-and-community still matches the providers.Capability,
Telemetrycoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removes a universal claim about the providers that goes stale as they arrive.Capability,
Tool governancedescription, core coverage, coverage by ecosystem, framing by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): a count of providers removed.Capability,
UI written in ABAPcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the claim that abap2UI5 is the sole provider, which went stale as providers arrived.Capability,
Unit testingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted the artifacts and said they were in staging; both are in the graph now and are named.Capability,
Yesterday
2 changes
ABAP Syntax Highlightingadded to the atlasVS Code syntax highlighting for .abap filesIDE extension,
Agent access to your codecoverage by ecosystem revisedRewritten at the maintainer's request (2026-10-25): what SAP ships named whole, and what the community adds written from what its ABAP MCP servers state about how they run, connect and sign in.Capability,
Sat 24
25 changes
Ajiemar Santiagoadded to the atlasPerson,
Alex S.added to the atlasPerson,
Alexander Tsybulskyadded to the atlasPerson,
Björn Schulzadded to the atlasPerson,
Show 21 more
dimi309added to the atlasPerson,
erlerbadded to the atlasPerson,
florianstephan01added to the atlasPerson,
Gabbianiiiiadded to the atlasPerson,
Glen Simpsonadded to the atlasPerson,
HaasFrankMartinadded to the atlasPerson,
Hieunx12added to the atlasPerson,
Jessie Cheahadded to the atlasPerson,
KDS042added to the atlasPerson,
Kirill Gorinadded to the atlasPerson,
Leon Sternadded to the atlasPerson,
MNicolai77added to the atlasPerson,
monty79added to the atlasPerson,
Ogulcan Kusluogluadded to the atlasPerson,
reichr-devadded to the atlasPerson,
Sebastian Machhausenadded to the atlasPerson,
seidorvtadded to the atlasPerson,
techedgegroup-sapadded to the atlasPerson,
Theodore Tsirpanisadded to the atlasPerson,
Tobias Leichadded to the atlasPerson,
Tolgonai Muratbekovaadded to the atlasPerson,
Fri 23
1 change
EPOD ADT MCP Serveradded to the atlasMCP server for ABAP on the ADT session, in Eclipse or standaloneMCP server,
Thu 22
15 changes
B-Tocs ABAP SDKadded to the atlasWeb service client and connector layer for calling out of ABAPPackage,
Klystronadded to the atlasMCP server in ABAP inside the application server, with agent skillsMCP server,
pyapi4abapadded to the atlasTemplate pairing a FastAPI service with ABAP reports that call itSample,
Skybuffer AI MCP serveradded to the atlasABAP add-on serving business data and transactions as MCP toolsMCP server,
Show 11 more
fgalastriadded to the atlasPerson,
IBM Watson APIsadded to the atlasPerson,
romankorimadded to the atlasPerson,
SAP Russiaadded to the atlasPerson,
SAP2Mooseadded to the atlasPerson,
Srijan Sarmahadded to the atlasPerson,
tf-Franz-Seidladded to the atlasPerson,
tmhewadded to the atlasPerson,
Uwe Kunathadded to the atlasPerson,
Vladimir Lutsasadded to the atlasPerson,
@mcp-abap-adt/corereleased 20.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
Wed 21
2 changes
abap-ai/mcp2added to the atlasStateless ABAP MCP server SDK for the 2026-07-28 protocol draftMCP server,
@mcp-abap-adt/corereleased 19.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
Tue 20
104 changes
4Artemy4added to the atlasPerson,
Abapinhoadded to the atlasPerson,
abapToolsadded to the atlasPerson,
abhijeetjangamadded to the atlasPerson,
Show 100 more
agraeberadded to the atlasPerson,
Alexadded to the atlasPerson,
Alexandr Zhuravlevadded to the atlasPerson,
Alexey Arsenyevadded to the atlasPerson,
Alistair Tudoradded to the atlasPerson,
alokm3hta-staradded to the atlasPerson,
Alwin van de Putadded to the atlasPerson,
apm.toadded to the atlasPerson,
AppKnightadded to the atlasPerson,
Arthur Silvaadded to the atlasPerson,
Artsemiadded to the atlasPerson,
AWS for SAPadded to the atlasPerson,
B-Tocs.org Communityadded to the atlasPerson,
BenBenBenNetzadded to the atlasPerson,
Benjamin Weisheitadded to the atlasPerson,
Bjørn Espen Raadimadded to the atlasPerson,
Björn Panteradded to the atlasPerson,
BlueFundaadded to the atlasPerson,
bryanmcainadded to the atlasPerson,
BTC Business Technology Consulting AGadded to the atlasPerson,
BTCAGadded to the atlasPerson,
Bunyanuch Saengnetadded to the atlasPerson,
Chairat Onyaem (Par)added to the atlasPerson,
Christoph Clausadded to the atlasPerson,
Codexadded to the atlasPerson,
corelineadded to the atlasPerson,
Daniel Huseradded to the atlasPerson,
DigitalBizWhizadded to the atlasPerson,
Divya Balakrishnaadded to the atlasPerson,
Edwin Vleeshouwersadded to the atlasPerson,
Endress+Hauser InfoServe GmbH+Co. KGadded to the atlasPerson,
Erik Heuschmannadded to the atlasPerson,
Florian Wallburgadded to the atlasPerson,
franzreitmayeradded to the atlasPerson,
Freight Artadded to the atlasPerson,
frozenraindropadded to the atlasPerson,
fschmidt-waremaadded to the atlasPerson,
GaudinUlkoradded to the atlasPerson,
GuidoJageradded to the atlasPerson,
Hiroshi Yoshiokaadded to the atlasPerson,
International Business Machinesadded to the atlasPerson,
Iván Rodrigoadded to the atlasPerson,
Jharna - MSadded to the atlasPerson,
JharnaAgrawaladded to the atlasPerson,
Jochen Röhrigadded to the atlasPerson,
Julian Büttneradded to the atlasPerson,
Kamil Kováčadded to the atlasPerson,
Krishna Chandra Dashadded to the atlasPerson,
LeTyskeradded to the atlasPerson,
Lukas Leistenadded to the atlasPerson,
lukas-klausneradded to the atlasPerson,
Marcadded to the atlasPerson,
Mark Saksadded to the atlasPerson,
Markus Malenkeadded to the atlasPerson,
mattiastrradded to the atlasPerson,
MDJoergadded to the atlasPerson,
Michael Biberadded to the atlasPerson,
Microsoft GitHub Useradded to the atlasPerson,
Mishaëladded to the atlasPerson,
mprevathiadded to the atlasPerson,
Naveen-Kurmadasadded to the atlasPerson,
NaveenKurmadasadded to the atlasPerson,
NitinKumar Guptaadded to the atlasPerson,
OlegBash599added to the atlasPerson,
Onur Akçaadded to the atlasPerson,
orhangoektas-sapadded to the atlasPerson,
os-neffadded to the atlasPerson,
Peter Langneradded to the atlasPerson,
Peter Reinbothadded to the atlasPerson,
Phani Puttabakulaadded to the atlasPerson,
ppm230590added to the atlasPerson,
prasanth23590added to the atlasPerson,
Praveen Kumar Reddy Chintaadded to the atlasPerson,
PShumilovadded to the atlasPerson,
raketenstart-abapadded to the atlasPerson,
RegGitHubadded to the atlasPerson,
Reto Fischeradded to the atlasPerson,
revathimp25added to the atlasPerson,
rmezrivadded to the atlasPerson,
roman-doubravaadded to the atlasPerson,
Sanju Kumariadded to the atlasPerson,
Seretis Kleanthisadded to the atlasPerson,
Simon Mülleradded to the atlasPerson,
Simone Gaffuriniadded to the atlasPerson,
sm-DataZooadded to the atlasPerson,
smithmariusadded to the atlasPerson,
Stefan Wixfortadded to the atlasPerson,
StoneRangeradded to the atlasPerson,
szelbiadded to the atlasPerson,
Tarak Mandaladded to the atlasPerson,
TestiTestmann91added to the atlasPerson,
thfiedleradded to the atlasPerson,
Tilo Körneradded to the atlasPerson,
Tobias Meyeradded to the atlasPerson,
TranRedadded to the atlasPerson,
Valaradded to the atlasPerson,
Vikas Bansaladded to the atlasPerson,
xamafeadded to the atlasPerson,
yalcingurleksapadded to the atlasPerson,
Zoltan Bothadded to the atlasPerson,
Mon 19
17 changes
ABAP Call Hierarchyadded to the atlasEclipse plugin showing the call hierarchy of ABAP membersIDE extension,
ABAP Code Searchadded to the atlasEclipse plugin searching ABAP sources from the search dialogIDE extension,
ABAP Search and Analysis Toolsadded to the atlasEclipse plugin for ABAP object search and CDS view analysisIDE extension,
ABAP Tagsadded to the atlasEclipse plugin for tagging ABAP repository objectsIDE extension,
Show 13 more
agentic-abap-evalsadded to the atlasABAP navigation tasks and a grader for coding agentsCLI,
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruptionSample,
ABAP Select Converterflavors, description, links revisedThe flavor rests on the page's own "It is primarily used to migrate existing code to ABAP Cloud."; nothing on either page places the tool in standard ABAP. The page's "Additional infos" link was read for the first time and is now links.docs: it states the beta and lists what the converter supports and does not, which replaces the earlier "nothing for a batch of statements", a limit read off what the form does not show. The my-ide-actions sentence now follows that repository's own words, "The basis is the SwH tool" and the security table's "SELECT Converter | Software-Heroes API | -> Full SELECT Statement", and calls it an IDE Action rather than a package, which is the type that entry carries.Web tool,
Authenticationecosystems revisedui5-middleware-oidc was staged in intake-20261019-bestofui5 under ui5-build-tooling because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
CDS Field Mappingdescription revisedSAP's Cloudification Repository is in the graph, so the README's source is named by its entry rather than by a URL none of this entry's sources gave. The README's sentence is "Source will be the Cloudification Repository, where the mapping old table to new Core Data Services is listed.", so the prose reports it as what the README names and not as how the mapping file is produced today: the file in the repository comes from an extractor class you copy and run in your own system. The CAST, CASE and ABS gap is attributed to the tool's page, which is where that sentence stands, rather than to the README.Web tool,
Cloudification Repository Viewerflavors revisedThe documentation's Introduction places what the viewer shows in one flavor: "The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer." Neither page states a standard ABAP use, so that flavor is left unstated.Web tool,
Editor supportecosystems revisedUI5 Language Assistant, SAP's VS Code extension for UI5 XML views and manifest.json, and the SAPUI5 Extension by iljapostnovs were staged in intake-20261019-bestofui5 with this concern as their best fit, and the capability was not open on the UI5 door. The UI5 reading comes from the UI5 Language Assistant README.Capability,
Input validationecosystems revisedopenui5-validator was staged in intake-20261019-bestofui5 under ui5-data-binding because this capability was not open on the UI5 door. The UI5 reading comes from the OpenUI5 pages on data types and validation messages.Capability,
Loggingecosystems revisedSRBJSLogger and openui5-error-collector were staged in intake-20261019-bestofui5 with no capability edge, because this capability was not open on the UI5 door. The UI5 reading comes from the sap/base/Log API documentation and the OpenUI5 Logging and Tracing page.Capability,
secondsky/sap-skillstype properties, flavors revisedRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.Skill,
Seed dataecosystems revisedvscode-ui5-odata-mock-generator and openui5-smart-mockserver were staged in intake-20261019-bestofui5 under ui5-testing; the first one's drafter noted that seed-data fit better but was not open on the UI5 door. The UI5 reading comes from the OpenUI5 mock server pages and SAP's ui5-middleware-fe-mockserver README.Capability,
Werkbankprovides revisedWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.Desktop app,
XLF Translatorflavors, type properties revisedThe flavor rests on the page's "The tool is mainly used to translate ABAP Cloud Content, which is generated using the 'Maintain Translation' app (XLIFF Version 1.2)." The web-tool block's uploads key carries the one sentence the page gives about the file leaving the machine, "After uploading, all fields that have a translation element are available for translation.", verbatim; access is left out because neither the page nor the site's FAQ says what it takes to use the tool. The prose no longer says the file is opened in the browser, which the word "uploading" does not support, no longer treats XLIFF 1.2 as what the tool accepts (the page states the version of the ABAP Cloud content it is mainly used for), and attributes "without installing an additional tool" to the maker. when_not_to_use was "One file per session, translated by hand, field by field", none of which the page states.Web tool,
Sun 18
4 changes
abapsmithadded to the atlasABAP MCP server over ADT with a local journal that can undo writesMCP server,
Modernization Agents for SAP on AWSadded to the atlasAWS agents for ABAP, PI/PO and BW modernisation workApp,
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missionsMCP server,
SAP Developers MCPentry revisedNEIGHBOURS §5.1 named the hosted MCP as a companion to index as an artifact, and the graph had no entry for it. ecosystem: umbrella because its content covers SAP technologies across stacks (llms.txt names ABAP Cloud, CAP, Fiori, HANA Cloud and integration) and no single door holds it. No read_only: the anonymous mounts are read-only, but the signed-in tier writes progress (complete_step). No tool_count: the quickstart and the API page list different tools per mount. The site also serves a GraphQL API, not recorded as an interface here for want of a page read. /mcp/homepage is left out of the description: the quickstart lists it as anonymous and the API page as signed-in.MCP server,
Sat 17
68 changes
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host appPackage,
@abap2ui5/linteradded to the atlasCommand-line checker for abap2UI5 app classes and their viewsCLI,
@abap2ui5/mcp-serveradded to the atlasMCP server for the abap2UI5 check, deploy and run loopMCP server,
abap-agent-runtimeadded to the atlasABAP-native MCP endpoint that drives opted-in abap2UI5 appsMCP server,
Show 64 more
abap-cloud-guiadded to the atlasReport-style programming model for abap2UI5 on ABAP CloudPackage,
abap2UI5 for Exceladded to the atlasOffice add-in running an abap2UI5 app in Excel's task paneApp,
abap2UI5 for VS Codeadded to the atlasVS Code extension to preview, activate and lint abap2UI5 appsIDE extension,
abap2UI5 frontendadded to the atlasabap2UI5 frontend as ABAP artefacts installed with abapGitPackage,
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web ComponentsPackage,
abap2UI5 headless frontendadded to the atlasDrives abap2UI5 app classes from ABAP Unit testsPackage,
abap2UI5 Layout Editoradded to the atlasDrag-and-drop UI5 view editor that writes an abap2UI5 app classWeb tool,
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpointDesktop app,
abap2UI5 Playgroundadded to the atlasIn-browser ABAP editor beside the abap2UI5 app it buildsWeb tool,
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocolPractice,
abap2UI5 samplesadded to the atlas129 abap2UI5 sample apps, one ABAP class eachSample,
abap2UI5-addons/open-source-libsadded to the atlasEleven abap2UI5 apps, one per open-source ABAP librarySample,
abap2UI5-addons/popupsadded to the atlasReady-made dialogs for abap2UI5 appsPackage,
abap2UI5-localadded to the atlasabap2UI5 folded into the local classes of one HTTP handlerPackage,
abap2UI5/samples-controlsadded to the atlasUI5 Demo Kit samples rebuilt as abap2UI5 appsSample,
abap2UI5/samples-stackadded to the atlasabap2UI5 apps in front of OData, RAP, events and other technologySample,
admin-cockpitadded to the atlasUsage, error and response-time monitor for abap2UI5App,
app-templateadded to the atlasStarter repository for an abap2UI5 app with CI and agent setupSample,
Clean-Core.ioadded to the atlasHosted workspace redrawing custom ABAP as BPMN and grading itWeb tool,
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successorsWeb tool,
config-managementadded to the atlasTheme, CSS and CSP settings of abap2UI5 pages kept in tablesApp,
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 appsPackage,
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5Sample,
ERPLadded to the atlasDuckDB extension reading SAP ERP tables, CDS views and BW queriesPackage,
erpl-node-rfcadded to the atlasRFC client for Node.js and TypeScript without the NW RFC SDKPackage,
http-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over HTTPApp,
launchpad-kpiadded to the atlasPuts a number from an abap2UI5 app on a Fiori launchpad tilePackage,
layout-managementadded to the atlasTable and form layouts with saved variants for abap2UI5Package,
lock-manageradded to the atlasHolds SAP locks across stateless abap2UI5 roundtripsPackage,
rap-extadded to the atlasFloorplans rendered from CDS UI annotations as abap2UI5 appsPackage,
rfc-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over RFCApp,
sapguiadded to the atlasThirty classic transactions rebuilt as abap2UI5 appsApp,
se16nadded to the atlasTable content browser in abap2UI5, for ABAP Cloud and on premiseApp,
selection-screenadded to the atlasSelect-options with saved variants for abap2UI5 appsPackage,
web-abap2UI5added to the atlasabap2UI5 transpiled to JavaScript and run in a browser tabWeb tool,
abap-adt-apireleased 9.0.01 content item in the atlas was written against an earlier version. Nothing is recorded about what changed.Package,
Agent access to your systemsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Authenticationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Browsing table datadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Cachingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Calling a service by handdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Change promotiondescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Clean code conventionsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Cloudification Repository Viewerrequires, connects revisedSAP's Cloudification Repository entered the graph, so the repository this reads is a node rather than a name in a sentence. Both edges rest on the viewer's own documentation: the repository "lists released standard APIs that can be used to build the TIER 1 layer", and the Repository field is a "Selection of the different release statuses that are made available by SAP in different JSON files". No protocol, direction or condition: the documentation states none.Web tool,
Code reviewdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Data modellingdescription, ecosystems, entry revisedMerged the duplicate ABAP capability into this one, repointed its provides edges, content explains edges and prose links, and retired abap-data-modelling. Its old pages redirect here.Capability,
Database connectorsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Driving the SAP GUIdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Event Meshdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
IDE provisioningdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Launchpad pluginsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
Loading a warehousedescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Maintaining table entriesdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Model visualisationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
ODatadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
OpenAPIdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
SAP GUI screens and listsdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Searching code in a systemdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Serve your application over MCPdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Source controlname, description revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Static analysisdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Transactional modeldescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
UI written in ABAPdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Unit testingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Fri 16
57 changes
Hammer Core Servicesadded to the atlasABAP-side component for the Hammer editorApp,
open-steamgateadded to the atlasLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemApp,
Tools for abapGitadded to the atlasHelper programs around abapGitApp,
abaphackeradded to the atlasPerson,
Show 53 more
Adityaadded to the atlasPerson,
Ajay Sorengadded to the atlasPerson,
Andriy Soboladded to the atlasPerson,
Aravindh Ganapathiadded to the atlasPerson,
arcanist123added to the atlasPerson,
Astrid Ellermann-Aarslevadded to the atlasPerson,
Bastian Dennstedtadded to the atlasPerson,
Birzhan Moldabayevadded to the atlasPerson,
Carsten Leueadded to the atlasPerson,
Christian Mezaadded to the atlasPerson,
Danilo Yorinoriadded to the atlasPerson,
dante4dadded to the atlasPerson,
David Slugaadded to the atlasPerson,
elenasteblinasapadded to the atlasPerson,
Fabian Fellhaueradded to the atlasPerson,
Frank Rogalskiadded to the atlasPerson,
Georg Reichertadded to the atlasPerson,
George Drakosadded to the atlasPerson,
Gurjant Singhadded to the atlasPerson,
harishb2018added to the atlasPerson,
Ingo Bräuningeradded to the atlasPerson,
Jack-Liangadded to the atlasPerson,
Jörgen Lindqvistadded to the atlasPerson,
mara305added to the atlasPerson,
MarcSAPadded to the atlasPerson,
MarinaBlankadded to the atlasPerson,
Martin Bredyadded to the atlasPerson,
Matthaeus Schueleadded to the atlasPerson,
Maxim Kenzhebayevadded to the atlasPerson,
Milosz1234517added to the atlasPerson,
mohammed-kazmiadded to the atlasPerson,
mubasisadded to the atlasPerson,
olgadolinskajaadded to the atlasPerson,
Patrick Jackesadded to the atlasPerson,
Peter Persieladded to the atlasPerson,
reidl-juergenadded to the atlasPerson,
RonnyPahlkeadded to the atlasPerson,
sachin-bk-22added to the atlasPerson,
SAP Tutorialsadded to the atlasPerson,
Sarat Krishnanadded to the atlasPerson,
Sebastian Baskovichadded to the atlasPerson,
silverfish2525added to the atlasPerson,
sleclercilluminaadded to the atlasPerson,
Sowrabh-Mehetreadded to the atlasPerson,
Srinivasa Raghavan Vadded to the atlasPerson,
Steffen-Mattesadded to the atlasPerson,
Sumithra Sudharsanamadded to the atlasPerson,
SvenSadded to the atlasPerson,
Thomas Gauweileradded to the atlasPerson,
Timofei Bazhukovadded to the atlasPerson,
tugba-sap-01added to the atlasPerson,
viktorbernhardtsapadded to the atlasPerson,
Zhaojingadded to the atlasPerson,
Thu 15
36 changes
@abaplint/transpileradded to the atlasTranspiles ABAP to JavaScript to run on Node.jsBuild tool,
cross-http-clientadded to the atlasHTTP client for classic on-premise ABAP and ABAP CloudPackage,
express-icf-shimadded to the atlasShim running an ABAP ICF handler behind an Express 4.x serverPackage,
open-abap-baladded to the atlasApplication logging for ABAP transpiled to JavaScript on Node.jsPackage,
Show 32 more
open-abap-coreadded to the atlasCore ABAP artifacts for code transpiled by @abaplint/transpilerPackage,
open-abap-guiadded to the atlasGUI controls for ABAP transpiled to JavaScriptPackage,
open-abap-lockadded to the atlasConcurrent and cross-session locking for open-abap on PostgreSQLPackage,
open-abap-odataadded to the atlasOData and Gateway shims serving SEGW-style services on Node.jsPackage,
open-abap-pdfadded to the atlasStandalone PDF generator written in ABAPPackage,
open-table-maintenanceadded to the atlasTable maintenance over HTTP for a table fixed in codePackage,
sap-mcp-serveradded to the atlasReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.MCP server,
Werkbankadded to the atlasLocal desktop workspace for AI conversations with SAP connectorsDesktop app,
abap-offstack-aunitprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 names four clients beside its install command and adds "and others", so the four named ones are the value and the open end is not read as a fifth. This is the only entry behind the door that states the third system_reach state, in a sentence of its own: nothing requires a provisioned SAP system. The boundary it states elsewhere, that shimmed-out classes stay an on-stack concern, is the entry's own warning and not a qualification of that value.Skill,
abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door. The README read on 2026-10-15 names the five clients the skills command line supports and adds "and other compatible agents", so the five named ones are the value; the README also documents separate routes for Claude Code, OpenCode and GitHub Copilot in VS Code, which name no client the sentence does not. system_reach is left out: the repository states nothing about needing a system or bringing one, and absent is not a no.Skill,
ADT MCP Serverdescription, provides[0] revisedSAP's launch post for the re-invented Joule for Developers points to the ADT MCP Server's available MCP tools in ADT for Eclipse and says the server drives the developer's own coding agent; it does not describe how the server is enabled in Eclipse. The Help page now reads "launches" where the quote said "starts".MCP server,
Agent access to your codeframing by ecosystem revisedBeside Agent access to your systems, the ABAP door read as two names for one thing. This one is about the code, development objects reached through ADT; that one is about business data and operations. The atlas maintainer's decision.Capability,
Agent evalscore coverage, coverage by flavor, facets, gap revisedThe note rested on "everyone" and "nobody", which nothing here sources. The replacement says what the material read on the three doors covers and what it leaves to the project, which is checkable.Capability,
Agent guidancecoverage by ecosystem, framing by ecosystem, facets, coverage by flavor, framing by flavor revisedskillOverflow entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists.Capability,
ARC-1 Skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills README read on 2026-10-15 names each client one at a time in its manual-install table, with a directory per client, which is why each value carries its own row; the plugin routes it documents beside that are for Claude Code and Agent Plugins, and the skills command line it offers states "any agent" rather than a list. system_reach rests on the prerequisite the README already states, which the entry's own warning repeats: the server is required for every skill that touches ABAP, and the reader connects it.Skill,
Authenticationcoverage by ecosystem, facets, framing by ecosystem revisedThe paragraph counted two services while seven entries stand behind the door, the router and the Cloud Connector among them, so it told a reader the door was smaller than it is.Capability,
claude-abap-devprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. Both answers were already quoted on this entry: the README calls it a Claude Code plugin and names no other client, and the sentence about detecting servers by tool name is the clearest statement of the third state on this door, since the reader supplies the servers and the skills do not care what they are called. Re-read on 2026-10-15 and unchanged.Skill,
claude-abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 lists Claude Code as the first prerequisite and names no other client the plugins install into, so the one value is the whole answer; the AGENTS.md template it ships is for agents that are not Claude and is not an install route the README states. system_reach rests on the sentence the entry's own warning already turned on: there is no connector here, and the reach comes from servers the reader connects.Skill,
Cloud Connectorprovides[capability:authentication] revisedThe edge read as though the connector propagated the user by itself. SAP's own page names three authentication types towards an internal system and says the calling application's destination configuration picks one, and that trust to the cloud entities whose tokens are accepted has to be configured explicitly. The property the BTP door compares on rests on the same sentence.App,
DanKromp/skillOverflowprovides revisedThe entry's own prose said the collection covers UI5 and Fiori work and the edge cited only the total count. The UI5 pass needed to know what that coverage is, because this entry states no flavor and so answers in all of a door's flavors; the two rows name the skills the fallback rests on, which is what the capability's freestyle and web-components readings now cite.Skill,
Fiori annotationscore coverage, coverage by flavor revisedThe door has two flavors and neither was assessed, so both were derived from the options alone. Java reads core-only: the three community providers are cds-plugins @sap/cds loads, and the Java side's own facts are the compiler running under the Maven build and the one hierarchy annotation the Java runtime reads itself.Capability,
LLM integrationcore coverage, coverage by flavor, framing by flavor, facets revisedTwo questions the options here answer differently and the page could not show. Which models an option reaches is the first fact a reader needs, because all but one of the CAP options are clients of SAP AI Core; whether the response can be streamed decides whether a chat surface is possible at all. Both are scoped to cap: the ABAP, UI5 and BTP options were not read for them in this pass.Capability,
Local developmentcore coverage, coverage by flavor, framing by flavor, facets revisedNine options answered this capability with nothing to compare them by, and they are not variants of one tool: the first question a reader has is which part of the local stack an option starts. The two flags separate the hybrid-testing helpers, where cds bind states that only the location of the credentials is stored on the machine and @sang2x/captools states that it writes the resolved VCAP_SERVICES into default-env.json.Capability,
rap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills are cloned into a Claude Code skills directory and the README names no other client, so the one value is the whole answer. system_reach rests on the README's own sentence about VSP, which the reader downloads and configures with their own SAP credentials: the bridge is named and not supplied.Skill,
SAP Power for Kiroprovides, description revisedThe entry said it is packaged as a Kiro power and not how it gets there or which Kiro it needs; the README read on 2026-10-15 states both.Skill,
sap-basis-opsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 says the repository is a Claude Code plugin marketplace and names no other client. system_reach rests on the sentence the entry's own description already paraphrased, and it is the clearest statement of that state on this door: the shell server is the reader's to supply, and the skills carry no credentials of their own.Skill,
sap-mcp-serverentry revisedHanded over in a chat as one address and written from the repository's own README, read raw. Placed on the ABAP door and on agent access to your systems, the concern split out of MCP servers on 2026-10-09: it reaches into a system you run from outside, as the door's two existing providers of that capability do. The README never says ABAP, so the placement rests on the system it reaches and the protocols it names — Gateway OData services, RFC/BAPI, RFC_READ_TABLE and DDIF_FIELDINFO_GET — rather than on a development model it states. Not umbrella: it names ECC and S/4HANA and reaches them through one stack's own protocols, so a door holds it. No tool_count: the README lists its tools in a table and states no count. No flavors: nothing read states standard ABAP or ABAP Cloud. No compat.runtimes: the server is Python with an optional Node bridge, which that enum cannot say.MCP server,
secondsky/sap-skillslinks, flavors, requires, provides, description revisedThe same correction as description.what_it_solves, on the edge that carries this artifact's answer to the capability, so the two do not state the repository's evidence model differently. The rewording also removes the two em dashes the prose scan reported in this field.Skill,
SuperClaude for SAPprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 calls it a Claude Code plugin in its own subtitle and names no other client; the installation steps are documented in a separate file that was not read, which does not change the client. system_reach is the state this entry defines: the server it depends on is installed, configured and connection-tested by its own setup command, which is the fact the entry's own warning about being a stack rather than a component already rests on.Skill,
Telemetrycore coverage, coverage by flavor, framing by flavor, framing by ecosystem, facets revisedThree questions the sources answer differently for the CAP options and that change which one a reader reaches for: which signals it produces, where it can send them, and whether the application has to write code for a signal of its own. Scoped to the CAP door; the ABAP and BTP options were not assessed in this pass.Capability,
Unit testingcore coverage, coverage by flavor revisedTwo staged options state abap-cloud and provide this capability; the gate reads them as providers once this capability is revised.Capability,
Werkbankecosystem revisedThe project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.Desktop app,
Wed 14
11 changes
Agent access to your codenormative relevance revisedThe policy's agentic provision reaches every server that calls ADT for an agent; it was stated on arc-1 alone and as unsourced prose in several boundaries.Capability,
aibap.mcpdescription revisedThe README's own constraint is now its explicit SAP API Policy relation, quoted.MCP server,
arc-1description revisedThe licensing side is its explicit SAP API Policy relation, sourced to its README; the rest restated what any server in front of ADT is. Removed at the atlas maintainer's request on 2026-10-14.MCP server,
Attachmentscoverage by ecosystem revisedThe five citations and four links to FileUploader.ts and UploadCollection.ts used the organisation the project has left, which now answers only as a redirect. Both files were opened at the new address on 2026-10-14 and carry the sentences quoted here, so every claim and every quote stands as written and only the addresses and their titles moved; the checked dates stay at the day each quote was last read in full.Capability,
Show 7 more
Driving the SAP GUInormative relevance revisedThe GUI servers' boundaries each restated the policy in the atlas's own words; it belongs to the concern, sourced to the policy.Capability,
kts982/mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
LLM integrationcoverage by flavor revisedThe PromptInput page no longer carries the sentence this rested on. Read again on 2026-10-14 it states "The @ui5/webcomponents-ai package is under development and considered experimental - components' APIs are subject to change. Furthermore, the package supports Horizon themes only", with no version marker in it. The since-2.0 claim had no second source, so it goes rather than stand unsourced; the experimental state and the Horizon-only limit stay, in the words the page now uses, which are the words coverage_by_ecosystem.ui5 already quoted. The flavor's own assessment of who provides it was not redone, so assessed_at stands.Capability,
mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
midasol/sap-mcp-serverdescription revisedThe whole paragraph was the policy, which Agent access to your systems carries as a condition sourced to the policy.MCP server,
sapgui.mcpdescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
vibing-steampunkdescription revisedThe policy is now a condition of Agent access to your code for ABAP, sourced to the policy itself.MCP server,
Mon 12
15 changes
abap-transport-reviewadded to the atlasTransport release check gated by GitHub pull request approvalApp,
pam-mcp-serveradded to the atlasLocal MCP server on support status from an SAP PAM exportMCP server,
SAP Support Radaradded to the atlasBrowser app checking SAP product support status from a PAM exportWeb tool,
AyhamTadded to the atlasPerson,
Show 11 more
DevEposadded to the atlasPerson,
Héctor Enríquezadded to the atlasPerson,
marcelhermanns-createadded to the atlasPerson,
SaranyaSampathadded to the atlasPerson,
@mcp-abap-adt/corereleased 18.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
abap-transport-reviewentry revisedEntered by intake from the repository README and the repository's own facts. Placed on the ABAP door in the standard-abap flavor only, because the README states the tools are classic ABAP using the CTS_REQUEST_CHECK BAdI, background jobs and the cluster table INDX, "none of which is part of ABAP Cloud".App,
Agent access to your systemscore coverage, coverage by ecosystem, description revisedMaintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged.Capability,
Knowing the maintenance status of a releaseentry revisedDrafted with sap-support-radar and pam-mcp-server, the first umbrella artifacts (ADR-0063), which had no concern to attach to: mcp-servers is serving an application one built, agent-systems-access reaches into a running SAP system, and documentation is first-party docs made searchable. On the ABAP, CAP and UI5 doors because each has a published SAP answer of its own: the Product Availability Matrix, capire's release schedule and the SAPUI5 version overview. BTP is left out: its services name plans and regions rather than releases, and no page was read that states a maintenance period for one. core-only on every door because SAP publishes the answer and no door holds an option of its own; the umbrella entries count into no door's coverage by construction.Capability,
pam-mcp-serverentry revisedStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.MCP server,
SAP Support Radarentry revisedStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.Web tool,
Serve your application over MCPcore coverage, coverage by ecosystem, core coverage, description, facets revisedThe comparison separates exposed contracts, context mechanisms, execution paths and surface selection; provider explanations retain conditions and restrictions. The capability definition and all nine provider conversions must be published together; accepting only the vocabulary leaves legacy provider strings incompatible.Capability,
Sat 10
1 change
Clean Core Measurementadded to the atlasReports Clean Core ATC results per system as Level A to D KPIsApp,
Fri 9
12 changes
abap-offstack-aunitentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/abap-offstack-aunit changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Written from the repository's own README; hard rule 7: skills are indexed, never authored here. The registry's skillspector scan is its own dated claim and is not carried as a field.Skill,
abap-skillsentry revisedA repository the SAP AI Skills Library collection cache carries as processedBy baseline-2026-09-18 and that was never drafted into the atlas, so the changed registry record of 2026-10-09 is the first occasion to enter it; first_seen keeps the baseline date and no revises flag applies, since there is no published entry to revise. Written from the repository's README, its SKILLS_INDEX.md, the skills directory listing and the abap-cloud SKILL.md; hard rule 7: skills are indexed, never authored here.Skill,
Agent access to your systemsentry revisedSplit out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling.Capability,
Agent guidanceecosystems revisedSAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and sap-commerce-skill entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked.Capability,
Show 8 more
btp-sap-odata-to-mcp-serverprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
midasol/sap-mcp-serverprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
odata_mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
odata_mcp_goprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
pyrfc-mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
sap-security-mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
sapskillsentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/clean-abap changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Represented once at repository level, as skillOverflow is: the registry registers one skill, clean-abap, while the repository documents and installs three, so the repository's count is used for the entry and both remain in the crawl record. Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Skill,
Serve your application over MCPecosystems, name revisedThe Commerce and SuccessFactors providers reach into a system from outside and moved to agent access to your systems with their slots.Capability,
Tue 6
4 changes
claude-abap-devadded to the atlasFive ABAP workflows for Claude Code on existing MCP serversSkill,
CoVelesadded to the atlasPerson,
claude-abap-deventry revisedHanded over as a URL in a chat session and written from the repository's own README. Hard rule 7: skills are indexed, never authored here, and the guardrails are reported as the maintainer states them rather than as anything the atlas has run. when_not_to_use and to_build_on_it are left for an editor.Skill,
sap-ai-dev-toolkitdescription, provides, requires, connects, type properties revisedRe-read against the README, tools.md and inventory.md at 0.9.3, published the same day; the entry was written on 2026-10-01 against 0.7.9, and npm records 41 releases in the eleven days since 0.2.5. Three cited sentences no longer exist in the source: the feature row now reads "Discover BAS destinations or local SAP GUI systems", the architecture flow now names "VSP + configured route (BAS, CF, or local SAP GUI)", and the row quoted for authentication ("No credentials in mcp.json") has become "Credential-aware setup", which states the BAS and local halves separately. So Business Application Studio is now a conditional requirement rather than an unconditional one, and the single destination authentication mode is joined by the local ones the README documents. The fourteen facets, the curated ADT surface and every other guardrail quote were re-verified unchanged.MCP server,
Mon 5
6 changes
ABAP-PRCadded to the atlasFramework for multi-step ABAP processes with monitoringPackage,
Brandeis Consultingadded to the atlasPerson,
@mcp-abap-adt/corereleased 17.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 17.0.0Setups against a system with a self-signed or company-CA certificate that worked without any TLS setting.MCP server,
Show 2 more
ABAP-PRCentry revisedEntered by intake from the repository README, the repository description and the maintainer's landing page.Package,
Async processingcoverage by flavor revisedABAP-PRC is the first option here to state ABAP Cloud: its README says the framework core is written in ABAP for Cloud Development on released APIs, and it runs its steps through the background processing framework or as application jobs. The paragraph on SAP's own mechanisms is unchanged and keeps its 2026-09-14 assessment date; no survey of the other providers was made. Its README lists SAP BTP ABAP Environment and S/4HANA Cloud Public Edition as coming soon, and its Fiori apps are classic BSP objects.Capability,
Sun 4
12 changes
arc-1-bopf-enhadded to the atlasarc-1 extension for reading and maintaining BOPF enhancementsMCP server,
arc-1-extension-sampleadded to the atlasSample arc-1 extension in TypeScript with ten custom toolsSample,
eclipsADT-o-matadded to the atlasPowerShell wizard installing Eclipse with ADT and pluginsCLI,
LISAadded to the atlasMCP server for reading and writing ABAP object translationsMCP server,
Show 8 more
ZARC1_EXTENSION_FORMSadded to the atlasarc-1 extension for SAPscript and Smart Forms objectsMCP server,
F-Weradded to the atlasPerson,
arc-1description revisedRe-read against the README, the npm registry record, the extensions page and the release notes on 2026-10-04, with arc-1 at 1.5.0 published 2026-10-02. Every claim the entry already carried still holds word for word, so the checked dates move and the text does not, except where the documentation says something the entry did not. Two such things: Custom_* tools an operator registers without forking, which the corpus already recorded on claude-sap-kit and not on the server those tools run in, and one agent plugin that installs the server together with ARC-1 Skills. The seven guardrails added were stated when the entry was written and left out of it; they are quoted, not counted. The run_code facet stays absent: the extensions page gates class and report execution behind two flags and a plugin the operator writes, which is not the server stating that it runs code.MCP server,
arc-1-bopf-enhentry revisedEntered by intake from the repository README after the admin had routed the URL to a refresh of arc-1, which reported it as a candidate of its own. Written from the README and the repository description.MCP server,
arc-1-extension-sampleentry revisedEntered by intake from the README, found through ARC-1's extensions page, which links it as the worked sample.Sample,
eclipsADT-o-matentry revisedEntered by intake from the repository README and description.CLI,
LISAentry revisedEntered by intake from the README, found through ARC-1's extensions page, which names it in its example of driving a custom ABAP HTTP service.MCP server,
ZARC1_EXTENSION_FORMSentry revisedEntered by intake from the repository README and description.MCP server,
Sat 3
5 changes
Maherd18/sap-mcp-serveradded to the atlasPolicy-checked MCP server for ABAP development over ADTMCP server,
Maher Darweeshadded to the atlasPerson,
@mcp-abap-adt/corereleased 16.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 16.0.0Descriptions of five authentication methods including client certificates and Kerberos, and setups that rely on a .env in the directory the server starts in.MCP server,
Show 1 more
Maherd18/sap-mcp-serverentry revisedHanded over as a URL. Behind the ABAP door because the objects it reads and changes are ABAP ones in a system reached over ADT. Two edges: agent access to your code for the eight tools over ADT, with create_objects entered as false because the README states that choice rather than leaving it out, and tool governance for the policy file, the allow-lists, the read-only switch, the approval and separation-of-duties rules, the dry-run mode and the audit log, which the README's own opening makes the point of the server. MCP servers was considered and left off: that capability is a protocol adapter on a running application service, and this one helps somebody write code, which its own description sends here. No flavor is stated, since the README names no ABAP release or cloud edition; tool_count is left out because the README names no number, and the eight in the prose is a count of its own Tools table. The second tool governance provider on the ABAP door, where the reading was community-only with one; the coverage note is left to revisit by hand.MCP server,
Thu 1
11 changes
ABAP Architectadded to the atlasEclipse plug-in turning JSON or XML into ABAP types and DDIC objectsIDE extension,
abaprapunmanagedadded to the atlasPractice repository for the unmanaged RAP scenarioSample,
abaprapunmanagedsaveadded to the atlasPractice repository for managed RAP with unmanaged saveSample,
abapthemesadded to the atlasThree colour themes for ABAP source in ADT for EclipseIDE extension,
Show 7 more
abapwuluadded to the atlasRefreshes the where-used list for objects in one packageCLI,
sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP systemMCP server,
Gurkan Yilmazadded to the atlasPerson,
Marco Marronefirst recorded in the atlasPerson,
Murat Tahtacıadded to the atlasPerson,
Bellasources, interfaces revisedThe entry recorded the MCP connection Bella opens to ARC-1 and not the one it answers: on the two subscription routes Bella starts a CLI with its built-in tools switched off and hands it the adt_* tools over an MCP server of its own. The README states the server, the address and the token in both of those sections. An interface is a fact about the node and belongs on the thing that offers it (docs/concepts/design-roles-and-interfaces.md §3), so it is entered here rather than left to be read off the CLI's side.IDE extension,
sap-ai-dev-toolkitentry revisedDrafted from the repository's own README and LICENSE after the URL was handed over directly. Typed as an MCP server because what it gives an agent is a generated stdio entry per BAS destination; the setup command and the HANA inspector ship in the same package.MCP server,

Wed 30
5 changes
Bellaadded to the atlasEclipse plugin bringing Claude into ABAP Development ToolsIDE extension,
Kilian Taubmannadded to the atlasPerson,
@mcp-abap-adt/corereleased 15.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 15.0.0Instructions that start a test run with CreateUnitTest and poll GetUnitTestStatus.MCP server,
Show 1 more
Bellaentry revisedHanded over as a repository URL in an intake request. It is the first entry on the ABAP door that puts the assistant inside the ADT editor rather than in front of ADT as a separate server, and its README compares its own tools with those of ARC-1, which the graph already holds.IDE extension,
Tue 29
9 changes
ABAP Statistical Toolsadded to the atlasABAP class for descriptive statistics over an internal tablePackage,
Hammeradded to the atlasNative macOS code editor for ABAP and CDSDesktop app,
pyrfc-mcpadded to the atlasMCP server calling RFC-enabled function modules behind an allowlistMCP server,
ui5-tcode-finderadded to the atlasBrowser page searching SAP transaction codesWeb tool,
Show 5 more
André Schärpfadded to the atlasPerson,
Yassin Bahriadded to the atlasPerson,
Finding a transaction codeentry revisedA browser tool for searching transaction codes had nowhere to attach, and the nearest nodes are all about something else: browsing table data is the rows a system holds rather than the way into a task, GUI automation drives screens rather than finding them, abap-classic-ui builds them, and documentation is what to read. Named on the ABAP door because a transaction code is an entry point of a classic SAP system, and marked not-applicable in ABAP Cloud, where there is no SAP GUI and so no command field to enter one into. The coverage rests on SAP's own documentation for the in-session routes; nobody has surveyed what else answers this from outside a system, which is why the relationship is unassessed.Capability,
pyrfc-mcpentry revisedHanded over as a URL. Filed behind the ABAP door because the system it reaches is an ABAP one and the reader who points it at theirs is working on that system, which is the opposite case from open-rfc, a client an ABAP developer would never install. Three edges: MCP servers for the tool surface over function modules, agent access to your code for read_abap_source alone, and tool governance for the allowlists, the table guard, the result limits and the audit log, which the README states as the point of the server rather than as a footnote. RFC connectivity was considered and left off: the RFC client here is PyRFC, so nobody installs this to call a function module from their own code. No flavor is stated, since the README names no ABAP release or cloud edition, and auth and tool_count are left out because the README names neither a mechanism nor a number.MCP server,
ui5-tcode-finderentry revisedStaged with the capability Finding a transaction code, drafted in the same batch because the corpus held no concern for it. ecosystem: abap is a placement rather than a stated fact: the repository is an OpenUI5 and TypeScript application, but its subject is the transaction codes of a classic SAP system and the only stack its features name is SAP GUI for HTML. serves_ecosystems: ui5 rests on the overview sentence naming the T-Codes a UI5 or Fiori project needs. use_as: reference because it is consulted at its own address rather than installed into a project.Web tool,
Mon 28
72 changes
claude-sap-kitadded to the atlasClaude Code plugin adding Custom_* tools to arc-1Skill,
_juliettechfirst recorded in the atlasPerson,
Abhishek Agarwalfirst recorded in the atlasPerson,
Adaptive Garagefirst recorded in the atlasPerson,
Show 68 more
Alessio Pelliccionefirst recorded in the atlasPerson,
alfo-devfirst recorded in the atlasPerson,
Andrei Blizorukovfirst recorded in the atlasPerson,
Anthony Quéréfirst recorded in the atlasPerson,
Arthur Barrettfirst recorded in the atlasPerson,
Artyom Bogachenkofirst recorded in the atlasPerson,
Atef Bellaajfirst recorded in the atlasPerson,
Callum Keoganfirst recorded in the atlasPerson,
catmemefirst recorded in the atlasPerson,
Chafirst recorded in the atlasPerson,
Chiranjeevisantosh Madugundifirst recorded in the atlasPerson,
Dan Lewfirst recorded in the atlasPerson,
Daniel Paulusfirst recorded in the atlasPerson,
Danny Avilafirst recorded in the atlasPerson,
David Nealefirst recorded in the atlasPerson,
David Newmanfirst recorded in the atlasPerson,
Doylefirst recorded in the atlasPerson,
Dustin Healyfirst recorded in the atlasPerson,
Eduardo Cruz Guedesfirst recorded in the atlasPerson,
Émilien (perso)first recorded in the atlasPerson,
ethanlajfirst recorded in the atlasPerson,
Fahleen Ariffirst recorded in the atlasPerson,
Federico Ruggifirst recorded in the atlasPerson,
Ganesh Bhatfirst recorded in the atlasPerson,
Gerald M.first recorded in the atlasPerson,
hellojacccfirst recorded in the atlasPerson,
heptapodfirst recorded in the atlasPerson,
Jakub Fidlerfirst recorded in the atlasPerson,
Jannik Maierhöferfirst recorded in the atlasPerson,
Joel Hirzelfirst recorded in the atlasPerson,
Jón Levyfirst recorded in the atlasPerson,
Joseph Licatafirst recorded in the atlasPerson,
Karthikeyan Nfirst recorded in the atlasPerson,
kenzaelk98first recorded in the atlasPerson,
Linus Gasserfirst recorded in the atlasPerson,
Marco Berettafirst recorded in the atlasPerson,
Max Sannafirst recorded in the atlasPerson,
Maximfirst recorded in the atlasPerson,
Michael Ludvigfirst recorded in the atlasPerson,
michnovkafirst recorded in the atlasPerson,
mohamed magdyfirst recorded in the atlasPerson,
Muhammad Abdullahfirst recorded in the atlasPerson,
MyGitHubfirst recorded in the atlasPerson,
NalinNairfirst recorded in the atlasPerson,
NKfirst recorded in the atlasPerson,
Odrecfirst recorded in the atlasPerson,
owengofirst recorded in the atlasPerson,
papasaidfinefirst recorded in the atlasPerson,
Pavel Fediushinfirst recorded in the atlasPerson,
Pedro Reisfirst recorded in the atlasPerson,
Peterfirst recorded in the atlasPerson,
poornapragnyahfirst recorded in the atlasPerson,
Rakshitfirst recorded in the atlasPerson,
Rene Heijdensfirst recorded in the atlasPerson,
rossbgfirst recorded in the atlasPerson,
Samuel Pathfirst recorded in the atlasPerson,
Scott Finlayfirst recorded in the atlasPerson,
Sean DMRfirst recorded in the atlasPerson,
Sean McGrathfirst recorded in the atlasPerson,
Seung Hyun Myungfirst recorded in the atlasPerson,
Shahryar Tayebfirst recorded in the atlasPerson,
silvius1996added to the atlasPerson,
Theo N. Truongfirst recorded in the atlasPerson,
WhammyLeaffirst recorded in the atlasPerson,
Zihao Zhoufirst recorded in the atlasPerson,
@mcp-abap-adt/corereleased 13.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
@mcp-abap-adt/corereleased 14.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
claude-sap-kitentry revisedHanded over as a URL. Typed skill rather than mcp-server or package: what a reader installs is a Claude Code plugin of three SKILL.md directories, and the tool surface it brings belongs to arc-1, which serves MCP — one artifact_type per entry (hard rule 9), the same shape ARC-1 Skills takes beside that server. It answers agent access to your code through the five Custom_* tools and agent guidance through the three skills, and states the standard-abap flavor by its requirements, which rule out the two public-cloud ABAP targets by name.Skill,
Sun 27
24 changes
ADT MCP Serverpart of, description revisedThe server is a preference inside the extension, and the connection to an ABAP system is the extension's, stated on its own entry with the protocols SAP's marketplace page names (docs/concepts/design-roles-and-interfaces.md, P3); a part points up at its whole and enters the fact once.MCP server,
arc-1connects, requires, description revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P1), and it attaches the system's entry. The two BTP connections are stated under the README's Cloud Foundry deployment heading, so they carry that condition; the Destination service's sentence states identity forwarding and no data flow, and the ABAP environment's sentence names no protocol. The README's credits table names abaplint as what the linter uses. Two older defects go with it: a nested link that rendered its outer bracket as text, and abap-adt-api named in the same quoted sentence as the other two inspirations and carried by no edge.MCP server,
Async processingcore coverage revisedcapire audit 2026-09-27, proposed pages read a fourth time: the description draws the line between queued work and messaging, and the events index states that line in SAP's words.Capability,
Attachmentscore coverage revisedThe paragraph opened with SAP's packages and never said that the runtime serves a @Core.MediaType element with nothing installed. capire's Serving Media Data page is that built-in layer, cited by pagination-and-streaming and not here. Two deliveries, said apart (docs/concepts/sap-ships-and-documents.md).Capability,
Show 20 more
Authenticationcore coverage revisedcapire audit 2026-09-27, proposed pages read once more: the security overview and the product security overview were cited nowhere; the first carries a boundary SAP draws itself.Capability,
Authorizationcore coverage revisedcapire audit 2026-09-27, proposed pages read once more: a page this capability owns was cited nowhere.Capability,
Configurationcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Capability,
Data modellingcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: the service definition page and the Node.js reflection API were cited nowhere; the Java reflection API already was.Capability,
Data privacycore coverage revisedcapire audit 2026-09-27, judgement pages read a fifth time: the description says data privacy is doing what the law requires, and the security index's table calls data privacy a legal concept and data protection a suite of security measures; the row is quotable as written.Capability,
Database connectorscore coverage revisedcapire audit 2026-09-27, link-only pass: a page this capability owns was cited nowhere.Capability,
Debuggingcore coverage revisedPackage pass 2026-09-27: the paragraph named one of the four SAP packages and cited the plugins index only; cds debug and the Java developer dashboard were cited nowhere.Capability,
Documentationcore coverage revisedPackage pass 2026-09-27: the capability had no paragraph and no source at all.Capability,
Event Meshcore coverage revisedcapire audit 2026-09-27, proposed pages read a fourth time: the paragraph says messaging rests on intrinsic eventing, and the events index says the same in SAP's words.Capability,
Feature togglescore coverage revisedcapire audit 2026-09-27: the Feature Toggles guide documents toggled features as built into both runtimes, with the production toggle provider left to the project, which is exactly what the one community option supplies. The capability had no core paragraph and no source.Capability,
fr0ster/mcp-abap-adtconnects, description, provides[0], lineage revisedThe README's acknowledgment names the project it started from; the graph holds it, and the edge is the maintainer's own sentence.MCP server,
Input validationchanged in, core coverage revisedcapire audit 2026-09-27, proposed pages read a third time: the boundary said the check past the constraints is a before handler of the developer's own, and the two pages that document that handler were cited nowhere; the Node.js page states the order the boundary implies, declarative first.Capability,
Local developmentcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Capability,
Localizationcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
Loggingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
ODatacore coverage, facets revisedA role in a design is filled from evidence that an option speaks what the fixed part exposes, and that join runs over one protocol vocabulary (docs/concepts/design-roles-and-interfaces.md, P2). Declared here so options can state it; absent stays "does not say".Capability,
Retrieval-augmented generationcore coverage revisedcapire audit 2026-09-27, link-only pages read a fourth time: vector embeddings are one of the three things SAP frames as CAP's native AI support, in the one sentence the section's index says of its own.Capability,
Serve your application over MCPcore coverage revisedcapire audit 2026-09-27, link-only pages read a fourth time: MCP services are one of the three things SAP frames as CAP's native AI support, in the one sentence the section's index says of its own.Capability,
Telemetrycore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
vibing-steampunkconnects revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P3): the sentence each ABAP server carries and nobody had entered, which the tool role of the ABAP pilot reads as the arrow from the server to the system.MCP server,
The last 30 days. Older changes stay in each entry's history.
AtomJSON