Every lesson from the SAP Trainer is added here, with explanations, diagrams, quizzes, follow-ups and sources. The contents on the left are organised by week and jump to each section.

The search covers all text. Lessons without matches are hidden and matches are highlighted.

This is the British English version. Deutsche Version

Trial lessonSaturday, 14 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

SAP Cloud Transport Management service (cTMS)

Short definition

cTMS is a cloud service on SAP BTP that transports development content such as UI5 apps, MTA projects, ABAP Cloud objects or iFlows across different subaccounts. For BTP, it therefore plays the role that STMS and CTS play in the ABAP world. It is aimed mainly at development teams and system administrators who want to move BTP content securely and consistently.

Context

cTMS is part of software logistics on BTP. SAP Continuous Integration and Delivery, SAP Business Application Studio and SAP Cloud Transport Management are part of SAP Build. Upstream, cTMS connects to the change management tools: SAP Cloud ALM and SAP Solution Manager.

cTMS transport landscape with SAP Cloud ALMSAP Cloud ALM controls deployments; cTMS transports content through DEV, QAS and PROD nodes in separate subaccounts. SAP Cloud ALM Features, approvals, deployment Cloud Transport Management DEV node Export from source QAS node Test subaccount PROD node Production subaccount Content: MTAs, UI5 apps, iFlows, ABAP Cloud objects
Cloud ALM controls, cTMS transports along the nodes DEV → QAS → PROD.

In depth

How it works and its building blocks

cTMS does not work on its own. It is an additional service that has to be integrated into the existing development processes of the cloud services or applications whose content it transports. The source tool exports content to cTMS, and cTMS then distributes it along the landscape. Transports can be triggered directly from tools that have been enabled for this, for example the web UI of SAP Cloud Integration.

The landscape consists of transport nodes, each representing a target subaccount or target system, and transport routes between these nodes. A node is connected to its target through a destination, in Cloud Foundry for example to the deploy service of the relevant space. For exports you need a service instance, which is created in a space of the subscribing subaccount.

The range of supported environments has grown. cTMS manages transports between accounts in different environments such as Cloud Foundry, ABAP and Neo. Since release 2302, lifecycle management for the BTP ABAP Environment can be integrated with cTMS, and since version 2023.16 SAP Analytics Cloud can transport Content Network packages via cTMS.

How cTMS worksThe source tool exports to cTMS, which forwards content via a transport route into the target subaccount. Source toolTriggers export cTMSService instance Transport routeNode to node Target accountvia destination
Content travels from the source tool via cTMS and the route to the target subaccount.

How it differs from similar terms

  • CTS/STMS: transports ABAP transport requests between ABAP systems. cTMS transports cloud content between subaccounts and environments.
  • SAP Continuous Integration and Delivery: builds and tests content. cTMS then takes care of controlled distribution.
  • Cloud ALM / ChaRM: control the process and approvals but do not transport anything themselves. They hand deployments over to CTS or cTMS.
cTMS compared with CTS, CI/CD and Cloud ALMCloud ALM or ChaRM control; CTS transports ABAP, cTMS cloud content; CI/CD builds and hands over to cTMS. Cloud ALM / ChaRMControl, do not transport CTS / STMSABAP transports cTMSCloud content CI/CDBuild and test
Cloud ALM and ChaRM control, CTS and cTMS transport, CI/CD delivers to cTMS.

In practice: prerequisites, set-up, pitfalls

SAP recommends a separate administration subaccount for the subscription and the service instance. Licensing is via Pay-As-You-Go for SAP BTP or the SAP BTP Enterprise Agreement; according to an SAP presentation, cTMS is also available in the free tier model.

Most of the effort goes into the connectivity. For Cloud Integration, for example, you create instances and service keys for the Content Agent service, the Process Integration Runtime and cTMS, and set up a total of five destinations in the development subaccount. The destination to cTMS usually authenticates via OAuth 2.0 with the client ID and client secret from the service key.

My own assessment, not sourced: typical pitfalls are missing role collections for transport operators, expired or wrongly assigned service keys, and destinations that point to the wrong space.

Setting up cTMS in four stepsCreate the admin subaccount, subscribe and create an instance, generate a service key, create destinations. Admin subaccountCentral Services Subscriptionplus instance Service keyOAuth client Destinationse.g. 5 for CPI
Set-up in four steps, from the admin subaccount to the destinations.

Comparison with Solution Manager

cTMS can be integrated with ChaRM and Quality Gate Management in Solution Manager. On-premise ABAP transports and cloud transports are then delivered in sync. In Cloud ALM, the feature bundles the transports instead of the change document. A transport created directly in SAP Cloud Integration can be assigned to a feature via the cTMS integration. Cloud ALM connects CTS for S/4HANA Cloud Private Edition and on-premise AS ABAP systems, and cTMS for, among others, BTP Cloud Foundry, Neo, Cloud Integration and API Management. External transports without a direct integration, such as configuration bundles in SAP SuccessFactors, are documented manually via transport references.

Solution Manager compared with Cloud ALMA ChaRM change in Solution Manager and a feature in Cloud ALM both use CTS and cTMS as the transport layer. Solution ManagerChaRM change, QGM SAP Cloud ALMFeature CTS and cTMSTransport layer stays
The control layer changes, the transport layer stays the same.

Current status

The integration of Cloud ALM and cTMS has been generally available since May 2022. SAP recommends one or more cTMS instances of your own in your own global account rather than the instance in the Cloud ALM global account, partly because several instances can then be connected. On 21 April 2026, SAP offered the online session “Govern your cloud deliveries with SAP Cloud ALM and SAP Cloud Transport Management”. No specific cTMS innovations from 2026 were found during research.

Timeline of cTMS and Cloud ALMMay 2022 integration generally available, then the switch to an instance of your own, April 2026 SAP session on governance. May 2022Integration available SwitchOwn instance recommended April 2026SAP governance session
From general availability in 2022 to the SAP session in April 2026.

Consultant's view

Customer question: “We run ChaRM in Solution Manager and have our first Integration Suite scenarios. Should we connect cTMS to Solution Manager now or wait for Cloud ALM?”

Answer: cTMS is the same transport layer in both cases. What you build now – nodes, routes and destinations – carries over when you move to Cloud ALM. Only the control layer is reconnected: the ChaRM change becomes the feature in Cloud ALM. I would therefore introduce cTMS straight away in its own subaccount and connect it to ChaRM. When you migrate, you connect the same instance to Cloud ALM.

Recommended path from ChaRM to Cloud ALMRun cTMS with ChaRM today, switch the control layer during migration, then use the same cTMS instance with Cloud ALM. TodaycTMS with ChaRM MigrationSwitch control layer AfterwardsSame instance, Cloud ALM
Build it today, and during migration simply reconnect the control layer.

Quiz

1. What does the SAP Cloud Transport Management service transport?

cTMS is a BTP service for development content across subaccounts. Classic ABAP transports run via CTS/STMS.

2. How is SAP Cloud Transport Management licensed?

According to the SAP product page, via Pay-As-You-Go or the BTP Enterprise Agreement; an SAP presentation also mentions the free tier model.

3. How do you handle SuccessFactors configuration bundles in Cloud ALM that have no direct deployment integration?

External transports without a direct integration can be documented manually in Cloud ALM via transport references.

Follow-up: Can cTMS run in the Cloud ALM subaccount?

(created with Claude Opus 5.5)

In short: technically this used to be the case, but today SAP recommends a cTMS instance of your own in your own BTP global account, ideally in a central administration subaccount.

Previously: when SAP Cloud ALM was introduced, the Cloud ALM account included cTMS by default. For newly provisioned Cloud ALM tenants, cTMS was already subscribed in the BTP subaccount. This subaccount sits in the global account that was created when Cloud ALM was requested.

Today: the new recommended integration has replaced the variant with cTMS in the Cloud ALM subaccount. SAP Knowledge Base Article 3775175 describes how to move an existing subscription to a global account of your own, because the old set-up may stop working after a back-end change. There is a dedicated SAP blog on migrating existing landscapes.

Why an instance of your own: several cTMS instances can be connected to one Cloud ALM instance, and Cloud ALM can then also transport content from SAP Analytics Cloud, which is not possible with instances in the Cloud ALM account. SAP recommends a separate administration subaccount for access control and separation of duties; source and target subaccounts may sit in different global accounts.

Not confirmed: a user blog from 2024 describes transport services via the Cloud ALM API with a bandwidth allowance included in the Cloud ALM usage rights. Whether this still applies after the switch is unclear; clarify licensing with SAP before quoting customers.

cTMS then and nowPreviously cTMS ran inside the Cloud ALM subaccount; today SAP recommends an instance of your own in a Central Services subaccount. Previously Cloud ALM global account Cloud ALM subaccount cTMS subscribed automatically Recommended today Your own BTP global account Central Services Own cTMS instance(s) SAP Cloud ALM Several instances, incl. SAC
Previously in the Cloud ALM subaccount, today as an instance of your own in your own global account.

Sources

Trial lessonSunday, 15 November 2026Topic: SAP Solution Manager(created with Claude Opus 5.5)

Architecture of SAP Solution Manager 7.1 and 7.2

Short definition

SAP Solution Manager 7.1 is a mandatory dual-stack system: AS ABAP and AS Java run under a shared SID and share one database. From SAP Solution Manager 7.2 onwards, the two stacks are separated. There is then an ABAP system based on SAP NetWeaver 7.40 and a Java system with its own SID, which work closely together.

Context

The diagram places both releases side by side and shows the path from 7.1 to 7.2.

SolMan 7.1 and 7.2 comparedOn the left SolMan 7.1 as a dual stack with one SID and one database, on the right SolMan 7.2 with separate ABAP and Java systems. SolMan 7.1 Dual stack, one SID AS ABAPNW 7.0 EHP2 AS JavaNW 7.0 EHP2 One databaseOne schema per stack SolMan 7.2 Two systems, two SIDs AS ABAPNW 7.40 AS JavaNW 7.50 DatabaseABAP system DatabaseJava system Path: upgrade with SUM, then dual-stack split with SWPM
A dual-stack system with one SID becomes two systems with SIDs of their own.

In depth

1. SolMan 7.1: one system, two runtime environments

Since SAP NetWeaver 7.0 EHP2, SAP has no longer recommended dual-stack systems for new installations. The only exceptions are scenarios in which the dual stack is mandatory. According to SAP Help, these include SAP Solution Manager 7.0 and 7.1 and SAP NetWeaver Process Integration 7.11. Technically, Solution Manager 7.1 is based on "SAP EHP2 for SAP NetWeaver 7.0".

