10/15/24, 3:53 PM

SAP Business Technology Platform

Generated on: 2024-10-15 15:53:21 GMT+0000

SAP Business Technology Platform (SAP BTP) | Cloud

PUBLIC

Original content: https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b?locale=en-

US&state=PRODUCTION&version=Cloud

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not reflect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 10/15/24, 3:53 PM

Basic Platform Concepts

SAP BTP offers users the ability to turn data into business value, compose end-to-end business processes, and build and extend
SAP applications quickly.

SAP Business Technology Platform is built on a multi-cloud foundation, which lets you choose from different infrastructures and
runtimes. The services and solutions of SAP BTP are available on multiple cloud infrastructure providers, and it supports different
runtimes, such as Cloud Foundry, ABAP, and Kyma, as well as multiple different regions, and a broad choice of programming
languages.

The central point of entry to the platform is the SAP BTP cockpit, where you can access your accounts and applications and
manage all activities associated with them.

Relationship between SAP BTP Accounts and Associated Activities

Solutions and Services

SAP BTP offers fast in-memory processing, sustainable, agile solutions and services to integrate data and extend applications,
and fully embedded analytics and intelligent technologies.

Services enable, facilitate, or accelerate the development of business applications and other platform services on SAP BTP.

For a complete list of services and capabilities, see SAP Discovery Center: Services .

For more information, see Solutions and Services.

Regions
You can deploy applications in different regions. Each region represents a geographical location (for example, Europe, US East)
where applications, data, or services are hosted.

This is custom documentation. For more information, please visit the SAP Help Portal 2
 10/15/24, 3:53 PM

Regions are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft
Azure, Google Cloud, and Alibaba Cloud. The third-party region providers operate the infrastructure layer of the regions, whereas
SAP operates the platform layer and Cloud Foundry.

A region is chosen at the subaccount level. For each subaccount, you select exactly one region (that is one data center).

For more information, see Regions.

Environments
Environments constitute the actual platform-as-a-service offering of SAP BTP that allows for the development and administration
of business applications. Environments are anchored in SAP BTP on subaccount level.

SAP BTP provides the following environments:

Cloud Foundry Environment

The Cloud Foundry environment enables you to develop new business applications and business services, supporting
multiple runtimes, programming languages, libraries, and services. You can leverage a multitude of buildpacks, including
community innovations and self-developed buildpacks.

ABAP Environment

Within the Cloud Foundry environment, you can create a new space for ABAP development. This is what we refer to as the
ABAP environment. It allows you to create extensions for ABAP-based products, such as SAP S/4HANA Cloud, and develop
new cloud applications. You can transform existing ABAP-based custom code or extensions to the cloud.

Kyma Environment

SAP BTP, Kyma runtime provides a fully managed cloud-native Kubernetes application runtime based on the open-source
project "Kyma". Based on modular building blocks, Kyma runtime includes all the necessary capabilities to simplify the
development and to run enterprise-grade cloud-native applications.

This is custom documentation. For more information, please visit the SAP Help Portal 3
 10/15/24, 3:53 PM
Neo Environment

The Neo environment lets you develop HTML5, Java, and SAP HANA extended application services (SAP HANA XS)
applications. You can also use the UI Development Toolkit for HTML5 (SAPUI5) to develop rich user interfaces for modern
web-based business applications.

 Remember
SAP Business Technology Platform, Neo environment will sunset on December 31, 2028, subject to terms of customer
or partner contracts.

For more information, see SAP Note 3351844 .

Enterprise and Trial Accounts

SAP BTP provides different types of global accounts, enterprise and trial. The type you choose determines pricing, conditions of
use, resources, available services, and hosts.

A trial account lets you try out the platform for free. Access is open to everyone. Trial accounts are intended for personal
exploration, and not for production use or team development. They allow restricted use of the platform resources and
services.

For more information, see Trial Accounts and Free Tier.

An enterprise account is usually associated with one SAP customer or partner and contains their purchased entitlements
to platform resources and services. It groups together different subaccounts that an administrator makes available to users
for deploying applications.

For more information, see Enterprise Accounts.

Commercial Models

SAP BTP offers two different commercial models:

Consumption-based commercial model: Your organization receives access to all current and future services that are
eligible for this model. You have complete flexibility to turn services on and off and to switch between services as your
business requires throughout the duration of your contract. This commercial model is available in the following flavors: SAP
BTP Enterprise Agreement (SAP BTPEA), Cloud Platform Enterprise Agreement (CPEA), and Pay-As-You-Go for SAP BTP.

For more information, see What Is the Consumption-Based Commercial Model?

Subscription-based commercial model: Your organization subscribes only to the services that you plan to use. You can
then use these services at a fixed cost, irrespective of consumption.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 10/15/24, 3:53 PM
For more information, see What Is the Subscription-Based Commercial Model?

Account Model

The SAP BTP cockpit is structured according to global accounts, directories, and subaccounts:

A global account is the realization of a contract you or your company has made with SAP. A global account is used to
manage subaccounts, members, entitlements and quotas. You receive entitlements and quotas to use platform resources
per global account and then distribute the entitlements and quotas to the subaccount for actual consumption. There are
two types of commercial models for global accounts: consumption-based model and subscription-based model. See
Commercial Models

With directories, you can organize and manage your subaccounts according to your technical and business needs.

Subaccounts let you structure a global account according to your organization’s and project’s requirements with regard to
members, authorizations, and entitlements.

In the SAP BTP, Cloud Foundry environment, the subaccount is divided into one or more spaces, which is where application
development, deployment, and maintenance take place.

For more information, see Account Model.

Entitlements and Quotas

When you purchase an enterprise account, you’re entitled to use a specific set of resources, such as the amount of memory that
can be allocated to your applications.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 10/15/24, 3:53 PM
On SAP BTP, all external dependencies such as databases, messaging systems, files systems, and so on, are services. In
this context, multitenant applications and environments are considered services.

Each service has one or more service plans available. A service plan is the representation of the costs and benefits for a
given variant of a particular service. For instance, a database may be configured with various "T-shirt sizes", each of which
is a different service plan.

An entitlement is your right to provision and consume a resource. In other words, entitlements are the service plans that
you're entitled to use.

A quota represents the numeric quantity of a service plan that you're entitled to consume in your global account and its
subaccounts.

For more information, see Entitlements and Quotas.

User and Member Management

On SAP BTP, member management takes place at all levels from global account to environment, while user management is
relevant for business applications.

User accounts enable users to log on to SAP BTP, access subaccounts, and to use applications according to the permissions
granted to them. We distinguish between two types of users:

Platform users are usually developers, administrators or operators who deploy, administer, and troubleshoot applications
and services on SAP BTP.

Business users use the applications that are deployed to SAP BTP. For example, the end users of SaaS apps or services,
such as SAP Workflow service or SAP Cloud Integration, or end users of your custom applications are business users.

Member management refers to managing permissions for platform users. A member is a user who is assigned to an SAP BTP
global account or subaccount. Administrators can add users to global accounts and subaccounts and assign roles to them as
needed. You can use predefined roles, for example the administrator role for managing subaccount members.

User management refers to managing authentication and authorization for your business users.

For more information, see User and Member Management.

Tools, Programming Models, Programming Languages, and APIs

This is custom documentation. For more information, please visit the SAP Help Portal 6
 10/15/24, 3:53 PM
SAP BTP provides various programming languages and tools for your development project:

SAP BTP includes many tools to help you develop and manage applications, and connect them to your on-premise systems.
For more information, see Tools.

SAP BTP supports many different programming languages; the availability of each depends on the development
environment you're using. For more information, see Programming Languages.

The SAP Cloud Application Programming Model offers a consistent end-to-end programming model that includes
languages, libraries, and APIs that are tailored for full-stack development on SAP BTP. For more information, see
Programming Models.

Depending on your use case, you can choose between different offerings for continuous integration and delivery. For more
information, see Continuous Integration and Delivery (CI/CD).

Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP. For more information, see APIs.

Solutions and Services

Consume the solutions and services by SAP BTP according to your preferred development environment and use cases.

Solutions

SAP BTP offers fast in-memory processing, sustainable, agile solutions and services to integrate data and extend applications,
and fully embedded analytics and intelligent technologies.

Services

Services enable, facilitate, or accelerate the development of business applications and other platform services on SAP BTP.
Services are grouped into the following service types:

Business services: Services that enable, facilitate, or accelerate the development of business process components or
provide industry-specific functionalities or content within a business application.

Technical services: Services that enable, facilitate, or accelerate the development of general or domain independent
content within a business application, independent of the application's business process or task.

You find all available services, solutions, and use cases in the SAP Discovery Center .

Use the service catalog to access service-specific resources:

This is custom documentation. For more information, please visit the SAP Help Portal 7
 10/15/24, 3:53 PM

Regions
You can deploy applications in different regions. Each region represents a geographical location (for example, Europe, US East)
where applications, data, or services are hosted.

About SAP BTP Regions

Regions are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft
Azure, Google Cloud, and Alibaba Cloud. The third-party region providers operate the infrastructure layer of the regions, whereas
SAP operates the platform layer and Cloud Foundry.

For an overview of all available regions, see SAP Discovery Center :

This is custom documentation. For more information, please visit the SAP Help Portal 8
 10/15/24, 3:53 PM

Selecting a Region

A region is chosen at the subaccount level. For each subaccount, you select exactly one region. The selection of a region is
dependent on many factors: For example, application performance (response time, latency) can be optimized by selecting a region
close to the user. For more information, see Selecting a Region.

Deploying Applications in Regions

When deploying applications, consider that a subaccount is associated with a particular region and that this is independent of your
own location. You may be located in the United States, for example, but operate your subaccount in a region in Europe. For more
information on subaccounts, see Subaccounts.

To deploy an application in more than one region, execute the deployment separately for each host. For more information, see
Deploy an Application.

Within a region, there can be multiple instances of the SAP BTP, Cloud Foundry environment. When creating a subaccount, SAP
BTP automatically assigns the account to a specific instance of the environment. Several subaccounts of the same global account
can be located in different datacenters in one region. This also affects the format of the API endpoint URL that is displayed in the
cockpit after enabling Cloud Foundry in your subaccount. There are two possible formats for the API endpoint URL, either
displayed with or without an index. Here's an example for eu10:

 Example
https://api.cf.eu10.hana.ondemand.com

https://api.cf.eu10-<XXX>.hana.ondemand.com

In both cases, the subaccount is located in the region eu10. The differences in the URLs are only an indicator of technical details on
the side of SAP BTP and do not affect the functionality of your applications. For information on enabling Cloud Foundry, see Create
Orgs.

High Availability
This is custom documentation. For more information, please visit the SAP Help Portal 9
 10/15/24, 3:53 PM
SAP has a number of processes in place to support resilience in SAP BTP, and provides different offerings so that you can support
the high availability of your applications. For more information, see Resilience, High Availability, and Disaster Recovery.

EU Access

Some customer contracts include EU Access, which restricts processing of personal data to EEA/Switzerland. If the global
account is marked with EU Access, the actual EU Access compliance status of subaccounts will be displayed during creation of
subaccounts.

 Note
If you require a subaccount with EU Access, make sure to select a provider and region where EU Access is available. Regions
that allow for EU Access are labeled as such in the map view filter in the SAP Discovery Center.

For some services, EU Access is generally not available, not even if the provider and region support EU Access.

Related Information
Regions and API Endpoints Available for the Cloud Foundry Environment
Regions and API Endpoints for the ABAP Environment
Regions for the Kyma Environment

Regions and API Endpoints Available for the Cloud Foundry

Environment
Regions for Enterprise Accounts

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

Microsoft eu20 Europe cf-eu20 West cf-eu20: cf-eu20: cf-eu20:

Azure (Netherlands) Europe
52.149.67.35, 40.119.153.88 api.cf.eu20.hana.ondemand.com
20.82.96.175,
cf-eu20-001: cf-eu20-001:
20.82.96.178,
20.82.96.211, 20.82.83.59 api.cf.eu20-
20.82.96.244, 001.hana.ondemand.com
20.82.96.220,
20.82.96.227,
20.82.97.50,
20.82.96.240,
20.82.96.234,
20.82.97.38,
20.82.96.222,
20.82.96.233,
20.82.96.248,
20.82.97.31,
20.82.97.45,
52.149.96.147,
20.56.169.152,
20.56.169.69,
20.56.169.0,

This is custom documentation. For more information, please visit the SAP Help Portal 10
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

20.56.169.41,
20.56.169.58,
20.56.169.161,
20.56.169.116,
20.56.169.167,
20.56.169.50,
20.56.169.175,
20.56.169.131,
20.56.169.66,
20.56.169.71,
20.56.169.138,
20.56.169.91,
52.142.226.14,
20.86.1.84,
20.86.1.80,
20.86.0.233,
20.86.1.131,
20.86.1.54,
20.86.1.128,
20.86.1.134,
20.86.1.163,
20.86.1.15,
20.86.0.250,
20.86.1.107,
20.86.1.157,
20.86.0.253,
20.86.1.12,
20.86.1.97

cf-eu20-001:

20.54.248.90,
20.54.248.142,
20.54.250.88,
20.54.250.91,
20.56.17.109,
20.56.18.130,
20.56.18.132,
20.56.18.179,
20.86.17.114,
20.86.17.142,
20.86.17.153,
20.86.17.159

Microsoft ap20 Australia cf-ap20 Australia 40.82.211.52, 20.53.99.41 api.cf.ap20.hana.ondemand.com

Azure (Sydney) East 40.82.206.131,
20.70.176.247,
20.40.81.59,
20.40.80.246,
20.40.81.36,
20.70.208.178,
20.70.208.228,
20.70.208.235,

This is custom documentation. For more information, please visit the SAP Help Portal 11
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

20.70.201.155,
20.70.201.89,
20.70.201.66

Microsoft ap21 Singapore cf-ap21 Southeast 40.90.179.153, 20.184.61.122 api.cf.ap21.hana.ondemand.com

Azure Asia 20.198.169.214,
20.198.168.45,
20.198.169.5,
40.90.170.226,
20.198.225.78,
20.198.225.102,
20.198.225.27,
40.90.162.117,
20.191.154.174,
20.191.154.191,
20.191.154.193

Microsoft us20 US West (WA) cf-us20 West US 2 40.90.195.191, 40.91.120.100 api.cf.us20.hana.ondemand.com

Azure 20.57.129.106,
20.57.128.95,
20.57.128.118,
40.90.209.71,
20.72.210.109,
20.72.209.240,
20.72.209.187,
40.90.200.224,
40.90.201.197,
40.90.201.85,
40.90.200.237

Microsoft jp20 Japan (Tokyo) cf-jp20 Japan East 52.185.186.130, 20.43.89.91 api.cf.jp20.hana.ondemand.com
Azure 20.194.193.229,
20.194.193.167,
20.194.194.97,
40.81.200.207,
20.78.122.9,
20.78.121.237,
20.78.122.8,
20.40.96.175,
20.78.2.104,
20.78.2.106,
20.78.2.107

Microsoft us21 US East (VA) cf-us21 East US 40.90.251.147, 40.88.52.17 api.cf.us21.hana.ondemand.com

Azure 52.146.1.155,
20.51.255.236,
52.146.1.223,
40.90.232.167,
20.55.49.185,
20.55.49.92,
20.55.49.186,
40.90.231.101,
52.151.248.29,

This is custom documentation. For more information, please visit the SAP Help Portal 12
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

52.146.15.82,
52.146.10.227

Microsoft ch20 Switzerland cf-ch20 Switzerland 20.208.128.83, 20.208.56.83 api.cf.ch20.hana.ondemand.com

Azure (Zurich) North 20.208.128.86,
20.208.128.87,
20.208.128.88,
51.103.208.79,
51.103.208.81,
51.103.208.85,
51.103.208.87,
51.107.2.38,
51.107.2.50,
51.107.2.52,
51.107.2.54

Amazon br10 Brazil (São cf-br10 sa-east-1 52.67.245.111, 18.229.91.150, api.cf.br10.hana.ondemand.com

Web Paulo) 18.231.45.151, 52.67.135.4,
Services 54.207.173.126, 54.232.179.204,
18.230.81.234, 18.228.53.198,
18.229.169.29, 52.67.149.240,
54.94.110.127, 54.94.179.209
18.231.101.158,
177.71.170.199,
54.232.227.140,
52.67.251.43,
54.232.20.181,
54.94.136.11,
52.67.221.224,
18.229.54.222,
54.232.250.83,
18.228.194.102,
18.228.198.142,
177.71.168.150

Amazon jp10 Japan (Tokyo) cf-jp10 ap- 54.238.10.97, 3.114.248.68, api.cf.jp10.hana.ondemand.com

Web northeast-1 54.250.43.250, 3.113.252.15,
Services 52.192.218.156, 13.114.117.83,
35.74.54.33, 18.178.155.134,
18.177.86.79, 57.180.140.5,
35.74.144.49, 57.180.145.179
3.114.115.232,
18.179.150.168,
54.249.134.63,
18.179.66.68,
54.250.33.48,
54.95.22.24,
52.198.77.221,
35.73.255.50,
54.178.62.192,
3.113.232.224,
52.198.66.114,
13.230.215.218

This is custom documentation. For more information, please visit the SAP Help Portal 13
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

Amazon ap10 Australia cf-ap10 ap- 52.62.223.36, 13.236.220.84, api.cf.ap10.hana.ondemand.com

Web (Sydney) southeast- 13.55.100.204, 13.211.73.244,
Services 2 13.54.168.75, 3.105.95.184,
13.55.239.117, 13.55.188.95,
13.210.173.131, 3.105.212.249,
13.54.77.205, 3.106.45.106
13.237.182.31,
52.65.102.82,
54.79.72.145,
13.236.142.207,
54.79.43.227,
13.54.252.220,
54.79.26.135,
13.54.220.129,
13.236.59.235,
13.238.9.23,
54.153.242.51,
3.105.234.54

Amazon ap11 Asia Pacific cf-ap11 ap- 13.251.40.148, 18.139.147.53, api.cf.ap11.hana.ondemand.com

Web (Singapore) southeast-1 13.228.68.14, 3.0.9.102,
Services 13.251.49.36, 18.140.39.70,
52.76.185.92, 13.229.158.122,
13.229.13.240, 18.140.228.217,
54.251.74.134, 52.74.215.89
52.220.111.202,
54.179.77.154,
52.76.123.164,
54.179.253.138,
13.213.119.83,
3.1.38.48,
52.76.114.209,
13.213.105.43,
13.213.132.88,
13.250.92.77,
18.140.150.56,
18.140.255.164

Amazon ap12 Asia Pacific cf-ap12 ap- 15.165.116.197, 3.35.106.215, api.cf.ap12.hana.ondemand.com

Web (Seoul) northeast-2 54.180.53.68, 3.35.255.45,
Services 3.35.252.222, 3.35.215.12,
52.78.49.16, 13.209.236.215,
15.164.33.162, 43.201.194.105,
3.34.19.116, 43.202.204.5
3.36.2.67,
3.35.57.231,
15.164.254.80,
3.36.165.189,
52.78.38.74,
15.165.249.251,
13.124.251.247,

This is custom documentation. For more information, please visit the SAP Help Portal 14
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

13.124.16.17,
15.165.83.237

Amazon ca10 Canada cf-ca10 ca-central-1 35.182.118.205, 35.183.74.34, api.cf.ca10.hana.ondemand.com

Web (Montreal) 35.182.198.31, 35.182.75.101,
Services 3.98.159.3, 3.98.102.153,
3.96.101.45, 15.157.88.166,
15.222.120.34, 3.98.202.222,
3.96.14.215, 52.60.210.33
3.97.48.154,
3.97.119.250,
35.182.95.49,
3.97.228.23,
35.182.185.156,
3.98.252.245,
15.223.62.0,
99.79.181.241,
3.98.167.60,
99.79.110.245,
52.60.239.204,
52.60.212.33

Amazon eu10 Europe cf-eu10 eu-central- cf-eu10: cf-eu10: cf-eu10:

Web (Frankfurt) 1
52.59.128.222, 3.124.208.223, api.cf.eu10.hana.ondemand.com
Services
52.28.241.88, 3.122.209.241,
cf-eu10-002:
18.184.81.94, 3.124.222.77,
3.67.200.70, 18.159.31.22, api.cf.eu10-
3.68.51.135, 3.69.186.98, 002.hana.ondemand.com
3.124.174.204, 3.77.195.119
3.68.31.37, cf-eu10-003:
cf-eu10-002:
3.67.58.183,
api.cf.eu10-
3.67.0.172, 3.126.229.22, 003.hana.ondemand.com
3.67.244.62, 18.193.180.19,
3.126.117.58, 3.64.227.236, cf-eu10-004:
3.66.100.105, 18.153.123.11,
3.68.13.226, api.cf.eu10-
3.121.37.195,
3.126.45.133, 004.hana.ondemand.com
3.73.215.90
3.67.249.135,
18.194.183.183, cf-eu10-003:
3.67.246.74,
3.127.77.3,
3.66.68.201,
3.64.196.58,
3.68.0.70,
18.156.151.247,
52.28.56.202,
18.197.252.154,
3.126.95.250,
3.79.137.29,
3.66.68.127,
52.58.93.50
18.195.244.40,
3.67.107.121, cf-eu10-004:
3.67.24.253,
18.193.50.255, 3.70.38.218,

3.121.35.143 18.196.206.8,
3.65.185.47,
cf-eu10-002: 3.73.109.100,

This is custom documentation. For more information, please visit the SAP Help Portal 15
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

18.198.196.89, 3.73.8.210,
18.193.21.232, 52.59.18.183
3.65.9.91,
52.29.190.137,
18.197.134.65,
3.67.182.154,
3.67.255.232,
3.66.249.150,
3.68.44.236

cf-eu10-003:

3.64.131.199,
3.64.88.217,
3.64.142.243,
18.198.18.157,
3.68.40.83,
3.67.235.98,
3.68.17.221,
18.198.149.19,
3.68.38.23

cf-eu10-004:

3.69.195.103,
3.64.170.167,
3.68.176.248,
3.121.49.211,
18.197.219.60,
3.70.38.84

Amazon eu11 Europe cf-eu11 eu-central- 18.156.140.38, 18.156.209.198, api.cf.eu11.hana.ondemand.com

Web (Frankfurt) 1 3.121.55.100, 18.157.105.117,
Services 35.156.198.246, 3.124.207.41,
52.59.77.121, 3.66.26.249,
18.185.57.85, 3.72.216.204,
3.121.79.209, 3.74.99.245
3.67.237.8,
35.156.31.32,
3.65.63.251,
3.122.176.63,
18.198.13.57,
18.157.114.142,
18.184.172.97,
18.159.180.188,
35.157.5.44

Amazon us10 US East (VA) cf-us10 us-east-1 cf-us10: cf-us10: cf-us10:

