Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
This blog will be a helpful insight for any architect or development project lead. Recently I had come across many companies and organization who are looking for cloud application. SAP has been changing its cloud platform offerings. The word cloud has been around SAP world from 2012 it was SAP HCP (HANA Cloud Platform) product then came to know as SCP (SAP Cloud platform) now its SAP BTP (Business Technology Platform). This article will give an insight how to plan and setup landscape to manage the lifecycle of cloud applications by knowing the features SAP BTP provides.



The SAP Cloud cockpit is organized according to global account, subaccounts, and directories.

Global account is the contract made with SAP. It is used to manage sub accounts, members, entitlements, and quotas. The entitlements and quotas received in global account is distributed to the subaccount. So not all quotas in global account are available in all sub accounts.

For instance: - 1 quota Kyma is available in global account and 2 subaccounts let’s say US East & Europe (Netherlands) are available under the global account. Then Kyma environment can be enabled only in one of the subaccounts it cannot be used in both subaccounts.

One or more subaccounts can be created under a global account. Subaccount are independent from each other. Each subaccount has its own region. Regions are provided by SAP or IaaS partners AWS, Microsoft Azure, GCP and Alibaba Cloud. This region represents a geographical location where application, data or services are hosted.

The applications performance can be optimized by selecting a region that’s geographically close to Users. Also choosing region depends on other factors like services available in region, country, or industry specific security requirements.

  1. Cloud Foundry Environment

  1. ABAP Environment

  1. Kyma Environment

The environment is available for each subaccount. SAP BTP supports different environments:

  • Cloud Foundry

  • ABAP

  • Kyma

These environments support wide choice of programming languages. Environment comes equipped with tools, technologies that is required for building application. We can develop our application in either of the environment utilizing different service quotas available. The business user will be able to access the application once its published.

Below are the tools and languages which I had come across for application development.


SAP BTP provides many tools that help to develop and manage applications. Also enables to connect applications to on-premise systems.

Programming Languages


SAP BTP allows to consume and publish API. These API allow us to access the data that is required for our application. We can build our own or consume the existing ones with subscription.

  • SAP API Business Hub – Browse and access APIs from SAP and partners. Test API with mock data in SAP system.

  • SAP API Management – Build, Manage and Publish the APIs


Over the past years I have tried most of the services in SAP Cloud platform, the architecture changes like Entitlements and Kyma environment are new in SAP BTP. In future many companies will be leveraging the SAP BTP platform for innovation solutions. The lifecycle management of cloud application in Cloud Foundry Environment or ABAP Environment or Kyma Environment are possible using SAP BTP Best practice. I have tried to cover my understanding on the platform services and capabilities on SAP BTP. The programming model that includes languages, libraries and APIs required for a full stack development is offered by SAP BTP.
Labels in this area