05-06-2021 3:44 PM
Using gCTS in combination with Jenkins etc allows you to deploy/transport changes easily to your PROD S/4 HANA "automagically" using your CI/CD pipelines. In the "old" world (= without gCTS), releasing changes to a PROD ABAP means you may get some really ugly problems when using a zero downtime approach:
ABAP has a so called code buffer (not sure if that's the real name). This code buffer does not get updated under certain circumstances. This can lead to some really ugly problems. The side effects can be avoided with some effort, none of the options is considered as "cool" outside the ABAP world. In the worst case, you can have real bugs/errors suddenly in your PROD system. Such errors can be really hard to analyze. Here a some more details (simplified):
Solutions so far have been:
As you can see, all of the cases above are either hard to achieve or cannot be carried our without a "downtime" from end user perspective. In agile and DevOps environments this feels like stone age.
Questions
Looking forward for your responses!
Thanks, Nabi
05-07-2021 10:40 AM
Hi Nabi,
gCTS is based on the same tools as CTS. Transport requests are created when you decide to activate a commit. The transport request contains the objects that are different between the commit that was previously active and the commit that you chose. The request is then imported via R3trans and tp. So the basic import process is still the same.
gCTS helps e.g. with the amount of requests that need to be imported into your production system. You don't need to go through the complete list of commit (and therewith create a transport request for each and every commit that might only contain few corrections). Importing just the latest commit is sufficient. Every object needs to imported only once.
So gCTS itself does not improve the online import functionality with respect to required restarts or options to use the coding. It can help reducing the import times.
Kind regards
Karin
05-07-2021 10:40 AM
Hi Nabi,
gCTS is based on the same tools as CTS. Transport requests are created when you decide to activate a commit. The transport request contains the objects that are different between the commit that was previously active and the commit that you chose. The request is then imported via R3trans and tp. So the basic import process is still the same.
gCTS helps e.g. with the amount of requests that need to be imported into your production system. You don't need to go through the complete list of commit (and therewith create a transport request for each and every commit that might only contain few corrections). Importing just the latest commit is sufficient. Every object needs to imported only once.
So gCTS itself does not improve the online import functionality with respect to required restarts or options to use the coding. It can help reducing the import times.
Kind regards
Karin
05-28-2021 1:12 PM
Thanks, Karin. I hoped there was maybe some improvement with S/4 HANA 2020...