6/11/25, 2:37 PM

SAP Business Technology Platform

Generated on: 2025-06-11 14:37:53 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 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 SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

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

This is custom documentation. For more information, please visit SAP Help Portal. 1
 6/11/25, 2:37 PM

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 Guides
The SAP BTP Administrator's Guide helps you plan your development projects on SAP BTP from onboarding to SAP Cloud Identity
Services, through setting up the correct organizational structure, to creating an account and security model, to developing and
operating applications.

The SAP BTP Developer’s Guide helps you define the correct methodologies and tools for your development project.

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

Related Information
SAP BTP Administrator's Guide
SAP BTP Developer's Guide
Access the Cockpit

Getting a Global Account

SAP BTP offers two types of global accounts: Trial accounts (completely free of charge) and enterprise accounts. Within an
enterprise account, you can use both free and paid plans.

This is custom documentation. For more information, please visit SAP Help Portal. 2
 6/11/25, 2:37 PM
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

Trial Accounts and Free Tier

Enterprise Accounts

Try Out SAP BTP for Free

Get an Enterprise Account

Try Out SAP BTP for Free

There are two ways to try out SAP BTP services and applications for free.

Context

A free trial account is intended for individuals, for example students, who want to explore SAP BTP for free. It is an isolated
account and subaccount, with preallocated service entitlements that can be used for a limited number of days.

Free tier is not an account type, but it's a set of free services that can be used within an enterprise account.

To learn which is best for your needs, see the Set Up an SAP BTP Account for Tutorials group in the SAP Developer Center.

Get an Enterprise Account

To use an enterprise account, you can either purchase a customer account, join the partner program to purchase a partner
account, or self-register for an enterprise account to try out free tier service plans.

For more information about the scope of our enterprise offering, see Enterprise Accounts. For more information about free tier
within an enterprise account, see Trial Accounts and Free Tier and Using Free Service Plans.

Related Information
Get an Account on SAP BTP to Try Out Free Tier Service Plans

Sign up for a Customer Account

A customer account is an enterprise account that allows you to host productive, business-critical applications with 24x7 support.

When you want to purchase a customer account, you can select from a set of predefined packages. For information about service
availability, prices, and estimators, seehttps://www.sap.com/products/technology-platform/pricing.html . You can also view the
service catalog via the SAP Discovery Center . Contact us on SAP BTP or via an SAP sales representative.

Free Tier

If you want to try out services for free, with the option of easily upgrading them later, you can get an enterprise account and use
free tier service plans only. See Get an Account on SAP BTP to Try Out Free Tier Service Plans . When you sign up for a global
account to try out free tier service plans, you need to select either an existing global account of your company, or create a new

This is custom documentation. For more information, please visit SAP Help Portal. 3
 6/11/25, 2:37 PM
global account. If you choose an existing global account, make sure to contact the global account admin of this global account, as
they'll receive the communication emails. In this case, we recommend to have them add you as Global Account Administrator. See
Assign Users to Role Collections and SAP BTP Onboarding Resource Center .

You can upgrade and refine your resources later on. You can also contact your SAP sales representative and opt for a configuration,
tailored to your needs.

Onboarding

After you have purchased a new customer account, you will receive an email confirming the provisioning of resources from the
platform services team and a second email with the URL and login ID to obtain access. Note, only the person who receives the
access email has initial access to SAP BTP.

If you chose an add-on to an existing global account, the initial access email will not be sent to you. You will need to contact the
Global Account Administrator from the initial BTP order. If you’re unsure who this person is, please contact your SAP Sales
representative. If you need to add a new global admin because the person with initial access is no longer available to grant you
access, then you can contact the SAP Support Portal, by creating a ticket at component BC-NEO-CIS-OPS.

 Tip
Check out the Live Onboarding Webinars .

Getting a Customer Account in China

If you are 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 .

Related Information
Commercial Models
Using Free Service Plans
Access the Cockpit

Join the Partner Program

A partner account is an enterprise account that enables you to build applications and to sell them to your customers.

To become a partner, you need to fill in an application form and then sign your partner contract. You will be assigned to a partner
account with the respective resources. To apply for the partner program, visit
https://partneredge.sap.com/content/partnerregistration/en_us/registration.html?
partnertype=BLD&engagement=0002&build=1 . You will receive a welcome mail with further information afterwards.

General information about the partner program is available onhttps://www.sap.com/partners/partner-program.html .

Next Steps

Getting Started in the Cloud Foundry Environment

Getting Started in the ABAP Environment

Getting Started in the Kyma Environment

Getting Started in the Cloud Foundry Environment

This is custom documentation. For more information, please visit SAP Help Portal. 4
 6/11/25, 2:37 PM
Get onboarded in the Cloud Foundry environment of SAP BTP. Follow the workflows for trial or customer accounts or subscribe to
business applications.

Getting Started with a Trial Account in the Cloud Foundry Environment

Quickly get started with a trial account.
Getting Started with an Enterprise Account in the Cloud Foundry Environment
Quickly get started with an enterprise account in the Cloud Foundry Environment.

Getting Started with a Trial Account in the Cloud Foundry

Environment
Quickly get started with a trial account.

1. Getting a Global Account

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

Before you begin, sign up for a free trial account. See Get a Free Trial Account. For more information about the scope of our trial
offering, see Trial Accounts and Free Tier.

If you want to familiarize yourself with the Cloud Foundry environment, see Cloud Foundry Environment.

2. Setting Up Your Account Model

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 5
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. When you register for a trial account, a subaccount and a space are created for you. You can create additional subaccounts
and spaces, thereby further breaking down your account model and structuring it according to your development scenario,
but first it's important you understand how to navigate to your accounts and spaces using the SAP BTP cockpit. See
Navigate to Orgs and Spaces.

2. If you like, create further subaccounts. See Create a Subaccount. You can also download and use the CLI forSAP BTP to
create new subaccounts. See Download and Start Using the btp CLI Client and Working with Global Accounts, Directories,
and Subaccounts Using the btp CLI.

3. If you haven't done so already, now is a good time to download and install the Cloud Foundry Command Line Interface (cf
CLI). This tool allows you to administer and configure your environment,enable services, and deploy applications. See
Download and Install the Cloud Foundry Command Line Interface. But don't worry, you can also perform all the necessary
task using the SAP BTP cockpit, which you don't need to install.

4. If you'd like to use the cf CLI, log on to your environment. See Log On to the Cloud Foundry Environment Using the Cloud
Foundry Command Line Interface.

5. If you like, create further spaces. See Create Spaces. If you want to learn more about subaccounts, orgs, and spaces, and
how they relate to each other, see Account Model.

3. Configuring Your Environment

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 6
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. Now that you've set up your account model, it's time to think about member management. You can add members at
different levels. For example, you can add members at the org level. See Add Org Members. For more information about the
roles that are available on the different levels, see User and Member Management.

2. You can also add members at the space level. See Add Space Members.

3. In a trial account, quotas are automatically assigned to your subaccounts, but you can change that assignment. See
Configure Entitlements and Quotas for Subaccounts. To learn more about entitlements and quotas, see Entitlements and
Quotas.

4. You can also assign quotas to different spaces within a subaccount. To do so, first create a space quota plan. See Create
Space Quotas or Create Space Quota Plans Using the Cloud Foundry Command Line Interface.

5. Then assign the quota plan to your space. See Assign Space Quotas to Spaces or Assign Quota Plans to Spaces Using the
Cloud Foundry Command Line Interface.

4. Developing and Deploying Applications

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 7
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. Develop your application. Check out the Developer Guide for tutorials and more information. See Development.

2. Deploy your application. See Deploy Business Applications in the Cloud Foundry Environment.

3. Integrate your application with a service. To do so, first create a service instance. See Creating Service Instances.

4. Bind the service instance to your application. See Binding Service Instances to Applications.

5. Alternatively, you can also create and use service keys. See Creating Service Keys. For more information on using services
and creating service keys, see About Services.

6. You can also create instances of user-provided services. See Creating User-Provided Service Instances.

 Tip
Also check out the tutorial Create Your First App on Cloud Foundry to see how you can deploy a pre-bundled set of artifacts
using the SAP BTP cockpit, access the app from your web browser, and create an instance of a service available on Cloud
Foundry and bind it to your app.

Related Information
Cloud Foundry Environment
Trial Accounts and Free Tier
Account Model
Entitlements and Quotas
User and Member Management
About Services

This is custom documentation. For more information, please visit SAP Help Portal. 8
 6/11/25, 2:37 PM

Setting Up Your Trial Account

Your trial account is set up automatically, so that you can start using it right away. However, if one or more of the automatic steps
fail, you can also finalize the setup manually, by following the steps below.

Create Your Trial Subaccount

The first thing that is needed in the setup of your trial account is the creation of a subaccount. If this step was successful in the
SAP BTP cockpit, you can directly skip to the next section.

Procedure
1. Navigate into your global account by choosing Enter Your Trial Account.

2. Choose New Subaccount.

3. Configure it as follows:

Field Input

Display Name trial

Description (Optional) Any text that describes your subaccount

Provider Desired infrastructure provider

Region Desired region

Subdomain <your_id>trial

Example: P0123456789trial

[Advanced] Enable beta features (Optional) Enables the use of beta services and applications.

[Advanced] Labels (Optional) You can assign labels to help identify and organize
the subaccounts in your global account. For example, you can
filter subaccounts by custom property in the Account Explorer
page. See Labels.

Results

You have successfully set up your trial subaccount.

Create Your Trial Org and Configure Entitlements

Once you have a subaccount (whether it was created automatically or you followed the steps described above), you need an org
and entitlements.

Procedure
1. Navigate to your subaccount by choosing its tile.

2. Choose Enable Cloud Foundry to create your org.

This is custom documentation. For more information, please visit SAP Help Portal. 9
 6/11/25, 2:37 PM
3. Once your org is created, choose Entitlements from the left hand-side navigation.

4. Choose Configure Entitlements to enter edit mode.

5. Choose Add Service Plans and select all the service plans available for your subaccount.

 Note
To select a service plan, choose a service from the left and tick all the service plans that appear on the right. Do that for
all services.

6. Once you've added all the service plans, you see them all in a table. Before you choose Save, for all the plans with numerical
quota, choose  to increase the amount to the maximum (until the icon becomes disabled).

7. Finally, choose Save to save all your changes and exit edit mode.

Results
You now have an org and all the entitlements for your subaccount. The last thing you need is a space where you can use the
services you've configured entitlements for and deploy applications.

Create Your Trial Space

Procedure
1. In your trial subaccount, navigate to Cloud Foundry Spaces using the left hand-side navigation.

2. Choose Create Space and name it dev.

3. Choose Create.

Results
You now have your trial set up all done and ready to go.

To get some guidance on how you can get started, navigate back to your Trial Home by choosing the first item in your breadcrumbs
at the top. There, you can find several guided tours to walk you through the basics of SAP Business Technology Platform and the
cockpit, as well as some more complex starter scenarios.

Setting Up a Trial Account From the Command Line

You can use the command-line interface to set up a trial account. For all tasks on global account and subaccount levels, you use
the SAP BTP command-line interface (btp CLI). Once you’ve created a Cloud Foundry environment instance (a Cloud Foundry
org), you use the Cloud Foundry CLI (cf CLI). This procedure works without the SAP BTP cockpit (except that you need the global
account subdomain to log in, which you may have to look up in the cockpit).

For all tasks on global account and subaccount level, you can use the the btp CLI instead of the SAP BTP cockpit. Once you’ve
created a Cloud Foundry environment instance (a Cloud Foundry org), use the Cloud Foundry CLI (cf CLI).

Prerequisites
You have created a trial account.

You have downloaded and extracted the following command-line tools:

SAP BTP command-line interface (btp CLI). See Download and Start Using the btp CLI Client

This is custom documentation. For more information, please visit SAP Help Portal. 10
 6/11/25, 2:37 PM
Cloud Foundry CLI (cf CLI). See Download and Install the Cloud Foundry Command Line Interface

Procedure

 Tip
In the btp CLI, you can view the command help of each command to get information about how to use the command, its syntax,
and input parameters. See Get Help.

Step No. Task Performed Do This More Information

By

1. Log in to your global account using Global Run this command in the btp CLI: See Log in.
the subdomain of your global account btp login
account. administrator
or viewer

2. View details of your global account. Global Run this command in the btp CLI: See Working with
account btp get accounts/global- Global Accounts,
admin or account Directories, and
viewer Subaccounts Using the
btp CLI.

4. View all the regions that are available Global Run this command in the btp CLI: This command also
to your global account and account btp list accounts/available- provides information
subaccounts. admin or region about the
viewer environments and
infrastructure provider
of each region.

5. Create subaccounts in your global Global Run this command in the btp CLI: See Working with
account. account btp create Global Accounts,
admin accounts/subaccount -- Directories, and
display-name <my-subaccount> Subaccounts Using the
--region <my-region> -- btp CLI and Account
subdomain <my-subaccount- Model.
subdomain>

6. View the details of the subaccounts in Global Run this command in the btp CLI: See Working with
your global account. account btp get accounts/subaccount Global Accounts,
admin or <ID of new subaccount> Directories, and
viewer Subaccounts Using the
btp CLI.

7. Add admins to your subaccounts. Subaccount Assign the role collection Subaccount See Managing Users
admin Administrator to the user by running and Their
the following command in the btp CLI: Authorizations Using
the btp CLI and
btp assign security/role-
Security
collection "Subaccount
Administration:
Administrator" --to-user
Managing
<user> --create-user-if- Authentication and
missing
Authorization.

8. View all the services and applications Global Run this command in the btp CLI: See Setting
that are entitled to your global account btp list accounts/entitlement Entitlements Using the
account, including quota information admin or btp CLI.
per service plan. viewer

This is custom documentation. For more information, please visit SAP Help Portal. 11
 6/11/25, 2:37 PM

Step No. Task Performed Do This More Information

By

9. Assign quotas to your subaccounts. Global Run this command in the btp CLI: See Setting
account btp assign Entitlements Using the
admin accounts/entitlement --to- btp CLI.
subaccount <my-subaccount-id>
--for-service <my-service> --
plan <my-service-plan> --
amount <number>

Validate with this command:

btp list accounts/entitlement

10. View all the entitlements in your Subaccount Run this command in the btp CLI: See Setting
subaccounts. admin or btp list accounts/entitlement Entitlements Using the
viewer --subaccount <my-subaccount- btp CLI.
id>

