Lesson 5 of 6
From GTS 11 to E4H
9 min
Listen to this lesson
GTS, edition for SAP HANA is not a support package on top of GTS 11.0. It is a new product on a new technical base (SAP S/4HANA Foundation and SAP HANA), with a new user interface built on SAP Fiori, a revised data model in several areas, renamed objects and a new license. Analysts and SAP partners describe the move as closer to a re-implementation than an upgrade, even where technical conversion tools are used.
Two decisions
| Decision | Options | Notes |
|---|---|---|
| Transition approach | System conversion of GTS 11.0 with SUM (brownfield) or new implementation (greenfield) | Conversion keeps data and much configuration but still needs follow-up for changed functions; new implementation allows a redesign. Check SAP's conversion guide for your target release. |
| Deployment | Standalone GTS system or co-deployment with S/4HANA | Co-deployment was reintroduced with release 2023: GTS runs in its own client on the same system instance as S/4HANA |
The two decisions every GTS 11.0 customer makes.
Standalone or co-deployed
In a standalone deployment, GTS runs on its own system and serves one or more feeders. In a co-deployment, GTS (software component GTSCORE) is installed on the same system instance as S/4HANA, in a separate client. SAP renamed conflicting GTS objects to make this possible. Even co-deployed, GTS stays logically separate: the feeder still transfers documents to it as to a standalone GTS, and it can still serve other feeders. The trade-off is that upgrades and downtime of one product affect the other. Sources generally recommend standalone for larger trade volumes and co-deployment for smaller ones; both are available on premise and in SAP S/4HANA Cloud Private Edition.
| Standalone | Co-deployed | |
|---|---|---|
| Systems | Separate GTS system landscape | GTS in its own client on the S/4HANA instance |
| Integration | Feeder transfer by RFC | Same feeder transfer pattern, inside one instance |
| Upgrades | Independent release cycle | Coupled: upgrades and downtime affect both |
| Multiple feeders | Yes | Yes, still possible |
| Typical fit | Higher volumes, several ERPs, own release rhythm | Smaller volumes, cost focus |
Contoso's decision
Ingrid and the solution architect chose a new implementation of release 2025, standalone, in Contoso's RISE landscape, for three reasons (illustrative course data). First, Contoso uses only SPL screening, embargo and US export legal control today, so the configuration is small and a redesign is cheap. Second, the Mexican acquisition will add import declarations and preference work, which Contoso would rather design fresh. Third, decoupling GTS from CMP's release calendar lets compliance content move on its own schedule. Master data (business partners, products and classifications, licenses) is transferred from CMP and loaded with prepared files; open blocked documents are cleared in GTS 11.0 before cutover.
What changes for users and testers
- User interface: SAP GUI transactions are replaced by Fiori apps; one source counts 70 transactions replaced by 17 redesigned apps. Test scripts must be rewritten, not adapted.
- Authorizations: roles and the authorization concept were redesigned; build and test roles for screening, legal control and customs specialists from scratch.
- Operations: some GTS 11.0 reports no longer exist, such as the blocked-document recheck report; define the new procedures.
- Search: SPL screening can use SAP HANA search configured in the legal regulation instead of GTS comparison terms; rerun calibration tests.
- Preference: long-term supplier declarations have a revised data model and new apps.
Cutover steps
| Step | Owner | Evidence |
|---|---|---|
| Freeze GTS 11.0 configuration changes | Ingrid | Change freeze notice |
| Load the current SPL list version into E4H; full screening of all partners | GTS administrator | Upload log; screening job log |
| Transfer products, classifications and licenses; reconcile counts | Theo's team | Count sheet signed by Ingrid |
| Clear open blocked documents in GTS 11.0 | Ingrid's team | Empty blocked-document list |
| Switch feeder RFC destinations for every document type | Sam | Configuration screenshot per document type |
| Create one order, one delivery and one PO per flow; confirm arrival in E4H | Priya's team | Customs documents in E4H with check results |
| Set GTS 11.0 to read-only for audit | Sam | Role change log |
Contoso's GTS cutover (illustrative course data).
What would you do?
A consultant suggests delaying the E4H move another year because "GTS 11.0 still works". Contoso is out of mainstream maintenance since January 2026. What is Priya's best input to the steering group?
- E4H is a new product: new base, Fiori apps, revised data model, new license.
- Choose conversion with SUM or new implementation, and standalone or co-deployment.
- Co-deployment (since 2023) puts GTS in its own client on the S/4HANA instance, coupling upgrades.
- Rewrite test scripts and roles; switch every feeder document type and prove it.
Check your understanding · not graded
Lesson check
1. Since which E4H release is co-deployment with S/4HANA available again?
2. How does a co-deployed GTS run?
3. Which tool performs a system conversion from GTS 11.0 to E4H?
4. What did Contoso's dress rehearsal find after the feeder switch?