Best Practices: SAP BTP ABAP Environment

Introduction: 

This blog post summarizes the best practices for getting started with the SAP BTP ABAP environment (aka Steampunk). Further articles and blog posts are linked in the appropriate places so that more information is available there if required.  

The SAP BTP ABAP environment was developed to create cloud-enabled business applications, services and extensions. It offers the ABAP cloud development model that uses SAP HANA Cloud, SAP Fiori and a cloud-optimized ABAP language with standard APIs. Developers can use a toolset for tight integration with Git-enabled lifecycle management. 

The use of SAP BTP ABAP environment offers 3 key benefits:

It enables a side-by-side extension option for the custom extension of SAP S/4HANAThe cloud transformation can be accelerated by using reusable ABAP assets to create innovative solutions for the cloudKeep the core clean, the on-premise custom code is kept on another decoupled platform, where you can profit from independent and regular release cycles

The following graphic shows the four different areas of use of the SAP BTP ABAP environment. Individual adaptations for each interest group are possible for each part so that the best possible benefit is achieved. 

SAP BTP ABAP Environment Positioning

Development

You can simply connect the ABAP Cloud system to Eclipse so that you can use the ABAP Development Tools (ADT) provided there to develop the ABAP Cloud apps. Build your own OData services using the ABAP RESTful application programming model optimized for SAP HANA Cloud. You can also analyze the ABAP code with advanced custom code migration tools and evaluate the effects of conversion to SAP S/4HANA, migration to SAP BTP or during the clean core journey. 

Administration and Integration

Administrative tasks such as user management and security setup can be performed via the role-based SAP Fiori Launchpad. Create extension projects between ABAP Cloud and other SAP Build tools, and easily integrate with existing on-premises systems and any SAP S/4HANA systems. You can also use third-party services that are based on HTTP. 

The central aspect of the SAP BTP ABAP environment is the broad range of data centers globally provided. You can choose from a total number of more than 20 data centers, a list of all of them can be found in the SAP Discovery Center. The number and therefore the variety will continue to increase, and further locations are planned and will soon be available. All other upcoming features can be found in the roadmap and the what’s new page for the SAP BTP ABAP environment in the SAP Help Portal. In addition, there is already a blog post in which the upgrade window for next year’s releases is listed and you can find information regarding the Cloud System Notification Subscriptions (CSNS).

The Landscape Portal is part of the SAP BTP ABAP environment offering and acts as a central tool to perform system administration (for example system hibernation), manage lifecycle operations, and facilitate the configuration and deployment of multitenant SaaS solutions.  

Choosing Your Starting Point: The Free Tier Option 

It is important to note at the initial stage that it is not necessary to create all the systems at once, but only those that are needed at the time. On the one hand, this ensures clarity and, on the other, saves unnecessary costs.  

We recommend using the Free Tier option for your first contact with this system. This allows you to try out everything free of charge and then decide whether you want to continue using it. This offer can be used for a maximum of 90 days. 

Setting Up Your System: Step-by-Step Guide 

The next step is the creation of a software component as a delivery unit for your project, this is possible via the SAP Fiori Launchpad. The free tier system can be converted into a standard plan development system, so that all projects and created files can be transferred. It is of course also possible to create a development system directly. The SAP BTP Cockpit is generally used for the system creation. 

With the ABAP Development Tools (ADT) for Eclipse, all items can be developed as usual and released using the transport requests. 

Once development is complete, a test system can be created via the SAP BTP Cockpit. The software components can then be pulled into the test system in the SAP Fiori Launchpad. 

Best Practices for System Management  

A subaccount to create a system is required. We recommend creating a separate subaccount for each system. This ensures maximum flexibility, for example with the trust settings. All information about Cloud Foundry and the required accounts and spaces can be found in the SAP Help Portal.

The next step is to define a region in which the system is located. There are three different hyperscalers to choose from, which are represented in more than 20 data centers worldwide. 

And each system must be assigned to a Cloud Foundry Space. Here too, it is recommended to use a Cloud Foundry Space for only one system to create a better overview. 

Optimizing Costs: Sizing and Hibernation Tips  

All systems should initially be created with the minimum size, one ACU (ABAP Compute Unit) and 2 HCUs (HANA Compute Unit). This usually provides sufficient coverage, as one ACU can serve around 1,000 active business users per day. These are the only two metrics that are relevant for this. The size can of course be easily changed and adapted at a later stage vie the SAP BTP Cockpit. An overview of the prices can be found in the SAP Discovery Center, where the ACUs and HCUs are also explained in more detail. 