Web
52.200.16.71, 52.4.101.240, api.cf.us10.hana.ondemand.com
Services
52.23.123.125, 52.23.1.211,
cf-us10-001:
52.202.170.155, 52.23.189.23,
18.210.47.160, 18.213.242.208, api.cf.us10-
18.211.235.11, 3.214.110.153, 001.hana.ondemand.com
54.156.172.106, 34.205.56.51

This is custom documentation. For more information, please visit the SAP Help Portal 16
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

34.234.191.59, cf-us10-001: cf-us10-002:

34.192.134.47,
3.227.182.44, api.cf.us10-
18.204.173.15,
52.86.131.53, 002.hana.ondemand.com
3.213.197.54,
3.220.114.17,
184.73.43.82,
44.218.82.203,
52.20.242.182,
44.219.57.163,
3.216.16.207,
50.16.106.103
34.225.190.250,
52.2.110.230, cf-us10-002:
54.234.93.200,
35.153.88.132, 107.20.66.86,
52.204.111.138, 54.234.152.59,
3.88.250.160, 34.202.68.0,
54.221.30.91, 3.214.116.95,
52.71.83.110, 54.144.230.36,
52.200.165.163, 54.226.37.104
54.208.119.130,
34.202.136.35,
34.192.100.96,
54.85.65.82,
54.205.71.200

cf-us10-001:

52.0.214.195,
18.213.153.162,
54.227.144.195,
3.225.73.158,
34.233.151.91,
23.23.172.117,
3.222.22.16,
34.238.1.234,
34.194.239.31,
3.225.44.56,
34.201.208.150,
75.101.157.228

cf-us10-002:

54.162.233.194,
34.206.160.141,
35.168.80.144,
18.232.28.65,
54.82.224.146,
3.221.4.74,
18.211.12.227,
54.159.45.198,
72.44.51.245

Google us30 US Central cf-us30 us-central1 35.202.96.192, 35.184.169.79 api.cf.us30.hana.ondemand.com

Cloud (IA) 35.193.171.152,
35.193.168.31,
35.202.69.204,
35.202.175.147,

This is custom documentation. For more information, please visit the SAP Help Portal 17
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

35.193.69.164,
35.202.1.6,
23.236.63.113,
35.193.30.116,
35.202.66.196,
34.68.152.205,
35.222.158.222,
104.197.20.168,
35.232.105.70,
35.224.211.196,
35.222.192.158,
35.193.8.172,
34.171.4.220,
34.172.37.175,
34.170.206.220,
34.172.145.231,
35.222.38.254,
35.239.28.216,
34.134.91.47,
34.123.17.36,
35.202.205.85,
34.118.207.84,
35.193.6.192,
34.122.222.203,
104.197.157.121,
34.135.159.154,
35.223.208.27,
146.148.74.171,
34.132.192.46,
34.68.109.37,
104.198.49.58,
35.225.164.132

Google eu30 Europe cf-eu30 europe- 34.107.28.38, 35.198.143.110 api.cf.eu30.hana.ondemand.com

Cloud (Frankfurt) west3 34.141.10.217,
34.141.116.52,
34.141.1.228,
34.141.123.52,
34.141.125.107,
34.141.46.51,
34.89.130.182,
34.89.146.167,
34.89.203.91,
34.89.232.158,
34.89.243.40,
35.198.83.71,
35.234.65.38,
35.242.208.222,
35.246.155.42,
35.246.171.35,
34.141.28.26,
34.159.160.86,
34.107.19.175,

This is custom documentation. For more information, please visit the SAP Help Portal 18
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

34.159.165.29,
35.242.240.154,
34.141.73.130,
34.159.27.236,
34.89.152.211,
35.242.194.75,
35.246.235.253,
34.159.127.190,
34.141.82.126,
35.234.69.102,
34.89.231.53,
34.159.188.133,
35.246.203.194,
34.159.201.78,
34.141.112.232,
35.198.84.213,
34.89.165.33

Google in30 India cf-in30 asia-south1 34.93.27.36, 34.93.125.74 api.cf.in30.hana.ondemand.com

Cloud (Mumbai) 34.93.89.145,
34.93.92.210,
34.93.137.163,
34.93.148.247,
34.93.155.252,
34.93.166.164,
34.93.180.0,
34.93.221.129,
35.200.131.125,
35.200.144.1,
35.200.175.62,
35.200.183.224,
35.200.194.175,
35.200.198.26,
35.200.209.142,
35.244.29.120,
35.200.137.225,
34.100.186.241,
35.200.169.254,
35.200.151.131,
35.200.252.103,
35.244.15.103,
35.244.16.76,
34.93.255.115,
35.244.53.153,
35.200.168.60,
35.200.222.30,
34.100.178.164,
35.244.2.193,
34.93.11.49,
34.100.211.195,
34.100.151.15,
34.93.95.83,
34.100.215.143,

This is custom documentation. For more information, please visit the SAP Help Portal 19
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

34.93.205.174,
34.93.159.24

Google il30 Israel (Tel cf-il30 me-west1 34.165.0.14, 34.165.59.26 api.cf.il30.hana.ondemand.com

Cloud Aviv) 34.165.0.115,
34.165.5.181,
34.165.5.246,
34.165.7.73,
34.165.12.173,
34.165.16.177,
34.165.16.210,
34.165.17.27,
34.165.18.240,
34.165.21.242,
34.165.24.112,
34.165.26.162,
34.165.37.171,
34.165.38.114,
34.165.40.240,
34.165.41.254,
34.165.80.207,
34.165.81.54,
34.165.110.15,
34.165.136.9,
34.165.150.108,
34.165.168.74,
34.165.171.197,
34.165.172.4,
34.165.194.20,
34.165.222.104,
34.165.223.90,
34.165.228.95,
34.165.231.165

Alibaba cn40 China cf-cn40 cn- 101.132.190.155, 139.224.7.71 api.cf.cn40.platform.sapcloud.cn

Cloud (Shanghai) shanghai 106.14.165.33,
106.14.184.113

Google sa30 KSA cf-sa30 me- 34.166.4.164, 34.166.32.46 api.cf.sa30.hana.ondemand.com

Cloud (Dammam) central2 34.166.4.182,
34.166.8.22,
34.166.10.68,
34.166.19.145,
34.166.20.65,
34.166.37.166,
34.166.38.149,
34.166.39.3,
34.166.40.145,
34.166.41.104,
34.166.44.55,
34.166.46.73,
34.166.46.216,
34.166.47.18,

This is custom documentation. For more information, please visit the SAP Help Portal 20
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical NAT IPs LB IPs (ingress, API Endpoint
Provider Key Key of IaaS (egress, IPs for for incoming
Provider requests from a requests)
Cloud Foundry
app)

34.166.50.229,
34.166.52.69,
34.166.53.147,
34.166.55.78,
34.166.57.177,
34.166.60.109,
34.166.61.61,
34.166.61.119,
34.166.61.169,
34.166.61.173,
34.166.62.51,
34.166.62.206,
34.166.63.160,
34.166.64.6,
34.166.65.231

Regions for Trial Accounts

IaaS Region Region Technical Technical Trial NAT IPs LB IPs API Endpoint Domain
Provider Name Key Key of (egress, IPs (ingress, for
IaaS for requests incoming
Provider from a Cloud requests)
Foundry app)

Amazon us10 US East cf-us10 us-east-1 3.218.99.154, 52.23.189.23, api.cf.us10.hana.ondemand.com us10.han

Web (VA) 52.72.147.227, 52.4.101.240,
Services 3.218.112.63 52.23.1.211

Microsoft ap21 Singapore cf-ap21 Southeast 52.139.216.172, 20.184.61.122 api.cf.ap21.hana.ondemand.com ap21.han

Azure Asia 20.195.24.178,
20.195.9.169

 Note
Trial accounts and subaccounts on trial can no longer be created on eu10, Europe (Frankfurt).

Existing trial accounts and subaccounts are not affected.

 Note
In the Cloud Foundry environment, IPs are controlled by the respective IaaS provider (AWS, Azure, or Google Cloud). IPs may
change due to network updates on the provider side. Any planned changes will be announced at least four weeks before they
take effect.

 Note
In the Cloud Foundry environment, the region in which a global account was created determines the API endpoint of all
subaccounts associated with it. For example, subaccounts created in a global account in region eu10 share the API endpoint
URL api.cf.eu10.hana.ondemand.com.

This is custom documentation. For more information, please visit the SAP Help Portal 21
 10/15/24, 3:53 PM

Regions and API Endpoints for the ABAP Environment

Regions for Enterprise Accounts

IaaS Region Region Name Technical Technical Key of NAT IPs (egress, IPs for API Endpoint Dom
Provider Key IaaS Provider requests from an ABAP
System)

Amazon ap10 Australia cf-ap10 ap-southeast-2 54.153.226.137, api.cf.ap10.hana.ondemand.com ap1

Web (Sydney) 54.153.194.85,
Services 54.79.209.86,
13.238.93.75

Amazon br10 Brazil (Sao cf-br10 sa-east-1 52.67.140.201, api.cf.br10.hana.ondemand.com br10

Web Paulo) 54.207.133.145,
Services 15.229.97.244,
18.228.92.201

Amazon ca10 Canada cf-ca10 ca-central-1 15.222.180.159, api.cf.ca10.hana.ondemand.com ca10

Web (Montreal) 15.222.175.12,
Services 52.60.183.108,
3.97.94.144

Amazon eu10 Europe cf-eu10 eu-central-1 18.197.217.237, cf-eu10: cf-e

Web (Frankfurt) 18.198.153.44, api.cf.eu10.hana.ondemand.com eu1
Services 18.157.206.182,
cf-eu10-002: api.cf.eu10- cf-e
52.57.94.154,
002.hana.ondemand.com 002
3.74.95.163,
18.156.20.40, cf-eu10-003: api.cf.eu10- cf-e
3.70.85.193, 3.76.177.92, 003.hana.ondemand.com 003
18.196.196.117,3.127.41.81,
3.69.221.68, cf-eu10-004: api.cf.eu10- cf-e
3.67.230.143, 004.hana.ondemand.com 004
3.74.106.119,
18.199.199.153,
3.78.46.180

Amazon eu11 Europe cf-eu11 eu-central-1 18.157.200.44, api.cf.eu11.hana.ondemand.com eu1

Web (Frankfurt) 3.121.238.156,
Services EU Access 3.67.47.252,
18.195.136.83,
3.120.9.225,
3.68.253.186

Amazon jp10 Japan (Tokyo) cf-jp10 ap-northeast-1 35.75.28.56, api.cf.jp10.hana.ondemand.com jp10

Web 35.74.196.78,
Services 35.74.158.17,
54.250.128.197,
52.196.122.86

Amazon ap11 Singapore cf-ap11 ap-southeast-1 54.179.221.168, api.cf.ap11.hana.ondemand.com ap1

Web 18.140.151.124,
Services 54.254.21.208,
54.251.135.238

Amazon ap12 South Korea cf-ap12 ap-northeast-2 3.39.57.235, 13.125.0.129, api.cf.ap12.hana.ondemand.com ap1
Web (Seoul) 13.124.63.148,
Services 13.209.63.123

This is custom documentation. For more information, please visit the SAP Help Portal 22
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical Key of NAT IPs (egress, IPs for API Endpoint Dom
Provider Key IaaS Provider requests from an ABAP
System)

Amazon us10 US East (VA) cf-us10 us-east-1 54.243.29.110, cf-us10: cf-u

Web 18.215.92.120, api.cf.us10.hana.ondemand.com us1
Services 34.232.200.153,
cf-us10-001: api.cf.us10- cf-u
18.232.247.104,
001.hana.ondemand.com 001
3.209.189.244,
18.204.158.200, cf-us10-002: api.cf.us10- cf-u
23.20.221.103, 002.hana.ondemand.com 002
54.86.32.250,
52.1.255.25

Microsoft eu20 Europe cf-eu20 westeurope 74.234.204.238, cf-eu20: cf-e

Azure (Netherlands) 98.71.236.50, api.cf.eu20.hana.ondemand.com eu2
108.143.241.97
cf-eu20-001: api.cf.eu20- cf-e
001.hana.ondemand.com 001

Microsoft ch20 Switzerland cf-ch20 switzerlandnorth 172.162.240.234, api.cf.ch20.hana.ondemand.com ch2

Azure (Zurich) 51.107.40.177,
Azure EU 51.103.221.23
Access

Microsoft us20 US West (WA) cf-us20 westus2 20.9.136.184, api.cf.us20.hana.ondemand.com us2

Azure 172.179.0.166,
20.9.147.50

Microsoft us21 US East (VA) cf-us21 eastus 172.190.88.27, api.cf.us21.hana.ondemand.com us2

Azure 20.83.171.94,
74.235.125.210

Microsoft ap20 Australia cf-ap20 australiaeast 20.211.81.46, api.cf.ap20.hana.ondemand.com ap2

Azure (Sydney) 20.70.213.77,
20.211.46.196

Microsoft ap21 Singapore cf-ap21 southeastasia 20.6.9.203, api.cf.ap21.hana.ondemand.com ap2

Azure 20.198.169.36,
20.195.25.14

Microsoft jp20 Japan (Tokyo) cf-jp20 japaneast 20.78.124.111, api.cf.jp20.hana.ondemand.com jp20

Azure 20.63.141.36, 20.78.37.7

Google eu30 Europe cf-eu30 europe-west3 34.141.88.79, api.cf.eu30.hana.ondemand.com eu3

Cloud (Frankfurt) 34.159.65.75,
34.141.107.207,
34.141.42.177,
34.141.126.80,
34.159.215.19

Google in30 India cf-in30 asia-south1 34.93.58.135, api.cf.in30.hana.ondemand.com in30

Cloud (Mumbai) 35.200.177.49,
35.244.63.61,
34.93.41.126,
34.93.191.130,
35.200.168.232

Google us30 US Central cf-us30 us-central1 34.121.78.84, api.cf.us30.hana.ondemand.com us3

Cloud (IA) 34.122.132.185,

This is custom documentation. For more information, please visit the SAP Help Portal 23
 10/15/24, 3:53 PM

IaaS Region Region Name Technical Technical Key of NAT IPs (egress, IPs for API Endpoint Dom
Provider Key IaaS Provider requests from an ABAP
System)

104.154.245.19,
34.171.92.122,
35.224.140.73,
34.31.173.8

Regions for Trial Accounts

IaaS Region Region Technical Technical Key Trial NAT IPs API Endpoint Domain
Provider Name Key of IaaS (egress, IPs
Provider for requests
from a Cloud
Foundry app)

Amazon us10 US East cf-us10 us-east-1 3.218.99.154, api.cf.us10.hana.ondemand.com us10.hana.ondemand

Web (VA) 52.72.147.227,
Services 3.218.112.63

Microsoft ap21 Singapore cf-ap21 southeastasia 20.6.9.203, api.cf.ap21.hana.ondemand.com ap21.hana.ondemand

Azure 20.198.169.36,
20.195.25.14

Regions for the Kyma Environment

To work with the Kyma environment, you need to specify the region for both your subaccount and the cluster.

 Note
In the Kyma environment, IP addresses for NAT Gateway that handles the egress traffic are configured dynamically. This means
that you cannot identify the IP address of NAT Gateway in advance. However, once the IP address is assigned, it remains
unchanged throughout the cluster's lifecycle.

Subaccount Regions
The table lists the regions you can choose from when creating a subaccount.

Subaccount Regions for Kyma

Global Account Region IaaS Provider Technical Key Region Name Plan ID
Type

Enterprise account ap21 Microsoft Azure cf-ap21 Singapore azure

Partner Test, Demo, azure_lite

and Development
trial
account

Trial account

Enterprise account us20 Microsoft Azure cf-us20 US West (WA) azure

Partner Test, Demo, azure_lite

and Development
account

This is custom documentation. For more information, please visit the SAP Help Portal 24
 10/15/24, 3:53 PM

Global Account Region IaaS Provider Technical Key Region Name Plan ID
Type

Enterprise account jp20 Microsoft Azure cf-jp20 Japan (Tokyo) azure

Partner Test, Demo, azure_lite

and Development
account

Enterprise account us21 Microsoft Azure cf-us21 US East (VA) azure

Partner Test, Demo, azure_lite

and Development
account

Enterprise account eu20 Microsoft Azure cf-eu20 Europe azure

(Netherlands)
Partner Test, Demo, azure_lite
and Development
account

Enterprise account ap20 Microsoft Azure cf-ap20 Australia (Sydney) azure

Partner Test, Demo, azure_lite

and Development
account

Enterprise account br20 Microsoft Azure cf-br20 Brazil (São Paulo) azure

Partner Test, Demo, azure_lite

and Development
account

Enterprise account ch20 Microsoft Azure cf-ch20 Switzerland (Zurich) azure

EU Access

Enterprise account us10 Amazon Web cf-us10 US East (VA) aws

Services
Trial account trial

Enterprise account eu10 Amazon Web cf-eu10 Europe (Frankfurt) aws

Services
Trial account trial

Enterprise account eu11 Amazon Web cf-eu11 Europe (Frankfurt) aws

Services EU Access

Enterprise account br10 Amazon Web cf-br10 Brazil (São Paulo) aws
Services

Enterprise account jp10 Amazon Web cf-jp10 Japan (Tokyo) aws

Services

Enterprise account ca10 Amazon Web cf-ca10 Canada (Montreal) aws

Services

Enterprise account ap12 Amazon Web cf-ap12 South Korea (Seoul) aws
Services

Enterprise account ap10 Amazon Web cf-ap10 Australia (Sydney) aws

Services

This is custom documentation. For more information, please visit the SAP Help Portal 25
 10/15/24, 3:53 PM

Global Account Region IaaS Provider Technical Key Region Name Plan ID
Type

Enterprise account ap11 Amazon Web cf-ap11 Singapore aws

Services

Enterprise account us30 Google Cloud cf-us30 US Central (IA) gcp

Enterprise account eu30 Google Cloud cf-eu30 Europe (Frankfurt) gcp

Enterprise account in30 Google Cloud cf-in30 India (Mumbai) gcp

Enterprise account jp30 Google Cloud cf-jp30 Japan (Osaka) gcp

Enterprise account sa30 Google Cloud cf-sa30 KSA (Dammam) gcp

Enterprise account il30 Google Cloud cf-il30 Israel (Tel Aviv) gcp

Enterprise account br30 Google Cloud cf-br30 Brazil (São Paulo) gcp

Enterprise account ap30 Google Cloud cf-ap30 Australia (Sydney) gcp

Cluster Regions
When you enable a Kyma environment for a given subaccount, you must select a plan and region where the cluster is going to be
created. Note that there is a number of regions available within each plan. They are all listed in the table:

Cluster Regions

Hyperscaler Plan ID Region Region Name

Microsoft Azure azure centralus US Central (IA)

azure_lite eastus US East (VA)

westus2 US West (WA)

northeurope North EU (Ireland)

uksouth UK South (London)

japaneast Japan (Tokyo)

southeastasia Singapore

westeurope Europe (Netherlands)

australiaeast Australia (Sydney)

switzerlandnorth Switzerland (Zurich)

brazilsouth Brazil (São Paulo)

trial southeastasia Singapore

Amazon Web Services aws eu-central-1 Europe (Frankfurt)

eu-west-2 Europe (London)

ca-central-1 Canada (Montreal)

This is custom documentation. For more information, please visit the SAP Help Portal 26
 10/15/24, 3:53 PM

Hyperscaler Plan ID Region Region Name

sa-east-1 Brazil (São Paulo)

us-east-1 US East (VA)

us-west-1 US West (N. California)

ap-northeast-1 Japan (Tokyo)

ap-northeast-2 South Korea (Seoul)

ap-south-1 India (Mumbai)

ap-southeast-1 Singapore

ap-southeast-2 Australia (Sydney)

trial eu-central-1 Europe (Frankfurt)

us-east-1 US East (VA)

Google Cloud gcp europe-west3 Europe (Frankfurt)

us-central1 US Central (IA)

asia-south1 India (Mumbai)

asia-northeast2 Japan (Osaka)

me-central2 KSA (Dammam)

me-west1 Israel (Tel Aviv)

australia-southeast1 Australia (Sydney)

southamerica-east1 Brazil (São Paulo)

Load Balancers
Depending on the IaaS Provider, the following Load Balancers are provisioned by default:

Default Load Balancers

IaaS Provider Default Load Balancer

Microsoft Azure Standard

Amazon Web Services Classic Network Load Balancer

Google Cloud External passthrough Network Load Balancer

For more details on the Load Balancers and their features, check out the official documention of the respective IaaS provider.

Related Information
Create a Kyma Instance
Available Plans in the Kyma Environment
Provisioning and Updating Parameters in the Kyma Environment

This is custom documentation. For more information, please visit the SAP Help Portal 27
 10/15/24, 3:53 PM

Resilience, High Availability, and Disaster Recovery

SAP has a number of processes in place to support resilience in SAP BTP, and provides different offerings so that you can support
the high availability of your applications.

How SAP Provides Resilience

SAP applies resilience principles when developing, updating, and deploying our SAP BTP applications and services.

SAP BTP provides resilience through the following:

Processes and Offerings Description Regional

Availability

Availability Zones To achieve better fault-tolerance in the Cloud Foundry environment, we deploy our All regions
services across multiple AZs, which improves the availability of a service if there that support
are issues with the infrastructure of one AZ. For more information, see Availability the Cloud
Zones in the Cloud Foundry Environment. Foundry
runtime. See
Regions and
API
Endpoints
Available for
the Cloud
Foundry
Environment.

Backups in Kyma runtime Kyma runtime relies on managed Kubernetes clusters for periodic backups of All regions
Kubernetes objects. For more information, see Kyma Environment Backup. that support
the Kyma
runtime. See
Regions for
the Kyma
Environment.

Backup and Recovery for SAP If you use SAP HANA Cloud, your SAP HANA Cloud instances are continually All regions
HANA Cloud backed up to safeguard your database and ensure that it can be recovered where SAP
speedily. For more information, see Backup and Recovery. HANA Cloud
is available.
See
Availability of
SAP HANA
Cloud.

Disaster Recovery The SAP BTP Disaster Recovery (DR) Plan is part of the overall SAP BTP Business All regions.
Continuity Plan, which includes crisis management and process continuity
activities that are triggered by a declared disaster. For more information, see
Disaster Recovery as Part of the Business Continuity Plan.

Best Practices for Resilient Applications

In addition to the services offered by SAP BTP, you can follow our best practices for developing and deploying applications, which
allow you to make your application running on SAP BTP stable and highly available.

Develop Resilient Applications

This is custom documentation. For more information, please visit the SAP Help Portal 28
 10/15/24, 3:53 PM
When developing your applications, apply the principles and patterns of resilient software design that fit your use case. For
more information, see Developing Resilient Apps on SAP BTP. For situations where the load is highly available and where
applications need to react by scaling, consider using Application Autoscaler. For more information, see What Is Application
Autoscaler?

