CYPIRE

ABAP Build Framework Setup

A digital tunnel symbolizing a technical environment with light at the end, representing minimal infrastructure requirements for the ABAP Build Framework Setup and Environment.

Environment and Requirements for the ABAP Build Framework

Getting started with ABAP Build Framework is straightforward and requires minimal setup.
Essentially you need your SAP system respectively your SAP transport landscape and a CI server to orchestrate your pipelines.

The best part? The SAP Build Framework is a standard SAP component, so it’s already preinstalled in your ABAP system, ready for you to use.

To enhance your workflow, consider integrating an SCM (Source Code Management) system. This will help you manage your code and pipeline more efficiently.

Additionally, you can incorporate an Issue Tracker of your choice into the process to meet all change management requirements. The ABAP Build Framework facilitates a robust change request process and ensures every change in your SAP landscape is well-documented.

Remember, the framework is designed to be flexible and can be adapted to suit your specific needs.

Let’s dive in to ensure that you meet the necessary prerequisites for using the ABAP Build Framework!

SAP System (ABAP Server)

The Build framework is conveniently delivered with SAP_BASIS component. Ensure you have at least the following Service Pack (SP) levels installed:

SAP BasisSP Level
7.5022
7.5113
7.5209
7.5307
7.5405
7.55 and above00

SAP regularly updates the Build Framework and its plugins, so it’s advisable to check for newer releases.

Simply reference the SAP Note 3141309 – ABAP Build Framework TCI overview. SAP provides a list of the various releases in this note, along with references to the specific TCI Notes. To access the latest features and improvements, implement the highest available TCI from this list.

To transfer Transport Requests across your SAP landscape, it’s essential that the SAP systems are part of a Transport Domain, of course.

Security

Considering security related requirements you might want to check the following SAP Notes:

CI Server

Continuous integration (CI) servers have become a crucial component of any successful software delivery project. With the widespread adoption of agile methodologies and Continuous Delivery practices, CI servers have taken center stage in the development lifecycle.

Animated GIF showing the the requirements and environment of the ABAP Build Framework interacting with a CI server. In this Setup the CI Server triggers actions like creating, releasing, or importing Transport Requests in SAP.


CI servers automate the integration and testing of code changes.
This automation helps in identifying and resolving integration issues early, thereby reducing the risk of bugs and conflicts. Key functions of CI servers include:

  • Automated Testing
    Running unit tests, integration tests, and other types of tests to ensure code quality.
  • Deployment Automation
    Facilitating the deployment of applications to various environments, such as staging and production.
  • Notification and Reporting
    Providing feedback to developers about the status of builds and tests.

To trigger the ABAP Build Framework, you can use any CI server or tool which can start HTTP(S) requests, including popular choices like Jenkins, GitLab CI, and GitHub Actions.

Source Code Management (SCM)

A Source Code Management (SCM) system is a software platform that helps developers manage changes to code, collaborate with others, and maintain different versions of their codebase over time. It allows multiple developers to work on the same codebase simultaneously, tracking changes, and identifying who made them. SCMs also provide features like branching, merging, and version control, ensuring that changes are properly recorded and can be rolled back if needed.

It is not mandatory for the operation of the ABAP Build Framework, but it can still be helpful to manage the CI configuration and scripts. Popular choices are GitLab, GitHub or Bitbucket.

Change Control

The ABAP Build Framework offers extensive control over the entire pipeline, including the underlying ABAP transports, through integration with a third-party tool. While such integration is optional and not required for utilizing CI/CD pipelines, it streamlines workflows and enhances communication & documentation among all stakeholders. This integration spans from requirements gathering with approval workflows to technical documentation, and facilitates direct linking to other changes, support incidents, or test cases.

Animated GIF showing the integration of change control with an issue tracker and CI server in the ABAP Build Framework. The workflow triggers actions like creating, releasing, or importing Transport Requests in SAP

To achieve this, you can use any issue tracker capable of sending a HTTP(S) request. Chances are, you already have such a tool in place!

An issue tracker is a software tool that helps developers and project managers track bugs, tasks, and feature requests throughout the software development lifecycle. It enables teams to log, prioritize, assign, and monitor the progress of issues. Popular examples of issue tracking tools include Jira, OpenProject, Taiga, GitHub Issues, and Trello.

To conclude, the ABAP Build Framework offers a streamlined and efficient way to manage your SAP landscape with minimal setup requirements. By leveraging your existing SAP system and a CI server, you can quickly implement a robust CI/CD pipeline. The flexibility of the framework allows you to adapt it to your specific needs, ensuring a tailored approach to your change management and documentation processes.

For detailed guidance on setting up the communication between your systems, please refer to the following resources: