OrganisationSAP
SAP
Capabilities
Provides
ABAP Cloud readinessABAPABAP Cloud readinessWhether code can run in ABAP Cloud — released APIs only, no direct table access, no obsolete statements — and what to do with the code that cannot.AccessibilityUI5AccessibilityMaking a UI usable with a screen reader, with a keyboard alone and without seeing the layout: accessible names on controls, a heading order, landmarks, focus handling and announcements. Target size for a finger is [touch operation](capability:ui5-touch-uis).Account provisioningBTPAccount provisioningSetting up cloud accounts, their organisational structure, resource entitlements, subscriptions and access assignments so the setup can be repeated from code. [Deployment](capability:deployment) puts an application onto a runtime that this account structure makes available.Agent access to your codeCAPABAPUI5BTPAgent access to your codeLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Agent guidanceCAPUI5BTPABAPAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.Agent toolingCAPBTPAgent 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.Agent workspacesBTPAgent workspacesGiving people a workspace to direct agents, retain the context of a task and interact with its results across connected applications. This is the user-facing experience around agents; building their logic belongs to [Agent tooling](capability:agent-tooling), and controlling their calls belongs to [Tool governance](capability:tool-governance).App hostingBTPUI5CAPApp hostingWhere a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.Application runtimesBTPApplication runtimesThe environments that execute application code and manage its processes, containers or managed language runtime. Getting a build onto one is [deployment](capability:deployment); serving a frontend’s built static files is [app hosting](capability:app-hosting).Architecture diagramsBTPArchitecture diagramsDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.AttachmentsCAPUI5ABAPBTPAttachmentsStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.AuthenticationCAPBTPABAPUI5AuthenticationEstablishing who is calling: validating credentials or tokens, resolving the user, and making that identity available to the application. [Authorization](capability:authorization) decides what that identity may do; [identity provisioning](capability:identity-provisioning) manages its lifecycle across systems.AuthorizationCAPBTPABAPAuthorizationDeciding who may read or change what, at service, entity and instance level — role checks, forwarded user context, and restrictions evaluated as query filters rather than after the fact.B2B message mappingBTPB2B message mappingDefining the structure of business messages exchanged between partners using different standards, and mapping one structure onto another. This includes interface specifications, schemas and transformations; executing them in middleware belongs to [integration flows](capability:integration-flows).Browsing table dataABAPBrowsing table dataLooking at what a system holds while developing or supporting it: the rows behind a key, the reference data a field points at, the tables that carry data for one object. Editing configuration records through maintenance screens is a different job, even where the same transaction does both.Build and dev-server toolingUI5Build and dev-server toolingServing an app locally and building it for deployment — proxying a backend, transpiling, bundling, and shaping the result for whatever will host it.Certificate managementABAPBTPCertificate managementKeeping the certificates a system trusts and presents over TLS current: importing root and intermediate CAs, requesting and importing its own signed certificate, and replacing one before it expires. Storing and rotating passwords and keys an application reads is [secrets rotation](capability:secrets-rotation).Change promotionABAPBTPCAPUI5Change promotionMoving a change through the environments of a landscape, from development through test to production, and knowing which change has reached which environment. A [CI/CD pipeline](capability:ci-cd) builds and tests on each source change, [deployment](capability:deployment) puts a build onto its runtime, and getting source into git is [source control](capability:abap-source-control).CI/CD pipelinesBTPCAPCI/CD pipelinesA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.Clean code conventionsABAPClean code conventionsThe naming, structure and language-subset conventions that make source code readable across a team — and the question of which of them a checker can enforce.Consumption monitoringBTPConsumption monitoringKnowing what a cloud account consumes as it runs, in credits, capacity units and cost per service and organisational unit, and being warned before a budget is spent. [Logging](capability:logging) and [telemetry](capability:telemetry) watch what an application does; this watches what it costs.Content filteringBTPCAPContent 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](capability:data-masking), which hides values: a filter refuses content.Data bindingUI5Data bindingKeeping a control and a model in step in both directions, including the formatting, type conversion and validation that sit between the two.Data federationCAPBTPData federationReading data that lives in another system as if it were local — by federating the query, by copying the rows, or by caching what was read. Three different answers to one question, and the choice is about how stale you can afford to be.Data maskingBTPCAPData 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.Data privacyCAPABAPBTPData privacyDoing what the law requires with personal data — knowing which fields are personal, answering a subject's request about them, and deleting them when the reason for holding them expires.Database connectorsCAPBTPABAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).DeploymentCAPBTPDeploymentGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.Deployment and operatorCAPBTPDeployment and operatorAutomating the build and deployment of a project with multiple modules: generating deployment descriptors and coordinating build, migration, deployment and validation commands. [Deployment](capability:deployment) describes the target runtime and lifecycle; this concerns the tooling that drives those steps.DestinationsCAPBTPUI5DestinationsReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.Document outputCAPABAPBTPDocument outputProducing a document a person receives — a printed form, a generated PDF, a filled template — and getting it to a printer or a queue rather than returning it as a payload.DocumentationCAPUI5BTPABAPDocumentationFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.Editor supportCAPABAPBTPUI5Editor supportWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.Encryption and signingABAPBTPEncryption and signingEncrypting, decrypting and signing data from application code: a document wrapped for one recipient, a payload signed so its origin can be checked, a value enciphered with a key both sides hold. Encryption of a connection, TLS, is set up in the system and is outside this concern.Event MeshCAPBTPABAPEvent MeshEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).Fiori annotationsCAPUI5ABAPFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.GeneratorsCAPABAPUI5GeneratorsGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.Health data interoperabilityBTPHealth data interoperabilityExchanging health-related data using the HL7 FHIR standard: FHIR resources profiled and stored for a project's own business and localization needs, reached over REST APIs, and connected to an external system through FHIR-specification messaging rather than a bespoke integration built per source.Identity provisioningBTPIdentity 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](capability:authentication) answers who is calling one request; provisioning decides whether the user exists in that system at all.Integration flowsBTPIntegration 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](capability:destinations), and brokering events between systems is [Event Mesh](capability:event-mesh).Integration scenario setupBTPIntegration scenario setupWalking through the technical configuration that connects systems — cloud to on-premise, or one cloud solution to another — as a guided, role-assigned checklist rather than a configuration guide followed by hand. [Integration flows](capability:integration-flows) move and transform the messages once the connection exists; this is the setup that runs before that.Key-user adaptationUI5ABAPBTPKey-user adaptationChanging a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.Launchpad and site contentBTPUI5Launchpad 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](capability:app-hosting); extending the surrounding shell is [launchpad plugins](capability:launchpad-plugins).Launchpad pluginsUI5ABAPBTPLaunchpad pluginsExtending an application launchpad’s shell rather than an individual app: adding header buttons, user-menu entries, frame areas or background behaviour shared across the apps it hosts. A development sandbox for launching an app is a separate concern.LintingCAPUI5LintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.LLM integrationCAPUI5BTPABAPLLM 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.Local developmentCAPABAPLocal developmentRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.LocalizationCAPABAPBTPUI5LocalizationServing labels, messages and translated content per user locale, including translatable model elements and per-tenant text overrides.Location servicesBTPCAPLocation servicesPutting a place on business data from a location provider: an address turned into coordinates or corrected, a base map to draw on, and a route with its distance and duration between two or more points. Storing geometries in the database and querying them there is [graph, spatial and document data](capability:multi-model-data).LoggingCAPBTPABAPUI5LoggingSeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.Low-code appsBTPLow-code appsBuilding an application by arranging UI components, logic flows and formulas in a visual editor instead of writing its code, backend included. Starting a coded project from a template is [generators](capability:generators), and building a native mobile client is [mobile apps](capability:mobile-apps).Mobile appsBTPMobile appsBuilding a native iOS or Android app over business data: onboarding, offline sync against an OData service, device features, and the client that runs on the phone. Distinct from a web app opened in a phone's browser; operating a web app with a finger is [touch operation](capability:ui5-touch-uis).Operations automationBTPOperations automationActing on a running landscape without someone at the console: an alert routed to where a person or a system will pick it up, and a command that troubleshoots or remediates when it arrives. [Logging](capability:logging), [telemetry](capability:telemetry) and [health checks](capability:health-checks) observe; this acts on what they report. Running an application's own recurring work is [job scheduling](capability:job-scheduling).Predictive modelsBTPPredictive modelsTraining, deploying and calling a model that predicts a value from tabular business data: a classification, a regression, a forecast. Distinct from [LLM integration](capability:llm-integration), where a language model generates text, even where both run on the same service.Process automationBTPProcess 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](capability:workflow-integration), and the screen a person approves a task on is [task and approval UIs](capability:task-uis).Prompt managementBTPCAPPrompt 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.Rate limitingCAPBTPRate limitingCapping how many requests a service will accept per tenant or per caller, so one consumer cannot exhaust a shared deployment, whether enforced by a policy in front of the application or inside its own process.Responsibility assignmentBTPResponsibility assignmentResolving who owns a business process, document or work item — a person or a team, from a condition-based rule or from a lookup mapped to an external system — and notifying them, so a framework can ask rather than hard-code an agent. Running the process itself is [process automation](capability:process-automation); the screen the responsible person acts on is [task and approval UIs](capability:task-uis).Retrieval-augmented generationCAPABAPBTPRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.RFC connectivityCAPBTPABAPRFC connectivityCalling ABAP function modules from outside the system over RFC, with destinations and connection pooling handled rather than hand-wired on the calling side.Routing and navigationUI5Routing and navigationTurning a URL hash into a view, and a view change back into a URL — so a deep link, a browser back button and a refresh all land where the user expects in a single-page app.SerialisationABAPSerialisationTurning typed in-memory data into a text or binary format such as JSON, CSV or protobuf and reading it back, including the mapping of names and types the language does not do for you. The protocol that carries the payload is a separate concern: an HTTP or OData client moves the bytes, and serialisation decides what they say.Serve your application over MCPCAPBTPABAPServe 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](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).Source controlABAPSource controlKeeping source code and development objects in version control, comparing their revisions, and moving them between development environments. Managed delivery of changes belongs to [transport management](capability:change-promotion).Static analysisABAPStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.TelemetryCAPABAPBTPTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.TestingCAPBTPTestingProving the service still does what it did — against the model and the handlers, without a deployed system and without a database somebody has to keep clean.ThemingUI5ThemingApplying a consistent visual identity across every control, including the parameters an app may read and the custom themes an organisation may build.Third-party connectorsBTPThird-party connectorsReaching a non-SAP cloud application through a prebuilt connector instead of coding against that vendor's API: the connector holds the credentials and presents the application's resources in one common REST form. Pointing at an endpoint whose API you call yourself is [destinations](capability:destinations), and moving and mapping the messages is [integration flows](capability:integration-flows).Tool governanceCAPABAPBTPTool 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.Trading partner agreementsBTPTrading partner agreementsKeeping track of who business documents are exchanged with and what is set up with each partner: a profile per partner with its contact person, identifiers, communication protocol and B2B standards, an agreement per partner, and one generic flow parameterised from them in place of a flow per partner. What a message looks like and how it maps is [B2B message mapping](capability:b2b-message-mapping), and executing the exchange is [integration flows](capability:integration-flows).TypeScript supportUI5TypeScript supportWriting apps and libraries in TypeScript — the type definitions, the module syntax the loader expects, and the build step that gets from one to the other.UI5 testingUI5UI5 testingProving a UI still works — unit tests over controllers and formatters, integration tests that drive real controls, and end-to-end runs against a served app.Vulnerability scanningBTPCAPUI5Vulnerability scanningFinding known vulnerabilities in the open-source components an application depends on, in the project's dependency tree before it is deployed and in the application once it runs, and following each one until it is fixed. Checking a file somebody uploaded is [malware scanning](capability:malware-scanning), and checking an application's own source for flaws is [static analysis](capability:abap-static-analysis).Web Components interopUI5Web Components interopUsing standards-based custom elements inside an app, and the question of which control set an app should be built from at all, two concerns that are often answered as one.
Demonstrates
Architecture diagramsBTPArchitecture diagramsDrawing the architecture and components of a solution so another person can understand their responsibilities and connections. Shared notation makes diagrams readable across teams.
Entries
Group by137 of 137 entries
EntrySignals
Maintains
@openui5/sap.ui.core@openui5/sap.ui.coreThe OpenUI5 core: the module loader, the MVC runtime, data binding, routing, theming and the test stack, which is everything a UI5 app does before a single community package is added.sap official, ui5
Framework core: module loader, MVC runtime, binding, routing, theming
@sap_oss/vscode-mta-tools@sap_oss/vscode-mta-toolsVS Code Multi-Target Application toolssap official, cap
VS Code Multi-Target Application tools
@sap-ai-sdk/ai-api@sap-ai-sdk/ai-apiThe AI Core API surface of SAP's AI SDK, covering deployments, configurations and the rest of the control plane, as opposed to calling a model.sap official, cap
AI Core control plane API surface of SAP's AI SDK
@sap-ai-sdk/core@sap-ai-sdk/coreThe shared internals that the packages of SAP's AI SDK build on, which its own readme says are not meant to be depended on directly.sap official, cap
Shared internals of SAP's AI SDK
@sap-ai-sdk/foundation-models@sap-ai-sdk/foundation-modelsThe package of SAP's AI SDK that calls foundation models through SAP AI Core and the Generative AI Hub, and the one an application actually reaches for.sap official, cap
Client for foundation models via SAP AI Core and Generative AI Hub
@sap-ai-sdk/orchestration@sap-ai-sdk/orchestrationThe Orchestration Service client of SAP's AI SDK, which applies templating, grounding, filtering and masking around a model call rather than in the application.sap official, cap
Orchestration Service client for templating, grounding and masking
@sap-ai-sdk/prompt-registry@sap-ai-sdk/prompt-registryA package for keeping prompts in SAP's prompt registry rather than in the codebase, so changing a prompt is not a deployment.sap official, cap
Client for prompts kept in SAP's prompt registry
@sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, cap
Destination lookup and connectivity proxy for the Cloud SDK
@sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientThe HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.sap official, cap
HTTP client carrying a destination's credentials
@sap-cloud-sdk/odata-common@sap-cloud-sdk/odata-commonThe shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.sap official, cap
Shared machinery under the Cloud SDK's OData and OpenAPI clients
@sap-cloud-sdk/openapi@sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.sap official, cap
Generated OpenAPI clients for the Cloud SDK
@sap-cloud-sdk/resilience@sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.sap official, cap
Timeouts, retries and circuit breaking around remote calls
@sap-cloud-sdk/util@sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.sap official, cap
General utilities shared across the Cloud SDK packages
@sap-theming/theming-base-content@sap-theming/theming-base-contentThe colour, font and metric definitions of the SAP themes, published as Less, CSS variable, SASS and JSON parameter sets for an HTML framework to read.sap official, ui5
Colour, font and metric definitions of the SAP themes
@sap-ux/cap-config-writer@sap-ux/cap-config-writerSAP's writer module for changing a CAP project's configuration from code, so a tool can add a UI5 app to a project that already exists, returning a mem-fs editor whose commit writes the changes.sap official, cap
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
Writer module for changing a CAP project's configuration from code
@sap-ux/cds-annotation-parser@sap-ux/cds-annotation-parserParses annotations out of CDS source, so tooling can read what a model says about its UI without compiling it.sap official, cap
Parser for annotations in CDS source
@sap-ux/cds-odata-annotation-converter@sap-ux/cds-odata-annotation-converterConverts CDS annotations into their OData form, which is the translation Fiori tooling needs to reason about a service the way a client sees it.sap official, cap
Converter from CDS annotations to their OData form
@sap-ux/create@sap-ux/createSAP Fiori tools as a command: npx @sap-ux/create changes the features of a Fiori project that already exists, through its add, generate, convert, remove, update and change subcommands.sap official, ui5
Command line for changing features of an existing Fiori project
@sap-ux/eslint-plugin-fiori-tools@sap-ux/eslint-plugin-fiori-toolsESLint rules from the Fiori tools team, aimed at the parts of a project their generators produce.sap official, cap
ESLint rules for projects the Fiori tools generators produce
@sap-ux/fe-fpm-writer@sap-ux/fe-fpm-writerA library that writes flexible programming model elements, such as a custom page wired into the app's routing, into a Fiori elements application for OData v4 from Node code.sap official, ui5
Writer of flexible programming model elements into Fiori elements apps
@sap-ux/fe-mockserver-plugin-cds@sap-ux/fe-mockserver-plugin-cdsLets the Fiori Elements mock server take a CDS file as its metadata source, so a UI is developed against the real model before a service exists.sap official, cap
Fiori Elements mock server plugin taking a CDS file as metadata
@sap-ux/fiori-annotation-api@sap-ux/fiori-annotation-apiThe programmatic API Fiori tooling uses to read and write annotations on a project, rather than editing the files as text.sap official, cap
Programmatic API for reading and writing project annotations
@sap-ux/fiori-docs-embeddings@sap-ux/fiori-docs-embeddingsFiori documentation indexed as embeddings, which is what makes it searchable by something other than a person scrolling it.sap official, cap
Fiori documentation indexed as embeddings
@sap-ux/fiori-generator-shared@sap-ux/fiori-generator-sharedThe shared functions and types the Fiori generators are built from; a dependency of theirs rather than a generator itself.sap official, cap
Shared functions and types of the Fiori generators
@sap-ux/fiori-mcp-server@sap-ux/fiori-mcp-serverSAP's Fiori MCP server, run as fiori-mcp, letting a coding assistant create and edit Fiori applications directly rather than describing the steps.sap official, ui5
MCP server for creating and editing Fiori applications
@sap-ux/i18n@sap-ux/i18nA library that reads and writes the i18n bundles of a UI5 or CAP project from Node code, the i18n.properties file of a UI5 app and the i18n folder of a CAP project alike.sap official, ui5
Reader and writer for i18n bundles of UI5 or CAP projects
@sap-ux/odata-service-writer@sap-ux/odata-service-writerA library that adds an OData service to a UI5 project that already exists, writing the file updates from a config object naming the service url, its OData version and a destination.sap official, ui5
Writer that adds an OData service to an existing UI5 project
@sap-ux/odata-vocabularies@sap-ux/odata-vocabulariesCarries the OASIS and SAP OData vocabularies as a package, with a VocabularyService for asking which terms exist, where they apply and what their types and properties are.sap official, ui5
OASIS and SAP OData vocabularies with a VocabularyService
@sap-ux/telemetry@sap-ux/telemetryLibrary for sending usage telemetry datasap official, cap
Library for sending usage telemetry data
@sap-ux/ui5-application-writer@sap-ux/ui5-application-writerA library that writes the base structure of a UI5 project from Node code, out of an app id, title and description, returning a mem-fs editor so a generator needs no template engine of its own.sap official, ui5
Writer of the base structure of a UI5 project from Node code
@sap/ams@sap/amsDecides what a signed-in user may do in a Node.js application that authenticates through SAP Cloud Identity Services, from policies written in DCL.sap official, cap
Authorization from DCL policies for Node.js apps on SAP Cloud Identity
@sap/ams-dev@sap/ams-devCompiles the DCL authorization policies of SAP's Authorization Management Service to DCN, so an AMS-secured application runs and is tested on a laptop.sap official, cap
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
Compiler from AMS DCL policies to DCN for local runs and tests
@sap/approuter@sap/approuterSAP's Node.js application router: the single entry point in front of a business application's microservices, which authenticates the user, forwards each request to a backend by route and serves static content.sap official, btp
SAP's Node.js application router in front of business applications
@sap/e2e-trace@sap/e2e-traceSAP Passport handling for a Node.js component: it reads the identifiers a request arrives with, updates them for the next system, and writes a statistics record per request to standard output.sap official, btp
SAP Passport handling for Node.js components
@sap/hana-client@sap/hana-clientSAP's own Node.js driver for SAP HANA: connect, run SQL and prepared statements, synchronously, through callbacks or as promises, over native client libraries npm installs per platform.sap official, btp
SAP's Node.js driver for SAP HANA
@sap/joule-studio-cli@sap/joule-studio-cliSAP’s CLI package for both legacy Joule digital assistants and the new Joule Studio solution workflow, through the joule and jl commands.sap official, btp
CLI for Joule digital assistants and Joule Studio solutions
@sap/joule-work-dev-cli-early-adopters@sap/joule-work-dev-cli-early-adoptersjl, the pro-code CLI of the new Joule Studio: a solution is a folder with a solution.yaml and typed assets, validated, built into a zip and deployed to Joule Studio's managed runtime, with Claude Code or OpenCode wired in over MCP. Early Adopter Care.sap official, btp
Pro-code CLI for building and deploying Joule Studio solutions
@sap/mdk-mcp-server@sap/mdk-mcp-serverFive tools for Mobile Development Kit work: create a project, generate pages and rules into it, drive the build and deploy, read the documentation, and pull OData metadata from Mobile Services.sap official, btp
It expects a real landscape, not just a project: a `.service.metadata` file naming the Mobile Services app, endpoint and destination, the Cloud Foundry CLI, and access to a BTP Cloud Foundry environment. From 0.4.0 macOS support is ARM64 only — Intel Macs are not supported — alongside Linux and Windows on x64 and ARM64.
MCP server with five tools for Mobile Development Kit work
@sap/ux-cds-compiler-facade@sap/ux-cds-compiler-facadeWraps the CAP CDS compiler behind one set of APIs for annotation handling, so tooling reads a model without tracking which compiler version is installed.sap official, cap
Wrapper around the CDS compiler for annotation handling
@sap/ux-cds-odata-language-server-extension@sap/ux-cds-odata-language-server-extensionAdds the OData annotation features to @sap/vscode-cds, the CDS plug-in for Visual Studio Code: completion, micro-snippets, diagnostics, vocabulary documentation, Go to Definition and an i18n check inside a .cds file.sap official, cap
OData annotation features for the @sap/vscode-cds extension
@ui5/cli@ui5/cliThe UI5 Tooling command line for project setup, the local dev server and the build, which defines a UI5 project's shape and its two extension points, custom middleware and custom tasks.sap official, ui5
UI5 Tooling command line for project setup, dev server and build
@ui5/logger@ui5/loggerUI5 CLI's internal logger, described by its own readme as internal — it appears here because other UI5 tooling depends on it.sap official, ui5
Internal logger of the UI5 CLI
@ui5/tooling-webc@ui5/tooling-webcDeprecated UI5 Tooling extensions that generate UI5 library wrapper projects for UI5 Web Components and serve them during development; the README points to ui5-tooling-modules instead.sap official, ui5
The declared repository is archived.
Deprecated UI5 Tooling extensions for UI5 Web Components wrappers
ABAP AI SDKABAP AI SDKSAP's reuse library for calling a large language model from ABAP code, powered by Intelligent Scenario Lifecycle Management and reaching the models in the Generative AI Hub; delivered with SAP BTP ABAP environment, SAP S/4HANA Cloud Public and Private Edition and SAP S/4HANA.sap official, abap
SAP reuse library for calling large language models from ABAP
ABAP Development Tools for EclipseABAP Development Tools for EclipseSAP's Eclipse plugins for ABAP: source, dictionary and CDS editors, Project Explorer, Outline and ABAP Unit, calling ADT resources on the connected system.sap official, abap
It is an Eclipse install. A development object that is not native-integrated in Eclipse opens in the SAP GUI that is installed locally with the client.
SAP's Eclipse plugins for ABAP development over ADT
ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abap
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
ABAP to JSON serializer and deserializerABAP to JSON serializer and deserializerAn open-source Z* version of SAP's standard /UI2/CL_JSON class, which serialises ABAP data to JSON and reads it back, installed with abapGit and needing SAP_BASIS 7.31 or later.sap official, abap
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
Agent Activation for Dynatrace Service for SAP BTPAgent Activation for Dynatrace Service for SAP BTPInjects the Dynatrace agent into Java applications on SAP BTP, so their metrics, events and end-to-end traces go to a Dynatrace SaaS monitoring environment the customer already runs.sap official, btp
Injects the Dynatrace agent into Java applications on SAP BTP
AgentryAgentryThe SAP BTP service for developing, testing and operating Agentry mobile applications, which take the functions of an SAP back-end system to mobile users.sap official, btp
BTP service for building and running Agentry mobile apps
aicore-skillsaicore-skillsFour agent skills for SAP AI Core, published as a plugin inside SAP's AI Skills Library: admin resources, the deployment lifecycle, the foundation models in the Generative AI Hub, and the Context Registry behind tabular prediction.sap official, btp
Four agent skills for SAP AI Core in SAP's AI Skills Library
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
API proxies with security and traffic policies and Developer Hub
Application AutoscalerApplication AutoscalerA Cloud Foundry service that raises or lowers the number of an application's instances by the scaling rules and schedules in a policy the developer defines.sap official, btp
Scales Cloud Foundry app instances by policy rules and schedules
Application Vulnerability ReportApplication Vulnerability ReportA BTP service that tracks vulnerabilities in the open-source components of applications deployed in a BTP landscape, with an OData API for taking the report into ticketing systems.sap official, btp
Tracks vulnerabilities in open-source components of BTP apps
btp-setup-automatorbtp-setup-automatorA containerised script that sets up an SAP BTP account from JSON configuration files: entitlements, subscriptions, service instances, administrators and role collections, instead of clicking through the cockpit.sap official, btp
The declared repository is archived.
Containerised script setting up an SAP BTP account from JSON config
cds-textmate-grammarcds-textmate-grammarThe TextMate grammar for the CDS language, which highlights .cds files where the CDS language server does not run, most visibly in GitHub's own file viewer through Linguist.sap official, cap
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
TextMate grammar for the CDS language
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
SAP's on-premises agent linking SAP BTP to customer-network systems
Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp
Builds and runs integration flows between cloud and on premise
Cloud Integration AutomationCloud Integration AutomationA guided, role-based workflow that partially automates the technical configuration steps needed to integrate an SAP cloud solution with on-premise and other SAP cloud solutions.sap official, btp
Guided workflow for configuring SAP cloud solution integration
code pal for ABAPcode pal for ABAPATC and Code Inspector checks for the parts of Clean ABAP a static analyser can actually check, installed into a system with [abapGit](artifact:abapgit-abapgit) rather than delivered with it.sap official, abap
This is the legacy edition, for on-premise systems from SAP_BASIS 7.40. On ABAP Cloud, [the Cloud Edition](artifact:sap-code-pal-for-abap-cloud) is the one that runs.
ATC and Code Inspector checks for Clean ABAP
code pal for ABAP — Cloud Editioncode pal for ABAP — Cloud EditionThe same Clean ABAP check set for ABAP Cloud, where the legacy edition cannot run.sap official, abap
Clean ABAP check set for ABAP Cloud
Data Attribute RecommendationData Attribute RecommendationTrains and deploys machine learning models that classify records such as products or users into categories and predict a missing numerical attribute from free text, numbers and categories, over a REST API.sap official, btp
ML models that classify records and predict attributes
hdbhdbSAP's HANA driver for Node.js, written entirely in JavaScript so installing it pulls in no native client, running SQL against SAP HANA and SAP HANA Cloud with streams and prepared statements.sap official, btp
Its own feature comparison marks connection pooling, automatic reconnect, active-active reads, client-side data encryption, statement distribution, Kerberos authentication, the hdbuserstore, promises and TypeScript types as [@sap/hana-client](https://www.npmjs.com/package/@sap/hana-client) only, so a service that wants a pool or a promise API writes both itself over a callback interface. OpenSSL is its one security provider where the other driver lists SAP CommonCryptoLib, OpenSSL and MSCrypto, and it runs on Node.js 18 or later.
Pure JavaScript SAP HANA driver for Node.js
Integration AdvisorIntegration AdvisorSpecifies B2B message interfaces and the mappings between them from a library of standards, and generates the schemas and scripts an integration flow runs, inside SAP Integration Suite.sap official, btp
B2B interface and mapping specification in Integration Suite
Intelligent Situation AutomationIntelligent Situation AutomationResolves SAP S/4HANA and SAP S/4HANA Cloud business situations automatically by applying business rules, as an extension of Situation Handling with a dashboard over the time it saves.sap official, btp
Rule-based resolution of SAP S/4HANA business situations
Joule in SAP Build CodeJoule in SAP Build CodeJoule's generative AI inside SAP Build Code, pitched as "optimized for Java and JavaScript application development": opened from SAP Business Application Studio's activity bar, slash commands generate a CAP data model, services, sample data, business logic and a Fiori elements UI.sap official, cap
Joule's generative AI inside SAP Build Code
Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrella
SAP's managed environment for building custom agents and workflows
Joule 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
Low-code SAP Build capability for custom Joule skills and agents
Joule WorkJoule WorkSAP’s workspace where people express a goal, work with the results in contextual Spaces and direct Joule Assistants and Joule Agents across SAP and third-party systems.sap official, umbrella
SAP's workspace for conversations, Spaces and directing agents
OAuth 2.0 on SAP BTPOAuth 2.0 on SAP BTPOAuth 2.0 protection for applications and APIs on SAP BTP, listed in Neo regions: the authorization code grant for web applications and the client credentials grant for API and IoT scenarios.sap official, btp
OAuth 2.0 grant flows for applications and APIs in Neo regions
Open ConnectorsOpen ConnectorsPrebuilt connectors to non-SAP cloud applications, each instance called as a harmonised RESTful API, inside SAP Integration Suite.sap official, btp
Prebuilt connectors to non-SAP cloud applications as REST APIs
Personalized RecommendationPersonalized RecommendationTrains and deploys a machine learning model over a website visitor's browsing history and item attributes, and serves next-item, similar-item, smart-search and user-affinity recommendations from it over a REST API.sap official, btp
Machine learning recommendations over browsing history via REST
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
AI runtime on BTP with the Generative AI Hub
SAP Alert Notification service for SAP BTPSAP Alert Notification service for SAP BTPA BTP service with one API for publishing alerts and subscribing to them: built-in events about BTP resources and an application's own, delivered to a communication channel or monitoring tool.sap official, btp
Publishing and subscribing to alerts about BTP resources and apps
SAP ASE ServiceSAP ASE ServiceSAP ASE database systems and tenant databases on BTP with SAP running the platform operations, used from Java applications on BTP or on premise over SQL, JPA and JDBC.sap official, btp
Managed SAP ASE databases on BTP for Java applications
SAP Automation PilotSAP Automation PilotA BTP service that runs operations commands: catalogues SAP ships for BTP DevOps scenarios and commands a team composes, started by hand, on a schedule or by an event.sap official, btp
Runs operations commands on BTP by hand, schedule or event
SAP BTP ABAP environmentSAP BTP ABAP environmentSAP's ABAP runtime on BTP: ABAP systems developed in the ABAP Cloud model on SAP HANA Cloud, for cloud apps, OData services and side-by-side extensions of SAP S/4HANA.sap official, btp
1 of 8 plans deprecated.
ABAP runtime on BTP for the ABAP Cloud model
SAP BTP, Cloud Foundry RuntimeSAP BTP, Cloud Foundry RuntimeThe Cloud Foundry runtime of SAP BTP: memory for applications in a Cloud Foundry org, run from SAP's Java, Node.js and Python buildpacks or community buildpacks and managed with the standard Cloud Foundry tools.sap official, btp
Cloud Foundry runtime of SAP BTP for polyglot applications
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
Managed Kubernetes runtime on SAP BTP based on Kyma
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
Low-code platform for web and native mobile apps
SAP Build CodeSAP Build CodeSAP's development environment on BTP for SAPUI5, SAP Fiori, mobile and CAP applications that run on the SAP BTP, Cloud Foundry Runtime, in which Joule generates models, services, logic, tests and apps.sap official, btp
Development environment on BTP for UI5, Fiori, mobile and CAP
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
Low-code and no-code tool for business processes and RPA bots
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
Business sites and digital workspaces with collaboration tools
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
Role-based business site for SAP and third-party apps
SAP Business Application StudioSAP Business Application StudioSAP's development environment for business applications, delivered as a cloud service and opened in a browser, where work happens in preconfigured dev spaces.sap official, btp
Browser-based development environment with dev spaces
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
Distributes business events between SAP cloud applications
SAP Cloud Identity Services - Identity ProvisioningSAP Cloud Identity Services - Identity ProvisioningProvisioning jobs that carry users and groups, with their authorisations, between cloud and on-premise business systems, SAP and non-SAP, in full or delta read mode.sap official, btp
Provisioning jobs carrying users and groups between systems
SAP Cloud LoggingSAP Cloud LoggingAn instance-based observability service built on OpenSearch that stores and analyses logs, metrics and traces from Cloud Foundry, Kyma, Kubernetes and other runtime environments.sap official, btp
OpenSearch-based store for logs, metrics and traces
SAP Cloud Management Service for SAP BTPSAP Cloud Management Service for SAP BTPREST APIs for the administration of a BTP account: directories and subaccounts, entitlements and quotas, subscriptions to multitenant applications, environment instances, and the events those operations raise.sap official, btp
REST APIs for administering a BTP account
SAP Cloud Portal ServiceSAP Cloud Portal ServiceSAP's BTP service for role-based portal sites: pages, apps and widgets behind single sign-on for employees, customers and partners, with content from SAP products and other providers.sap official, btp
Role-based portal sites with pages, apps and widgets
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
Moves MTA archives and content between SAP BTP accounts
SAP Content Agent ServiceSAP Content Agent ServiceA BTP service that assembles content from other BTP services into an MTAR with its dependencies, then downloads it, exports it to a transport queue or imports it into another subaccount.sap official, btp
Assembles BTP service content into an MTAR for transport
SAP Continuous Integration and DeliverySAP Continuous Integration and DeliveryA BTP service that runs SAP's predefined CI/CD pipelines for designated SAP development projects, building, testing and deploying the changes pushed to a connected Git repository.sap official, btp
Predefined CI/CD pipelines for SAP development projects
SAP Custom Domain ServiceSAP Custom Domain ServiceExposes a BTP application publicly under the customer's own domain instead of the default subdomain, with the TLS/SSL certificate and TLS configuration that domain is served with.sap official, btp
Serves BTP applications under the customer's own domain
SAP Customer Identity and Access Management for B2CSAP Customer Identity and Access Management for B2CSAP's customer identity service: registration, login and consent for the users of a company's websites and apps, kept in one profile per customer, with regional data storage and risk-based authentication as options.sap official, btp
Registration, login and consent for customer-facing sites
SAP Data Privacy IntegrationSAP Data Privacy IntegrationA reuse service whose APIs an application calls for its data privacy duties: retention rules and deletion at the end of purpose, reports of the personal data held, and anonymisation of unstructured data.sap official, btp
APIs for retention, deletion and personal data reports
SAP Data Quality Management, microservices for location dataSAP Data Quality Management, microservices for location dataA BTP service of APIs for address cleansing, geocoding, reverse geocoding and type-ahead address suggestions, embedded into a business process or application.sap official, btp
APIs for address cleansing, geocoding and suggestions
SAP Data Retention ManagerSAP Data Retention ManagerA BTP service that holds residence and retention rules for applications' personal and transactional data, and triggers blocking, deletion, archiving and destruction.sap official, btp
Retention rules triggering blocking, deletion and archiving
SAP Document Management service, application optionSAP Document Management service, application optionA standalone, ready-to-use web application for enterprise content, with file and folder management, viewers, versioning and status, over SAP's own repository or a CMIS-compliant one.sap official, btp
Ready-to-use web application for enterprise content
SAP Document Management service, integration optionSAP Document Management service, integration optionA BTP service of APIs and a reusable UI5 component for adding document management, with folders, versions and status, to a business application over SAP's repository or a CMIS-compliant one.sap official, btp
APIs and a UI5 component for document management in apps
SAP Forms Service by AdobeSAP Forms Service by AdobeAdobe Document Services on BTP: renders print and interactive PDF forms from stored templates, called over a REST API from a cloud application or connected to an ABAP system.sap official, btp
Adobe Document Services on BTP for print and interactive PDFs
SAP HANA Service (SAP Regions) for SAP BTPSAP HANA Service (SAP Regions) for SAP BTPManaged SAP HANA 2.0 database systems in fixed sizes from 64 GB to 1 TB, in SAP's own regions, with tenant databases bound to applications on SAP BTP.sap official, btp
Managed SAP HANA 2.0 databases in fixed sizes on SAP BTP
SAP HANA Spatial Services for SAP BTPSAP HANA Spatial Services for SAP BTPA BTP service of four APIs, geocoding, map tiles, routing and matrix routing, over a third-party location provider whose licence the customer brings, returning results to combine with business data.sap official, btp
APIs for geocoding, map tiles and routing
SAP Health Data Services for FHIRSAP Health Data Services for FHIRA cloud-native implementation of the HL7 FHIR standard for designing, storing and exchanging health-related data, reached through REST APIs and messaging endpoints and extended with custom resources and FHIR profiles.sap official, btp
HL7 FHIR implementation for storing and exchanging health data
SAP Integration Suite, Event MeshSAP Integration Suite, Event MeshThe event broker activated inside SAP Integration Suite: queues, topic subscriptions and webhook subscriptions, reached over AMQP, MQTT and HTTP.sap official, btp
Event broker inside SAP Integration Suite
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
SAP's AI engagement layer across SAP applications
SAP Joule for Developers, ABAP AI capabilitiesSAP Joule for Developers, ABAP AI capabilitiesSAP's AI for ABAP development in ADT for Eclipse and VS Code: chat, code completion, explain, test and CDS generation, RAP logic prediction, and since June 2026 an agentic mode over the ADT MCP Server, metered in AI units through the ABAP AI Hub Service on BTP.sap official, abap
SAP's AI for ABAP development in ADT for Eclipse and VS Code
SAP Keystore ServiceSAP Keystore ServiceA repository for cryptographic keys and certificates in SAP BTP's Neo data centres, which an application retrieves at runtime for signing, encryption and SSL communication.sap official, btp
Key and certificate repository in SAP BTP's Neo data centres
SAP Master Data IntegrationSAP Master Data IntegrationA multi-tenant cloud service that replicates master data between two or more clients, giving a hybrid landscape a consistent view of it, with filters set through SAP Business Data Orchestration service.sap official, btp
Cloud service replicating master data across a hybrid landscape
SAP Mobile ServicesSAP Mobile ServicesThe SAP BTP service behind native and cross-platform mobile apps over enterprise data: authentication and security policies, offline OData sync, push, MDK app updates and usage reporting.sap official, btp
2 of 8 plans deprecated.
SAP BTP service for native and cross-platform mobile apps
SAP Monitoring Service for SAP BTPSAP Monitoring Service for SAP BTPMetrics, availability and JMX checks, and email or webhook alerts for Java, HTML5 and SAP HANA XS applications and database systems, in Neo regions of SAP BTP.sap official, btp
Metrics, availability checks and alerts for apps in Neo regions
SAP Personal Data ManagerSAP Personal Data ManagerA BTP service that finds data subjects, tells them which of their personal data an application or service stores and uses, and handles their requests about it.sap official, btp
Service answering data subjects about their stored personal data
SAP Print serviceSAP Print servicePrint queues between cloud applications and a customer's local printers: an application queries queues and creates print queue items through public APIs, and the queues are managed in the service.sap official, btp
Print queues between cloud applications and local printers
SAP Private Link ServiceSAP Private Link ServiceA private network connection between a selected SAP BTP service and a selected service in an application's own account with a partner cloud provider, so the traffic between them never touches the public internet.sap official, btp
Private network link between a BTP service and a partner cloud
SAP Responsibility Management serviceSAP Responsibility Management serviceA BTP service that resolves who is responsible for a business process, object or work item from condition-based rules or teams, and notifies them, for a workflow or another framework to call.sap official, btp
Resolves who is responsible for a process or item, and notifies them
SAP Service ManagerSAP Service ManagerThe BTP registry for service brokers and environments: consumes SAP BTP services from any connected runtime environment, tracks the service instances created, and shares them between environments.sap official, btp
Registry for service brokers, instances and environments on SAP BTP
SAP Solution Lifecycle Management service for SAP BTPSAP Solution Lifecycle Management service for SAP BTPDeploys, updates, monitors and deletes Solutions in the Neo environment of SAP BTP, each carried by a Multitarget Application archive, and subscribes a subaccount to a multitenant Solution provided by another.sap official, btp
Deploys and manages MTA-based Solutions in the Neo environment
SAP Translation HubSAP Translation HubSAP's translation service for software texts and documents, drawing on repositories of verified and company translations and on machine translation by SAP's neural MT or large language models.sap official, btp
Translation service for software texts and documents
SAP Usage Data Management Service for SAP BTPSAP Usage Data Management Service for SAP BTPREST APIs that return BTP usage per metric for an account, directory or region, monthly or daily, and monthly cost per subaccount under the CPEA consumption-based model.sap official, btp
REST APIs for SAP BTP usage per metric and monthly cost
SAP Web IDE Full-StackSAP Web IDE Full-StackSAP's IDE service on BTP for SAPUI5 and SAP Fiori apps, full-stack SaaS applications, SAP S/4HANA extensions, hybrid mobile apps and IoT apps, with an SDK for extending the IDE itself.sap official, btp
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
sap-fiori-guidelinessap-fiori-guidelinesAn agent skill SAP publishes in its AI Skills Library, built from the Fiori Design Guidelines at v1.145: eighteen reference files an agent reads before it picks a control, a page type or an AI pattern.sap official, ui5
Agent skill built from the Fiori Design Guidelines
sap-fiori-iossap-fiori-iosAn agent skill SAP publishes for SAP Fiori for iOS: it maps a node of the Fiori iOS UI Kit in Figma onto SwiftUI code, and answers which Fiori component a Figma variant becomes.sap official, btp
Agent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUI
sap-tutorials-contentsap-tutorials-contentAn agent skill that maps the public developers.sap.com content API: the catalogue, the navigation, a tutorial's HTML or JSON, and full-text search, all anonymous and read-only.sap official, btp
Agent skill mapping the developers.sap.com content API
SAP/automation-pilot-agent-skillsSAP/automation-pilot-agent-skillsEight skills for writing, reviewing and operating SAP Automation Pilot content — command generation, catalogue exploration, code review, the content and executions APIs, debugging, schedules, and generating an MCP server from a command.sap official, btp
It works against a tenant, through the REST API, with credentials in the environment — so these skills act rather than advise, and the review skill is a check on generated content rather than a substitute for one. Nothing here is useful without an Automation Pilot tenant to point at.
Eight skills for writing and operating SAP Automation Pilot content
SAP/leanix-ai-pluginsSAP/leanix-ai-pluginsOne Claude Code plugin, sap-leanix, bundling two skills that build and debug LeanIX automation scripts and create and manage calculations, both working through the LeanIX MCP server.sap official, btp
Enterprise-architecture work, not development: this describes what your landscape records, never what your code does. And the skills assume the server — without [the LeanIX MCP server](artifact:sap-leanix-mcp-server) reachable against your instance, they are instructions with nothing to call.
Claude Code plugin with two skills for SAP LeanIX scripting
SAP/ui-theme-designer-plugins-for-coding-agentsSAP/ui-theme-designer-plugins-for-coding-agentsOne plugin that teaches a coding agent the SAP Design System, Fiori design tokens, and which theming parameters a given control actually reads, installed into Claude Code or GitHub Copilot.sap official, ui5
Knowledge about theming, not a theme build: nothing here compiles a theme or deploys one, and it says nothing about a custom control's own parameters.
Agent plugin on the SAP Design System and theming parameters
Terraform Provider for SAP BTPTerraform Provider for SAP BTPThe plugin that lets a Terraform or OpenTofu configuration manage the resources of an SAP BTP global account, from directories and subaccounts to entitlements, role collections and subscriptions.sap official, btp
Terraform and OpenTofu provider for SAP BTP global accounts
Trading Partner ManagementTrading Partner ManagementPartner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of Cloud Integration so one flow serves every partner, inside SAP Integration Suite.sap official, btp
Partner profiles and agreements for B2B exchange in Integration Suite
UI flexibility serviceUI flexibility serviceKey-user adaptation and personalisation for UI5 applications on SAP BTP: UI changes, shared views, drafts and versions, stored by the service and applied at runtime.sap official, btp
Key-user adaptation and personalisation for UI5 apps on SAP BTP
vscode-ui5-language-assistantvscode-ui5-language-assistantSAP's VS Code extension for SAPUI5 and OpenUI5: completion, validation, hover tooltips, go to definition, quick fix and formatting for XML views, and completion and validation for manifest.json.sap official, ui5
VS Code extension for SAPUI5 and OpenUI5 XML views and manifest
Maintains: samples, sketches and references
abap-file-formatsabap-file-formatsSAP's specification for how ABAP objects serialise to files, which makes the on-disk form of an ABAP object a published contract rather than a tool's private choice.sap official, abap
SAP's specification for serialising ABAP objects to files
ADT resourcesADT resourcesThe HTTP endpoint an ABAP system exposes as the adt ICF service under /sap/bc/adt, so a client outside the system can reach development objects, delivered with the platform rather than installed.sap official, abap
A client that cannot reach the adt ICF service over HTTP has nothing to call.
HTTP endpoint under /sap/bc/adt exposing ABAP development objects
API CompositionAPI CompositionOne API over the business data in a landscape: a business data graph queried with OData V4 or GraphQL, instead of each source system's own API.sap official, btp
Business data graph queried with OData V4 or GraphQL
Clean ABAPClean ABAPSAP's open, versioned style guide for ABAP: the answer to how a piece of ABAP should be written, an agreement a team adopts rather than anything to install.sap official, abap
Open, versioned style guide for ABAP
Cloudification RepositoryCloudification RepositorySAP's list of released APIs for SAP Cloud ERP, with the successors of the objects that are not released — the content the ABAP test cockpit's cloud readiness and clean core checks are pointed at.sap official, abap
It is a catalogue of SAP's objects and not a reading of your code: it states that an object is not released, never that you used it, and the finding is the ATC check's. For SAP Cloud ERP Private the files exist for feature pack stack releases only, with no update per support package, so a system between two stacks is checked against its stack's file.
SAP's list of released APIs for SAP Cloud ERP with successors
SAP AI LaunchpadSAP AI LaunchpadThe SaaS front end over SAP AI Core on BTP: a Model Library, Grounding Management for document pipelines, Workspaces that connect AI runtimes, and ML Operations for the lifecycle of a scenario.sap official, btp
SaaS front end over SAP AI Core
SAP BTP Solution Diagram GuidelinesSAP BTP Solution Diagram GuidelinesSAP's visual language for BTP solution diagrams, in line with the SAP Fiori Horizon principles and colour palette, with editable templates for draw.io and PowerPoint.sap official, btp
SAP's visual language and templates for BTP solution diagrams
SAP/architecture-centerSAP/architecture-centerThe repository the SAP Architecture Center site is built from: SAP's reference architectures, each drawn as editable draw.io diagrams, with Mermaid for flows.sap official, btp
Source repository of SAP's reference architectures
Writing and topics
14 of 14 pieces
Piece, what it offersStill applies
Access to Generative AI ModelsAccess to Generative AI ModelsSets 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 integration takes on the BTP door; the page's implementation sections sit behind its steps and were not read.
Agentic AI Security & GovernanceAgentic AI Security & GovernanceNames 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 governance is named for.
Content FilteringContent FilteringContent 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 Core produces content meeting a stated safety standard, which is the ground content filtering covers on the BTP door.
Custom Joule SkillsCustom Joule SkillsA 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 Studio 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.
Data MaskingData MaskingData 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 Core 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 masking takes on the BTP door.
Document GroundingDocument GroundingDocument Grounding is a managed retrieval-augmented-generation service under the Generative AI Hub on BTP, which SAP's page on SAP AI Core 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.
Content-based Agents with SAP Joule Studio Agent BuilderContent-based Agents with SAP Joule Studio Agent BuilderJoule Studio, classic edition, 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 Services, and can be tried against a test conversation before deployment. That is the tool-and-turn-taking ground agent tooling covers, here built through Joule Studio rather than in application code.
Model Context Protocol (MCP)Model Context Protocol (MCP)Frames 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 Suite'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 servers covers; for security it points at a separate page.
Pro-Code AI AgentsPro-Code AI AgentsPro-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 tooling covers, building an agent's own tool-calling loop rather than exposing an application to somebody else's agent.
Prompt TemplatingPrompt TemplatingPrompt 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 Core 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 management as a stored and managed object rather than a string embedded in the caller.
Vector RAG vs Graph RAGVector RAG vs Graph RAGA section introduction rather than the comparison itself: it states that the choice between Vector RAG and Graph RAG depends on the domain and the task, and that Vector RAG is the one to use when the subject area has a clear description and the model must be held to specific data structures and attribute values. The four sub-pages it introduces, two on vector-based and two on graph-based RAG, carry the comparison. It sits on the same retrieval question retrieval-augmented generation answers, without naming CDS, CAP or a store.
Configure an MCP Server Created from an HTTP EndpointConfigure an MCP Server Created from an HTTP EndpointDocuments configuring API Management’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.
MCP Server — SAP Integration SuiteMCP Server — SAP Integration SuiteSAP's own page for the MCP Server artifact in SAP Integration Suite, 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.
API Policy - FAQAPI Policy - FAQSAP’s June 2026 FAQ, version 1.3, explains the scope and use conditions of the SAP API Policy, including published and non-published APIs, ADT developer access, AI-driven usage and third-party MCP servers. It also addresses data extraction and the responsibilities of customers and partners. The FAQ is informational: it does not modify contracts, and applicable agreements and product documentation prevail if they conflict with it.
Details
History
- @openui5/sap.ui.coreThe edge carried no source, so what the package answers for this capability was an unattributed claim. The three parts are each stated by SAP's own documentation, and the level the package covers, unit and integration, is the comparison the capability now declares. End-to-end is left absent rather than entered as a no: the OPA page's restrictions are the capability's boundary and are recorded there. The other six edges were not read for this job and are unchanged.
- @sap-ai-sdk/foundation-modelscapability:llm-integration declared model_access and response_streaming on 2026-10-15. The package's own chat-completion page, read the same day, states that its chat client streams over server-sent events, which is the fact that decides whether a chat surface can show an answer as it is written; the edge rested on the repository README alone before.
- @sap-ai-sdk/orchestrationcapability:llm-integration declared model_access and response_streaming on 2026-10-15. The orchestration chat-completion page, read the same day, states that the model is the name property of the promptTemplating configuration and that the harmonised API behind it lets a different model be used without the client code changing, and that the client streams over server-sent events. Both facts decide something for a reader and neither was on the edge.
- @sap-ux/telemetryTelemetry curation for the CAP door. The entry stood among the options a reader compares for observing a running CAP service, and its own README places it elsewhere: a library SAP Fiori tools use to collect anonymous usage data. The sentence is recorded so the page states what it is; whether the edge, the cds-plugin type and the CAP door are right is left for review rather than changed here.
- @sap/approuterThe edge said the router logs the user in and propagated the user information, which on a capability page reads as though the backends were covered. The README's two sentences on that are now quoted on the edge, and the property the BTP door compares on, whether an option passes the signed-in user onward, rests on SAP's own architecture page for the gateway.
- @sap/approuterThe UAA sentence was read again in the 23.0.0 README during this pass and was still there.
- @sap/joule-studio-cliCurrent 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.
- aicore-skillscapability: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.
- Cloud ConnectorThe 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.
- Joule StudioThe product overview describes "Workflows and integrations for both SAP and non-SAP systems." It also names CAP development; RA0029 places customer agents on BTP. These establish served views, while the new SAP-managed environment has no separate BTP catalogue listing established by this intake.
- Joule StudioThe 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.
- Joule WorkRA0029 describes the workspace across SAP and non-SAP systems: "Users express a goal and Joule orchestrates actions across SAP and non-SAP systems to get it done." Its customer-managed BTP agents connect to Joule, establishing the BTP served view; no separate BTP catalogue listing for Work was established.
- Joule WorkThe 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.
- OAuth 2.0 on SAP BTPThe announced end was only in the paragraph, so a reader comparing the authentication options behind the BTP door met this one as an equal of the others. SAP's catalogue record states it, and the field is where the statement is shown as the maker's own.
- OAuth 2.0 on SAP BTPThe 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.
- SAP/automation-pilot-agent-skillscapability:agent-guidance declared the installs_into property on the BTP door. The README's prerequisites table names Claude Code as required to use the skills and names no other host, so the value is one entry rather than a list.
- SAP/automation-pilot-agent-skillsThe 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-pluginscapability:agent-guidance declared the installs_into property on the BTP door. The README's setup section states the skills follow the open Agent Skills standard and links one loading guide per client, so each value carries the line that names it. The plugin marketplace route is Claude Code's alone, which is why that client is both in the install command and in the list.
- SAP/leanix-ai-pluginsThe 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.
- SAP/ui-theme-designer-plugins-for-coding-agentscapability:agent-guidance widened the installs_into property to the UI5 door. The plugin's own README carries two install commands, one for the Claude Code marketplace and one for the Copilot one, and a third route through the skills command line that names no client.
- SAP/ui-theme-designer-plugins-for-coding-agentsThe plugin's own README read on 2026-10-15 lists parameter inheritance beside component consumption in the design-tokens skill, and the entry said nothing about how the plugin gets in front of an agent. Both are facts a reader needs before the parameter mapping is any use to them.
- API ManagementThe comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
- API ManagementConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- API ManagementConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- API ManagementConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- API ManagementConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- API ManagementPreserves the documented 30/50 tool-limit conflict as a condition for selecting a deployment; the HTTP creation-guide quotation is now attached explicitly alongside the API-artifact and configuration citations.
- API ManagementResolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions.
- API ManagementIndependent review found that the MCP-specific uncertainty does not describe a situation in which the whole API gateway service is the wrong choice.
- API ManagementIndependent source review supports prompts guiding agent interaction rather than templates; retains both sourced tool-count limits as an explicit MCP-specific discrepancy.
- aicore-skillsThe 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-contentA 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-guidelinesRead 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. Hard rule 7: skills are indexed, never authored here.
- sap-fiori-iosRead 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.
- @sap_oss/vscode-mta-toolsThe old repository's README says it has moved to the app-studio-toolkit monorepo; the edge now cites the README at the new address.
- API CompositionAn 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.
- Cloud IntegrationThe 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.
- SAP Cloud Management Service for SAP BTPSAP'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.
- aicore-skillsRead 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 Build Work Zone, advanced editionSAP'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 editionSAP'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 Private Link ServiceSAP'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).
- API ManagementMoved 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.
- Cloud IntegrationThe 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.
- @sap/approuterThe 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.
- Cloud ConnectorThe 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.
- SAP Cloud Identity Services - Identity ProvisioningSAP's catalogue names Identity Provisioning as one of the services SAP Cloud Identity Services include. The first `part_of` on an artifact.
- SAP Document Management service, integration optionAdd 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/approuterThe description already named the services the router binds to, so a reader could see them and not walk to them. Each is now an edge resting on the README sentence that states the binding.
- @sap/approuterSAP'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.
- @sap-ai-sdk/orchestrationPrompt management, data masking and content filtering entered as capabilities on 2026-09-14, each an orchestration module in SAP AI Core; this package is the client for all three and carried only the broader LLM integration edge.
- @sap-ai-sdk/prompt-registryPrompt management entered as a capability on 2026-09-14 with SAP AI Core's Prompt Registry as the core answer; this package is that registry's client and had only the broader LLM integration edge.
- @ui5/loggerFiled under logging, which is a running service's log output. This is the UI5 CLI's internal logger, described by its own README as internal — it answers nothing a reader would pick for logging, and belongs where the tooling that depends on it lives.
- @sap-ux/fiori-mcp-serverMCP is how this is delivered, not what it answers — artifact_type carries the transport. It helps an agent work on real code rather than exposing a running service to one, which is a different capability.
- @sap-ux/fiori-mcp-serverIt creates and edits Fiori applications and ships from SAP/open-ux-tools; nothing about it is CAP's. Typed cap by placement, which defaults every candidate to the primary door. serves_ecosystems keeps it behind the CAP door, where a CAP developer building a Fiori front end still finds it.
- @sap-ux/fiori-mcp-serverlinks.repo is the whole of SAP/open-ux-tools, which carries much else besides this. Naming the package directory says which part of the monorepo the artifact is — and it is what lets a sweep tell this entry apart from the next package in the same repository.
- @sap/mdk-mcp-serverEntered 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/automation-pilot-agent-skillsEntered 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-pluginsEntered 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.
- SAP/ui-theme-designer-plugins-for-coding-agentsEntered 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-ai-sdk/ai-apiTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ai-sdk/ai-apiPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ai-sdk/coreTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ai-sdk/corePlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ai-sdk/foundation-modelsTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ai-sdk/foundation-modelsPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ai-sdk/orchestrationTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ai-sdk/orchestrationPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ai-sdk/prompt-registryTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ai-sdk/prompt-registryPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/connectivityTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/connectivityPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/http-clientTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/http-clientPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/odata-commonTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/odata-commonPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/openapiTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/openapiPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/resilienceTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/resiliencePlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-cloud-sdk/utilTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-cloud-sdk/utilPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/cds-annotation-parserTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/cds-annotation-parserPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/cds-odata-annotation-converterTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/cds-odata-annotation-converterPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/eslint-plugin-fiori-toolsTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/eslint-plugin-fiori-toolsPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/fe-mockserver-plugin-cdsTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fe-mockserver-plugin-cdsPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/fiori-annotation-apiTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fiori-annotation-apiPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/fiori-docs-embeddingsTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fiori-docs-embeddingsPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/fiori-generator-sharedTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fiori-generator-sharedPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @sap-ux/fiori-mcp-serverTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @sap-ux/fiori-mcp-serverPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- @ui5/loggerTyped cds-plugin by placement, which defaults every candidate to that. It is not one.
- @ui5/loggerPlacement assumes cap for everything it accepts.
- @ui5/loggerPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- First entry seenDiscovered via bestofui5, npm registry, The discovery pass, npm registry · npm:sap cap plugin, GitHub API · SAP/open-ux-tools, GitHub API · SAP, npm registry · npm:scope:@sap, npm registry · npm:cds-plugin, Added by hand, sap-ai-mcp-servers, npm registry · npm:cds-, GitHub API, SAP AI Skills Library · github.com/SAP/ai-skills-library, SAP AI Skills Library · github.com/SAP/ai-skills-library — skills/sap-fiori-guidelines, SAP AI Skills Library · github.com/SAP/ai-skills-library — skills/sap-fiori-ios, SAP AI Skills Library · skills.cloud.sap.
For your agent
- Ref
actor:sap- JSON
- /actors/sap.json
- MCP
- Connecting an agent