11. Create a Cloud Foundry org Subaccount Run this command in the btp CLI: See Working with
(environment instance) in your admin btp create Environments Using
subaccounts. accounts/environment-instance the btp CLI.
--subaccount <my-subaccount-
id> --display-name <my-
environment> --environment
<cloudfoundry>

12. View details of the environment Subaccount Run this command in the btp CLI: See Working with
instances in your subaccounts. admin or btp list Environments Using
viewer accounts/environment-instance the btp CLI.
--subaccount <my-subaccount-
id>

13. Create a Cloud Foundry space. Org manager Run these cf CLI commands: See Create Spaces
Using the Cloud
cf login
Foundry Command

cf create-space Line Interface.

14. Add Cloud Foundry org and space Org manager Run these cf CLI commands: See Add Organization
members. cf set-org-role <USERNAME> Members Using the
<ORG> <ROLE> Cloud Foundry
Command Line
cf set-space-role <USERNAME>
Interface and Add
<ORG><SPACE><ROLE>
Space Members Using
the Cloud Foundry
Command Line
Interface.

15. Display all available services in the Org manager Run this cf CLI command: See Using Services in
Cloud Foundry marketplace. the Cloud Foundry
cf marketplace Environment.

Using the btp CLI, you can perform account maintenance tasks, such as updating global account and subaccount details, deleting
subaccounts, and deleting environment instances.

Subaccount members can also use the btp CLI to work with multitenant applications. See Working with Multitenant Applications
Using the btp CLI.

This is custom documentation. For more information, please visit SAP Help Portal. 12
 6/11/25, 2:37 PM

Next Steps

Org/space members can create service instances, which are entitled to the subaccount, using also the cf create-service
<allowed-service-plan> command in the cf CLI. Use the cf CLI command cf services to verify that the service instances
exist.

For more information about developer tasks, see Development in the Cloud Foundry Environment.

Related Information
Command Syntax of the btp CLI
Download and Start Using the btp CLI Client
Commands in the btp CLI

Getting Started with an Enterprise Account in the Cloud Foundry

Environment
Quickly get started with an enterprise account in the Cloud Foundry Environment.

This topic focuses on how to get started with a customer or partner account using the SAP BTP cockpit. However, you can also
perform these tasks using the CLI. See Setting Up a Global Account via the Command Line.

1. Setting Up Your Account Model

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

1. After you've received your logon data by email, create subaccounts in your global account. This allows you to further break
down your account model and structure it according to your business needs. See Create a Subaccount.

2. If you haven't done so already, now is a good time to download and install the Cloud Foundry Command Line Interface (cf
CLI). This tool allows you to administer and configure your environment, enable services, and deploy applications. See

This is custom documentation. For more information, please visit SAP Help Portal. 13
 6/11/25, 2:37 PM
Download and Install the Cloud Foundry Command Line Interface. But don't worry, you can also perform all the necessary
task using the SAP BTP cockpit, which you don't need to install.

3. If you'd like to use the cf CLI, log on to your environment. See Log On to the Cloud Foundry Environment Using the Cloud
Foundry Command Line Interface.

4. Create a Cloud Foundry organization in each of your subaccounts. See Create Orgs

5. Create spaces. See Create Spaces.

2. Configuring Your Environment

1. You can either use the cockpit or the cf CLI to configure your environment. If you'd like to use the cockpit, it's important you
understand how you can navigate to your accounts and spaces. See Navigate to Orgs and Spaces.

2. It's time to think about member management. You can add members at different levels. For example, you can add members
at an org level. See Add Org Members. For more information about roles, see User and Member Management.

3. You can also add members at a space level. See Add Space Members.

4. Before you can start using resources such as services or application runtimes, you need to manage your entitlements and
add quotas to your subaccounts. See Configure Entitlements and Quotas for Subaccounts. To learn more about
entitlements and quotas, see Managing Entitlements and Quotas Using the Cockpit. Note that if you want to try out
services for free, you need to select free tier service plans if available. For a list of free services, check the SAP Discovery
Center .

5. You can also assign quotas to different spaces within a subaccount. To do so, first create a space quota plan. See Create
Space Quotas or Create Space Quota Plans Using the Cloud Foundry Command Line Interface.

This is custom documentation. For more information, please visit SAP Help Portal. 14
 6/11/25, 2:37 PM
6. Then assign the quota plan to your space. See Assign Space Quotas to Spaces or Assign Quota Plans to Spaces Using the
Cloud Foundry Command Line Interface.

3. Developing and Deploying Applications

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

1. Develop your application. Check out the Developer Guide for tutorials and more information. See Development.

2. Deploy your application. See Deploy Business Applications in the Cloud Foundry Environment.

3. Integrate your application with a service. To do so, first create a service instance. See Creating Service Instances

4. Bind the service instance to your application. See Binding Service Instances to Applications.

5. Alternatively, you can also create and use service keys. See Creating Service Keys. For more information on using services
and creating service keys, see About Services.

6. You can also create instances of user-provided services. See Creating User-Provided Service Instances.

Setting Up a Global Account via the Command Line

Your global account is the entry point for managing the resources, landscape, and entitlements for your departments and projects
in a self-service manner in SAP BTP. You can use the command-line tool btp CLI to set it up, and the cf CLI to manage Cloud
Foundry instances.

Set up your account model using the btp CLI by creating subaccounts in your enterprise account. You can create any number of
subaccounts in the Cloud Foundry environment and region.

This is custom documentation. For more information, please visit SAP Help Portal. 15
 6/11/25, 2:37 PM
To manage Cloud Foundry, i.e. for managing service instances and members in orgs and spaces, creating spaces, as well as
assigning quota to orgs and spaces, you use the cf CLI.

Prerequisites
You have purchased an enterprise global account.

You have downloaded and extracted the following command-line tools:

SAP BTP command line interface (btp CLI). See Download and Start Using the btp CLI Client

Cloud Foundry CLI (cf CLI). See Download and Install the Cloud Foundry Command Line Interface

Procedure

 Tip
In the btp CLI, you can view the command help of each command to get information about how to use the command, its syntax,
and input parameters. See Get Help.

Step No. Task Performed Do This More Information

By

1. Log in to your global account using Global Run this command in the btp CLI: See Log in.
the URL of the btp CLI server and the account btp login
subdomain of your global account. administrator
or viewer

2. View details of your global account. Global Run this command in the btp CLI: See Working with
account btp get accounts/global- Global Accounts,
admin or account Directories, and
viewer Subaccounts Using the
btp CLI.

3. Add admins to your global account. Global Assign the role collection Global See Managing Users
account Account Administrator to a user by and Their
admin running the following command in the btp Authorizations Using
CLI: the btp CLI and
Security
btp assign security/role-
Administration:
collection "Global Account
Managing
Administrator" --to-user
Authentication and
<user> --create-user-if- Authorization.
missing

4. View all the regions that are available Global Run this command in the btp CLI: This command also
to your global account and account btp list accounts/available- provides information
subaccounts. admin or region about the
viewer environments and
infrastructure provider
of each region.

This is custom documentation. For more information, please visit SAP Help Portal. 16
 6/11/25, 2:37 PM

Step No. Task Performed Do This More Information

By

5. Create subaccounts in your global Global Run this command in the btp CLI: See Working with
account. account btp create accounts/subaccount Global Accounts,
admin --display-name <my-subaccount> Directories, and
--region <my-region> -- Subaccounts Using the
subdomain <my-subaccount- btp CLI.
subdomain>

6. View the details of the subaccounts Global Run this command in the btp CLI: See Working with
in your global account. account btp get accounts/subaccount Global Accounts,
admin or <ID of new subaccount> Directories, and
viewer Subaccounts Using the
btp CLI.

7. Add admins to your subaccounts. Subaccount Assign the role collection Subaccount See Managing Users
admin Administrator to the user by running and Their
the following command in the btp CLI: Authorizations Using
the btp CLI and
btp assign security/role-
Security
collection "Subaccount
Administration:
Administrator" --to-user
Managing
<user> --create-user-if-
Authentication and
missing
Authorization.

8. View all the services and applications Global Run this command in the btp CLI: See Setting
that are entitled to your global account btp list accounts/entitlement Entitlements Using the
account, including quota information admin or btp CLI.
per service plan. viewer

9. Assign quotas to your subaccounts. Global Run this command in the btp CLI: See Setting
account btp assign Entitlements Using the
admin accounts/entitlement --to- btp CLI.
subaccount <my-subaccount-id>
--for-service <my-service> --
plan <my-service-plan> --
amount <number>

Validate with this command:

btp list accounts/entitlement

10. View all the entitlements in your Subaccount Run this command in the btp CLI: See Setting
subaccounts. admin or btp list accounts/entitlement Entitlements Using the
viewer --subaccount <my-subaccount- btp CLI.
id>

