AI guide
# Implementing SAP Global Trade Services — Reading Guide
## 【One-Line Pitch】
A practical, configuration-focused handbook for implementing SAP GTS, edition for SAP HANA—covering system setup, compliance management, customs procedures, and preference management—essential reading for SAP consultants, trade compliance managers, and IT leads planning a greenfield deployment or migrating from legacy SAP GTS 11.0.
## 【Book Arc】
- **Opening (~0%–9%)**: Introduces SAP GTS, edition for SAP HANA as the central platform for global trade management, highlighting the shift to SAP Fiori-based UX, redesigned apps, embedded analytics, enterprise search, and improved integration with SAP S/4HANA, SAP TM, and SAP EWM. Sets the stage for why the new edition matters.
- **Early (~9%–24%)**: Explains the relationship between SAP S/4HANA for International Trade and SAP GTS, covering commodity code classification, Intrastat reporting, and sanctioned party list (SPL) screening options—including cloud-based screening on SAP BTP. Clarifies what belongs in each system.
- **Early (~24%–33%)**: Dives into baseline settings and organizational structure—the backbone of any implementation. Covers foreign trade organizations (FTOs), legal units (LUs), mapping to feeder system company codes and plants, and leading practices for tax ID and legal regulation determination.
- **Middle (~39%–52%)**: Walks through compliance management, focusing on SPL screening. Uses a business case (Belgian company Beta exporting to Malaysia) to illustrate the end-to-end process: screening all transaction parties, handling hits, blocking documents, and managing blocked partners via SAP Fiori apps.
## 【Key Takeaways】
- **SAP GTS, edition for SAP HANA is the strategic trade platform** (Opening): SAP will focus future enhancements here, not in SAP S/4HANA's built-in trade functions. If you need deep customs, export control, or preference management, plan around SAP GTS.
- **The new UX is Fiori-based and app-driven** (Opening): Legacy SAP GUI transactions are being redesigned into out-of-the-box Fiori apps with workbenches for status, progress, and proposed follow-up actions. Expect a learning curve but better daily usability.
- **Organizational structure drives everything** (Early): The FTO represents the legal entity and determines legal regulations; LUs map to plants and storage locations. Get the mapping right—tax ID determination, licenses, and customs authorizations all depend on it.
- **One FTO, one tax ID, one country** (Early): A leading practice is assigning one company code per FTO. Multiple LUs can sit under one FTO, but only within the same country. This constraint shapes how you model multi-country operations.
- **SPL screening is automated but requires human oversight** (Middle): SAP GTS screens all parties in a transaction (sold-to, ship-to, payer, carrier, forwarder) against denied party lists. Hits block documents automatically; trade compliance teams must analyze, release, or confirm blocks.
- **Screening status is maintained per business partner** (Middle): Partners are screened when master data transfers from the feeder system; documents trigger new screening only when something changes. This reduces redundant checks while keeping compliance current.
- **Integration with SAP S/4HANA is tighter than before** (Early): Commodity codes can be maintained in SAP GTS and transferred to SAP S/4HANA via standard interfaces. Best practice: classify in SAP GTS, then sync to S/4HANA.
## 【Reading Tips】
- **Skim the opening chapters (0%–9%)** if you already know why you need SAP GTS; the value is in the "what's new" summary, not deep technical detail.
- **Deep-read the organizational structure chapter (24%–33%)**—it's the most conceptually dense and the foundation for everything else. Pay special attention to FTO/LU mapping rules and leading practices.
- **Use the SPL screening business case (39%–52%) as a template**: The Beta/Freelance Aviation example walks through a realistic export scenario with a compliance hit. Follow it end-to-end to understand the block-and-release workflow.
- **Watch for the "leading practices" callouts**—they're scattered throughout and represent real-world implementation wisdom, not just configuration steps.
- **If you're migrating from SAP GTS 11.0**, the book's later chapters (not fully covered in this excerpt set) address conversion preparation and execution—prioritize those when you get there.
## 【Coverage Limits】
This guide synthesizes the first half of the book (setup, organization, and SPL screening). The excerpts do not cover customs management configuration, trade preference management, identity-based preference processing, reporting/analytics details, or the migration from SAP GTS 11.0—those appear in later chapters.
##
Passage locations
Excerpt 1
cs of global trade management, so let’s switch gears to SAP. The following sections describe SAP’s global trade management capabilities within SAP GTS and SA...
View in text
Excerpt 2
product can be made effective from a specified future date. The maintenance of commodity codes has been improved through the development of a mass classifica...
View in text
Excerpt 3
user should assign LUs to FTOs only within the same country. If there is an LU in one specific country, but the actual FTO resides in another country, then a...
View in text
Excerpt 4
imately responsible for not transacting with denied parties. Manually screening business partners is a highly time-consuming, error-prone task, so Beta decid...
View in text