ABAP and Java share one SID and are installed together. Each stack has its own database schema in the same database. An ABAP-only operation is not possible; Solution Manager 7.1 runs only as a dual stack.

For the LMDB this means that an AS ABAP and an AS Java with the same SID and the same message server are automatically combined into a "dual stack" technical scenario.

SolMan 7.1 dual stackOne system with a shared SID contains AS ABAP and AS Java; each uses its own schema in a shared database. One SAP system with a shared SID AS ABAPApplication functions AS JavaDiagnostics, agents Shared database ABAP schema Java schema
One SID, two runtime environments, one database with two schemas.

2. SolMan 7.2: two independent systems

With release 7.2, SAP abandoned the dual-stack architecture. The ABAP part is based on SAP NetWeaver 7.40, and ABAP and Java run as two independent systems. According to the SAP knowledge base, the two can be installed separately, either on the same host or on different hosts.

The Java stack initially ran on NetWeaver 7.40 and was later raised to AS Java 7.50. That Java 7.40 base has been out of maintenance since 31 December 2020. SAP is not raising the ABAP part to 7.50, however, because most of its functions are based on the CRM 7.0 EhP3 stack.

In practice this means two SIDs. In the Maintenance Planner you therefore also generate two stack.xml files, one for ABAP and one for Java.

Host options for SolMan 7.2Option 1: ABAP and Java systems on one host. Option 2: both on separate hosts. Each system has its own SID and its own stack.xml. Option 1: one host Host ABAPown SID Javaown SID Option 2: two hosts Host A ABAPown SID Host B Javaown SID One stack.xml per system in the Maintenance Planner
The two systems can share a host or run separately.

3. Division of tasks between ABAP and Java

In 7.2 the tasks are divided much as in 7.1.

  • Java stack: It mainly handles communication with the various agents. According to an answer in the SAP Community, it is indispensable for Solution Manager Diagnostics Agents, Byte Code Adapters, CA Wily Introscope and the SLD. SAP covers this question in KBA 2577037.
  • ABAP stack: It carries the application functions. For reporting, Solution Manager uses SAP BW, either in the current SolMan client or in a separate client. According to the change history of an SAP guide, SAP has not supported an external BW for 7.2 since January 2018.
  • User management: The Java system uses the ABAP system for the UME, so users are maintained centrally in ABAP.
  • Introscope: According to the Master Guide, the CA Introscope Enterprise Manager is installed on the Solution Manager host or on a separate host.
Division of tasks between ABAP and JavaManaged systems with Diagnostics Agents send data to the SolMan Java system, which works with the SolMan ABAP system providing applications, BW reporting and the UME. Managed systemsDiagnostics Agents SolMan JavaAgents, SLD, Introscope SolMan ABAPApplications, BW Java UME resides in ABAP
Java talks to the agents; ABAP carries the applications and user management.

4. The database

SolMan 7.1: There is exactly one database, in which each stack has its own schema.

SolMan 7.2: SAP HANA is supported as a database for the first time. The Solution Manager usage rights include database licences for SAP HANA and SAP ASE. These licences, however, apply exclusively to Solution Manager.

New installation with ASE: According to SAP KBA 2642172, an installation of ABAP and Java needs two ASE databases with separate SIDs.

Splitting an existing system: The split tool offers two options. With "Keep Database", the Java database stays in place; a field report describes this as SAP's recommendation. Alternatively, you move the Java database with "Move your Java Database". In practice, there are therefore also 7.2 systems whose ABAP and Java instances share one database on the same host after the split.

Check the dual-stack split guide and the SAP Notes to see whether, and how, this is supported long term in your constellation. Sources in the SAP Community contradict each other here: one answer says MCOD is not supported in 7.2.

Database options in Solution Manager7.1 with one database and two schemas; 7.2 after the split with Keep Database or Move Database; SAP HANA and ASE licence for Solution Manager only. SolMan 7.11 DB, 2 schemas 7.2: Keep DatabaseJava DB stays in place 7.2: Move DatabaseJava DB is moved From 7.2: SAP HANA supportedHANA and ASE licence for SolMan only
One database in 7.1, two split options in 7.2.

5. The path from 7.1 to 7.2 and maintenance

The SAP upgrade guide for 7.2 sets out this sequence: first the upgrade with SUM, then, after the SUM post-processing steps, the dual-stack split, and finally the follow-up work. The split is mandatory and is carried out with the dual-stack split tool from Software Provisioning Manager (SWPM). The follow-up work includes adjusting the SLD settings in the ABAP and Java systems to the new SLD server and port.

The background is SAP's NetWeaver strategy: the Java stacks of NetWeaver 7.00 to 7.02 were in mainstream maintenance only until 2017, and from NetWeaver 7.5 onwards SAP no longer supports dual-stack deployments.

For SolMan 7.2, mainstream maintenance runs until the end of 2027. Customers who choose the optional extended maintenance for SAP Business Suite 7 until the end of 2030 also receive it for SolMan 7.2 at no extra cost. It covers only selected areas, however: requirements management, project and process management, Test Suite, Change Control Management, ITSM and landscape management.

Upgrade from SolMan 7.1 to 7.2Sequence: SolMan 7.1 dual stack, upgrade with SUM, dual-stack split with SWPM, follow-up work such as SLD targets. Below, the maintenance dates. SolMan 7.1Dual stack Upgradewith SUM Splitwith SWPM Follow-upe.g. SLD targets NW 7.0x Java: mainstream maintenance until 2017SolMan 7.2: mainstream until end of 2027, extended until end of 2030
Upgrade first, then split, then follow-up work.

Consultant's view

  • Size two systems: A field report on 7.2 SP4 gives as an example 4 cores and 16 GB for ABAP with ASCS, central instance and Introscope, and 2 cores and 8 GB for Java with SCS, central instance and Introscope MoM. This is not an SAP sizing, but it shows that Java needs resources of its own.
  • Do not leave out Java: Without the Java stack, Solution Manager is not fully functional. Diagnostics Agents, Byte Code Adapters, Introscope and the SLD depend on it.
  • Plan agent versions: The Diagnostics Agents follow the SolMan version level. Updating them via SolMan is tied to updating the whole stack: AS ABAP first, then AS Java.
  • Mind the licence limits: The HANA or ASE right covers Solution Manager only, not any other applications.
  • Clarify the strategy with the customer: Mainstream maintenance for 7.2 ends at the end of 2027. For customers with SAP Enterprise Support, a Cloud ALM tenant is free of charge. Anyone who understands the architecture of 7.1 and 7.2 can assess properly which functions move to Cloud ALM and which stay in SolMan for now.
Checkpoints from a consultant's viewFour checkpoints: sizing for two systems, agent versions follow the SolMan stack, database licence for SolMan only, strategy because maintenance ends in 2027. SizingPlan ABAP and Java separately AgentsVersion follows the SolMan stack LicenceHANA and ASE for SolMan only StrategyMainstream maintenance ends 2027
Four checkpoints for operations and strategy.

Quiz

1. How is SAP Solution Manager 7.1 built technically?

SolMan 7.0 and 7.1 are mandatory dual-stack systems. ABAP and Java share one SID and each uses its own schema in the same database.

2. What is the Java stack in SolMan 7.2 mainly responsible for?

The Java stack mainly handles communication with Diagnostics Agents, Byte Code Adapters, Introscope and the SLD. Applications and BW reporting reside in ABAP.

3. According to the SAP upgrade guide, when does the dual-stack split take place on the way from 7.1 to 7.2?

The guide lists the split after the SUM post-processing. It is mandatory and is carried out with the dual-stack split tool (SWPM).

Follow-up: What does switching off SolMan mean for the SLD and LMDB?

(created with Claude Opus 5.5)

What disappears with SolMan

SAP describes the LMDB as part of SAP Solution Manager, providing central access to all landscape data. When SolMan is switched off, the LMDB therefore disappears too. Three things in particular are lost:

  • The data basis of the SolMan applications: Change Control Management, monitoring and alerting, and root cause analysis use the system information in the LMDB.
  • The classic upload to the Maintenance Planner: Data in the Maintenance Planner is replicated from the LMDB of the connected Solution Manager. This data flow needs a different route.
  • Manual maintenance in the LMDB: Systems without a data supplier that were created only there by hand are lost as well.

What happens to the SLD

The SLD is not the same as the LMDB. It keeps running as long as it is operated on a Java system of its own. It has two roles: it gathers and distributes the data from the SLD data suppliers, and it provides landscape data and data created in the SLD, such as software components or business systems, to client applications. According to SAP, other tools and services can take over the first role. The SLD remains indispensable only for its client applications:

  • PI/PO: The SLD provides technical system data and creates business systems. Customers moving to SAP Integration Suite do not need an SLD.
  • NWDI: The SLD creates software components, defines team development landscapes and manages name reservations. NWDI has the same maintenance duration as the SLD.
  • Web Dynpro Java: It is supported for as long as the SLD itself.

My own inference: if the central SLD currently runs as a local SLD on the SolMan Java system, it is lost along with SolMan. It must then first move to a standalone Java system or be replaced.

In both scenarios the data suppliers have to be redirected. During decommissioning they are deactivated; if a system is not physically removed, its SLD data suppliers should point to another SLD.

Scenario A: with Focused Run

  • Its own LMDB: Focused Run has an LMDB of its own and takes over the role of the SolMan LMDB.
  • Without an SLD: A single Focused Run can process the SLD data in ABAP itself, so no SLD is needed.
  • Multiple namespaces: The LMDB in Focused Run separates data by customer network. The SolMan LMDB knows only the "active" namespace.
  • SLDR: The System Landscape Data Router forwards the data from RZ70, sapstartsrv and other data suppliers to an LMDB or an SLD. It can be used only with Focused Run and does not store any landscape data itself.
  • Maintenance Planner: The SAP Support Backbone uses the landscape data from Focused Run.
  • With Cloud ALM: Customers using Focused Run and Cloud ALM register and distribute their systems via Focused Run, Cloud ALM and the Landscape Information Services (LIS).

Limitations: Focused Run is not included in any SAP maintenance agreement and must be licensed separately. It has its own maintenance timeline, independent of Solution Manager.

Scenario B: without Focused Run

  • Cloud ALM: Systems are registered and distributed via Cloud ALM and the Landscape Information Services.
  • Support Portal and Maintenance Planner: LIS explicitly provides for an exceptional case without SAP Solution Manager and without an SLD. The customer profile serves software maintenance with the Maintenance Planner; the system data concern licence and installation data.
  • Manual route: SAP Notes 2287046 and 2408911 describe the system info XML and uploading system information to the Maintenance Planner.
  • SLD: It remains necessary only if PI/PO, NWDI or Web Dynpro Java are in use.

Consultant's view: Before switching off, take stock of who uses the SLD, where it runs and where all data suppliers report to. Then decide how system data will reach the Support Portal in future, via Focused Run or via LIS. Only then decommission SolMan; when decommissioning, a system is removed from the LMDB first and from the SLD afterwards.

Landscape data after SolManLeft, with Focused Run: data suppliers send to the SLD Data Router, which feeds the FRUN LMDB. Right, without Focused Run: Landscape Information Services upload system data to the SAP Support Portal; an SLD remains necessary only for PI/PO, NWDI and Web Dynpro Java. With Focused Run Without Focused Run Data suppliersRZ70, sapstartsrv, etc. SLD Data Router (SLDR)distributes the landscape data LMDB in Focused Runprocesses SLD data itself Support Backbone and Cloud ALM Data suppliersSet a new target Landscape Info ServicesSystem data upload SAP Support PortalMaintenance Planner, Cloud ALM SLD only for PI/PO, NWDI, WD Java
With Focused Run its LMDB takes over; without Focused Run SAP services take over.

Follow-up: What role does SAP Cloud ALM play with regard to the LMDB?

(created with Claude Opus 5.5)

In short: Cloud ALM has no LMDB. Its place is taken by the Landscape Management app, the "Landscape Management Service" (LMS) in SAP's component naming.

Landscape Management holds information on cloud services, on-premise systems and business services. This landscape information is the basis for all other applications in SAP Cloud ALM. Its structure differs from the LMDB, however: there, the data suppliers send their data to the SLD, which forwards it 1:1 to the LMDB by synchronisation. In Cloud ALM, systems register directly by routes of their own.

My own inference: the SLD, CIM model and CR content do not appear in SAP's description of Cloud ALM. I found no explicit SAP statement that Cloud ALM does not need these components at all.

Connecting managed systems

  • ABAP on-premise: Registration via ST-PI and report /SDF/ALM_SETUP. An LMS_ID is then generated, and the system appears in Landscape Management as "Registered". Data flows by push; the "CALM Scheduler" job triggers the collection via asynchronous RFCs. The Cloud Connector cannot be used for ABAP on-premise systems.
  • PI/PO (Java): The Cloud Connector is needed here, because this system type has no ST-PI. The system is imported as "SAP Netweaver AS for Java" and does not have to be created manually.
  • Cloud services: SAP recommends the daily automatic import from the System Landscape Information Service (SLIS). By default, only services with the same customer number as Cloud ALM are imported.
  • Non-ABAP and non-SAP systems: Their data can be sent via the Cloud ALM APIs. Because OpenTelemetry is an open standard, third-party data providers can also be connected via inbound APIs.

Consultant's view

  • System copies: After a refresh from production, a refreshed quality system receives the same LMS ID as the production system. The Cloud ALM configuration is integrated into post-copy automation (PCA).
  • Data collection: Cloud ALM follows a central configuration approach, so the data collection processes must be configured explicitly.
  • With Focused Run: Customers using Focused Run and Cloud ALM register and distribute their systems via Focused Run, Cloud ALM and the Landscape Information Services.
SAP Cloud ALM architecture with managed systemsA Cloud ALM tenant contains Landscape Management as the basis of all applications. Below, four kinds of managed system: ABAP on-premise via ST-PI push, PI/PO Java via the Cloud Connector, cloud services imported from SLIS and non-ABAP systems via inbound APIs. SAP Cloud ALM (tenant on SAP BTP) Landscape ManagementBasis of all applications ApplicationsMonitoring, change, projects ABAP on-premST-PI, push PI/PO JavaCloud Connector Cloud servicesImport from SLIS Non-ABAPInbound APIs Arrow up: the system sends to Cloud ALM Arrow down: Cloud ALM queries PI/PO via the Cloud Connector
Landscape Management replaces the LMDB; each system type has its own connection route.

Sources

Lesson

Follow-up: SLD and LMDB

Follow-up: Cloud ALM

Many details come from SAP Community posts rather than official SAP documentation. The SAP Notes and guides cited are authoritative.

Week 1Monday, 16 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

BTP at a glance: global account, directory, subaccount

Short definition

The SAP BTP account model organises all platform resources in a hierarchy of a global account, optional directories and subaccounts. The global account represents the contract with SAP. Directories structure and delegate administration. Only in the subaccount do applications, service instances and runtime environments actually run. The model solves the task of representing contract, costs, responsibilities and technical separation (such as development, test and production) in a single structure.

Context

The account model is the foundation for all the other lessons this week. Tomorrow's runtime environments (Cloud Foundry, Kyma, ABAP Environment) are enabled per subaccount. Wednesday's entitlements and quotas flow downwards through this hierarchy. CAP applications (Thursday) are deployed to a subaccount. Trust with Identity Authentication, destinations and the Cloud Connector (Friday) are also configured at subaccount level.

As a Cloud ALM user, one detail matters to you: when SAP provisions Cloud ALM, it creates a global account of its own with a subaccount of its own that is intended exclusively for Cloud ALM (SAP Learning, Cloud ALM onboarding course). The Cloud Transport Management service from the trial lesson of 14 November also lives as a subscription in a subaccount.

SAP BTP account modelA global account contains two directories; below them are three subaccounts in regions, in which runtime environments are enabled. Global accountContract with SAP Directory Salesoptional, can be nested Directory ITEntitlements, users Subaccount DevRegion eu10 Subaccount ProdRegion eu20 Subaccount SharedRegion eu10 In the subaccount: Cloud Foundry, Kyma, ABAP Environment
The global account carries the contract, directories organise, subaccounts host the runtimes.

In depth

How it works and its building blocks

According to SAP Learning, the global account is the realisation of the contract with SAP. Through it you manage directories, subaccounts, members, entitlements and quotas. The cockpit always shows exactly one global account at a time; if you have several, you choose which one to enter when you log on.

Directories are an optional organisational layer between the global account and subaccounts. A directory can contain further directories and subaccounts. Since August 2021, up to five directory levels can be nested (SAP Community blog on the upgrade to feature set B). An article by Rizing describes the same thing as a hierarchy of up to seven levels, with the global account at the top and the subaccount at the bottom, so the two figures are consistent. Directories have two features that can be switched on: entitlement management (the directory becomes a "managed directory", and only the entitlements assigned to it are available to its subaccounts) and user management with the role collections Directory Administrator and Directory Viewer. Regions play no part for directories; they only manage, they host nothing.

The subaccount is the unit in which the actual work takes place. Besides a name and a parent object, it needs a region and a unique subdomain. Every subaccount runs in exactly one region, and by choosing the region you also choose the infrastructure provider (hyperscaler). A multi-environment subaccount offers Cloud Foundry, Kyma and the ABAP Environment. A Cloud Foundry environment has exactly one org (a 1:1 relationship), with any number of spaces below it. The ABAP Environment, by contrast, appears like an ordinary service instance.

From contract to subaccountContract, global account, optional directory and subaccount as a chain. ContractCommercial model Global accountEntitlements Directoryoptional SubaccountRegion, apps
From the contract via the global account and optional directories to the subaccount.

How it differs from similar terms

Directory or subaccount? A directory groups and delegates; a subaccount hosts. Runtimes are enabled and services instantiated only in the subaccount; a directory has neither a region nor applications.

Subaccount, org and space: Cloud Foundry brings a deeper hierarchy of its own. The org belongs to the subaccount one to one, and the spaces below it separate work areas and share the org's quota. Anyone who equates "subaccount" with "space" will later plan the separation of development and production at the wrong level.

Labels instead of directories: Labels are metadata consisting of a key and up to ten values, such as "cost centre" or "landscape: Dev/Test/Prod". They replace the former "custom properties", allow filtering in the Account Explorer and also appear in the cost and usage evaluation. Directories therefore represent the binding structure, labels the additional views on it.

Feature set A and B: Directories and labels exist only in cloud management tools feature set B; only there do global accounts have a subdomain of their own (mirror of the SAP documentation on GitHub, unofficial copy). According to an SAP Community post, most global accounts have now been migrated to feature set B.

Directory, subaccount and label comparedA directory groups and hosts nothing, a subaccount has a region and hosts apps, a label consists of a key and values for filtering and costs. Directorygroups, delegateshosts nothing Subaccountexactly one regionhosts apps, services Labelkey, up to 10 valuesfilters, costs
Directories organise, subaccounts host, labels provide additional views.

In practice: prerequisites, set-up, typical pitfalls

Prerequisites: For structure and entitlements you need the Global Account Administrator role collection; among other things, it lets you create subaccounts and set entitlements. You can use the default role collections (Global Account, Subaccount and Directory Administrator), but you can neither change nor delete them. Whoever creates a subaccount or directory automatically becomes its initial administrator; in emergencies, global account administrators can add themselves as administrators of a subaccount or directory.

Set-up: SAP Learning recommends a naming scheme following the pattern "(directory …) purpose", for example "EU HCM Dev". Set labels for cost centre, owners and landscape from the outset. The subaccount also has a "Used for production" flag; according to an SAP Community post, it helps BTP support recognise production accounts quickly during an incident.

Pitfalls:

  • Consumption can be evaluated only per subaccount, directory or Cloud Foundry space, not per application. A project whose costs you want to allocate cleanly therefore needs its own subaccount, directory or space. Exact billing exists only at global account level (SAP PRESS blog, based on SAP documentation).
  • A global account can have only one type of consumption model (SAP Learning, solution architect course). Consumption-based and subscription-based models, on the other hand, can be combined.
  • If you enable entitlement management in a directory that already contains subaccounts, all entitlements of those subaccounts are added to the directory automatically.
  • The region is a fundamental decision, because it determines latency, data residency and the hyperscaler.

My own assessment: I did not find a way in the official sources to change the region of an existing subaccount afterwards; plan it as a fixed decision.

Order of steps when building the account modelCheck feature set B, define structure and names, set labels, distribute entitlements; below, the note that costs can be evaluated only per subaccount, directory or space. Feature set Bcheck Structuredefine names Labelscost centre Entitlementsdistribute Pitfall: costs only per subaccount, directory or space
Structure and labels first, then distribute entitlements.

Comparison with Solution Manager and Focused Run

In Solution Manager and Focused Run, the LMDB describes the technical landscape: technical systems, product versions, hosts. The BTP account model is something different. It is a commercial and organisational container that carries the contract, quotas, responsibilities and cost allocation. What runs technically in a subaccount is described by the account model only roughly (environment, region, subscriptions).

