Developing with SAP Extension Suite

SAP BTP Account Model

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain the account model

SAP Business Technology Platform Account Model

Usage Scenario

Your company has ordered and received a global account in SAP Business Technology Platform () to use services from there. To understand the basics, you need to familiarize yourself with the account model.


is an integrated offering comprising four technology portfolios:

  • Database and data management
  • Application development and integration
  • Analytics
  • Intelligent technologies

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

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

Global Accounts

A global account is the realization of a contract you 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.


Subaccounts let you structure a global account according to your organization’s and project’s requirements with regard to members, authorizations, and entitlements. A global account can contain one or more subaccounts in which you deploy applications, use services, and manage your subscriptions. Subaccounts in a global account are independent of each other. This is important to consider with respect to security, member management, data management, data migration, integration, and so on, when you plan your landscape and overall architecture.

Regions and Environments

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

Each environment comes equipped with the tools, technologies, and runtimes that you need to build applications. The availability of different environments allows for greater flexibility in your development process.

The following environments are available: Cloud Foundry Environment, ABAP Environment, Neo Environment, and KYMA Environment.

Basic Platform Concepts

If your global account is on cloud management tools, feature set B, the new hierarchical element called directory is introduced, which is essentially a grouping of subaccounts. Furthermore, subaccounts can have multiple environments.

The figure below depicts the relationship between a global account, its directories, subaccounts, environments, regions, entitlements, and quotas for feature set B.

A subaccount is specified for the environment Neo or for the environment Multi-Environment (KYMA, ABAP and Cloud Foundry environment).

: Different Account Model Examples

To create a staged development environment, your account model can be built on functional areas.

Using this account model, you can distribute the subaccount administration to several teams, which allows for easy scaling as the number of cloud projects grows while still having a manageable amount of maintenance and governance efforts. If possible, consider assigning responsible colleagues to each group of three subaccounts, i.e. to each account landscape.

Create directories per location or subsidiary.

In this account model, you create different directories for geographical areas. Additionally, for example, you can create custom properties for subaccounts that belong to the same departments in those locations.


You have now become familiar with the account model and its basic concepts and know how the terms global accounts, subaccounts, regions and environments are related.

Save progress to your learning plan by logging in or creating an account