Activating pipelines from the SAP System
Integrating SAP development with modern Continuous Integration (CI) workflows is a powerful way to ensure code quality and streamline delivery. With the Build Framework, you can trigger a pipeline on your CI server directly from your SAP system.
One of the key features of the Build Framework is its ability to start a pipeline automatically when a Transport Request is released from an SAP Development System. This ensures that any new code changes are immediately validated for functionality, performance, and quality, helping teams catch issues early in the development cycle. By automating this step, you not only reduce manual overhead but also create a more reliable and repeatable release process.
On this page, you’ll learn how to activate the Business Add-In (BAdI) that enables this integration between your ABAP system and your CI/CD infrastructure. Whether you’re just beginning your CI journey with SAP or looking to optimize your existing setup, this guide will walk you through the necessary steps to get your pipelines running smoothly from within the SAP environment.
There are two points in time to choose from when to start the pipeline:
Trigger a Pipeline before the release of a Transport Request
This option intercepts the release sequence, initiates a pipeline, and cancels the transport export. An error message may appear indicating an abort, but rest assured that a pipeline is being initiated in the background.
The transport will ultimately reach the “release started” status, which is the expected outcome.
Upon successful completion of the pipeline, the release transport plug-in should be used to carry out the final export. Alternatively, if issues arise, the reopen transport plug-in must be engaged to revert the transport to a modifiable state.
Trigger a Pipeline after the release of a Transport Request
Initiate a pipeline upon the release of a transport, which subsequently conducts various checks based on the pipeline’s specific configuration. Typically, the pipeline is designed to alert the end user promptly in the event of any issues, thereby facilitating timely resolution.
BAdI Management
The two scenarios mentioned are controlled via Business Add-Ins (BAdIs) that are provided by SAP as standard.
You can access the BAdI Configuration screen directly via transaction code /BUILD/ENTRANCE
Within the configuration interface, the following options are available:
- Activate BAdI
This option displays a list of relevant BAdIs for the Build Framework. You can select a specific BAdI to activate. - Deactivate Current BAdI
This allows you to deactivate the currently active BAdI. - Show All BAdIs Related to the Build Framework
This displays all BAdIs associated with the Build Framework. - Show Documentation of BAdIs
This presents a list of relevant BAdIs for the Build Framework. Selecting one will allow you to view the documentation detailing the functions within the BAdI. - Add/Remove BAdIs Related to the Build Framework
This option directs you to the SE16 where you can add or remove additional BAdIs to tailor your process.
Note
Before the activation of a BAdI a pipeline must be properly defined and configured with the corresponding build plug-ins. Additionally, the pipeline must be incorporated into the build configuration as specified in transaction /BUILD/ENTRANCE (see Pipeline Trigger Configuration).
Choose the BAdI you want to work with by selecting it via the Button Activate BadI.
/BUILD/CHECK_BEF_REL
This BAdI will initiate a pipeline before a Transport Request is released.
The pipeline will not be initiated if there unresolved tasks within the transport request!
/BUILD/CHECK_AFT_REL
This BAdI will start a pipeline after the transport is released.
Both options involve evaluating various criteria before initiating the pipeline. The pipeline will not be activated under the following conditions:
- An exception has been granted to bypass the pipeline.
- The transport type is invalid.
- It is a local transport request.
- The transport lacks at least one existing repository object.
- The member is not included in the authorized list.
- There is no build script associated with the transported objects.
After activating a BAdI you should be able to see the selected BAdI in the Current Active BAdI field.
Now that you’ve activated the BAdI you’re well on your way to achieving a more efficient and automated delivery pipeline.
What’ Next
While triggering a build from within SAP is a popular option, it’s not the only one available! Depending on your architecture and project requirements, you may choose to trigger builds through alternative workflows or external systems. The flexibility of the Build Framework allows you to tailor the integration to suit your organization’s needs.
Ready to take the next step? Dive into advanced configuration options, explore integration with other tools, or start customizing your pipeline logic to support more complex workflows.