My own assessment: the obvious analogy from the SolMan world is therefore not the LMDB but rather the question of how responsibilities and areas are divided up in SolMan.

Familiar from Cloud ALM practice: when Cloud ALM is provisioned, SAP sets up a global account and a subaccount intended exclusively for Cloud ALM. SAP warns against deleting this subaccount or the subscription, because all artefacts, data and configurations are then lost (SAP Learning). SAP KBA 3152095 explains why a new global account is created for this rather than a subaccount in the existing one. For consulting discussions this means: your own extensions and integrations belong in the global account of the BTP contract, not in the Cloud ALM account.

SolMan/Focused Run, the BTP account model and Cloud ALMSolMan and Focused Run model technical systems in the LMDB, the BTP account model represents contract and organisation, Cloud ALM runs in a global account of its own. SolMan / FRUNLMDB: technical systems BTP account modelContract, organisation Cloud ALMown global account
The LMDB describes technology, the account model describes contract and organisation; Cloud ALM has a global account of its own.

Current status and innovations

  • Available: According to SAP KBA 3365019, the multi-cloud foundation (Cloud Foundry, Kyma, ABAP) has been the default environment for new customers since 2020.
  • Available: Up to five nested directory levels have been possible since August 2021 (SAP Community blog).
  • Available: Labels replace the former custom properties; the custom-properties parameter in the btp CLI and the customProperties field in the REST APIs are marked as deprecated (unofficial mirror of the SAP documentation).
  • Available: The SAP BTP Enterprise Agreement (BTPEA) was introduced in April 2024 and is an evolution of CPEA (SAP tutorial on developers.sap.com).
  • Announced: The Neo environment reaches end of life on 31 December 2028; new functions are available only in the multi-cloud foundation (SAPinsider, SAP event page).
  • Preview: No preview functions relating to the account model itself were found during research.
Milestones of the BTP account model2020 multi-cloud as default, August 2021 five directory levels, April 2024 BTPEA, 31 December 2028 end of the Neo environment (announced). 2020Multi-cloud Aug 20215 levels April 2024BTPEA 31 Dec 2028End of Neo
Three available milestones and the announced end of Neo (dashed).

Consultant's view

Customer question: “We have three subsidiaries. Do we need a separate global account for each one?”

Answer: Not necessarily. The global account stands for a contract with SAP, and SAP's best-practice guide explicitly describes an account model in which each subsidiary gets its own directory, supplemented by labels for cost centres and owners. With user management in the directory, each subsidiary can have its own directory administrators who maintain their subaccounts themselves without gaining rights over the whole global account; with entitlement management, each subsidiary gets its own quota. Two points nevertheless speak for separate global accounts. First, exact billing exists only per global account; if the subsidiaries need legally separate invoices, splitting costs via directories and labels may not be enough. Second, a global account can carry only one type of consumption model; if the subsidiaries sign different consumption contracts, this inevitably leads to separate global accounts. And regardless of that, Cloud ALM stays in its own global account anyway.

My own assessment: whether internal cost allocation via labels is sufficient for the customer is a decision for the controlling department.

One global account with a directory per subsidiaryOne global account for one contract; below it one directory each for subsidiary A, subsidiary B and subsidiary C, each with its own administrators and a cost centre label. Global accountone contract Subsidiary Aown admins, label Subsidiary Bown admins, label Subsidiary Cown admins, label
One contract, one directory per subsidiary with its own administrators and labels.

Quiz

1. At which level do applications, service instances and runtime environments run?

Only subaccounts host runtimes, services and subscriptions. The global account represents the contract; directories only structure and delegate.

2. What is the maximum number of directory levels that can be nested?

Since August 2021, up to five directory levels have been possible. The figure seven describes the whole hierarchy, including the global account at the top and the subaccount at the bottom.

3. You enable entitlement management in a directory that already contains subaccounts. What happens?

According to SAP Learning, enabling it automatically assigns all entitlements of the contained subaccounts to the directory. From then on, the subaccounts may use only the directory's entitlements (managed directory).

Sources

Official SAP sources

SAP Community (community posts, not official documentation)

Trade press and specialist blogs

Unofficial copies of the SAP documentation (emergency use only)

help.sap.com could not be accessed directly when this lesson was created; the statements are based on SAP Learning, SAP KBAs and the mirrors marked above.

Week 1Tuesday, 17 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

Runtime environments: Cloud Foundry, Kyma, ABAP environment

Short definition

A runtime environment determines where and how applications run on BTP. SAP names three strategic runtime environments: Cloud Foundry for simple deployment and operation of cloud applications, Kyma for more complex requirements, and the ABAP environment (SAP user group presentation “SAP BTP Foundation”). They answer the question of which technology, which team and which operating model suit an extension, without the customer running its own infrastructure.

Context

The runtimes build directly on yesterday’s account model: environments are enabled or disabled per subaccount, and several runtimes of the same environment can exist in one subaccount (SAP Learning). Wednesday’s entitlements and quotas determine how much of each runtime a subaccount may use. CAP (Thursday) is the programming model for Cloud Foundry and Kyma. All three runtimes need Identity Authentication, destinations and the Cloud Connector (Friday) to talk securely to back ends. Saturday’s side-by-side extensions run on exactly these runtimes.

Cloud Foundry has a fixed rule: each subaccount can contain only one Cloud Foundry org, but the number of spaces in that org is not limited. The ABAP environment has a special role because, according to SAP Learning, it runs as a service instance in a space and is enabled like any other service instance.

Runtimes in the subaccountA subaccount contains a Cloud Foundry org with an app space and an ABAP space, and a Kyma cluster with namespaces and modules. Subaccount (region, infrastructure) Cloud Foundry: one org App space CF applications ABAP space ABAP system Kyma: Kubernetes cluster Namespaces Workloads Modules Istio etc.
Cloud Foundry with one org and spaces, Kyma as a cluster with namespaces and modules, the ABAP environment in a CF space.

In depth

How it works and its building blocks

Cloud Foundry is BTP’s polyglot platform. It supports several runtimes, programming languages, libraries and services and uses many buildpacks, including community buildpacks and SAP’s own (SAP Learning). The developer supplies code, and the buildpack turns it into a runnable container. The hierarchy is lean: subaccount, org, spaces.

Kyma is a fully managed Kubernetes runtime based on the open-source project “Kyma”. Kyma has a modular design. Active by default are API Gateway for exposing and securing APIs, the SAP BTP Operator for creating and managing BTP services in Kyma, and Istio (SAP Learning). Further modules such as Serverless, Eventing or Telemetry are added as needed. Modules are delivered through release channels, and only one release channel can be set per module.

ABAP environment: It is cloud-enabled but not cloud-native, and therefore needs a cloud-native environment as its foundation, namely Cloud Foundry (SAP Learning). The sources contradict each other here: an SAP Community post states that the ABAP environment technically lives within the Cloud Foundry or the Kyma environment. The SAP Learning statement on Cloud Foundry is authoritative.

Tools per level: According to SAP Learning, you work with the btp CLI for global account, directory and subaccount, the cf CLI for Cloud Foundry, org and space, and kubectl for Kyma. For the ABAP system, the ABAP Development Tools (ADT) are added (see Practice).

Tools per levelbtp CLI controls the account model, cf CLI the org and spaces, kubectl the Kyma cluster, ADT the ABAP system. btp CLIAccount model cf CLIOrg and spaces kubectlKyma cluster ADTABAP system
Each level has its own tool.

Distinction from similar terms

Cloud-native or cloud-enabled? SAP Learning distinguishes two classes: Cloud Foundry and Kyma are cloud-native runtimes that host service instances and many applications; the ABAP environment is a cloud-enabled runtime purely for ABAP applications.

Steampunk: The term comes up often in projects. E3 Magazin describes it as the official name for the BTP ABAP environment, a PaaS solution for cloud-based side-by-side extensions, decoupled from the ERP core.

Embedded Steampunk: This must be distinguished from the S/4HANA Cloud ABAP environment, which allows on-stack extensions directly in the S/4 system (E3 Magazin). Same development model, but a different place.

Neo: The fourth, older environment reaches its end of life on 31 December 2028 (SAPinsider). It is no longer an option for new projects.

Kyma instead of Serverless Runtime: The former SAP BTP Serverless Runtime was discontinued because, according to an SAP Community post, the Kyma runtime proved to be the more beneficial and more well-rounded runtime for customers. Serverless functions now run as a Kyma module.

Distinguishing the environmentsCloud Foundry and Kyma are cloud-native, the ABAP environment is cloud-enabled, Neo ends on 31 December 2028. Cloud-nativeCloud Foundry, Kyma Cloud-enabledABAP environment NeoEnds 31 Dec 2028
Two cloud-native runtimes, one cloud-enabled runtime, Neo is being phased out.

Practice: prerequisites, set-up, typical pitfalls

Prerequisites: Everything starts with the entitlement in the subaccount. For the ABAP environment, the size is set with two units: one ABAP compute unit corresponds to 16 GB, and one HANA compute unit corresponds to the block size of the underlying SAP HANA Cloud (15 GB on AWS, 16 GB on Microsoft Azure) (SAP Learning).

Set-up: In Cloud Foundry, enabling the environment creates the org. Because each org belongs to exactly one subaccount, SAP recommends reusing the subaccount’s subdomain as the org name. You then create spaces, because at least one space is needed to deploy and run applications. In Kyma, the required modules are added after provisioning. The ABAP environment is created through the service marketplace as a service instance in a space.

Pitfalls:

  • Minimum ABAP size: The sources contradict each other. SAP Learning names at least one unit of ABAP runtime and at least two units of HANA memory; the SAP Community FAQ page names 0.5 ACU and two HCUs. Check the current status in the SAP Discovery Center before making an offer.
  • Cost of development systems: According to the community FAQ, hibernation waives the ACU costs and reduces the HCU costs to 12.5% of the original price. Not hibernating systems wastes money.
  • Tooling: ABAP Cloud is mandatory, and according to the community FAQ the ABAP Development Tools (ADT) are the only available tool, for both Eclipse and VS Code. SAP GUI and SE80 are no longer available.
  • Number of systems: The FAQ generally recommends one system per subaccount, because trust settings are defined at subaccount level.
Set-up stepsEntitlement, enable the environment, create spaces or modules, then deploy or develop; below, the note on hibernating development systems. Entitlementin subaccount EnableCF, Kyma, ABAP StructureSpaces, modules UseDeploy, develop Pitfall: hibernate development systems when idle
From entitlement to use; hibernate development systems when they are not needed.

Comparison with Solution Manager and Focused Run