Working with Availability Zones

To benefit from the high availability mechanisms in Cloud Foundry, set up your applications with multiple instances. For
more information, see .

Disaster Recovery as Part of the Business Continuity Plan

The cloud platform disaster recovery (DR) plan is part of the overall cloud platform business continuity plan, which includes crisis
management and process continuity activities that are triggered by a declared disaster.

Standard Disaster Recovery

SAP can restore productive tenants from backups as soon as practicable in case of a disaster resulting in the loss of the primary
production data center.

As the magnitude of a disaster is unpredictable, a region might not be restored in a reasonable time. In addition, a new
infrastructure might need to be set up at a different location, which might require the purchase and setup of new hardware.
Therefore, we can't guarantee any fixed recovery timelines.

Environments
Environments constitute the actual platform-as-a-service offering of SAP BTP that allows for the development and administration
of business applications. Environments are anchored in SAP BTP on subaccount level.

Each environment comes equipped with specific tools, technologies, and runtimes that you need to build applications. So a multi-
environment subaccount is your single address to host a variety of applications and offer diverse development options. One
advantage of using different environments in one subaccount is that you only need to manage users, authorizations, and
entitlements once per subaccount, and thus grant more flexibility to your developers.

Environment Instances

To actually use an environment in a subaccount, you must enable it, which creates an instance of that environment. There are
several ways to create environment instances:

In the SAP BTP cockpit, on the subaccount overview, choose Enable.

This is custom documentation. For more information, please visit the SAP Help Portal 29
 10/15/24, 3:53 PM
In the SAP BTP cockpit, under Service Marketplace. Here, you get more information, such as the available plans and links
to further information.

Using the btp CLI command btp create accounts/environment-instance

Cloud Foundry Environment

The Cloud Foundry environment allows you to create polyglot cloud applications in Cloud Foundry. It contains the SAP BTP,
Cloud Foundry runtime service, which is based on the open-source application platform managed by the Cloud Foundry
Foundation.
ABAP Environment
Within the Cloud Foundry environment, you can create a new space for ABAP development. This is what we refer to as the
ABAP environment. It allows you to create extensions for ABAP-based products, such as SAP S/4HANA Cloud, and develop
new cloud applications. You can transform existing ABAP-based custom code or extensions to the cloud.
Kyma Environment
SAP BTP, Kyma runtime provides a fully managed cloud-native Kubernetes application runtime based on the open-source
project "Kyma". Based on modular building blocks, Kyma runtime includes all the necessary capabilities to simplify the
development and to run enterprise-grade cloud-native applications.
Neo Environment
The Neo environment lets you develop HTML5, Java, and SAP HANA extended application services (SAP HANA XS)
applications. You can also use the UI Development Toolkit for HTML5 (SAPUI5) to develop rich user interfaces for modern
web-based business applications.

Related Information
Account Administration

Cloud Foundry Environment

The Cloud Foundry environment allows you to create polyglot cloud applications in Cloud Foundry. It contains the SAP BTP, Cloud
Foundry runtime service, which is based on the open-source application platform managed by the Cloud Foundry Foundation.

The Cloud Foundry environment enables you to develop new business applications and business services, supporting multiple
runtimes, programming languages, libraries, and services. You can leverage a multitude of buildpacks, including community
innovations and self-developed buildpacks. It also integrates with SAP HANA extended application services, advanced model.

For more information about Cloud Foundry, see the official Cloud Foundry documentation at https://docs.cloudfoundry.org/ .

Related Information
Getting Started in the Cloud Foundry Environment
Development in the Cloud Foundry Environment
Administration and Operations in the Cloud Foundry Environment

Supported and Unsupported Cloud Foundry Features

Find out which Cloud Foundry features the Cloud Foundry environment on SAP BTP supports and doesn't support.

Supported Features Unsupported Features

Diego runtime. See Container-to-Container Networking. See

https://docs.cloudfoundry.org/concepts/diego/diego- https://docs.cloudfoundry.org/concepts/understa
architecture.html . networking.html .

This is custom documentation. For more information, please visit the SAP Help Portal 30
 10/15/24, 3:53 PM

Supported Features Unsupported Features

SSH. See https://docs.cloudfoundry.org/devguide/deploy-apps/app- Isolation Segments. See