11. Create a Cloud Foundry org Subaccount Run this command in the btp CLI: See Working with
(environment instance) in your admin btp create Environments Using
subaccounts. accounts/environment-instance the btp CLI andOrg
--subaccount <my-subaccount- Management Using the
id> --display-name <my- SAP BTP Command
environment> --environment Line Interface (btp CLI)
<cloudfoundry> --plan standard .
--parameters "
{\"instance_name\":\"myOrg\"}"

12. View details of the environment Subaccount Run this command in the btp CLI: See Working with
instances in your subaccounts. admin or Environments Using

This is custom documentation. For more information, please visit SAP Help Portal. 17
 6/11/25, 2:37 PM

Step No. Task Performed Do This More Information

By

viewer btp list accounts/environment- the btp CLI.

instance --subaccount <my-
subaccount-id>

13. Create a Cloud Foundry space. Org manager Run these cf CLI commands: See Create Spaces
Using the Cloud
cf login
Foundry Command
cf create-space Line Interface.

14. Add Cloud Foundry org and space Org manager Run these cf CLI commands: See Add Organization
members. cf set-org-role <USERNAME> Members Using the
<ORG> <ROLE> Cloud Foundry
Command Line
cf set-space-role <USERNAME>
Interface and Add
<ORG><SPACE><ROLE>
Space Members Using
the Cloud Foundry
Command Line
Interface.

15. Display all available services in the Org manager Run this cf CLI command: See Using Services in
Cloud Foundry marketplace. the Cloud Foundry
cf marketplace Environment.

Using the btp CLI, you can perform additional account maintenance tasks, such as updating global account and subaccount
details, deleting subaccounts, and deleting environment instances.

Subaccount members can also use the btp CLI to work with multitenant applications. See Working with Multitenant Applications
Using the btp CLI.

Next Steps

Org/space members can create service instances, which are entitled to the subaccount, using also the cf create-service
<allowed-service-plan> command in the cf CLI. Use the cf CLI command cf services to verify that the service instances
exist.

For further documentation about developer tasks, see Development in the Cloud Foundry Environment.

Related Information
Command Syntax of the btp CLI
Download and Start Using the btp CLI Client
btp CLI Command Reference

Getting Started in the ABAP Environment

Get onboarded in the SAP BTP ABAP environment. Follow the workflows for trial or customer accounts.

Getting Started with a Customer Account in the ABAP Environment

This is custom documentation. For more information, please visit SAP Help Portal. 18
 6/11/25, 2:37 PM
After you have purchased a customer account, learn how to get started in the ABAP environment.
Getting Started with Custom Code Analysis in the ABAP Environment
Learn how to get started with Custom Code Analysis in the SAP BTP ABAP environment.

Getting Started with a Customer Account in the ABAP

Environment
After you have purchased a customer account, learn how to get started in the ABAP environment.

 Note
This documentation informs you about the first steps as an administrator in the ABAP environment. For more information
about getting started as a developer, see Getting Started as a Developer in the ABAP Environment.

1. Logging on to SAP BTP

1. After you have purchased your customer account, you will receive an e-mail with a link to the home page of SAP BTP and
the logon data as administrator for the global account.

2. Log on to SAP BTP.

You are now in the SAP BTP cockpit.

3. Navigate to your global account.

2. Automated Initial Setup Using a Booster (Optional)

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

To set up a development system quickly, you can use the booster Prepare an Account for ABAP Development. The interactive
booster guides you through the process of setting up your subaccounts, configuring entitlements, assigning members, and so on.
For more information, see Using a Booster to Automate the Setup of the ABAP Environment (Optional).

Using a booster is optional. If you don't use the booster, you must perform more steps manually.

3. Manual Setup

Even if you have used the booster, some manual setup steps are still required. In the following, steps that are performed by the
booster are indicated.

This is custom documentation. For more information, please visit SAP Help Portal. 19
 6/11/25, 2:37 PM
a. Setting Up Your Account Model

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

1. (Not required if you have used the booster):

Create a subaccount for ABAP environment in your global account (see Creating a Cloud Foundry Subaccount for the ABAP
Environment ).

This allows you to further break down your account model and structure it according to your business needs.

2. (Not required if you have used the booster):

Create organizations and spaces (see Creating a Cloud Foundry Organization and Space).

If you want to learn more about subaccounts, orgs, and spaces, and how they relate to each other, see Account Model.

b. Setting Up the ABAP System

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 20
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. (Not required if you have used the booster):

Before you can start using resources such as services or application runtimes, you must manage your entitlements and add
quotas to your subaccount (see Increasing the Quota for the ABAP Environment ).

2. (Not required if you have used the booster):

Optionally, if your developers want to deploy their own apps in Cloud Foundry, increase the quota for the Cloud Foundry
runtime (see Increasing the Quota for the Cloud Foundry Runtime (Optional)).

3. (Not required if you have used the booster):

Create your ABAP system (see Creating an ABAP System).

4. (Not required if you have used the booster):

Subscribe to the Web access for ABAP SaaS application to get direct browser access to your instances in the ABAP
environment (see Subscribing to the Web Access for ABAP).

This also allows you to access the administration launchpad including your own SAP Fiori applications. You only have to
subscribe once for each subaccount.

c. Creating Administrator and Developer Users

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 21
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. Optionally, you can create additional administrator users for the ABAP environment as follows:

a. (Not required if you have used the booster):

Add users as administrators of the Cloud Foundry organization that you created for the ABAP environment (see
Adding a User as Org Manager for the Cloud Foundry Organization).

b. (Not required if you have used the booster):

Add the users as managers for the Cloud Foundry space that you created for the ABAP environment (see Adding a
User as Space Manager for the Cloud Foundry Space ).

c. Log on to the administration launchpad (see Logging on to the Administration Launchpad of the ABAP
Environment).

d. Create employee records for the new administrators (see Creating an Employee Record for a New Administrator).

e. Assign the administrator role for the ABAP environment to the new users (see Assigning the ABAP Environment
Administrator Role to the New Administrator User).

2. For your developers, create business users and assign them to the developer business role as follows:

This is custom documentation. For more information, please visit SAP Help Portal. 22
 6/11/25, 2:37 PM
a. (Not required if you have used the booster):

Create new members for the space that you created for the ABAP environment and assign developer roles to the
new members (see Creating New Space Members and Assigning Space Developer Roles to Them).

b. Create employee records for the new developer users (see Creating an Employee Record for a New Developer).

c. Assign the ABAP developer users to the ABAP developer role (see Assigning the ABAP Developer User to the ABAP
Developer Role).

4. What's Next

After the initial setup of the ABAP environment, your developers can now develop applications using ABAP Development Tools. You
can tell your developers to get started (see Getting Started as a Developer in the ABAP Environment).

As next steps, you can optionally set up additional tools for your developers or ensure the integration with other systems:

If your developers need a UI development tool, set up SAP Business Application Studio (see Setup of UI Development in
SAP Business Application Studio (Optional)).

As a default identity service in the ABAP environment, you get SAP ID. You might want to set up a custom identity service
(see Setup of a Custom Identity Service).

As an alternative to SAP Business Application Studio, you can also set up SAP Web IDE (see Setup of UI Development in
SAP Web IDE (Optional)).

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

Please note that image maps are not interactive in PDF outputs.

Related Information
Learning Journey
Discovery Center
SAP Community
SAP Road Map Explorer
Video Tutorials

This is custom documentation. For more information, please visit SAP Help Portal. 23
 6/11/25, 2:37 PM

Using a Booster to Automate the Setup of the ABAP Environment

(Optional)
You can use a booster to automate some of the required steps for setting up the ABAP environment. Automation includes creating
a subaccount and space, configuring the required entitlements, and assigning administrators and developers to the subaccount.

Context

A booster is a set of guided interactive steps that enable you to select, configure, and consume services on SAP BTP. For more
information, see Boosters.

 Caution
The booster is only intended to create development systems. For non-development systems, follow the steps to set up the
ABAP environment manually (see Getting Started with a Customer Account in the ABAP Environment).

Procedure
1. Log on to the SAP BTP cockpit and choose the global account for the Cloud Foundry environment as administrator.

2. From the navigation menu, choose Boosters.

3. Choose the booster Prepare an Account for ABAP Development.

The tab pages Overview, Components, and Additional Resources are displayed, where you get more information about the
booster.

4. Choose Start.

5. After the booster wizard has successfully checked the prerequisites, choose Next to continue.

6. On the Select Scenario dialog, choose whether you'd like the booster to create your ABAP environment service instance in
a new, or in an existing subaccount.

7. On the Configure Subaccount dialog, entitlements and quotas for the new subaccount are proposed, but you can change
them if needed:

For the ABAP environment service, the service plan standard enables you to size ABAP server and persistence
independently from each other in 16 GB units. These units are represented in the quota plans abap_compute_unit
and hana_compute_unit.

As part of the default quota assignment, you get at least 1 compute unit in the abap_compute_unit service plan and
at least 2 compute units in the hana_compute_unit service plan. This corresponds to the minimum configuration
for an instance of the ABAP Environment service. You can also choose higher quotas in the dialog of the booster.

For the Web Access to ABAP service, a default plan is chosen that you cannot change. You need the service and the
quota for direct browser access to your instances in the ABAP environment, including access to the administration
launchpad for ABAP.

Depending on what you have ordered for your account, additional entitlements for the services Cloud Foundry
Runtime, SAP Build Work Zone, standard edition, and SAP Business Application Studio might be shown. They are
optional; you can remove the entitlements if you don't need them right now and want to add them later:

A quota for the Cloud Foundry runtime is only needed for the ABAP environment if your developers want to
deploy their own apps in Cloud Foundry.

The SAP Build Work Zone, standard edition enables organizations to establish a central point of access to
SAP, custom-built, and third party applications and extensions, both in the cloud and on premise.

SAP Business Application Studio is a UI development environment.

8. On the Configure Subaccount dialog, follow the instructions on the screen to enter subaccount name, provider, region, and
so on.

9. On the Add Users dialog, add the e-mail addresses of new users in the ABAP environment.
This is custom documentation. For more information, please visit SAP Help Portal. 24
 6/11/25, 2:37 PM
This step allows you to quickly create additional administration users for the ABAP environment, if needed, and developer
users. In the Origin field, you can see the identity provider for the ABAP environment. By default, this is SAP ID service
(sap.ids), but if you have set up a custom identity provider, you can choose this provider from the dropdown list.

 Note
If the optional entitlement for SAP Build Work Zone, standard edition is selected in the Configure Subaccounts step,
please select a custom identity provider for applications. If you choose the default identity provider, the subscription to
the SAP Build Work Zone, standard edition application will fail. Refer to Establish Trust and Federation Between SAP
Authorization and Trust Management Service and SAP Cloud Identity Services for more information.

10. On the Configure ABAP Environment Instance dialog, enter a 3-character ID for your ABAP system.

11. Review your settings and finish the booster.

Results
After the booster has run successfully, the following tasks have been performed automatically:

A new Cloud Foundry subaccount for the ABAP environment is created and enabled.

A space and an organization for the ABAP environment are available.

A service instance for the ABAP environment has been created.

A system ID of your choice has been assigned to the ABAP system.

An identity provider (SAP ID service or a custom identity provider) has been set up for the ABAP environment.

For the ABAP environment service, quotas have been distributed for the ABAP server and the SAP HANA persistence. The
quotas that you have chosen are deducted from the available quota for each service in your global account..

If you have entitlements for SAP Build Work Zone, standard edition and SAP Business Application Studio, then you have
subscribed to these services and standard quotas have been assigned accordingly. Entitlements for subscription services
are assigned to the subaccount.

You’re subscribed to the Web access for ABAP SaaS application and get direct browser access to your instances in the
ABAP environment. Entitlements for subscription services are assigned to the subaccount.

Additional users with Cloud Foundry organization manager and space manager roles have been added. If you have ordered
the SAP Build Work Zone, standard edition as a service, the additional administration users have also been assigned to the
role collection Launchpad_Admin.

Additional users for developers with space developer role have been added. If you have ordered SAP Business Application
Studio as a service, the additional developer users have also been assigned to the role collection
Business_Application_Studio_Developer.

 Note
The booster speeds up the initial setup, but there are still some tasks that you need to perform after the booster has run.

In the following, you can find documentation for all necessary intial tasks, including the tasks that you don't need to perform if
you have run the booster successfully. A note at the beginning of each task indicates that you can skip it if you’ve used the
booster.

ABAP Environment: Initial Settings

This is custom documentation. For more information, please visit SAP Help Portal. 25
 6/11/25, 2:37 PM
With the initial settings, you as an administrator and your ABAP developers can get started in the ABAP environment.

After the initial settings are done, the ABAP environment is ready for your ABAP developers so they can implement business
services using ABAP Development Tools (ADT).

Creating a Cloud Foundry Subaccount for the ABAP Environment

Create a Cloud Foundry subaccount for the ABAP environment in your global account using the cockpit.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip these steps.

For the ABAP environment, you need a Cloud Foundry subaccount as a technical environment. If you want to reuse an existing
Cloud Foundry subaccount, make sure that it uses the providers and regions that are available for provisioning an ABAP
environment. For more information about the providers and regions for ABAP environment, see Regions.

Procedure
1. From your global account, choose New Subaccount.

2. Specify a display name, for example, ABAP.

3. Optional: Enter a description.

4. Leave the Neo Environment checkbox deselected.

5. Choose the desired infrastructure provider and region for your subaccount.

You can find the available providers and regions for the ABAP environment in Regions.

6. Enter a subdomain for your subaccount. The subdomain will become part of the URL for accessing applications that you
subscribe to from this subaccount.

 Note
You can choose any string of your choice. However, note that the subdomain can contain only letters, digits and hyphens
(not allowed in the beginning or at the end), and must be unique across all subaccounts in the same region. Uppercase
and lowercase letters can be used, however that alone does not qualify as a means to differentiate subdomains (for
example, SUBDOMAIN and subdomain are considered to be the same).

7. If your subaccount is to be used for production purposes, select the Used for production option.

8. Choose Create.

Creating a Cloud Foundry Organization and Space

Create a Cloud Foundry organization and Cloud Foundry space that will correspond to the instance of the ABAP environment.

Context

 Note

This is custom documentation. For more information, please visit SAP Help Portal. 26
 6/11/25, 2:37 PM
If you have already created an organization and space for the ABAP environment, you can skip these steps. If you have run the
booster Prepare an Account for ABAP Development, you can also skip these steps.

For more information about creating Cloud Foundry spaces, see Create Spaces.

Procedure
1. Log on to the SAP BTP cockpit in the global account for the Cloud Foundry environment as administrator.

2. Choose the tile of the Cloud Foundry subaccount.

3. Check whether Cloud Foundry is enabled: If it's enabled, the Cloud Foundry organization name appears as organization on
the screen area Cloud Foundry.

4. If Cloud Foundry is not enabled yet, proceed as follows:

a. Choose Enable Cloud Foundry.

b. On the Create Cloud Foundry Organization dialog, enter a name for the Cloud Foundry organization and choose
Create.

c. Choose the free or standard plan for the Cloud Foundry runtime according to your needs.

5. On the Cloud Foundry screen area, choose the link for spaces.

6. If the Cloud Foundry space in the Cloud Foundry organization does not exist yet, proceed as follows:

a. Choose New Space.

b. On the New Space dialog, enter a name for the new Cloud Foundry space, for example, dev, and leave the
checkboxes for space manager and space developer checked.

c. Choose Create.

Increasing the Quota for the ABAP Environment

Before you can create a service instance for the ABAP environment, you must assign some of the available quota to the
subaccount for the ABAP environment.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

If you are working in an enterprise account, you need to add quotas to the services that you purchased in your subaccount before
they can appear in the service marketplace. For more information, see Configure Entitlements and Quotas for Subaccounts.

Procedure
1. Log on to the SAP BTP cockpit as administrator.

2. Go to your global account.

3. From the navigation area, choose Entitlements Entity Assignments .

4. Enter the subaccount for the ABAP environment and choose Go.

5. Choose Configure Entitlements.

6. Choose Add Service Plans.

In the following popup, the available entitlements for this subaccount are shown.

This is custom documentation. For more information, please visit SAP Help Portal. 27
 6/11/25, 2:37 PM
7. For the ABAP environment entitlement, select the plans abap_compute_unit, standard, and hana_compute_unit.

With the selection of the standard service plan, you can size the ABAP runtime and the SAP HANA memory independently
from each other. To be able to do your sizing, you must also select the quota plans abap_compute_unit and
hana_compute_unit.

8. Choose Add 3 Service Plans.

9. On the following screen, increase the quotas in the abap_compute_unit service plan at least by 1 and in the
hana_compute_unit service plan at least by 2.

The minimum configuration of 1 ABAP compute unit and 2 HANA compute units is sufficient in many cases to create one
service instance for the ABAP environment. If you need more resources, choose higher quotas. Keep in mind that
increasing the SAP HANA Cloud storage using the parameter size_of_persistence_disk consumes 0.002 HANA
compute units for each GB that exceeds the minimal size of the persistence disk.

10. Choose Save.

Results

After you have assigned an entitlement for the three plans with respective quotas to your subaccount, you can create an ABAP
system. This is the point where you can then decide how many blocks of ABAP compute units and HANA compute units you want
to assign to your new system. See Creating an ABAP System.

Related Information
ABAP Compute Units

Increasing the Quota for the Cloud Foundry Runtime (Optional)

Check if your subaccount has a quota for the Cloud Foundry runtime and increase it, if needed.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

A quota for the Cloud Foundry runtime is optional. It's only needed for the ABAP environment if your developers want to deploy
their own apps in Cloud Foundry.

Procedure
1. Log on to the SAP BTP cockpit as Cloud Foundry administrator.

2. Go to your global account.

3. From the navigation area, choose Entitlements Entity Assignments .

4. If there is no entry for the Cloud Foundry runtime, choose Configure Entitlements and Add Service Plans.

5. In the following popup, proceed as follows:

a. Choose Cloud Foundry Runtime.

b. Under Available Service Plans, select the checkbox MEMORY.

c. Choose Add 1 Service Plan.

6. Choose + to add at least 1 to the subaccount.

This is custom documentation. For more information, please visit SAP Help Portal. 28
 6/11/25, 2:37 PM
7. Choose Save.

Selecting a Service Plan for the Web Access for ABAP

Before you can subscribe to the Web Access for the ABAP environment, you must select the relevant service plan.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

If you are working in an enterprise account, you need to add quotas to the services that you purchased in your subaccount before
they can appear in the service marketplace.

Procedure
1. Log on to the SAP BTP cockpit as administrator.

2. Go to your global account.

3. From the navigation area, choose Entitlements Entity Assignments .

4. Enter the subaccount for the ABAP environment and choose Go.

5. Choose Configure Entitlements.

6. Choose Add Service Plans.

In the following popup, the available entitlements for this subaccount are shown.

7. For the Web Access for ABAP entitlement, select the plan default (Application).

8. Choose Add 1 Service Plan.

9. Choose Save.

Creating an ABAP System

Create a service instance for the ABAP environment from the Service Marketplace.

Prerequisites
You have increased the quota for the ABAP environment. See Increasing the Quota for the ABAP Environment.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can also skip this step.

For more information about creating service instances, see Create Service Instances Using the Cockpit.

Procedure

This is custom documentation. For more information, please visit SAP Help Portal. 29
 6/11/25, 2:37 PM
1. Log on to the SAP BTP cockpit and navigate to the Cloud Foundry subaccount. See Navigate in the Cockpit .

2. From the navigation area, choose Services Service Marketplace.

You see a list of all services that are available to you.

3. Choose ABAP environment.

4. Choose Create.

A wizard opens that helps you create your instance.

 Tip
To see a list of all instances that have already been created in your subaccount, choose Services Instances and
Subscriptions from the navigation area. Here, you can also create a new ABAP environment instance.

5. Select the standard service plan.

6. Choose Cloud Foundry as your runtime environment.

7. Select a space.

8. Enter a CLI-friendly instance name, and choose Next.

The instance name identifies the service instance in the Cloud Foundry environment. Specify an instance name that is
unique among all the service instances in a space and only contains alphanumeric characters (A-Z, a-z), periods,
underscores, and hyphens.

9. Provide additional instance parameters for the configuration by either using the default form or by uploading a JSON file
from your computer or by specifying the parameters in JSON format. Here is a list of all parameters:

Parameter (technical name in

parenthesis) Note

Admin Email Address The admin email address is used to create the initial user for the ABAP system
(admin_email) automatically, including the assignment of the administrator role to this user. You
can access the ABAP environment system only with this specified user. By default,
the email address is used as subject name identifier.

Admin Employee ID The admin employee ID is an optional parameter used to provide the employee ID
admin_employee_id for the initial user. You can either set it directly by using this parameter during
instance creation or after instance creation in the Maintain Employees Fiori
application of the ABAP environment service instance. Once set, it cannot be
changed anymore. The employee ID must only contain uppercase letters, digits,
underscores, hyphens and periods, and must not be longer than 60 characters.

ABAP System Description The ABAP system description is optional.

(description)

Development System The development system checkbox is checked by default. By using this setting,
(is_development_allowed) you can control the changeability of development objects in the system. If you want
to protect all your customer-related software components and ABAP namespaces
against manual changes via ABAP development tools for Eclipse, uncheck the box.
This setting is used for test and productive systems, where changes must be
imported only. For information about which business catalogs are available in
development systems only, see Business Catalogs for Development Tasks.

ABAP System ID The ABAP system ID must consist of exactly three alphanumeric characters. Only
(sapsystemname) uppercase letters are allowed. The first character must be a letter (not a digit). The
ID does not have to be technically unique.

Total ABAP Runtime Size The Total ABAP runtime size refers to the runtime size of the ABAP environment
(size_of_runtime) service instance. This is the sum of the runtime size of all ABAP application servers

This is custom documentation. For more information, please visit SAP Help Portal. 30
 6/11/25, 2:37 PM

Parameter (technical name in

parenthesis) Note

of an ABAP environment service instance. The size is specified in number of ABAP

compute units that should be used from the quota plan abap_compute_unit, with
one ABAP compute unit representing 16 GB. The supported number of
abap_compute_unit is 1, 2, 4, 6, 8, 16, 24, or 32. For more information, see ABAP
Compute Units.

The total ABAP runtime size should be a whole-number multiple, ranging from 2 to
16 times the size of the ABAP runtime size per application server. This is because
each ABAP environment instance contains between 2 and 16 application servers, all
of the same size. For example, if the application_server_size is 2, the
size_of_runtime should be at least 4 ACUs. Conversely, if the
application_server_size is 0.5, the size_of_runtime shouldn't exceed 8
ACUs. Another example: if the application_server_size is 2, setting the
size_of_runtime to 5 won't work. This is because a total runtime size of 5 ACUs
can't be split into three application servers with 2 ACUs each.

ABAP Runtime Size per Application The ABAP Runtime Size per Application Server refers to the size of a single ABAP
Server application server in an ABAP environment service instance. It's specified in ABAP
(application_server_size) compute units (ACUs), with one ACU representing 16 GB. This parameter doesn't
consume additional abap_compute_unit quota. Instead, it determines the
distribution of the quota defined via the total ABAP runtime size among the
application servers. Possible values are 0.5, 2, or 'auto', which is the default.

A higher value results in fewer, but larger, application servers. Conversely, a lower
number results in more, but smaller, application servers for the same total ABAP
runtime size. If 'auto' is chosen, then 0.5 ACU is assigned per application server if
size_of_runtime is < 4 for systems without elastic scaling, or
size_of_runtime < 8 for systems with elastic scaling. Otherwise, 2 ACUs are
assigned per application server.

Every ABAP environment instance has between 2 and 16 application servers of the
same size each. Therefore, the possible value for the ABAP runtime size per
application server depends on the total ABAP runtime size. For instance,
application_server_size = 2 can only be set if the size_of_runtime is at
least 4 ACUs. On the other hand, application_server_size = 0.5 can only be
set if the size_of_runtime isn't higher than 8 ACUs.

To decide what value to choose, consider the following:

Servers of size 0.5 ACUs allow more fine-granular scaling and are suitable
for most use cases.

Larger servers allow slightly more user sessions per ACU. This might be
more efficient in systems with very high ACU consumption. They're also a
precondition for some exceptional use cases, such as ATC checks for very
large ABAP programs.

Elastic Scaling of the ABAP Application The elastic scaling of the ABAP application server parameter defines whether or
Server not to adapt the number of ABAP application servers dynamically, depending on
(elastic) the system load.

By default, the checkbox is not checked (elastic = false), and the service
instance will have a fixed number of ABAP application servers with a total ABAP
runtime size as defined by the parameter Total ABAP Runtime Size (see above).

If you enable elastic scaling by checking the checkbox (elastic = true),

application servers will be automatically added to the service instance when the
load increases and removed when the load decreases. More specifically, the

This is custom documentation. For more information, please visit SAP Help Portal. 31
 6/11/25, 2:37 PM

Parameter (technical name in

parenthesis) Note

number of application servers will scale between the number of ACUs (ABAP
compute units) needed for two application servers as a minimum (1 ACU if
application_server_size = 0.5 or 4 ACU if application_server_size = 2), and the
number of ACUs configured in the Total ABAP Runtime Size parameter (see above)
as a maximum.

This feature considerably helps in cost-saving as charges are only levied based on
the actually allocated ACUs, and not on the configured maximum. Still, to ensure
that defined quotas are not exceeded, the maximum number of ACUs that is set in
the Total ABAP Runtime Size parameter is allocated from the available ACU quota
for the entire duration that the service instance is provisioned.

The scaling typically occurs within a couple of minutes. Especially when a service
instance is scaled down, there is a grace period of a few minutes to allow the
completion of short-lived requests. Before enabling elastic scaling in production, we
advise to test your typical workload patterns and monitor the embededed Health
Monitoring app to verify the suitability of this cost-saving measure. Maintaining a
higher number of statically configured ACUs might be better for handling sudden
large spikes in the system load.

HANA Cloud Memory Size The HANA Cloud memory size refers to the memory size of the SAP HANA Cloud
(size_of_persistence) database used by the ABAP environment service instance. The size is specified in
number of HANA compute units that should be used from the quota plan
hana_compute_unit, with one HANA compute unit representing a block size of 16
GB for the underlying SAP HANA Cloud instance. The supported number of
hana_compute_unit per HANA instance is 2, 4, 8, 16, 32, or 64.

HANA Cloud Disk Size The HANA Cloud disk size refers to the disk size in GB of the SAP HANA Cloud
(size_of_persistence_disk) database used by the ABAP environment service instance. If the parameter is set to
auto, the SAP HANA Cloud storage size is set to the minimal value 40 *
size_of_persistence + 40. The maximum allowed value is 120 *
size_of_persistence + 40. If you set a higher value, it will consume 0.002
HANA compute units (HCU) for any GB exceeding the minimal default size of the
persistence disk. Therefore, the HCU ratio of additional storage disk to RAM is 1 :
31.25 per GB (as 1 HCU = 16 GB).

Admin User Name The admin user name is an optional parameter used to provide the user name for
(admin_user_name) the initial user. It must be provided if the login attribute is set to user_name (see
below).

Login Attribute Using an email address as subject name identifier might not be possible if the e-
(login_attribute) mail address is ambiguous across users, or if the trusted identity provider
configured for authentication in the subaccount of the ABAP environment instance
is already configured with the subject name identifier Login Name. In this case,
you can change the login attribute to user_name. In addition, provide the user
name for the initial user in the admin user name (see above).

 Caution
Currently, it's only possible to change the login attribute when creating a new
ABAP system. To change the settings afterwards, please create a service ticket.

 Note
Make sure that you don't choose more compute units than you have assigned to your subaccount for the ABAP
environment (see Increasing the Quota for the ABAP Environment).

This is custom documentation. For more information, please visit SAP Help Portal. 32
 6/11/25, 2:37 PM
For more information about ABAP system sizing and Native Storage Extension for selected SAP HANA tables, see ABAP
System Sizing and Native Storage Extension for the ABAP Environment.

 Caution
Be aware that not all parameters can be changed if you update your ABAP system. For a list of updatable parameters,
see Updating an ABAP System.

10. Choose Next to review and verify your instance details.

11. Choose Create.

The ABAP environment instance is being set up, which might take a while. Wait for an email that is sent when the setup is
completed and the system up and running. The email is sent to the email address that you specified as admin email in the
previous steps.

Updating an ABAP System

Learn how to update your ABAP environment instance.

Context
After you have created an ABAP environment instance, you can change the following properties:

ABAP System Description

Total ABAP Runtime Size (size_of_runtime)

ABAP Runtime Size per Application Server (application_server_size)

Elastic Scaling of the ABAP Application Server

HANA Cloud Memory Size (size_of_persistence)

HANA Cloud Disk Size (size_of_persistence_disk)

 Note
The updates of these properties are done without any downtime, or - in case of updating the HANA memory or disk size - with
near zero downtime (meaning that the database is not accessible for a few seconds only).

To change the initial admin, you have to use the Maintain Employees SAP Fiori app. See Maintain Employees.

To update your system from a free to a standard plan, see Update to a Paid Service Plan. Make sure you have enough
hana_compute_units and abap_compute_units available as quota in your subaccount before updating to a paid plan. For more
information, see Increasing the Quota for the ABAP Environment.

 Restriction
A downsizing of the HANA Cloud memory size is only possible down to the minimum amount of memory required for a stable
performance of the HANA Cloud database. Before the memory size is decreased, an SQL query (as described on SAP HANA
Database Downsizing) is automatically run on the database to make sure the downsizing is possible based on the already
consumed memory.

The HANA Cloud memory size cannot be decreased while a system is stopped. To decrease the HANA Cloud memory size of a
stopped instance, the instance has to be started via the Landscape Portal first.

This is custom documentation. For more information, please visit SAP Help Portal. 33
 6/11/25, 2:37 PM
The HANA Cloud disk size can currently only be increased, and not decreased.

Both the HANA Cloud memory and the disk size can only be resized once every 24 hours.

Procedure
1. In the SAP BTP cockpit, choose your Cloud Foundry subaccount and navigate to the space, in which you have created your
ABAP environment instance. See Navigate in the Cockpit.

2. From the navigation area, choose Services Instances and Subscriptions .

You see a list of all instances that have been created.

3. Select your ABAP environment instance and choose Update by clicking on  at the end of the row. If you'd like to check the
values that are currently configured first, please select View Parameters instead.

4. In the Update Instance wizard, you can update the parameters listed above. See Increasing the Quota for the ABAP
Environment. The currently configured values are prefilled in the Update Wizard, so you can keep the values that you don’t
want to change as they are.

5. Choose Update Instance to save your changes.

Results
Your ABAP environment instance is being updated. This might take a while.

Subscribing to the Web Access for ABAP

You need to subscribe to the Web access for ABAP SaaS application to get direct browser access to your instances in the ABAP
environment, including access to the administration launchpad for ABAP.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

This subscription is required to access the SAP Fiori launchpad for the administrator and to access developed SAP Fiori
applications. Subscription is required only once per subaccount (for all systems to be created in all spaces of this subaccount).
After subscribing to the application, you have access to the administration launchpad, where you can configure application roles
and assign those roles to your users.

Procedure
1. Log on to the SAP BTP cockpit in the Cloud Foundry subaccount of the global account for Cloud Foundry as administrator.

2. In the navigation area, choose Services Service Marketplace .

3. Choose the SaaS application tile Web access for ABAP.

4. If the application is not shown as active, choose Create and wait for the subscription to be provisioned.

Creation of Additional Administrator Users (Optional)

After you have set up the ABAP environment for administration, add more administrator users for the ABAP environment.

This is custom documentation. For more information, please visit SAP Help Portal. 34
 6/11/25, 2:37 PM
After you have completed the administrative setup, only your user is available as administrator in the ABAP environment. You will
probably want to create more administration users for your ABAP environment. Creating more administration users also helps you
verify that your administrative setup is correct and complete.

Related Information
Adding a User as Org Manager for the Cloud Foundry Organization
Adding a User as Space Manager for the Cloud Foundry Space
Logging on to the Administration Launchpad of the ABAP Environment
Creating an Employee Record for a New Administrator
Assigning the ABAP Environment Administrator Role to the New Administrator User

Adding a User as Org Manager for the Cloud Foundry

Organization
After you have created a Cloud Foundry organization for the ABAP environment, you can add more users as organization
managers.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development and entered additional administrators, you can skip
these steps.

Procedure
1. Log on to the SAP BTP cockpit as administration user for Cloud Foundry.

2. Go to your subaccount for the ABAP environment.

3. From the navigation area, choose Org Members.

4. Choose Add Members.

5. Enter the user’s e-mail address in the E-mails field.

6. Select the checkbox for org manager.

7. Choose OK.

Adding a User as Space Manager for the Cloud Foundry Space

After you have created a Cloud Foundry space for the ABAP environment, you can add more users as space managers.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development and entered users as additional administrators, you
can skip these steps.

This is custom documentation. For more information, please visit SAP Help Portal. 35
 6/11/25, 2:37 PM

Procedure
1. Log on to the SAP BTP cockpit as administration user for Cloud Foundry.

2. Go to your subaccount for the ABAP environment.

3. Choose Spaces.

4. Choose the Cloud Foundry space in the Cloud Foundry org.

5. In the navigation area, choose Members.

6. Choose Add Members.

7. Enter the user’s e-mail address in the E-mails field.

8. Select the checkbox for space manager.

9. Choose OK.

Logging on to the Administration Launchpad of the ABAP

Environment
To add another user as administrator for the ABAP instance, log on to the administration launchpad of the ABAP environment.

Prerequisites
You are the administrator who has created the ABAP system (see Creating an ABAP System).

Procedure
1. In the SAP BTP cockpit, go to the Cloud Foundry subaccount for the ABAP environment as administrator.

2. Choose the space in the Cloud Foundry subaccount.

3. In the navigation area, choose Services Service Instance .

4. Choose the service instance for the ABAP environment.

5. Choose View Dashboard.

The logon window for the administration launchpad of the ABAP environment opens.

6. If you are using the custom Identity Authentication service for SAP BTP, you don't need to enter your user and password,
but choose the available link of the custom Identity Authentication service and log on.

7. If you need to enter your user and password, remember to log on with the right user that was defined before (see Creating
an ABAP System).

Results
The administration launchpad opens. You can now proceed with creating an employee record for the administrator.

Creating an Employee Record for a New Administrator

To be able to create a new administration user, you first need to create an employee record for the new administrator.

Prerequisites

This is custom documentation. For more information, please visit SAP Help Portal. 36
 6/11/25, 2:37 PM
You have logged on to the administration launchpad of the ABAP environment as administrator user (see Logging on to the
Administration Launchpad of the ABAP Environment).

Procedure
1. From the SAP Fiori launchpad, open the Maintain Employees app.

2. Choose Create.

3. Enter the data for the new administrator, including employee ID, name, and e-mail address.

The entered e-mail is important because it is the default approach to authorization and represents the mapping between
the user in the identity provider and in the ABAP environment.

4. Choose Create.

Results
You can now create a business user and assign administration roles to the business user.

Assigning the ABAP Environment Administrator Role to the New

Administrator User
Add the new administration user as administrator to the ABAP instance.

Prerequisites
You have logged on to the administration launchpad of the ABAP environment as administrator (see Logging on to the
Administration Launchpad of the ABAP Environment). You have created an employee record for another, new administrator.

Procedure
1. On the SAP Fiori launchpad, choose the Maintain Business Users tile.

2. Choose New.

3. In the following dialog, choose the employee record of the new administrator from the list.

4. Confirm the system message that you want to create a new user.

5. Add the time zone to the business user data.

6. On the Assigned Business Roles tab, choose Add.

7. Select the checkbox for the predefined administrator business role SAP_BR_ADMINISTRATOR.

8. Select the checkbox for other administrator roles that are available for your organization and choose OK.

9. Choose OK.

10. Choose Save.

Creation of Developer Users

After you have set up the ABAP environment for development, create developer users for the ABAP environment.

Creating developer users also helps you verify that your development setup is correct and complete.

This is custom documentation. For more information, please visit SAP Help Portal. 37
 6/11/25, 2:37 PM

Creating New Space Members and Assigning Space Developer

Roles to Them
For your developers, create new members in the space for the ABAP environment and assign developer roles to them.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

Procedure
1. Log on to the SAP BTP cockpit as Cloud Foundry administrator.

2. Choose the tile for the Cloud Foundry subaccount.

3. In the navigation area, choose Spaces.

4. Choose the space for the ABAP environment.

5. In the navigation area, choose Members.

All members currently assigned to the space are shown in a list.

6. Choose Add Members.

7. Enter e-mail addresses of your developer users.

8. You can use commas, spaces, semicolons, or line breaks to separate members.

9. Select the space developer role for the users and save your changes.

Creating an Employee Record for a New Developer

Create an employee record for a new developer user for the ABAP environment.

Procedure
1. Log on to the administration launchpad of the ABAP environment as administrator (see Logging on to the Administration
Launchpad of the ABAP Environment).

2. Choose the Maintain Employees tile.

3. Choose Create.

4. Enter the data for the new developer, including employee ID, name, and e-mail address.

The entered e-mail is important because it represents the mapping between the user in the identity provider and in the
ABAP environment.

5. Choose Save.

Assigning the ABAP Developer User to the ABAP Developer Role

Add the developer user as business user to the ABAP instance.

Prerequisites
This is custom documentation. For more information, please visit SAP Help Portal. 38
 6/11/25, 2:37 PM
You have created an employee record for the new developer user (see Creating an Employee Record for a New Developer).

You have created an ABAP developer role based on the business role template SAP_BR_DEVELOPER, which provides developers
with unrestricted read and write access in the ABAP environment. Alternatively, you have created a business role based on a
development-related business catalog (see Business Catalogs for Development Tasks).

Procedure
1. Log on to the administration launchpad of the ABAP environment as administrator (see Logging on to the Administration
Launchpad of the ABAP Environment).

2. On the SAP Fiori launchpad, choose the Maintain Business Users tile.

3. Choose New.

4. In the following dialog, choose the employee record of the new developer user from the list.

5. Confirm the system message that you want to create a new user.

6. On the Assigned Business Roles tab, choose Add.

7. Select the checkbox for the ABAP developer role that you have created before (see Prerequisites).

8. Choose OK and save your entries.

Creating a Service Key (Optional)

In the SAP BTP cockpit, you can create a service key for the ABAP system. You can later use this service key, for example, to log on
to the ABAP system from ABAP development tools for Eclipse for test purposes.

Context
You can use service keys to generate credentials to communicate directly with a service instance. After you have configured the
service keys for your service, local clients, apps in other spaces, or entities outside your deployment can access your service with
these keys. Using a service key is one option how you can access the service instance of the ABAP environment, for example, as
administrator for test purposes. Note, however, that there's also another option for users of ABAP development tools for Eclipse:
instead of using an existing service key, developers and other users with a user and password for the ABAP system can also use
the project creation wizard in ABAP development tools for Eclipse to log on to the ABAP service instance and use the service key
that is automatically provided by the service instance. You can also create service keys for other use cases, such as: Creating an
Inbound Communication Arrangement with Service Key Type Basic and Configuring the Timeout of the @sap/approuter
Component.

 Note
The process for connecting to an ABAP service instance URL when creating a new ABAP Cloud project in ABAP development
tools for Eclipse has changed. For more information, see ABAP Service Instance URL.

Procedure
1. As Cloud Foundry administration user, log on to the SAP BTP cockpit.

2. Go to your Cloud Foundry subaccount for the ABAP environment.

3. In the navigation area, choose Spaces.

4. Choose the tile for the ABAP environment space.

5. From the navigation area, choose Services Instances and Subscriptions .

6. Choose the service instance of the ABAP system.

This is custom documentation. For more information, please visit SAP Help Portal. 39
 6/11/25, 2:37 PM
7. In the Service Keys section of the details area, choose Create.

8. Enter a name for the service key, for example, ABAP Development.

9. Choose Save.

10. Copy the created service key for later reuse.

Setup of UI Development in SAP Business Application Studio

(Optional)
If developers want to use SAP Business Application Studio to create and deploy SAP Fiori application UIs, you need to perform
some administrative activities to set it up.

In the Cloud Foundry environment, SAP Business Application Studio is a service that provides a modular development
environment, including the development of SAP Fiori applications. As an alternative to SAP Business Application Studio, you can
also use SAP Web IDE. We recommend that you use SAP Business Application Studio.

 Note
The process for connecting to an ABAP service instance URL when creating a new ABAP Cloud project in ABAP development
tools for Eclipse has changed. For more information, see ABAP Service Instance URL.

Prerequisites
For setting up SAP Business Application Studio, you need the following:

You are a member of the global account.

You are an organization manager in your Cloud Foundry subaccount (see also Adding a User as Org Manager for the Cloud
Foundry Organization).

You have created an ABAP service instance (see also Creating an ABAP System).

You are a security administrator. If you have created a subaccount for the ABAP environment in the Cloud Foundry
environment, your user automatically has the security administration role.

Setting Up SAP Business Application Studio

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip the first two steps.

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 40
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. To enable the creation and deployment of SAP Fiori application UIs, subscribe to SAP Business Application Studio in the
same subaccount in which you've created your ABAP service instance (see Subscribing to SAP Business Application
Studio).