For operations, what matters is how the three runtimes are monitored:

  • ABAP environment in Cloud ALM: Health monitoring has its own metrics, for example ABAP runtime errors, current sessions, locked business and communication users, and ABAP compute units.
  • Cloud Foundry in Cloud ALM: Health monitoring can monitor custom Java and Node.js applications running in the Cloud Foundry environment.
  • Cloud Foundry and Kyma with OpenTelemetry: The Expert Portal describes instrumenting custom applications with the data collection libraries based on OpenTelemetry.
  • Real user monitoring: According to the Expert Portal it supports the ABAP environment, Cloud Foundry, Kyma and Neo.
  • Focused Run: The Expert Portal describes how to connect the SAP BTP ABAP environment to SAP Focused Run.

Own assessment: Compared with Solution Manager, the work shifts from managing agents (Diagnostics Agent, Host Agent) to communication scenarios, destinations and code instrumentation. For Cloud Foundry and Kyma apps, the quality of monitoring therefore depends heavily on whether the development team builds in the instrumentation.

Monitoring the runtimesFocused Run can connect the ABAP environment, Cloud ALM health monitoring covers ABAP and CF apps, OpenTelemetry instruments CF and Kyma apps. Focused RunABAP env. connectable Health monitoringABAP, CF apps OpenTelemetryCF and Kyma apps
Three ways of monitoring the BTP runtimes.

Current status and news

  • Available: The ABAP environment has a fixed release rhythm: new releases arrive quarterly in February, May, August and November, and a pre-upgrade option delivers new functions about four weeks earlier (community FAQ).
  • Available: Elastic scaling in the ABAP environment: when the mechanism detects high load, it adds further application servers up to the instance’s ACU configuration, which acts as the maximum (SAP Community post).
  • Announced: At SAP Sapphire in May 2026, SAP unveiled the SAP Business AI Platform (BAIP). SAPinsider explains that BAIP brings together SAP BTP, SAP Business Data Cloud and SAP Business AI and that BTP is part of BAIP, not replaced by it. Other sources speak of a renaming, so the positioning is still evolving. The community FAQ already mostly uses the name “SAP Business AI Platform, ABAP environment”.
  • Announced: Neo’s end on 31 December 2028. SAP announced as early as June 2023 that it would discontinue the Neo environment by the end of 2028 (DSAG statement) and explicitly does not approve any extension beyond the end of 2028 (SAPinsider).
  • Status unclear: An SAP product page describes Joule with the SAP BTP Kyma runtime as help for keeping clusters healthy. Whether the function is generally available or in preview could not be confirmed in the official documentation.
TimelineJune 2023 announcement of Neo’s end, May 2026 unveiling of the SAP Business AI Platform, 31 December 2028 end of Neo (announced, dashed). June 2023Neo end announced May 2026BAIP unveiled 31 Dec 2028Neo end of life
Two events and the announced end of Neo (dashed).

Consultant's view

Customer question: “We want to build several extensions for S/4HANA. Should we use Cloud Foundry, Kyma or the ABAP environment?”

Answer: The decision follows the team’s skills first and only then the technology. If the customer has a strong ABAP team and the work concerns ABAP-related logic, the ABAP environment is the natural choice, because it supports extensions for ABAP-based products such as SAP S/4HANA Cloud and can bring existing ABAP code to the cloud (SAP Learning). If the team works with Java or Node.js and needs simple applications that are quick to operate, Cloud Foundry fits. If the team knows Kubernetes and needs microservices, containers or event-driven functions, Kyma fits. The two cloud-native runtimes share a programming model: according to SAP Learning, CAP is the appropriate choice when deploying to Cloud Foundry or Kyma and offers a uniform programming model for the languages supported there. For existing customers with Neo applications, migration belongs in every roadmap. Monitoring should be clarified early: for ABAP, Cloud ALM delivers metrics directly; for Cloud Foundry and Kyma apps, the team must plan the instrumentation.

Own assessment: A choice between Cloud Foundry and Kyma is less final as long as the application is cleanly built on CAP.

Decision logicFrom the question about team and application to the ABAP environment, Cloud Foundry or Kyma. Which team, which app? ABAP environmentABAP team, ABAP logic Cloud FoundryJava, Node.js, CAP KymaContainers, Kubernetes
The team’s skills decide the runtime first.

Quiz

1. How many Cloud Foundry orgs can a subaccount contain?

Each subaccount has exactly one Cloud Foundry org. Dev, test and prod are separated by spaces or by separate subaccounts.

2. Which Kyma modules are active by default after provisioning?

Istio, API Gateway and the SAP BTP Operator are active by default. Serverless, Eventing, Telemetry and further modules are added as needed.

3. According to the community FAQ, what happens to the costs when an ABAP environment system is hibernated?

According to the community FAQ, no ACU costs arise during hibernation, while the HANA compute units still cost 12.5% of the original price.

Sources

Official SAP sources

SAP Community (community posts, not official documentation)

Trade press and user groups

help.sap.com was not checked directly; the statements are based on SAP Learning, the SAP Support Expert Portal and the marked community and press sources.

Week 1Wednesday, 18 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

Entitlements, quotas and service plans

Short definition

An entitlement is the contractually acquired right to provision and use a resource on SAP BTP; in the cockpit, the btp CLI and the cloud management APIs it appears as a combination of service plans and the quota you may use. The quota is the numeric quantity that defines the maximum permitted usage of a resource – in other words, how much of a service or technical plan you may use (SAP blog in the SAP Community). A service plan is a variant of a service (e.g. Free, Standard, Trial) and limits the available quantity of the service (SAP Developers). Together, the three terms solve a governance problem: the contract sits centrally, while consumption happens in a decentralised way across many subaccounts.

Context

The term follows directly on from Monday and Tuesday. Monday covered the account model: entitlements and quotas are managed at global account level, distributed to directories and subaccounts, and consumed by the subaccounts (SAP Developers). Tuesday covered the runtime environments: they too depend on entitlements – Cloud Foundry orgs receive their resource quotas from the subaccount's entitlements (SAP Learning). The entitlements themselves are derived from the contracts with SAP (SAP Learning). Entitlements are therefore the link between the contract (commercial) and the service instance (technical).

Flow of entitlements in SAP BTPFrom the contract via the global account to a managed directory and subaccounts, down to consumption in instances, subscriptions and Cloud Foundry org quota. Contract with SAPBTPEA, CPEA, PAYG, subscription Global accountEntitlements and quota pool Directory (managed)Own quota pool Subaccount BAssigned directly Subaccount AFrom the directory ConsumptionService instances, subscriptions, CF org quota
The contract fills the global account; from there, entitlements flow to the subaccounts either directly or via a managed directory, where they are consumed.

In depth

How it works and its building blocks

Every service on SAP BTP offers one or more service plans, which can be thought of as variants; the chosen plan is the entitlement, and the quota describes how much of that plan you may use (SAP Community, member post). Which plans exist for a service is shown in the SAP Discovery Center on the “Pricing” tab (SAP Developers). Assignment is done in the cockpit via “Configure Entitlements” and “Add Service Plans”; there you see all entitlements available to the directory or subaccount (SAP Developers).

The key difference is between plans with and without a quantity. For plans with a quantity, you distribute a number (e.g. instances or storage units). For plans without a quantity, you can assign the service to several subaccounts without having to think about how to split it; the assignment then works like “enabling” (SAP Developers). If you remove quotas or entitlements from a subaccount, they become available again at global account level and can be assigned to other subaccounts (SAP Developers). Quota is therefore a pool that is redistributed – not a consumption meter.

Building blocks of an entitlementService, service plan, quota and assignment as a chain; returning quota refills the pool. Servicee.g. HANA Cloud Service planFree, Standard … QuotaAmount or “on” AssignmentTo subaccount ↻ Removed quota flows back into the global account's pool
From the service via the plan and the quota to the assignment; returned quota is available again in the global account.

Distinction from similar terms

In everyday use, four terms are often confused. Entitlement is the right, quota the quantity, service plan the technical variant. The fourth term sits one level lower: the space quota in Cloud Foundry defines memory, number of routes, and service and app instances for a space; it is created in the cockpit under Cloud Foundry → Space Quotas, and the creation dialogue shows the org quota as the upper limit for each field (SAP Learning). The space quota is thus a Cloud Foundry-internal means of further dividing the org quantity already received via entitlement – not a BTP entitlement.

Equally important is the distinction between instance and subscription: services are either instantiated or subscribed to; a subscription runs standalone without a runtime environment, and subscriptions often use limited quotas (SAP Learning). Finally, the free tier is not a separate account but a set of entitlements within a consumption-based global account that allows certain services to be activated via free plans (SAP Developers). This distinguishes it from the trial account, which is a separate test account.

Distinguishing the termsFour tiles: entitlement as a right, quota as a quantity, service plan as a variant, space quota as a Cloud Foundry-internal split. EntitlementRight to use a plan QuotaMaximum permitted quantity Service planTechnical variant of the service Space quotaCF-internal, splits org quantity
Three BTP terms and the Cloud Foundry-internal space quota compared.

Practice: prerequisites, set-up, typical pitfalls

The first prerequisite is understanding the commercial model. For enterprise accounts there is the consumption-based model in the flavours BTPEA (since April 2024), CPEA (for existing CPEA accounts) and Pay-As-You-Go, plus the subscription-based model (SAP Developers). CPEA and BTPEA are based on prepaid cloud credits with an annual consumption commitment and can only be used in parallel in separate global accounts (SAP Learning). According to a partner guide (vendor blog, supplementary), consumption-based and subscription-based models can be combined in the same global account, but not two consumption flavours such as CPEA and Pay-As-You-Go (EPI-USE Labs).

The second prerequisite is a distribution concept. If you want to limit the entitlements for a group of subaccounts, you place them in a directory and activate entitlement management there (SAP Learning). From then on, the subaccounts in it can only use the entitlements assigned to the directory; if you activate the feature for a directory that already contains subaccounts, their entitlements are added to the directory automatically (SAP Learning). This is the first pitfall: if a subaccount sits in a managed directory, a service must first be assigned to the directory (SAP Developers).

For automation there is the btp CLI with the command assign accounts/entitlement, which offers options including distributing and auto-assigning to the subaccounts of a directory (example still using the old name sapcp, SAP blog), as well as the resource btp_subaccount_entitlement in the Terraform provider for SAP BTP (SAP Developers).

Typical pitfalls are shown by the titles of relevant SAP knowledge base articles: Cloud Foundry runtime memory cannot be increased via the entitlements in a CPEA global account (KBA 3195551); the message “No quotas were purchased for this global account” appears for Cloud Foundry Runtime on a CPEA account (KBA 3044842); a Cloud Foundry org shows 0 MB of memory, so no deployment is possible (KBA 3774567). The solutions are in the full texts in SAP for Me; only the symptoms are deliberately reproduced here.