ssh-overview.html . https://docs.cloudfoundry.org/adminguide/isolat
segments.html .
Custom Domains. See
https://docs.cloudfoundry.org/devguide/deploy-apps/routes- TCP Routing. See
domains.html#domains . https://docs.cloudfoundry.org/adminguide/enabl
routing.html .
Docker. See https://docs.cloudfoundry.org/adminguide/docker.html
. Secure Service Credential Delivery (with Credhub
https://docs.cloudfoundry.org/credhub/index.htm
Running Tasks. See https://docs.cloudfoundry.org/devguide/using-
https://github.com/cloudfoundry/credhub/blob/
tasks.html .
service-credentials.md
Request Tracing

Zipkin Tracing. See

https://docs.cloudfoundry.org/adminguide/zipkin_tracing.html
.

Websockets. See
https://docs.cloudfoundry.org/adminguide/supporting-
websockets.html .

Space-Scoped Service Brokers. See

https://docs.cloudfoundry.org/services/managing-service-
brokers.html .

Route Services (only user-provided and fully-brokered services). See

https://docs.cloudfoundry.org/services/route-services.html .

Sharing Service Instances (not all services support instance sharing).

See https://docs.cloudfoundry.org/devguide/services/sharing-
instances.html .

HTTP/2. See https://docs.cloudfoundry.org/adminguide/supporting-

http2.html#application .

Streaming Logs to Log Management Services. See

https://docs.cloudfoundry.org/devguide/services/log-
management.html .

SAP BTP-Specific Configurations

The following technical configurations are specific to SAP BTP and differ from the default configuration:

SAP BTP supports the Cloud Foundry command line interface (CF CLI) version 8 or newer. Older versions of the CF CLI are
not supported.

By default, a newly pushed (or started) Cloud Foundry application needs to respond to a health check within the first 60
seconds, otherwise the application is considered to have failed. For more information, see
https://docs.cloudfoundry.org/devguide/deploy-apps/healthchecks.html#health_check_timeout . On SAP BTP, however,
you can override this timeout to up to 10 minutes. For instructions, see https://docs.cloudfoundry.org/devguide/deploy-
apps/large-app-deploy.html .

On SAP BTP, application SSH access is disabled by default. For more information on SSH, see
https://docs.cloudfoundry.org/devguide/deploy-apps/app-ssh-overview.html .

SAP BTP supports the Cloud Foundry API version 3. The Cloud Foundry API v2 has been deprecated and is no longer
supported. For more information, see https://v3-apidocs.cloudfoundry.org/ .
This is custom documentation. For more information, please visit the SAP Help Portal 31
 10/15/24, 3:53 PM
On SAP BTP, the Cloud Foundry API is protected by a rate limit against misuse. The limit is in the range of a few 10k
requests per hour per user on average. Starting in April 2023, the rate limit for the deprecated Cloud Foundry API v2 will be
decreased and eventually reach the range of a few hundred requests per hour per user.

In addition to the general rate limit on the Cloud Foundry API, requests for certain API endpoints related to services face a
separate limit on concurrent requests. The Cloud Foundry API responds with HTTP status code 429 if a rate limit is reached
and provides a Retry-After Header suggesting when the client can attempt a retry. For more information, see
https://docs.cloudfoundry.org/running/rate-limit-cloud-controller-
api.html#Rate%20Limit%20Responses:%20Service%20Brokers .

In the SAP BTP, Cloud Foundry environment, the total HTTP Request Header and HTTP Response Header size is limited to
64 KB to protect against misuse.

In the SAP BTP, Cloud Foundry environment, for both HTTP Request Headers and HTTP Response Headers the total
amount of Headers is limited to 101.

In the SAP BTP, Cloud Foundry environment, the limit of concurrent HTTP connections between client and application is
3000 per application container.

In the SAP BTP, Cloud Foundry environment, the HTTP keep-alive timeout towards the client is set to 60s to protect
against misuse. 60s is the maximum time span allowed to wait for a new HTTP request to appear if keep-alive is
enabled.

In the SAP BTP, Cloud Foundry environment, an internal HTTP keep-alive is set to 90s. A higher value must be set on
application-side to avoid intermittent disruptions. For more information, see step 4 of 3406978 .

In the Cloud Foundry environment, there’s a logging rate limit to guard against malicious applications. By default, the limit
is 4000 logs per second per application instance, but in exceptional high load scenarios it may be lowered by the platform.
If this limit is exceeded, additional logs from the application instance are dropped and a warning message is injected into
the application instance’s log stream every second. This message also contains the exact current log rate limit.

Applications requiring sent envelopes to be delivered to external Log Management Services should use the Cloud Foundry
syslog drain capability. See https://docs.cloudfoundry.org/devguide/services/log-management.html .

In the SAP BTP, Cloud Foundry environment, the time between signaling a container to shut down gracefully and forcefully
stopping it is set to 60 seconds. The default in Cloud Foundry is 10 seconds, see
https://docs.cloudfoundry.org/devguide/deploy-apps/app-lifecycle.html#shutdown . This time interval will not be taken
into account if there are no explicit kernel signal handlers implemented in the application.

In the SAP BTP, Cloud Foundry environment, applications get a guaranteed CPU share of ¼ core per GB instance memory.
As the maximum instance memory per application is 16 GB, this allows for vertical scaling up to 4 CPUs.

If applications running on the same virtual machine don't use their guaranteed CPU, other applications might get more
CPU. This isn’t guaranteed and might be subject to change in the future. If you encounter performance problems, scale up
your application or increase the application start timeout.

The number of running threads per application instance is limited to 10,420. Reaching this limit can cause performance
issues.

When pushing or scaling your application, you can define a disk_quota that can be up to 10 GB. For more information,
see https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-attributes.html#disk-quota .

When deploying applications on SAP BTP, the maximum application package size is 1.5 GB. If your application is larger than
that, the deployment fails. For more information, see https://docs.cloudfoundry.org/devguide/deploy-apps/large-app-
deploy.html .

In the SAP BTP, Cloud Foundry environment, the hard limit for open file descriptors is 32,768 (32K) per container.

In global accounts that support the consumption-based commercial model you might see a quota limit for certain services.
This is a technical limit only, not a business limit. If you need to increase this limit, report an incident to SAP support for

This is custom documentation. For more information, please visit the SAP Help Portal 32
 10/15/24, 3:53 PM
component BC-NEO-CIS.

In the SAP BTP, Cloud Foundry environment, the SAP HANA database supports up to 1000 simultaneous connections per
database.

In the SAP BTP, Cloud Foundry environment, each application can be mapped to approximately 1000 routes (128 KB). The
total length of the routing information must not exceed this limit.

Cloud Foundry Audit Events have a retention period of 14 days. For more information on Audit Events, see
https://docs.cloudfoundry.org/running/managing-cf/audit-events.html .

Availability Zones in the Cloud Foundry Environment

The Cloud Foundry environment follows the recommendations of our partner IaaS providers by leveraging the availability zones
(AZ) concept.

About Availability Zones

Availability zones (AZ) are single failure domains within a single geographical region and are separate physical locations with
independent power, network, and cooling. Multiple AZs exist in one region and are connected with each other through a low-
latency network.

2-AZ and 3-AZ Deployments

To achieve better fault-tolerance, our partners recommend deploying services across multiple AZs, which improves the availability
of a service if there are issues with the region infrastructure of one AZ.

High Availability at Platform and Application Level

The SAP BTP Cloud Foundry environment follows these recommendations to support high availability at the platform and
application level:

High availability of the platform components:

The building blocks of Cloud Foundry and the virtual machines on which the Cloud Foundry application instances
are scheduled run in a high availability setup. Their instances are distributed across different AZs.

The technology that manages the deployment of the Cloud Foundry environment monitors the health of the
platform. If there are infrastructure failures, it re-creates the faulty components.

High availability on the application level:

We recommend running multiple application instances to increase availability. For more information, see Run
Multiple Instances to Increase Availability . On SAP BTP, there are three ways to increase application instances:

This is custom documentation. For more information, please visit the SAP Help Portal 33
 10/15/24, 3:53 PM
Scaling your application using the application manifest. The manifest.yml allows you to make and save
configurations for your application. To scale, you can configure the instance count in the manifest and push
the application again with the new configuration. See App Manifest Attribute Reference . To avoid
downtimes when updating your application configuration, you can also consider using rolling application
deployments. See Rolling App Deployments .

Scaling your application using the cf scale command in the Cloud Foundry command line interface (CF
CLI). See Scaling an App Using cf scale .

Scaling your application using the SAP BTP cockpit. See Add or Remove Application Instances.

The Cloud Foundry container scheduler takes care of distributing the different instances of one application on
virtual machines in different AZs. For more information, see How Diego Balances App Processes .

Cloud Foundry is constantly monitoring the health state of application instances and restarts instances that are
considered unhealthy. See Using App Health Checks .

When the number of desired instances doesn't match the number of actually running instances, Cloud Foundry
reschedules the missing instances, for example, when the virtual machines that an application instance was initially
scheduled on become unresponsive.

For more information on high availability configuration, see High Availability in Cloud Foundry .

For more information on application stability and resilience, see .

Additional Information About Cloud Foundry

Links to additional information about Cloud Foundry that is useful to know but not necessarily directly connected to the SAP BTP,
Cloud Foundry environment.

Content Location

BOSH http://bosh.cloudfoundry.org

BOSH documentation http://bosh.io/docs

Buildpacks http://docs.cloudfoundry.org/buildpacks

Components of Cloud Foundry http://docs.cloudfoundry.org/concepts/architecture/

Cloud Foundry Concepts http://docs.cloudfoundry.org/concepts/

Deployment of Cloud Foundry http://docs.cloudfoundry.org/deploying

Developer Guide for Cloud Foundry http://docs.cloudfoundry.org/devguide

Diego Application Process Balancing https://docs.cloudfoundry.org/concepts/diego/diego-auction.html

Glossary for Cloud Foundry http://docs.cloudfoundry.org/concepts/glossary.html

Overview of Cloud Foundry http://docs.cloudfoundry.org/concepts/overview.html

Sample applications for Cloud Foundry https://github.com/cloudfoundry-samples

Security settings for Cloud Foundry http://docs.cloudfoundry.org/concepts/security.html

Cloud Foundry Services http://docs.cloudfoundry.org/services

This is custom documentation. For more information, please visit the SAP Help Portal 34
 10/15/24, 3:53 PM

Content Location

http://docs.cloudfoundry.org/devguide/services/user-
provided.html

Considerations for designing and running an application in the http://docs.cloudfoundry.org/devguide/deploy-apps/prepare-to-

cloud deploy.html

Installing the Cloud Foundry command line interface http://docs.cloudfoundry.org/devguide/installcf/install-go-cli.html

Blog about Cloud Foundry http://blog.cloudfoundry.org/

Commercial Information for Cloud Foundry Runtime

This page explains the relationship between the service plans in the SAP Discovery Center and those in the SAP BTP cockpit, and
provides information to help you understand how the service is billed.

Service

Overview

The diagram below shows how the service plans listed in the SAP Discovery Center correspond to the plans you choose in the
SAP BTP cockpit , depending on the commercial model of your enterprise global account. For more information about the
commercial models offered by SAP, see Commercial Models.

Diagram captions: Service plans and environment plans in SAP BTP cockpit [Show/Hide]

Service Plan (SAP BTP Cockpit)

The plan that the global account administrator can assign to a subaccount or a directory on the Entitlements page by choosing
Edit Add Service Plans .

 Tip
Open image in new tab for the full-screen version.

This is custom documentation. For more information, please visit the SAP Help Portal 35
 10/15/24, 3:53 PM

Screenshot: Assigning a service plan to a subaccount in SAP BTP cockpit [Show/Hide]

For more information about the procedure, see Configure Entitlements and Quotas for Subaccounts or Configure Entitlements and
Quotas for Directories.

Environment Plan (SAP BTP Cockpit)

The plan that the subaccount administrator can select on the Overview page of a subaccount when choosing Enable Cloud
Foundry.

 Tip
Open image in new tab for the full-screen version.

Screenshot: Selecting an environment plan for the subaccount in SAP BTP cockpit [Show/Hide]

For more information about the procedure, see Create Orgs.

 Note
An environment plan is a service plan associated with an environment. For more information about services and service plans,
see Entitlements and Quotas.

Service Plans

The tables below provide details about the plans for SAP BTP, Cloud Foundry runtime. They can give you more context for
understanding the diagram in the Overview section.

This is custom documentation. For more information, please visit the SAP Help Portal 36
 10/15/24, 3:53 PM

Table 1: Plans for Consumption-Based Commercial Model [Show/Hide]

Environment Plan (SAP

Service Plan (SAP Service (SAP BTP Service Plan (SAP BTP
BTP Cockpit: Enable Explanation
Discovery Center) Cockpit: Entitlements) Cockpit: Entitlements)
Cloud Foundry)

Standard - - standard This is a paid plan for

productive use. In the
consumption-based
commercial model, you are
charged based on how much
runtime memory has been
consumed by your
applications running in the
Cloud Foundry environment.
For details, see Service
Specifics.

 Caution
With this plan, you get a
technical quota of 200 GB
of runtime memory per
Cloud Foundry org. This
doesn't mean that you can
use the runtime memory
for free. The technical
quota represents a limit on
how much runtime
memory all the spaces in
the org can use at any
given time. To increase this
limit, create a case on the
SAP Support Portal
using the component BC-
NEO-CIS.

The plan is available for all

subaccounts by default and
can be enabled by a
subaccount administrator.

Free Cloud Foundry free (Environment) free This is a free tier plan that
Environment allows you to try out and
(cloudfoundry) evaluate the service. For more
information, see Using Free
Service Plans.

With this plan, you get a free

quota of runtime memory for
your Cloud Foundry org. The
amount of such free quotas
per global enterprise account
is limited.

The plan must be assigned to

the subaccount by a global
account administrator (or a
directory administrator),

This is custom documentation. For more information, please visit the SAP Help Portal 37
 10/15/24, 3:53 PM

Environment Plan (SAP

Service Plan (SAP Service (SAP BTP Service Plan (SAP BTP
BTP Cockpit: Enable Explanation
Discovery Center) Cockpit: Entitlements) Cockpit: Entitlements)
Cloud Foundry)

before it can be enabled by a

subaccount administrator.

 Note
Only community support is
available for free tier
service plans and these are
not subject to SLAs. Use of
free tier service plans is
subject to additional terms
and conditions as provided
in the Business Technology
Platform Supplemental
Terms and Conditions .

See SAP Build Code Cloud Foundry build-code build-code This plan is only for using the
Environment SAP BTP, Cloud Foundry
(cloudfoundry) runtime as part of SAP Build
Code. For more information,
see What Is SAP Build Code.

 Note
The plan is not depicted on
the diagram in the
Overview section.

Table 2: Plans for Subscription-Based Commercial Model [Show/Hide]

Service Plan (SAP Environment Plan (SAP

Service Plan (SAP Service (SAP BTP Cockpit:
BTP Cockpit: BTP Cockpit: Enable Explanation
Discovery Center) Entitlements)
Entitlements) Cloud Foundry)

Standard Cloud Foundry Runtime MEMORY standard This is a paid plan for
(APPLICATION_RUNTIME) productive use. In the
subscription-based
commercial model, you pay
for runtime memory quota in
advance.

The runtime memory quota

purchased with your
subscription must be entitled
to subaccounts through the
service plan MEMORY. This
service plan is associated with
the service Cloud Foundry
Runtime
(APPLICATION_RUNTIME),
which is specific to the
subscription-based
commercial model.

The plan standard is available

for all subaccounts by default

This is custom documentation. For more information, please visit the SAP Help Portal 38
 10/15/24, 3:53 PM

Service Plan (SAP Environment Plan (SAP

Service Plan (SAP Service (SAP BTP Cockpit:
BTP Cockpit: BTP Cockpit: Enable Explanation
Discovery Center) Entitlements)
Entitlements) Cloud Foundry)

and can be enabled by a

subaccount administrator.
The runtime memory quota
can be entitled to the
subaccount only by a global
account administrator (or a
directory administrator).
These steps are independent,
but both of them are required
to run applications in the
Cloud Foundry environment.

See SAP Build Cloud Foundry Environment build-code build-code This plan is only for using the
Code (cloudfoundry) SAP BTP, Cloud Foundry
runtime as part of SAP Build
Code. For more information,
see What Is SAP Build Code.

 Note
The plan is not depicted on
the diagram in the
Overview section.

Metrics

The table below provides details about the metrics for SAP BTP, Cloud Foundry runtime. It includes the names of services, with
which the metrics are associated on the pages Usage (accessed from the global account level) and Usage Analytics (accessed
from the subaccount level) in the SAP BTP cockpit.

Service Metric Definition Additional Information

Cloud Foundry GB Memory Temporary memory bank where For billing purposes, the metric GB Memory is
Runtime computers store data that needs to calculated as the total hourly usage of Cloud
be retrieved and processed quickly. Foundry runtime memory across all spaces in
the global account over a calendar month,
The memory represents the size of
divided by 730 hours and rounded up to the
the data that can be processed and
next full GB. For an example of such calculation,
CPU represents the speed at which
see Consumption Monitoring.
the data can be retrieved.

 Note
In the Cloud Foundry environment,
applications get a guaranteed CPU share of
¼ core per GB of runtime memory quota
reserved for an application instance. For
more information, see SAP BTP-Specific
Configurations.

SAP Build Code CF Runtime The metric CF Runtime is intended only for
monitoring the usage of SAP BTP, Cloud
Foundry runtime when it's used as part of SAP
Build Code. For more information, see What Is
SAP Build Code.

This is custom documentation. For more information, please visit the SAP Help Portal 39
 10/15/24, 3:53 PM

Service Metric Definition Additional Information

 Note
The metric is not depicted on the diagram in
Service.

Service Specifics

In the context of SAP BTP, Cloud Foundry runtime, the terms consumption (or consume) and usage (or use) refer to the runtime
memory quota reserved by the platform for each application instance. This quota serves as the basis for calculating the billable
consumption, as explained in Consumption Monitoring.

 Caution
From a billing standpoint, it doesn't matter how much of the reserved runtime memory quota is utilized when the application is
running. Billable consumption is calculated based on the full amount of runtime memory reserved, regardless of how much
runtime memory actually gets utilized.

 Note
If an application is stopped, it doesn't reserve any runtime memory and, therefore, doesn't contribute to runtime memory
consumption.

There are two application settings that define how much runtime memory an application uses at any given time:

Runtime memory quota reserved for each application instance (default: 1024 MB)

Number of running application instances (default: 1)

You can specify custom values for these settings when deploying an application in the Cloud Foundry environment. You can also
change them for an application that has already been deployed without having to redeploy it.

How to set runtime memory quota and number of instances when deploying applications

Option 1: Create a manifest YAML file and specify the following application attributes:

memory : runtime memory quota per application instance

instances : number of application instances

For more information about the manifest formatting, see https://docs.cloudfoundry.org/devguide/deploy-apps/manifest-

attributes.html .

You can then deploy your application with the manifest in one of two ways:

Using the SAP BTP cockpit: Deploy an Application

Using the Cloud Foundry CLI: https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html

Option 2: In the SAP BTP cockpit, choose Deploy Application, deselect Use Manifest and specify the following:

Instance Memory (MB): runtime memory quota per application instance

Number of Instances: number of application instances

For more information about the procedure, see Deploy an Application.

Option 3: In the Cloud Foundry CLI, use the command cf push with the following flags:

This is custom documentation. For more information, please visit the SAP Help Portal 40
 10/15/24, 3:53 PM
-m: runtime memory quota per application instance

-i: number of application instances

For more information about the procedure, see https://docs.cloudfoundry.org/devguide/deploy-apps/deploy-

app.html#custom-push .

How to change runtime memory quota and number of instances for already deployed applications

Option 1: In the SAP BTP cockpit, on the Overview page of the application you can:

Change the runtime memory quota per application instance under Change Instance Details Instance Memory
(MB)

Change the number of application instances as described in Add or Remove Application Instances

Option 2: In the Cloud Foundry CLI, you can use the command cf scale with the following flags:

-m: change the runtime memory quota per application instance

-i: change the number of application instances

For more information about the procedure, see https://docs.cloudfoundry.org/devguide/deploy-apps/cf-scale.html .

You can use the Application Autoscaler to automatically increase or decrease the number of application instances based on the
policies you have defined. For more information, see What Is Application Autoscaler.

 Tip
For tips on how to optimize the consumption of runtime memory, see the blog post Optimise your SAP BTP, Cloud Foundry
runtime costs . Note that while the general principles outlined in the blog post still apply, some of the UI texts and parameter
names may have changed.

Supplemental Terms and Conditions

For more information, see the section SAP BTP, Cloud Foundry Runtime in the SAP Business Technology Platform Service
Description Guide .

Glossary

Commercial Information Glossary

ABAP Environment
Within the Cloud Foundry environment, you can create a new space for ABAP development. This is what we refer to as the ABAP
environment. It allows you to create extensions for ABAP-based products, such as SAP S/4HANA Cloud, and develop new cloud
applications. You can transform existing ABAP-based custom code or extensions to the cloud.

The ABAP environment is based on the latest ABAP platform cloud release that is also used for SAP S/4HANA Cloud. It leverages
the innovations provided by SAP HANA. The software stack contains standard technology components that are familiar from the
standalone Application Server ABAP. The ABAP environment supports the ABAP RESTful Application Programming Model
including SAP Fiori and Core Data Services (CDS). SAP services and APIs are offered according to the new approach of released
objects. The ABAP environment can be integrated with other SAP BTP services, such as SAP Destination service, SAP Build Work
Zone, standard edition, SAP Workflow Management, and SAP Interactive Forms by Adobe.

This is custom documentation. For more information, please visit the SAP Help Portal 41
 10/15/24, 3:53 PM
Each ABAP system in the ABAP environment utilizes a dedicated SAP HANA database, which is provided by the SAP HANA Cloud
service and managed by the ABAP environment. The database is linked 1:1 to the ABAP system.

For information about regional availability, see Regions and API Endpoints for the ABAP Environment.

Related Information
Getting Started in the ABAP Environment
Development in the ABAP Environment
Administration and Operations in the ABAP Environment
Using Free Service Plans
Discovery Center
SAP Community
SAP Road Map Explorer
Learning Journey
Tutorials

ABAP Development Tools for Eclipse

ABAP development tools for Eclipse is SAP’s state-of-the-art integrated development environment (IDE) for ABAP development on
the open Eclipse platform.

Features
ABAP development tools for Eclipse enables you to perform ABAP-based development tasks, when you want to build, to extend,
and to run ABAP applications based on SAP products, such as SAP S/4HANA and SAP S/4HANA Cloud, private edition for classic
ABAP development as well as SAP BTP, ABAP environment and SAP S/4HANA Cloud for Cloud development.

ABAP development tools for Eclipse supports ABAP developers with the following possibilities:

Highly flexible, customizable Eclipse UI for ABAP development tools

High-performance, failover-safe online development in multiple ABAP systems simultaneously

Display and edit functionality for multiple ABAP objects in parallel

Advanced and efficient source code editing including refactoring support

Optimum support of task-oriented and test-driven development

Robust and reliable quality assurance and supportability tools.

Built-in extensibility of the IDE using the established Eclipse plug-in technology

In particular, ABAP development tools for Eclipse is a modern development toolset where ABAP developers can use, for example
the following features:

Syntax check

Code completion

Syntax highlighting

Pretty printing

This is custom documentation. For more information, please visit the SAP Help Portal 42
 10/15/24, 3:53 PM
Navigation

Search

Quick fixes

and many more

Tools User Guides

The ABAP Development Tools: User Guide describes the functionality and usage of the possibilities. It focuses on use cases for
creating, editing, testing, debugging, and profiling development objects.

The ABAP CDS Development Tools: User Guide describes the functionality and usage of tools for ABAP Core Data Services (CDS)
in the ABAP environment. It focuses on use cases for creating, editing, testing, and analyzing ABAP CDS entities.

Release Notes

ABAP development tools for Eclipse is released to customers in combination with the SAP BTP ABAP environment shipments.
Documentation in the context of ABAP Platform will be shipped in accordance with the relevant SAP product shipments.

The release notes are a general overview of the most significant changes relating to features of ABAP development tools for
Eclipse in the context of ABAP development and the ABAP programming models.

For more information, see Release Notes of ABAP Development Tools for Eclipse

FAQs

If you are an SE80 expert and new to ABAP development tools for Eclipse, the frequently asked questions (FAQs) enable you to
skim the features you want to perform in ADT.

For more information, see FAQs for SE80 Experts Using ADT

Installation
To install ABAP development tools for Eclipse, follow the Installation Guide. Alternatively, you may get ABAP development tools for
Eclipse from the SAP Development Tools page under the terms of the SAP DEVELOPER LICENSE AGREEMENT.

Support
The use of ABAP development tools for Eclipse is subject to the terms and conditions of your license agreement with SAP which is
directly related to the SAP shipment channel from whichABAP development tools for Eclipse was initially downloaded and
installed.

Commercial Information for SAP BTP, ABAP environment

This page explains the relationship between the service plans of the SAP Discovery Center and the service plans of the SAP BTP
cockpit and provides information to help you understand how the service is billed.

Service

This is custom documentation. For more information, please visit the SAP Help Portal 43
 10/15/24, 3:53 PM
Overview

Discovery Center: SAP BTP ABAP environment

 Note
For more information about consumption-based models, please check What is the Consumption-Based Commercial Model?

SAP BTP Cockpit: Service Plans

Name Service Plan Description

free Free Allows you to create small proof-of-concept development

projects. Also can be used for the piloting of a remote ABAP test
cockpit scenario against on-premise systems in the Custom Code
Migration app. The instance will be stopped each night
automatically and needs to be started again via the Landscape
Portal. Only community support is available for free tier service
plans and these are not subject to SLAs.

standard Standard Allows you to create projects for development, test, and
productive ABAP systems. The minimum system size is 2 HANA
Compute Units and 1 ABAP Compute Unit.

It is mandatory to assign a combination of three entitlement

service plans: ABAP Compute Unit, HANA Compute Unit, and
either the Free, Standard, or SaaS OEM plan.

abap_compute_unit Standard Allows you to configure runtime memory, which refers to volatile
memory used during the execution of applications. This memory
provides fast read and write access but loses all data when the
system is restarted or shut down. The metric measures the
amount of runtime memory used in 16 GB blocks on an hourly
basis.

This is custom documentation. For more information, please visit the SAP Help Portal 44
 10/15/24, 3:53 PM

Name Service Plan Description

It is mandatory to assign a combination of three entitlement

service plans: ABAP Compute Unit, HANA Compute Unit, and
either the Free, Standard, or SaaS OEM plan.

hana_compute_unit Standard Allows you to configure persistent memory, which refers to

storage that retains data even after the system is restarted or
shut down. The metric measures the amount of persistent
storage used in 16 GB blocks on an hourly basis.

It is mandatory to assign a combination of three entitlement

service plans: ABAP Compute Unit, HANA Compute Unit, and
either the Free, Standard, or SaaS OEM plan.

saas_oem SaaS OEM Allows you to create projects for ABAP systems to run
multitenancy SaaS applications. The minimum system size is 2
HANA Compute Units and 1 ABAP Compute Unit.

It is mandatory to assign a combination of three entitlement

service plans: ABAP Compute Unit, HANA Compute Unit, and
either the Free, Standard, or SaaS OEM plan.

16_abap_64_db (Deprecated) 16 GB Runtime and 64 GB This ABAP runtime service plan provides a 16 GB ABAP runtime
Persistence (Deprecated) with a 64 GB database. No additional sizing is possible.

This service plan is deprecated. Please change the service plan to

“standard”.

Metrics

Metric Definition

Memory Temporary memory bank where computers store data that needs to be retrieve and
processed quickly.

The memory represents the size of the data that can be processed , and CPU represents the
speed at which the data can be retrieved.

Supplemental Terms and Conditions

For more information, see the SAP Business Technology Platform Service Description Guide .

Kyma Environment
SAP BTP, Kyma runtime provides a fully managed cloud-native Kubernetes application runtime based on the open-source project
"Kyma". Based on modular building blocks, Kyma runtime includes all the necessary capabilities to simplify the development and
to run enterprise-grade cloud-native applications.

Kyma as a Managed Service

Kyma environment permits a native consumption of the Multi-Cloud Foundation Services (What Is the Multi-Cloud Foundation?)
and smooth consumption of SAP and non-SAP applications. It also supports out-of-the-box CAP, SAP Cloud SDK, application
router, and HTML5 deployer.

This is custom documentation. For more information, please visit the SAP Help Portal 45
 10/15/24, 3:53 PM
Kyma implements a dedicated application runtime to deploy highly scalable, robust, and secure containerized microservices.

 Note
Kyma as a managed service automatically checks all Kyma-managed resources. Any unexpected modifications are discarded,
and the resource is reverted to the original state.

Every Kyma environment consists of:

A Kubernetes cluster based on project "Gardener" on a cloud provider and region (data center) of your choice. To find out
the available regions and providers, see Regions for the Kyma Environment.

A set of Kyma modules picked by a user in the release channel of their choice installed on the provisioned cluster.

Integration

Every Kyma environment runs on a single Kubernetes cluster created for a specific subaccount. The configuration of the Kyma
environment enables you to connect it to a multitude of SAP systems. This way, you can build various formations that aggregate
the SAP systems and environment according to your business use cases.

SAP systems connected to a Kyma environment expose APIs and events. To extend the existing logic of these SAP services, you
can build serverless applications called “Functions”, and trigger them to react to particular events or calls to your application's API.
You can also use the Kyma environment to deploy microservices or even build full-stack applications.

Related Information
Getting Started in the Kyma Environment
Development in the Kyma Environment
Administration and Operations in the Kyma Environment
Security in the Kyma Environment

This is custom documentation. For more information, please visit the SAP Help Portal 46
 10/15/24, 3:53 PM
Discovery Center

Kyma's Modular Approach

With Kyma's modular approach, you can install only the modules you need, instead of a predefined set of components.

Kyma Module or Component?

Classic Kyma runtime offered a fixed set of mandatory interdependent components whose development rhythm was synchronized
and determined by the release schedule. One by one, all Kyma components have been converted to modules that work
independently from each other.

The modular approach boosts Kyma's extensibility and scalability and makes it more cost-effective. With fully modularized Kyma,
you can choose from many of its modules to facilitate your business needs best. You can add or delete modules on demand and
configure them, thus determining the costs generated by the infrastructure that your modules use.

You can decide which modules are needed for your workload, although some features may still require the presence of other
modules or related capabilities. For example, the API Gateway module depends on Istio capabilities, but it doesn't require the Istio
module from Kyma. Instead, the API Gateway module needs Istio custom resources, such as Gateway and VirtualService, to be
present in the cluster. If you want to use your own Istio installation, the API Gateway module will use it as soon as the required
resources are available.

Learn more about the available Kyma modules: Kyma Modules.

Learn how to add a module under Add and Delete a Kyma Module.

Kyma Release Channels

Sets of Kyma modules are deployed in two release channels:

Regular channel is the default release channel.

Fast channel provides more frequent releases. It offers early previews of all new features and changes before they are
promoted to the regular channel. It also allows you to test and provide feedback on the new features sooner.

According to the Kyma modules` release cycle, we first release a new module's major or minor version in the fast channel. After
approximately two weeks, we promote the release to the regular channel.

 Note
In case of important functionality fixes or critical vulnerabilities identified by our security organization, the timeline doesn't
apply, as we provide hotfixes between regular releases.

You can use one or both release channels in your Kyma cluster, but you can define only one release channel per module. For
example, you can mix different modules from the regular and fast channels in your development cluster, but you cannot deploy the
same module in the regular and fast versions in one cluster.

 Note
You can upgrade module versions, but you cannot downgrade them. To test the upstream versions, you can switch a module or
an entire cluster from the regular channel to the fast one. To return to the regular channel, you must wait until the version you
are using in the fast channel is promoted to the regular channel. Once the versions in both the fast and regular channels are the
same, you can switch back to regular. Alternatively, you can delete and add your module from the regular channel.

This is custom documentation. For more information, please visit the SAP Help Portal 47
 10/15/24, 3:53 PM
To find out which module version is running in your cluster, go to Kyma dashboard .

Release Notes
A release of a new module’s version is announced with a release note in What’s New for SAP Business Technology Platform for
both, the fast and regular channels:

On the day of the release in the fast channel, a release note is published with the Preview label.

After approximately two weeks, the module version becomes available in the regular channel and the Preview label is
removed.

Related Information
Kyma Functionalities

Kyma Modules
With Kyma's modular approach, you can install just the modules you need, instead of a predefined set of components.

You can choose to add any modules as required. To learn how, see Add and Delete a Kyma Module. To find out which module
version is running in your cluster, go to Kyma dashboard .

 Tip
A release of a new module’s version is announced with a release note in What’s New for SAP Business Technology Platform for
both, the fast and regular channels:

On the day of the release in the fast channel, a release note is published with the Preview label.

When the module version becomes available in the regular channel (after approximately two weeks), the Preview label is
removed.

Default Kyma Modules

When you create Kyma runtime in SAP BTP cockpit, it is provisioned with the default modules added. The default modules are not
mandatory. If you don't need them, you can delete them in Kyma dashboard . See Add and Delete a Kyma Module.

Default Kyma Modules

Module Purpose Documentation

Technical name

API Gateway API Gateway provides functionalities that allow you to kyma-project.io: API Gateway module
expose and secure APIs.
api-gateway

Istio Istio is a service mesh with Kyma-specific configuration. kyma-project.io: Istio module

istio

SAP BTP Operator Within the SAP BTP Operator module, BTP Manager installs Using SAP BTP Services in the Kyma
the SAP BTP service operator that allows you to consume Environment
btp-operator

This is custom documentation. For more information, please visit the SAP Help Portal 48
 10/15/24, 3:53 PM

Module Purpose Documentation

Technical name

SAP BTP services from your Kubernetes cluster using kyma-project.io: SAP BTP Operator
Kubernetes-native tools. module

GitHub: BTP Manager releases

GitHub: SAP BTP service operator

releases

Optional Kyma Modules

When you create Kyma runtime in SAP BTP cockpit, the following modules are not added by default, but you can choose to add
and delete them anytime in Kyma dashboard . See Add and Delete a Kyma Module.

Optional Kyma Modules

Module Purpose Documentation

Technical name

Application Connector Application Connector allows you to connect with external kyma-project.io: What is Application
solutions. No matter if you want to integrate an on-premise Connectivity in Kyma?
application-connector
or a cloud system, the integration process doesn't change,
GitHub repository: Application
which allows you to avoid any configuration or network-
Connector Manager
related problems.

Keda The Keda module comes with Keda Manager, an extension kyma-project.io: Keda module
to Kyma that allows you to install KEDA (Kubernetes
keda
Event Driven Autoscaler).

Serverless With the Serverless module, you can define simple code Deploy Workloads in the Kyma
snippets (Functions) with minimal implementation effort. Environment to Extend SAP Systems
serverless
kyma-project.io: What is Serverless in
Kyma?

kyma-project.io: Serverless
Configuration

GitHub repository: Serverless

Telemetry The Telemetry module collects application logs and Kyma Telemetry Module
distributed traces for your application, and dispatches them
telemetry What's New for Telemetry
to your preferred backends.

GitHub repository: Telemetry

NATS NATS deploys a NATS cluster within the Kyma cluster. You kyma-project.io: NATS module
can use it as a backend for Kyma Eventing.
nats GitHub repository: NATS

Eventing Eventing provides functionality to publish and subscribe to Configure SAP Event Mesh for Kyma
CloudEvents. Eventing
eventing
At the moment, the SAP Event Mesh default plan and NATS kyma-project.io: Eventing module
are supported. If you choose NATS, add the NATS module.
GitHub repository: Eventing

Other SAP Modules

This is custom documentation. For more information, please visit the SAP Help Portal 49
 10/15/24, 3:53 PM
These modules are developed and maintained by SAP teams outside of Kyma. To get help or request a feature, contact the module
provider directly.

Other SAP Modules

Module Purpose Documentation

Technical name

Transparent Proxy Use the transparent proxy for Kubernetes to connect Transparent Proxy in the Kyma
workloads in a Kubernetes cluster to Internet and on- Environment
transparent-proxy
premise applications.

Connectivity Proxy Use the connectivity proxy for Kubernetes to connect On-Premise Connectivity in the Kyma
workloads in a Kubernetes cluster to on-premise systems, Environment
connectivity-proxy
exposed via the Cloud Connector.

Kyma Functionalities
SAP BTP, Kyma runtime and open source project "Kyma" offer slightly different functionalities and install a different set of
components.

For all functionalities that the Kyma environment offers, see the official project "Kyma" documentation .

Functionality Comparison

Functionality open source project "Kyma" SAP BTP, Kyma runtime

Service Level Agreements  

Managed Kubernetes  

Managed Kyma  

Kyma CLI  limited (SAP BTP, Kyma runtime supports

commands for serverless Functions, not the
commands related to installation.)

Centrally hosted Kyma dashboard  

System landscape management in SAP BTP  

cockpit

In-cluster system landscape management  

(Application Connector)

Kyma Runtime: Basic Concepts

This table explains basic concepts relating to the Kyma environment. It aims to give you an understanding of the Kyma
environment before you actually start using it to build extensions for your SAP solutions.

 Note
For an overview of the basic Kubernetes concepts that the Kyma environment heavily relies on, see the official Kubernetes
documentation .

This is custom documentation. For more information, please visit the SAP Help Portal 50
 10/15/24, 3:53 PM

Concept Description

Kyma cluster A Kubernetes cluster provisioned with the latest version of the open-source project "Kyma". You can enable such a
cluster on a given subaccount through the SAP BTP cockpit. After creating a Kyma environment instance on your
subaccount, the cluster is provisioned automatically through Gardener on your chosen cloud service provider. To access
the cluster, you must have appropriate roles assigned to your subaccount.

Kyma module An extension to the Kyma environment that can be added, deleted, or re-configured at runtime.

Role Access to every cluster is managed by the roles assigned. Roles give the assigned users a different level of permissions
suitable for different purposes. For more information, read Assign Roles in the Kyma Environment.

Namespace Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. This way, several
users can share a cluster but have access only to resources within the namespace they have permissions for. This allows
for increasing the security and organization of your cluster by dividing it into smaller units. Access to namespaces in the
Kyma environment depends on your Kubernetes RBAC permissions.

Service A service operator is a piece of software that provides a set of all necessary resources (such as
operator CustomResourceDefinitions and controllers) needed to provision third-party services in your Kubernetes cluster.

Binding The connection you create between a service instance and an SAP solution so that they can communicate with each
other. You can also bind a service instance to any workload running in the Kyma environment, such as a Function or a
microservice.

Credentials / Sensitive data necessary for an SAP solution to call the service, connect to it, and authenticate it. Depending on whether
Secrets you use Kyma dashboard or kubectl to create the binding between a service instance and an SAP solution, the
Kubernetes Secret object that contains these credentials is either created automatically or you need to create it
manually.

Function A simple code snippet that you can run without provisioning or managing servers. It implements the exact business logic
you define. A Function is based on the Function custom resource and can be written in either Node.js or Python. A
Function can perform a business logic of its own. You can also bind it to an instance of a service and configure it to be
triggered whenever it receives a particular event type from the service or a call is made to the service's API. Functions
are executed only if they are triggered by an event or an API call.

Microservice An architectural variant for extensions or applications, where you separate the tasks into smaller pieces that interact
with each other as loosely coupled, independently deployable units of code. A failing microservice should not cause your
whole application to fail. Microservices are packed in a container that is always running; it's idling if there is no load. The
microservice should always be reachable even when the Pods move around. Microservices typically communicate
through APIs.

Commercial Information for Kyma Runtime

This page explains the relationship between the service plans of the SAP Discovery Center and the service plans of the SAP BTP
cockpit and provides information to help you understand how the service is billed.

Service

Overview

This is custom documentation. For more information, please visit the SAP Help Portal 51
 10/15/24, 3:53 PM

SAP Discovery Center: Kyma Runtime

 Note
For more information, see What is the Consumption-Based Commercial Model?

SAP BTP Cockpit: Service Plans

Name Service Plan (Discovery Description

Center)

free Free Subscribe to the 30-day free plan provided on Amazon Web
Services. This plan uses Kyma on a limited size cluster (4 CPU -
16 GB RAM). The upgrade to the paid plan is not yet supported.
Only best-effort support is available for free tier service plans and
these are not subject to SLAs. The services you plan to use must
be available in the same region as the subaccount for the Kyma
runtime.

aws Standard Select Amazon Web Services as the cloud provider where your
Kyma cluster is deployed.

gcp Standard Select Google Cloud as the cloud provider where your Kyma
cluster is deployed.

azure Standard Select Microsoft Azure as the cloud provider where your Kyma
cluster is deployed.

Metrics
The usage metric for the Cloud Service is a Capacity Unit (CU) per month.

This is custom documentation. For more information, please visit the SAP Help Portal 52
 10/15/24, 3:53 PM

Metric Definition

Capacity Unit Number of units consumed by the usage of the services as outlined in the solution-specific
product supplement.

For SAP BTP, Kyma runtime, there are two capacity units: one to measure the workload, the
second to measure the storage.

Backward Calculation

Formula

The relationship between consumed workload/storage and the respective CU is straightforward.

However, cost per monthly bill may vary because it depends on the size of the nodes that were used. There is no fixed formula
because of Kyma's flexible scaling.

Underlying Metrics

In the following tables, “CU” stands for “Capacity Unit”.

For CPU

Amount of CPU/CPU Nodes Number of CU per Hour

2 0.48055555555555557 x 0.75

4 0.48055555555555557

8 0.48055555555555557 x 2

16 0.48055555555555557 x 4

32 0.48055555555555557 x 8

... ...

For Storage

Amount of Storage Number of CU per Hour

1GB 0.00056423611

32GB 0.01805555552 (0.00056423611 x 32)

Examples

Your bill for Nodes shows 1800 capacity units charged for 4vCPU Nodes in a month.

This means that you were running roughly 1800 / 0.4806 = 3745.32 hours worth of 4vCPU nodes. Given that a month has
720 hours, this means you were running 3745.32/720 = 5.2 Nodes cluster for a full month.

Due to Kyma’s automatic scaling, 5.2 does not mean actual size. It means that during some hours in the month, the cluster
size was 4 nodes. At other times, there was more load, so the cluster autoscaled to 5 or 6 nodes, based on your
configurations. So your average cluster size for the full month was 5.2 Nodes.

Your bill for storage shows 200 capacity units charged for storage (32GB block) for the month.

This is custom documentation. For more information, please visit the SAP Help Portal 53
 10/15/24, 3:53 PM
This means that you used 200 / 0.0181 = 11049.72 hours of 32GB storage blocks. Given that a month has 720 hours, this
means that you have used 11049.72/720 = 15,34 blocks of 32GB over the month. So, you used 15.34 * 32 = 491GB of
storage continuously during the month.

This implies that as you started using Kyma, you deployed more applications that used storage of various sizes, such as
4GB or 8GB.

Note that storage is provided in blocks of 32GB, so if you used 33 GB, you would be charged for 2 * 32GB, that is 64 GB.

Calculator
Find the Kyma price calculator on https://kyma-project.github.io/price-calculator/ and use it to estimate the costs for your
SAP BTP, Kyma runtime.

1. Choose the size of virtual machine (VM).

2. Choose the minimum of VMs you need.

3. Estimate the hours per month you expect to run them.

4. Optionally, add more Nodes and more storage to the calculation.

Note that the result is an estimate, and the monthly bill may vary depending on the actual hours and size of the Kyma cluster
(workload and storage) that was running in a month.

Supplemental Terms And Conditions

For more information, see SAP Business Technology Platform Service Description Guide , section “SAP BTP, KYMA RUNTIME”.

Glossary

Commercial Information Glossary

Service Specifics

As soon as you instantiate a Kyma cluster, the basic costs for the empty cluster incurs.

Cost may then vary depending on the actual workloads and storage you consume per month.

Neo Environment
The Neo environment lets you develop HTML5, Java, and SAP HANA extended application services (SAP HANA XS) applications.
You can also use the UI Development Toolkit for HTML5 (SAPUI5) to develop rich user interfaces for modern web-based business
applications.

See also:

What Is SAP BTP, Neo Environment

Development, Neo Environment

Extensions, Neo Environment

Administration and Operations, Neo Environment

This is custom documentation. For more information, please visit the SAP Help Portal 54
 10/15/24, 3:53 PM
Security, Neo Environment

Getting Support, Neo Environment

Migration from the Neo to the Multi-Cloud Foundation

To learn more about why and how to migrate your scenarios on SAP BTP, see Migrating from the SAP BTP Neo Environment to the
Multi-Cloud Foundation.

Trial Accounts and Free Tier

Explore the different options for trying out SAP BTP.

Trial Account or Free Tier Offering: When to Use Which?

Before setting up your account, you need to decide which free offering for SAP BTP is suitable for your needs:

Pay-As-You-Go or CPEA accounts with free tier service plans are open to customers, partners, and let you try out SAP
BTP in a per service defined time span for free. These account types enable you to test your scenarios and generally offer
the option to upgrade to paid service plans. These accounts also allow you to store data long-term and move projects to
production. You also get access to our community, including free technical resources such as tutorials and blog posts. For
more information, see Enterprise Accounts and Using Free Service Plans.

You can self-register for an enterprise account with free tier service plans. For more information, see Get an Account on
SAP BTP to Try Out Free Tier Service Plans .

 Note
Only community support is available for free tier service plans and these are not subject to SLAs.

 Note
The option to upgrade from free tier service plans to paid service plans is not yet available for all services and runtimes,
such as Kyma. See Using Free Service Plans to read more about upgrading from free tier service plans to paid service
plans.

A trial account lets you try out SAP BTP for free for 90 days. The services provided for the trial account allow restricted use
of the platform resources and services. Access is open to everyone. Trial accounts are intended for personal exploration,
your own non-productive testing, and evaluation of the services in accordance with SAP BTP trial terms and conditions .
A SAP BTP trial account must not be used for production use or team development. You are not permitted to use the trial
account in any productive or commercial manner.

You can self-register for a trial account. For more information on how to do that, see Get a Free Account on SAP BTP Trial

Free Tier and Always Free Tags in the SAP Discovery Center
In the SAP Discovery Center service catalog overview , some services display the tag Free Tier, which indicates the service is
offering a free tier service plan. Some services display the tag Always Free, which indicates the service is offering a service plan
that comes free of additional charges, as it is already included in your overall SAP BTP contract. You can use the filter function of
the SAP Discovery Center to filter for services that offer Free Tier and Always Free plans. The Always Free service plans include
the following note in their service plan description: "This service plan is included in the overall SAP Business Technology Platform
contract".

This is custom documentation. For more information, please visit the SAP Help Portal 55
 10/15/24, 3:53 PM

 Note
Always Free service plans might not be available in all regions or for all providers.

Trial Lifecycle

Use your SAP BTP trial account:

Familiarize yourself with the Trial Scope or try out one of our Starter Scenarios on the Tutorial Navigator .

Extend your SAP BTP trial account in intervals:

Your 90-day trial period is divided in intervals. If you sign in to your trial account regularly, the intervals are extended
automatically for you by up to 30 days or until your overall 90-day trial is finished.

If you don't sign in to your trial account for 30 days or more, your account will be suspended. All suspended
accounts will be deleted and you won't be able to use applications or services.

Delete your SAP BTP trial account:

After 90 days, your trial account is automatically deleted. But if you want to proactively delete your SAP BTP trial
account, you can navigate to the global accounts scope and select the Account Explorer page, then click the Delete
Trial Account button.

If you want to continue to use an SAP BTP trial account after deletion, you need to set up a new account.

If you want to explore SAP BTP without time limit, create an enterprise account with free tier service plans
allowing you to test your scenarios. See: Get an Account on SAP BTP to Try Out Free Tier Service Plans .

 Caution
Environments enabled on your trial account may not be valid for your whole trial period. To learn about the validity period for
the Kyma environment, see About the Trial Account.

Trial Scope
A trial account enables you to explore the basic functionality of SAP BTP.

SAP BTP trial accounts use cloud management tools feature set B. For more information, see Cloud Management Tools —
Feature Set Overview.

SAP BTP trial accounts are available in several regions. For more information, see Regions.

You can create directories in your trial account. For more information, see Managing Directories Using the Cockpit

You can use productive and beta services. To consume beta services, you must enable the subaccount for beta features
during the subaccount creation or when you edit the subaccount details.

You can manage platform users by assigning them role collections. For more information, see Working with Role
Collections.

A trial account includes 4 GB of memory for applications.

You can use 8 GB of instance memory.

There are 10 total routes and 40 total services available.

You can use 2 configured on-premise systems with the Cloud connector.

There’s no service level agreement with regards to the availability of the platform.

This is custom documentation. For more information, please visit the SAP Help Portal 56
 10/15/24, 3:53 PM
You can use HDI containers in a shared SAP HANA database (only available on cf-us10).

For cleanup purposes, applications stop automatically on a daily basis. You need to manually restart them when needed.

 Note
Applications are stopped at midnight (or some time later depending on server load) relative to the region in which you
created your trial account. If you're working in a time zone that is far from the region where your trial account was
created, then your applications may stop during business hours.

You can have a trial tenant of SAP Cloud identity Services, see Get Your Tenant.

Related Information
Getting Started with a Trial Account in the Cloud Foundry Environment
Getting Started with a Trial Account in the Kyma Environment

Enterprise Accounts
Enterprise accounts are usually associated with SAP customer or partner contracts and contain their purchased entitlements to
platform resources and services. However, it's also possible to create an enterprise account for personal exploration.

SAP BTP provides different types of global accounts, enterprise and trial. The type you choose determines pricing, conditions of
use, resources, available services, and hosts.

If you want to start out using services for free, you can create a trial account and only use free tier service plans: The major benefit
of using such an account for exploration purposes is that you can upgrade your services to productive use without losing any of
your data. Check out the Free Tier Services in SAP Discovery Center and learn the details about Using Free Service Plans in your
enterprise account.

Another way to start out using services for free is to create a trial account. But keep in mind that when you want to use your global
account productively, there’s no way to migrate your data from the trial account to a productive enterprise account. For more
information, see Trial Accounts and Free Tier.

Enterprise Accounts

The main features of enterprise accounts are described for use by customers and by partners in the following table:

Customer Account Partner Account

Use case A global account that enables you to host productive, A global account that enables you to build
business-critical applications with 24/7 support. applications and to sell them to your customers.

You can purchase a global account just like any other If you want to start out exploring services for free,
SAP software. You can upgrade and refine your you can sign up for a Pay-As-You-Go for SAP BTP
resources later on. You can also contact your SAP global account and make use of the free tier services
sales representative and opt for a configuration, only. See Using Free Service Plans.
tailored to your needs.

If you want to start out exploring services for free,

you can sign up for a Pay-As-You-Go for SAP BTP
global account and make use of the free tier services
only. See Using Free Service Plans.

This is custom documentation. For more information, please visit the SAP Help Portal 57
 10/15/24, 3:53 PM

Customer Account Partner Account

Benefits Support for productive applications.

Includes SAP Application Development
licenses that enable you to get started with
scenarios across cloud and on-premise
applications.

Offers the opportunity to certify applications

and receive SAP partner logo package with
usage policies.

Advertise and sell applications via the SAP

Store

Services available Productive services. Productive and beta services.

Limitations Resources according to your contract. Predefined resources according to your partner
package. You can purchase additional resources if
necessary.

Registration For more information about SAP Integration Suite Sign up to join the SAP Partner Program .
and SAP Extension Suite pricing, see
https://www.sap.com/products/extension-
suite/pricing.html and
https://www.sap.com/products/integration-
suite/pricing.html .

Contact us on SAP BTP or via an SAP sales

representative.

If you’re located in China and want to buy a global

account on SAP BTP you need to contact an SAP
sales representative:
https://www.sap.cn/registration/contact.html .

Available Regions See Regions. See Regions.

Cancelling a SAP BTP Enterprise Account

As a business user, you can cancel your contract via your account executive. As an individual user with a trial acoount, you can
cancel your account in your SAP for Me account . You can also contact the SAP store via their "Contact Us" function.

For the commercial models available for enterprise accounts, see Commercial Models.

Related Information
Getting Started in the Kyma Environment
Getting Started with a Customer Account in the ABAP Environment
Getting Started with an Enterprise Account in the Cloud Foundry Environment

Commercial Models
SAP BTP offers two different commercial models for enterprise accounts.

This is custom documentation. For more information, please visit the SAP Help Portal 58
 10/15/24, 3:53 PM
Consumption-based commercial model: Your organization receives access to all current and future services that are
eligible for this model. You have complete flexibility to turn services on and off and to switch between services as your
business requires throughout the duration of your contract. This commercial model is available in the following flavors: SAP
BTP Enterprise Agreement (SAP BTPEA), Cloud Platform Enterprise Agreement (CPEA), and Pay-As-You-Go for SAP BTP.

For more information, see What Is the Consumption-Based Commercial Model?

Subscription-based commercial model: Your organization subscribes only to the services that you plan to use. You can
then use these services at a fixed cost, irrespective of consumption.

For more information, see What Is the Subscription-Based Commercial Model?

 Note
You can use both commercial models, either in separate global accounts or in the same global account depending on your
business needs. Contact your SAP account executive or sales representative for more information. Note however that you
cannot mix more than one flavor of the consumption-based commercial model in the same global account.

For information about service availability, prices, and estimators, see https://www.sap.com/products/technology-
platform/solutions.html and https://www.sap.com/products/technology-platform/integration-suite/pricing.html . You can
also view the service catalog via the SAP Discovery Center .

What Is the Consumption-Based Commercial Model?

 Note
The use of the consumption-based commercial model is subject to its availability in your country or region.

With the consumption-based model, your organization purchases an entitlement to all current and future SAP BTP services that
are eligible for this model. Throughout the duration of your contract, you have complete flexibility to turn services on and off and to
switch between services as your business requires.

The consumption-based commercial model is available in the following flavors: the SAP BTPEA (SAP BTP Enterprise Agreement),
the CPEA (Cloud Platform Enterprise Agreement), and Pay-As-You-Go for SAP BTP. Each option is suited to different business

This is custom documentation. For more information, please visit the SAP Help Portal 59
 10/15/24, 3:53 PM
situations and levels of financial commitment, as described in the table below. For additional information and clarifications, please
contact your account executive.

SAP BTPEA Your organization makes a prepaid investment in cloud

credits for the contract duration with an annual
commitment to consume SAP BTP services.

This model is suitable for customers that have well-

established and planned use cases, and who want the
flexibility of turning services on and off, and switching
between services, without the commitment of being tied to
a single service throughout the duration of the contract.

You receive a monthly balance statement that provides

information about the usage consumption of each service
and the corresponding costs. The total monthly cost is
deducted from your cloud credits balance.

This model has a minimum investment entry, and volume-

based discounts are available.

You are billed annually in advance. Any overages are billed

in arrears at list price.

You can top up your cloud credits at any time to prevent

overages.

You get access to new SAP BTP services that are added to
the consumption-based service catalog.

CPEA Your organization makes a prepaid investment in cloud

credits for the contract duration with an annual
 Note commitment to consume SAP BTP services.

Certain restrictions apply. See the Frequently Asked Questions

This model is suitable for customers that have well-
section in https://www.sap.com/products/technology-
established and planned use cases, and who want the
platform/pricing.html .
flexibility of turning services on and off, and switching
between services, without the commitment of being tied to
a single service throughout the duration of the contract.

You receive a monthly balance statement that provides

information about the usage consumption of each service
and the corresponding costs. The total monthly cost is
deducted from your cloud credits balance.

This model has a minimum investment entry, and volume-

based discounts are available.

You are billed annually in advance. Any overages are billed

in arrears at list price.

You can top up your cloud credits at any time to prevent

overages.

Pay-As-You-Go for SAP BTP You have the same access to all the services that are
available in SAP BTPEA, but with a highly flexible zero-
commitment model – you pay nothing upfront and there is
no minimum usage requirement or annual commitment.

You pay only for the SAP BTP services that you want, when
you use them.

You are billed monthly in arrears.

This is custom documentation. For more information, please visit the SAP Help Portal 60
 10/15/24, 3:53 PM
Service charges are non-discountable.

This low-risk model is suitable for customers with use

cases that are not well defined, and are interested in
running a proof-of-concept in a productive environment.
This model provides the flexibility of turning services on
and off, and switching between services, as needed
throughout the duration of the contract.

A seamless transition to the CPEA model is available, on

the condition that you have no other CPEA-based global
accounts.

If you want information about the Pay-As-You-Go for SAP BTP for
cloud test, demo, and development commercial model , go to the
SAP Partner Portal .

 Note
In global accounts that use the consumption-based commercial model, SAP BTP, Cloud Foundry runtime is not listed in
the Entitlements pages in the SAP BTP cockpit. A technical limit of 200 GB of Cloud Foundry runtime memory is
assigned by default to every subaccount. The limit defines the maximum amount of runtime memory that can be used
in the subaccount. Note that the “Standard” plan in the consumption-based commercial model is a paid plan and that
you are billed based on the amount of Cloud Foundry runtime you consume. For more information on consumption
monitoring, see Consumption Monitoring.

If you need to increase this limit, report an incident to SAP support on the BC-NEO-CIS component. This also applies
to other services that have a technical quota limit.

 Tip
You can monitor costs and service usage throughout the contract period. See Monitoring Usage and Consumption Costs in
Your Global Account.

For information about eligible services and pricing, see https://www.sap.com/products/technology-platform/pricing.html , or

access the SAP BTP service catalog via the SAP Discovery Center . The SAP BTP service catalog allows you to identify service
availability per data center and to determine licensing model compatibility per available service plan.

As part of the free tier model for SAP BTP, some services offer free service plans that allow you to try out these services without
any additional charge within your SAP BTPEA, CPEA, or Pay-As-You-Go for SAP BTP global account. For more information, see
Using Free Service Plans.

To find frequently asked questions about the consumption-based commercial model, see the Frequently Asked Questions section
in https://www.sap.com/products/technology-platform/pricing.html .

 Note
Depending on your business needs, you can combine the consumption-based commercial model with the subscription-based
commercial model in the same global account, or you can use both commercial models in the same global account. Contact
your SAP account executive or sales representative for more information. Note however that you cannot mix more than one
flavor of the consumption-based commercial model in the same global account.

Related Information
What Is the Subscription-Based Commercial Model?
Monitoring Usage and Consumption Costs in Your Global Account
View Subaccount Usage Analytics
Managing Global Accounts Using the Cockpit

This is custom documentation. For more information, please visit the SAP Help Portal 61
 10/15/24, 3:53 PM
Managing Directories Using the Cockpit
Managing Subaccounts Using the Cockpit
Managing Entitlements and Quotas Using the Cockpit

What Is the Subscription-Based Commercial Model?

Your organization receives a fixed price and period (typically a 1 to 3-year period) for access to your subscribed SAP BTP services.

Under this commercial agreement:

You are entitled to use only the subscribed services.

To access additional services, at an extra cost, you can modify your contract via your sales representative or account
executive.

You pay at a fixed cost, regardless of consumption of subscribed services.

You pay in advance when the contract period starts.

Your organization can renew the subscription at the end of the contract period.

For information about available services and pricing, see SAP Store .

You can also access the SAP BTP service catalog via the SAP Discovery Center to identify the availability of services by data
center, and also to determine licensing model compatibility per service plan.

Note that some services can be subscribed based on a user metric or a resource metric. For example, a Portal service can be
based on the number of site visits or user metrics. A resource-based metric is more common when dealing with a large number of
users; for example, suppliers accessing a portal to interact with your organization. Since it isn't always possible to predict how
many resources would be required upfront for a three-year period, you can increase your original order if resource usage exceeds
your subscribed quota. Using SAP BTP cockpit, you can view resource consumption within your global account on a monthly basis.

In the subscription-based model, you also get access to bundles or packages that comprise several related services and apps.
Most of the time, this works out to be more cost effective when compared to subscribing to individual SAP BTP services.

Can an existing global account under a consumption-based contract be transformed

to the subscription-based model?
You can change your existing contract from the consumption-based commercial model to a subscription license. Keep in mind that
not all services that are eligible for the consumption-based model are compatible with the subscription-based model. We
recommend that you contact your SAP account executive or sales representative to discuss feasibility and terms of transforming
your contract.

Note that you can use both consumption and subscription-based commercial models either in separate global accounts or in the
same global acccount depending on your business needs. Contact your SAP account executive or sales representative for more
information.

Related Information
What Is the Consumption-Based Commercial Model?
Monitoring Usage and Consumption Costs in Your Global Account
View Subaccount Usage Analytics
Managing Global Accounts Using the Cockpit
Managing Directories Using the Cockpit
This is custom documentation. For more information, please visit the SAP Help Portal 62
 10/15/24, 3:53 PM
Managing Subaccounts Using the Cockpit
Managing Entitlements and Quotas Using the Cockpit

Using Free Service Plans

The free tier model for SAP BTP lets you try out services in global accounts without any additional cost using the consumption-
based commercial model and an enterprise account.

We offer free service plans for many services within SAP BTP. Free service plans are limited in scope and capacity. They are
designed to allow you and your team to explore new SAP BTP capabilities before committing to subscribing to a full capacity paid
service.

The free tier model for SAP BTP is added automatically to new and existing contracts using the consumption-based commercial
model. There, the free service plans are visible.

 Note
The use of the consumption-based commercial model is subject to its availability in your country or region.

The consumption-based commercial model is available in the following flavors: the SAP BTPEA (SAP BTP Enterprise Agreement),
the CPEA (Cloud Platform Enterprise Agreement) and Pay-As-You-Go for SAP BTP. For more information, see What Is the
Consumption-Based Commercial Model?.

To try out services that participate in the free tier model for SAP BTP, create a service instance using the Free service plan offered
by the service.

 Tip
To find out which services offer the free plans, see Discover Free Services. Here, you also find information on how to identify the
technical limitations of the free plan of each service. Access Free Services by assigning entitlements to subaccounts and
creating service instances.

Once you reach the technical limits of a service and want to continue using it, you must move to a paid service plan. Upgrading an
existing service instance from free tier to paid usually doesn't require creating a new service instance. Find out how to upgrade a
service plan at Upgrade to a Paid Service Plan.

Use of free tier service plans is subject to additional terms and conditions as provided in the Business Technology Platform
Supplemental Terms and Conditions Only community support is available for Free service plans and these aren't subject to
SLAs.

Discover Free Services

Find out which services offer Free plans and what the limitations are.

Free Tier services can be explored in the service catalog of SAP Discovery Center. A free tier service appears as a "Free" plan
offering for a service.

1. Access the Service Catalog in the SAP Discovery Center .

2. In the Categories section, select Free Tier Services.

This is custom documentation. For more information, please visit the SAP Help Portal 63
 10/15/24, 3:53 PM

3. Select one of the services displayed in the catalog.

4. Navigate to the Pricing tab.

On this page, you can see all available plans for this service, including the limitations of each plan. Plans that participate in
the free tier model for SAP BTP are labeled Free.

Access Free Service Plans

To try out the free tier model for SAP BTP, you must entitle your subaccount for the free plan and create a service instance using
this plan.

 Note
The free tier model for SAP BTP is available for accounts that use the consumption-based commercial model.

1. Enter your global account.

For more information, see Access the Cockpit.

2. Configure entitlements for the subaccount in which you want to use the free service plans. Select the service and choose
the free plan.

For more information, see Managing Entitlements and Quotas Using the Cockpit.

3. Navigate into the subaccount and go to the Service Marketplace.

4. Find the service you want to try out and select it.

You find a description of the available service plans, including the free service plan. By clicking More, you find the scope and
limitations of the free plan for this service.

5. Create an instance of the service and select the free service plan.

For more information, see View and Manage Services from the Service Marketplace.

You can now start using this service.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 10/15/24, 3:53 PM

Update to a Paid Service Plan

Once you've reached the limits of the free plan, you can upgrade the free service plan to a paid plan.

 Note
The option to upgrade from free tier service plans to paid service plans is not yet available for all services and runtimes, such as
Kyma. To use a paid service plan for Kyma runtime, you will need a new Kyma cluster. It is possible to have both - free and paid
clusters - in parallel.

 Note
To update the ABAP environment to a paid service plan, you first need to configure entitlements and quotas for the ABAP
environment. You need at least the following entitlements assigned to your subaccount:

service plan: standard

quota plans:

1 abap_compute_unit

2 hana_compute_unit

For more information, see Increasing the Quota for the ABAP Environment.

 Note
It's not possible to switch from a paid plan to a free plan.

1. In your subaccount, navigate to the Instances and Subscriptions page.

2. Find the instance of the service and click  (Actions) and Update.

3. In the Update Instance dialog, change the plan to a paid service plan.

4. Click Update Instance to save your changes.

You can now use the service without the limitations of the free service plan.

Scope
The free tier model for SAP BTP is available for CPEA and Pay-As-You-Go for SAP BTP contracts. For more information, see
What Is the Consumption-Based Commercial Model?.

Services using the free tier service plans run on the same platform as paid services.

Services are technically limited. This limit depends on the service. You can find a description of the service plans in the
Service Marketplace in the cockpit or in the SAP Discovery Center .

Account Model
Learn more about the different types of accounts on SAP BTP and how they relate to each other.

Accounts are structured according to global accounts, subaccounts, and directories.

This is custom documentation. For more information, please visit the SAP Help Portal 65
 10/15/24, 3:53 PM
To learn more about managing your account model, see Account Administration.

Global Accounts
A global account is the realization of a contract you or your company has made with SAP.

A global account is used to manage subaccounts, members, entitlements and quotas. You receive entitlements and quotas to use
platform resources per global account and then distribute the entitlements and quotas to the subaccount for actual consumption.
There are two types of commercial models for global accounts: consumption-based model and subscription-based model. See
Commercial Models .

Global accounts are region- and environment-independent. Within a global account, you manage all of your subaccounts, which in
turn are specific to one region.

Subaccounts
Subaccounts let you structure a global account according to your organization’s and project’s requirements with regard to
members, authorizations, and entitlements.

A global account can contain one or more subaccounts in which you deploy applications, use services, and manage your
subscriptions. Subaccounts in a global account are independent from each other. This is important to consider with respect to
security, member management, data management, data migration, integration, and so on, when you plan your landscape and
overall architecture.

Each subaccount is associated with a region, which is the physical location where applications, data, or services are hosted. The
specific region is relevant when you deploy applications and access the SAP BTP cockpit using the corresponding cockpit URL.
The region assigned to your subaccount doesn't have to be directly related to your location. You could be located in the United
States, for example, but operate your subaccount in Europe.

The entitlements and quotas that have been purchased for a global account have to be assigned to the individual subaccounts.

Global accounts and subaccounts are completely independent of user accounts. For more information, see User and Member
Management.

This is custom documentation. For more information, please visit the SAP Help Portal 66
 10/15/24, 3:53 PM
Subaccounts, Cloud Foundry Orgs and Kyma Clusters

When you enable the Cloud Foundry environment in one of your subaccounts, the system automatically creates a Cloud
Foundry org for you. The subaccount and the org have a 1:1 relationship and the same navigation level in the cockpit (even
though they may have different names). You can create spaces within that Cloud Foundry org. Spaces let you further break
down your account model and use services and functions in the Cloud Foundry environment.

For more information about Cloud Foundry orgs and spaces, see the Cloud Foundry documentation at
https://docs.cloudfoundry.org/concepts/roles.html .

When you enable the Kyma environment in one of your subaccounts, the system automatically creates a Kubernetes
cluster equipped with the latest version of the open-source project "Kyma" for you. The subaccount and the Kyma cluster
have a 1:1 relationship. You can create namespaces within that Kyma cluster. Namespaces let you further break down your
account model and use services and functions in the Kyma environment. For more information, see the Kubernetes
documentation at https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ .

Directories
With directories, you can organize and manage your subaccounts according to your technical and business needs.

A directory can contain directories and subaccounts to create a hierarchy. Using directories to group other directories and
subaccounts is optional - you can still create subaccounts directly under your global account.

You can create a hierarchical structure that is up to 7 levels deep. The highest level of a given path is always the global account and
the lowest is a subaccount, which means that you can have up to 5 levels of directories between the global account and the lowest
level subaccount.

This is custom documentation. For more information, please visit the SAP Help Portal 67
 10/15/24, 3:53 PM

Directories enable you to:

Group and filter directories and subaccounts

Monitor usage and costs for contracts that use the consumption-based commercial model

Optionally, you can also enable the following features in your directories:

Manage Entitlements: Enables the assignment of a quota for services and applications to the directory from the global
account quota, for distribution to the directory's subaccounts.

When you assign entitlements to a directory, you express the entitlements and maximum quota that can be distributed
across its children subaccounts. You also have the option to choose the auto-assignment of a set amount of quota to all
subaccounts created or moved to that directory. Subaccounts that are already in the directory when you select that option
will not be auto-assigned quota.

 Note
If you've enabled the Manage Entitlements feature for a given directory, you must first assign the necessary
entitlements and maximum allowed quota from the global account to that directory. Then you can distribute this
"reserved" quota to any of the directory's child subaccounts.

Manage Authorizations: Enables authorization management for the directory. For example, it allows certain users to
manage directory entitlements. You can only use this feature in combination with the Manage Entitlements feature.

Related Information
Manage the Account Explorer Hierarchy
Configure Entitlements and Quotas for Directories
Configure Entitlements and Quotas for Subaccounts
Getting a Global Account
Setting Up Your Account Model
Managing Global Accounts Using the Cockpit
Managing Directories Using the Cockpit
Managing Subaccounts Using the Cockpit
Working with Global Accounts, Directories, and Subaccounts Using the btp CLI
Account Administration Using APIs of the SAP Cloud Management Service

This is custom documentation. For more information, please visit the SAP Help Portal 68
 10/15/24, 3:53 PM

Relationship Between Global Accounts and Subaccounts

[Feature Set A]
A global account can group together different subaccounts that an administrator makes available to users. Administrators can
assign the available quotas of a global account to its different subaccounts and move it between subaccounts that belong to the
same global account.

The hierarchical structure of global accounts and subaccounts lets you define an account model that accurately fits your business
and development needs. For example, if you want to separate development, testing, and productive usage, you can create a
subaccount for each of these scenarios in your global account. You can also create subaccounts for different development teams
or departments in your organizations.

For more information about the relationship between a global account and its subaccounts, see the graphic in Basic Platform
Concepts. For best practices, see Setting Up Your Account Model.

Relationship Between Global Accounts, Subaccounts, and

Directories
A global account can group together different directories and subaccounts that an administrator makes available to users.
Administrators can assign the available entitlements and quotas of a global account to its different subaccounts and move it
between subaccounts that belong to the same global account.

 Note
The content in this section is only relevant for cloud management tools feature set B. For more information, see Cloud
Management Tools - Feature Set Overview.

The hierarchical structure of global accounts, directories, and subaccounts lets you define an account model that accurately fits
your business and development needs. For example, if you want to separate development, testing, and productive usage for
different departments in your organization, you can create a directory for each department, and within each directory, you group
subaccounts for development, testing, and production.

Labels
Labels are user-defined words or phrases that you can assign to various entities in SAP BTP to categorize them in your global
account, to identify them more easily.

For example, in the Account Explorer page in the cockpit, you can quickly filter for directories and subaccounts by label.

You can assign labels to these entities when you create or edit them using the SAP BTP cockpit, command line interface (btp CLI),
or REST APIs:

Directories

Subaccounts

Multitenant application subscriptions

Service instances

Environment instances

This is custom documentation. For more information, please visit the SAP Help Portal 69
 10/15/24, 3:53 PM

 Note
For environment instances, these custom labels are user defined and apply only to SAP BTP. They are not the same
labels that might be defined by your environment broker.

Labels are made up of a label name (also referred to as a key) and up to 10 values associated with the label. You can apply label
names and values in any way that suits your business and technical needs.

Types of labels and examples

Types of Labels Examples

Single-value labels are useful for labels that have an identifier, or

Label Name: Cost Object
for labels with fixed lists.
Value: The ID of a cost center number or internal order that
is associated with the entity, such as: 000001134789

Label Name: Status

Value: Active or Inactive

Label Name: Landscape

Value: Dev or Test or Production

Multi-value labels make them useful for labels that typically have
Label Name: Contacts
more than one value assigned to them.

Value: The e-mail addresses or names of users that are

responsible for the entity, such as: admin-
[email protected] and [email protected]

Labels can also be assigned with a name only and no value. In such
Label Name: For demo only
cases, the label behaves like tag.
Note that currently for service instances, labels must have at least Label Name: Audited
value.
Label Name: Flagged for deletion

 Note
Labels replace what were previously called "custom properties". Custom properties supported only single values per label and
were available only to directories and subaccounts. As a result of the move to labels, all relevant commands in the SAP BTP
command line interface (btp CLI) and in the relevant REST APIs in the SAP Cloud Management service have been updated
accordingly. The custom-properties parameter in the btp CLI and the customProperties field in the relevant REST APIs
are deprecated.

You can assign labels when you create an entity, and then later add, change, or remove labels by editing the entity.

 Tip

In the Account Explorer and Instances and Subscriptions pages in the SAP BTP cockpit, assigned labels are shown in
the Labels column. To display the column if it is not shown, click  (Configure Table Columns).

In the Account Explorer page, you can view the labels that are assigned to a directory or subaccount by choosing the
More Info option of each directory and subaccount.

Assigned labels are also listed under the Labels tab when you display the Overview page of every directory and
subaccount.

This is custom documentation. For more information, please visit the SAP Help Portal 70
 10/15/24, 3:53 PM
In the Account Explorer and Instances and Subscriptions pages, you can filter the displayed entities by their assigned
labels in the Search field.

In the Instances and Subscriptions page, you can also view the labels that are assigned to a subscription or instance by
expanding its details panel.

When working with labels, consider the following aspects:

In the cockpit, each entity can have up to 10 labels assigned to it.

You cannot add the same label name more than once to the same entity.

Existing label names and values are offered as suggestions when you or anyone else assigns a label to other entities of the
same type in your global account.

When you view a subaccount in the cockpit, the subaccount also shows the labels that are assigned to its parent directory
and to other directories that are above it in the same path in your account structure. And in the Account Explorer, when you
filter by labels that are assigned to a directory, the subaccounts in that directory path are also listed. We refer to these as
inherited labels.

Label names and values are case-sensitive, which means you can create variants of the same label name with a different
casing; for example, My Label and My label can coexist as separate labels. We recommend that you avoid using
different casing or styling to create variants of the same names or values.

Related Links

Create a Subaccount

Change Subaccount Details

Create a Directory

Cloud Management Tools — Feature Set Overview

Commands in the btp CLI

Account Administration Using APIs of the SAP Cloud Management Service

Managing Service Resources Using the APIs of the SAP Service Manager

Creating Service Instances

Working with Environment Instances

Subscribe to Multitenant Applications Using the Cockpit

Entitlements and Quotas

When you purchase an enterprise account, you’re entitled to use a specific set of resources, such as the amount of memory that
can be allocated to your applications.

Services and Service Plans

On SAP BTP, all external dependencies such as databases, messaging systems, files systems, and so on, are services. In this
context, multitenant applications and environments are considered services.

Each service has one or more service plans available. A service plan is the representation of the costs and benefits for a given
variant of a particular service. For instance, a database may be configured with various "T-shirt sizes", each of which is a different
service plan.

This is custom documentation. For more information, please visit the SAP Help Portal 71
 10/15/24, 3:53 PM

Entitlements
An entitlement is your right to provision and consume a resource. In other words, entitlements are the service plans that you're
entitled to use.

Quotas
A quota represents the numeric quantity of a service plan that you're entitled to consume in your global account and its
subaccounts.

From the perspective of your SAP BTP global account contract, the global quota of a service plan can be defined as either fixed or
unlimited:

Fixed quota: The quota or allowance of the service plan is the upper limit at which the plan can be consumed collectively
across your global account. This is typical of global accounts that have the subscription-based commercial model
agreement.

Unlimited quota: There is no upper limit to how much the service plan can be used collectively across your global account.
This is typical of most services that are eligible to global accounts with a consumption-based commercial model
agreement (Cloud Platform Enterprise Agreement (CPEA) and Pay-As-You-Go for SAP BTP). At the end of the month, the
number of units used determines how much you are charged.

Regardless of whether the global quota of a plan on the global account level is fixed or unlimited, the specifics and properties of
each plan determines how its quota can be distributed by the global account admin to the subaccounts in your global account.
There are two types of quota assignments:

Numeric assignments: The global account admin assigns the plan to a subaccount and specifies the maximum quantity of
units from the global quota that can be consumed by the subaccount. Admins can use this assignment to limit users from
exceeding a specific quota for cost-controlling purposes. Typically, but not always, the assigned quota is directly related to
the number of instances that can be created in subaccounts for the assigned plan.

Non-numeric assignments: The global account admin does not assign a specific quantity but simply grants access to the
specific plan by assigning the plan to the subaccount. When the plan is assigned, it's available for use by the subaccount.
SaaS application assignments are typically non-numeric, whereby a subaccount can either subscribe to the app or not. For
services that fall into this category of non-numeric assignments, there is usually no limit to the number of instances that
can be created.

See also the sections below and Managing Entitlements and Quotas Using the Cockpit.

Distribution and Usage of Entitlements and Quotas

Entitlements and quotas are purchased and managed at global account level, from where they’re distributed to subaccounts,
which consume them.

This is custom documentation. For more information, please visit the SAP Help Portal 72
 10/15/24, 3:53 PM

 Tip
You can also distribute entitlements to directories, and then redistribute to the subaccounts under the directories; however,
this is optional. By default, directories are not enabled to manage entitlements. This feature needs to be enabled per directory
by the global account administrator.

When assigning entitlements and quotas to directories, you also have the option to automatically assign a set amount of quota to
each new subaccount added to the directory. This option doesn’t apply to subaccounts that are already in the directory when you
select this option. The quota you assigned to the directory is then gradually distributed to all subaccounts that you add to that
directory, until it runs out. Once the directory quota runs out, if you add a new subaccount to that directory it won't get any quota
automatically anymore.

Since directories are only a way of grouping subaccounts, you can't consume a service at directory level. However, when you assign
entitlements and quotas from the global account to a directory, the quota you assigned is shown as used, even if there are no
subaccounts in that directory to consume the quota. You can think of it as a way to "reserve" quota and make sure it's not assigned
to other subaccounts or directories.

When you remove quotas or assignments from a directory or subaccount, they become available again at global account level and
can be assigned to other directories or subaccounts; unless the quota is reserved for a given directory then the freed quota
remains available only to that directory and its subaccounts.

 Note
Before a subaccount admin can enable a quota-based environment, such as Kyma, the subaccount admin must first assign the
environment as an entitlement to the subaccount. Other environments, such as Cloud Foundry, are available by default to all
subaccounts, and therefore are not available as entitlements.

For more information, see:

Configure Entitlements and Quotas for Subaccounts

Configure Entitlements and Quotas for Directories

Quota Plans
In the Cloud Foundry environment, you can further distribute the quotas that are allocated to a subaccount. This is done by
creating space quota plans and assigning them to the spaces.

Space quota plans are optional and are used to limit how much each space can use, not to enable. If you don't create any space
quota plans, all spaces in a subaccount using the Cloud Foundry environment have access to all entitlements and quotas in that
subaccount. This means that one space could use up all the quota in a subaccount. If you want to prevent that from happening and
set a limit to how much each space can use from the total quota available in the subaccount, you can use quota plans and assign
them to spaces.

For more information on space quota plans in the Cloud Foundry environment, see:

https://docs.cloudfoundry.org/adminguide/quota-plans.html

Managing Space Quotas

Resource Providers
SAP BTP allows you to connect your global account in the SAP BTP Cockpit to your provider account from a non-SAP cloud
vendor, and consume remote service resources that you already own and which are supported by SAP through this channel.

This is custom documentation. For more information, please visit the SAP Help Portal 73
 10/15/24, 3:53 PM
For example, if you’re subscribed to Amazon Web Services (AWS) and have already purchased services, such as PostgreSQL, you
can register the vendor as a resource provider in SAP BTP and consume this service across your subaccounts together with other
services offered by SAP.

SAP BTP currently supports the following vendors and their consumable services:

Cloud Vendor Supported Services

Amazon Web Services Amazon Relational Database Service (RDS) - PostgreSQL

Microsoft Azure Azure Database for PostgreSQL.

After you configure a new resource provider, its supported services are added as entitlements in your global account. In the
Entitlements page in the cockpit, you can then allocate the required services and quotas to the relevant directories and
subaccounts in your global account.

For more information, see Managing Resource Providers.

Related Information
Managing Entitlements and Quotas Using the Cockpit
Tutorial: Manage Entitlements on SAP BTP Trial
Troubleshooting: Entitlement and Quota Problems

User and Member Management

On SAP BTP, member management takes place at all levels from global account to environment, while user management is
relevant for business applications.

User Accounts
A user account corresponds to a particular user in an identity provider. The user is always stored in an external identity provider,
such as a custom tenant of SAP Cloud Identity Services - Identity Authentication or the default identity provider.

User accounts enable users to log on to SAP BTP, access subaccounts, and to use applications according to the permissions
granted to them.

 Note
A user name alone doesn't determine a concrete user account with associated authorizations, as you can have users with the
same user name in different identity providers. Accessible data and allowed operations also depend on the identity provider.
The concrete user is identified by the combination of user name and identity provider.

 Example
There are two users with the same user name, which is the email address here. The two users with different identity providers
have different authorizations and can access different applications.

[email protected] from the custom identity provider has authorizations to access her favorite industrial
applications. She needs the logon with the custom identity provider for her actual work.

This is custom documentation. For more information, please visit the SAP Help Portal 74
 10/15/24, 3:53 PM
[email protected] from the default identity provider has no authorizations.

Before diving into the different user and member management concepts, it's important to understand the difference between the
two types of users we’re referring to: platform users and business users.

For more information, see Platform Users and Business Users.

Related Information
Working with Users
Roles and Role Collections
Attributes
Trust and Federation with Identity Providers

Platform Users
Platform users are usually developers, administrators or operators who deploy, administer, and troubleshoot applications and
services on SAP BTP. They’re the users that have full access and give certain permissions, for instance, at global account,
directory, or subaccount level. Members only have basic access.

Platform users who have administrative permissions can view or manage the list of global accounts, subaccounts, and
environments, such as Cloud Foundry orgs and spaces. Members have basic access to them using the SAP BTP cockpit, the SAP
BTP command-line interface (btp CLI), or environment-specific CLI, such as the Cloud Foundry (CF) CLI.

For platform users, there's a default identity provider. We expect that you have your own identity provider. We recommend that you
configure your custom tenant of SAP Cloud Identity Services as the identity provider and connect SAP Cloud Identity Services to
your own corporate identity provider.

 Note
For China (Shanghai) and Government Cloud (US) regions, a different default identity provider is used, and you can't use SAP
Cloud Identity Services as identity provider in the global account.

If you want to use two-factor authentication in the China (Shanghai) region, see this blog article on SAP Community.

This is custom documentation. For more information, please visit the SAP Help Portal 75
 10/15/24, 3:53 PM

Member Management

Member management refers to managing permissions for platform users. Members have only basic access to SAP BTP.

Member management happens at global account, directory, subaccount, and environment level. Members' permissions apply to
all operations that are associated with the global account, the organization, or the space, irrespective of the tool used. Depending
on the scope and the cloud management tools you're using, you manage members in different ways:

Global Accounts Directories Subaccounts

You manage global account members by You manage directory members by You manage subaccount members by
assigning role collections to platform users. assigning role collections to platform users. assigning role collections to platform users.
Use the following predefined role Use the following predefined role
collections: collections:  Note
Neo subaccounts don’t use role
Global Account Administrator Directory Administrator
collections.
Global Account Viewer Directory Viewer
For more information, see Managing
Assign these role collections from the SAP Assign these role collections from the SAP Member Authorizations in the Neo
BTP cockpit or the btp CLI. BTP cockpit or the btp CLI. Environment.

See: See:
Use the predefined role collections, such as:
Role Collections and Roles in Global Role Collections and Roles in Global
Subaccount Administrator
Accounts, Directories, and Subaccounts Accounts, Directories, and Subaccounts
Subaccount Viewer
Add Members to Your Global Account Create Users
Assign these role collections from the SAP
Create Users Manage Users in Directories
BTP cockpit or the btp CLI.

See:

Role Collections and Roles in Global

Accounts, Directories, and Subaccounts

Add Members to Your Subaccount

Create Users

Member Management in the Cloud Foundry Environment

Orgs Spaces

Manage org members on the Members page at environment level Manage space members on the Members page at space level in the
in the SAP BTP cockpit or with the Cloud Foundry CLI. SAP BTP cockpit or with the Cloud Foundry CLI.

A platform user added as an org member can be either an Org A platform user added as a space member can be either a Space
Manager or an Org Auditor or implicitly an Org User. Manager, Space Developer, Space Auditor, or Space Supporter.

See: See:

About Roles in the Cloud Foundry Environment About Roles in the Cloud Foundry Environment

https://docs.cloudfoundry.org/concepts/roles.html#roles https://docs.cloudfoundry.org/concepts/roles.html#roles

Add Org Members Add Space Members

For more information on the Kyma environment, see Assign Roles in the Kyma Environment.

See also About User Management in the Cloud Foundry Environment.

This is custom documentation. For more information, please visit the SAP Help Portal 76
 10/15/24, 3:53 PM

Role Collections and Roles in Global Accounts, Directories, and

Subaccounts
SAP BTP provides a set of role collections to set up administrator access to your global account and subaccounts.

Role collections group authorizations for resources and services. Your administrators assign these role collections to other
platform users to create new administrators. Role collections consist of individual roles. For more information on role collections,
roles, see the related link.

Role collections are account-specific. Role collections that exist in the global account don’t exist in the subaccounts. Likewise, role
collections in subaccounts aren’t available in the global account.

 Note
Neo subaccounts don’t use role collections.

For more information, see Managing Member Authorizations in the Neo Environment.

Role Collections

You can use the default role collections, but you can’t change or delete them. SAP BTP provides the following administrator role
collections:

Global Account Administrator

Subaccount Administrator

Directory Administrator

Cloud Connector Administrator

Connectivity and Destination Administrator

Destination Administrator

Subaccount Service Administrator

SAP BTP provides also viewer role collections for the global account and for subaccounts. In contrast to the administrator role
collections, viewer role collections only grant read access.

Global Account Viewer

Subaccount Viewer

Directory Viewer

Administrator Role Collections

If you assign the Global Account Administrator role collection to a user, this user can perform administration tasks for
subaccounts, role collections, identity providers, entitlements, and regions on the level of the global account. If you assign the
Global Account Viewer role collection, this user can view subaccounts, role collections, identity providers, entitlements, and
regions on the level of the global account.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 77
 10/15/24, 3:53 PM
You can also use the command-line interface (CLI) for SAP BTP to assign authorizations. For more information on managing
authorizations, see the related link.

Global Account Administrator Role Collection

Roles Included Description

Global Account Admin Role for global account members with read-write authorizations for
core commercialization operations, such as updating global
accounts, setting entitlements, and creating, updating, and
deleting subaccounts.

The GlobalAccount_Admin role template contains this role. You

find the role template in the SAP BTP Cockpit if you choose the cis-
central!<suffix> application identifier.

 Example
cis-central!b1

Global Account Usage Reporting Viewer Role for global account members with read-only authorizations for
core commercialization operations, such as viewing global account
usage information.

The GlobalAccount_Usage_Reporting_Viewer role template

provides this role. You find the role template in the SAP BTP
Cockpit if you chose the uas!<suffix> application identifier

User and Role Administrator Manage authorizations, trusted identity providers, and users.

The xsuaa_admin role template provides this role. You find the role
template in the SAP BTP Cockpit if you choose the xsuaa!<suffix>
application identifier.

 Example
xsuaa!tl

System Landscape Administrator Administrative access to systems and scenario-related resources.

The GlobalAccount_System_Landscape_Administrator role

template provides this role. You find the role template in the SAP
BTP Cockpit if you choose the cmp!<suffix> application identifier.

 Example
cmp!b7

If you assign the Subaccount Administrator role collection to a user, you grant a user administration permission for a subaccount.

Subaccount Administrator Role Collection

Roles Included Description

Cloud Connector Administrator Operate the data transmission tunnels used by the Cloud
connector.

Destination Administrator Manage destination configurations, certificates and subaccount

trust via the Destination editor in the SAP BTP cockpit.

This is custom documentation. For more information, please visit the SAP Help Portal 78
 10/15/24, 3:53 PM

Roles Included Description

Subaccount Admin Role for subaccount members with read-write authorizations for
core commercialization operations, such as viewing subaccount
entitlements, and creating and deleting environment instances.

Subaccount Service Administrator Administrative access to service brokers and environments on a

subaccount level.

User and Role Administrator Manage authorizations, trusted identity providers, and users.

If you assign the Cloud Connector Administrator role collection to a user, you grant the user administration permissions for the
Cloud Connector in a subaccount.

Cloud Connector Administrator Role Collection

Roles Included Description

Cloud Connector Administrator Operate the data transmission tunnels used by the Cloud
connector.

If you assign the Connectivity and Destination Administrator role collection to a user, you grant the user administration
permissions for the Cloud Connector and SAP Destination service in a subaccount.

Connectivity and Destination Administrator Role Collection

Roles Included Description

Cloud Connector Administrator Operate the data transmission tunnels used by the Cloud
connector.

Destination Administrator Manage destination configurations, certificates and subaccount

trust via the Destination editor in the SAP BTP cockpit.

If you assign the Destination Administrator role collection to a user, you grant the user administration permissions for the SAP
Destination service in a subaccount.

Destination Administrator Role Collection

Roles Included Description

Destination Administrator Manage destination configurations, certificates and subaccount

trust via the Destination editor in the SAP BTP cockpit.

If you assign the Subaccount Service Administrator role collection to a user, you grant the user administration permissions for
the Service Manager in a subaccount.

Subaccount Service Administrator Role Collection

Roles Included Description

Subaccount Service Administrator Administrative access to service brokers and environments on a

subaccount level.

Viewer Role Collections

This is custom documentation. For more information, please visit the SAP Help Portal 79
 10/15/24, 3:53 PM
If you assign the Global Account Viewer role collection to a user, you grant read access to the same information as the Global
Account Administrator role collection.

Global Account Viewer Role Collection

Roles Included Description

Global Account Viewer Role for global account members with read-only authorizations for
core commercialization operations, such as viewing global
accounts, subaccounts, entitlements, and regions.

Global Account Usage Reporting Viewer Role for global account members with read-only authorizations for
core commercialization operations, such as viewing global account
usage information.

User and Role Auditor Read-only access for authorizations, trusted identity providers, and
users.

System Landscape Viewer Viewer access to systems and scenario-related resources.

If you assign the Subaccount Viewer role collection to a user, you restrict a user's viewer permission to the subaccounts.

Subaccount Viewer Role Collection

Roles Included Description

Cloud Connector Auditor View the data transmission tunnels used by the Cloud connector to
communicate with back-end systems.

Destination Viewer View destination configurations, certificates and subaccount trust

via the Destination editor in the SAP BTP cockpit.

Subaccount Service Auditor Read-only access to service brokers and environments on a

subaccount level

Subaccount Viewer Role for subaccount members with read-only authorizations for
core commercialization operations, such as viewing subaccount
entitlements, details of environment instances, and job results.

User and Role Auditor Read-only access for authorizations, trusted identity providers, and
users.

Directory Role Collections

The role collections Directory Administrator and Directory Viewer can be assigned after the creation of a directory. If you select
the Enable user management checkbox, you receive the Directory Administrator role collection by default. You can't create
custom role collections for directories.

The Directory Administrator role collection grants a user administration permission for directories.

Directory Administrator Role Collection

Roles Included Description

Directory Admin Role for directory members with read-write authorizations for core
commercialization operations, such as updating directories, setting
entitlements, and creating, updating, and deleting subaccounts.

This is custom documentation. For more information, please visit the SAP Help Portal 80
 10/15/24, 3:53 PM

Roles Included Description

Directory Usage Reporting Viewer Role for directory members with read-only authorizations for core
commercialization operations, such as viewing directory usage
information.

User and Role Administrator Manage authorizations, trusted identity providers, and users.

The Directory Viewer role collection grants a user read access to the same information as the Directory Administrator role
collection.

Directory Viewer Role Collection

Roles Included Description

Directory Usage Reporting Viewer Role for directory members with read-only authorizations for core
commercialization operations, such as viewing directory usage
information.

Directory Viewer Role for directory members with read-only authorizations for core
commercialization operations, such as viewing directories,
subaccounts, entitlements, and regions.

User and Role Auditor Read-only access for authorizations, trusted identity providers, and
users.

Roles

Create your own role collections by using the roles of the default role collections. The roles are based on role templates, which are
provided by applications. The application identifier refers to the application, which provides the role templates.

 Example
The GlobalAccount_Admin role template provides the Global Account Admin role. You find the role template in the cockpit if
you choose the cis-central!<suffix> application identifier.

 Example
cis-central!b1

The following table provides the information about the roles that are available.

Role Details

Roles Available in Role Templates Application Identifier

Cloud Connector Subaccount Cloud_Connector_Administrator connectivity!<suffix>

Administrator

Cloud Connector Auditor Subaccount Cloud_Connector_Auditor connectivity!<suffix>

Destination Administrator Subaccount Destination_Administrator destination-xsappname!

<suffix>

Destination Viewer Subaccount Destination_Viewer destination-xsappname!

<suffix>

This is custom documentation. For more information, please visit the SAP Help Portal 81
 10/15/24, 3:53 PM

Roles Available in Role Templates Application Identifier

Directory Admin Directory Directory_Viewer cis-central!<suffix>

Directory Usage Reporting Directory Directory_Usage_Reporting_Viewer uas!<suffix>

Viewer

Directory Viewer Directory Directory_Admin cis-central!<suffix>

Global Account Admin Global account GlobalAccount_Admin cis-central!<suffix>

Global Account Viewer Global account GlobalAccount_Viewer cis-central!<suffix>

Global Account Usage Global account GlobalAccount_Usage_Reporting_Viewer uas!<suffix>

Reporting Viewer

System Landscape Global account GlobalAccount_System_Landscape_Administrator cmp!<suffix>

Administrator

System Landscape Viewer Global account GlobalAccount_System_Landscape_Viewer extension-service-cmp!

<suffix>

Subaccount Admin Subaccount Subaccount_Admin cis-local!<suffix>

Subaccount Viewer Subaccount Subaccount_Viewer cis-local!<suffix>

Subaccount Service Subaccount Subaccount_Service_Administrator service-manager!<suffix>

Administrator

Subaccount Service Subaccount Subaccount_Service_Auditor service-manager!<suffix>

Auditor

User and Role Global account and xsuaa_admin xsuaa!<suffix>

Administrator subaccount

User and Role Auditor Global account and xsuaa_auditor xsuaa!<suffix>

subaccount

Roles in Environments

If you've enabled environments in your subaccount, manage the roles for those environments. For more information, see:

About Roles in the Cloud Foundry Environment

Assign Roles in the Kyma Environment

 Note
The ABAP environment uses the roles of the SAP BTP, Cloud Foundry Environment.

Related Information
User and Member Management
Working with Role Collections
Building Roles and Role Collections for Applications
Mapping Role Collections in the Subaccount
Managing Users and Their Authorizations Using the btp CLI

This is custom documentation. For more information, please visit the SAP Help Portal 82
 10/15/24, 3:53 PM

Bringing Your Corporate Identity Provider for Platform Users

SAP BTP supports the use of your own identity provider for platform users.

Platform users perform technical development, operations, and administration tasks. They manage global accounts, directories,
and subaccounts using the SAP BTP cockpit and the SAP BTP CLI. They also develop and operate custom applications. By hosting
these users in your own identity provider, you gain a number of advantages over hosting them in SAP ID service or in SAP Universal
ID.

Integrate the management of these users with your broader identity management strategy, hosted on your own identity
providers. You control your own user lifecycle and single sign-on strategies throughout the entire landscape.

Enforce your own password and authentication policies, such as stronger passwords or multifactor authentication.

The following figure illustrates the architecture required for platform users. This configuration is independent of the default
configuration with SAP ID service. You can continue to use SAP ID service in parallel.

Authentication Architecture for Platform Users with a Corporate Identity Provider

In the preceding figure, you enable trust between the SAP BTP global account and your corporate identity provider over your
tenant of SAP Cloud Identity Services - Identity Authentication. Trust is configured differently in the Kyma environment (see the
related link). For each global account, you choose the SAP Cloud Identity Services tenant to use as the identity provider for
platform users. For the platform identify provider, you can have up to three SAP Cloud Identity Services tenants per global
account. Multiple global accounts can share the same SAP Cloud Identity Services tenant. When you log on to a platform resource,
such as the cockpit, you indicate the SAP Cloud Identity Services tenant that you want to log on with. For example, to log on to the
cockpit, copy a URL parameter from the cockpit to identify the tenant:

https://cockpit.btp.cloud.sap/cockpit/?idp=<tenant>.accounts.ondemand.com

For example: https://cockpit.btp.cloud.sap/cockpit/?idp=cidppuxhm.accounts.ondemand.com

Once you’ve logged on, the cockpit displays any global accounts and subaccounts of which your platform user is a member.

A user identifier alone isn’t enough to identify a user. Additionally, you also need an identifier for an identity provider. The reason is
that the system treats users with the same name but from different identity providers as separate users.

For global accounts, directories, multi-environment subaccounts, and the Cloud Foundry environment, the user identifier is always
an email address, and the identifier of the identity provider is the origin key (alias for the trust configuration). For example, a
platform user in the default identity provider, SAP ID service, and another user in your corporate identity provider with the same
email address might have different authorizations.

 Example
There are two users with the same email address. It is common practise that the two users with different identity providers
have different authorizations and can access different applications.

This is custom documentation. For more information, please visit the SAP Help Portal 83
 10/15/24, 3:53 PM
[email protected] with the default identity provider isn't authorized for any subaccount.

[email protected] with the acme-platform custom identity provider is the administrator for multiple
subaccounts. The subaccounts are only visible when she logs on with the custom identity provider.

You can log on to the cockpit with both, but the cockpit displays different user information. This difference is because you’ve
logged on with different identity providers.

For Neo subaccounts, it is, by default, the P user ID for local SAP Cloud Identity Services users or whatever the corporate identity
provider connected to the SAP Cloud Identity Services tenant sends as subject. The identifier of the identity provider is the default
domain of the SAP Cloud Identity Services tenant, for example acme.accounts.ondemand.com. It is called "user base". For
more information, see Platform Identity Provider.

You also see this difference when assigning roles. You must provide the origin or user base in addition to the email address or user
ID of the user. When platform users use the Cloud Foundry command-line interface or service dashboards, they need to remember
the origin. You can choose your own origin, but the origin must be unique across all customers. We recommend that you use a
meaningful name that helps identify the target it points to.

In SAP Cloud Identity Services - Identity Authentication in Neo subaccounts, there's one application that represents SAP BTP
overall. So, if you have multiple global accounts with the same SAP Cloud Identity Services tenant, they all share the same
application in your SAP Cloud Identity Services tenant. Here customers typically configure settings such as the corporate identity
provider used for authentication and user attribute mapping between systems. For more information, see Map User Attributes
from a Corporate Identity Provider for Platform Users.

Related Information
Log On with a Custom Identity Provider to the Cloud Foundry Environment Using the Cloud Foundry Command-Line Interface
Establish Trust and Federation of Custom Identity Providers for Platform Users
Configure a Custom Identity Provider for Kyma

Impact of Upgrading from Feature Set A to Feature Set B on User

and Account Management
While we've tried to make upgrading your account management feature set as simple as possible, we've had to make a few
adjustments. To help you find your way, we've gathered a summary of changes you can expect in your accounts.

 Note
For more information about the upgrade process itself, see SAP Note 3027721 .

Reactivation of the Default Identity Provider for Applications

If you deactivated the default identity provider, SAP ID service, for business users in multi-environment subaccounts in cloud
management tools feature set A, the process of upgrading to cloud management tools feature set B reactivates the default identity
provider. We reactivate the default identity provider because cloud management tools feature set B also uses it for platform users.

 Recommendation
Keep at least one user from the default identity provider in each account to still have access if there are ever issues with a
custom identity provider.

This is custom documentation. For more information, please visit the SAP Help Portal 84
 10/15/24, 3:53 PM
Even though the default identity provider has been reactivated, the option to authenticate with the default identity provider is
hidden from business users. Business users are redirected to your custom identity provider. Hiding the default identity provider
ensures that the user experience for your business users remains the same. Users from the default identity provider can log on,
only if the users are authorized, in other words, users with existing shadow users.

For more information about shadow users, see Working with Users.

 Note
Whether the default identity provider was reactivated or not, applications that share the default identity provider, such as SAP
Support Portal or your demo application in your subaccount, no longer require reauthentication, when you switch from one
application to the other. This change improves the single sign-on experience.

Custom Identity Providers for Platform Users

In cloud management tools feature set B, you're free to integrate custom identity providers for platform users. If you use custom
identity providers for platform users in cloud management tools feature set A, see SAP Note 3264627 .

Global Account Users Identified by E-Mail Address

With cloud management tools feature set B, global account users from the SAP ID service are identified by their e-mail address
and not their user ID. If you've multiple user accounts that share the same e-mail address, they all get the same authorizations.

Mapping Account Authorizations Between Feature Set A and Feature Set B

The following table lists the role collections for account administration that a user has in cloud management tools feature set B,
based on the role memberships the user had in cloud management tools feature set A.

Account Authorization Mappings Between Feature Set A and Feature Set B

Authorizations in Feature Set A Authorizations in Feature Set B More Information

Administrator of global account Global Account Administrator in global In cloud management tools feature set A,
account and Subaccount Administrator in members of the global account have global
multi-environment subaccounts account administrator privileges. Such
users can create and manage subscriptions
for subaccounts.

 Tip
To ensure that your global account
administrators still have these
authorizations, these users are also
assigned subaccount administrator
authorizations in all multi-environment
subaccounts of the global account. After
the move, consider if your global
account administrators really need
subaccount administrator access to all
your subaccounts.

Security administrator in multi- Subaccount Administrator in multi- Security administrators rely mostly on the
environment subaccount environment subaccount User & Role Administrator role for their
authorizations. In cloud management tools
feature set B, these authorizations are

This is custom documentation. For more information, please visit the SAP Help Portal 85
 10/15/24, 3:53 PM

Authorizations in Feature Set A Authorizations in Feature Set B More Information

bundled in the Subaccount Administrator

role collection.

Mapping Cloud Foundry Authorizations Between Feature Set A and Feature Set B
The following table lists the roles and role collections a user receives, based on the Cloud Foundry roles the user had in cloud
management tools feature set A.

Mappings of Cloud Foundry Authorizations Between Feature Set A and Feature Set B

Authorizations in Feature Set A Authorizations in Feature Set B More Information

Org Manager Org Manager In cloud management tools feature set A, a

user with the Org Manager, Space
Space Manager Space Manager
Manager, or Space Developer roles could
Space Developer Space Developer also manage cloud connectors and
destinations. To make sure that such users
don't lose any authorizations, we check the
 Note
users authorizations and add the required
If the user doesn't already have the
role collections.
Subaccount Administrator role
collection, the user receives the
Connectivity and Destination
Administrator role collection.

Org Auditor Org Auditor No change.

Space Auditor Space Auditor

Role Collection Names

Any role collection that you created in cloud management tools feature set A with a name that is a reserved role collection name in
cloud management tools feature set B, will have the suffix "(Custom)" appended to your role collection's name. For example,
Subaccount Administrator will be renamed to Subaccount Administrator (Custom) after the upgrade.

No Impact on Neo Subaccounts

The authorization model of Neo subaccounts remains the same in both feature sets.

Business Users
Business users use the applications that are deployed to SAP BTP. For example, the end users of SaaS apps or services, such as
SAP Workflow service or SAP Cloud Integration, or end users of your custom applications are business users.

Application developers (platform users) create and deploy application-specific security artifacts for business users, such as
scopes. Administrators use these artifacts to assign roles, build role collections, and assign these role collections to business users
or user groups. In this way, they control the users' permissions in the application.

For business users, there's a default identity provider, too. We expect that you have your own identity provider. We recommend that
you configure your custom tenant of SAP Cloud Identity Services as the identity provider and connect SAP Cloud Identity Services
to your own corporate identity provider.

This is custom documentation. For more information, please visit the SAP Help Portal 86
 10/15/24, 3:53 PM

User Management
User management refers to managing authentication and authorization for your business users.

To manage your business users:

1. Configure trust to an application identity provider in your subaccount.

2. Create shadow users in your subaccount for your business users in your identity provider.

When a user accesses a resource, SAP BTP redirects the user to the identity provider for authentication. You assign
authorizations to shadow users in SAP BTP.

3. Assign role collections either directly to users or map them to user groups.

The role collections were either delivered from the applications to which you subscribed or custom developed by your
team.

To learn more about user management, see Security Administration: Managing Authentication and Authorization.

Tools, Programming Models, Programming Languages, and APIs

SAP BTP provides various programming languages and tools for your development project.

Tools
SAP BTP includes many tools to help you develop and manage applications, and connect them to your on-premise systems.
Programming Languages
SAP BTP supports many different programming languages; the availability of each depends on the development
environment you're using.
Programming Models
Continuous Integration and Delivery (CI/CD)
Configure and run predefined continuous integration and delivery (CI/CD) pipelines that automatically build, test, and
deploy your code changes to speed up your development and delivery cycles.
APIs
Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP.
Cloud Management Tools — Feature Set Overview
Cloud management tools represent the group of technologies designed for managing SAP BTP.
Prerequisites and Restrictions
Find a list of the product prerequisites and restrictions for SAP BTP.

Tools
SAP BTP includes many tools to help you develop and manage applications, and connect them to your on-premise systems.

The availability of tools can depend on the cloud management tools feature set that you are running on. For more information, see
Cloud Management Tools — Feature Set Overview.

Tool Description

Account Administration in the Cockpit The SAP BTP cockpit is the web-based administration interface of
SAP BTP and provides access to a number of functions for

This is custom documentation. For more information, please visit the SAP Help Portal 87
 10/15/24, 3:53 PM

Tool Description

configuring and managing applications, services, and subaccounts.

Use the cockpit to manage resources, services, security, monitor
application metrics, and perform actions on cloud applications.

Cloud Connector The Cloud Connector serves as the link between on-demand
applications in SAP BTP. This is the browser-based and existing on-
premise systems. You can control the resources available for the
cloud applications in those systems.

Command Line Interface for Cloud Foundry The Cloud Foundry command line interface enables you to work
with the Cloud Foundry environment to deploy and manage your
applications.

SAP BTP Command Line Interface The SAP BTP command line interface (btp CLI) is the command
line tool for convenient account management, such as managing
global accounts, directories, subaccounts, entitlements,
environment instances, multitenant application subscriptions, and
users and their authorizations.

kubectl The Kubernetes command line tool to communicate with a

Kubernetes cluster's control plane, using the Kubernetes API.

kubelogin A kubectl plugin for Kubernetes OpenID Connect (OIDC)

authentication.

Helm The package manager for Kubernetes, used for installing and
managing Kubernetes applications in form of Helm charts.

ABAP RESTful Application Programming Model The programming model that defines the architecture for efficient
end-to-end development of intrinsically SAP HANA-optimized
OData services (such as SAP Fiori apps) in the ABAP environment.

SAP BTP SDK for iOS The SAP BTP SDK for iOS is based on the Apple Swift programming
language for developing apps in the Xcode IDE and includes well-
defined layers (SDK frameworks, components, and platform
services) that simplify development of enterprise-ready mobile
native iOS apps. The SDK is tightly integrated with SAP Mobile
Services for Development and Operations.

SAP BTP SDK for Android The SAP BTP SDK for Android provides development tools for
creating native Android mobile applications that use SAP Mobile
Services. The SDK is based on the Java programming language and
is built on top of Google's Android SDK.

SAP Cloud SDK SAP Cloud SDK provides a layer of abstractions for features of SAP
BTP such as logging, multitenancy, and connectivity. It also
includes project templates for different execution environments
and implementations.

Eclipse Tool for the Cloud Foundry Environment The Eclipse plug-in for the Cloud Foundry environment is a Java-
based toolkit for Eclipse IDE that enables you to develop and deploy
Java and Spring applications in the Cloud Foundry environment
from Eclipse or Spring Tool Suite, as well as perform operations
such as logging, managing user roles, creating connectivity
destinations, and so on.

SAP Business Application Studio SAP Business Application Studio is the next generation of SAP Web
IDE - Develop, debug, test, and deploy SAP business applications.

This is custom documentation. For more information, please visit the SAP Help Portal 88
 10/15/24, 3:53 PM

Tool Description

SAP Build SAP Build enables everyone, no matter the skill level, to create and
augment enterprise applications, process automations, and
business sites with drag-and-drop simplicity.

Service-Specific Tools The services that run on SAP BTP can come with service-specific
tools. For an overview of the services and their tools, see the SAP
Discovery Center .

Programming Languages
SAP BTP supports many different programming languages; the availability of each depends on the development environment
you're using.

The following programming languages are available in the environments:

Supported Environments and Programming Languages

Environment Programming Language

Cloud Foundry environment Java

Node.js

Python

ABAP environment ABAP

Kyma environment Serverless Functions: Node.js and Python

Microservices: Any cross-platform programming language

Programming Models

ABAP Cloud
ABAP Cloud reflects the modern way to develop ABAP. It allows you to build lifecycle-stable and cloud-ready business applications,
services, and extensions.

ABAP Cloud provides tools and techniques that ensure cloud qualities, promotes new technologies, contains a cloud-optimized
subset of the ABAP language, and makes upgrade cycles easier by a clear separation between custom code and SAP code by only
using released APIs and objects. See .

SAP Cloud Application Programming Model (CAP)

The SAP Cloud Application Programming Model (CAP) is a framework of languages, libraries, and tools for building enterprise-
grade services and applications. It supports Java (with Spring Boot), JavaScript, and TypeScript (with Node.js), which are some of
the most widely adopted languages. CAP guides developers along a path of proven best practices and a great wealth of out-of-the-
box solutions to recurring tasks.

CAP-based projects benefit from a primary focus on the domain. Instead of delving into overly technical disciplines, CAP focuses
on accelerated development and safeguarding investments in a world of rapidly changing cloud technologies.

This is custom documentation. For more information, please visit the SAP Help Portal 89
 10/15/24, 3:53 PM
Here are some of the benefits that come with the SAP Cloud Application Programming Model (CAP):

Built-in best practices

Support for Visual Studio Code and SAP Business Application Studio tools

Safeguarded application development investments

No runtimes lock-in

Reuse and integration of SAP BTP application services

Latest UX and themes

See .

Continuous Integration and Delivery (CI/CD)

Configure and run predefined continuous integration and delivery (CI/CD) pipelines that automatically build, test, and deploy your
code changes to speed up your development and delivery cycles.

 Note
For links to all SAP solutions for CI/CD, blog posts, presentations, and tutorials, have a look at our Continuous Integration and
Delivery by SAP overview.

Continuous integration (CI) describes a software development process, in which various team members integrate their
contributions frequently into a single main line. Before each integration, the changes are verified through builds and automated
testing. Thereby, you can detect errors as quickly as possible and prevent integration problems before completing the
development.

The continuous delivery (CD) concept expands on the one of continuous integration. It adds the aspect that any change that has
successfully passed the tests is immediately ready to be deployed to production, both from a technical and a qualitative point of
view.

The following graphic shows the basic flow for continuous integration and delivery:

This is custom documentation. For more information, please visit the SAP Help Portal 90
 10/15/24, 3:53 PM

Continuous Integration Basic Flow

For more information about the continuous integration and continuous delivery concepts, see What Are Continuous Integration
and Continuous Delivery?.

Use

Depending on your use case, you can choose between different CI/CD pipelines to help you implement continuous integration and
delivery in your software development.

SAP Continuous Integration and Delivery lets you configure and run predefined pipelines for the development of the following
applications:

SAP Cloud Application Programming Model

Configure a CI/CD pipeline for the development of applications that follow the SAP Cloud Application Programming Model
in the Cloud Foundry runtime.

Configure an SAP Fiori in the Cloud Foundry Environment

Configure a CI/CD pipeline for the development of SAPUI5/SAP Fiori applications in the Cloud Foundry runtime.

Configure an SAP Fiori in the Neo Environment

Configure a CI/CD pipeline for the development of SAPUI5/SAP Fiori applications in the Neo environment.

Configure an SAP Fiori for the ABAP Platform

This is custom documentation. For more information, please visit the SAP Help Portal 91
 10/15/24, 3:53 PM
Configure a CI/CD pipeline for the development of SAPUI5/SAP Fiori applications for the ABAP platform.

Configure an SAP Integration Suite ArtifactsSAP Integration Suite Artifacts

Configure a CI/CD pipeline for the development of SAP Cloud Integration artifacts in the Cloud Foundry runtime.

Configure a Container-Based Applications

Configure a CI/CD pipeline for the development of container-based applications.

To learn more about the CI/CD pipelines supported by SAP Continuous Integration and Delivery and the stages each pipeline can
comprise, see Supported Pipelines.

Get Started with CI/CD

SAP Continuous Integration and Delivery provides an easy, UI-guided way to set up the service and configure and run your
pipelines, without hosting your own Jenkins instance.

To set up SAP Continuous Integration and Delivery:

1. Enable the service in the SAP BTP cockpit.

2. Assign either the Administrator or Developer role to your user.

3. Enable the API usage to connect SAP Continuous Integration and Delivery to other services, if necessary.

To configure SAP Continuous Integration and Delivery:

 Note
Only administrators of SAP Continuous Integration and Delivery can configure the service.

1. Configure credentials for connecting SAP Continuous Integration and Delivery to other services (for example, GitHub,
GitLab, Bitbucket Server, or Azure Repos to clone your sources, and SAP BTP to deploy your built application).

2. Add your repository.

Now you can create and modify your CI/CD jobs and monitor their outcome. If you want to automate your builds, you can
configure a webhook between your repository and the service. You can create and modify timed triggers for your jobs, if necessary.

For more information, see Initial Setup and Configuration, or follow the tutorial Configure and Run a Predefined SAP Continuous
Integration and Delivery (CI/CD) Pipeline .

Learn and Get Certified

Depending on your learning goals and level of expertise, you can choose from the following offerings:

Efficient DevOps with SAP

This openSAP course introduces general DevOps approaches and key principles. Learn about the basic CI/CD principles
(week 1) and how to deliver cloud applications using CI/CD (week 3).

Continuous Integration and Delivery Introduction Guide

The CI/CD Introduction Guide provides you with basic knowledge for setting up and implementing continuous integration
and delivery processes. It gives an overview of the concepts and principles of CI/CD, explains both procedures and their
relation, and helps you plan your own CI/CD process.

This is custom documentation. For more information, please visit the SAP Help Portal 92
 10/15/24, 3:53 PM

APIs
Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP.

An Application Programming Interface or API is an interface provided by an application for interacting with other applications.
APIs specify how software programs are able to exchange information with each other, even if designed and run by different
organizations. They facilitate interaction by selectively exposing certain functionality, allowing different apps, websites, and
devices to communicate effectively with each other. More importantly, APIs enable businesses to reach beyond regular business
channels and share data, content, and services directly to both B2B (business to business) and B2C (business to consumer)
clients, making UI development easy.

API Offerings on SAP BTP

SAP BTP enables you to consume APIs and publish your own ones through the following offerings:

Offering Description

SAP BTP on SAP Business Accelerator Hub The SAP Business Accelerator Hub provides you with one central
repository for browsing and accessing APIs from SAP and selected
partners. Test APIs and try out mock data in your systems.

It is also the official place where REST and OData REST API
references are published.

API Management Capability within SAP Integration Suite With the API Management capability, you can build, manage,
publish, and monetize your own APIs within one secure and
scalable environment.

Software Development Kits (SDKs) The SDKs available for SAP BTP offer APIs to, for example,
accelerate enterprise app development.
For an overview of the available SDKs, see Tools.

Related Information
SAP API Style Guide

Cloud Management Tools — Feature Set Overview

Cloud management tools represent the group of technologies designed for managing SAP BTP.

We're currently renovating and adding core functionalities to SAP BTP. As part of this process, we're upgrading enterprise
accounts from the existing cloud management tools feature set A to the renovated cloud management tools feature set B. We're
doing this upgrade as a phased rollout, so cloud management tools feature sets A and B will coexist for some time. For more
information about the account upgrade process and frequently-asked questions, see 3027721 .

How can I know which cloud management tools feature set I'm using?
There’s an easy way to check if you're currently using cloud management tools feature set A or B. Access the SAP BTP cockpit and
choose your username from the top right-hand corner of the screen. From the menu, select  About to get information about the
cloud management tools feature set you're using.

This is custom documentation. For more information, please visit the SAP Help Portal 93
 10/15/24, 3:53 PM

Access the SAP BTP cockpit

Feature sets A and B don't share the same cockpit. So in your feature set A cockpit, you'll only see feature set A global accounts,
while in your feature set B cockpit, you'll only see your feature set B global accounts.

When using cloud management tools feature set A: Choose https://account.eu1.hana.ondemand.com to access the SAP BTP
cockpit.

When using cloud management tools feature set B: Choose https://cockpit.btp.cloud.sap to access the cockpit. Depending on
your own geo location this URL will redirect you to the closest regional Cockpit URL.

For more information, see Access the Cockpit.

What are the differences between the two cloud management tools feature sets?

New/Changed Features and Feature Set A Feature Set B

Behaviors

Directories — NEW Not applicable Summary:

Group and filter directories and subaccounts

Monitor usage and costs for contracts that use

the consumption-based commercial model

With directories, you can organize and manage your

subaccounts according to your technical and business
needs.

A directory can contain directories and subaccounts

to create a hierarchy. Using directories to group other
directories and subaccounts is optional - you can still
create subaccounts directly under your global
account.

See:

Directories

Create a Directory

This is custom documentation. For more information, please visit the SAP Help Portal 94
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

Manage the Account Explorer Hierarchy

Labels — NEW Not applicable Summary:

Set labels for categorization and identification
purposes

Additional filtering options

Labels allow you to categorize your directories,

subaccounts, multitenant application subscriptions,
service instances, and environment instances so that
you identify them more easily within your global
account. For example, the Account Explorer and
Instances and Subscriptions pages in the cockpit
allow you search by label name or value.

Labels are user-defined so you can apply them as you

wish according to your own business and technical
needs.

You can manage labels for the supported entities

using the SAP BTP cockpit, command line interface
(btp CLI), or REST APIs.

See Labels.

APIs for SAP BTP — NEW Not applicable Summary:

Discover and consume REST APIs to manage, build,
and extend the cloud operation capabilities of SAP
BTP. For example:

Manage global accounts, directories, and

subaccounts

Assign entitlements for services and

applications to directories and subaccounts

Manage the provisioning of environment

instances and get information relating to
provisioned services

Manage subaccount subscriptions to

multitenant applications

Generate reports based on the resource and

cost consumption within your accounts.

See Account Administration Using APIs of the SAP

Cloud Management Service and Monitoring Usage
Information Using APIs of the SAP Usage Data
Management Service [Feature Set B].

SAP BTP command line interface Not applicable Summary:

(btp CLI) — NEW Use the btp CLI for convenient account management
tasks on the command line and to automate these
procedures. For example:

Manage global accounts, directories, and

subaccounts

Set entitlements

This is custom documentation. For more information, please visit the SAP Help Portal 95
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

Work with environments

Work with multitenant applications

Manage users and their authorizations

To log in to a global account, you need the CLI server

URL
https://cpcli.cf.eu10.hana.ondemand.com
and the global account subdomain. Only global
accounts on feature set B have global account
subdomains (see cockpit).

See:

Account Administration Using the SAP BTP Command

Line Interface (btp CLI)

btp CLI Command Reference

Setting Up a Global Account via the Command Line

Global account navigation — Summary: Summary:

CHANGED "Home" scope outside the Global accounts selection dialog displayed
global account in the cockpit before entering the cockpit

Global Accounts page in the Option to set a default global account

cockpit
"Home" scope removed from the cockpit
Switching between global
Switching between global accounts via the
accounts via breadcrumbs
selection dialog or breadcrumbs (first
(second element)
element)
Overview page is the first in the
Subaccounts page is the first in the global
global account scope
account scope
With feature set A, your cockpit
With feature set B, there's no scope beyond the global
contains a number of general views
account in the cockpit anymore. Therefore, after
outside of the global account scope.
logging on to the cockpit and before actually entering
These include a Global Accounts page,
it, if you have more than one global account, you're
where you can find all your global
asked to choose which of the available cloud
accounts listed as tiles, and from where
management tools feature set B global accounts you
you can navigate to your desired global
want to enter. Only feature set B global accounts are
account.
visible here. This is done via a global account selection
Since it has several views outside of the dialog, where you also have the option to remember
global account scope, your cockpit your selection. Doing that sets the global account you
contains an additional "home" scope, chose as default, so that next time you access the
which is represented by the first cockpit you’re automatically taken to your default
element in the breadcrumbs. Your global account instead of seeing the selection dialog.
global account is therefore represented
As the cockpit doesn't have a "home" scope anymore,
by the second element in the
the global account becomes the outermost scope and
breadcrumbs. You can also use that
is therefore represented by the first element in the
second element to navigate from one
breadcrumbs. You can still navigate from one global
global account to another.
account to another either by using the breadcrumbs,
Once you're in a global account, the or by choosing Switch Global Accounts to launch the
first page you see is the global account global account selection dialog, where you can also
overview page. To navigate to a modify or remove your default global account.
subaccount, you have to navigate to

This is custom documentation. For more information, please visit the SAP Help Portal 96
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

the Subaccounts page from the left Once you're in a global account, the first page you see
hand-side navigation. is the Subaccounts page, from where you can directly
navigate to your subaccount — one less click needed.
See Navigate in the Cockpit
Usage and cost information for your global account is
displayed in the global account's Usage Analytics
page.

See Navigate in the Cockpit.

Entitlements — CHANGED Summary: Summary:

Only manage entitlements for Manage entitlements for both services and
services multitenant applications

Assign entitlements to Assign entitlements to subaccounts

subaccounts individually individually

Service Assignments view Assign entitlements to directories

With feature set A, entitlements only Auto-assign entitlements to all new

apply to services and you have two subaccounts in a directory
views for them: Subaccount
One single view for your entitlements, no
Assignments, where you can assign or
Service Assignments page
edit entitlements to individual
subaccounts, and Service With feature set B, you manage entitlements for both
Assignments, which is a read-only view services and multitenant applications. Since you have
displaying the distribution of your directories as a way to group your subaccounts, you
available services across subaccounts. can also assign entitlements to a directory and choose
the option to automatically assign a certain amount of
See:
quota to each subaccount added to that directory in
Entitlements and Quotas the future (as long as it doesn't exceed the quota of
that directory).
Managing Entitlements and Quotas
Using the Cockpit This means that you can more efficiently assign quota
to multiple subaccounts that should have the same
Configure Entitlements and Quotas for
entitlements.
Subaccounts
In addition, you no longer have the Service
Assignments view with feature set B.

See:

Entitlements and Quotas

Managing Entitlements and Quotas Using the Cockpit

Configure Entitlements and Quotas for Directories

Subscribe to Multitenant Applications Using the

Cockpit

Global account security — Summary: Summary:

CHANGED
Global account membership Global account membership is determined by
determines if a user is global the assignment of a role collection.
account administrator or not.
Predefined role collections for global accounts
Members of subaccounts have define full and read-only access.
view-only access to their global
You can define your own role collections with
accounts.
the authorizations delivered by SAP.

This is custom documentation. For more information, please visit the SAP Help Portal 97
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

With feature set A, the Members tab With feature set B, you have a fine-grained
determines which users are global authorization concept for the management of global
administrators. These users can assign accounts. We deliver a set of role collections for the
or remove global administrator management of global accounts. If these role
membership to other users. collections don’t match your needs, you can configure
your own role collections using the authorizations we
See:
supply. For example, you have control over which
User and Member Management global account users can create subaccounts and
which can’t.
Add Members to Your Global Account
The Authorization and Trust Management (XSUAA)
Impact of Upgrading from Feature Set service is responsible for access management for
A to Feature Set B on User and Account global accounts. This service is the same service that
Management performs access management at the subaccount
level, although it’s a different instance of the service.

In the cockpit, a new Security tab provides access to

management functions for role collections and user
assignment.

With feature set B, global account users are identified

by their e-mail address and not their user ID.

See:

User and Member Management

Role Collections and Roles in Global Accounts,

Directories, and Subaccounts

Default Role Collections of SAP BTP

Subaccount security — CHANGED Summary: Summary:

Subaccount administrators are Subaccount administrators and members are

determined by assignment determined by the assignment of role
under security administrators. collections.

Subaccount members are Predefined role collections for subaccounts

determined by assignment of define the level of access.
roles in the Cloud Foundry org
Provision subaccount members with SCIM
under the Members tab.
APIs
With feature set A, you define
Membership in subaccounts and any
administrators in the cockpit under the
environments, such as the Cloud Foundry org,
Security tab with the Administrators
are controlled by separate authorizations.
menu item.
With feature set B, you have a fine-grained
See:
authorization concept for the management of
User and Member Management subaccounts. We deliver a set of role collections for
the management of subaccounts. If these role
Impact of Upgrading from Feature Set
collections don’t match your needs, you can configure
A to Feature Set B on User and Account
your own role collections using the authorizations we
Management
supply.

Access to environments, such as a Cloud Foundry org,

is semi-independent from subaccount membership. A
subaccount member isn't necessarily a member of an
environment, but a member of an environment is a
member of its subaccount.
This is custom documentation. For more information, please visit the SAP Help Portal 98
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

See:

User and Member Management

Role Collections and Roles in Global Accounts,

Directories, and Subaccounts

Add Members to Your Subaccount

Default Role Collections of SAP BTP

Custom Identity Provider for Summary: Summary:

Platform Users — CHANGED
Custom identity providers enable you Custom identity providers enable you to integrate
to integrate platform and business platform and business users from SAP Cloud Identity
users from SAP Cloud Identity Services Services - Identity Authentication or your own
- Identity Authentication or your own corporate identity provider.
corporate identity provider.
See: Trust and Federation with Identity Providers
See: Trust and Federation with Identity
Restrictions When Using Custom Identity Providers for
Providers
Platform Users
Impact of Upgrading from Feature Set
A to Feature Set B on User and Account
Management

(Trial Only) Automatic Setup of Trial Not applicable Summary:

Account — CHANGED Your trial account is automatically set up for
you after you choose Enter Your Trial Account
from the trial homepage in the cockpit for the
first time.

You get a global account with a subaccount

called trial, which in turn contains an org and a
space called dev.

All entitlements are assigned to the

subaccount that is provisioned automatically.

With feature set B, you can access the trial homepage

in the cockpit before your trial account is set up and
ready to use. This means that you can launch a starter
scenario or guided tour before you have the global
account, subaccount, org, space and entitlements in
place. You trigger the automatic creation when you
first choose Enter Your Trial Account from the trial
homepage.

(Trial Only) Trial Account Extension - Not applicable Summary:

CHANGED You cannot access a suspended trial global
account.

You can still see the counter with the

remaining number of days in the same place,
but you cannot extend your trial from there.

You extend your trial account from a dialog

similar to the global account selection dialog
described previously in this table under global
account navigation.

This is custom documentation. For more information, please visit the SAP Help Portal 99
 10/15/24, 3:53 PM

New/Changed Features and Feature Set A Feature Set B

Behaviors

With feature set B, it's not possible anymore to access

suspended trial global accounts. Before your trial
interval expires, you can still see the counter with the
remaining number of days in the same place. However,
once your trial interval expires and you try to access it,
you will instead be prompted by a dialog asking you to
extend your trial first.

 Note
The overall trial period is 90 days and is divided in
intervals.

If you don't log in to your account for 30 days or

more, your account will be suspended. During
suspension, your applications may be stopped and
you won't be able to access them. However, your
data will not be deleted yet. You can unsuspend
your account as long as there are days left in your
trial period.

When your 90-day trial period is finished, your

account will be deleted, and you will no longer be
able to access your data. You can then set up a new
trial account.

(Trial Only) Deletion of SAP BTP Trial Not applicable Summary:

- NEW Possible to easily delete only your SAP BTP
trial account.

With feature set B, you can delete your SAP BTP trial
account. Simply navigate into your trial global account
by choosing Enter Your Trial Account on the trial
home page. Once you're on the Subaccounts page of
your global account, you will see a new button giving
you the option to delete your trial account.

 Note
Cloud management tools feature set B applies also to the Neo environment. For more information about the scope offered with
the enhanced capabilities, see Working with Cloud Management Tools Feature Set B in the Neo Environment.

Prerequisites and Restrictions

Find a list of the product prerequisites and restrictions for SAP BTP.

General Constraints
For information on constraints and default settings to consider when you deploy an application in the Cloud Foundry
environment, see http://docs.cloudfoundry.org/devguide/deploy-apps/large-app-deploy.html#limits_table .

SAP BTP exposes applications only via HTTPS. For security reasons, applications can’t be accessed via HTTP.

SAP BTP Tools

This is custom documentation. For more information, please visit the SAP Help Portal 100
 10/15/24, 3:53 PM
SAP BTP Tools for Java and SDK have been tested with Java 7, and Java 8.

SAP BTP Tools for Java and SDK run in many operating environments with Java 7, and Java 8 that are supported by Eclipse.
However, SAP doesn’t systematically test all platforms.

SAP BTP Tools for Java must be installed on Eclipse IDE for Java EE developers.

For the platform development tools, SDK, Cloud connector, and SAP JVM, see https://tools.hana.ondemand.com/#cloud .

Browser Support

For a list of supported browsers for the SAP BTP cockpit, see Feature Scope Description.

For a list of supported browsers for developing SAPUI5 applications, see Browser and Platform Support.

To find out the browser support for a specific service, refer to the corresponding feature scope description.

For security reasons, SAP BTP doesn’t support TLS1.1 and older, SSL 3.0 and older, and RC4-based cipher suites. Make sure that
your browser supports at least TLS1.2 and modern ciphers (for example, AES).

Getting Started
Once you're familiar with the basic concepts of SAP BTP, you can start your first workflows or check out further resources that
help you get started quickly.

Onboarding Guide
The guide Best Practices for SAP BTP helps you plan your development projects on SAP BTP from setting up the correct
organizational structure to creating an account and security model, to developing and operating applications.

Getting Started Workflows

Learn how to get a global account and get started with a trial or an enterprise account on SAP BTP. A trial account lets you try out
SAP BTP for free, and within an enterprise account, you can use so-called free tier service plans for free. See Trial Accounts and
Free Tier.

Depending on your use case, follow the appropriate workflow:

Getting a Global Account

Getting Started in the Cloud Foundry Environment

Getting Started in the ABAP Environment

Getting Started in the Kyma Environment

Additional Resources
The SAP Developer Center provides further resources to get you started:

SAP Discovery Center

SAP BTP in SAP Developer Center

Start Developing on SAP BTP Tutorials

This is custom documentation. For more information, please visit the SAP Help Portal 101
 10/15/24, 3:53 PM

Related Information
SAP BTP Administrator's Guide
Access the Cockpit

This is custom documentation. For more information, please visit the SAP Help Portal 102