2. To allow developers to develop applications using SAP Business Application Studio, assign developers to the
Business_Application_Studio_Developer role collection (see Assigning Permissions for SAP Business
Application Studio).

3. Create a service key for your ABAP system, which you will need to set up a service destination (see Creating a Service Key
for the ABAP System).

4. To connect your ABAP system with SAP Business Application Studio, set up a destination in the same subaccount in which
you have subscribed to SAP Business Application Studio (see Creating a Destination to the ABAP System for SAP Business
Application Studio).

Subscribing to SAP Business Application Studio

If developers want to use SAP Business Application Studio as development environment for UIs, you need to subscribe to SAP
Business Application Studio in your subaccount.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

For more information about SAP Business Application Studio and how to subscribe to it, see also Subscribe to SAP Business
Application Studio.

Procedure
1. Log on to the SAP BTP cockpit as Cloud Foundry administrator.

2. Choose the tile of the global account of the Cloud Foundry environment.

3. From the global account, navigate to the same subaccount where the ABAP instance is present.

4. From the navigation area, choose Services Service Marketplace .

5. Search for Studio.

This is custom documentation. For more information, please visit SAP Help Portal. 41
 6/11/25, 2:37 PM
The SAP Business Application Studio tile is displayed.

6. Choose the application name.

7. Choose Create.