If the system has more than just the minimum size available, it is possible to use the elastic scaling. The resources are adjusted and automatically scaled based on the required workload. To be able to use this functionality, the BTPEA Commercial Model is required. 

The default setting when creating a system is a development system, but if you want to create a test or productive system, you must uncheck this box. To distinguish between the different systems, you can assign them a descriptive ID in the “ABAP System ID” field. 

The system hibernation function can be used to save further costs. This function is suitable for stopping development systems outside working hours, for example at weekends, starting test systems only when they are needed or starting the productive system only when it goes live. It can simply be started up via the Landscape Portal. 

A detailed cost analysis for customers can be found in this blog post. 

Recommended System Landscapes: Finding the Right Fit 

The various landscapes are only briefly explained here, detailed descriptions can be found in the documentation. When setting up the systems, we recommend that you only start with the system that is currently required. It is not necessary to set up the entire system landscape directly. It is sufficient if only the development system is set up first and then the test or production system as soon as the need is met. On the one hand, this provides a better overview at the beginning and on the other hand, costs can be reduced. 

3-System Landscape 

This landscape consists of a development system, a quality assurance system and the production system. This allows the tests of new developments to be tested directly in parallel and ensures that the application is also executable in non-development systems. 

5 System Landscape 

In this scenario, the code lines for development and corrections can be handled separately. The correction system and the test system are on the same level as the production system. This means that the respective corrections can be tested before they are imported into the production system. To develop larger releases and code parts, there is an actual development system. There is also the corresponding test system. Urgent corrections can be implemented directly and have no influence on the normal development cycle. 

Note: At this point you can use the system hibernation function, because if it is not necessary to enter corrections frequently, the correction system and the associated test system can be shut down and thus also save costs. If there is a need for these systems, they can simply be started up again. A detailed explanation of the system hibernation can be found in this blog post. 

This learning journey  can give you an overview of how to create an ABAP environment on the SAP BTP or you can attend our monthly Customer and Partner Roundtable. Among other topics, new product features are presented in this meeting, live demos are shown by experts or you have the opportunity to ask questions live. To register for the roundtable, please follow the SAP Community for SAP BTP ABAP Environment, where the next date will be announced in a blog post and registration details will be provided. If you have missed a roundtable or would like to look at past ones again, you can find them on GitHub, where the respective slides are also available. 

Hopefully this blog post has given you a clear introduction to the SAP BTP ABAP environment. 

