With the introduction of SAP Global Trade Services, edition for SAP HANA 2023, co-deployment on top of SAP S/4HANA Private edition may be a viable option for some.
This blog briefly discusses the four main transition scenarios from SAP GTS 11.0 to SAP GTS, edition for SAP HANA 2023.
Co-deployment on top of SAP S/4HANA will undoubtedly be perceived as a favorable option by many, especially those looking for reduced infrastructure costs and lower TCO. However, it is essential to know that these benefits do not come without sacrifice. For example, GTS upgrades may impact SAP S/4HANA system availability and vice versa. Therefore, Standalone will still be the recommended option for most current GTS user organizations. In addition, it is vital to be aware that even when co-deployed, SAP GTS, edition for SAP HANA will be a logically separated system requiring the same level of integration between "ERP" and GTS as the standalone version. On the upside, the co-deployed, SAP GTS, edition for SAP HANA can still connect to multiple ERP systems and is not limited to its host's system.
Depending on the chosen transition scenario, one or more implementation approaches are available. We have elaborated on this in a separate blog (https://blogs.sap.com/2023/05/02/brown-blue-or-green-how-to-move-to-sap-global-trade-services-editio....
A brief recap here:
Greenfield Approach (with optional data loads)
Selective Data Migration
Conversion (Brownfield Approach)
Let us now look closer at the 4 main transition scenarios. Scenario A and B is only relevant for customers that are currently running SAP GTS on top of SAP ECC.
Scenario A practically means that a combined SAP ECC and SAP GTS are split into two separate instances. Before this can happen, we first need to establish a new standalone instance of SAP GTS 11.0. Following this, we can use any of the three available implementation approaches to convert SAP ECC to SAP S/4HANA and SAP GTS 11.0 to SAP GTS, edition for SAP HANA respectively.
In Scenario B we move from a co-deployed SAP GTS 11.0 on top of SAP ECC to a co-deployed SAP GTS, edition for SAP HANA on top of an SAP S/4HANA instance.
SAP GTS, edition for SAP HANA can only be co-deployed in a separate client. With SAP GTS 11.0 there were two options; installed in the same or in a separate client.
If SAP GTS 11.0 is co-deployed in the same client, we will not be able to use the SAP Software Update Manager. Greenfield is therefore the only available implementation approach.
If SAP GTS 11.0 is co-deployed in a separate dedicated client, we can use any of the three implementation approaches to move to SAP GTS, edition for SAP HANA in a separate dedicated client on an instance of SAP S/4HANA.
In Scenario C we move an existing SAP GTS 11.0 standalone solution to a standalone instance of SAP GTS, edition for SAP HANA.
The Brownfield procedure can cover the conversion to SAP GTS, edition for SAP HANA, and the OS/DB migration to SAP HANA in one technical procedure via Database Migration Option (DMO) of SUM.
For more information on DMO, please see: https://blogs.sap.com/2013/11/29/database-migration-option-dmo-of-sum-introduction/
Additionally, a transition to a Private Cloud setup can be achieved as part of the same brownfield procedure using DMO of SUM with System Move.
Alternatively, this transition can also be performed in multiple cutovers/projects. E.g.
1. OS/DB migration to SAP HANA using SWPM
2. Conversion to SAP GTS E4H using SUM
3. Move to the cloud using HSR
Depending on the existing GTS version and database, there are several options for scenario C.
Scenario C - Option 1 - Already SAP GTS 11.0 on SAP HANA database
If you already run SAP GTS 11.0 on an SAP HANA DB, option 1, using either conversion or selective data migration are viable options.
Scenario C - Option 2 - SAP GTS 11.0 on any DB
If you are running SAP GTS on any DB (not on SAP HANA DB) a conversion of the database is required in addition to the system conversion. This can be done either as part of the conversion/upgrade;
or be done in a two-step way, by performing a DB-migration to SAP HANA DB before the conversion to SAP GTS, edition for SAP HANA.
Scenario C - Option 3 - Shift to the Cloud
Many companies will also use the transition to SAP GTS, edition for SAP HANA to make a shift to the cloud, by moving to SAP GTS, edition for SAP HANA, Private Cloud Edition.
Scenario C - Option 4 - Earlier versions of SAP GTS
A limited number of companies are running older and unsupported releases of SAP GTS. For customers running SAP GTS 10.0 or 10.1, there are two options. A two-step approach with an intermediate upgrade to GTS 11.0, or a direct jump upgrade from GTS 10.0 or 10.1 to SAP GTS, edition for SAP HANA.
Despite Standalone deployment still being the recommended deployment option, we expect a number of GTS user organizations currently running standalone to move to SAP GTS, edition for SAP HANA co-deployed on SAP S/4HANA.
This can be done either in a two-step process as shown below;
or with a more direct approach;
Both of these options will require that DMLT teams from SAP and migration tools are involved. DMLT stands for Data Management and Landscape Transformation and is a set of services provided by SAP.
More information is available here: https://www.sap.com/services-support/service-offerings/data-mgmt-landscape-transformation.html
Independent of your current SAP GTS version and deployment model and independent of the desired end state with SAP GTS, edition for SAP HANA, there are several options to choose from, when planning your transformation project. Good luck!
This blog post would not have been possible without the work of my fellow colleagues, and in particular oliver.freytag.
This blog briefly discusses the four main transition scenarios from SAP GTS 11.0 to SAP GTS, edition for SAP HANA 2023.
- Co-deployment to Standalone
- Co-deployment to Co-deployment
- Standalone to Standalone
- Standalone to Co-deployment
Standalone vs. Co-deployment
Co-deployment on top of SAP S/4HANA will undoubtedly be perceived as a favorable option by many, especially those looking for reduced infrastructure costs and lower TCO. However, it is essential to know that these benefits do not come without sacrifice. For example, GTS upgrades may impact SAP S/4HANA system availability and vice versa. Therefore, Standalone will still be the recommended option for most current GTS user organizations. In addition, it is vital to be aware that even when co-deployed, SAP GTS, edition for SAP HANA will be a logically separated system requiring the same level of integration between "ERP" and GTS as the standalone version. On the upside, the co-deployed, SAP GTS, edition for SAP HANA can still connect to multiple ERP systems and is not limited to its host's system.
Brown, Blue, or Green
Depending on the chosen transition scenario, one or more implementation approaches are available. We have elaborated on this in a separate blog (https://blogs.sap.com/2023/05/02/brown-blue-or-green-how-to-move-to-sap-global-trade-services-editio....
A brief recap here:
Greenfield Approach (with optional data loads)
- Install new system.
- Configure and customize new processes.
- If needed develop new custom code.
- Optionally: selectively load data from an existing SAP GTS or legacy system into the new SAP GTS system using a data migration tool of your choice.
Selective Data Migration
- Copy the existing SAP GTS system.
- Delete all master and transactional data. Keep all customizing and custom coding.
- Convert the empty system with an upgrade-like procedure to the new SAP GTS, edition for SAP HANA product.
- Selectively load data from an existing SAP GTS or legacy system into the new SAP GTS system using a data migration tool of your choice.
Conversion (Brownfield Approach)
- Use an upgrade-like procedure to convert the existing system including all data, customizing, and custom developments to the new SAP GTS, edition for SAP HANA product.
Let us now look closer at the 4 main transition scenarios. Scenario A and B is only relevant for customers that are currently running SAP GTS on top of SAP ECC.
Scenario A: GTS 11.0 Co-deployment on SAP ECC to SAP GTS, edition for SAP HANA Standalone
Scenario A practically means that a combined SAP ECC and SAP GTS are split into two separate instances. Before this can happen, we first need to establish a new standalone instance of SAP GTS 11.0. Following this, we can use any of the three available implementation approaches to convert SAP ECC to SAP S/4HANA and SAP GTS 11.0 to SAP GTS, edition for SAP HANA respectively.
| Advantages | Disadvantages |
|
|
Scenario B: GTS 11.0 Co-deployment on SAP ECC to SAP GTS, edition for SAP HANA Co-deployment
In Scenario B we move from a co-deployed SAP GTS 11.0 on top of SAP ECC to a co-deployed SAP GTS, edition for SAP HANA on top of an SAP S/4HANA instance.
SAP GTS, edition for SAP HANA can only be co-deployed in a separate client. With SAP GTS 11.0 there were two options; installed in the same or in a separate client.
If SAP GTS 11.0 is co-deployed in the same client, we will not be able to use the SAP Software Update Manager. Greenfield is therefore the only available implementation approach.
If SAP GTS 11.0 is co-deployed in a separate dedicated client, we can use any of the three implementation approaches to move to SAP GTS, edition for SAP HANA in a separate dedicated client on an instance of SAP S/4HANA.
| Advantages | Disadvantages |
|
|
Scenario C: GTS 11.0 Standalone to GTS, edition for SAP HANA Standalone
In Scenario C we move an existing SAP GTS 11.0 standalone solution to a standalone instance of SAP GTS, edition for SAP HANA.
The Brownfield procedure can cover the conversion to SAP GTS, edition for SAP HANA, and the OS/DB migration to SAP HANA in one technical procedure via Database Migration Option (DMO) of SUM.
For more information on DMO, please see: https://blogs.sap.com/2013/11/29/database-migration-option-dmo-of-sum-introduction/
Additionally, a transition to a Private Cloud setup can be achieved as part of the same brownfield procedure using DMO of SUM with System Move.
Alternatively, this transition can also be performed in multiple cutovers/projects. E.g.
1. OS/DB migration to SAP HANA using SWPM
2. Conversion to SAP GTS E4H using SUM
3. Move to the cloud using HSR
Depending on the existing GTS version and database, there are several options for scenario C.
Scenario C - Option 1 - Already SAP GTS 11.0 on SAP HANA database
If you already run SAP GTS 11.0 on an SAP HANA DB, option 1, using either conversion or selective data migration are viable options.
Scenario C - Option 2 - SAP GTS 11.0 on any DB
If you are running SAP GTS on any DB (not on SAP HANA DB) a conversion of the database is required in addition to the system conversion. This can be done either as part of the conversion/upgrade;
or be done in a two-step way, by performing a DB-migration to SAP HANA DB before the conversion to SAP GTS, edition for SAP HANA.
Scenario C - Option 3 - Shift to the Cloud
Many companies will also use the transition to SAP GTS, edition for SAP HANA to make a shift to the cloud, by moving to SAP GTS, edition for SAP HANA, Private Cloud Edition.
Scenario C - Option 4 - Earlier versions of SAP GTS
A limited number of companies are running older and unsupported releases of SAP GTS. For customers running SAP GTS 10.0 or 10.1, there are two options. A two-step approach with an intermediate upgrade to GTS 11.0, or a direct jump upgrade from GTS 10.0 or 10.1 to SAP GTS, edition for SAP HANA.
Scenario 😧 GTS 11.0 Standalone to GTS, edition for SAP HANA Co-Deployment
Despite Standalone deployment still being the recommended deployment option, we expect a number of GTS user organizations currently running standalone to move to SAP GTS, edition for SAP HANA co-deployed on SAP S/4HANA.
This can be done either in a two-step process as shown below;
or with a more direct approach;
Both of these options will require that DMLT teams from SAP and migration tools are involved. DMLT stands for Data Management and Landscape Transformation and is a set of services provided by SAP.
More information is available here: https://www.sap.com/services-support/service-offerings/data-mgmt-landscape-transformation.html
Conclusion
Independent of your current SAP GTS version and deployment model and independent of the desired end state with SAP GTS, edition for SAP HANA, there are several options to choose from, when planning your transformation project. Good luck!
Credits
This blog post would not have been possible without the work of my fellow colleagues, and in particular oliver.freytag.
- SAP Managed Tags:
1 Comment
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