Assigning Permissions for SAP Business Application Studio

Use the available role collection Business_Application_Studio_Developer to assign the relevant permissions to your
developers to work in SAP Business Application Studio.

Context
Developers using SAP Business Application Studio must be assigned to developer roles based on the
Business_Application_Studio_Developer role template. When you subscribe to SAP Business Application Studio, a role
collection containing the relevant developer permissions is automatically created. You must assign the role collection to your
developers.

 Note
In the following steps, you can assign a role collection to an individual user. If you have run the booster Prepare an Account for
ABAP Development, you can skip this step.

As an alternative, if you are using a custom identity service and identity provider groups, you can also assign the role collection
to the identity provider group for your developers. For more information, see Setup of a Custom Identity Service and Mapping a
Role Collection to the Identity Provider Group for Developers.

Procedure
1. In the SAP BTP cockpit, navigate to your subaccount for the ABAP environment.

2. From the navigation area, choose Security Role Collections .

3. Choose the role collection Business_Application_Studio_Developer.

4. Go to the Users section and choose Edit.

5. Enter the user ID of the user that you want to assign to the role collection.

6. Save your changes.

Creating a Service Key for the ABAP System

Create a service key for the ABAP system, which will later be needed to configure a destination from SAP Business Application
Studio to the ABAP system.

 Note
The process for connecting to an ABAP service instance URL when creating a new ABAP Cloud project in ABAP development
tools for Eclipse has changed. For more information, see ABAP Service Instance URL.

You can use service keys to generate credentials to communicate directly with a service instance. After you have configured the
service keys for your service, local clients, apps in other spaces, or entities outside your deployment can access your service with
these keys. For more information about service keys, see Creating Service Keys.

1. As Cloud Foundry administration user, log on to the SAP BTP cockpit.

This is custom documentation. For more information, please visit SAP Help Portal. 42
 6/11/25, 2:37 PM
2. Go to your Cloud Foundry subaccount for the ABAP environment.

3. In the navigation area, choose Spaces.

4. Choose the tile for the ABAP environment space.

5. From the navigation area, choose Services Instances .

6. Choose the service instance for the ABAP system.

7. In the Service Keys section of the details area, choose Create.

8. Enter a service key name, for example, ABAP Destination, and save.

9. From the service key, copy the following for later reuse:

The URL of the ABAP system from the url element

The client ID from the clientid element in the uaa section

The content of the clientsecret element in the uaa section

The URL from the url element in the uaa section

Related Information
SAP BTP Cockpit

Creating a Destination to the ABAP System for SAP Business

Application Studio
Learn how to set up a destination in the same Cloud Foundry subaccount in which you have subscribed to SAP Business
Application Studio to establish communication between the ABAP environment and SAP Business Application Studio.

Context
The process for connecting to an ABAP service instance URL when creating a new ABAP Cloud project in ABAP development tools
for Eclipse has changed. For more information, see ABAP Service Instance URL.

Procedure
1. Log on to the SAP BTP cockpit as administrator.

2. From your global account, navigate to your Cloud Foundry subaccount.

3. In the navigation area, choose Destinations.

4. Choose New Destination.

5. Enter the following data:

Field User Input

Name Enter a name for the destination, for example,

SAP_Business_Application_Studio.

Type HTTP

Description

URL Enter the URL of the ABAP system that you copied from the
<url> element in the service key (see Creating a Service Key

This is custom documentation. For more information, please visit SAP Help Portal. 43
 6/11/25, 2:37 PM

Field User Input

for the ABAP System).

Proxy Type Internet

Authentication OAuth2UserTokenExchange​

Client ID Enter the content of the <clientID> element that you copied
from the uaa section of the service key (see Creating a Service
Key for the ABAP System).

Client Secret Enter the content of the <clientsecret> element that you
copied from the uaa section of the service key (see Creating a
Service Key for the ABAP System).

Token Service URL Type Choose Dedicated.

Token Service URL Enter <uaa-url>/oauth/token, where <uaa-url> is the

content of the <url> element that you copied from the uaa
section of the service key (see Creating a Service Key for the
ABAP System).

6. Choose New Property and add the following properties:

Property Value

HTML5.DynamicDestination true

HTML5.Timeout​ 60000

WebIDEEnabled true

WebIDEUsage odata_abap,dev_abap,abap_cloud

7. Make sure that the Use default JDK truststore checkbox is checked.

8. Choose Save.

Related Information
Creating a Destination for Cross-Subaccount Communication

Creating a Destination for Cross-Subaccount Communication

Learn how to create a destination with SAML assertion authentication to establish communication between an ABAP environment
system and SAP Business Application Studio when they are set up in different subaccounts.

Procedure
1. Log on to the SAP BTP cockpit as an administrator.

2. From your global account, navigate to your Cloud Foundry subaccount.

3. In the navigation area, choose Connectivity Destinations .

4. Choose New Destination.

5. Enter the following data:

This is custom documentation. For more information, please visit SAP Help Portal. 44
 6/11/25, 2:37 PM

Field User Input

Name Enter a name for the destination, for example

SAP_Business_Application_Studio.

Type HTTP

Description Optionally, enter a description.

URL Enter the URL of your system by copying the Host Name from
the Communications Systems app, for example 1a354373-
d200-46f6-9d5c-
daab9a65d9b6.abap.eu10.hana.ondemand.com

Proxy Type Internet

Authentication SAMLAssertion​

Audience Enter the URL of your system and add -web as follows
1a354373-d200-46f6-9d5c-daab9a65d9b6.abap-
web.eu10.hana.ondemand.com

AuthnContextClassRef urn:oasis:names:tc:SAML:2.0:ac:classes:PreviousSession

6. Choose New Property and add the following properties:

Property Value

HTML5.DynamicDestination true

HTML5.Timeout​ 60000

WebIDEEnabled true

WebIDEUsage odata_abap,dev_abap

nameIdFormat urn:oasis:names:tc:SAML:1.1:nameid-
format:emailAddress

or

urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

depending on the login_attribute configuration chosen during

ABAP system provisioning (see Creating ABAP System)

7. Make sure that the Use default JDK truststore checkbox is ticked.

8. Choose Save.

Related Information
Creating a Destination to the ABAP System for SAP Business Application Studio
Creating a Communication System for SAP Business Application Studio

Creating a Communication System for SAP Business Application

Studio
This is custom documentation. For more information, please visit SAP Help Portal. 45
 6/11/25, 2:37 PM
Create a communication system to set up communication between your ABAP environment system and SAP Business Application
Studio.

Procedure
1. In the SAP BTP cockpit, download your subaccount-specific trust certificate by navigating to Connectivity
Destinations Download Trust .

2. In the SAP Fiori launchpad of your ABAP environment system, create a communication system by using the
Communication Systems app. See How to Create Communication Systems.

