The ABAP Platform on SAP HANA 2.0 provides a great platform for trying out the ABAP language and toolset. It is extensively pre-configured with Fiori launchpad, SAP Cloud Connector, SAP Java Virtual Machine, pre-configured backend /frontend connections, roles, and sample applications.
This solution is intended for two groups of developers:
- Non-ABAP developers, who are interested in learning more about the ABAP language and development tools
- ABAP developers, who are interested in learning about version 7.54
How to get it: NEW Docker Image
We now provide everything you need in one Docker image. This means that you no longer have to set up a virtual machine, Linux distro, and ABAP server.
Get it here: SAP ABAP Platform 1909, Developer Edition
Setup instructions are also available.
You will need to register with DockerHub.
You will need:
- Either: a Docker for Desktop installation, for Windows or Mac.
- Or Docker Engine for Linux, e.g. Ubuntu.
During installation, you will need to read and accept the SAP Software End User License Agreement. A link is provided here for your convenience: SAP Software End User License Agreement.
Additional products and material: SAPGUI for Windows / SAPGUI for Java, Readme, miniSAP License
All available in SAP Developers Trials and Downloads .
Highlights of the 1909 Edition
ABAP RESTful Application Programming Model (RAP)
The ABAP RESTful Application Programming Model (short: RAP) offers developers an efficient way to build enterprise-ready, SAP HANA-optimized, OData-based Fiori UI services and Web APIs in the cloud as well as on-premise. It is the evolutionary successor to the ABAP Programming Model for SAP Fiori.
For more information, see:
- The blog post Getting Started with the ABAP RESTful Application Programming Model (RAP), by Carine Tchoutouo Djomo
- The SAP Help Portal: ABAP RESTful Application Programming Model
Git-Enabled Change and Transport System (gCTS)
A new way of transporting objects, gCTS enables you to use Git to store your ABAP development objects. gCTS makes use of special Git features, such as working on local copies of a central remote Git repository. Software development takes place in the usual editors like ABAP Development Tools (ADT). Changes to objects are still recorded in transport requests. Current states of objects can be pushed to remote Git repositories, either by releasing a transport request or while you’re working.’
For the official documentation overview, see: Git-Enabled Change and Transport System
The official documentation for configuration, Configuring Git-enabled Change and Transport System contains three steps. However, we have preconfigured the first two, so you only have to complete the third, Configure Repositories.
Some certificates are already available. If you would like to connect to your own GitHub server or to a provider other than github.com, you have to add the appropriate certificates to the ABAP system in transaction STRUST. The configuration has been done for the default user ‘DEVELOPER’.
To get started with gCTS, simply open the gCTS app in the SAP Fiori Launchpad (FLP).
If you are a SAP customer, partner, or employee, the following SAP Note provides additional information: SAP Note: 2821718 . However, the essential configuration has already been done for everyone.
Custom Code Migration with the ABAP Test Cockpit (ATC)
We actually introduced this in AS ABAP 7.52 SP04, Developer Edition and it was very popular, so we decided to include it again. Basically,we’ve preconfigured the developer edition to run as a central check system for those checks. You can test this out of the box locally in SAP ADT, then configure the rest of your landscape to work with it.
This is particularly useful for SAP S/4HANA Readiness Checks and SAP Cloud Readiness Check.
For more general information on ATC, see these two excellent blogs, by Olga Dolinskaja:
SAP Cloud Connector
SAP Cloud Connector provides a link between SAP Cloud Platform applications and on-premise systems. It runs as on-premise agent in a secured network; acts as a reverse invoke proxy between the on-premise network and SAP Cloud Platform; and lets you use existing on-premise assets without exposing the entire internal landscape.
If you are interested in connecting your developer edition with a licensed version of SAP Cloud Platform, ABAP Environment (aka “Steampunk”), I have written a tutorial mission on this: Connect Your On-Premise System with SAP Cloud Platform, ABAP Environment
For more information, see:
- SAP Help Portal, SAP Cloud Platform Connectivity: SAP Cloud Connector
- SAP Community blog post (third-party content): SAP Cloud Platform Cloud Connector – A Brief Guide for Beginners
Yes, abapGit is available out of the box.
Documentation is here: abapGit Documentation
If you are not yet familiar with abapGit, this post by Graham Robinson is a great introduction, with how-to videos:
Other Highlights of ABAP Platform 1909: Overview
Official slide deck for ABAP Platform in SAP S/4HANA 1909 – Overview and Product Highlights.
FAQ and Troubleshooting
I have also started compiling FAQ and Troubleshooting – so if you have any questions, please check there first.
Note: From now on, please DO NOT post a blog comment if you require troubleshooting.
Please post on the ABAP Development forum : ABAP Development: Ask a Question , using the hashtag #ABAP_Trial.
If it’s a problem downloading the files, rather than installing the downloaded files, again please post a question, including #ABAP_Trial and your country / region.
(We now have 9 blog posts referring to 3 different versions of the download developer edition:
- Very few people follow these blog posts, so you will not get help from the vast majority of the community
- It makes it difficult for other users to find similar issues in future, which leads to many duplicated errors
- There is no capacity to monitor all blogs for all released versions)
Thank you for your understanding.
Guides and Tutorials
If you’re not sure where to start with your new system, we have written several tutorials.
FAQ and Troubleshooting also contains some info on Cookbook-style projects, where Community members have described projects involving different versions of the developer edition.