Skip to Content
Product Information

gCTS is here

Do you know gCTS?

Maybe not – it is quite new.

Do you need gCTS?

Maybe – if your ABAP development processes should go for DevOps.

To solve the riddle: gCTS is short for Git-enabled Change and Transport System. The basic idea is that you can use Git to store your ABAP development objects.

The developers continue working in the ABAP workbench (SE80) or in ABAP development tools (ADT). They continue recording their changes in tasks. They continue releasing tasks and transport requests.

But: releasing the transport request does no longer mean that the transport request is added to the import queues of the follow-on systems of your system landscape. Releasing the transport request means that a commit is created in Git. The objects that were changed are added as files to a Git repository.

You can connect other ABAP runtimes to this repository. You can then choose from the commits to pull one or the other into this ABAP system.

You can set up a continuous integration process for your ABAP development.

gCTS still has a way to go until it can fully support DevOps or distributed development. But the basics are there. You can try them out for a simple ABAP package if you like – no need to immediately switch your whole ABAP development department to gCTS.

Interested in more?

To learn what is available right now in S/4HANA 1909, you can read the documentation on the SAP Help Portal: Git-enabled Change and Transport System

To get the full picture of what is planned, read our statement of direction Continuous integration in an ABAP environment

Or if you prefer a recorded session from SAP TechEd Las Vegas 2019: LT110 – Include ABAP in DevOps: Get the Picture


You must be Logged on to comment or reply to a post.
  • Hi Karin,

    great blog post! I really like the possibilities gCTS brings with it and the way described in the statement of direction sounds great.

    But I don’t think we should say gCTS enables DevOps. gCTS makes it easier to set up your development process as you do it with other technology stacks and enable CI/CD. But DevOps is much more. It’s not only about CI/CD, monitoring, automated testing and other technical aspects. It’s at least for the same amount a cultural topic and a big change for all SAP development departments at customers I’ve seen.



  • Hi Karin,

    that’s great news! Looking forward working with it.

    I’ve got one question:
    In ABAP-Git the serialization of table records is usually not supported (only via plugins or using the detour via BC-Sets). What is the technique used in gCTS? BC-Sets tend to be a bit slow when containing too many records.



  • Hi Thorsten,

    currently, gCTS does not support customizing. Anything that can be part of a Workbench request can be handeled via gCTS – even TABU entries. This with the exception that deletion ob TABUs are not supported and that there is no specific client handling. Which means that the source client will always be the target client. You can check note 288887 for details.

    Hope this helps
    Kind regards

    • Hi Karin,


      Are there any plans to bring gCTS to the SAP Netweaver versions that still support the SAP Business Suite (ECC 6)?


      Kind regards,


      • Hi Rammutla,


        there are no plans to downport gCTS to anything below SAP S/4HANA 1909. This is due to technical reasons as it is simply not possible to make gCTS work in the way it does on previous releases and due to the fact that new features are published in new releases.

        If you need to be able to work with gCTS in older releases, please let me know via mail naming the customer (if he allows) and the business reason. We collect these requirements and if there is a big need for this, we can think about options how it might be possible to allow at least an integration with gCTS to some extend.

        Thanks and kind regards