3. Navigate to section General SAML Bearer Assertion Provider and switch the toggle button to ON.

4. Upload the Signing Certificate first and then enter the following data:

 Note
The signing certificate is the trust certificate that you have downloaded from your destination.

Field User Input

User ID Mapping Mode User Name

SAML Bearer Issuer From the Signing Certificate Subject, copy the common name
(the string after CN=) and paste it in the SAML Bearer Issuer
field.

Setup of a Custom Identity Service

For your business users in the ABAP environment, you set up a custom identity service.

Custom Identity Service for the ABAP Environment

For platform users such as the administrator, the default identity provider is SAP ID Service, which is set up by default. For the
business users in the ABAP environment, you must set up a custom identity service. For example, the users of your deployed
application or users of subscribed apps or services, such as SAP Business Application Studio, are business users. For more
information about platform and business users in the ABAP environment, see User Types.

In this documentation, a custom trust configuration is described using SAP Cloud Identity Services - Identity Authentication. The
Identity Authentication service is a cloud solution for identity lifecycle management for SAP BTP applications. You can set up SAP
BTP as a service provider, and Identity Authentication service as an identity provider.

Identity Authentication Service as Proxy

If you have your own custom identity providers at your company, you can use SAP Cloud Identity Services - Identity Authentication
as a proxy. For more information about setting up the Identity Authentication service as a proxy, see Establish Trust and Federation
Between UAA and Identity Authentication and Configure Trust with Corporate Identity Provider.

More Information

This documentation describes the basic trust concepts and helps you to get started with a simple landscape. To learn more about
trust setup with custom identity providers, check the following, more detailed documentation:

This is custom documentation. For more information, please visit SAP Help Portal. 46
 6/11/25, 2:37 PM
For more information about trust in SAP BTP, see Trust and Federation with Identity Providers.

For more information about the Identity Authentication service, see Overview and Initial Setup.

Establishing Trust of Type OpenID Connect

If you want to use a custom identity provider, you must set up trust between the subaccount and the SAP Cloud Identity Services -
Identity Authentication service.

Context

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

If you have custom identity provider, you can use a function in SAP BTP cockpit to set up trust between your subaccount and the
Identity Authentication service for SAP BTP automatically. The trust configuration is of type OpenID Connect.

For more information, see Establish Trust and Federation Between SAP Authorization and Trust Management Service and Identity
Authentication.

Procedure
1. In the SAP BTP cockpit, go to the subaccount for your ABAP system.

2. From the navigation area, choose Security Trust Configuration .

3. Choose Establish Trust.

4. In the following popup, select a identity provider from the dropdown list.

Only identity providers that are associated with your customer ID are shown.

5. Choose Establish Trust.

Trust of type OpenID Connect between your subaccount and the identity provider is generated.

6. Log on to the Identity Authentication service.

7. From the navigation area, choose Applications & Resources Applications .

8. Search for the application that has been created as part of the trust setup.

The name of the application has the format SAP BTP subaccount <Subaccount Name>, but you can change it if needed.

 Note
Older application names have the format XSUAA_<Subaccount Name>.

9. Verify that the subject name identifier matches the login_attribute chosen during ABAP system provisioning.

ABAP login_attribute SAP Cloud Identity Services Subject Name Identifier

email email

user_name login name

This is custom documentation. For more information, please visit SAP Help Portal. 47
 6/11/25, 2:37 PM

Creating Identity Provider Users and Groups

Learn how you create identity provider users and groups in the Identity Authentication service.

Context and Use Cases

This configuration is needed for easier developer authentication using Identity Authentication service. With the creation of identity
provider groups, you can also more easily map role collections to entire user groups instead of single users, or map identity
provider groups to groups in the Neo environment, for example.

This documentation illustrates the basic concepts and helps you to get started with users and groups in a simple landscape for the
ABAP environment.

Prerequisites
You have already created developer users in the ABAP environment (see Creation of Developer Users).

Creating an Identity Provider Group for Developers

In the administration console of the Identity Authentication service, you can create an identity provider group for the developers.

Context
An identity provider group for developers is useful, for example, if you want to assign a role collection to all developers in one step,
such as the Application_Studio role collection for SAP Business Application Studio.

You also use identity provider groups for developers if you want to assign all developers to a corresponding group in the Neo
environment, which is necessary if your developers want to use SAP Web IDE as UI development tool.

For more information about creating user groups in the Identity Authentication service, see Create a New User Group.

Procedure
1. Log on to the tenant's administration console for the Identity Authentication service at https://<tenant
ID>.accounts.ondemand.com/admin as administration user.

2. In the navigation area, choose Users & Authorizations User Groups .

3. If no user group for developers exists, choose + Add.

4. Enter a name, for example, Developers.

5. Enter a display name and a description.

6. Choose Save.

7. Note down the group name for later reference.

Creating Identity Provider Users for Developers

In the administration console of the Identity Authentication service, you can create identity provider users for the developers
working in the ABAP environment.

This is custom documentation. For more information, please visit SAP Help Portal. 48
 6/11/25, 2:37 PM

Context
You create identity provider users if you work with your own custom identity provider, such as the Identity Authentication service
for SAP BTP. You can use the identity provider users, for example, for developers who develop UIs and services using SAP Web IDE
or SAP Business Application Studio.

For more information about creating users in the Identity Authentication service, see Create a New User.

Procedure
1. Log on to the tenant's administration console for the Identity Authentication service at https://<tenant
ID>.accounts.ondemand.com/admin as administration user.

2. In the navigation area, choose Users & Authorizations User Management .

3. Choose + Add User.

4. Enter the name, e-mail address and login name of the developer.

5. Leave the account type set to Employee.

6. Make sure that the account activation is set to Send activation e-mail.

7. Choose Save.

Assigning the Identity Provider User Group to the Identity

Provider Users for Developers
Assign the identity provider user group for developers to the identity provider users that you have created for the developers.

Prerequisites
You have already created identity provider users. You have also already created identity provider user groups, for example, for SAP
Web IDE, for SAP Business Application Studio, or for both.

Context
You now assign these identity provider user groups to the identity provider users for the developers.

For more information about assigning user groups, see Assign Groups to a User.

Procedure
1. Log on to the tenant's administration console for the Identity Authentication service at https://<tenant
ID>.accounts.ondemand.com/admin as administration user.

2. In the navigation area, choose Users & Authorizations User Management .

3. Choose the identity provider user that you have created for the developer.

4. Choose the User Group tab.

5. Choose Assign Groups.

6. Choose the identity provider group for developers that you have created (for example, Developers for SAP Web IDE, or
BAS_DEVELOPERS for SAP Business Application Studio).

7. Choose Save.

This is custom documentation. For more information, please visit SAP Help Portal. 49
 6/11/25, 2:37 PM

Mapping a Role Collection to the Identity Provider Group for

Developers
For developers to be able to work with SAP Business Application Studio, you can use a predefined role collection and assign it to
the identity provider group that you created for the developers.

Prerequisites

 Note
If you have run the booster Prepare an Account for ABAP Development, you can skip this step.

You have subscribed to SAP Business Application Studio (see Subscribing to SAP Business Application Studio).

Context

 Note
These steps are only relevant if developers want to use SAP Business Application Studio as development environment for UIs.

Developers who want to load, develop, and deploy applications in SAP Application Studio must be assigned to developer roles
based on the Business_Application_Studio_Developer role template. There's no need to create these roles for SAP Business
Application Studio. When you subscribe to SAP Business Application Studio, role collections together with these business role
templates are created automatically.

This procedure briefly describes how to assign the role collections to the developer user group in your custom identity provider.
For more information about managing authorizations, see Manage Authorizations.

Procedure
1. Log on to the SAP BTP cockpit as Cloud Foundry administrator.

2. Choose the tile of the global account of the Cloud Foundry environment.

3. In the SAP BTP cockpit, navigate to your subaccount for the ABAP environment.

4. From the navigation area, choose Security Role Collections .

5. Choose the Business_Application_Studio_Developer role collection.

6. Go to the User Groups section and choose Edit.

7. Select the identity provider where the user group is stored.

8. Enter the name of the user group that you created before, for example, Developers.

9. Save your entries.

Setup of UI Development in SAP Web IDE (Optional)

If your developers want to use SAP Web IDE as a development tool for creating UIs, you as an administrator need to perform some
additional settings.

If your developers want to use SAP Web IDE, which is part of the Neo environment, they need to work in the Cloud Foundry and the
Neo environments. To enable an easier authentication of the developers in the Cloud Foundry and Neo environments, set up SAP

This is custom documentation. For more information, please visit SAP Help Portal. 50
 6/11/25, 2:37 PM
BTP as a service provider, and Identity Authentication service as an identity provider. For the integration, you must set the trust on
both sides and map the identity provider group for developers to its corresponding Neo group.

 Recommendation
We recommend that you use SAP Business Application Studio as a UI development environment instead of SAP Web IDE.

Neo Environment: Trust Setup

To enable an easier authentication of the developers in the Cloud Foundry and Neo environments, set up SAP BTP as a service
provider, and Identity Authentication service as an identity provider.

Before you follow the steps outlined here for setting up trust between the Neo application and the Identity Authentication service,
make sure that you have already set up the Identity Authentication service as custom identity provider for the Cloud Foundry
account. For more information, see Setup of a Custom Identity Service.

Exporting SAML Identity Provider Metadata

Export the SAML metadata of the identity provider for the SAML trust setup on the service provider side.

Context
You need this step only if the SAML metadata file for the Identity Authentication service tenant has not been downloaded already.
For more information about tenant SAML 2.0 configuration, see Tenant SAML 2.0 Configuration.

Procedure
1. Log on to the tenant's administration console for the Identity Authentication service at https://<Your custom Identity
Authentication service tenant>.accounts.ondemand.com/admin as administration user.

2. In the navigation area, choose Applications & Resources Tenant Settings .

3. Choose SAML 2.0 Configuration.

4. Choose Download Metadata File (or download it directly from https://<Your custom Identity Authentication service
tenant>.accounts.ondemand.com/saml2/metadata).

5. Specify a file name and save it locally to your hard drive.

 Note
Specify a file name that you can easily recognize later, for example, metadataIDP<tentant-id>.xml, because you
need to download and upload multiple SAML metadata files later.

Configuring the Neo Account as SAML Service Provider and

Export SAML Metadata
Configure the Neo account as local SAML service provider.

Context

 Note
This is custom documentation. For more information, please visit SAP Help Portal. 51
 6/11/25, 2:37 PM
The following steps are only relevant if your developers will use SAP Web IDE in the Neo environment for UI development.

This configuration is needed for developer authentication in the Neo environment (Web IDE runs in the Neo environment).

In the SAML 2.0 communication, each account acts as a service provider. In this documentation, we use the term “local service
provider” to describe the account in SAP BTP as a service provider in the SAML 2.0 communication. You need to configure how the
local service provider communicates with the identity provider. This includes, for example, setting a signing key and certificate to
verify the service provider’s identity and encrypt data.

For more information, see Configure SAP BTP as a Local Service Provider.

Procedure
1. Log on to the SAP BTP cockpit as Neo administrator.

2. Go to the subaccount for the Neo environment.

3. In the SAP BTP cockpit, choose Security Trust .

4. On the Local Service Provider tab, choose Edit.

5. Change the configuration type from Default to Custom.

6. If the fields for the signing key and the signing certificate are already filled, leave them as they are and don't generate a new
key pair.

7. If the fields for the signing key and the signing certificate are empty, choose Generate Key Pair.

8. Set principal propagation to Enabled.

9. Leave the settings for force authentication as they are.

10. Choose Save and confirm the alert message.

11. If you haven't downloaded the SAML metadata file yet: Choose Get Metadata.

The metadata file is downloaded automatically.

12. Rename the downloaded file so that you can easily recognize it later on, for example, to metadataNeo<tentant-
id>.xml,

You must download and upload multiple SAML metadata files. Renaming the file helps you distinguishing the metadata files
from each other.

Results
You can now switch to the Application Identity Provider tab to import the SAML identity provider metadata.

Establishing Trust to the SAML Identity Provider for the Neo

Account
Import the SAML identity provider metadata to the Neo account to configure SAML trust to the identity provider (that is, the
Identity Authentication service tenant).

Prerequisites
You have downloaded the SAML identity provider metadata file from the Identity Authentication service tenant (see Exporting
SAML Identity Provider Metadata).

This is custom documentation. For more information, please visit SAP Help Portal. 52
 6/11/25, 2:37 PM

Context

 Note
The following steps are only relevant if your developers will use SAP Web IDE in the Neo environment for UI development.

You want to use Identity Authentication service as an SAML 2.0 identity provider. For more information, see Configure Trust to the
SAML Identity Provider.

Procedure
1. Log on to the SAP BTP cockpit as Neo administrator.

2. In the SAP BTP cockpit, navigate to the subaccount for the Neo environment.

3. In the navigation area, choose Security Trust .

4. Choose the Application Identity Provider tab.

5. Choose Add Trusted Identity Provider.

6. Choose Browse.

7. Upload the metadata file of the custom Identity Authentication service tenant.

 Note
During the setup of the ABAP environment, you need to upload multiple SAML metadata files. Make sure that you
upload the correct file. If you have followed the naming conventions suggested in this documentation, the file needed
here is metadataIDP<tentant-id>.xml.

8. Enter a description.

9. Choose Save.

Creating a Neo Application as Trusted Service Provider

Create and configure an application to represent the Neo account in the Identity Authentication Service tenant as SAML 2.0
service provider.

 Note
The following steps are only relevant if your developers will use SAP Web IDE in the Neo environment for UI development.

Creating an SAML Application for the Neo Account

As a first step, you need to create the application for the Neo account.

1. Log on to the tenant's administration console for the Identity Authentication service at https://<tenant
ID>.accounts.ondemand.com/admin as administration user.

2. In the navigation area, choose Application & Resources Applications .

3. Choose + Add.

4. Enter an application name for the Neo account (the service provider) in the Identity Authentication service.

5. Choose Save.

This is custom documentation. For more information, please visit SAP Help Portal. 53
 6/11/25, 2:37 PM

Configuring the Neo Application as Trusted Service Provider

Import the SAML service provider metadata from the Neo environment to the Identity Authentication service tenant (that is, the
SAML identity provider). This configures SAML trust to the Neo account as SAML service provider.

1. Under Applications, choose the entry for the Neo application that you have just created.

2. Choose SAML 2.0 Configuration.

3. Choose Browse.

4. Upload the metadata file of the SAML service provider from the Neo account that you have downloaded before (see also
Configuring the Neo Account as SAML Service Provider and Export SAML Metadata).

 Note
