## 2 Basic Platform Concepts
SAP BTP offers users the ability to turn data into business value, compose end-to-end business processes, and build and extend SAP applications quickly.
SAP Business Technology Platform is built on a multi-cloud foundation, which lets you choose from different infrastructures and runtimes. The services and solutions of SAP BTP are available on multiple cloud infrastructure providers, and it supports different runtimes, such as Cloud Foundry, ABAP, and Kyma, as well as multiple regions, and a broad choice of programming languages.
The central point of entry to the platform is the SAP BTP cockpit , where you can access your accounts and applications and manage all activities associated with them.
Relationship between SAP BTP Accounts and Associated Activities
<!-- image -->
## Solutions and Services
SAP BTP offers fast in-memory processing, sustainable, agile solutions and services to integrate data and extend applications, and fully embedded analytics and intelligent technologies.
Services enable, facilitate, or accelerate the development of business applications and other platform services on SAP BTP.
For a complete list of services and capabilities, see SAP Discovery Center: Services .
For more information, see Solutions and Services [page 16].
## Regions
You can deploy applications in different regions . Each region represents a geographical location (for example, Europe, US East) where applications, data, or services are hosted.
<!-- image -->
Regions are provided either by SAP or by our Infrastructure-as-a-Service (IaaS) partners Amazon Web Services (AWS), Microsoft Azure, Google Cloud, and Alibaba Cloud. The third-party region providers operate the infrastructure layer of the regions, whereas SAP operates the platform layer and Cloud Foundry.
A region is chosen at the subaccount level. For each subaccount, you select exactly one region (that is one data center).
For more information, see Regions [page 17].
## Environments
Environments constitute the actual platform-as-a-service offering of SAP BTP that allows for the development and administration of business applications. Environments are anchored in SAP BTP on subaccount level.
<!-- image -->
SAP BTP provides the following environments:
- Cloud Foundry Environment [page 57]
The Cloud Foundry environment enables you to develop new business applications and business services, supporting multiple runtimes, programming languages, libraries, and services. You can leverage a multitude of buildpacks, including community innovations and self-developed buildpacks.
## · ABAP Environment [page 76]
The ABAP environment allows you to create extensions for ABAP-based products, such as SAP S/4HANA Cloud, and develop new cloud applications. You can transform existing ABAP-based custom code or extensions to the cloud.
## · Kyma Environment [page 81]
SAP BTP, Kyma runtime provides a fully managed cloud-native Kubernetes application runtime based on the open-source project "Kyma". Based on modular building blocks, Kyma runtime includes all the necessary capabilities to simplify the development and to run enterprise-grade cloud-native applications.
- Neo Environment [page 98]
The Neo environment lets you develop HTML5, Java, and SAP HANA extended application services (SAP HANA XS) applications. You can also use the UI Development Toolkit for HTML5 (SAPUI5) to develop rich user interfaces for modern web-based business applications.
<!-- image -->
## Enterprise and Trial Accounts
SAP BTP provides different types of global accounts, enterprise and trial . The type you choose determines pricing, conditions of use, resources, available services, and hosts.
<!-- image -->
- A trial account lets you try out the platform for free. Access is open to everyone. Trial accounts are intended for personal exploration, and not for production use or team development. They allow restricted use of the platform resources and services.
For more information, see Trial Accounts and Free Tier [page 99].
- An enterprise account is usually associated with one SAP customer or partner and contains their purchased entitlements to platform resources and services. It groups together different subaccounts that an administrator makes available to users for deploying applications. For more information, see Enterprise Accounts [page 101].
## Commercial Models
SAP BTP offers two different commercial models:
<!-- image -->
- Consumption-based commercial model: Y our organization receives access to all current and future services that are eligible for this model. You have complete flexibility to turn services on and off and to switch between services as your business requires throughout the duration of your contract. This commercial model is available in the following flavors: SAP BTP Enterprise Agreement (SAP BTPEA), Cloud Platform Enterprise Agreement (CPEA), and Pay-As-You-Go for SAP BTP.
- For more information, see What Is the Consumption-Based Commercial Model? [page 104]
- Subscription-based commercial model: Y our organization subscribes only to the services that you plan to
- use. You can then use these services at a fixed cost, irrespective of consumption.
For more information, see What Is the Subscription-Based Commercial Model? [page 107]
## Account Model
The SAP BTP cockpit is structured according to global accounts, directories, and subaccounts:
<!-- image -->
- 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 [page 103]
- With directories , you can organize and manage your subaccounts according to your technical and business needs.
- In subaccounts , you deploy applications, use services, and manage your subscriptions. You can use them to manage members, authorizations, and entitlements. In the SAP BTP, Cloud Foundry environment, the subaccount is divided into one or more spaces, which is
- where application development, deployment, and maintenance take place.
For more information, see Account Model [page 111].
## Entitlements and Quotas
When you purchase an enterprise account, you're entitled to use a specific set of resources, such as the amount of memory that can be allocated to your applications.
<!-- image -->
- On SAP BTP, all external dependencies such as databases, messaging systems, files systems, and so on, are services . In this context, multitenant applications and environments are considered services. Each service has one or more service plans available. A service plan is the representation of the costs and benefits for a given variant of a particular service. For instance, a database may be configured with various "T-shirt sizes", each of which is a different service plan.
- An entitlement is your right to provision and consume a resource. In other words, entitlements are the service plans that you're entitled to use.
- A quota represents the numeric quantity of a service plan that you're entitled to consume in your global account and its subaccounts.
For more information, see Entitlements and Quotas [page 117].
## User and Member Management
On SAP BTP, user management takes place at all levels from global account to environment. There are different types of users, such as depending on their roles in the company.
User accounts enable users to log on to SAP BTP, access subaccounts, and to use applications according to the permissions granted to them. We distinguish between two types of users:
<!-- image -->
- Platform users are usually developers, administrators or operators who deploy, administer, and troubleshoot accounts, applications and services on SAP BTP.
- Business users use the applications that are deployed to SAP BTP. For example, the end users of SaaS apps or services, such as SAP Build Work Zone, or end users of your custom applications are business users.
Member management refers to managing permissions for platform users. A member is a user who is assigned to an SAP BTP global account or subaccount. Administrators can add users to global accounts and subaccounts and assign roles to them as needed. You can use predefined roles, for example the administrator role for managing subaccount members.
User management refers to managing authentication and authorization for your business users.
For more information, see User and Member Management [page 121].
## Tools, Programming Models, Programming Languages, and APIs
SAP BTP provides various programming languages and tools for your development project:
- SAP BTP includes many tools to help you develop and manage applications, and connect them to your on-premise systems. For more information, see Tools [page 136].
- SAP BTP supports many different programming languages; the availability of each depends on the development environment you're using. For more information, see Programming Languages [page 139].
- The SAP Cloud Application Programming Model offers a consistent end-to-end programming model that includes languages, libraries, and APIs that are tailored for full-stack development on SAP BTP. For more information, see Programming Models [page 139].
- Depending on your use case, you can choose between different offerings for continuous integration and delivery. For more information, see Continuous Integration and Delivery (CI/CD) [page 140].
- Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP. For more information, see APIs [page 143].