Setting up entitlementsFour steps: check the model, assign to directory or subaccount, create instance or subscription, check consumption. Check modelBTPEA, PAYG … AssignDirectory first CreateInstance, subscr. Check usageCosts and Usage
Set-up in four steps: clarify the model, assign (in managed directories, there first), create, monitor consumption.

Comparison with Solution Manager and Focused Run

SAP Cloud ALM follows a different path from typical BTP services: you request the tenant via “Systems and Provisioning” in SAP for Me (SAP Learning). The usage right is contained in SAP Enterprise Support, cloud editions, in SAP Enterprise Support or in Product Support for Large Enterprises; only SAP Focused Run has to be licensed separately (SAP Support). Even here, quota-like quantities appear: according to KBA 3590742, an SAP Cloud ALM tenant extension comprises an additional productive tenant, 8 GB of SAP HANA memory usage and 8 GB of outbound API data transfer per calendar month.

Own assessment (not from the sources): Solution Manager and Focused Run have no counterpart to entitlements in the platform sense. There, the licence agreement and your own hardware sizing determine what is possible, and operations manage capacity themselves. On BTP, this capacity planning becomes a distribution task within the global account – comparable to no longer ordering servers for SolMan but shifting allowances between projects.

Comparison of capacity controlOn the left on-premise with licence and own sizing, on the right BTP with entitlements in the global account, below Cloud ALM with a tenant via SAP for Me. SolMan / Focused RunLicence plus own sizing SAP BTPEntitlements in global account SAP Cloud ALMRight from Enterprise Support, tenant via SAP for Me
On-premise controls capacity through licence and sizing, BTP through entitlements; Cloud ALM is provisioned via SAP for Me.

Current status and news

Available: The entitlement pages in the cockpit show commercial information; an “Entitlement Source” filter shows how a plan got into the global account, and “Always Free” and “Free Tier” labels mark plans without consumption charges (SAP blog). The former “Usage Analytics” page is now called “Costs and Usage” and offers, among other things, comparisons by service or subaccount as well as trends (SAP blog).

Available: Free tier plans are limited in usage capacity on a monthly basis, do not expire, and the upgrade to a paid plan is done in the cockpit without technical migration (SAP Learning).

Available, date not stated: SAP reports a platform update that brought more flexibility in managing entitlements for the Cloud Foundry runtime; the documentation on service plans and initial set-up was revised accordingly (SAP blog). The details are in a separate article that could not be retrieved – hence no further statements on it.

No announced or preview features specific to entitlements were found in official sources.

Current statusThree available innovations: BTPEA since April 2024, transparency in the cockpit, more flexible Cloud Foundry entitlements. BTPEASince April 2024 Cockpit transparencySource, labels, costs CF runtimeMore flexible entitlements All three available; no preview features found
Three available innovations around entitlements; no preview features found.

Consultant's view

Customer question: “We have a BTPEA contract with SAP HANA Cloud. Why does our developer in the DEV subaccount still not get an SAP HANA Cloud plan to choose from?”

Answer: A contract alone is not enough, because the entitlements initially sit only in the global account and must be distributed to directories and subaccounts before a subaccount can consume them (SAP Developers). I therefore check in three steps. First: does the DEV subaccount have an entry for the right plan at all? If not, it is added via “Configure Entitlements” and “Add Service Plans”. Second: is DEV located in a directory with entitlement management activated? Then the plan must first be assigned to the directory, otherwise it will not appear for DEV (SAP Developers). Third: is there still free quota in the global account? The “Remaining Global Quota” column shows how much is still available (SAP Developers); if it is exhausted, quota must be returned from another subaccount, which then becomes available again in the global account.

Own recommendation: maintain entitlements as code (btp CLI or Terraform) so that DEV, QAS and PROD reproducibly receive the same plans.

Check chain for a missing service planThree checks: plan in the subaccount, managed directory, remaining quota in the global account; then create the instance. 1. Plan there?In the subaccount 2. Directory?Assign there first 3. Quota left?Check globally Create instanceIn the subaccount
Three checks before the instance can be created in the subaccount.

Quiz

1. A subaccount sits in a directory with entitlement management activated. What has to happen for it to be able to use a new service plan?

In a managed directory, the subaccounts can only use the entitlements assigned to the directory. The plan therefore has to arrive there first.

2. What happens to quota that you remove from a subaccount?

Removed quotas or entitlements become available again in the global account and can be assigned to other subaccounts. Quota is a pool that is redistributed.

3. Which statement about the free tier is correct?

The free tier is not an account but a set of entitlements with free plans in a consumption-based global account. The plans do not expire, are limited monthly and can be upgraded without migration. A time-limited test account is the trial account.

Sources

Official SAP sources

SAP Community (community posts, not official documentation)

Vendor blog (supplementary)

help.sap.com could not be accessed directly in this session; the statements are based on SAP Developers, SAP Learning, SAP Support and the marked community and vendor sources.

Week 1Thursday, 19 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

SAP Cloud Application Programming Model (CAP)

Short definition

CAP is a framework of languages, libraries and tools for building enterprise-grade services and applications (SAP PRESS Blog). It solves a familiar problem with extensions: a lot of effort goes into technical infrastructure instead of business logic. CAP applies proven best practices by default, so that developers can concentrate on their business domain rather than on recurring technical groundwork (capire, "Introduction to CAP").

Context

CAP is one of the two programming models on BTP; SAP Learning names CAP and the ABAP RESTful Application Programming Model (RAP) as the options. CAP therefore ties in with this week's lessons. Tuesday covered the runtimes: CAP applications run in Cloud Foundry or Kyma, RAP runs in the ABAP environment. Wednesday covered entitlements: the services a CAP app needs (database, authorisation, logging) must be available in the subaccount as an entitlement with a suitable service plan. Tomorrow adds identity and destinations, which CAP apps use for sign-in and for calls to back ends.

Where CAP sits in SAP BTPSubaccount with the Cloud Foundry/Kyma runtimes for CAP and the ABAP environment for RAP, below them the BTP services used, connected to S/4HANA and other back ends. BTP subaccount Cloud Foundry / KymaCAP: Node.js or JavaModels in CDS ABAP environmentRAP: ABAPABAP CDS BTP services (via entitlement)HANA Cloud, authorisation, logging, messaging S/4HANA, other back ends
CAP runs in Cloud Foundry or Kyma and uses BTP services from the subaccount's entitlements.

In depth

How it works and its building blocks

The core is CDS. According to SAP Learning, CDS is the data modelling infrastructure and the backbone of the programming model; it captures service definitions and data models. Domain models describe the static aspects of a business domain as entity-relationship models. Associations represent relationships, and compositions extend this to document structures. Services build on top: with CQL, de-normalised views on the domain model are declared in CDS, for example for tailored service APIs (capire, "About CAP").

The core idea is "models fuel runtimes". CAP uses the declarative information about data and services to serve requests automatically, including complex deep queries with expands, filters, sorting and aggregations (capire, "Core Concepts"). There are two stacks for the runtime: libraries for Java and Node.js with which services can be provided and consumed synchronously and asynchronously (SAP Learning). The protocols are decoupled from the model. A CDS service definition is enough to serve REST, OData or GraphQL endpoints generically; add-ons provide a GraphQL adapter and an OData V2 adapter (capire).

From the CDS model to the endpointDomain model, service definition, generic runtime and the protocols OData, REST and GraphQL in sequence. Domain modelEntities in CDS ServiceProjections RuntimeNode.js / Java OData REST GraphQL
One model gives rise to the service, the runtime and several protocols.

How it differs from similar terms

The two kinds of CDS are easily confused. ABAP CDS is an ABAP technology and part of RAP. CDS in CAP is a modelling language of its own with its own compiler. Both follow similar ideas but are not the same artefact. An overview from a certification portal (ERPPrep, not SAP documentation) puts it this way: CAP models with CDS, RAP with the ABAP Dictionary plus ABAP CDS.

The real distinction concerns RAP. RAP is an ABAP development model for cloud-ready applications, services and extensions on the BTP ABAP environment, in S/4HANA Cloud and in S/4HANA 1909 and later (SAP blog "RAP vs. CAP"). CAP, by contrast, is polyglot and runs outside the ABAP stack. SAP Build Code is not an alternative to CAP but a tool on top of it: according to an SAP blog (TechEd 2023), CAP in SAP Build Code simplifies defining data models and services with CDS and exposes them as OData services.

CAP and RAP comparedTwo columns: CAP with Node.js or Java, the CDS language, Cloud Foundry and Kyma; RAP with ABAP, ABAP CDS, the ABAP environment and S/4HANA 1909 and later. CAPLanguage: Node.js or JavaModel: CDS (CAP)Runtime: Cloud Foundry, Kyma RAPLanguage: ABAPModel: ABAP CDSABAP env., S/4HANA 1909+
Same idea, different stacks: CAP is polyglot, RAP lives in ABAP.

In practice: prerequisites, set-up, typical pitfalls

CAP follows the "grow as you go" principle. A project starts in seconds with cds init and cds watch. You first work offline with local mocks and later add features, work in hybrid mode or deploy. A modulith is recommended first; microservices are cut only when needed (capire). SQLite and H2 in-memory are used for development, SAP HANA and PostgreSQL in production. Once the prerequisites for Cloud Foundry or Kyma are met, cds up builds and deploys the application, to Cloud Foundry by default (release notes, March 2025).

Multitenancy is important for operations: MTX isolates tenants at runtime and handles deployment, subscription and updates. Then there is the extensibility concept: SaaS customers, partners or internal teams can add annotations, fields, entities and custom logic without needing extension points, and switch these on or off per tenant (capire).

Typical pitfalls are versions and dependencies. For the current major release, SAP warns against mixing packages with older versions, as this is untested – for example, not @sap/cds 10.x with @sap/cds-mtxs 3.x. For the runtimes: Node.js 22 is the minimum, 24 recommended; JDK 21 is the minimum, JDK 25 recommended (release notes, June 2026). Another pitfall concerns monitoring (next section).

Grow as you goFour steps: local with SQLite and mocks, hybrid with real BTP services, deployment with cds up, productive with HANA Cloud and MTX. LocalSQLite, mocks Hybridreal BTP services Deploymentcds up ProductionHANA Cloud, MTX
From a local project to productive operation in four steps.

Comparison with Solution Manager / Focused Run

There is no direct counterpart to CAP in SolMan, because CAP is a development framework. The comparison becomes relevant in operations. With custom ABAP developments, the data came from the stack, for example via agents and extractors. A CAP app only delivers telemetry if it is instrumented. The Cloud ALM Expert Portal describes how to equip your own applications in Cloud Foundry and Kyma with the Data Collection Instrumentation Libraries; Business Process Monitoring and Exception Monitoring process this OpenTelemetry data for Java and Node.js. SAP describes Cloud ALM as the central observability platform for BTP and explains how to instrument CAP applications with OpenTelemetry (sap.com).

Focused Run can do this too: as of Focused Run 4.0 FP02, Health Monitoring, Exception Monitoring and Real User Monitoring receive OpenTelemetry metrics from instrumented customer applications in Cloud Foundry; this is enabled via the Focused Run reverse proxy using Cloud ALM (Focused Run Expert Portal).

Not confirmed: a post in the SAP Community (2024) says that CAP's built-in OpenTelemetry support does not send data to Cloud ALM. I could not verify whether this still applies. The safe route is the SAP instrumentation libraries from the Expert Portal.

Monitoring a CAP appA CAP app with the SAP instrumentation library sends OpenTelemetry data to Cloud ALM; Focused Run 4.0 FP02 and later receives it as well. CAP appwith SAP instrumentation OpenTelemetryTraces, errors Cloud ALMBPMon, exceptions Focused Run4.0 FP02 and later
No instrumentation, no data: the CAP app has to deliver OpenTelemetry.

Current status and innovations

Available: The current major release is "cds 10" (June 2026): @sap/cds and @sap/cds-dk 10.x, @sap/cds-compiler 7.x, @sap/cds-mtxs 4.x, CAP Java 5.x. CAP Java 5 requires at least Spring Boot 4.0, with 4.1 recommended. In CAP Java, built-in OData processing now replaces Apache Olingo (release notes, June 2026). The most recent version I found is cds-dk 10.2.0 from 21 October 2026: in it, cds login supports browser-based sign-in with SAP Cloud Identity Services (IAS) via OAuth 2.0 with PKCE (changelog).

Beta: Of interest for the AI topic in week 6 is the MCP adapter. Any CAP service can be turned into an MCP server with the @mcp annotation, so that AI agents can work with it without additional implementation (capire). It is labelled beta for Node.js; the Java version is not yet public. Also in beta: the data privacy plug-in for Node.js with SAP DPI integration, and Event Mesh support, Node.js only.

Alpha: CAP-level agents, the CAP Skills Library and the AI Core plug-ins, including automatic field recommendations in the UI.

CAP innovations by maturityThree columns: available (cds 10 and CAP Java 5, built-in OData in Java, cds login with IAS), beta (MCP adapter, data privacy, Event Mesh), alpha (CAP-level agents, Skills Library, AI Core plug-ins). Availablecds 10 / Java 5built-in OData (Java)cds login with IAS BetaMCP adapterData privacyEvent Mesh AlphaCAP-level agentsSkills LibraryAI Core plug-ins
What can be used today and what is still in beta or alpha.

Consultant's view

Customer question: "Our ABAP developers are strong. Should we use CAP or RAP for new extensions?"

Answer: I would base the decision on the use case, not on the team's preference. If the extension is closely tied to S/4HANA data and transactional logic, RAP is the obvious choice, because RAP runs on the ABAP environment, in S/4HANA Cloud and in S/4HANA 1909 and later, and the team can apply its know-how directly. If the solution needs its own data storage in HANA Cloud or PostgreSQL, multitenancy as SaaS, events, non-SAP systems or, in future, AI agents via MCP, CAP is the stronger option. Important for operations: plan monitoring from the start. A CAP app needs OpenTelemetry instrumentation, otherwise Cloud ALM cannot see it – unlike in the ABAP world, where the stack provides much of this. The two models can also be combined.

My own assessment: I found no SAP rule of thumb with fixed thresholds; the answer weighs up the sources cited.

Decision aid: CAP or RAPThe question of what the solution needs leads to RAP for close S/4HANA ties and an ABAP team, and to CAP for SaaS, events, non-SAP systems or AI. What does it need? RAPclose to S/4HANA, ABAP team CAPSaaS, events, non-SAP, AI
The use case decides, not the team's preference.

Quiz

1. What is the backbone for data models and service definitions in CAP?

According to SAP Learning, CDS is the modelling infrastructure and the backbone of CAP. The ABAP Dictionary belongs to RAP; OData is only one of the protocols.

2. Which combination does SAP cite in the cds 10 release as an example not to mix?

The June 2026 release notes cite @sap/cds 10.x with @sap/cds-mtxs 3.x as an untested mix. Node.js 24 and Spring Boot 4.1 are actually recommended.

3. What status does the MCP adapter (@mcp) have according to the June 2026 release notes?

The MCP adapter is labelled beta for Node.js; the Java version is not yet public.

Follow-up: What exactly is OpenTelemetry?

(created with Claude Opus 5.5)

Basic idea. According to the official project page, OpenTelemetry (OTel for short) is an observability framework and toolkit that helps generate, export and collect telemetry data such as traces, metrics and logs. Observability there means understanding the internal state of a system from its outputs. For this, the code must be instrumented, i.e. emit traces, metrics or logs, and this data must be sent to an observability back end (opentelemetry.io). OTel is not a monitoring tool with dashboards: it defines how signals are captured and exported, but does not interpret them (Resolve AI, vendor page). The analysis is done by a back end – in the SAP world, for example, Cloud ALM or Focused Run.

Origin. OTel is an open-source project of the Cloud Native Computing Foundation (CNCF) and was created by merging the OpenCensus and OpenTracing projects (Uptrace, vendor blog).

Building blocks (according to the vendor sources Uptrace and SigNoz):

  • API: programming interface used to instrument code to capture traces, metrics and logs.
  • SDK and instrumentation libraries: implement the API in the respective language; with auto-instrumentation, often without changing the application code.
  • Semantic conventions: uniform attribute names, so that data from different sources is comparable.
  • Collector: receives, processes and forwards data. It is not mandatory but is usually recommended.
  • OTLP (OpenTelemetry Protocol): the transport protocol between SDK, Collector and back end, over either gRPC or HTTP.

The signals. Traces show the path of a request through several services, metrics are measurements over time, logs are timestamped events. The added value is that OTel links the three signals through a shared context, so that during an incident you can jump from the trace to the matching log (Coralogix, vendor blog). Profiling is being added as a fourth signal (Uptrace, Resolve AI). Because the format is vendor-neutral, the choice of back end remains open.

OTel in Cloud ALM. SAP uses OTel as the basis for data collection: SAP's own SaaS applications and customer-built PaaS applications use the Data Collection Instrumentation Libraries, which produce standard OTel data with some SAP-specific extensions. Data from SAP applications flows via the SAP-managed Data Collector Runtime; data from customer applications goes directly to Cloud ALM. Monitoring must be switched on in Cloud ALM per service and use case, and the data can be forwarded to Focused Run. For customer applications, Business Process Monitoring, Exception Monitoring, Health Monitoring and Real User Monitoring use this data (Java and Node.js), and Job & Automation Monitoring for SAP Job Scheduler jobs. Cloud Foundry and Kyma are supported (Cloud ALM Expert Portal).

In practice, this means for a CAP app: for Java there is the otel-agent-ext-java library, for Node.js xotel-agent-ext-js. Access is via a technical user of the SAP Repository Based Shipment Channel (RBSC). In the BTP subaccount you create a destination named CALM_datacollector (OAuth2ClientCredentials) with the details from the API service key. For back-end-only scenarios, auto-instrumentation is enough; front-end collection (FESR) is needed only for Real User Monitoring (Cloud ALM Expert Portal).

My own assessment: in Solution Manager, the Diagnostics Agent and Wily Introscope delivered telemetry via an SAP-proprietary route. In the cloud, OTel replaces this proprietary route with an open standard. The SAP back end remains; only the data format is open.

OpenTelemetry data flow to Cloud ALMAn instrumented application generates traces, metrics and logs and sends them via OTLP to a back end such as Cloud ALM, optionally on to Focused Run. ApplicationSDK / auto-instr. SignalsTraces, metrics, logs Back ende.g. Cloud ALM Focused Run (optional) OTLP
The application generates the signals, OTLP carries them, the back end analyses them.

Sources for the follow-up

Sources

Official SAP sources

SAP Community (community posts, not official documentation)

Trade press and other sources (supplementary)

Week 1Friday, 20 November 2026Topic: SAP BTP(created with Claude Opus 5.5)

Identity and connections: Identity Authentication, destinations, Cloud Connector

Short definition

Today is about two questions that every BTP application has to answer: who is the user, and how does the application reach a target system? Identity Authentication (IAS, part of SAP Cloud Identity Services) handles sign-in and single sign-on, the Destination service stores connection data centrally outside the code, and the Cloud Connector builds an outbound tunnel from the corporate network to BTP, so that cloud applications can reach on-premise systems without opening inbound ports in the firewall.

Context

The three building blocks follow directly on from the previous days. On Monday you saw that every subaccount has its own trust relationship with identity providers – this is exactly where IAS plugs in. Wednesday covered entitlements: Destination and Connectivity are services that you assign to the subaccount and bind to an application as an instance. And yesterday's CAP application does not call its back ends via hard-coded URLs but via destination names. The path of a request therefore looks like this: the user signs in via IAS (which in turn can delegate to a corporate IdP such as Entra ID), the application receives a token, looks up the destination, and for targets in the corporate network the call runs via the connectivity proxy through the Cloud Connector's tunnel to the back end.

Identity and connections on SAP BTPThe user signs in via Identity Authentication, the application in the subaccount uses the Destination and Connectivity services, and the Cloud Connector in the corporate network builds an outbound tunnel and forwards calls to the back end. SAP BTP – subaccount Applicatione.g. CAP app DestinationURL, auth, proxy type ConnectivityProxy to tunnel Identity AuthenticationSign-in, SSO, token Corporate IdPoptionally delegated Corporate network (on-premise) Cloud Connectoroutbound tunnel Back endS/4HANA, ECC
The Cloud Connector builds the tunnel from the inside out; requests then run through this tunnel to the back end.

In depth

How it works and its building blocks

SAP Cloud Identity Services bundle several services: Identity Authentication handles sign-in and single sign-on, Identity Provisioning the lifecycle of users and groups. IAS speaks SAML 2.0 and OpenID Connect and can store users itself or, acting as a proxy, delegate sign-in to a corporate IdP. For BTP, one distinction matters, and SAP Learning sets it out clearly: platform users (administrators, developers, operations) sign in to the cockpit and the tools, business users to the applications. By default, every global account trusts SAP ID service – the IdP operated by SAP with S-users and P-users. For both user groups, however, SAP explicitly recommends a dedicated IAS tenant.