During the setup of the ABAP environment, you need to upload multiple SAML metadata files. Make sure that you
upload the correct file. If you have followed the naming conventions suggested in this documentation, the file needed
here is metadataNeo<tentant-id>.xml.

5. Choose Save.

Configuring the Subject Name Identifier Sent to Cloud Foundry

Configure the subject name identifier that the Identity Authentication service (as identity provider) sends to the Neo application.
Use the email address as user identifier for the Neo account.

1. Under Applications, choose the entry for the Neo application.

2. Choose Subject Name Identifier.

3. Choose Basic Configuration and select E-Mail from the dropdown list.

4. Choose Save.

Configuring the Default Name ID Format for the Neo Application (Optional)
Optionally, you can configure the default name ID attribute of the identity provider for Neo. Use the email address as user identifier
for the Neo account.

1. Under Applications, choose the entry for the Neo application in the Identity Authentication service.

2. Choose Default Name ID Format.

3. Choose the E-Mail radio button.

4. Choose Save.

Configuring the SAML Assertion Attributes for Cloud Foundry

Include the attributes first_name, last_name, mail, and Groups for the SAML assertion.

1. Under Applications, choose the entry for the Neo application.

2. Choose Attributes.

3. Choose Add to enter the following attributes (if they don't already exist):

This is custom documentation. For more information, please visit SAP Help Portal. 54
 6/11/25, 2:37 PM

Name Value

first_name First Name

last_name Last Name

mail E-Mail

Groups Groups

 Note
Make sure that you enter Groups (with upper case G), not groups, in the Name field, so that it matches the
assertation attribute used for the Neo environment.

4. Choose Save.

More Information
Configuring Applications

Configure Trust

Configure the Subject Name Identifier Sent to the Application

Enabling SAP Web IDE Full-Stack in the Neo Account

Enable the SAP Web IDE Full-Stack service in the Neo account if it is not yet enabled.

Context

 Note
You only need this step if your developers want to use SAP Web IDE as environment for UI development. As an alternative, you
can also use SAP Business Application Studio.

SAP Web IDE Full-Stack is a development environment to create new or extend existing SAP Fiori, SAPUI5, or hybrid applications.
For more information about the SAP Web IDE Full-Stack, see SAP Web IDE Full-Stack.

Procedure
1. Log on to the SAP BTP cockpit for the Neo environment as Neo administration user.

2. In the navigation area, choose Services.

3. Scroll down to the Web IDE Full-Stack tile.

4. If the service is not yet enabled, choose the Web IDE Full-Stack tile.

5. On the Service: Web IDE Full-Stack: Overview screen, choose Enable.

6. Wait for the status to change to the green Enabled status.

This may take a few minutes.

This is custom documentation. For more information, please visit SAP Help Portal. 55
 6/11/25, 2:37 PM

Creation of Developer Users for SAP Web IDE

If your developers want to use SAP Web IDE, use identity provider users for them to ease log on to the Neo enviroment.

If you have followed the steps for setting up a custom identity provider, you have already created a developer group in the tenant
for the Identity Authentication service (see also Setup of a Custom Identity Service). Now you need to create a developer group in
the Neo enviroment and map this group to the developer group in the tenant for the Identity Authentication service.

Creating a Neo Group for Developers

Define a Neo group to map the developer group of the identity provider to the DiDeveloper role of SAP Web IDE.

Context

 Note
The following steps are only relevant if your developers will use SAP Web IDE in the Neo environment for UI development.

For more information about roles, see Managing Roles.

Procedure
1. Log on to the SAP BTP cockpit (Neo account) as Neo administration user.

2. In the navigation area, choose Security Authorizations .

3. Choose the Groups tab.

4. Choose New Group.

5. Enter a group name, for example, Developers, and choose Save.

6. In the Roles screen area, choose Assign.

7. As subaccount, select the service provider account of the Web IDE, for example, sapwebide EU1.

8. As application, select the Web IDE application (di).

9. As role, select the predefined Web IDE developer role DiDeveloper.

10. Choose Save.

Mapping the Identity Provider Group Developers to the Neo

Group
Map the developer group of the identity provider to the Neo developer group with the Web IDE DiDeveloper role.

Context

 Note
The following steps are only relevant if your developers will use SAP Web IDE in the Neo environment for UI development.

The mapping is part of the trust configuration to the SAML identity provider. For more information, see Configure Trust to the
SAML Identity Provider.

This is custom documentation. For more information, please visit SAP Help Portal. 56
 6/11/25, 2:37 PM

Procedure
1. Log on to the SAP BTP cockpit (Neo account) as Neo administration user.

2. In the navigation area, choose Security Trust .

3. Choose the Application Identity Provider tab.

4. Choose the link for the custom identity authentication service tenant.

5. Choose the Groups tab.

6. If no group for Neo developers exists, choose Add Assertion-Based Group.

7. Enter the following data:

Option Description

Group Select Developers.

Mapping Rules (part 1) Enter Groups.

Mapping Rules (part 2) Select

equals.

Mapping Rules (part 3) Enter the developer group name from the Identity
Authentication service that was created by the administrator
for the Identity Authentication service, for example,
Developers.

If you are not the responsible administrator for the Identity

Authentication service, make sure that you are informed about
the group name (see also Creating an Identity Provider Group
for Developers).

8. Choose Save.

Getting Started as a Developer in the ABAP Environment

Learn about your first steps to get started as a developer in the ABAP environment.

 Note
This documentation informs you about the first steps as a developer and assumes that the necessary steps for setting up the
ABAP environment are done. For more information about how to set up the ABAP environment and getting started as an
administrator, see Getting Started with a Customer Account in the ABAP Environment.

Developing Applications: Overview

This image is interactive. Hover over each area for a description. Click highlighted areas for more information.

This is custom documentation. For more information, please visit SAP Help Portal. 57
 6/11/25, 2:37 PM

Please note that image maps are not interactive in PDF outputs.

1. Download and install ABAP Development Tools (ADT) from https://tools.hana.ondemand.com/#abap. See Video Tutorial:
Configure ABAP Development Tools .

 Note
SAP GUI is not supported in the ABAP environment. You can only use ADT as your development environment.

2. Create an ABAP cloud project with ADT to connect to the ABAP system in the ABAP environment (see Connect to the ABAP
System).

3. Develop your application (see Development in the ABAP Environment). To learn more about how to develop applications,
see Tutorial: Create Your First ABAP Console Application and Video Tutorial: Create Application .

More Information About Development in the ABAP Environment

For more information about ABAP development, see Development in the ABAP Environment.

Tutorial Overview

Getting Started

Mission

Build an SAP Fiori app Using the ABAP RESTful Application Programming Model

Create Database Table and Generate UI Service

Enhance the Business Data Model and Enable OData Streams

Enhance the Business Object Behavior With Unmanaged Internal Numbering

Enhance the Business Object Behavior With Determinations

Enhance the Business Object Behavior With Validations

Enhance the Business Object Behavior With Instance Action

Enhance the Business Object Behavior With Factory Action

Enhance the Business Object Behavior With Dynamic Feature Control

Write an ABAP Unit Test for the RAP Business Object

Group: Create and Expose CDS Views (Unmanaged Scenarios)

This is custom documentation. For more information, please visit SAP Help Portal. 58
 6/11/25, 2:37 PM
Create a Simple Database Table for ABAP Environment

Create and Expose Core Data Services Based on a Database Table

Add Transactional Behavior to Your Core Data Services

Group: Create an ABAP Core Data Services (CDS) View in SAP BTP ABAP Environment

Enhance an ABAP Core Data Services (CDS) View in SAP Business Technology Platform (BTP) ABAP Environment

ABAP Dictionary and ABAP Language

Group: Start Developing ABAP Tables

Create an ABAP Database Table and Relevant ABAP Dictionary Objects

Create ABAPDoc Comments in Your Class in ABAP Environment

Create an ABAP Managed Database Procedure (AMDP) and Analyze Its Performance

Analytics
Develop and Consume Queries on SAP Analytics Cloud

Develop Queries Based on Booking Supplement and Consume on SAP Analytics Cloud

Authorization Model
Group: Create Authorization Model with SAP BTP ABAP Environment

Create Data Model and Lock Object in SAP BTP ABAPEnvironment

Create Behavior and Service in SAP BTP ABAP Environment

Create Authorization Model and App in SAP BTP ABAPEnvironment

Maintain Business Roles and Access Restrictions in SAP BTP ABAPEnvironment

Business Configuration
Group: Create a SAP Fiori based Table Maintenance App

Create Business Configuration Maintenance Object

Providing Authorization Control for a Business Configuration Maintenance Object

Use Custom Business Configurations app

Explore additional features of the Business Configurations app

Lifecycle Management and CI/CD

Transfer Your ABAP Source Code With SAP Cloud Platform ABAP Environment via abapGit

Create Branches with SAP BTP ABAP Environment

Use Checkout Functionality of Branches to Switch Between Different Versions of Code

This is custom documentation. For more information, please visit SAP Help Portal. 59
 6/11/25, 2:37 PM
Transport a Software Component Between two Systems

Use abapGit to Transfer ABAP Source Code to the Cloud

Connect ABAP On-Premise to a Central Check System for Custom Code Migration Using ABAP Test Cockpit (ATC)

Cloud Operations
Monitor an SAP BTP ABAPEnvironment Service Using SAP Focused Run (FRUN)

Monitor an SAP BTP ABAPEnvironment Service Using SAP Cloud ALM (CALM)

Eventing
How to Create RAP Business Events in SAP BTP ABAPEnvironment

Event Consumption in ABAP Development Tools for Eclipse

How to Create RAP Business Events in an On-Premise System (In Progress)

Integration
Group: Expose an ABAP CDS View Externally Using a Communication Scenario

Expose a Standard Core Data Service for ABAP Environment

Maintain a Communication Arrangement for Inbound Communication

Mission: Get Data From an On-Premise System Using a Remote Function Call (RFC)

Get Data from an On-Premise System Using a Remote Function Call (RFC) Scenario

Remote Function Call (RFC) - Connect to Your On-Premise System from SAP BTP ABAPEnvironment

Test the Business API (BAPI) with an ABAP Console App

Get Data from an On-Premise System Using a Custom Entity

RFC: Inspect Your Class in the ABAP Debugger

RFC: Enhance the Handler Class With Filtering

Mission: Get Data from a Remote System Using an OData Service

Enable Connection From a Remote Instance of SAP BTP ABAPEnvironment

Prepare Consuming System and Create Service Consumption Model

Create Remote Client Proxy and ABAP Console App

Implement Custom Entity and Query Implementation Class

Mission: Connect to SAP S/4HANA Cloud with SAP BTP ABAP Environment

Create Communication System to Connect to SAP BTP ABAPEnvironment

Create Service Consumption Model for Business Partner and Sales Order Item Cube

Create Service Binding for Bonus Plan Scenario with SAP BTP ABAPEnvironment

This is custom documentation. For more information, please visit SAP Help Portal. 60
 6/11/25, 2:37 PM
without group/mission:

Call an External API and Parse the Response in SAP BTP ABAPEnvironment

Create RFC Proxy Class

Connect ABAP On-Premise to a Central Check System for Custom Code Migration Using ABAP Test Cockpit (ATC)

Using ODBC driver for SQL Service

Consume SOAP Based Web Services with SAP BTP ABAP Environment

Tools, User, Identity Management

Create an SAP Cloud Platform ABAP Environment Trial User

without group/mission:

Install ABAP Development Tools (ADT) and abapGit Plugin

Create a Developer User in SAP Cloud ABAP Environment

Provision Users into your SAP BTP ABAP Environment

UI Development
Develop and Run SAP Fiori Application With SAP Business Application Studio

Add the Shopping Cart Fiori Application to FLP

Add SAP BTP ABAP environment App to Portal Site

Developing and extending SAP Fiori Elements App

RAP Feature Showcase App

Create a Travel App with SAP Fiori Elements Based on OData V4 RAP Service

without group/mission:

Develop and Run SAP Fiori Application With Visual Studio Code

Develop SAP Fiori App & Deploy to Cloud Foundry Using SAP-managed App Router

Add Cloud Foundry to Portal Site

Set SAP BTP ABAP Environment as a ContentProvider for SAP Build Workzone, standard edition

Use Custom Themes in the SAP BTP ABAP Environment

SAP S/4HANA Cloud, ABAP Environment

Group: Develop an SAP Fiori App to Trigger Purchase Requisitions API

Create a Shopping Cart Business Object

Create Value Help, Enhance the Behaviour Definition and Behaviour Implementation of the Shopping Cart Business Object

Integrate released Purchase Requisition API into Online Shop Business Object

This is custom documentation. For more information, please visit SAP Help Portal. 61
 6/11/25, 2:37 PM
Develop a Custom UI with SAP S/HANA Cloud ABAP Environment

Integrate List Report into Fiori Launchpad

Without group/mission

Implement a Business Add-In (BAdI) to Check a Purchase Requisition

Implement a Field Control Using a Business Add-In (BAdI)

Create Custom Logic Using Key User Extensibility and Perform Trace

Create and Debug a BAdI Implementation in ABAP Development Tools (ADT)

Badges
Taster: Get Started with SAP BTP ABAP Environment

Level 1: Get to know the ABAP RESTfulApplication Programming Model

Level 2: Level up with SAP BTP ABAP Environment

Level 3: SAP BTP ABAP Environment: Intermediate Topics

Getting Started with Custom Code Analysis in the ABAP

Environment
Learn how to get started with Custom Code Analysis in the SAP BTP ABAP environment.

You want to use the SAP BTP ABAP environment to analyze your custom code remotely in your SAP ECC or SAP S/4HANA
systems? This documentation will help you gain insight into all the options to work with the ABAP Test Cockpit (ATC) in the SAP
BTP ABAP environment.

The following list covers all possible use cases and will guide you to the respective documentation chapters providing more details
on each use case.

1. ABAP Test Cockpit Configurator: Use this app to maintain ATC configurations using the SAP Fiori launchpad.

For more information on this app, see ABAP Test Cockpit Configurator.

To learn how to enable the app, see Enable Usage of the ABAP Test Cockpit Configurator App.

2. Custom Code Analysis: If you want to check your custom code in your on-premise system remotely using the SAP BTP
ABAP environment as the central check system, you need to set up the Custom Code Migration app on the SAP Fiori
launchpad.

To enable the Custom Code Migration app, see Enable Usage of the Custom Code Migration App.

To learn all about custom code migration, see the Custom Code Migration Guide for SAP S/4HANA 2023.

3. ATC Developer Scenario: You can use a system in the SAP BTP ABAP environment as a central check system to run ATC
checks from an on-premise system against this system. To do this, a number of configurations will be necessary.

To learn how to use the ATC as a central check system, see Configuring Remote ATC Using a Central Check System.

To learn how to set up the ATC developer scenario, see Configuring the ATC Developer Scenario.

This is custom documentation. For more information, please visit SAP Help Portal. 62
 6/11/25, 2:37 PM
4. Working with Exemptions: Learn about your options to exempt your ATC findings.

To learn how to enable the Approve ATC Exemptions app to be able to exempt the findings from your custom code analysis,
see Enable Usage of the Approve ATC Exemptions App.

For more information on the Approve ATC Exemptions app, see Approve ATC Exemptions.

5. Schedule Custom Code Analysis: The Schedule Custom Code Analysis app enables you to schedule projects created in the
Custom Code Migration app as application jobs. With this functionality, the analyses can be performed once or periodically.

To learn more about the app and how to enable it, see Schedule Custom Code Analysis.

6. Maintain the Baseline: In the Custom Code Migration app, it is now possible to maintain the ATC baseline. This means that
you can add/remove custom code project check results to/from the baseline​and choose whether you would like to exempt
your findings, suppress your findings or reduce their priority. After adding findings to the baseline, they won't appear in the
subsequent check results of the custom code project.

To learn more about the baseline functionality in the Custom Code Migration app, see Custom Code Migration.

Related Information
SAP BTP ABAP environment
Custom Code Analysis

Getting Started in the Kyma Environment

As an administrator, you must perform several steps to set up a fully operational Kyma environment to which you can connect the
chosen SAP solutions.

Prerequisites

To perform administrative and development tasks, you need a global account and one or several subaccounts for which you
can provision the Kyma environment. For details, see Creating a Kyma Instance.

The subaccount must have the following entitlements assigned:

Kyma environment (added by the subaccount manager)

Service Manager (added by default). However, if you removed the entitlement, you must add it again in your
subaccount

For details, see Configure Entitlements and Quotas for Subaccounts.

Procedure
1. Set up a Kubernetes cluster with the project "Kyma" to connect and extend SAP systems: Creating a Kyma Instance

2. Add the modules you'd like to use: Kyma Modules.

3. Assign the roles to users to allow the administrators to manage Kyma and the developers to create Functions: Assign Roles
in the Kyma Environment

 Caution
Assign the roles before the users start using the Kyma dashboard. Not granting the roles results in an error.

4. Use the Kyma environment to integrate external systems: Register an SAP Customer Experience System

This is custom documentation. For more information, please visit SAP Help Portal. 63
 6/11/25, 2:37 PM
You have the following options:

Integrate a CX system and the Kyma environment, so that the Functions you develop can use the system's API and
receive business events.

Integrate an SAP S/4 HANA Cloud system to use the services it provides to extend your applications.

After you've integrated externals systems, the developers can start working on their Functions.

5. Extend SAP S/4HANA Cloud by developing event-driven extensions and applications: Extending SAP S/4HANA Cloud in the
Cloud Foundry and Kyma Environment

6. Group several solutions into one formation to meet the requirements of your business scenario: Including SAP Systems in a
Formation

Results
You have set up the Kyma environment and connected it as required.

Next Steps
After the administrator has set up the Kyma environment, the developers can access it through the Kyma dashboard. After logging
on, developers can start creating extensions for the SAP systems either from the Kyma dashboard or from the terminal after
downloading the kubeconfig file with the cluster configuration. For details, see Development in the Kyma Environment.

Getting Started with an Enterprise Account in the Kyma

Environment
Quickly get started with an enterprise account in the Kyma environment using the SAP BTP cockpit.

Procedure
1. Get a global account.

After you’ve signed up for your enterprise account, you get an e-mail with a link to SAP BTP and the logon data as
administrator for the global account.

Log on to SAP BTP and navigate to your global account.

 Note
For more information on available plans, including free tier, see Available Plans in the Kyma Environment.

2. Set up your subaccount. For more information, see Create a Subaccount.

You can create more subaccounts to break down your account model and structure it according to your development
scenario. But first it's important you understand how to navigate to your accounts using the SAP BTP cockpit.

You can also download and use the SAP BTP command line interface (btp CLI) to create new subaccounts. See Download
and Start Using the btp CLI Client and Working with Global Accounts, Directories, and Subaccounts Using the btp CLI.

3. Create your Kyma environment. For more information, see Creating a Kyma Instance.

4. Configure your Kyma environment.

Now that you've set up your account model, it's time to think about member management. You can add members at
different levels:

For Kyma-specific role assignment, see Assign Roles in the Kyma Environment.

This is custom documentation. For more information, please visit SAP Help Portal. 64
 6/11/25, 2:37 PM
To learn more about how user roles are assigned in SAP BTP, have a look at User and Member Management.

5. Develop your applications and extend SAP solutions.

Check out Development in the Kyma Environment to learn more.

Related Information
Available Plans in the Kyma Environment

Getting Started with a Trial Account in the Kyma Environment

Quickly get started with a trial account in the Kyma environment.

Procedure
1. Get a global account.

Sign up for a free trial account. See Get a Free Trial Account. For more information about the scope of our trial offering, see
Trial Accounts and Free Tier .

For more information on available plans, including free tier, see Available Plans in the Kyma Environment.

2. Set up your subaccount.

When you register for a trial account, a subaccount is created for you.

If you want to create more subaccounts to break down your account model and structure it according to your development
scenario, see Create a Subaccount. But first it's important you understand how to navigate to your accounts using the SAP
BTP cockpit.

You can also download and use the SAP BTP command line interface (btp CLI) to create new subaccounts. See Download
and Start Using the btp CLI Client and Working with Global Accounts, Directories, and Subaccounts Using the btp CLI.

3. Create your Kyma environment. For details, see Creating a Kyma Instance and Enable Trial Kyma Environment.

4. Configure your Kyma environment.

Now that you've set up your account model, it's time to think about member management. You can add members at
different levels:

For Kyma-specific role assignment, see Assign Roles in the Kyma Environment.

To learn more about how user roles are assigned in SAP BTP, have a look at User and Member Management.

5. Develop your applications and extend SAP solutions.

Check out Development in the Kyma Environment to learn more.

You can also provide extensions for the SAP Commerce Cloud, SAP Cloud for Customer, and SAP Field Service
Management systems. For more information, read Extending SAP Solutions.

About the Trial Account

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

Trial Period
This is custom documentation. For more information, please visit SAP Help Portal. 65
 6/11/25, 2:37 PM
The trial account is valid for 90 days. During this time, you can explore and use the basic functionality of SAP BTP, Kyma runtime
for 14 days. After 90 days, your account is automatically deleted, and you’ll no longer be able to access your data. See Trial
Accounts and Free Tier to learn more about the trial periods.

Note that while your trial account is valid for 90 days, the Kyma environment that you create with it expires 14 days after its
creation and is then deleted permanently. To create a new Kyma environment, you must first disable the expired Kyma on your
subaccount. To learn how to do that, see Disable Expired Trial Kyma Environment.

 Caution
Once your account has expired, your cluster is deleted and all the cluster resources are removed. We recommend that you back
up your cluster configuration to restore it quickly if you choose to create a new Kyma environment.

Scope and Limitations

It's possible to provision only one Kyma environment per global account.

You can manage members in your trial account.

Kyma trial accounts are available in all SAP BTP regions.

A trial account provides you with a 1-node cluster with 4 vCPU and 16 GB of memory. An idle cluster without any customer
workload uses around 33% of vCPU and 33% of memory.

A trial account comes with a cluster with built-in eventing.

Events are processed in-memory and are not persisted to disk. Not delivered events will be lost on restart of the eventing
infrastructure.

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

Related Information
Trial Accounts and Free Tier
Assign Roles in the Kyma Environment

Setting Up Your Trial Account

Your global trial account is set up automatically, so that you can start using it right away. However, if one or more of the automatic
steps fail, you can also finalize the setup manually by following the steps below.

Create Your Trial Subaccount

The first thing that is needed in the setup of your trial account is the creation of a subaccount. If this step was successful in the
SAP BTP cockpit, you can directly skip to the next section.

Procedure
1. Navigate into your global account by choosing Enter Your Trial Account.

2. Choose New Subaccount.

3. Configure your trial account:

This is custom documentation. For more information, please visit SAP Help Portal. 66
 6/11/25, 2:37 PM

Field Input

Display Name trial

 Note
The value for this parameter is a sample one, you can
provide a name of your choice.

Description Optional

Provider Desired infrastructure provider

Region Desired region

Subdomain <your_id>trial

Example: P0123456789trial

Enable beta features Optional

Enables the use of beta services and applications.

Custom Properties Optional

You can use custom properties to identify and organize the

subaccounts in your global account. For example, you can filter
subaccounts by custom property in some cockpit pages.

Results
You have successfully set up your trial subaccount.

Add Entitlements
Once you have a subaccount (whether it was created automatically or you followed the steps described above), you need
entitlements to get your trial up and running.

Procedure
1. Navigate to your subaccount by choosing its tile.

2. Choose Entitlements from the left-hand side navigation.

3. Choose Configure Entitlements to enter edit mode.

4. Choose Add Service Plans and select all the service plans available for your subaccount.

 Note
To select a service plan, choose a service from the left and tick all the service plans that appear on the right. Do that for
all services.

5. Once you've added all the service plans, you see them all in a table. Before you choose Save, for all the plans with numerical
quota, choose  to increase the amount to the maximum (until the icon becomes disabled).

6. Finally, choose Save to save all your changes and exit edit mode.

This is custom documentation. For more information, please visit SAP Help Portal. 67
 6/11/25, 2:37 PM

Enable Trial Kyma Environment

After you’ve successfully added the entitlements, you can enable your trial Kyma environment and start developing.

Procedure
1. Navigate to your subaccount.

2. Create your Kyma environment. For details, see Creating a Kyma Instance.

3. Provide the name of your cluster and, optionally, a description.

Wait until the cluster is provisioned and you see the link to the Kyma dashboard.

4. Access the Kyma dashboard. For further information on the development options, see Development in the Kyma
Environment.

Results
Your trial Kyma environment is ready to use.

Disable Expired Trial Kyma Environment

After your trial Kyma environment has expired, you must disable it to remove all the data connected to the cluster from SAP
systems.

Procedure
1. Navigate to your subaccount.

2. In the Kyma Environment section of your subaccount overview, click Disable Kyma.

 Note
On deletion of the expired cluster, we attempt to delete the Service Instances that you created with the cluster. If we
cannot do that, you have to remove the Service Instances yourself before you disable such a Kyma Environment.

Extend Trial Kyma Environment

You cannot extend your trial Kyma environment. After your trial Kyma environment has expired, you must disable it on your
subaccount and enable it again to create a new cluster.

Procedure
1. Navigate to your subaccount.

2. Disable your expired Kyma environment.

3. After your Kyma environment has been successfully disabled, create a new Kyma environment.

Development
Develop and run business applications on SAP Business Technology Platform (SAP BTP) using our cloud application programming
model, APIs, services, tools, and capabilities.

This is custom documentation. For more information, please visit SAP Help Portal. 68
 6/11/25, 2:37 PM
SAP BTP supports multiple environments. It features a number of tools and programming languages that increase your flexibility
and freedom when developing applications. You can choose the environment that best suits your use cases and skill set and get to
work. You also have the possibility to integrate applications you’ve built with other solutions by SAP.

Environment options

Cloud Foundry Kyma ABAP

Benefits Simplified developer Take full advantage of the ABAP programming language
experience for business advanced features and rich
Fast prototyping with ABAP
application development ecosystem of Kubernetes
RESTful Programming Model
Large choice of programming Free choice of programming (RAP)
languages languages and models
Integrated development
(containerized deployments)
Intuitive “code-to-container” lifecycle
packaging and deployment, Combines microservices and
Reuse existing on-prem ABAP
managed by the platform serverless functions
assets
Platform-managed application Built-in, managed service mesh
security patching and updates based on Istio, and other cloud-
native open-source modules to
Automatic application routing,
reduce the development effort
load balancing, health checks,
and multilevel self-healing Built-in, managed event mesh

Support for CAP – an Managed infrastructure: day-2

opinionated business app operations, security patches,
development framework and updates

Full administrator access

Refined horizontal and vertical

automatic scalability

Dedicated application runtime

Zero downtime infrastructure

setup by default

Support for CAP – an

opinionated business app
development framework

Support for on-premise

connectivity

Additional Comparison: SAP BTP, Kyma Runtime Comparison: SAP BTP, Kyma Runtime Development in the ABAP
Information and SAP BTP, Cloud Foundry Runtime and SAP BTP, Cloud Foundry Runtime Environment

Shared
No infrastructure vendor lock-in
Benefits
Build scalable multitenancy business applications (SaaS)

Out-of-the-box consumption of SAP and hyperscaler services

Built on industry standards and open technology

Good For Managed build-on approach Open build-on approach User-centric process
extensions
Enterprise-grade business Enterprise-grade applications
applications and services Robust, transactional cloud
Cloud-native development of
applications
apps and services

This is custom documentation. For more information, please visit SAP Help Portal. 69
 6/11/25, 2:37 PM

Cloud Foundry Kyma ABAP

Cloud-native web applications Low latency infra-services Migrating and adapting add-
and services communication ons to the cloud

Scalable, microservice-based Reduced infrastructure Reusing existing on-premise

applications management effort ABAP code

Small to medium extensions Highly scalable, microservice- Enabling ABAP developers to

built with CAP/low-code based applications go to the cloud
tooling
Applications built with CAP

Skills Any major programming Kubernetes knowledge Ability to write modern ABAP
languages code
Docker
SAP Fiori/UI5 and SAP HANA Core data services
NodeJS or Python for
serverless functions SAP Fiori/UI5 and SAP HANA

Any major programming

language

SAP Fiori/UI5 and SAP HANA

We provide detailed information about developing, configuring, and deploying your applications depending on your preferred
environment and development approach.

Development in the Cloud Foundry Environment

Learn more about developing applications on the SAP BTP, Cloud Foundry environment.
Development in the ABAP Environment
Learn more about developing applications in the ABAP environment.
Development in the Kyma Environment
Learn more about developing applications in SAP BTP, Kyma runtime.

Related Information
SAP BTP Administrator's Guide
Developing with the SAP Cloud Application Programming Model
Consuming Services in SAP BTP

This is custom documentation. For more information, please visit SAP Help Portal. 70