SAP-samples/s4hana-gcts-badi
A BAdI implementation that wires the ABAP transport organizer to gCTS, so releasing a transport task also commits it to Git and registers the release.
Git-enabled Change and Transport System (gCTS) lets ABAP change and transport management use a Git repository as its external version store, but the classic transport-organizer flow does not call it on its own. This BAdI plugs into that flow so that releasing a task also commits to the connected Git repository and registers the release with the gCTS Registry, task-based rather than at the transport level. It requires SAP S/4HANA 2020 SPS2 or later, gCTS already configured, and SAP Note 3204481 to avoid missing objects when importing into a repository with a subdirectory.
Facts
Where it sits
Who is behind it
In the atlas: maintains 222@SAP-samplesmaintainerAjinkya PatilContributes to this
In the atlas: contributes to 112@ajinkyapatil8190Martin BredyContributes to this
In the atlas: contributes to 1@martin-bredySarat KrishnanContributes to this
In the atlas: contributes to 1@sarat-krk3 contributors
What it declares
Every artifact
- Type
- Sample
- Origin
- By SAP
As a sample
- Form
- does not say
Connections
Keeping source and development objects in version control
Download
README
quoted from SAP-samples/s4hana-gcts-badi under Apache-2.0, readIntegrating gCTS with Transport Organizer processes
Description
Git-enabled Change and Transport System (gCTS) enables you to manage your ABAP change and transport management processes using Git as an external version management system. You can use it to leverage the functions of Git repositories and to set up continuous integration and delivery processes (CI/CD) for ABAP. The aim of gCTS is to allow DevOps processes for ABAP, as well.
- You can find more information about gCTS in general on the SAP Help Portal at Git-Enabled Change and Transport System
- You can use the coding provided in this repository if you would like to integrate your ABAP development processes with gCTS to enable task-based committing and to integrate the gCTS Regsitry in the process of releasing a task
- You can find a detailed description of the BAdI implemetation, its options and functionality in this SAP Community blog post Integrating gCTS with Transport Organizer processes
Requirements
- your ABAP system is on SAP S/4HANA 2020 SPS2 at least
- you have gCTS configured
- you have SAP Note 3204481 - gCTS: Fix for missing objects when importing into a repository with a subdirectory implemented
Download and Installation
- fork this repository
- connect your ABAP development system to the forked repository via gCTS
- clone it to your ABAP development system
A detailed description is provided in the blog post Integrating gCTS with Transport Organizer processes in SAP Community
Known Issues
None currently known
How to obtain support
Create an issue in this repository if you find a bug or have questions about the content.
For additional support, ask a question in SAP Community. Use the tag 'Software Logistics - Change Control and Transport'
Contributing
If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.
License
Copyright (c) 2022 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-samples-s4hana-gcts-badi- JSON
- /artifacts/sap-samples-s4hana-gcts-badi.json
- MCP
- Connecting an agent