onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewSAP Business Technology Platform, also named SAP Business AI Platform

New in BTP/BAIP

7 days30 days90 daysAll time
In the last 30 days
361added to the atlas270new pieces of content466revisions
Change: 2
Kind
Origin
Domain
Clear all
827 changes
DayCapability
Change RevisedChange Added to the atlas

Today
48 changes
BASEnvSyncadded to the atlasCarries home-directory dotfiles from one BAS dev space to anotherIDE extension,
Bryan Thompsonadded to the atlasPerson,
Robin van het Hofadded to the atlasPerson,
Account provisioningcore coverage revisedReassessed against the graph (check:capabilities): a newer independent provider covers access assignments, a kind the text did not name. State unchanged.Capability,
Show 44 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,
Agent toolingcore coverage, coverage by flavor, coverage by ecosystem revisedReassessed against the graph (check:capabilities): sap-joule-studio and sap-joule, both sap-official, now provide this capability behind the BTP door, so the note's claim about every entry no longer held. The state stays core-only: no provider of another origin counts for the door.Capability,
Agent workspacescore coverage revisedReassessed against the graph (check:capabilities): Joule Work is a sap-official provider serving BTP, so the core is present; the note's absence claim is dropped.Capability,
App hostingcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the absence claim about ui5 artifacts.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,
Audit loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note counted providers, said every provider is a service although a SAP-published practice for HANA audit policies now sits behind the door, and carried a typo. The state stays core-only: that practice is sap-official and no provider of another origin counts for the door.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,
Cataloguing and lineagecore coverage revisedReassessed against the graph (check:capabilities): a newer community server publishes Delta shares as data products in Business Data Cloud, a kind the text did not name.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,
Consumption monitoringcore coverage revisedReassessed against the graph (check:capabilities): the note counted repositories, and the service that the core sentence names is now an artifact in the graph, so it is linked. State stays core-only.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,
Deploymentcoverage by ecosystem revisedReassessed against the graph (check:capabilities): SAP's BTP services now provide this capability behind the door, so the note's count-like absence of providers no longer holds. The state stays core-only: the providers are SAP-official and none comes from the community.Capability,
Destinationscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the entry is in the graph, so the name links to it and not to its repository (WRITING section 3.6).Capability,
Document extractioncoverage by ecosystem revisedReassessed against the graph (check:capabilities): removed the provider-count and absence claims (docs/WRITING.md §3); the states are unchanged.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,
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,
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,
Identity provisioningcore coverage revisedReassessed against the graph (check:capabilities): the note claimed every repository behind the entry is a sample, which stopped being true when the SAP-official service entry arrived. State stays core-only.Capability,
Launchpad and site contentcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed that no community artifact exists, which no longer holds; it now names the kinds the SAP service and the community package add.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,
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,
Mobile appscore coverage revisedReassessed against the graph (check:capabilities): the note explained a state the providers contradict and counted collections.Capability,
Operations automationcore coverage revisedReassessed against the graph (check:capabilities): removed a count of repositories and named the kinds of newer providers, which are SAP-official BTP services and leave the state core-only.Capability,
Platform migrationcore coverage revisedReassessed against the graph (check:capabilities): a partner artifact serving the BTP door provides this capability, which the core-only state contradicted. The core stays, since what_core_does is sourced.Capability,
Predictive modelscore coverage revisedReassessed against the graph (check:capabilities): the note explained the state by the batch it was written from and counted repositories; it now names the kinds of SAP service that have since arrived. The state stays core-only: both are sap-official services on the btp door.Capability,
Process automationcore coverage revisedReassessed against the graph (check:capabilities): a rule-based SAP service for S/4HANA situations joined the providers and changes the shape of the answer. State stays core-only.Capability,
Prompt managementcoverage by ecosystem, core coverage revisedReassessed against the graph (check:capabilities): the note was a claim about who provides, which the option list derives.Capability,
Rate limitingcore coverage revisedReassessed against the graph (check:capabilities): API Management, an SAP-official service on the BTP door, lists CAP in serves_ecosystems and provides this capability, so the core is present for CAP beside the in-process community plugins. The relationship stays unassessed for lack of documentary evidence on the history.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,
Secrets rotationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): SAP Credential Store is sap-official and lists cap in serves_ecosystems, so SAP is present for CAP.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,
Task and approval UIscoverage by ecosystem revisedReassessed against the graph (check:capabilities): SAP Task Center (btp-task-center, sap-official) lists ui5 in serves_ecosystems, so the UI5 door has an SAP-official presence; the note also made an absence claim about the graph.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,
Vulnerability scanningecosystems, description revisedPublic feedback issue #10. CAP and UI5 coverage assessed as unmapped: no atlas artifact provides the dependency-tree check there yet.Capability,
Yesterday
1 change
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
205 changes
btp-agentadded to the atlasLangGraph agent and UI5 chat screen over four BTP MCP serversSample,
SAP-samples/hana-cli-claude-pluginadded to the atlasClaude Code plugin registering hana-cli's MCP serverMCP server,
abhishekmishra2305added to the atlasPerson,
AjayNayak01added to the atlasPerson,
Show 201 more
Akash Mishraadded to the atlasPerson,
Alain VIGUIEadded to the atlasPerson,
Aleksandar Aytovadded to the atlasPerson,
Alexadded to the atlasPerson,
Alexander Biskopadded to the atlasPerson,
Alexander Dümontadded to the atlasPerson,
Alexander Laisadded to the atlasPerson,
Alexander Nickeadded to the atlasPerson,
alisadermenadded to the atlasPerson,
alisonjiadded to the atlasPerson,
amanvarshney-sapadded to the atlasPerson,
Amin Tehauchaadded to the atlasPerson,
amrita-varshiniadded to the atlasPerson,
Andreas Hircheadded to the atlasPerson,
Andreas Kyrianadded to the atlasPerson,
AndreasForsteradded to the atlasPerson,
Andrey Rzhaksynskiyadded to the atlasPerson,
ankitshah25added to the atlasPerson,
Anurag Batraadded to the atlasPerson,
arjith-p-jadded to the atlasPerson,
Asher Kirshenbaumadded to the atlasPerson,
Axel Siebenbornadded to the atlasPerson,
Bhagabat Prasad Beheraadded to the atlasPerson,
Biser Simeonovadded to the atlasPerson,
Bjoern Brencheradded to the atlasPerson,
Brook Zhaoadded to the atlasPerson,
ceylinoadded to the atlasPerson,
ceylinozdemiradded to the atlasPerson,
chantakkuenadded to the atlasPerson,
Chen Xinadded to the atlasPerson,
cherepnevadded to the atlasPerson,
Chris Bezuidenhoutadded to the atlasPerson,
Chris Perumaladded to the atlasPerson,
chris-snopudadded to the atlasPerson,
Christian Savchevadded to the atlasPerson,
Christianeadded to the atlasPerson,
Christoph Morgenadded to the atlasPerson,
Claire Tsengadded to the atlasPerson,
Claire Westadded to the atlasPerson,
claudipadded to the atlasPerson,
Clemens Biehladded to the atlasPerson,
Clemens Hoffmannadded to the atlasPerson,
d022911added to the atlasPerson,
Dan Antonioadded to the atlasPerson,
Daniel Kurzynskiadded to the atlasPerson,
Daniel Wroblewskiadded to the atlasPerson,
daniil-bolobonovadded to the atlasPerson,
Dariaadded to the atlasPerson,
davbizer93added to the atlasPerson,
Dhrubajyoti Pauladded to the atlasPerson,
DIGANTA-MANDALadded to the atlasPerson,
Divya-Shanmugambadded to the atlasPerson,
Domnicadded to the atlasPerson,
Eason-Lingadded to the atlasPerson,
elenaylzadded to the atlasPerson,
elinazhelevaadded to the atlasPerson,
Emil Aleksandrovadded to the atlasPerson,
Fabian Spechtadded to the atlasPerson,
faizakareem02added to the atlasPerson,
fdobrigkeitadded to the atlasPerson,
Felix Schneideradded to the atlasPerson,
Francisco Robledoadded to the atlasPerson,
FrankGottfriedadded to the atlasPerson,
Gajraj Mohiniadded to the atlasPerson,
Gaurav Abbiadded to the atlasPerson,
Gauravi Shuklaadded to the atlasPerson,
gauravpalekar1980added to the atlasPerson,
gdsapadded to the atlasPerson,
geigerj0added to the atlasPerson,
Gowrisankaradded to the atlasPerson,
Hartmut Straubadded to the atlasPerson,
Helen Vernonadded to the atlasPerson,
hemshukadded to the atlasPerson,
i307698added to the atlasPerson,
ikasarovadded to the atlasPerson,
ilias-gmailadded to the atlasPerson,
ilyabelozerovadded to the atlasPerson,
Ivan Dimitrovadded to the atlasPerson,
ivanaangelovadded to the atlasPerson,
Jacek Konopelskiadded to the atlasPerson,
James Fitzpatrickadded to the atlasPerson,
Jeet Kapaseadded to the atlasPerson,
jensglanderadded to the atlasPerson,
JieJi1995added to the atlasPerson,
jing headded to the atlasPerson,
Joe Görlichadded to the atlasPerson,
Johannes Brandenburgeradded to the atlasPerson,
John Kengadded to the atlasPerson,
jonas-200added to the atlasPerson,
Jonas-Isradded to the atlasPerson,
Joshua Vécseiadded to the atlasPerson,
Joyadded to the atlasPerson,
JRSAPAIadded to the atlasPerson,
Kaloyan Proynovadded to the atlasPerson,
Kaloyan Simitchiyskiadded to the atlasPerson,
Kannan Kumaradded to the atlasPerson,
kdayradzhievadded to the atlasPerson,
Keren Rotenbergadded to the atlasPerson,
Krasimir Kargovadded to the atlasPerson,
Kristian Atanasovadded to the atlasPerson,
Lea Poletinadded to the atlasPerson,
levwzadded to the atlasPerson,
lisa-rzoadded to the atlasPerson,
Lorena Hanseradded to the atlasPerson,
Louis Desreumauxadded to the atlasPerson,
Lucia Subatinadded to the atlasPerson,
Luís Marquesadded to the atlasPerson,
Maheswar147added to the atlasPerson,
Maiara-Ellwangeradded to the atlasPerson,
ManoharGuptaKancharlaadded to the atlasPerson,
manolvalchevadded to the atlasPerson,
mara004added to the atlasPerson,
MarcDaniauadded to the atlasPerson,
Markus Balsamadded to the atlasPerson,
Martin Plummeradded to the atlasPerson,
Martin Raeppleadded to the atlasPerson,
Matthew Shawadded to the atlasPerson,
MaximilianGanderadded to the atlasPerson,
mayaStefanovaSapadded to the atlasPerson,
michael-cliffadded to the atlasPerson,
Miguel Angel Meza Martinezadded to the atlasPerson,
mjmoylan0added to the atlasPerson,
mmicciolo-sapadded to the atlasPerson,
Mo Sahihi Benisadded to the atlasPerson,
Moritz Schrammadded to the atlasPerson,
Mrizwanshaikadded to the atlasPerson,
msaravanabhavanadded to the atlasPerson,
nagesh-caparthyadded to the atlasPerson,
nagesh-caparthy1added to the atlasPerson,
namadiptaadded to the atlasPerson,
Nandana Sivaprasadadded to the atlasPerson,
nataliakadded to the atlasPerson,
ncktz-cbsadded to the atlasPerson,
Neetha Pucknatadded to the atlasPerson,
Nidhi Sawhneyadded to the atlasPerson,
Nikola Braukmülleradded to the atlasPerson,
Nikola Simeonovadded to the atlasPerson,
Nikolay Penchevadded to the atlasPerson,
nikolay-kabadzhovadded to the atlasPerson,
Nina Hingerladded to the atlasPerson,
Nitish Kumaradded to the atlasPerson,
Ogulcan Kusluogluadded to the atlasPerson,
oksanazubchenkoadded to the atlasPerson,
oleksiikrasnovskyiadded to the atlasPerson,
Oliver Stiefboldadded to the atlasPerson,
Patrick Lowinadded to the atlasPerson,
Pavel-lazhbanauadded to the atlasPerson,
phalaksha-c-g-sap-comadded to the atlasPerson,
Philippe Addoradded to the atlasPerson,
Piotr Tesnyadded to the atlasPerson,
PrayasDas03added to the atlasPerson,
Raghunath Deshpandeadded to the atlasPerson,
Rangel Ivanovadded to the atlasPerson,
Ricardo Chinadded to the atlasPerson,
rob-sc-sapadded to the atlasPerson,
Roshin Rajan Panackaladded to the atlasPerson,
rronaldkadded to the atlasPerson,
sam-1-0added to the atlasPerson,
San Tranadded to the atlasPerson,
SarahKraemeradded to the atlasPerson,
Selvakumar Shanmugamadded to the atlasPerson,
Sergio Rozenszajnadded to the atlasPerson,
sherene-tan-sapadded to the atlasPerson,
shivendu14added to the atlasPerson,
Sid Bhattacharyaadded to the atlasPerson,
Siddhartha Routhadded to the atlasPerson,
smitaNayakadded to the atlasPerson,
SoniaPetrescuadded to the atlasPerson,
Stefan Yonkovadded to the atlasPerson,
Stephan Aßmusadded to the atlasPerson,
Stephan Klevenzadded to the atlasPerson,
Stephanie Jerchadded to the atlasPerson,
stevenjacobson1added to the atlasPerson,
Stoyan Gradevadded to the atlasPerson,
Stoyan Ivanovadded to the atlasPerson,
stoyanZiadded to the atlasPerson,
suhanigargadded to the atlasPerson,
Sven Kohlhaasadded to the atlasPerson,
Swenadded to the atlasPerson,
Tarang Guptaadded to the atlasPerson,
Teodoradded to the atlasPerson,
todd-r-hannaadded to the atlasPerson,
Trinidadadded to the atlasPerson,
tsvetanmadanski-sapadded to the atlasPerson,
UzYavadded to the atlasPerson,
Vasko Bozhurskiadded to the atlasPerson,
Velizar Kalapovadded to the atlasPerson,
velizarstoianovadded to the atlasPerson,
Viral Singhadded to the atlasPerson,
vishnupriyar05added to the atlasPerson,
Vivekadded to the atlasPerson,
Volker Saggauadded to the atlasPerson,
Werner Todadded to the atlasPerson,
Wolfgang Scheeradded to the atlasPerson,
yashika-Gulatiadded to the atlasPerson,
yatsealiadded to the atlasPerson,
Yavor Mladenovadded to the atlasPerson,
zhouwei0115added to the atlasPerson,
詹斯迪added to the atlasPerson,
SAP HANA Cloudprovides revisedThe capability was added on 2026-10-24 for administering a database instance; SAP HANA Cloud ships its administration tools, so it is the core answer on BTP.Service,
SAP-samples/hana-developer-cli-tool-exampleprovides, serves ecosystems, domain, provides revisedIts performance analysis, privilege grants and backup and recovery commands had no capability to sit under; Database administration was added for them the same day.CLI,
Fri 23
6 changes
BTP MCP Serverserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README names BTP Core Services and the proxy it runs on, never CAP. It read as a routing leftover from when the MCP servers capability lived on the CAP door; the entry stays on BTP, its home.MCP server,
hana-mcp-serverserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README names HANA and no CAP stack. Removed with the other unsourced tags from that sweep; the entry stays on BTP, its home.MCP server,
odata-mcp-proxyserves ecosystems revisedThe tag came in with the entry on 2026-09-10 and nothing sourced it: the README describes a config-driven proxy on BTP Cloud Foundry and names no CAP stack. Removed with its sibling configs; the entry stays on BTP, its home.MCP server,
SAP Analytics Cloudlinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Service,
Show 2 more
SAP Business Data Cloudlinks revisedSAP publishes the What's New entries for SAP Business Data Cloud on its own feed; the entry linked none before.Service,
SAP Dataspherelinks revisedSAP moved the What's New entries for SAP Business Data Cloud, SAP Datasphere and SAP Analytics Cloud to the Business Data Cloud feed; the old BTP feed had stopped carrying them.Service,
Thu 22
1 change
scecadded to the atlasDocker Compose IoT edge stack that connects to SAP BTPSample,
Tue 20
20 changes
abhijeetjangamadded to the atlasPerson,
AWS for SAPadded to the atlasPerson,
B-Tocs.org Communityadded to the atlasPerson,
Björn Panteradded to the atlasPerson,
Show 16 more
cch-engineeringadded to the atlasPerson,
Christoph Clausadded to the atlasPerson,
Daniel Huseradded to the atlasPerson,
GuidoJageradded to the atlasPerson,
huschlekadded to the atlasPerson,
lofonDadded to the atlasPerson,
Lukas Leistenadded to the atlasPerson,
Markus Malenkeadded to the atlasPerson,
MDJoergadded to the atlasPerson,
mprevathiadded to the atlasPerson,
orhangoektas-sapadded to the atlasPerson,
ppm230590added to the atlasPerson,
prasanth23590added to the atlasPerson,
revathimp25added to the atlasPerson,
thfiedleradded to the atlasPerson,
yalcingurleksapadded to the atlasPerson,
Mon 19
7 changes
@marianfoo/sap-mcp-authdescription, type properties, connects revisedRe-read against the README as it stands today. "No token endpoint" and "there is no client-credentials flow to use instead" were absence claims about SAP's portals that no source makes, so they are gone and the paragraph now says what the module does and whom it serves. The maintainer's own unofficial caveat, and the origins password login refuses, are in when_not_to_use. The package block states that it is imported into the caller's own program and installed from npm. The README names Cloud Identity Services as the tenant the login goes to, which is an edge rather than a phrase in a paragraph.Package,
Agent workspacesecosystems revisedThe ABAP, CAP and UI5 views existed only to hold Werkbank, whose stack-specific part is its catalog of development skills and connectors, not the workspace. That contribution moved to Agent guidance; nothing behind those doors offers a workspace of its own.Capability,
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,
Destinationsecosystems revisedui5-middleware-destination was staged in intake-20261019-bestofui5 under ui5-build-tooling; its drafter left out a destinations edge because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Show 3 more
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,
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,
Sun 18
3 changes
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
289 changes
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpointDesktop app,
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successorsWeb tool,
SAP-samples/digital-manufacturing-extension-samplesadded to the atlasSamples for the six extension types of SAP Digital ManufacturingSample,
[Blog Post] SAP Event Mesh - Consuming S4 events simultaneously in CAP-based applications and SAP Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Show 285 more
[Blog Post] SAP Event Mesh – CAP based implementation of SAP Event Mesh in a Single-Tenant Scenarioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
[BTP HANA Cloud Database] : How to access HANA Cloud Database & HDI Container in BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
#BTP #SAPCAP: Quirky Nuggets (N03-N04)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
#SAPCAP: Win Customer Trust using Data Privacy and Protection Services on BTP - Part 2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
#SAPCAP: Win Customer Trust using Data Privacy and Protection Services on BTP - Part 3explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
2024/01最新版！Productivity Toolsを使ったCAPバックエンド開発②~HANA Cloud編~explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Accelerate your migration to SAP Integration Suiteexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Access to Generative AI Modelsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Doc,
Account provisioningdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Adapting SAP Joule for Purchase Order Creation from an Existing Purchase Requisitionexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Adding Custom Metrics to a CAP application using cap-js/telementry plugin and SAP Cloud Loggingexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Adding Shell Plugin to SAP Fiori CAP Application and Deploying to Cloud Portal Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
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,
Agentic AI on BTP: a Multi‑Agent App with Pydantic AIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Agentic AI on BTP: a Single Agent with LangGraphexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Agentic CAP: Build MCP servers and enterprise AI agentsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Agentic Engineering for SAP BTP Extensionsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Agentic memory: Knowledge graph engine and recall in SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Agentic SAP BW modernization: Your path to SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
AI-enabled administration: Automating log analysis with generative AI hubexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
AI-native North Star architecture — Platform Layerexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
AkzoNobel: Modernizing integration at enterprise scaleexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
An approach to secure multiple integrated SAP CAP java applications with a common XSUAA service instanceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
An Innovative Language Exchange App developed with SAP Build Apps, CAP, Kyma, and OpenAIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Analyze and optimize ABAP Cloud model apps built on core data servicesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
API Composition: Seamless Enterprise Data Access for Developers and AI Agentsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
App hostingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
Application runtimesdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Architecting Multi-Region HA/DR resiliency patternsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Architecture diagramsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. 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,
Authorization Management Service in SAP Cloud Identity Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Automate BTP Custom Domain certificates using Let's Encryptexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Automate your Job Postings Using Generative AI (ChatGPT) & SAP Build Process Automation Appsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
B2B integration factory: How Versuni verified more than 200 EDI interfacesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
B2B message mappingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Banking Sentinel: A Multi-Agent Credit-Risk Copilot on SAP BTP, Built on a Mixed AI Stackexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Beyond Basic AI Error Handling in SAP CPI - A Rules-First Architecture with HANA Cloud Learningexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
BTP Audit Log MCP Server: Security Monitoring with AI Assistantsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
BTP Cloud Foundry MCP Server: Managing CF Environments with AIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Build BTP CAP App with Fiori Integration – Part 2: Implementing End to End Appexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Build real-time event-driven integrations for your enterpriseexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Build your own event-driven scenario with advanced event meshexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Building a CAP App with Fiori Integration – Part 1: Environment & HANA Cloud Setupexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Building a SaaS Multitenant Application Using SAP CAP Framework — Without a Databaseexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Building agentic applications with SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Building an LLM Agent in CAP Java with Spring AIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Building an LLM Agent using CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Building an SAP BTP Agent Architecture from Scratch: Python + CAP + HANAexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Building SaaS Products on SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Cachingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Calling Claude from ABAP: How I Wired SAP AI Core into a Real Business Scenarioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
CAP - Specifying the queues to be consumed from SAP Event Meshexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
CAP multitenancy with Work Zoneexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
CAP on Kyma - Deploy your CAP apps to SAP BTP, Kyma Runtimeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
CAP Service to Fetch + Create Sales Order in S4 HANA Public Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
cf-create-app: Create End-to-End apps and deploy to Cloud Foundry in minutesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Change promotiondescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
CI/CD pipelinesdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Configure an SAP CAP Application to Connect to an SAP HANA Cloud Database in Another Global Account or Subaccountexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Configure Journal Entry Posting Approval from Store Template in Build Process Automationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Configuring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integrationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Connect SAP CAP (Node.js) to On-Premise/Private PostgreSQL using SAP Cloud Connectorexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Connect to Public Cloud API in Node.js via Authorisation Codeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Connecting a Custom MCP Server to Joule Work Desktop: A Seamless and Secure Authentication Flowexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Connecting AI agents to the ABAP RESTful application programming modelexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Consume Remote Services in a Full-Stack CAP Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Workshop,
Consuming data from SAP Datasphere in SAP BTP CAP Applicationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Consumption monitoringdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Conversational search for the Cloud Integration capabilityexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Create a CAP Application with SAP HANA Cloud from Scratch and Deploy to Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Creating a Hybrid CAP (Node.js) Profile with PostgreSQL on BTP from Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Creating a meal generator application with SAP Build, Cloud Application Programming and openAIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Custom Joule Agent for SAP Ariba SLP - Building an AI Agent for Supplier Registration Approvalexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Database connectorsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Deploy a Full-Stack CAP Application in SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Workshop,
Deploy and Run the Incident Management Application in the SAP BTP, Kyma Runtime with a Mock Serverexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Tutorial,
Deploying a CAP Application to SAP Cloud Platform, Kyma runtime & connecting an iOS appexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Deploying CAP services with the in-memory SQLite databaseexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Deploymentdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Deployment and operatordescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Designing a Multi‑Tenant Solutions on SAP BTP – Architecture and Prototype Walkthroughexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Designing Event-Driven Applicationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
DevOps with SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Distributed Resiliency of SAP CAP applications using SAP HANA Cloud (Multi-Zone Replication)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Document Groundingexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Doc,
Don't Wait for SAP: Unlocking MCP Servers in BAS Right Nowexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Dynamic authorisation with user attributes in SAP CAP and AMSexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Dynamic OData from "any" API through SAP BTP Kymaexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Effective from June 30th 2026 - XSUAA Deprecation of GET Method for OAuth Token Retrievalexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Enabling Authorization Policies in SAP Cloud Identity Services - IAS with AMS/CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Enhancing agentic AI with trusted business dataexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Establish a central entry point with SAP Build Work Zoneexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Establish a central inbox with SAP Task Centerexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Evaluating SAP’s new MCP servers: UI5, CAP, and Fiori tools in practiceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Event Driven Architecture with Event Mesh - Part-1explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Event Driven Architecture with Event Mesh – Part-2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Event Driven SAP CAP on Kyma with Agentic AI and UI Auto Refreshexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Event Meshdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Event-driven Extensions for SAP SuccessFactors on SAP BTP – Connecting the Dotsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Event-Driven Multi-Tenant Architecture on SAP BTP with CAP and SAP Event Meshexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Evolving the identity lifecycle for an AI-first futureexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Explore SAP Fiori elements for ABAP developersexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Talk,
Explore version control and automation with GitHub in Cloud Integrationexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Explore your Hyperscaler data with SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Exploring Application Frontend Service: Deploying the UI of an MTA Appexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Exposing Calculation View with Dynamic Client via OData APIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Exposing SAP S4 Onprem data to external System || Odata Service || BTP || Destination-Connectivityexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Extend SAP SuccessFactors on SAP BTP with CAP - Deploy to SAP HANA Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Extend SAP SuccessFactors on SAP BTP with CAP - Import SAP SuccessFactors OData Services definitionsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Extend SAP SuccessFactors on SAP BTP with the SAP Cloud Application Programming Modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Workshop,
Extend Upload Set to Fiori Elements and utilize Document Management Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Extend Upload Set with Table to Fiori Elements and utilize Object Storeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Flexible analytics at speed: Calculation views in SAP Business Data Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
From Concept to action: Hands-On with the CAP Operator and the Partner Reference Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
From R/3 ABAP to CAP/Fiori Elements on SAP BTP- Deploymentexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
From SAP Integration Suite iFlow to MCP Tools: Exposing OData APIs to AI Agentsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
From XSUAA to AMS: Architecting S4HANA CAP Extensions with Policy-Based Authorizationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-3]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-4]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-5]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fullstack CAP Application with HANA Cloud (Decoupled Architecture) [Part-6]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
GenAI Mail Insights - Leveraging the generative AI hub in SAP AI Core to improve customer supportexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Generate agentic workflows using SAP-managed n8n in Joule Studioexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Generating PDF on BTP CF using CAP and Puppeteerexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Generative AI on SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Get Started with an SAP Cloud Application Programming Model Project in SAP Continuous Integration and Deliveryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Tutorial,
Govern AI-supported actions across enterprise systemsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Graph, spatial and document datadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Guide to Process Automation APIs - Part I - Getting Startedexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
HANA AI Toolkit — Local MCP Serverexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Hands on SAP Document AI: Next-generation intelligent document processingexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Hey ABAP Cloud please let me save my data export to Azure Storage please🥺🙏- part 4explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
How I Use AI for Development and Why Context Mattersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
How SAP Document AI brings agentic intelligence to business documentsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
How SAP secures enterprise AI agents with identity propagationexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
How to Approve/Reject Task via API in SAP Build Process Automationexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
How to create an API to run a HANA Cloud Stored Procedure in Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
How to get authenticated user information with CAP in three different ways – Using the XSUAA APIexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
How to use a CAP application to manage DMQ messages on SAP Advanced Event Meshexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
How to use SAP Data Intelligence with SAP Cloud Connectorexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
HTML5.Timeout for CAP destinations in mta.yaml longer than defaultexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Hybrid testing using PostgreSQL on SAP BTP, hyperscaler optionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Implementation of Observability using OpenTelemetry in SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Implementing Dynamic Subaccount-Based Routing in SAP CAP with SAP BTP Destinationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Implementing Event-Driven Architecture in CAP Java using SAP Event Meshexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Insights of Cloud SDK, CAP, XSUAA, SSH and other BTP topics from 2021explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Integrate SAP Business Technology Platform audit logs with IBM Security QRadarexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Integrating a Custom AI Model into SAP CAP Using AI Launchpadexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Integrating and Extending Jouleexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Integrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Integration scenario setupdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Integration Tests in a Cloud Foundry Java App using SAP Cloud Application Programming Modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Intelligent, governed, and agentic integrations with SAP Integration Suiteexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
IPS provisioning to ABAP Cloud Developer Trialexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Knowledge graph and agent memory: Build an agent that remembersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Kyma Evolution: Transforming SAP Kyma into a tailor-made SaaS Platform for sbs extensionsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Kyma Integration with SAP Cloud Logging. Part 1: Introduction and shipping Logsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Kyma Integration with SAP Cloud Logging. Part 2: Let's ship some tracesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Launchpad and site contentdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. 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,
Lets Deep dive into CAPM and HANA Cloud --> HANACapexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Loading a warehousedescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Low-code appsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Making CAP Application Development Easier and Faster with the Help of Storyboard in SAP Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Medallion Reference Architecture for Big Data Processing in SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Mercedes-Benz’s journey to SAP Integration Suiteexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Migrating from Application Logging Service to Cloud Loggingexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Migrating from ASANWEE to ASAAEMEE: From SAP Event Mesh to SAP Advanced Event Meshexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Migrating Your CAP Applications from SAP Web IDE to SAP Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Mobile appsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Model context protocol (MCP) unlocked: Enable governed access to AI agentsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Modern integration at TÜV Rheinland: APIs, events and cloud transformationexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Modernisation and migration to SAP Integration Suite made simpleexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Modernize your database landscape with SAP HANA Cloudexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant MTA: providing a Cloud Portal Service with FIORI apps to subscriber accountsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS Application using CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Multitenant SaaS applications on SAP BTP using CAP - The Reloaded Version!explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS applications on SAP BTP using CAP? SAP BTP, Kyma Runtime!explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS applications on SAP BTP using CAP? Tried-and-True!explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS apps on SAP BTP using CAP? Tried-and-True! – The Advanced Versionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS apps on SAP BTP using CAP? Tried-and-True! – The Basic Versionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Multitenant SaaS apps on SAP BTP using CAP? Tried-and-True! – The Expert Featuresexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Named-User Attribution Across BTP Subaccounts: A Two-Hop IAS Token Exchange for Cloud Integrationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Nice patch SAP! Revisiting your SAP BTP security measures after AI Core vulnerability fixexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
OData entity as a governed query surface for agents, not a toolexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
OpenAPIdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Part 1: Creating and Deploying a SAP CAP Application with SAP HANA on SAP BTP (Cloud Foundry)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Part 2: Runtime Architecture & Cost efficiency gainsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Perform SAP Principal Propagation with Microsoft Entra ID for SAP SuccessFactors!explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Performance Trace Node.js App on BTP with Dynatraceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Platform migrationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Principal Propagation from BTP Web App to S/4HANA via SAP Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Process automationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Product Updates for SAP Build Code – June 2025 Editionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Publish events from CAP Node.js applications to Event Mesh of Integration Suiteexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Quickly Deploy a Sample CAP Application to BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
RFC/BAPIs Meet AI Agents: Why SAP Integration Suite MCP Server Mattersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Roadmap to upgrade from SAP Process Orchestration: Agentic era preparationexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Run and Deploy SAP CAP (Java) with PostgreSQL on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Run and Deploy SAP CAP (Node.js or Java) with PostgreSQL on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SaaS Self-Onboarding and One-Domain Concept in SAP BTP, Kyma Runtime using CAPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP AI Services - DOX - Gen AI with SAP CAP Plugin - Part 3explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP API Management for Beginners – Part 1: What Is APIM & A Complete Features Tourexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP API Management for Beginners – Part 4: OAuth 2.0, KVM, Traffic Policies, Threat Protection&CORSexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BAIP, ABAP environment: Monitoring and troubleshootingexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
SAP BTP - KYMA - SERVICE MESHexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Account Architecture Best Practices: A Practitioner's Field Guideexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Audit Log Access Just Got Easier - Here’s What’s Newexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Audit log Enable and retrieve logsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Destinations in a Nutshell Part 1 - Motivation & NoAuthentication Destinationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Showcase - Use SAP Cloud Application Programming to do Native Development on HANA Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP Showcase – SAP Continuous Integration and Delivery (SAP CI&D) for SAP HANA Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP BTP XSUAA Security Configuration Comparison: Attribute-Based vs. Authority-Based Approachesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Build Process Automation – Use Principal Propagation in Actions sample: CAP Node.js Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Build Process Automationで「グループ宛て承認ワークフロー」を構築するexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Business Technology Platform: Authorization and Trust Management Serviceexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP CAP JWT Token Flow in codeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP CAP Lessons Learned: Run a CAP app using SQLite on SAP BTP - Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Cloud Logging Serviceでコンテナメトリクスを監視するexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Datasphere Integration Patterns: Lessons Learned from Two Years of Implementationsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Document AIexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
SAP IAM integration with SAP Cloud Identity Servicesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
SAP Integration Suite as the foundation for enterprise agentic AIexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
SAP Job Scheduling Service + Cloud Application Programming Model application (CAP) + SAP Authorization and Trust Management Service (XSUAA)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Job Scheduling Service: 🔧 Generate Your Own Client Library from OpenAPI Specexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Joule implementation in an S/4HANA private cloud 3 system landscapeexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP Just Became AI-Agent Ready — Here's a Step-by-Step MCP Walkthroughexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP SuccessFactors extensibility easy with SAP BTP, Kyma runtimeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP's API Policy on AI Agents: What It Prohibits, Allows, and Leaves Openexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SAP’s compositional design system: Craft enterprise UIs with AI on the flyexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Secrets rotationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Secure Service Consumption Across Hyperscalersexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Securing a CAP Node.js App with SAP AMS on BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Securing CAP Applications with SAP Cloud Identity Services and AMSexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Sending Emails from SAP CAP Applications with Any SMTP Providerexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
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,
Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud Servicesexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Setting Up PostgreSQL for SAP BTP Development: A Practical Guideexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SFSFとHANA Cloudを使用するCAPのアプリケーション開発explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Sharing SAP HANA Cloud instance to multiple subaccounts and creating HDI containersexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Simple steps to deploy your CAP project to HANA cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Simplifying SaaS Self-Onboarding Automation using Terraform in Kyma and Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Simplifying SAP BTP Authentication in Pipelines with SAP Passport and Playwrightexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
SQLite as database for a multi-target (/productive) CAP Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Stop guessing, start counting: How generative AI fixed an inventory messexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Streamline User Targeting with Segments in SAP Feature Flagsexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Streamlined Kyma deployment for CAP applicationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Surviving and Thriving with the SAP Cloud Application Programming Model: Deployment to SAP BTP, Kyma runtimeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Surviving and Thriving with the SAP Cloud Application Programming Model: Local development hurdlesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Swagger UI | SAP BTP Extension Generators | Hands-on Video Tutorialsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Testingecosystems revisedThe same concern on the SAP Digital Manufacturing door, opened 2026-10-17: SAP published test automation modules for the product's standard apps.Capability,
Testing SAP Build Process Automation task UI in SAP Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Testing your CAP HANA Artifacts with jest – including multitenancy, hdbprocedure and hdbviewexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
The fastest and easiest way to run full-stack applications in SAP Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
The fastest way to a deployable CAP app on SAP BTP Cloud Foundryexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
The new way to consume Service Bindings on Kyma Runtimeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Third-Party MCP Server Access to SAP Solutions on BTPexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Reference architecture,
Tips for running CAP nodejs in SAP BTPexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Triggering SAP Build Process Automation Processes from SAP Cloud Application Programming (CAP) Appsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
UI for the BTP Application Vulnerability Reportexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Understanding and Developing Fiori Plugins with Extension API & TypeScriptexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
Understanding security approaches in SAP CAP using XSUAA in node.js flavor and MTA.explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Unlock composable business using SAP Integration Suite, advanced event meshexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Talk,
Unlocking Efficiency: Leveraging SAP BTP Document Management Service in Fiori Applications # 2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Use REST services in Graphexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Use SCP CF Destination service in NodeJs locallyexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Useful CAP CDS and Fiori Commands to Accelerate Development and Deploymentexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using Custom Actions to display PDF from SAP BTP Forms service into a CAP SAPUI5 applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using Postman for API Testing with XSUAAexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using RFC Function Modules and BAPIs in SAP Build Process Automationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using SAP managed iFlows for Time series data Integration in SAP IBP – Part 1 - Reading dataexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using SAP managed iFlows for Time series data Integration in SAP IBP – Part 2 - Writing dataexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Using the Terraform Provider for SAP BTP to simplify Subscriber Tenant Onboardingexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Why developers should care about credential-types for xsuaa?explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Why SAP Cloud Identity Matters for SAP Task Center: It’s About Trust and Global User IDexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Blog,
XSUAA Based Authentication - Using Managed Approuterexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
XSUAA Based Authentication - Using Standalone Approuterexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
XSUAA Local Testingexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
从BTP Launchpad里的sapui5应用里调用部署的CPI IFLOWexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Blog,
Fri 16
47 changes
Abinaya Srinivasanadded to the atlasPerson,
aburduhos-logalitechadded to the atlasPerson,
Ajay Sorengadded to the atlasPerson,
Akane Yasutomiadded to the atlasPerson,
Show 43 more
Alex Pfeiladded to the atlasPerson,
Alexander Bundschuhadded to the atlasPerson,
amiramarweniadded to the atlasPerson,
Andreas Thaleradded to the atlasPerson,
ariluluadded to the atlasPerson,
B Raghavendra Raoadded to the atlasPerson,
Boyan Velinovadded to the atlasPerson,
David Slugaadded to the atlasPerson,
David Stockeradded to the atlasPerson,
Didoadded to the atlasPerson,
Dingenhaagadded to the atlasPerson,
f-blassadded to the atlasPerson,
Fabian Fellhaueradded to the atlasPerson,
finnybabuadded to the atlasPerson,
Gayathri Narayanaadded to the atlasPerson,
HP Seitzadded to the atlasPerson,
Ihnen42added to the atlasPerson,
Joerg Meyeradded to the atlasPerson,
Johannes Kratzschadded to the atlasPerson,
Jorge Sousa Villafainaadded to the atlasPerson,
kdassadded to the atlasPerson,
KP Saueradded to the atlasPerson,
Leona Hasaniadded to the atlasPerson,
Līgaadded to the atlasPerson,
Logali Techadded to the atlasPerson,
MarievonSeggernadded to the atlasPerson,
Matthias Bühladded to the atlasPerson,
NiklasHerrmann21added to the atlasPerson,
Nora von Thenenadded to the atlasPerson,
Prashant Gautamadded to the atlasPerson,
Ran Bianadded to the atlasPerson,
Raphaeladded to the atlasPerson,
robbymanisadded to the atlasPerson,
Samuele Barzaghiadded to the atlasPerson,
SAP Tutorialsadded to the atlasPerson,
SAP-MartinNaumannadded to the atlasPerson,
Sarah Erdmannadded to the atlasPerson,
Shrinivasan Neelamegamadded to the atlasPerson,
Sunny kapooradded to the atlasPerson,
T. Griebeadded to the atlasPerson,
timolasiadded to the atlasPerson,
Vinayak Adkoliadded to the atlasPerson,
Vitaliy Rudnytskiyadded to the atlasPerson,
Thu 15
50 changes
@saptools/brunoadded to the atlasRunner for Bruno collections against XSUAA-protected CF appsCLI,
@saptools/cf-debuggeradded to the atlasNode.js inspector tunnel over cf ssh to Cloud Foundry appsCLI,
@saptools/cf-exploreradded to the atlasFile search in apps deployed to SAP BTP Cloud Foundry over cf sshCLI,
@saptools/cf-function-traceadded to the atlasStep-by-step state recorder for one JavaScript function in Node.jsCLI,
Show 46 more
@saptools/cf-hanaadded to the atlasSQL runner against the SAP HANA Cloud database bound to a CF appCLI,
@saptools/cf-inspectoradded to the atlasShell debugger for remote Node.js over the Chrome DevTools ProtocolCLI,
@saptools/cf-live-traceadded to the atlasHTTP trace hook streaming a running CF Node.js app's trafficCLI,
@saptools/cf-logsadded to the atlasLog fetcher and parser for one Cloud Foundry appCLI,
@saptools/cf-metricsadded to the atlasRead-only query tool for metrics in SAP Cloud LoggingCLI,
@saptools/cf-oteladded to the atlasRead-only query tool for OpenTelemetry spans in SAP Cloud LoggingCLI,
@saptools/cf-syncadded to the atlasCloud Foundry topology cache for the other @saptools packagesCLI,
@saptools/cf-tailadded to the atlasMerged log tail of every started app in a Cloud Foundry spaceCLI,
@saptools/cf-xsuaaadded to the atlasOAuth2 token fetcher for a Cloud Foundry app's XSUAA bindingCLI,
@saptools/sqltoolsadded to the atlasSQLTools connection from a Cloud Foundry app's HANA bindingCLI,
cap-reuse-html5added to the atlasFiori elements app in the HTML5 Application Repository with cdm.jsonSample,
Joule Studioadded to the atlasSAP's managed environment for building custom agents and workflowsWeb tool,
Joule Workadded to the atlasSAP's workspace for conversations, Spaces and directing agentsWeb tool,
Mario Ponceadded to the atlasPerson,
@arc-mcp/xsuaa-authprovides[capability:authentication] revisedThe BTP door now compares its authentication options on whether the signed-in identity reaches the next system. The README's sentence about the ./btp entrypoint states it for this package, and it was read again on this date.Package,
@sap/approuterprovides[capability:authentication], requires[0] revisedThe UAA sentence was read again in the 23.0.0 README during this pass and was still there.App,
@sap/joule-studio-clidescription, provides, links revisedCurrent npm README for 2.0.4, published 2026-10-07, says "Installing @sap/joule-studio-cli gives you two commands:" and lists joule and jl. SAP Help now installs this package for the new Studio workflow. The historical alpha package stays separately indexed; no unverified rename or lineage relationship is inferred.CLI,
@saptools/cf-xsuaaprovides[capability:authentication] revisedOn a capability page the edge put a token command line beside an OAuth server and an identity provider with nothing to tell them apart. The edge now says which part of the concern it answers, that it validates nothing, and states the property the BTP door compares on: a token with no user present.CLI,
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,
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,
Agent toolingcore coverage, coverage by flavor, framing by flavor, facets, normative relevance revisedcapire's own guide opens with a caution naming section 2.2.2 of the SAP API Policy and stating that CAP-level agents are not an SAP-endorsed architecture or pathway for exposing, proxying or providing agentic access to SAP Application APIs. That is the core's statement about where this capability may be pointed, so it belongs beside the framing rather than only in the boundary sentence. Recorded as context to inspect, not as a coverage assessment.Capability,
Agent workspacesecosystems revisedAttach Werkbank to the same user-facing concern. Its own catalog lists ARC-1 and ABAP Cloud, CAP Upgrade, and UI5 development skills, while its README describes persistent conversations and Spaces. The additional views record only that scoped attachment; BTP coverage and its assessment date are preserved.Capability,
aicore-skillsprovides revisedcapability:agent-guidance declared the installs_into property on the BTP door, and the README's Installation section names the harnesses in one sentence. The entry's own description already carried the same four; the value puts it where the door's options can be compared on it. Two sentences from the lifecycle skill were read on the same day and added as sources for the edge, since they state how an operation is run and what a mutating script requires.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,
btp-solution-diagram-generatorprovides revisedThe edge said the rules are packaged and not what the package holds, which is the thing that separates this option from the other three skill sets behind the door that carry the same guideline. The README's own list was read on 2026-10-15 and its three lines are now the edge's sources.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,
Cloud Identity Servicesprovides[capability:authentication] revisedThe only sentence about this service was its one-liner, so the capability page listed it beside the OAuth server with nothing to tell the two apart. SAP's trust and federation page states what the service is and what a tenant's own policies cover, and the default identity provider page states the corporate identity provider behind it, which is the property the BTP door now compares on.Service,
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,
drawio-skill-sapprovides, description revisedThe entry carried the one-line install command and not the path the README's own first option uses, which is what a reader on Copilot needs.Skill,
Joule Studioecosystem, artifact type, links revisedThe browser builder and managed runtime do not establish a separately subscribed and bound BTP service. Keep CAP and BTP as served views: the product overview names CAP development, and the current SAP Help tutorial requires "An SAP S/4HANA system configured with an SAP BTP destination." The architecture chapter is titled "Building AI Agents with SAP Joule Studio on SAP BTP" while distinguishing the SAP-managed runtime from Bring Your Own Agent in a customer subaccount. The CLI link is backed by the current npm README, which now ships both joule and jl; its atlas record is revised in the same batch. The positive basis for web-tool is SAP’s description of a visual browser-based builder with no local setup. It identifies the hosted development interface, including provisioned access; it does not classify the runtime as an unbound or customer-hosted service.Web tool,
Joule Workecosystem, artifact type, ecosystem revisedThe three-record acceptance on 2026-10-15 established the workspace as a separate part of SAP Joule. Retain that family split: SAP Joule records the BTP formation and identity integration, while Work records the user-facing experience across systems. RA0029 says "The experience is available across web, desktop and mobile"; there is no separate BTP subscription or binding documented for Work. Its BTP served view describes interaction with customer-managed agents connected to Joule, not a BTP runtime or core-coverage claim.Web tool,
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,
OAuth 2.0 on SAP BTPlifecycle, provides[capability:authentication] revisedThe BTP door now compares its authentication options on whether a token can be had with no person present. The catalogue sentence about the client credentials grant states it for this service, and it was read again on this date.Service,
SAP Authorization and Trust Management serviceprovides[capability:authentication] revisedThe edge said only that the service answers authentication, so the page could not say which part of the concern it answers. SAP's architecture page states the three: the trust, the assertion it receives, and the token it signs. The two properties the BTP door now compares options on are stated from the same page: a token with no user present, and a corporate identity provider behind it.Service,
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-architectureprovides, description revisedThe entry said other agents can run it and not what that costs. The README's own caveat, read on 2026-10-15, is that the auto-load is Claude's alone, which is the difference between this option and a Claude-only one.Skill,
sap-cloud-integration-pipeline-assistantprovides revisedcapability:agent-guidance declared the installs_into property on the BTP door. The README names GitHub Copilot agent mode in its install step and gives a .claude/skills/ path beside it under the heading "For Claude", which names a product family rather than one of the property's values, so only Copilot is entered and the Claude line is kept as a source on the edge.Skill,
SAP-samples/html5-applications-migration-skills-for-sap-btpprovides, description revisedThe entry said the plugin needs no network access, which the README states, and said nothing about the four command lines the same README requires before anything is built or deployed. A reader who stopped at the first half would take the migration for the whole job. The cleanup skill's own sentence, which undeploys from Cloud Foundry, is added as a source on the edge beside it, because the two statements sit in one README and both are true of different steps.Skill,
SAP-samples/joule-a2a-agent-toolkitprovides, description revisedThe entry said the skills generate commands, which the README states of btp-cli, cf-cli and joule-cli, and said nothing about /sap-a2a-agent-toolkit:deploy-agent, which the Quick Start uses to deploy the scaffolded agent. The distinction decides whether anything here reaches an account, so it is now on the entry, and the README's own cf login and joule login step is named in the warning where the account conditions already were.Skill,
SAP/automation-pilot-agent-skillsprovides, description revisedThe README read on 2026-10-15 lists curl and jq in the same prerequisites table as Claude Code, for the API calls and the JSON parsing, and the entry named neither. The two API sentences read the same day are added as sources on the edge, since what the skills do through the Content Management and Executions APIs was described in the entry without a quote behind it.Skill,
SAP/leanix-ai-pluginsprovides, requires revisedThe edge rested on one phrase, "designed to work with the LeanIX MCP Server", which says the skills are written for it but not that a reader has to do anything. The sentence read on 2026-10-15 states the connection and the sign-in flow, which is what makes the requirement concrete.Skill,
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,
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,
Testingcoverage by ecosystem revisedIntake of @saptools/bruno, which runs request collections against services deployed to Cloud Foundry: the concern exists behind the BTP door.Capability,
Wed 14
4 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,
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,
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,
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,
Mon 12
19 changes
Ashutosh Kumar Singhadded to the atlasPerson,
azhariqbaladded to the atlasPerson,
BirgitSadded to the atlasPerson,
claudiacsrosalinoadded to the atlasPerson,
Show 15 more
Daniil Bolobonovadded to the atlasPerson,
Héctor Enríquezadded to the atlasPerson,
Manisha Debnathadded to the atlasPerson,
Nacho Muñoz Álvarezadded to the atlasPerson,
Palakadded to the atlasPerson,
Piyush_003added to the atlasPerson,
prajnaparmitaadded to the atlasPerson,
rupamaityadded to the atlasPerson,
SaranyaSampathadded to the atlasPerson,
Shilpa Vijadded to the atlasPerson,
Siddhartha Routhadded to the atlasPerson,
Udo Paltzeradded to the atlasPerson,
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,
API Managementprovides[mcp-servers], provides, description revisedIndependent source review supports prompts guiding agent interaction rather than templates; retains both sourced tool-count limits as an explicit MCP-specific discrepancy.Service,
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,
Sun 11
2 changes
calmcpadded to the atlasMCP server with read tools over the SAP Cloud ALM APIsMCP server,
calmcpentry revisedThe repository was handed over directly. Written from the README, the repository's own record and the product page at consetto.com. Filed on the BTP door because Cloud ALM has no door of its own and the server deploys to Cloud Foundry, binds XSUAA and resolves a destination there, the same strain recorded on cloud-alm-itsm-mcp. origin_ring is independent because the product page states it: "calmcp is an independent open-source project."MCP server,
Fri 9
41 changes
sap-cloud-integration-pipeline-assistantadded to the atlasAgent skill for the Pipeline Concept in SAP Cloud IntegrationSkill,
sap-cx-developer-companionadded to the atlasAgent skill for SAP Customer Experience APIs, CDS and errorsSkill,
sap-mdk-appsadded to the atlasAgent skill for Mobile Development Kit projectsSkill,
@mariodefe/sap-datasphere-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,
Show 37 more
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,
AI Core 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,
AI-native North Star architecture — Platform Layerparts revisedFilled from SAP's own pages at the maintainer's request (docs/concepts/product-doors.md was the occasion; the AI-native door reads these designs). Every part names what the graph holds; what it lacks is listed as candidates in the curation note.Reference architecture,
aicore-skillsdescription revisedThe SAP AI Skills Library registry snapshot of 2026-10-09 lists a fourth skill under plugins/aicore-skills, genai-hub-tabular-orchestration, and plugin.json names four skill directories where the entry of 2026-09-25 described three. Read from that skill's own SKILL.md and plugin.json: the Context Registry layers, the sap-rpt tabular prediction models and the BTP command line it wants for HDL access are added, and the sentence about the DO NOT USE FOR clauses is corrected, because the new skill sends what it declines to genai-hub-orchestration, which plugin.json does not list.Skill,
BTP CF 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,
BTP 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,
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,
CI 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,
cloud-alm-itsm-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,
CostingGeek/sap-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,
cpi-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,
drawio-skill-sapentry 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 LICENSE and the skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. It is a fourth independent BTP diagram skill beside marianfoo-btp-drawio-skill, lemaiwo-btp-drawio-skill and miyasuta-claude-drawio-btp-diagram, and GitHub reports it as not a fork of any of them.Skill,
Generative AI on SAP BTPparts, roles, paths revisedThe readme names the place for plugins and SDKs by example and leaves it open, and the RAG page names SAP's standardized services or a custom-built approach as the choice (docs/concepts/design-roles-and-interfaces.md §3). The three scenario pages are overlapping flows over the same parts, so they are not ways; the two runtimes are.Reference architecture,
hana-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,
Integrating and Extending Jouleparts revisedFilled from SAP's own readmes at the maintainer's request; the AI-native door reads these designs. Every part names what the graph holds; what it lacks is listed as candidates in the curation note.Reference architecture,
MCP Server for SAP BTP Administrationprovides 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,
mcp-integration-suiteprovides 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,
mcp-is-tpmprovides 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,
mcp-sap-cpiprovides 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,
mcp-sap-datasphere-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,
mcp-sap-focusedrunprovides 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,
odata-mcp-proxyprovides 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 LeanIX 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,
sap_analytics_cloud_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-bdc-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-bdc-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,
sap-cloud-integration-pipeline-assistantentry revisedA new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cloud-integration-pipeline-assistant; the repository documents the same skill under .github/skills/ and .claude/skills/, which is where a reader copies it from. Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Skill,
sap-cx-developer-companionentry revisedA new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cx-developer-companion. Written from the repository's own README and SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the SAP Commerce door because the CX API explorer and the error resolver are written against Commerce Cloud OCC and Sales and Service Cloud, with CAP and BTP as served doors for the CDS half.Skill,
sap-mdk-appsentry revisedA repository new to the SAP AI Skills Library registry snapshot of 2026-10-09, with no prior processed record in the collection cache, registering one skill at skills/sap-mdk-apps. Written from the repository's README and that skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the BTP door, where the atlas already holds @sap/mdk-tools and @sap/mdk-mcp-server.Skill,
sap-pi-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,
sap-tutorials-contententry 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. One of the three skills the repository registers: the other two name no SAP stack and stay out. Written from the skill's own SKILL.md and GitHub's record for the repository and the sap-tutorials organisation, which GitHub marks verified with the email sapdocs@sap.com and the tutorial navigator as its site. 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,
Thu 8
4 changes
auth-transportadded to the atlasUI5 app and CAP service copying role collections between subaccountsApp,
auth-transport2added to the atlasMTA projects sharing a role collection across role templatesSample,
btp-ui5-show-userinfoadded to the atlasUI5 app reading the signed-in user via launchpad and approuterSample,
btp-user-role-requestadded to the atlasFiles for two Japanese posts on BTP user registration with SAP BuildSample,
Tue 6
1 change
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
1 change
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,
Thu 1
32 changes
sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP systemMCP server,
ADITYAfirst recorded in the atlasPerson,
Alexander Riederfirst recorded in the atlasPerson,
Andrefirst recorded in the atlasPerson,
Show 28 more
Andre Dossingerfirst recorded in the atlasPerson,
Anna Wengerfirst recorded in the atlasPerson,
Armin Kramerfirst recorded in the atlasPerson,
Christian Volkfirst recorded in the atlasPerson,
Daniel Kuntzefirst recorded in the atlasPerson,
Gurkan Yilmazadded to the atlasPerson,
Heiko Kiesslingfirst recorded in the atlasPerson,
ilyabelozerovsapfirst recorded in the atlasPerson,
Jens Maurerfirst recorded in the atlasPerson,
Johannes Ottfirst recorded in the atlasPerson,
Marcfirst recorded in the atlasPerson,
Martin Frickfirst recorded in the atlasPerson,
Nidhi Murkutefirst recorded in the atlasPerson,
PRAJIN OLLEKKATT PRAKASANfirst recorded in the atlasPerson,
ravi-ydvfirst recorded in the atlasPerson,
Rui Nogueirafirst recorded in the atlasPerson,
rui8472first recorded in the atlasPerson,
sachin prajapatfirst recorded in the atlasPerson,
Sangeetha Jayakumarfirst recorded in the atlasPerson,
SAP Archivefirst recorded in the atlasPerson,
Sarthak Goyalfirst recorded in the atlasPerson,
sdischer-sapfirst recorded in the atlasPerson,
Thanh Phong Lamfirst recorded in the atlasPerson,
TieyanFufirst recorded in the atlasPerson,
Vipin Menonfirst recorded in the atlasPerson,
Vipin Nairfirst recorded in the atlasPerson,
vtopalova23first recorded in the atlasPerson,
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,