​ Best Practices: SAP BTP ABAP EnvironmentIntroduction: This blog post summarizes the best practices for getting started with the SAP BTP ABAP environment (aka Steampunk). Further articles and blog posts are linked in the appropriate places so that more information is available there if required.  The SAP BTP ABAP environment was developed to create cloud-enabled business applications, services and extensions. It offers the ABAP cloud development model that uses SAP HANA Cloud, SAP Fiori and a cloud-optimized ABAP language with standard APIs. Developers can use a toolset for tight integration with Git-enabled lifecycle management. The use of SAP BTP ABAP environment offers 3 key benefits:It enables a side-by-side extension option for the custom extension of SAP S/4HANAThe cloud transformation can be accelerated by using reusable ABAP assets to create innovative solutions for the cloudKeep the core clean, the on-premise custom code is kept on another decoupled platform, where you can profit from independent and regular release cyclesThe following graphic shows the four different areas of use of the SAP BTP ABAP environment. Individual adaptations for each interest group are possible for each part so that the best possible benefit is achieved. SAP BTP ABAP Environment PositioningDevelopmentYou can simply connect the ABAP Cloud system to Eclipse so that you can use the ABAP Development Tools (ADT) provided there to develop the ABAP Cloud apps. Build your own OData services using the ABAP RESTful application programming model optimized for SAP HANA Cloud. You can also analyze the ABAP code with advanced custom code migration tools and evaluate the effects of conversion to SAP S/4HANA, migration to SAP BTP or during the clean core journey. Administration and IntegrationAdministrative tasks such as user management and security setup can be performed via the role-based SAP Fiori Launchpad. Create extension projects between ABAP Cloud and other SAP Build tools, and easily integrate with existing on-premises systems and any SAP S/4HANA systems. You can also use third-party services that are based on HTTP. The central aspect of the SAP BTP ABAP environment is the broad range of data centers globally provided. You can choose from a total number of more than 20 data centers, a list of all of them can be found in the SAP Discovery Center. The number and therefore the variety will continue to increase, and further locations are planned and will soon be available. All other upcoming features can be found in the roadmap and the what’s new page for the SAP BTP ABAP environment in the SAP Help Portal. In addition, there is already a blog post in which the upgrade window for next year’s releases is listed and you can find information regarding the Cloud System Notification Subscriptions (CSNS).The Landscape Portal is part of the SAP BTP ABAP environment offering and acts as a central tool to perform system administration (for example system hibernation), manage lifecycle operations, and facilitate the configuration and deployment of multitenant SaaS solutions.  Choosing Your Starting Point: The Free Tier Option It is important to note at the initial stage that it is not necessary to create all the systems at once, but only those that are needed at the time. On the one hand, this ensures clarity and, on the other, saves unnecessary costs.  We recommend using the Free Tier option for your first contact with this system. This allows you to try out everything free of charge and then decide whether you want to continue using it. This offer can be used for a maximum of 90 days. Setting Up Your System: Step-by-Step Guide The next step is the creation of a software component as a delivery unit for your project, this is possible via the SAP Fiori Launchpad. The free tier system can be converted into a standard plan development system, so that all projects and created files can be transferred. It is of course also possible to create a development system directly. The SAP BTP Cockpit is generally used for the system creation. With the ABAP Development Tools (ADT) for Eclipse, all items can be developed as usual and released using the transport requests. Once development is complete, a test system can be created via the SAP BTP Cockpit. The software components can then be pulled into the test system in the SAP Fiori Launchpad. Best Practices for System Management  A subaccount to create a system is required. We recommend creating a separate subaccount for each system. This ensures maximum flexibility, for example with the trust settings. All information about Cloud Foundry and the required accounts and spaces can be found in the SAP Help Portal. The next step is to define a region in which the system is located. There are three different hyperscalers to choose from, which are represented in more than 20 data centers worldwide. And each system must be assigned to a Cloud Foundry Space. Here too, it is recommended to use a Cloud Foundry Space for only one system to create a better overview. Optimizing Costs: Sizing and Hibernation Tips  All systems should initially be created with the minimum size, one ACU (ABAP Compute Unit) and 2 HCUs (HANA Compute Unit). This usually provides sufficient coverage, as one ACU can serve around 1,000 active business users per day. These are the only two metrics that are relevant for this. The size can of course be easily changed and adapted at a later stage vie the SAP BTP Cockpit. An overview of the prices can be found in the SAP Discovery Center, where the ACUs and HCUs are also explained in more detail. If the system has more than just the minimum size available, it is possible to use the elastic scaling. The resources are adjusted and automatically scaled based on the required workload. To be able to use this functionality, the BTPEA Commercial Model is required. The default setting when creating a system is a development system, but if you want to create a test or productive system, you must uncheck this box. To distinguish between the different systems, you can assign them a descriptive ID in the “ABAP System ID” field. The system hibernation function can be used to save further costs. This function is suitable for stopping development systems outside working hours, for example at weekends, starting test systems only when they are needed or starting the productive system only when it goes live. It can simply be started up via the Landscape Portal. A detailed cost analysis for customers can be found in this blog post. Recommended System Landscapes: Finding the Right Fit The various landscapes are only briefly explained here, detailed descriptions can be found in the documentation. When setting up the systems, we recommend that you only start with the system that is currently required. It is not necessary to set up the entire system landscape directly. It is sufficient if only the development system is set up first and then the test or production system as soon as the need is met. On the one hand, this provides a better overview at the beginning and on the other hand, costs can be reduced. 3-System Landscape This landscape consists of a development system, a quality assurance system and the production system. This allows the tests of new developments to be tested directly in parallel and ensures that the application is also executable in non-development systems. 5 System Landscape In this scenario, the code lines for development and corrections can be handled separately. The correction system and the test system are on the same level as the production system. This means that the respective corrections can be tested before they are imported into the production system. To develop larger releases and code parts, there is an actual development system. There is also the corresponding test system. Urgent corrections can be implemented directly and have no influence on the normal development cycle. Note: At this point you can use the system hibernation function, because if it is not necessary to enter corrections frequently, the correction system and the associated test system can be shut down and thus also save costs. If there is a need for these systems, they can simply be started up again. A detailed explanation of the system hibernation can be found in this blog post. This learning journey  can give you an overview of how to create an ABAP environment on the SAP BTP or you can attend our monthly Customer and Partner Roundtable. Among other topics, new product features are presented in this meeting, live demos are shown by experts or you have the opportunity to ask questions live. To register for the roundtable, please follow the SAP Community for SAP BTP ABAP Environment, where the next date will be announced in a blog post and registration details will be provided. If you have missed a roundtable or would like to look at past ones again, you can find them on GitHub, where the respective slides are also available. Hopefully this blog post has given you a clear introduction to the SAP BTP ABAP environment.    Read More Technology Blogs by SAP articles 

#SAP

#SAPTechnologyblog