is required, along with its integration into the SAP S/4HANA system. There are two SAP GTS deployment approaches available for the project, each with distinct infrastructure and operational requirements.

This document evaluates these options and recommends the most suitable approach based on the project's specific requirements, complexity, and business objectives. The evaluation considers factors such as system compatibility, ease of implementation, costs, and system landscape requirements.

A decision on the deployment approach must be made at this stage, as the SAP GTS Co-Deployed approach within S/4HANA presents an opportunity to optimize landscape costs. The available deployment options are:

Option A: SAP GTS Co-Deployed within S/4HANA

Starting from S/4HANA 2023, SAP GTS can now run in a separate client of a S/4HANA Instance without compromising the functional scope—an improvement over previous S/4HANA versions. Key characteristics of this deployment include:

• SAP GTS and SAP S/4HANA share the same database and application server, meaning they also share system resources. 
• GTS runs on a separate client in the S/4HANA platform. This is required because as indicated in the SAP documentation “You must install SAP Global Trade Services, edition for SAP HANA 2023 in a separate client from SAP S/4HANA 2022/2023 or master data distribution from S/4 to GTS will not work”.
• Unified Maintenance: Updates and patches are managed together with SAP S/4HANA, creating a technical dependency between both solutions.
• IT Operations and administrative tasks are shared by both solutions.

Option B: Deploying SAP Global Trade Services (GTS) as a standalone system while integrating it with SAP S/4HANA 

This has been the traditional approach for SAP GTS implementations. Until S/4HANA 2023, this was the only deployment option that ensured full functional scope availability.

Key characteristics of this deployment include:

• Independent System: SAP GTS operates on dedicated application and database servers, separate from S/4HANA.

• Integration Interfaces Required: Data exchange with S/4HANA relies on RFC, IDocs, APIs, or other integration methods.

• Separate Administration & Maintenance: System operations, updates, and administration must be managed independently.

• Higher Infrastructure Costs: Requires additional servers, resources, and licenses, increasing total cost of ownership (TCO).

While this deployment offers full functional scope as for option A, it also results in higher complexity and costs due to separate system management and integration requirements.

More details are available here:

• https://community.sap.com/t5/financial-management-blogs-by-sap/your-way-to-sap-gts-edition-for-sap-hana-on-premise-or-cloud/ba-p/13782776Blog SAP GTS Deployment
• System Landscape for SAP Global Trade Services, edition for SAP HANA | SAP Help Portal
• SAP Global Trade Services, edition for SAP HANA | SAP Help Portal

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

• Functional Restrictions: Both deployment options provide the same functional capabilities.

• Future Flexibility: A co-deployed SAP GTS system can be separated into a standalone deployment if needed.

• Software Component Alignment: S/4HANA and SAP GTS must remain synchronized in terms of software components, creating a technical dependency in both scenarios.

• System Time Zone: All SAP applications, including SAP GTS, operate on UTC time, following SAP’s recommended best practice. There are no specific time zone requirements for SAP GTS.

• No Workbench Object Conflicts: SAP GTS uses its own workbench objects, ensuring no impact when running in a co-deployed mode.

• Project Implementation Unaffected: Both options fully support all required activities for a SAP GTS Greenfield implementation, including:

  • Interface configuration

  • Data loading

  • Testing

  • Customizing

  • Development

• No Historical Data Migration: Existing historical data from the current SAP GTS system (SID WGP) will not be migrated. Only open items could be required.

• Co-Location of GTS with S/4HANA: In order to ensure good performance of the many thousands of run-time checks performed by transactions inside S/4HANA against GTS, the network latency between GTS and S/4HANA must be very low. This necessitates deploying GTS and S/4HANA in the same datacenter location, and precludes the use of a single global GTS system for all S/4HANA systems. 

• Shared Infrastructure: SAP GTS and SAP S/4HANA share the same database and application server . Therefore, additional system resource requirements must be analyzed to ensure optimal performance.
• Resource Analysis  based on the Early Watch Alert (EWA) from 17 March 2025 for the current SAP GTS runs on a separate client
• Simplified Integration: No need for complex RFC interface configurations.
• Lower Infrastructure Costs: No separate system required.
• production environment (SID WGP):
  • • WGP runs on a shared AWS r6i.2xlarge server with following attributes: 8 CPUs, 64GB RAM, 1.1TB DB disk.

    • SAP GTS specific tables occupy approximately 346GB.

    • Other technical tables (logs, change documents...) occupy approximately 219GB
    • DB Disk Average monthly growth is 7GB approximately 

    • Current DB disk use is high (950 GB) , but as per the data strategy, historical data migration is not required, only open items will be migrated, significantly reducing disk space requirements.

    • 61 active users.

    • Based on above data we can conclude that estimated additional infrastructure needs on S/4HANA for SAP GTS system are equivalent to a "Small" size system (e.g., 2/4 CPUs, 16/32GB RAM, <500 gb disk, 60 users).

• Separate Client: GTS operates in a dedicatedS/4HANA client, ensuring functional separation. That also mean that the workbench objects are shared between all the SAP S/4HANA system clients. This will not have any impact since SAP GTS Standard objects use its own Namespace (/SAPSLL/) and packages (/SAPSLL/*). Custom objects (if required) for GTS should be created in the a dedicated namespace to avoid conflicts with other potential developments.

• Simplified Maintenance: Updates, patches, and operations

Easier Maintenance: Updates and patches

• are managed together with SAP S/4HANA, reducing administrative effort.

• Real-

time

• Time Access:

GTS can directly

• Direct access to 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.

• improves efficiency.

• Cost Efficiency: Eliminates the need for an external SAP GTS system, leading to lower infrastructure and operational costs.

• System Resources Considerations: Since SAP

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.

• infrastructure resources, proper sizing adjustments must be factored in during implementation.

• The co-deployed client applies to every S/4HANA instance to be created in Syensqo landscape, that means:
  • a co-deployed GTS client in the primary S/4HANA instance in the EU, and
  • a co-deployed GTS client in the S/4HANA instance for China

Option B: Deploying SAP Global Trade Services (GTS) as a standalone system while integrating it with SAP S/4HANA

This option involves running Refers to the option of Run SAP GTS as a standalone instance, separate from SAP S/4HANA.

Key Points:

• Independent Operation: SAP GTS runs independently from SAP S/4HANA on a dedicated application server and database.

• Integration Requirement: Integration interfaces are needed to enable data exchange between SAP GTS and S/4HANA.

• Maintenance: Requires separate operational management, with updates and patches handled independently for SAP GTS.

• Resource Efficiency: By processing system activities separately, this option reduces slightly the sizing requirements for SAP S/4HANA.

• Landscape Requirements: With this approach would be required a SAP GTS System for every project environment, meaning: Development, Integration Test, User Acceptance Test, PreProduction, Production.

• Increased Costs: This approach incurs higher