The Destination service is a configuration store. A destination contains a name, type (HTTP, RFC, LDAP, MAIL, TCP), URL, authentication type and the proxy type. The proxy type determines the route: "Internet" goes straight to the network, "OnPremise" via the Connectivity service and the Cloud Connector, "PrivateLink" via a private endpoint at the hyperscaler. Destinations can sit at subaccount level (for all applications) or at the level of a service instance (for one application only). The Connectivity service provides the proxy through which Cloud Foundry applications write into the tunnel; in Kyma, the Connectivity Proxy and the Transparent Proxy take on this role.

The Cloud Connector is Java-based software that you install in the corporate network. It works as a reverse invoke proxy: it builds an encrypted connection to the subaccount, keeps it open and re-establishes broken connections itself. Using access control, you define which internal hosts are reachable under which virtual names, and which paths or RFC function modules; everything else stays invisible. It supports HTTP, RFC, LDAP and TCP and logs access and configuration changes.

Path of a request to an on-premise systemFour steps: sign-in via IAS, look up the destination, connectivity proxy, Cloud Connector to the back end. 1 Sign-inIAS issues token 2 Destinationlook up target 3 ProxyOnPremise route 4 Connectorto back end
Sign-in, destination, proxy and Cloud Connector come into play one after another in an on-premise call.

Distinction from similar terms

Three mix-ups come up again and again in projects. First: SAP ID service and Identity Authentication are not the same. SAP ID service is the shared IdP for S-users, managed by SAP; an IAS tenant, by contrast, belongs to you – you control password rules, two-factor sign-in, conditional authentication and delegation to the corporate IdP. SAP Learning also points out that some newer applications require a dedicated Cloud Identity Services tenant for business users.

Second: the Destination service and the Connectivity service are often lumped together. The destination is the "address book" with target and sign-in method; the Connectivity service is the "line" into the tunnel. For an on-premise target you need both. For internet targets, the destination is enough.

Third: the Cloud Connector is not a classic reverse proxy in the DMZ. A Web Dispatcher or NGINX in the DMZ accepts inbound connections from the internet; the Cloud Connector, by contrast, accepts no connections from outside but builds them outwards itself. This is also the difference from Private Link: Private Link connects BTP privately with resources at the same hyperscaler, whereas the Cloud Connector reaches into a genuine corporate network.

Distinguishing the termsThree pairs: SAP ID service versus own IAS tenant, destination versus connectivity, Cloud Connector versus DMZ reverse proxy. SAP ID servicemanaged by SAP Own IAS tenantcontrolled by you Destinationaddress book Connectivityline into the tunnel Cloud Connectoroutbound only DMZ reverse proxyaccepts inbound
Three pairs of terms that are often confused in projects.

In practice: prerequisites, set-up, typical pitfalls

For IAS, set-up starts with the tenant, which according to an SAP Community guide must be assigned to the same cost centre as the global account. You then set up trust to the IAS tenant in the subaccount – separately for platform and business users – and decide whether IAS authenticates itself or forwards to the corporate IdP. A common pitfall is switching off SAP ID service before the new trust has been tested; in the worst case you lock yourself out of the cockpit.

For the Cloud Connector, you download the subaccount's authentication data in the cockpit under Connectivity and import it in the connector's administration UI. You then maintain the system mappings (internal host, virtual host, protocol) and the exposed resources. The virtual host name from the Cloud Connector is what goes into the destination as the URL – not the real internal host name. For production scenarios, a master–shadow set-up for high availability and regular updates are part of the package.

For single sign-on all the way to the back end, the key term is principal propagation. The Cloud Connector creates a short-lived X.509 certificate from the signed-in user's token and passes it on to the back end, which trusts it via an imported system certificate and maps the user to a back-end user by rule (in the ABAP system via rule-based certificate mapping). Typical errors are an unsynchronised trust in the Cloud Connector ("Principal Propagation" tab), a wrong subject pattern and missing trust in the back end's ICM. Important: during the conversion only the user's identity is preserved; other attributes from the token are not passed to the back end.

Principal propagation via the Cloud ConnectorUser token, Cloud Connector creates a short-lived X.509 certificate, back end maps it to a user by rule. User tokenfrom IAS, SAML/JWT Cloud Connectorshort-lived X.509 Back endmapping by rule
Principal propagation: the token becomes a short-lived certificate, which the back end maps to a user.

Comparison with Solution Manager / Focused Run

From your SolMan world you know the separation between user management in the ABAP stack (SU01, possibly SAP Identity Management) and the technical connections via SM59 and managed system configuration. On BTP, IAS takes on the role of central sign-in, and the destination is the counterpart of the SM59 connection – with the difference that it is managed as a service and the application queries it at runtime. This fits with the fact that SAP Identity Management 8.0 is the final release; according to SAPinsider, maintenance ends on 31 December 2027, and Cloud Identity Services are moving into this role.

It gets interesting with SAP Cloud ALM, because the routes differ there. Cloud ALM itself does not authenticate users; the assigned IAS tenant does. For ABAP on-premise systems (push via ST-PI), the SAP Cloud ALM Expert Portal states explicitly that the Cloud Connector cannot be used for the connection to Cloud ALM; the data goes out directly via HTTPS, possibly via a corporate proxy. For SAP PI on Java, by contrast, Cloud ALM uses the Cloud Connector, because ST-PI is not available there. In addition, Cloud ALM can monitor the Cloud Connector itself as a managed component, which requires a user with the role sccmonitoring or sccadmin. In Focused Run, in turn, a reverse proxy in Cloud ALM is used for cloud services so that push data from the cloud arrives – here too, the direction of the connection is the core of the design.

Comparison of the SolMan world and the BTP worldSU01 and IdM correspond to IAS, SM59 corresponds to the destination; with Cloud ALM, ABAP on-premise does not use the Cloud Connector, PI Java does. SU01 / SAP IdM Identity Authentication SM59 connection Destination Cloud ALM, ABAP on-premise: no connector Cloud ALM, PI Java: via connector
Familiar SolMan building blocks and their BTP counterparts; with Cloud ALM, the route depends on the system type.

Current status and new features

Cloud Connector 2.19 (available): The current line is 2.19. Information on the release date of 2.19.0.2 is contradictory: one specialist blog gives March 2026, the consultancy Xiting April 2026. According to a personal admin blog (supplementary source, not official), 2.19 brings, among other things, RFC over WebSocket, new administration roles and additional REST monitoring APIs. SAP Note 3767634 (Patch Day October 2026, CVE-2026-58242, CVSS 3.5) fixed a missing authorisation check; according to the security vendor Pathlock, the correction is included from version 2.19.1, and the note does not mention a workaround. Since 2.18 there has also been central trust store management for LDAP and e-mail, as well as automatic renewal of the subaccount certificate.

New endpoints for the tunnel (available, changeover under way): The SAP Help page on the Connectivity service prerequisites lists new domains under platform.cloud.sap "as of 15 November 2026" for several regions – that is, for just a few days. For you as the person responsible for operations, this means checking the firewall and proxy rules for the Cloud Connector's outbound connections. The same page also announces the activation of IPv6 addresses (AWS no earlier than February 2026, Google Cloud no earlier than April 2026).

Whether your region is affected has to be checked in the table on the Help page – only excerpts of the page were available during research.

Identity (changeover under way): With the "Bring your own identity" programme, SAP is moving sign-in to its own portals to IAS; according to sap.com, sign-in via SAP Universal ID has run through the standard IAS mechanism since January 2026, and from July 2026 account associations are formed automatically by e-mail address. This mainly affects S-user sign-ins, not your BTP trust directly.

New features in 2026 around the Cloud Connector and connectivityVersion 2.18 trust stores and certificate renewal, 2.19 stability and new features, 2.19.1 security fix, new tunnel domains from 15 November 2026. 2.18Trust stores, certs 2.19Spring 2026 2.19.1Note 3767634 15 Nov 2026new domains
Key milestones in 2026: versions 2.18 to 2.19.1 and the new tunnel domains.

Consultant's view

Customer question: "Our IT security does not want to open any inbound ports, but the business department wants a BTP app with single sign-on to our S/4HANA in our own data centre. Is that possible, and what do we need to prepare?"

Answer: Yes, this is exactly what the combination is designed for. The Cloud Connector is installed in the internal network and builds the connection to BTP from the inside out, so the firewall needs no inbound rule – only outbound connections to the region's connectivity endpoints need to be allowed, and you should check these straight away because of the new domains since mid-November. In the Cloud Connector, you expose only the S/4HANA system under a virtual name, and within it only the OData paths that the app really needs. For single sign-on, we set up a dedicated IAS tenant that delegates to your Entra ID or another corporate IdP; the BTP app uses a destination with proxy type OnPremise and principal propagation. From this, the Cloud Connector creates a short-lived certificate per request, and S/4HANA maps it by rule to the correct user, so that authorisations and change logs continue to run under the real user. What needs to be prepared is therefore: a server for the Cloud Connector (with a shadow instance for production), the certificates for the system certificate and CA, the certificate rule and the trust in the back end, and an update process that applies security notes such as 3767634 promptly.

Preparation package for SSO to on-premise S/4HANAFour building blocks: Cloud Connector with shadow, IAS tenant with corporate IdP, destination with principal propagation, certificate rule in the back end. Connectorwith shadow IAS tenantto corporate IdP Destinationprincipal prop. Back endcertificate rule
The four building blocks to prepare for SSO to an on-premise S/4HANA.

Quiz

1. Why do no inbound ports need to be opened in the corporate firewall for the Cloud Connector?

The Cloud Connector initiates the tunnel from the corporate network to BTP and keeps it open. A DMZ reverse proxy, by contrast, would accept inbound connections.

2. A CAP app is to call an S/4HANA system in the company's own data centre. Which proxy type belongs in the destination?

OnPremise routes the call via the Connectivity service into the Cloud Connector's tunnel. PrivateLink is intended for private endpoints at the hyperscaler, Internet for publicly reachable targets.

3. A customer wants to connect ABAP on-premise systems to SAP Cloud ALM via ST-PI and use the existing Cloud Connector for this. What is correct according to the SAP Cloud ALM Expert Portal?

The Expert Portal states explicitly that the Cloud Connector cannot be used for the connection between ABAP on-premise and Cloud ALM. For SAP PI on Java, on the other hand, it is used because ST-PI is not available there.

Sources