Tue 29
5 changes
sap-fiori-iosadded to the atlasAgent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUISkill,
sap-knowledge-pipelineadded to the atlasPython library turning OData or HANA records into chunked documentsPackage,
Yassin Bahriadded to the atlasPerson,
sap-fiori-iosentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact because the registry keeps other people's code in their own repositories. This skill is SAP's own code in that repository, so it is entered from its SKILL.md, README and references directory, as plugins/aicore-skills was on 2026-09-25. The BTP door is where the atlas answers native iOS work (capability:mobile-apps names the SAP BTP SDK for iOS), and capability:agent-guidance exists on that door. Hard rule 7: skills are indexed, never authored here.Skill,
Show 1 more
sap-knowledge-pipelineentry revisedHanded over as a URL. Filed behind the BTP door because what it reads is an SAP OData service and SAP HANA, and neither the library nor its recipes touch CAP, UI5 or ABAP; the repository's own topics are rag, rag-pipeline, sap, sap-btp and sap-hana. One edge, retrieval-augmented generation: the capability's CAP coverage says the layer above the vector, splitting long text into chunks and deciding what goes into the prompt, is hand-written in every entry there, and that layer is what this library is. Data import and export was considered and left off, since that capability is about a file somebody supplies rather than records read out of a live service, and OData is about serving a model as OData rather than consuming one. The optional SAP hdbcli driver is named in the prose and carries no edge: SAP's Node.js driver is the artifact @sap/hana-client, so its Python sibling belongs in the graph the same way and not as an external, which is an editorial decision rather than one for this batch.Package,
Mon 28
5 changes
ARC-DRAWadded to the atlasMCP server drawing BTP solution diagrams on a draw.io canvasMCP server,
Emerson Tosinadded to the atlasPerson,
Lize Caifirst recorded in the atlasPerson,
ARC-DRAWdescription revisedThe README declares the status early (v0.x), installation from source and testing with Claude Code alone, and the entry carried none of it. The maturity label is the maintainer's own, dated here, and the live-canvas requirement is what separates this option from the ones that write a file.MCP server,
Show 1 more
Architecture diagramscore coverage, facets revisedEvery provider edge on this capability was re-read against its own documentation in this pass.Capability,
Sun 27
36 changes
API Compositionadded to the atlasBusiness data graph queried with OData V4 or GraphQLService,
btp-setup-automatoradded to the atlasContainerised script setting up an SAP BTP account from JSON configCLI,
Terraform Provider for SAP BTPadded to the atlasTerraform and OpenTofu provider for SAP BTP global accountsPackage,
Agent toolingcore 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,
Show 32 more
API Compositionentry revisedAn impact assessment of CostingGeek/sap-mcp found the API the whole entry rests on had no node: the prose named SAP Graph and nothing pointed at it. Written from SAP's own API Composition documentation in SAP-docs/btp-integration-suite, pinned at commit 33f3395. No provides edge yet — the capabilities the atlas holds for serving OData and GraphQL are scoped to the CAP and ABAP doors and describe serving your own model, which is a different concern from composing several systems' APIs; whether this answers an existing capability or needs one is an editorial call.Service,
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,
Audit loggingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
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,
BTP MCP Serverprovides revisedThe README lists create, update and delete on subaccounts and directories and entitlement assignment; the only edge was to the MCP-server capability, so the account-provisioning page did not list it.MCP server,
CI/CD pipelinesecosystems revisedThe capire audit of 2026-09-27 proposed CI/CD as a CAP concern and found this capability already on the BTP door, where the service is. capire's Deploy using CI/CD Pipelines guide is the CAP door's own answer, cds add github-actions and the service's ready-made CAP pipeline; three content entries about CAP pipelines had been filed under deployment for want of the door. Added by the maintainer's decision.Capability,
Cloud Integrationprovides[integration-flows] revisedThe option states the protocols its adapters speak, one sentence per value, from SAP Help's introduction page: its transport-channel sentence and its adapter table, which names each of the others one adapter at a time (docs/concepts/design-roles-and-interfaces.md, P2). JMS is an adapter name there and no sentence names it as a protocol, so it stays out.Service,
CostingGeek/sap-mcpdescription, connects, type properties revisedRead from the README and from saptools.py, which were the entry's sources from the start and state all three: the Claude Desktop config launches it from a local directory, the server runs on stdio, and the key travels in an apikey header. tool_count is left out — the README enumerates one tool and states no number, and the field rests on a stated count elsewhere in the corpus.MCP server,
Data federationfacets, core coverage, name revisedThe concern this node holds is what capire calls data federation: making data that lives in another system available as if it were local, by federating the query, by copying the rows, or by caching what was read. Replication is one of the three strategies, and the facets declared on 2026-09-27 compare the options on exactly that axis, so a node named after one strategy read as if the other two were elsewhere. The id stays, as the 2026-09-13 rename kept it: it is the stable ref every record, edge and link carries. BTP keeps its own framing name, Master data integration. Proposed by the capire audit of 2026-09-27; decided by the maintainer.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,
Deploymentcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
Designing Event-Driven Applicationsparts, areas, edges, explains revisedThe record states what its source draws around and between the parts (docs/concepts/reference-architectures.md §9.2): SAP cloud applications, SAP BTP and the third-party landscape as areas, the extension application the readme's flow names, and the event flow from an SAP cloud application to the hub and from a third-party broker over the bridge to SAP's event services. The checker's reading of the first draft: the bridge's SAP end now rests on the two sentences that name advanced event mesh and the Event Mesh capability as SAP's event brokers; SAP BTP is a zone of SAP's cloud, since the readme names no subaccount, and the two capabilities stand beside Integration Suite rather than within it; and the piece no longer explains async-processing, which is in-process work its own summary sets aside.Reference architecture,
Destinationscore coverage revisedP1 backfill 2026-09-27: the paragraph shared no page with the runtime edge because it had no page at all. capire documents the connectivity component under Outbound Authentication; the paragraph now rests on it and on the pages the edge cites.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,
Integration flowsfacets 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,
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,
MCP Server for SAP BTP Administrationprovides revisedSAP's page says the server manages the BTP account structure, which is what account provisioning is; the only edge was to the MCP-server capability, so the account-provisioning page did not list it.MCP server,
Multitenancycore coverage revisedP1 backfill 2026-09-27: the paragraph and the runtime edge now rest on a page in common.Capability,
Multitenant SaaS Application using CAPparts, areas, edges revisedThe record states what its source draws around and between the parts (docs/concepts/reference-architectures.md §9.2): the provider and consumer subaccounts, the users and API clients, and the flow of subscription, data and authentication as the architecture page states it. On the checker's reading of the first draft: only the application is placed in the provider subaccount, since the page places nothing else there; the registration with the SaaS Provisioning service is the stated direction, not events the service raises; and API Management's policies are stated with no path, so no arrow.Reference architecture,
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,
SAP Cloud Management Service for SAP BTPinterfaces revisedSAP's page on account administration through this service's APIs names the four and says they are included in the core services for SAP BTP; the hub's catalogue states each one's title, version and state (docs/concepts/design-roles-and-interfaces.md §3.2, P7). What an application reaches this service over is then a named surface with a page. No status is entered: the hub's state is a crawled claim reported beside the interface.Service,
SAP Document AIinterfaces revisedAn interface may be named and stays a field (docs/concepts/design-roles-and-interfaces.md §3.2, P7): the hub's catalogue states the two APIs' titles, versions and states, and SAP's Help pages name the channels and the workspace, so a design's arrow can say which surface it lands on and a reader has the page to open. The inbound channels read mail: SAP's Help page names mail as the only channel type, so the SharePoint folders the reference architecture mentions are its claim and not the maker's. No status is entered: the hub's state is a crawled claim reported beside the interface.Service,
SAP Document AIparts, areas, edges, roles, edges[client to docai] revisedThe ingestion page links the upload operation of document_information_extraction_api_v2 as the API-based integration, and the service now names that surface (docs/concepts/design-roles-and-interfaces.md §3.2, P7), so the arrow says which API it lands on and wears its protocol.Reference architecture,
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,
Testingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
The last 30 days. Older changes stay in each entry's history.
AtomJSON