SAP S/4 HANA 2020 is there. It comes with new offerings and features for gCTS.
The most important one is maybe the new repository layout – we call it Layout Version 3. When you create new repositories, the new repository layout will be used, the file format will be set to JSON by default (as long as the repository is empty, you can also switch to xml if you like ) and support for table data will be included. With JSON as file format the readability of the repository content is improved.
But why is that feature that important? Do you really need it? Most probably yes – the new layout version is the prerequisite for one of the most wanted features since gCTS is out: You can now also push customizing transport requests into your Git repository and pull them into one client on the target system. Technically speaking, objects of the types TDAT and VDAT are supported – support for CDAT objects is not available yet , but we plan to include it, soon.
Using gCTS for customizing is very simple: Just enter the correct target system when creating the transport request – this is the virtual SID (vSID) that you defined when you created your repository.
You can find more details on the SAP Help Portal in the chapter Use gCTS for Customizing Data.
gCTS also takes first steps towards supporting conflict resolution
To give you an idea, what the conflict resolution UI looks like:
In addition, SAP S/4HANA 2020 comes with two improvements that help you setting up gCTS more smoothly and checking the configuration:
Another good thing about the Enable gCTS Wizard and the Health Check: You can add them to your SAP S/4HANA 1909 system as well, by implementing a few SAP Notes or implementing a Support Package – Check the central gCTS Note 2821718 for details.
You can find many more details and links to documentation topics in the section Git-Enabled Change and Transport System of the ABAP Platform What’s new Viewer.
The most important one is maybe the new repository layout – we call it Layout Version 3. When you create new repositories, the new repository layout will be used, the file format will be set to JSON by default (as long as the repository is empty, you can also switch to xml if you like ) and support for table data will be included. With JSON as file format the readability of the repository content is improved.
But why is that feature that important? Do you really need it? Most probably yes – the new layout version is the prerequisite for one of the most wanted features since gCTS is out: You can now also push customizing transport requests into your Git repository and pull them into one client on the target system. Technically speaking, objects of the types TDAT and VDAT are supported – support for CDAT objects is not available yet , but we plan to include it, soon.
Using gCTS for customizing is very simple: Just enter the correct target system when creating the transport request – this is the virtual SID (vSID) that you defined when you created your repository.
You can find more details on the SAP Help Portal in the chapter Use gCTS for Customizing Data.
gCTS also takes first steps towards supporting conflict resolution
- Automatic push and pull are not an option, if you expect conflicts and need to resolve them. Up to now, gCTS used to pull the current state of the remote repository and merge the changes into that state before pushing. The consequence of this is that changes that were provided to the remote repository from another source could be overwritten by your new push as committing and pushing were executed at once . So, the first step towards conflict resolution is to stop this behavior. Therefore, you have to set two parameters for the repository (or on system level if you want to introduce the behavior for all repositories) Disable Automatic Pull and Push
- The Objects tab in the gCTS app provides the tools that you need to track files that cause conflicts. For conflicting files, you can open a conflict resolution UI which shows the local and the remote versions as well as a merge suggestion that you need to edit. Please check the SAP Help Portal at Use the Conflict Resolution Editor for more details
To give you an idea, what the conflict resolution UI looks like:
In addition, SAP S/4HANA 2020 comes with two improvements that help you setting up gCTS more smoothly and checking the configuration:
- The Wizard to Enable gCTS and
- the Health Check to get details if everything works fine or if there are issues.
Another good thing about the Enable gCTS Wizard and the Health Check: You can add them to your SAP S/4HANA 1909 system as well, by implementing a few SAP Notes or implementing a Support Package – Check the central gCTS Note 2821718 for details.
You can find many more details and links to documentation topics in the section Git-Enabled Change and Transport System of the ABAP Platform What’s new Viewer.
- SAP Managed Tags:
18 Comments
