Change and Transport System

The Change and Transport System (CTS) helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape.

The complete documentation on how to configure CTS and how to set up transport landscapes is available on the SAP Help Portal at Change and Transport System.

If you need to transport non-ABAP objects, please refer to the page about enhanced Change and Transport System (CTS+). On this page, you can find guides and information about applications which support CTS+.

Git-enabled CTS

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. It is available for both, workbench and customizing objects, starting with SAP S/4HANA 2020. Please check the What's new viewer to find out about the feature set that is available for your release.

You can use gCTS to set up CI processes for ABAP. A scenario description is available on the Project 'Piper' site: Set up a Pipeline-Based ABAP Development and Testing Process Using Git-Enabled Change and Transport System(opens in new tab).

To integrate gCTS into your ABAP development processes, you can implement a BAdI. A detailed description is provided in the blog post Integrating gCTS with Transport Organizer processes(opens in new tab)

 

gCTS in SAP S/4HANA Cloud Public Edition

 

In SAP S/4HANA Cloud Public Edition, the multi-off delivery lets you develop ABAP extensions in an SAP S/4HANA Cloud Public Edition, one-system landscape and use gCTS to deploy them on any SAP S/4HANA Cloud Public Edition, three-system target landscape that isn't connected to your landscape. Documentation is available on the SAP Help Portal at Multi-Off Delivery(opens in new tab).

HTA for HDI

SAP HANA Transport for ABAP for SAP HANA Deployment Infrastructure (HTA for HDI) enables you to develop content for ABAP for SAP HANA applications (both HDI and ABAP objects) and transport the content together using the Change and Transport System of AS ABAP. HTA for HDI is the successor of HTA (available for SAP HANA Repository) by offering a solution for HDI objects as of Enhancement Package 2, Support Package 02 of SAP NetWeaver 7.5.

Find more information:

  • in the documentation on the SAP Help Portal.
  • in the guide that describes the configuration steps to enable HTA for HDI.
    (if you have installed older releases that do not provide the XSA Cockpit, please use the previous version of the guide)

HTA

With SAP HANA Transport for ABAP (HTA), you can synchronize objects and packages from the SAP HANA repository to the SAP HANA Transport for ABAP repository (HTA repository) in the ABAP system and add them to a transport request. HTA can be used when development objects in ABAP and SAP HANA have closely linked content and need to be transported together. More information about HTA:

Central CTS

Central CTS (cCTS) adds the new entities of Clusters and Collections to the world of CTS. These entities are used to bundle systems within clusters and transport requests (coming from different systems) within collections.

The Concepts for Central CTS are explained on the SAP Help Portal

Change Request Management (ChaRM) and Quality Gate Management (QGM) of SAP Solution Manager make use of these entities of the cCTS infrastructure. 

If you need to configure central CTS, refer to the guide How To... Set Up cCTS for ChaRM and QGM(opens in new tab) for SAP Solution Manager 7.2

Central CTS cannot be used outside of ChaRM or QGM