| Status | Approved |
| Owner | WENNINGER-ext, Sascha |
| Stakeholders |
Issue
A key decision is required on how will be implemented the SAP GTS environment. The integration of SAP Global Trade Services (GTS) with S/4HANA can be approached in two main ways:
A )Embedding SAP GTS directly into the S/4HANA system.
B) Maintaining SAP GTS as a separate instance while integrating with S/4HANA.
Recommendation
Given the cost and simplified run benefits of a unified and streamlined system, the recommendation if for embedding SAP GTS into S/4HANA (Option A).
Background & Context
In the context of ERP Rebuild Project is required to implement the SAP Global Trade Services (GTS) solution and integrate it with the S/4HANA system.
Since S/4HANA 2023 it is possible to run SAP GTS in an Embedded mode without compromise the functional scope (which was not possible in previous S/4HANA versions).
Now must be decided the deployment approach since we have the opportunity to reduce landscape costs with the SAP GTS embedded mode.
In previous releases this was not possible without some compromise on scope.
More details are available here:
Assumptions
No functional restrictions : Same functionality is available for each options
Embedded system could be carved out to stand alone if needed in the future
Constraints
If we select RISE to have a seperate system then we will have to pay for this system for the life of the contract (7 years) so we need to make a decision now
Impacts
- No functional impacts since same functionality is available for embedded and standalone options.
- More technical dependencies in one system if we go embedded. High trade volumes might affect system performance
- Higher RISE costs of we go with a separate systems
Business Rules
None
Options considered
- Embedding SAP GTS directly into the S/4HANA system.
- Maintaining SAP GTS as a separate instance while integrating with S/4HANA.
Option A: Embedding SAP GTS directly into the S/4HANA system.
The embedded option refers to deploying SAP GTS within the same SAP S/4HANA system instead of running it as a separate standalone system. SAP GTS would run on the S/4HANA box as a separate client.
Key Points:
- SAP GTS and SAP S/4HANA share the same database and application server.
- GTS runs on a separate client
- Simplified Integration: No need for complex RFC interface configurations.
- Lower Infrastructure Costs: No separate system required.
- Easier Maintenance: Updates and patches are managed together with SAP S/4HANA.
- Real-time Access: GTS can directly access S/4HANA data without synchronization delays.
- Reduces latency as trade compliance checks and customs processes run within the same system
- Reduces administrative workload compared to managing a separate GTS instance.
- System Resource Impact: Since GTS and S/4HANA share the same resources, high trade volumes might affect system performance
- Eliminates the need for an external GTS system and reduces infrastructure costs.
Option B: Maintaining SAP GTS as a separate instance while integrating with S/4HANA.
Refers to the option of Run SAP GTS as a standalone instance.
Key Points:
- SAP GTS runs independently from SAP S/4HANA.
- Requires integration interfaces (e.g., RFC, IDocs, APIs) to exchange data with S/4HANA.
- Reduces the performance impact on SAP S/4HANA since system activities are processed separately
- Needs separate system administration, operation and updates.
- Higher initial costs due to the need for additional hardware, hosting, and maintenance
Evaluation
Option A | Option B | |
|---|---|---|
| Landscape Cost |
|
|
| Landscape Complexity |
|
|
| Maintenance Complexity |
|
|
| Functional Scope |  Full Scope | Full Scope |
| Performance |  Share system resources with other processed | System resources Full dedicated to GTS process |
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||