NewSAP Business Technology Platform, also named SAP Business AI Platform
In the last 90 days
371 changes
SAP Health Data Services for FHIRadded to the atlasHL7 FHIR implementation for storing and exchanging health data
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).
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).
Configure an MCP Server Created from an HTTP EndpointpublishedDocuments configuring API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btp’s HTTP-source MCP server tools, resources, prompts and policies. Resources are selected from GET operations and have URI templates/content types; prompts define User/Assistant messages with optional arguments, alongside MCP policy configuration.
Agentic CAP: Build MCP servers and enterprise AI agentspublishedCAP applications become AI agents over the Model Context Protocol and the Agent2Agent protocol, which is the serve your application over MCPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design concern, and SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp is the LLM integrationLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.SAP and community, narrow by design through which AI is embedded in a CAP app, with recommendations from the SAP-RPT-1 model as the abstract's example. The abstract names the two protocols and the one model and does not say which packages carry them. A two-hour TechEd 2026 session in a hands-on room (Tuesday 27 October, Berlin), presented by Daniel HutzelDaniel Hutzelgave 3 talks, contributed to 32 entriessap official, Daniel SchlachterDaniel Schlachtercreated 9 pieces, contributed to 10 entriessap official, Marc Huber and Sami Lechner, written here from SAP's abstract; the recording is not yet published.
Show 4 more
Model Context Protocol (MCP)publishedFrames the Model Context Protocol as the answer to an M-times-N integration problem: one shared protocol turns M agents and N tools into M plus N connections, and one server can be called by any compliant agent. On SAP BTP its implementation section lists an SAP MCP Hub as a no-code way to expose enterprise tools, SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp's MCP Gateway as what it calls the governed path for exposing SAP and non-SAP APIs as MCP-compliant tools, custom SDK-based servers, SAP's MCP servers for development, and an MCP adapter for CDS as a CAP plugin marked coming soon. That is the ground MCP serversServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design covers; for security it points at a separate page.
Turn SAP APIs into MCP Tools for AI Agents using SAP Integration Suite Free TrialpublishedWalks through building an MCP serverServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design on SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp's free trial from an existing API artifact — the Business Partner API against a public S/4HANA Cloud sandbox — rather than from an HTTP endpoint with an OpenAPI specification or from RFC-enabled function modules, the creation wizard's other two source types, left unexplained here. Covers the API artifact's Content Modifier policy that injects the Business Accelerator Hub API key before the backend call, and the "Trust Upstream MCP Authorization" setting that lets the MCP server delegate authorization checks to that source API instead of duplicating them. Ends by fetching an OAuth token from a Process Integration Runtime service key and pointing an MCP client at the deployed server over streamable HTTP.
MCP Server — SAP Integration SuitepublishedSAP's own page for the MCP Server artifact in SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp, and where the gateway that runs it is described: MCP clients and API clients reach the same backends through two gateways that share security, traffic management and multi-protocol connectivity. Sets out the three primitives a server may expose — tools derived from API operations with an input and output schema, resources addressed by URI for context rather than action, and prompts as reusable interaction patterns. Says availability depends on the Integration Suite service plan, and points at the three creation paths as separate pages.
HANA AI Toolkit — Local MCP ServerpublishedAn MCP server that turns the hana-ml Python library into governed tools an agent can call against a HANA Cloud instance, shipped in the hana-ai toolkit and exposed over stdio, SSE and streamable HTTP. Its one firm rule is attributable execution: an audit module writes the MCP-side identity — agent, model, session, tool, redacted arguments — into the HANA connection before any SQL runs, and fails the call if that write fails. A worked example of governance on an MCP tool surface, from SAP's data side rather than CAP's.
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.
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.
SAP Analytics Cloudadded to the atlasSaaS for business intelligence, planning and predictive analytics
SAP Datasphereadded to the atlasCloud data warehouse with spaces, views and analytic models
Show 2 more
SAP Analytics Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.
SAP Datasphereentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: the data and analytics capabilities are on the BTP door only, so on CAP this was counted behind the door and grouped under nothing. A CAP service reaches it through a destination, which is the BTP door's concern.
SAP Document Management service, application optionadded to the atlasReady-to-use web application for enterprise content
SAP Document Management service, integration optionserves ecosystems revisedAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.
SAP Document Management service, integration optionadded to the atlasAPIs and a UI5 component for document management in apps
Redis on SAP BTP, hyperscaler optionadded to the atlasManaged Redis from the hyperscaler via a BTP service binding
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.
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).
Explore your Hyperscaler data with SAP Business Data CloudpublishedSAP's map of the ways data held on hyperscaler and partner platforms is joined with SAP data in SAP Business Data CloudSAP Business Data CloudSAP's umbrella over the data estate: installed intelligent content and data products, a governed catalog they are published through, and a path out to SAP Databricks.sap official, btp, with a sub-page each for AWS, Azure, Google Cloud, DatabricksDatabricksA unified data and AI platform. sap-bdc-mcp-server creates the Delta shares it registers with SAP Business Data Cloud in a Databricks workspace. and Snowflake. It sets four modes side by side: BDC Connect shares data products in both directions over the Delta Sharing protocol from the object store layer, while in the SAP DatasphereSAP DatasphereSAP's cloud data warehouse: spaces, modelled views and analytic models over data brought in or federated from source systems, with the business context carried along rather than rebuilt.sap official, btp layer federation reads remote tables in place, Replication Flows copy SAP data out to stores such as Amazon S3 or Google BigQuery, and Data Flows import files and transform them into Datasphere tables, the last three being the ground loading a warehouseLoading a warehouseGetting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from replication, which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.SAP and community, unassessed covers. The Snowflake and BigQuery connectors are dated to 2026 releases, and a closing page lists what slows federation, from source and tenant in different regions to queries that do not filter and aggregate at the source.
Transforming Enterprise Data Strategy with SAP Business Data CloudpublishedSAP's layered picture of SAP Business Data CloudSAP Business Data CloudSAP's umbrella over the data estate: installed intelligent content and data products, a governed catalog they are published through, and a path out to SAP Databricks.sap official, btp, from lake storage and compute up to a knowledge core and agents, with eight sub-pages that each work one part through. The data products page is the cataloguing and lineageCataloguing and lineageFinding what data exists across the estate and what it promises — catalogs and data products, the contract a consumer can rely on, where a field came from, and what a column actually contains once you profile it. The question asked before modelling starts and again when somebody asks where a number came from.SAP and community, unassessed part: datasets described by Open Resource Discovery metadata, listed in the BDC catalog and shared over Delta Sharing to SAP Databricks and SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp, with SAP DatasphereSAP DatasphereSAP's cloud data warehouse: spaces, modelled views and analytic models over data brought in or federated from source systems, with the business context carried along rather than rebuilt.sap official, btp as a consumer on the intelligent content page; other pages install intelligent content, bring SAP BW data in through the Data Product Generator, provision groups by SCIM from Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp into SAP Databricks, which is identity provisioningIdentity provisioningGetting users, groups and role assignments into every system that needs them, and out again when a person leaves, through provisioning jobs or SCIM APIs. Authentication answers who is calling one request; provisioning decides whether the user exists in that system at all.SAP only, and train predictive modelsPredictive modelsTraining, deploying and calling a model that predicts a value from tabular business data: a classification, a regression, a forecast. Distinct from LLM integration, where a language model generates text, even where both run on the same service.SAP only in SAP Databricks that SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp then serves for batch and real-time scoring. The main page states direction more than mechanism, and the BW page marks SQL Share for derived and OData for analytical data products as to be available.
Show 2 more
SAP Business Data Cloudadded to the atlasData products, a governed catalog and a path to SAP Databricks
SAP Business Data Cloudentry revisedEntered so the data and analytics capabilities have SAP's answer as an artifact rather than as a paragraph with a citation — the asymmetry every one of those three coverage notes admitted to. Written from SAP Help, read today, which is what the checked date means.
SAP Master Data Integrationadded to the atlasCloud service replicating master data across a hybrid landscape
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.
SAP-samples/hana-developer-cli-tool-exampleadded to the atlasDeveloper-centric command line for SAP HANA
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.
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).
hdbadded to the atlasPure JavaScript SAP HANA driver for Node.js
SAP HANAadded to the atlasSAP's relational database platform, on-premise and in HANA Cloud
Show 10 more
Medallion Reference Architecture for Big Data Processing in SAP HANA CloudpublishedSAP's medallion layout for SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp: structured, semi-structured and unstructured data lands raw in HANA Cloud, data lake files as the bronze layer, is cleansed into a common structure in silver, held in data lake files or the HANA database, and is curated and read-optimised in gold, from where it can also be exposed as a Delta Share. The staged path from raw to consumable is the ground loading a warehouseLoading a warehouseGetting data into an analytical store and keeping it current — connections to source systems, replication and the other integration tasks, import jobs and their lifecycle, and the monitoring that tells you a load failed before a report does. Distinct from replication, which is an application reading data that lives elsewhere as if it were local rather than a warehouse being filled.SAP and community, unassessed covers, with Spark jobs and SAP DatasphereSAP DatasphereSAP's cloud data warehouse: spaces, modelled views and analytic models over data brought in or federated from source systems, with the business context carried along rather than rebuilt.sap official, btp data flows named as ways to move data between layers and SAP Analytics CloudSAP Analytics CloudSAP's SaaS front end for analytics: business intelligence, planning and predictive in one product, and the place a Datasphere analytic model is meant to end up being read.sap official, btp among the consumers of gold. It leaves the ingestion method open, to be chosen by source, freshness and performance, and names no pipeline or schedule beyond that.
SAP ASE Serviceadded to the atlasManaged SAP ASE databases on BTP for Java applications
SAP HANA Service (SAP Regions) for SAP BTPadded to the atlasManaged SAP HANA 2.0 databases in fixed sizes on SAP BTP
SAP-samples/hana-hdbext-promisfied-exampleadded to the atlasPromise-based wrappers around the SAP HANA client libraries
SAP HANA Cloudprovides revisedRAG on CDS reads that HANA Cloud supplies the vector column and the similarity function, and the capability opened to the BTP door on 2026-09-14, yet the service carried no edge to it; the store the CAP-door pipelines write into is now an option on the capability.
SAP HANA Cloudadded to the atlasManaged SAP HANA database service on BTP
PostgreSQL on SAP BTP, hyperscaler optionprovides revisedEntered with a delivers edge and no provides, so it was behind the BTP door with nothing to group under. database-connectors gained the BTP door the same day.
SAP HANA Cloudentry, serves ecosystems revisedAdded by me the day it was entered, and it did not hold: an ABAP developer does not choose the database — S/4 runs on HANA — so database-connectors is not a decision made on the ABAP door.
PostgreSQL on SAP BTP, hyperscaler optionadded to the atlasManaged PostgreSQL from the hyperscaler via a BTP service binding
@sap/hana-clientadded to the atlasSAP's Node.js driver for SAP HANA
SAP HANA Cloud as an Esri GeodatabasepublishedSAP's design for running an Esri ArcGIS Enterprise geodatabase inside SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp, so that geometries and SAP business data sit in one database and are joined in a HANA calculation view, which is the spatial part of graph, spatial and document dataGraph, spatial and document dataStoring and querying data that is not plain rows, such as a network of relationships, a geometry or a JSON document, in the database that already holds the rows instead of in a separate store per model. Free-text search over entities is search; similarity over embeddings is retrieval-augmented generation.SAP only. It traces three personas: an analyst in ArcGIS Pro building query layers over that view, a developer whose CAP@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap application models spatial types such as ST_Point in CDS, and an analyst using a Fiori app on top of such an application. The deployment advice stops at placement: ArcGIS Server and HANA Cloud go in the same region and availability zone, because Esri's certified architectures allow under 5 milliseconds of network latency between them.
dbt-sap-hana-cloudadded to the atlasdbt adapter targeting SAP HANA Cloud as its warehouse
SAP Data Quality Management, microservices for location dataadded to the atlasAPIs for address cleansing, geocoding and suggestions
SAP HANA Spatial Services for SAP BTPadded to the atlasAPIs for geocoding, map tiles and routing
Object Store on SAP BTPprovides revisedPlace the service under its direct job of object storage. CAP attachment integration remains represented by existing dependency edges from the attachment plugins.
Object Store on SAP BTPadded to the atlasBinding onto hyperscaler object storage, chosen by plan
Integration Advisoradded to the atlasB2B interface and mapping specification in Integration Suite
SAP Private Link Servicerequires revisedSAP's Discovery Center lists the runtime as a required service of the plan, and npm run check:catalogue listed the relation with no edge. Basis entitlement: the catalogue says a plan cannot be bought without it, which is commercial and is not drawn as a runtime dependency (vocab PERSPECTIVES, 2026-09-22).
SAP Private Link Serviceadded to the atlasPrivate network link between a BTP service and a partner cloud
btp-cloud-connector-setup-automationadded to the atlasYeoman generator for Cloud Connector mappings and BTP destinations
SAP Destination serviceserves ecosystems revisedThe destination is resolved by the router or the service, not by UI5 code, so the decision is made on the CAP and BTP doors.
Show 1 more
SAP Destination serviceadded to the atlasNamed, credentialed addresses of other systems resolved at runtime
SAP Forms Service by Adobeadded to the atlasAdobe Document Services on BTP for print and interactive PDFs
SAP Print serviceadded to the atlasPrint queues between cloud applications and local printers
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).
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.
SAP Integration Suite, Event Meshadded to the atlasEvent broker inside SAP Integration Suite
SAP Integration Suite, advanced event meshpart of, connects revisedThe use case for receiving Kafka messages lists the Kafka bridge as a documented contribution, and the graph held no edge from the broker to Kafka, so a generated diagram could not draw the path. From SAP's Kafka bridging pages; no protocol is entered because neither page names one.
Show 4 more
SAP Cloud Application Event Hubadded to the atlasDistributes business events between SAP cloud applications
SAP Integration Suite, advanced event meshadded to the atlasEvent streaming and management platform in Integration Suite
Event Meshadded to the atlasManaged queues and topics over AMQP, MQTT and REST
Designing Event-Driven ApplicationspublishedSAP's guidance for building applications on event-driven architecture with BTP services. It sets out a two-part strategy: SAP Cloud Application Event HubSAP Cloud Application Event HubDistributes the business events SAP cloud applications publish to the other SAP cloud applications in a landscape, with subscriptions managed in its own UI and no topics or queues to configure.sap official, btp for events between SAP cloud applications and BTP, and the SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp family for dedicated event brokers in hybrid landscapes. Its sub-pages then cover EDA patterns, design considerations and AWS and Azure IoT integration. The framing is integration between systems; the in-process outbox and queueing inside one CAP service are not its subject.
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.
Cloud Integrationadded to the atlasBuilds and runs integration flows between cloud and on premise
Cloud Integrationconnects revisedThe use case for receiving Kafka messages lists the Kafka sender adapter as a documented contribution, and the graph held no edge from Cloud Integration to Kafka. From SAP's adapter pages, which name the Kafka protocol and, in the adapter's General tab, TCP as its transport.
Application to Application IntegrationpublishedSAP's reference architecture for application-to-application integration, where messages carrying transactional data such as sales orders pass between business applications in near real time and each one triggers the next process step. When the sender's and receiver's APIs do not match, Cloud Integration in SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp sits between them to determine receivers, filter, map structures and convert protocols, which is the ground of integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only; SAP Connectivity serviceSAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp, Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp and SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp reach on-premise receivers, and the edge integration cell runtime keeps processing inside a customer-managed landscape where compliance requires it. Direct exchange without middleware is allowed when the two APIs already align, asynchronous communication is the default the page states, and it is drawn at the level of the pattern, following SAP's Integration Solution Advisory Methodology, without designing any one flow.
Show 4 more
Business to Business IntegrationpublishedSAP's reference architecture for business-to-business integration, the exchange of business documents with customers, suppliers and other trading partners over agreed standards such as EDIFACT, ANSI X.12 and IDoc and protocols such as AS2. Its design-time steps are Cloud Integration in SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp, the predefined content of SAP Business Accelerator Hub, and Integration Advisor, which defines message implementation and mapping guidelines and generates runtime artifacts from them; Trading Partner Management then turns partner profiles into agreements pushed to the Partner Directory, and generic integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only on Cloud Integration read those agreements at runtime to exchange messages with each partner. The alternatives it names are API-based exchange where an industry has standardised its APIs, and SAP Business Network with the managed gateway for spend management in place of connecting partners one by one.
Connect Business Processes with SAP Master Data IntegrationpublishedSAP's reference architecture for keeping master data such as materials, business partners and cost centres consistent across applications with SAP Master Data Integration, a central hub that stores every change in an event log and distributes it to the solutions that consume it. Cloud Integration in SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp carries what the hub does not reach, SAP solutions it does not yet support and third-party or on-premise systems, through an SAP Master Data Integration adapter, which is where the design meets integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only; newer SAP S/4HANA releases connect to the hub without it. Consolidation, data quality and central governance are outside the architecture and left to SAP Master Data Governance, and SAP Master Data Integration itself has no entry in the atlas yet.
Edge Integration Cell on HyperscalerspublishedSAP's architecture for Edge Integration Cell, the runtime of SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp that executes integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only in a Kubernetes cluster the customer runs, while design, monitoring and governance stay on SAP BTP and the runtime reaches BTP over outbound-only channels. The main page gives the reasons SAP names for it: data residency, security policies that forbid inbound access, and latency to a distant BTP region. Three sub-pages draw the same setup on AWS, Azure and Google Cloud, each with a private network across three availability zones, a managed Kubernetes cluster, managed PostgreSQLPostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. and RedisRedisAn in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one., sizing left to an SAP Note, and each says it outlines a small production deployment to be treated as a starting point.
integration-suite-partner-directory-accelerator-for-pipeline-conceptadded to the atlasJava Swing tool maintaining Partner Directory entries for the Pipeline
Cloud Integration Automationadded to the atlasGuided workflow for configuring SAP cloud solution integration
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.
Cloud Connectorconnects revisedThe Connectivity service required the Cloud Connector, and nothing said which of the two opens the connection. SAP's documentation does: the connector registers with the service.
Cloud Connectoradded to the atlasSAP's on-premises agent linking SAP BTP to customer-network systems
SAP Connectivity servicerequires revisedThe Cloud Connector entered in intake-20260915-cloud-connector; the service's description already named it in plain words.
Show 2 more
SAP Connectivity serviceserves ecosystems revisedIt provides RFC connectivity, a CAP-side concern; a UI5 frontend reaches a backend through its router, not through the Connectivity service.
SAP Connectivity serviceadded to the atlasProxy from cloud apps to on-premise systems via Cloud Connector
Open Connectorsadded to the atlasPrebuilt connectors to non-SAP cloud applications as REST APIs
Trading Partner Managementadded to the atlasPartner profiles and agreements for B2B exchange in Integration Suite
@sap/mdk-mcp-serveradded to the atlasMCP server with five tools for Mobile Development Kit work
@sap/mdk-mcp-serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.
SAP-samples/hana-cli-claude-pluginadded to the atlasClaude Code plugin registering hana-cli's MCP server
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.
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 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.
Show 4 more
MCP Server for SAP BTP Administrationadded to the atlasSAP-hosted MCP endpoint for BTP account administration
SAP LeanIX MCP Serveradded to the atlasHosted MCP endpoint onto an SAP LeanIX instance
MCP Server for SAP BTP Administrationentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.
SAP LeanIX MCP Serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it. Classified btp because the ecosystem list has no door for enterprise architecture and hard rule 9 allows only one; the strain is recorded here rather than hidden in the choice.
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missions
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.
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.
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.
Show 18 more
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.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.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.
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.
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.
sap-fiori-iosadded to the atlasAgent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUI
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.
aicore-skillsadded to the atlasFour agent skills for SAP AI Core in SAP's AI Skills Library
aicore-skillsentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact. The plugin was added there on 2026-09-21 and the registry front end at skills.cloud.sap had not listed it when the registry was crawled on 2026-09-25, so it is entered from its own plugin.json, README and three SKILL.md files. Hard rule 7: skills are indexed, never authored here.
sap-tutorials-contentadded to the atlasAgent skill mapping the developers.sap.com content API
SAP-samples/html5-applications-migration-skills-for-sap-btpadded to the atlasClaude Code plugin with skills migrating HTML5 apps to appFront
SAP-samples/sap-devs-cliadded to the atlasCLI adding SAP developer knowledge and MCP servers to AI coding tools
SAP-samples/joule-a2a-agent-toolkitadded to the atlasSkills for building an A2A agent for Joule and deploying it to CF
SAP/automation-pilot-agent-skillsadded to the atlasEight skills for writing and operating SAP Automation Pilot content
SAP/leanix-ai-pluginsadded to the atlasClaude Code plugin with two skills for SAP LeanIX scripting
SAP-samples/joule-a2a-agent-toolkitentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.
SAP/automation-pilot-agent-skillsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.
SAP/leanix-ai-pluginsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here. Filed under btp for the same reason its MCP server is: hard rule 9 allows one ecosystem and there is no door for enterprise architecture.
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).
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).
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).
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).
Show 16 more
Joule Studioadded to the atlasSAP's managed environment for building custom agents and workflows
@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.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.
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.
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.
Integrating and Extending JoulepublishedSAP's reference architecture for SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btp across SAP cloud applications: a request is checked against a Scenario Catalog of the applications' skills and a Knowledge Catalog answered by retrieval-augmented generation, combined with the user's roles and history, sent to an LLM available through the generative AI hub, and, where a Joule function is needed, turned into a call to the backend. Its identity page is the authenticationAuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. Authorization decides what that identity may do; identity provisioning manages its lifecycle across systems.SAP and community, narrow by design path: each user sits in the Identity Directory of Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp with a Global User ID, Identity Provisioning synchronises role assignments into SAP Build Work Zone, whose navigation service decides which functions a user may call, and the Destination service exchanges the user's token to call a function in the user's name. Its extension page covers Joule StudioJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btp in SAP Build, where Joule skills automate rule-based tasks over APIs and AI agents plan and reason with models and document grounding from SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp, the ground agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed covers; a later Joule Studio page describes a managed Joule Studio Runtime on the SAP Business AI Platform, which has no entry here.
SAP Jouleadded to the atlasSAP's AI engagement layer across SAP applications
@sap/joule-studio-cliadded to the atlasCLI for Joule digital assistants and Joule Studio solutions
@sap/joule-work-dev-cli-early-adoptersadded to the atlasPro-code CLI for building and deploying Joule Studio solutions
AI-native North Star architecture — Platform LayerpublishedThe platform layer of SAP's North Star architecture, the chapter that says where agents run and what a developer builds them with. It names an AI Golden Path built on the SAP Cloud Application Programming Model, the ABAP Cloud development model with RAP and the SAP Fiori design system, and a managed agent runtime on SAP BTP that is designed to provide software development kits for building agents in any framework, an agent sandbox, container-hosted execution, a skills registry and continuous evaluations, which is the ground agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed covers. Agents are extended without changing their code through four patterns, the first of them tool extensibility through the Model Context Protocol, the concern MCP serversServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through service integration, connecting its exposed contract with agent access to your systems. Development assistance belongs to agent access to your code.SAP and community, narrow by design is named for; the process-layer chapter adds that a pro-code path with a standardised agent SDK and a prompt-driven path through the Joule Studio solution produce the same code artifact on the same runtime. It describes a design SAP intends rather than products that exist, and the SDK and the registry it names have no entry here yet.
Content-based Agents with SAP Joule Studio Agent BuilderpublishedJoule Studio, classic editionJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btp, the capability in SAP Build the page calls Joule Studio, is where an organisation creates and manages its own Joule skills and Joule agents; its Agent Builder is for a custom agent that handles a multi-step task by combining instructions, model-backed planning and reasoning, and a configured set of tools, Joule skills, document resources, MCP servers, or other agents run as subagents. The page states an agent executes inside the calling user's own security context through SAP Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp, and can be tried against a test conversation before deployment. That is the tool-and-turn-taking ground agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed covers, here built through Joule Studio rather than in application code.
Custom Joule SkillspublishedA custom Joule skill is a workflow written to extend what Joule does out of the box for one specific business need, built and deployed through Joule StudioJoule Studio, classic editionThe low-code capability in SAP Build for custom Joule skills and Joule agents: skills call OData APIs through BTP destinations, agents get a model, instructions, tools and MCP servers, and both deploy to Joule.sap official, btp in SAP Build; the page states this is the supported way to extend Joule's built-in capabilities. Through Joule Studio a skill reaches SAP and external APIs via the destinations already configured in the BTP subaccount and Build environment, with the workflow itself versioned, monitored and deployable from the same tool.
Joule Studio, classic editionadded to the atlasLow-code SAP Build capability for custom Joule skills and agents
Pro-Code AI AgentspublishedPro-code agents are the most flexible way the page frames building an agentic workflow on SAP BTP: full autonomy, custom API integrations and algorithms chosen by the developer, set against declarative alternatives such as content-based agents and Joule Scenarios. It names LangGraph as the framework it recommends for production, enterprise-grade agentic workflows, alongside the ReAct pattern as the plan-act-observe loop such an agent runs. That is the ground agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed covers, building an agent's own tool-calling loop rather than exposing an application to somebody else's agent.
Building an LLM Agent in CAP Java with Spring AIpublishedThe Java counterpart to the author's own Node.js post, and written as one: connecting to AI Core with the SAP AI SDK, then calling an agent and a tool through Spring AI. Opens with a section on libraries and workflows — which framework does what, and what is left to you — before any code.
Building an LLM Agent using CAPpublishedThe argument is that CAP is already most of what an agent framework wants — services, handlers, a typed model — so the agent is built inside it rather than beside it. AI Core through sap-ai-sdk, then Langchain for the agent and its tools. Long, with a TLDR at the top for people who want the shape without the walk.
Joule Workadded to the atlasSAP's workspace for conversations, Spaces and directing agents
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.
Content FilteringpublishedContent filtering screens a large language model's input and output for low-quality, irrelevant or unsafe content: the four categories it names being hateful, violent, sexual and vulgar content, checking a request once on the way in and once on the way back. The page states smaller models can do this filtering efficiently, reading perplexity scores to flag anomalies, with the aim that SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp produces content meeting a stated safety standard, which is the ground content filteringContent filteringChecking what goes into a model and what comes out of it against content rules, and stopping or flagging a request that fails them. Distinct from data masking, which hides values: a filter refuses content.SAP only covers on the BTP door.
Data MaskingpublishedData masking replaces identifiable or confidential text in a prompt with placeholders such as <Person_0> or <Organization_1> before it reaches a large language model, using pattern matching and machine learning to find what to replace. The page states SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp supports it as a feature and sets out five steps for applying it, defining the masking scope, choosing a technique, preserving the prompt's intent, checking compliance and risk, then testing and monitoring the result. That is the shape data maskingData maskingReplacing the personal or confidential values in a prompt with placeholders before it leaves for a model, and putting them back in the answer. Anonymisation, where the values are gone for good, and pseudonymisation, where they return, are the two forms; which fields count as sensitive is the application's question, not the module's.SAP only takes on the BTP door.
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).
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.
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.
SAP Document AIpublishedSAP's reference architecture for SAP Document AISAP Document AIExtracts header fields and line items from invoices, payment advices, purchase orders and custom document types, as structured data over a REST API — the extraction is the service's, the schema can be yours.sap official, btp, first as SAP composes the service on BTP for document extractionDocument extractionGetting structured data out of a document somebody sent you — an invoice, a purchase order, a scanned form — instead of having a person key it in. The mirror image of document output, and a different problem from reading a service: the input is a file, the shape is unknown until something reads it, and the answer arrives with a confidence rather than a guarantee.SAP only: OCR, pretrained models, customer-defined schemas and LLM calls through SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp and its Prompt Registry in one pipeline, with tenant-isolated persistence in SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp, PostgreSQLPostgreSQLA relational database. For CAP it is the production database when the answer is not HANA, reached through an adapter that translates CDS queries into its SQL. and an object store. Its scenario pages then lay out a solution in three layers: intake through Outlook and SharePoint inbound channels, the workspace UI, the Joule Work mobile app or the upload API; classification and extraction with a confidence score per field, automatic confirmation above a threshold and review of the rest in the workspace; and posting through outbound channels, directly to a REST API, through an SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp flow, or through a CAP@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap service that maps the fields and calls SAP S/4HANA over OData. Enrichment beyond the service's own master data lookup is left to a CAP application or an Integration Suite flow triggered from an outbound channel, and direct API posting leaves error handling, retries and monitoring to the application.
Show 1 more
SAP Document AIadded to the atlasExtracts header fields and line items from business documents
CAP in the age of AI #6 - vector embeddingspublishedVector embeddings put to work in the incident managementcapire/incidents-appThe Incident Management reference application — the one SAP's own tutorial paths build, step by step, and the model cds add incidents-sample drops into a project.sap official, cap sample, answering whether this problem has been seen before. An
embedding element of type Vector is calculated and stored from the vector_embedding function, so the database refreshes it whenever the text behind it changes, and cosine_similarity compares it with a freshly embedded string; because a title says little, a scheduled action first summarises each incident's conversation through a model on SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp and the embedding is taken from that summary. The similar-incidents list is a view joining incidents to themselves, with order and limit set in a before handler on the expanded query, and the vector element excluded from the service, since OData knows nothing about vectors — on SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp the function is native, while SQLite needs packages added to the project.CAP in the age of AI #7 - vector embeddings wrap-uppublishedThe same embeddings model taken from SQLite to SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp, then handed to an agent. Locally it is @cap-js/ai@cap-js/aiOut-of-the-box value-help recommendations powered by SAP RPT-1, SAP AI Core as a standard CAP service, and an experimental local embedding model behind SQLite's vector functions.sap official, cap that adds the vector functions SQLite lacks and downloads an all-MiniLM L6v2 ONNX model on first start; on HANA natural language processing has to be switched on, the model name is a mandatory argument, the vectors it returns are 768 dimensions, and dimensions must match on both sides of a comparison. HANA itself can be given SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp as a remote source for other embedding models, which a
CDS.ql expression has to inject because the postfix notation only takes what the CDS model holds, and the hour ends with a search function over cosine similarity exposed over @cap-js/mcp@cap-js/mcpA CAP plugin that serves an @mcp-annotated service over MCP with three generated tools, describe, query and call_action, and writes its endpoint into the local agent's configuration in development.sap official, cap, so an agent asked about low output from solar panels calls semantic search instead of writing the query itself.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).
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).
Show 5 more
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.
Access to Generative AI ModelspublishedSets out the plain way to call a deployed generative AI model on SAP BTP: a request that carries the prompt, the model and the parameters that control generation, with the same code able to switch between models. It lists data masking, prompt templating and filtering as features that come with the access rather than as code the caller writes, which is the shape LLM integrationLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.SAP and community, narrow by design takes on the BTP door; the page's implementation sections sit behind its steps and were not read.
SAP AI Coreadded to the atlasAI runtime on BTP with the Generative AI Hub
Generative AI on SAP BTPcapability revisedThe capability moved to a neutral id when it opened to HANA, BTP and ABAP; the concern and this entry's edge to it are unchanged.
Generative AI on SAP BTPpublishedThe reference shape for a generative AI application on BTP: a CAP@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap backend, SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp holding data and embeddings for similarity search through its vector engine, and the Generative AI Hub in SAP AI Core as the single access point to foundation models. It shows retrieval-augmented generation on that stack and names the CAP plugins and SDKs that connect the pieces, for both Cloud Foundry and Kyma.
Data Attribute Recommendationadded to the atlasML models that classify records and predict attributes
Personalized Recommendationadded to the atlasMachine learning recommendations over browsing history via REST
Federated Machine Learning with SAP DataspherepublishedSAP's design for training predictive models on an external machine learning platform against SAP DatasphereSAP DatasphereSAP's cloud data warehouse: spaces, modelled views and analytic models over data brought in or federated from source systems, with the business context carried along rather than rebuilt.sap official, btp data that is not replicated to that platform. The open-source FedML Python library runs in the platform's notebook, connects to Datasphere over Python/SQLDBC and reads the analytic models in which Datasphere unifies SAP and non-SAP sources; a trained model can then be deployed to SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp, or in several sub-pages to SAP BTP, Kyma runtimeSAP BTP, Kyma runtimeA fully managed Kubernetes runtime on SAP BTP, based on the open-source project Kyma, where extensions to SAP solutions run as containerised microservices and serverless Functions.sap official, btp, which is the predictive modelsPredictive modelsTraining, deploying and calling a model that predicts a value from tabular business data: a classification, a regression, a forecast. Distinct from LLM integration, where a language model generates text, even where both run on the same service.SAP only path where training happens outside SAP. Sub-pages cover Amazon SageMaker, Azure Machine Learning, Google Vertex AI, DatabricksDatabricksA unified data and AI platform. sap-bdc-mcp-server creates the Delta shares it registers with SAP Business Data Cloud in a Databricks workspace., NVIDIA RAPIDS on GPUs and IBM watsonx.
Prompt TemplatingpublishedPrompt templating replaces a static prompt with a structured, reusable template whose placeholders are filled in at runtime, which the page says helps LLM responses stay consistent and lets the same instructions be adapted across tasks. On SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp this is implemented through the Prompt Registry, and the page states that storing prompts as plain strings in code is possible but not recommended. That is prompt managementPrompt managementKeeping the prompts an application sends to a model as templates with placeholders, stored and versioned apart from the code that calls them, so a change of wording is not a deployment. What people conflate under it: the template filled at runtime, the registry it lives in, and the orchestration step that fills it.SAP only as a stored and managed object rather than a string embedded in the caller.
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).
Document GroundingpublishedDocument Grounding is a managed retrieval-augmented-generation service under the Generative AI Hub on BTP, which SAP's page on SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp places inside that service: it ingests documents from Amazon S3, SharePoint, SAP Document Management Service, SAP Work Zone or an SFTP server, and handles chunking, embedding and retrieval itself, refreshing content automatically when a source document changes. The page states this managed path is recommended for most enterprise scenarios because it covers the whole lifecycle end to end, and offers a separate Document Grounding Vector API for data that is already chunked and embedded, for cases that need finer control over chunking and metadata.
Agentic AI Security & GovernancepublishedNames seven threat categories agentic AI introduces beyond ordinary application security: prompt injection, excessive agency, supply-chain and model-integrity compromise, memory poisoning, improper output handling, resource abuse and agent-to-agent communication poisoning. Its answer is a defence-in-depth structure of security controls, input validation, privilege management, supply-chain checks, memory segmentation, output validation, execution quotas, secure communication, paired with governance and oversight: audit logging, explainability, human-in-the-loop review, fairness assessment and continuous monitoring. States the reason plainly: an agent decides, chains actions across turns, keeps memory between them and can act on real systems, a different risk profile from a single request-response call. That is the authorisation and audit-trail question tool governanceTool governanceControlling what an agent may call, with which authorisations, and leaving an audit trail of what it did. The authorisation question that MCP exposure raises but does not answer.SAP and community, unassessed is named for.
s4hana-hana-audit-policiesadded to the atlasSQL templates for HANA audit policies of an S/4HANA tenant
SAP Audit Log serviceadded to the atlasIngests and retains compliance audit data from BTP
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).
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).
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.
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.
Show 11 more
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.
SAP Authorization and Trust Management serviceconnects[0] revisedThe second reader read the connects batch of 2026-09-19 on 2026-09-22, after its acceptance, and found: neither quote names this service, and only one names Cloud Identity Services, so the page's title, which names both parties, is quoted beside them.
SAP Authorization and Trust Management serviceconnects revisedThe two security services had no edge between them, although most BTP diagrams draw one. SAP's administration guide states the trust and the protocol it is established with.
OAuth 2.0 on SAP BTPadded to the atlasOAuth 2.0 grant flows for applications and APIs in Neo regions
SAP Customer Identity and Access Management for B2Cadded to the atlasRegistration, login and consent for customer-facing sites
Secure Service Consumption Across HyperscalerspublishedSAP's design for a workload on SAP BTP that calls Amazon Web Services or Google Cloud services with short-lived credentials instead of stored keys, which is the outbound side of authenticationAuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. Authorization decides what that identity may do; identity provisioning manages its lifecycle across systems.SAP and community, narrow by design: the BTP application proving who it is to another cloud. On AWS it draws two paths, an ID token from Identity Authentication in Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp exchanged through AWS STS for an IAM role, or an X.509 certificate kept in SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp and presented to IAM Roles Anywhere; on Google Cloud only the token path, through Workload Identity Federation and an impersonated service account. It is drawn for those two hyperscalers only, and Microsoft Azure has no page in it.
Cloud Identity Servicesserves ecosystems revisedABAP authorisation is authorisation objects and roles, a different concern that an identity service does not answer, and on UI5 token validation happens in the router or the service rather than in the frontend. Listed behind both doors, it grouped under nothing on either.
SAP Authorization and Trust Management serviceserves ecosystems revisedThe same as Cloud Identity Services: ABAP's authorisation model is not XSUAA's, and a UI5 frontend does not validate the JWT — the router and the service do.
Cloud Identity Servicesadded to the atlasIdentity Authentication and Identity Provisioning as one tenant
SAP Authorization and Trust Management serviceadded to the atlasOAuth server issuing JWTs and holding scopes for BTP apps
SAP IAM integration with SAP Cloud Identity ServicespublishedIdentity and access management for SAP SaaS in a landscape where SAP is one vendor among several: SAP Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp as the designated interface, single sign-on over SAML 2 and OIDC, identity lifecycle through SCIM 2 replication of users and groups, and authorization designed per domain — an S/4HANA role and a BTP role collection are different objects that both have to reach the user. Drawn from customer projects, and the source of what authenticationAuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. Authorization decides what that identity may do; identity provisioning manages its lifecycle across systems.SAP and community, narrow by design here says about Cloud Identity Services.
SAP Custom Domain Serviceadded to the atlasServes BTP applications under the customer's own domain
SAP Data Privacy Integrationadded to the atlasAPIs for retention, deletion and personal data reports
SAP Data Retention Manageradded to the atlasRetention rules triggering blocking, deletion and archiving
SAP Personal Data Manageradded to the atlasService answering data subjects about their stored personal data
SAP Keystore Serviceadded to the atlasKey and certificate repository in SAP BTP's Neo data centres
SAP Cloud Identity Services - Identity Provisioningpart of revisedSAP's catalogue names Identity Provisioning as one of the services SAP Cloud Identity Services include. The first
part_of on an artifact.SAP Cloud Identity Services - Identity Provisioningadded to the atlasProvisioning jobs carrying users and groups between systems
SAP Malware Scanning serviceadded to the atlasScans uploaded files over REST with ClamAV
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.
Road map for SAP Integration Suite: What ships next across all capabilitiespublishedSAP's road map for SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp across its capability areas: API ManagementAPI ManagementAPI proxies in front of backend services, with security and traffic management policies attached to them, and Developer Hub where consumers subscribe.sap official, btp, event-driven integration, business process and trading partner integration, and hybrid runtimes for SAP and third-party systems. The abstract promises recent deliveries and the planned innovations that make the platform agent-ready within SAP Business AI Platform; it names the areas and no shipping item, so the edges rest on the product and the one area it names by a product name. A TechEd 2026 session (Thursday 29 October, Berlin; also IN804V, virtual), written here from SAP's abstract; the recording is not yet published.
API Managementadded to the atlasAPI proxies with security and traffic policies and Developer Hub
API Managementprovides revisedMoved here from SAP Integration Suite. SAP files MCP Server under API Management in its documentation, and every creation path read lists the activated API Management capability as a prerequisite.
SAP Credential Storeadded to the atlasVault for an application's passwords, keys and keyrings
Application Vulnerability Reportadded to the atlasTracks vulnerabilities in open-source components of BTP apps
btp-setup-automatoradded to the atlasContainerised script setting up an SAP BTP account from JSON config
Terraform Provider for SAP BTPadded to the atlasTerraform and OpenTofu provider for SAP BTP global accounts
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.
SAP Cloud Management Service for SAP BTPadded to the atlasREST APIs for administering a BTP account
Show 1 more
SAP Service Manageradded to the atlasRegistry for service brokers, instances and environments on SAP BTP
SAP BTP ABAP environmentadded to the atlasABAP runtime on BTP for the ABAP Cloud model
SAP BTP, Cloud Foundry Runtimeadded to the atlasCloud Foundry runtime of SAP BTP for polyglot applications
SAP BTP, Kyma runtimeadded to the atlasManaged Kubernetes runtime on SAP BTP based on Kyma
SAP Usage Data Management Service for SAP BTPadded to the atlasREST APIs for SAP BTP usage per metric and monthly cost
SAP-samples/btp-ai-core-usage-monitoradded to the atlasPython agent alerting on SAP AI Core capacity unit consumption
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).
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).
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).
SAP Cloud Transport Managementadded to the atlasMoves MTA archives and content between SAP BTP accounts
Show 5 more
SAP Content Agent Serviceadded to the atlasAssembles BTP service content into an MTAR for transport
SAP Solution Lifecycle Management service for SAP BTPadded to the atlasDeploys and manages MTA-based Solutions in the Neo environment
The fastest way to a deployable CAP app on SAP BTP Cloud FoundrypublishedThe gap between an application that runs locally and one that runs deployed — binding, bundling, the database connection, authorization — treated as the problem rather than as setup. Since updated for cds up, which is the shortest answer the core now offers, and the post carries that update inline rather than leaving the original standing.
Architecting Multi-Region HA/DR resiliency patternspublishedPatterns for running BTP applications across regions when the default multi-availability-zone resilience is not enough: DNS-based load balancing across regional endpoints with Azure Traffic Manager, Route 53 or Cloud DNS, replication of data and configuration between regions, and the fundamentals of single-region versus multi-region resiliency in its sub-pages. BTP services are multi-AZ by default; a multi-region setup is something the customer architects, and this is SAP's description of how.
DevOps with SAP BTPpublishedHow SAP frames a delivery pipeline for applications on BTP Cloud Foundry: continuous integration through the SAP Continuous Integration and Delivery service and its pipeline templates for CAP and Fiori, transport and change management across environments, and a section on reasonable alternatives for teams with existing CI infrastructure. Culture first, tools second, and explicit that the setup differs on other BTP environments.
@sap/artifact-managementadded to the atlasMTA generation and Cloud Foundry deploy for VS Code workspaces
@sap/mdk-toolsadded to the atlasCLI to build, deploy, migrate and validate MDK projects
@sap/artifact-managemententry revisedplace.mjs scaffolds a stub with guessed defaults; this fills it in from the package's own record.
@sap/mdk-toolsentry revisedplace.mjs scaffolds a stub with guessed defaults; this fills it in from the package's own record.
SAP Feature Flags serviceadded to the atlasBoolean and string flags read by applications at runtime
SAP Job Scheduling serviceadded to the atlasCalls an application endpoint on a schedule and logs each run
SAP Cloud Loggingadded to the atlasOpenSearch-based store for logs, metrics and traces
SAP Application Logging service for SAP BTPadded to the atlasCollects Cloud Foundry or Kyma logs into a searchable Kibana
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).
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.
SAP Software-as-a-Service Provisioning serviceadded to the atlasRegisters a multitenant application for subaccount subscriptions
Multitenant SaaS Application using CAPpublishedSAP's reference architecture for a multitenant SaaS application on BTP built with CAP@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap: one deployment serving many tenants with logically separated data, the subscription and onboarding flow, and the BTP services the design leans on. Written for partners and line-of-business teams building on BTP, and it is SAP's own side of the shape multitenancyMultitenancyServing many tenants from one deployment — onboarding, tenant-isolated data, per-tenant schema deployment and the operational tooling around it. It is decided once, before anything is built, and narrows the artifacts in almost every capability downstream: most sharply in caching and anything else holding state in process.SAP and community, narrow by design takes on BTP.
Application Autoscaleradded to the atlasScales Cloud Foundry app instances by policy rules and schedules
SAP Alert Notification service for SAP BTPadded to the atlasPublishing and subscribing to alerts about BTP resources and apps
SAP Automation Pilotadded to the atlasRuns operations commands on BTP by hand, schedule or event
Agent Activation for Dynatrace Service for SAP BTPadded to the atlasInjects the Dynatrace agent into Java applications on SAP BTP
SAP Monitoring Service for SAP BTPadded to the atlasMetrics, availability checks and alerts for apps in Neo regions
@sap/e2e-traceadded to the atlasSAP Passport handling for Node.js components
SAP BTP Solution Diagram Guidelinesadded to the atlasSAP's visual language and templates for BTP solution diagrams
SAP Continuous Integration and Deliveryadded to the atlasPredefined CI/CD pipelines for SAP development projects
SAP Build Codeadded to the atlasDevelopment environment on BTP for UI5, Fiori, mobile and CAP
SAP Business Application Studioadded to the atlasBrowser-based development environment with dev spaces
SAP Web IDE Full-Stackadded to the atlasIDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
SAP Build Appsadded to the atlasLow-code platform for web and native mobile apps
@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.
@sap/approuterconnects revisedThe router's five service bindings said that it needs each service and not how it talks to it. Each is now also a connection, with what the README states about it and nothing it does not: OAuth2 is named for the UAA and for no other.
@sap/approuteradded to the atlasSAP's Node.js application router in front of business applications
@sap/approuterrequires, alternative to revisedSAP's own Application Frontend service page names the HTML5 Application Repository and the application router as what to stay on where those meet your needs better, and the service entry already carries the edge to the repository.
Show 3 more
SAP Application Frontend serviceadded to the atlasManaged hosting and routing for built frontends
SAP HTML5 Application Repository service for SAP BTPadded to the atlasStores UI5 and HTML5 apps and serves them through the approuter
SAP Application Frontend serviceentry revised@sap/appfront-cli was in the corpus and the service it drives was not, so the BTP door listed a CLI with nothing behind it. SAP's own page names the HTML5 Application Repository as the thing to stay on where it fits better, which is why the two carry an alternative_to edge rather than one quietly superseding the other.
UI flexibility serviceadded to the atlasKey-user adaptation and personalisation for UI5 apps on SAP BTP
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).
SAP Build Work Zone, advanced editionbundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn. Mobile Services and UI theme designer are listed too and have no entry.
SAP Build Work Zone, standard editionbundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn. Mobile Services and UI theme designer are listed too and have no entry.
Establish a central entry point with SAP Build Work ZonepublishedSAP's reference architecture for a business site in SAP Build Work Zone, standard editionSAP Build Work Zone, standard editionA role-based business site on BTP that puts SAP, custom-built and third-party applications and extensions, cloud and on premise, behind one point of access.sap official, btp or SAP Build Work Zone, advanced editionSAP Build Work Zone, advanced editionA BTP service for business sites and digital workspaces: one role-based entry point to SAP and third-party apps, processes, tasks and web content, with blogs, wikis, feeds and other collaboration beside them.sap official, btp as one entry point to business applications, processes, information and communication, on the web or in the Joule Work mobile app. Three of its eight flow steps are how content gets in, the ground launchpad and site contentLaunchpad and site contentGetting apps, cards, pages and workspaces in front of users in an application launchpad or portal, including content providers, content packages and access roles. Serving the application’s files is app hosting; extending the surrounding shell is launchpad plugins.SAP only covers: custom apps through the channel to the subaccount's SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPStores built UI5 and HTML5 applications and serves them at runtime through the approuter, so an app ships no static server of its own.sap official, btp, other content through content providers that expose it over APIs from cloud or on-premise systems and content packages uploaded as files, and SAP Cloud Transport ManagementSAP Cloud Transport ManagementMoves software deliverables between SAP BTP accounts along a modelled landscape of transport nodes and routes: Multitarget Application archives, and application-specific content such as SAP Cloud Integration iFlows.sap official, btp or manual export and import to move it between environments. Users and role assignments come from Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp, and the components inside the subscription, among them Notifications, SAP Mobile Services and UI Theme Designer, cannot be decoupled from the product, so a custom mobile app needs its own SAP Mobile Services subscription.
Show 3 more
SAP Build Work Zone, advanced editionadded to the atlasBusiness sites and digital workspaces with collaboration tools
SAP Build Work Zone, standard editionadded to the atlasRole-based business site for SAP and third-party apps
SAP Cloud Portal Serviceadded to the atlasRole-based portal sites with pages, apps and widgets
SAP Translation Hubadded to the atlasTranslation service for software texts and documents
Agentryadded to the atlasBTP service for building and running Agentry mobile apps
SAP Mobile Servicesadded to the atlasSAP BTP service for native and cross-platform mobile apps
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).
SAP Task Centerrequires revisedSAP's Discovery Center lists both Work Zone editions as required services of the all-tasks plan, and npm run check:catalogue listed the relations with no edge. Basis entitlement and conditional: the plan's own description says either edition serves (vocab PERSPECTIVES, 2026-09-22).
Establish a central inbox with SAP Task CenterpublishedSAP's reference architecture for SAP Task CenterSAP Task CenterOne inbox across SAP applications: tasks from S/4HANA, SuccessFactors, Ariba and BTP workflows in one list, with a public API for a custom task provider.sap official, btp as one inbox for the tasks of several SAP applications, opened in the Task Center web app or as To-Dos in SAP Start and SAP Mobile Start, which is the inbox half of task and approval UIsTask and approval UIsThe screen a person approves something on — a workflow or process task rendered as a form, embedded in an inbox that supplies its context. Distinct from workflow integration, which is about driving the engine: this is the half a human touches, and its hard part is that it cannot run without the engine that normally feeds it.SAP only. It rests on Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp: every task provider must work with Identity Authentication, its users must carry the Global User ID and so must the recipients of each task, and sign-on between the provider and Identity Authentication is what lets a user navigate from Task Center into the provider. Task Center reaches providers through destinations in a customer subaccount, with Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp for on-premise SAP S/4HANA.
SAP Task Centeradded to the atlasOne inbox for tasks across SAP applications and BTP workflows
Intelligent Situation Automationadded to the atlasRule-based resolution of SAP S/4HANA business situations
Integrate and Extend with SAP Build Process AutomationpublishedSAP's reference architecture for SAP Build Process AutomationSAP Build Process AutomationSAP's low-code and no-code tool for business processes: graphical process models, drag-and-drop forms, decision tables and robotic process automation bots, with dashboards over running process instances.sap official, btp integrating and extending SAP and non-SAP solutions in cloud and hybrid landscapes, the ground process automationProcess automationModelling and running a business process: the process flow, the forms people fill in, decision tables, bots for repetitive steps, and dashboards over the instances that run. Starting a process from an application and reacting to it is workflow integration, and the screen a person approves a task on is task and approval UIs.SAP only covers. Processes start from events, APIs, schedules or forms, the forms built in SAP Build Process Automation, as UI5 applications or in SAP Build AppsSAP Build AppsSAP's low-code platform for web and native mobile applications, built by drag and drop, with no-code backends and access to SAP systems through BTP authentication and destinations.sap official, btp; they reach other systems through the SAP Connectivity serviceSAP Connectivity serviceThe proxy through which a cloud application reaches an on-premise system behind a Cloud Connector — HTTP, RFC and raw sockets — without that system being exposed.sap official, btp with actions over APIs from sources that include CAP@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, cap and RAP OData destinations and SAP Business Accelerator Hub specifications, and users reach them through SAP Build Work Zone and SAP Mobile Start, with SAP Task CenterSAP Task CenterOne inbox across SAP applications: tasks from S/4HANA, SuccessFactors, Ariba and BTP workflows in one list, with a public API for a custom task provider.sap official, btp as the place tasks are managed. Decisions, Process Visibility, Processes and Automations come inside the one subscription and cannot be decoupled from it; CAP appears only as a source of API actions, and the examples are business scenarios such as mass job requisitions in SAP SuccessFactors.
SAP Build Process Automationadded to the atlasLow-code and no-code tool for business processes and RPA bots
SAP Responsibility Management serviceadded to the atlasResolves who is responsible for a process or item, and notifies them
Under no capability
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successors
SAP-samples/digital-manufacturing-extension-samplesadded to the atlasSamples for the six extension types of SAP Digital Manufacturing
API Compositionadded to the atlasBusiness data graph queried with OData V4 or GraphQL
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.
Show 109 more
SAP Integration Suitebundles revisedSAP's Discovery Center lists these among the plan's included services, and npm run check:catalogue listed the relation with no edge. An entitlement and not a dependency: a bundles edge, read by the commercial perspective (vocab PERSPECTIVES, 2026-09-22), listed and never drawn.
SAP Integration Suiteprovides revisedMoved to API Management, the part SAP's documentation names as doing it. An edge sits on the smallest thing the documentation names.
API Managed IntegrationpublishedSAP's reference architecture for API-managed integration, which puts the API Management capability of SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp in front of business applications as API proxies that intercept each call to apply security policies, transformations and governance and to collect usage metrics. SAP defines it as a pattern that complements the other integration patterns, and draws three routes behind the proxy: a managed API forwarded to its provider for simple transformations and protocol adaptations, the Graph capability exposing data from several sources as one connected API, and Cloud Integration for mediation beyond API Management's scope, with the edge integration cell runtime for managing APIs in a customer-managed Kubernetes environment. SAP states that it delivers no predefined scenarios for this pattern, so the proxies and policies are the customer's or partner's to build.
Joule in SAP Build Codeadded to the atlasJoule's generative AI inside SAP Build Code
SAP/architecture-centeradded to the atlasSource repository of SAP's reference architectures
ai-enabled-integrations-codejamadded to the atlasCodeJam on LLM-backed integration flows and MCP via API Management
aicore-genai-samplesadded to the atlasSample apps for SAP AI Core's Generative AI Hub capabilities
analytics-cloud-scim-api-samplesadded to the atlasPostman collections for the SAP Analytics Cloud SCIM API
btp-admin-guide-samplesadded to the atlasTerraform samples for the SAP BTP Administrator's Guide account model
btp-edge-integration-cell-on-azureadded to the atlasInstructions for deploying Edge Integration Cell onto Microsoft Azure
btp-gen-ai-hub-sdk-samplesadded to the atlasSetup guide and Python notebooks for SAP AI Core's Generative AI Hub
btp-hello-world-fioriadded to the atlasMission building a Hello World SAPUI5 app on a BTP Launchpad Site
btp-kyma-helloworldadded to the atlasGetting-started guide for a Hello-World function on SAP BTP, Kyma
btp-neo-java-app-migrationadded to the atlasGuide and samples for moving Java apps from Neo to Cloud Foundry
btp-s4hana-nocode-extensionadded to the atlasMission building a no-code S/4HANA UI extension with SAP Build Apps
btp-spend-analysisadded to the atlasIntegration flows pulling SAP Ariba spend data into SAP Datasphere
btp-terraform-mooc-terra1added to the atlasCode samples for the Getting Started with Terraform on SAP BTP course
btp-terraform-samplesadded to the atlasSamples for the Terraform Provider for SAP BTP
cf-autoscaler-custom-metrics-mtlsadded to the atlasGolang sample sending custom metrics to the CF Autoscaler over mTLS
cf-mta-examplesadded to the atlasMTA examples for SAP BTP, Cloud Foundry, one per deployment topic
cf-routing-samplesadded to the atlasCloud Foundry routing samples: HTTP/2, gRPC, IP allow-lists
cloud-integration-pipeline-datastore-extension-uiadded to the atlasCAP and Fiori elements app for managing Cloud Integration datastores
cloud-mdk-samplesadded to the atlasMobile development kit sample apps and how-to demonstrations
cloud-mdk-tutorial-samplesadded to the atlasSample projects referenced by the mobile development kit tutorials
hana-graph-examplesadded to the atlasSQL scripts and a notebook for SAP HANA's built-in graph algorithms
hana-shine-xsaadded to the atlasSHINE demo application for learning SAP HANA XS Advanced
hda-cross-pm-samplesadded to the atlasTutorials and use cases for SAP HANA database and analytics products
hxe-hibernate-google-app-engineadded to the atlasJava demo running Spring and Hibernate against SAP HANA
iq-to-hdl-migrationadded to the atlasPython utilities migrating SAP IQ into HANA Cloud, data lake
joule-studio-setup-terraformadded to the atlasTerraform template for a BTP subaccount set up for Joule Studio
Sample CAP Application with SAP Cloud SDK for AIadded to the atlasCAP samples calling SAP AI Core through the SAP Cloud SDK for AI
SAP AI Launchpadadded to the atlasSaaS front end over SAP AI Core
SAP BTP AI Best Practice Demo - Content Filtering - CAPadded to the atlasCAP samples comparing SAP AI Core responses with content filtering
SAP BTP AI Best Practice Demo - Data Masking - CAPadded to the atlasCAP samples generating email through SAP AI Core with anonymization
SAP BTP AI Best Practice Demo - Prompt Registry - CAPadded to the atlasCAP samples using SAP AI Core's Prompt Registry for templates
SAP BTP AI Best Practice Demo - Prompt Templating - CAPadded to the atlasCAP samples filling a prompt template sent to SAP AI Core
SAP BTP AI Best Practice Demo - Vector Embedding (RAG) - CAPadded to the atlasCAP samples embedding CSV rows into the SAP HANA Cloud vector store
SAP BTP AI Best Practice Demo - Vector Query (RAG) - CAPadded to the atlasCAP samples running RAG similarity queries over SAP HANA Cloud vectors
sap-btp-ai-best-practicesadded to the atlasSample implementations for AI-powered applications on SAP BTP
sap-concur-user-provisioning-service-apisadded to the atlasPostman collection for the SAP Concur User Provisioning Service APIs
sap-genai-hub-with-sap-hana-cloud-vector-engineadded to the atlasWorkshop on HANA Cloud vector engine, Generative AI Hub and LangChain
SAP-samples/application-vulnerability-report-scan-user-automationadded to the atlasPython script assigning the AVR scan user to Cloud Foundry spaces
SAP-samples/automation-pilot-examplesadded to the atlasImportable SAP Automation Pilot commands for operations scenarios
SAP-samples/btp-a2a-dispute-resolutionadded to the atlasCross-cloud A2A demo of agents settling a shipment dispute
SAP-samples/btp-agentic-ai-use-casesadded to the atlasTwo runnable industry AI agent projects built around Joule
SAP-samples/btp-ai-core-consumption-monitoradded to the atlasCAP and React dashboard for SAP AI Core capacity unit consumption
SAP-samples/btp-onboardingadded to the atlasGuide to the first setup tasks on a new SAP BTP enterprise account
SAP-samples/btp-resource-consumption-monitoradded to the atlasApp monitoring SAP BTP credit consumption with alerts on increases
SAP-samples/btp-sourcing-decision-boardadded to the atlasProcurement decision support cross-validating two AI agent strategies
SAP-samples/cloud-btp-cli-api-codejamadded to the atlasCodeJam material on the btp CLI and the Core Services API
SAP-samples/cloud-sample-webhooksadded to the atlasJava servlets relaying Neo alerts on premise via Cloud Connector
SAP-samples/codejam-code-based-agentsadded to the atlasCodeJam on code-based AI agents in Python or TypeScript on SAP BTP
SAP-samples/concur-joule-ips-jobsadded to the atlasIdentity Provisioning jobs syncing SAP Concur users for Joule
SAP-samples/connecting-systems-services-integration-suite-codejamadded to the atlasCodeJam building an integration flow in SAP Integration Suite
SAP-samples/generative-ai-codejamadded to the atlasCodeJam deploying an LLM on Generative AI Hub and building RAG
SAP-samples/hana-cf-get-started-trialadded to the atlasStarting project for a tutorial on NoSQL, graph and spatial in HANA
SAP-samples/hana-cloud-modeling-learning-journeyadded to the atlasCourse files for Developing Data Models with SAP HANA Cloud
SAP-samples/manage-apis-codejamadded to the atlasCodeJam on API management in SAP Integration Suite
SAP-samples/smartrecruiters-ai-recruiting-custom-agentadded to the atlasRecruiting agent on SmartRecruiters data flagging stalled candidates
SAP-samples/teched2022-XP281added to the atlasTechEd 2022 workshop on Alert Notification and Automation Pilot
SAP-samples/teched2024-XP280added to the atlasTechEd 2024 session on Terraform setup of SAP Build services
SAP-samples/teched2025-AI160added to the atlasHands-on building an AI agent with the SAP Cloud SDK for AI
SPFI-Reference-Applicationadded to the atlasSpring Boot reference implementing the SPFI V2 tenant lifecycle API
teched2022-XP260added to the atlasTechEd 2022 session on SAP BTP security recommendations
teched2023-DA263added to the atlasTechEd 2023 session on SAP HANA features over HDI
teched2023-XP185vadded to the atlasHands-on applying SAP BTP security recommendations to a trial account
teched2024-IN280added to the atlasTechEd 2024 session on Integration Suite between SAP IBP and others
teched2025-AI161added to the atlasTechEd 2025 session on benchmarking and optimising prompts
teched2025-AI163added to the atlasTechEd 2025 lab building a Joule Agent for Global Track and Trace
teched2025-AI165added to the atlasTechEd 2025 hands-on on a Joule Studio agent collaborating over A2A
teched2025-CS261added to the atlasTechEd 2025 workshop monitoring a BTP app with SAP Cloud ALM
teched2025-DA261added to the atlasTechEd 2025 workshop on SAP HANA Cloud's AI capabilities
teched2025-DA265added to the atlasTechEd 2025 workshop on Just Ask natural-language questions
teched2025-DA267added to the atlasTechEd 2025 workshop on seamless planning for xP&A in BDC
teched2025-IN161added to the atlasTechEd 2025 session on migrating SAP PO scenarios to Integration Suite
teched2025-XP261added to the atlasHands-on integrating Cloud Identity Services with Microsoft Entra
teched2025-XP263added to the atlasTechEd 2025 hands-on on SAP BTP advanced administration tools
teched2025-XP264added to the atlasTechEd 2025 session on Day-2 operations for SAP BTP, Kyma runtime
teched2025-XP265added to the atlasTechEd 2025 workshop on Day-2 operations for a CAP app on CF
teched2025-XP267added to the atlasTechEd 2025 session on Automation Pilot fixes from Cloud ALM alerts
workzone-content-package-templatesadded to the atlasProject templates for SAP Work Zone content packages
xsc-to-native-hana-cloudadded to the atlasGuide converting XS Classic content to native SAP HANA Cloud artefacts
xsc-xsa-migrationadded to the atlasGuide to migrating XS Classic content to XS Advanced
ai-core-samplesadded to the atlasTutorial notebooks and templates for a first SAP AI Core project
aicore-multioutput-regression-restaurant-inspectionsadded to the atlasML service on SAP AI Core scoring restaurant-inspection violations
analytics-cloud-rpt15-prediction-demoadded to the atlasFastAPI backend for SAP-RPT-1.5 predictions from SAP Analytics Cloud
btp-private-link-approuteradded to the atlas@sap/approuter patterns in front of SAP Private Link Service
btp-service-metadataadded to the atlasMachine-readable catalogue of SAP BTP pay-as-you-go services
hana-apl-apis-runtimesadded to the atlasSQL examples for the HANA APL APIs plus scoring runtimes
hana-ml-samplesadded to the atlasCode examples for predictive and ML scenarios on SAP HANA
private-link-aws-servicesadded to the atlasSpring Boot apps routing AWS SDK traffic over SAP Private Link
sap-rpt-samplesadded to the atlasBruno collections and code for SAP-RPT predictions on tabular data
SAP-samples/ams-samples-javaadded to the atlasJava apps showing policy-based authorization with AMS on SAP BTP
SAP-samples/ams-samples-nodeadded to the atlasNode.js apps showing policy-based authorization with AMS on SAP BTP
SAP-samples/btp-aws-monitronadded to the atlasProof of concept turning AWS IoT events into S/4HANA notifications
SAP-samples/cloud-cf-feature-flags-sampleadded to the atlasSpring Boot demo evaluating a toggle from the Feature Flags service
SAP-samples/event-driven-integrations-codejamadded to the atlasCodeJam moving from polling to pub-sub on advanced event mesh
SAP-samples/event-mesh-client-java-samplesadded to the atlasSpring Boot apps messaging over SAP Event Mesh's Java JMS client
SAP-samples/event-mesh-client-nodejs-samplesadded to the atlasNode.js samples for SAP Event Mesh's AMQP 1.0 messaging client
SAP-samples/hana-ml-py-codejamadded to the atlasCodeJam on a first machine learning workflow in SAP HANA Cloud
SAP-samples/multi-cloud-html5-apps-samplesadded to the atlasHTML5 apps on the HTML5 Application Repository across CF and Kyma
SAP-samples/sap-bdc-explore-hyperscaler-dataadded to the atlasGuides connecting hyperscaler sources into SAP Datasphere in BDC
SAP-samples/teched2025-DA260added to the atlasTechEd 2025 workshop on SAP Business Data Cloud connectivity options
SAP-samples/teched2025-DA264added to the atlasTechEd 2025 jump-start on a semantic model in SAP Datasphere and SAC
SAP-samples/teched2025-IN162added to the atlasTechEd 2025 workshop piping business events into HANA vectors
SAP-samples/teched2025-IN163added to the atlasTechEd 2025 workshop on exactly-once, in-order delivery
teched2025-DA266added to the atlasTechEd 2025 material on two SAP Databricks scenarios in BDC
SAP Integration Suiteadded to the atlasIntegration service on BTP with Cloud Integration and API Management
@sap/appfront-cliadded to the atlasCLI for the SAP BTP Application Frontend service