SaaS Based SAP GTS Design Blueprint

By Jay Singh (dee167@outlook.com)

Contents
1. Introduction ...................................................................................................................................... 3
2. Project Summary .............................................................................................................................. 5
3. General Control Setting in SAP GTS .............................................................................................. 5
4. SPL Control Settings & Customizing .............................................................................................. 9
5. Legal Control Customizing ............................................................................................................ 12
6. Embargo Service Customizing ...................................................................................................... 16
7. Document Copy Control from S/4 Feeder to GTS .................................................................... 17
8. Goods accompanying Documents (GTS Customs) ..................................................................... 18
9. Background Jobs to be Scheduled ............................................................................................... 18
10. Data Sources ................................................................................................................................ 20
1. Introduction

We are moving towards digitalization of both ERP and non-ERP products. Widespread agile
approach is adopted to deliver projects for quick and better customer experience. In
industrial 4.0 revolution, many startups and big consulting companies came up with
innovative products which are easy to implement with best user experience. They
implement the product, connect with your existing ERP/non-ERP systems, deliver Functional
Specification document (FSD), Configuration document and technical specification document
(TSD) and go. If you are from customer business side, involved in six digital products
implementation, then you might have 18 documents with too many technical details. To
understand these documents either you need to connect with IT department or
implementation partner. These services may be chargeable or come under AMS support,
where you are charged for support services as a lumpsum. I find here we are missing the
relevance of blueprint document ,also called as Business Blue Print Document (BPD) which is
taking its last breath in the era of agility.

However, I recommend business blue print document is a vital document, especially for
cloud offerings. BPD provide you end to end business process, along with system integration
in business language. These will be easy to understand by business and also helpful for the
support team.

Let me share a real customer story which recently happened during our cloud based SaaS
based SAP GTS offering.

In November 2015, SAP introduced a major release of S/4 HANA called 1511 release. In the
release 1511, “ECC SD Foreign Trade (SD-FT)” will be no more supported. Many of my
European based customers contacted me for advice, on how to manage existing SD-FT
functionality, if they plan migration to S/4 HANA. So the option was either move to SAP GTS
or custom build the functionality in core S/4. Both options were not reasonable from ROI
and system perspective. Say for example, is it worth to invest million $ on SAP GTS, if you
are only using ECC SD-FT for custom document printing? Looking into the requirement, we
have started working on need based innovation and hosted cloud based SAP GTS which can
be subscribed as SaaS model. In the first phase, Compliance management as Service (CmaS)
was launched successfully. We will be working with Seburger team to design and test the
cloud based integration with ATLAS and NCTS. Once it is complete, weplan to launch Custom
Management Integration as a Service (CmiaS).

We observed during the project, that the customer was not confident on hybrid based
services ,where S/4 HANA is on-premise and shared SAP GTS system hosted on the cloud.
Though we have handed over the agreed delivery document FSD, Configuration document
and TSD but business userswere hardly able to understand. It was too technical for them.
We did not see the “wow” factor on the customer's face,while handing over the project to
the support team. So we thought, why not to spend few more days and provide them
Business Blue Print document. Though we were not responsible for entire landscape, then
also we prepared and handed over BPD, the first expression from project sponsor was
“wow, we got what we want, that also in tangible form ,else everything is on cloud”.

Now we realised BPD is an important document in the digital and virtual cloud world. FSD
and TSD are merely a process document ,where customer and partner both know, the
customer can’t make any changes in shared SaaS services. Therefore BPD is going to be a
critical document for business and support team.

So thought of sharing this cloud based BPD document which is exclusively written by me
based on my recent cloud based GTS implementation. This topic is intended for SAP GTS
Consultant, SAP GTS Business user, Compliance Manager, SAP Project Managers, IT
managers, solution architects and SAP GTS existing users. This document doesn't have any
customer information. You can reference this BPD for your GTS implementation projects, it
is based on GTS 11 SP10.

We exclusively provide all transactions and analytics on Fiori apps only. Only limited access
provided for direct transaction in the core system. A user screenshot provided below for
your reference:

This document defines at a high level the Business Processes, as well as S/4 HANA and GTS
Technical Configuration. This document can be utilized as the source of S/4 HANA
Configuration Data to be mapped to the SAP GTS Environment for use in any of the SAP GTS
Implementation project.
2. Project Summary
With expansion of companies product portfolio and geographical region, the business
structures are becoming more complex and markets becoming more global nowadays. The
necessity of handling foreign trade of a business is rapidly gaining importance. To manage
entire company’s export and import SAP Global Trade Services (GTS) provides the tools
which cater most of the requirement of the global market. To insure this S/4 HANA and
cloud based GTS will:

1. Apply an initial automated screening process to the current Business Partners (earlier
called as Vendor and Customer Master Data).
2. Apply automated screening process to new Business partner for both vendor and
customer.
3. Apply automated transactional screening process to sales orders and purchase orders,
and their subsequent documents.

3. General Control Setting in SAP GTS

3.1 Number Ranges

IMG path: SAP Global Trade Services > General Settings > Number Ranges >

3.1.1 Business Partners

01 0000000001 9999999999
AB A ZZZZZZZZZ

3.1.2 Product Master

01 00000000000000000001 99999999999999999999

3.1.3 Custom document

Note this range are year dependent, so the range for the following year
must be set before December 31.

01 2017 0000100000 9999999999

01 2018 0000100000 9999999999
01 2019 0000100000 9999999999
3.2 Organizational Structure

The organizational structure of the company is mapped with respect to the legal and
customs law requirements, that is, the conduct of the company vis-à-vis the
authorities. The organizational structures of the S/4 HANA system are also mapped to
the organizational structures for customs law. We recommend one Foreign Trade
Organization Unit per company.

3.2.1 Company Codes

The company codes from the S/4 HANA system are mapped to the Foreign Trade
Organizational, whereby more than one company code can be assigned to an
organizational unit, but one company code can be assigned to exactly one
organizational unit at any one time.

All Company Codes should be mapped to individual Foreign Trade Organizations:

OUDE XYZ Germany Ltd.

OUSE XYZ Sweden Ltd.
OUDK XYZ Dansk Ltd.

Data Source: T000

Company code to be assigned:

1000
1001
1002

3.2.2 Legal Units

The legal units provided with a detailed view of an organizational unit, that is, they
divide the organizational unit into several areas (several plants (as legal units) for
each company code (organizational unit). We recommend One Legal Unit per country.

Data Source: T00W

Three legal unit will be created for Germany, Sweden and Denmark. No other legal
units required.
3.2.3 Document Structure

When documents are transferred from the S/4 HANA system, a customs document,
on which the different services are based, is created for each document. Maintain
all the relevant structures for the customs document here.

3.2.3.1 Document Type

Each customs document is created with a specific document type. At the

document type level, we can control which services are to be carried out for
the customs document.
Data Source: Sales – TVAK, MM – T161

SAP Standard:
EXPDLV Customs Document (Export) - Delivery Document Level
EXPINV Customs Document (Export) - Billing Document Level
EXPORD Customs Document (Export) - Sales Document Level
EXPQT Customs Document (Export) - Quotation Document Level
IMPORD Customs Document (Import) - Purchasing Document Level

3.2.3.2 Item Categories

Each customs document item is created with a specific item category. At item
category level, we can control which services are to be carried out for the
customs document.
Data Source: Sales – TVAP, MM – T163Y

SAP Standard:
EXDLV1 Customs Doc. Item (Export) - Delivery Doc. Item Cat. Level
EXINV1 Customs Doc. Item (Export) - Billing Doc. Item Cat. Level
EXORD1 Customs Doc. Item (Export) - Sales Doc. Item Cat. Level
 EXQT1 Customs Doc. Item (Export) - Quotation Doc. Item Cat. Level
IMORD1 Customs Doc. Item (Import) - Purchasing Doc. Item Cat. Level

3.2.3.3 Partner Functions

Each customs document is created with several partners at header and item
level, whereby each partner has a specific partner function. All active partner
functions must be listed here.
Data Source: TPAR

Partners:
AG Sold-to Party Export/Dispatch
AP Contact Person Export/Dispatch (should be excluded from check)
EN Ult. Consignee Export/Dispatch
LF Vendor Import/Arrival
RE Bill-to Party Export/Dispatch
RG Payer Export/Dispatch
SP Carrier Import/Arrival and Export/Dispatch
WE Ship-to Party Export/Dispatch
WL Goods Supplier Import/Arrival

3.2.4 Legal Regulations

The laws to be observed when goods are exported from or imported to a country
are defined as legal regulations.

3.2.4.1 Country Group

Country Groups will be required for Group A, B, D, and E countries. Groups will
also be made for countries in Group A but not B, and finally a group will be
made for EU territories.

Point to Remember: Countries may only exist in one group at a time.

Assignment to 2 country groups will cause the system to fail to find a license
exception.

3.2.4.2 Legal Regulation Definition

 The legal regulations to be observed are defined on the basis of the countries
involved and the company’s line of business. We will create a new regulation
for each regulated market. Countries recognizing the CE approval will be
grouped under 1 Europe Regulation.

e.g. EMBUN German Foreign Trade Laws Embargo - United Nations

3.2.4.3 Determine Active Legal Regulations

All business transactions defined in the system as a customs document have to

determine which services are to be used and which legal regulations are to be
observed meaning, which legal regulations are ‘active’ for that business
transaction. This procedure defines the rule set for determining these factors.

We prefer “Determine Legal Regulation at Country Level” as an option.

3.2.4.4 Activating Legal regulation

Legal regulations have to be activated for each country (import country and
export country) so that the system knows which legal regulations require an
SPL check.
• Regulatory regulations will be activated in the SE, DE, DK and the originating
country
• EMBUN Export Administration Regulations will be activated for all countries.
• SPL and Embargo will be activated for all countries.

3.2.4.5 Create Depreciation Groups

Depreciation Groups to be created:

MM0A01 Depreciation Group (Import): Purchase Order Documents
MM0B01 Depreciation Group (Import): Inbound Deliveries
MM0C01 Depreciation Group (Import): Goods Receipts
SD0A01 Depreciation Group (Export): Sales Documents
SD0B01 Depreciation Group (Export): Outbound Deliveries
SD0C01 Depreciation Group (Export): Billing Documents
SD0D01 Depreciation Group (Export): Quotations

4. SPL Control Settings & Customizing

4.1 SPL Control Settings

Various options are available for setting the sensitivity of the comparison between the
partner address and the SPL master record. The system uses different linguistic rules
(aliases, phonetics, and so on) to enable it to identify names that, for example, are spelt
differently but pronounced the same.
4.1.1 Delimiters

Delimiters are separators used within a name or address. If the name in an address
contains a character specified in the delimiter, the name is split at the point where
the character appears. Note that you also have to specify a blank space as a
separator. The screen below shows some common separators. A delimiter is defined
for a specific rule set.

SAP Standard -_,./;:'"[]{}\|`~

(Point to remember: A space must be included)

4.1.2 Exclusion

In each rule set, you can specify strings that are to be ignored (excluded) when
addresses are compared in an SPL check. This generally refers to strings that
appear frequently in addresses (“Inc.”, for example).

The following list is an example list and should not be considered a

recommendation:

4.1.3 Alias Text

 4.1.4 Normalization
When the comparison index is being generated, we can “normalize” the various
index entries. Normalization involves taking specific characters or character
combinations and replacing them with a fixed character string. In English, for
example, you might replace the “O’” in Irish surnames with an “O”.

Examples:
K C
Y I
PH F
PSY SI

4.2 Legal Regulation Name Lists

Recommended name EUSPL

4.2.1 List Types

Before assigning SPL master data to the various boycott lists, we have to define
the boycott lists (also called ‘list types’) in the system.

Recommended we will load all 35 list types from MK data. Some examples are
as following:

BALK SDN, Western Balkans (OFAC)

BYE Blocked Yugoslav Entities (OFAC)
BYV Blocked Yugoslav Vessels (OFAC)
CBW Chemical Biological Weapons Concerns (DOS)
DOS Department of State debarred Parties (DOS)
DOTO Designated Terrorist Organization (DOS/OFAC)
DTO Designated Terrorist Organization (DOS/OFAC)
 4.2.2 Rule Set

The rule set is assigned to a legal regulation. The same rule set can also be
assigned to several different legal regulations, but only one rule set can be
assigned to each legal regulation.

Recommended: phonetic search set on.

Detailed Control Settings:

Keyword Generated from Name Logical AND

Keyword Generated from Country Logical OR (at least one OR operation
satisfied)
Keyword Generated from City Logical OR (at least one OR operation satisfied)
Keyword Generated from Street Name Logical OR (at least one OR operation
satisfied)

4.2.3 Changes

The following fields will be checked for changes:

5. Legal Control Customizing

5.1 Activation

5.1.1 Document Type

EXPDLV Customs Document (Export) - Delivery Document Level
EXPORD Customs Document (Export) - Sales Document Level
IMPORD Customs Document (Import) - Purchasing Document Level

5.1.2 Item Category

 EXDLV1 Customs Doc. Item (Export) - Delivery Doc. Item Cat. Level
EXORD1 Customs Doc. Item (Export) - Sales Doc. Item Cat. Level
EXQT1 Customs Doc. Item (Export) - Quotation Doc. Item Cat. Level
IMORD1 Customs Doc. Item (Import) - Purchasing Doc. Item Cat. Level

5.1.3 Legal Regulations

• Regulatory regulations will be activated in the DE, DK and SE and the originating
country
• EU Export Administration Regulations will be activated for all countries.
• SPL and Embargo will be activated for all countries.

5.2 Determination Procedure

All business transactions defined in the system as a customs document have to

determine which services are to be used and which legal regulations are to be observed
(that is, which legal regulations are ‘active’ for that business transaction).

This procedure defines the rule set for determining these factors. We set up “Determine
Legal Regulation at Country of departure / destination level” for better control.

5.3 Legal Regulations

5.3.1 Procedure for Determining License Types

Legal Regulations can be assigned based upon legal Regulation plus one
or two more criteria. Currently the criteria supported are: Country,
Country Group, Control Class, and Control Grouping level and
combinations.

We have configured, Initial Determination on Country Level only.

5.3.2 Control Settings for License Determination Service

5.3.2.1 Product Master Maint.

Two settings are possible, all products subject to legal control or no
products are subject to legal control.

All products are subject to legal control will be the initial

configuration.

Products flagged as requiring regulatory control will be subject to

legal control under all regulatory regulations.

All products will default to no control under the any other

Regulations.
5.3.2.2 Control Grouping Activated

Control groupings simplify maintenance of the determination tables

for the license types by grouping together various export control
numbers that require an identical license type. Groupings can only be
used if the appropriate setting has been activated in Customizing for
the legal regulation.

In our case, “No Control grouping is required”.

5.3.2.3 Peculiarity Code for Goods Activated

Peculiarity Codes are used in Europe to add additional information

about a material

In our case we set up as “Peculiarity Codes are not required”

5.3.2.4 Partner Group for Determining Country of Destination

The country of departure/destination of the export is used on the
basis of the partner function contained in the document and in this
partner grouping. The first partner function is used (which is
contained in both the document and the partner grouping). No
further partner functions are checked.

Proposed Order:
10 AE Ultimate Consignee
20 WE Ship to Party
30 AG Sold to Party
40 RE Bill to Party

5.3.2.5 Procedure for Determining License Types

LTDET License Type determination – EU

5.3.2.6 Sequential Determination of License Types Activated

In our case, Sequential determination is not needed.

Though following options are available:

• Legal regulation / Country / Control grouping level
• Legal regulation / Country / Control class level
• Legal regulation / Country group / Control grouping level
• Legal regulation / Country group / Control class level
• Legal regulation / Country level
• Legal regulation / Country group level
• Legal regulation / Control grouping level
 • Legal regulation / Control class level
• Legal regulation level

5.3.2.7 Allowed statuses

All the possible statuses in a license must be maintained for each
legal regulation.

Example export statuses will be:

5.3.2.8 Assign Time Zone to Deadline Type

A time zone must be maintained for all the deadline types assigned in
the “General Control” cockpit.

• CHECK Check Date CET

• VALFRO Valid-From Date CET
• VALTO Valid-To Date CET

5.3.3 Text Determination Procedures for License Types (Configurable)

The following text areas will be available on the regulatory licenses:

0002 Submission Purpose
0003 Notes
0004 Responsible Person

5.3.4 License Types

The following license types will be created: The abbreviations for these
license types will be consistent across all regulations in which they are
used:

Control Settings:
All statuses will be assigned to each of the license types.
 5.3.5 Defining the Rule Set for the Export Control List
Number Schema – ECCN

Detailed Structure:
Level Length Maintenance Description
10 2 Exact Length Chapter
20 7 "From - To" Range ECCN Number

Regulatory Schemas
Level Length Maintenance Description
10 5 Exact Length CLASS
20 3 "From - To" Range LEVEL

5.3.6 Assign Procedure for License Maintenance

Legal Regulation Description Customs TS – Exp

EAR License Determination EU - Export EUECL

5.3.7 Assign License Determination Procedure

Few example:

6. Embargo Service Customizing

6.1 Activation

6.1.1 Document Types

EXPDLV Customs Document (Export) - Delivery Document Level
EXPORD Customs Document (Export) - Sales Document Level
 IMPORD Customs Document (Import) - Purchasing Document Level
6.1.2 Item Category
EXDLV1 Customs Doc. Item (Export) - Delivery Doc. Item Cat. Level
EXORD1 Customs Doc. Item (Export) - Sales Doc. Item Cat. Level
EXQT1 Customs Doc. Item (Export) - Quotation Doc. Item Cat. Level
IMORD1 Customs Doc. Item (Import) - Purchasing Doc. Item Cat. Level

6.1.3 Legal Regulations

The following embargo regulation must be activated in all countries XYZ Ltd.
sells to:

6.2 Determination Procedure

All business transactions defined in the system as a customs document have to determine
which services are to be used and which legal regulations are to be observed (that is, which
legal regulations are ‘active’ for that business transaction). This procedure defines the rule
set for determining these factors.

Currently “Determine Legal Regulation at Country of departure / destination level” was set
up in our system.

6.3 Legal Regulations

6.3.1 Determination
The Embargo check includes two checks:
• Legal regulation / Partner Country
• Legal regulation / Country of Departure/Partner Country

If all sales are all sales are EU based, we recommend;

• Legal Regulation / Partner Country

Embargo’s will be configured for : Cuba, North Korea, Libya, Iraq, Iran, The
Federal Republic of Yugoslavia (Serbia & Montenegro), Sudan and Syria.

7. Document Copy Control from S/4 Feeder to GTS

7.1 Change Pointers

 Change Pointers must be activated globally in transaction BD61.

7.2 Change Pointers for Message Types

The following message types are activated in transaction BD50:

/SAPSLL/CREMAS_SLL

/SAPSLL/DEBMAS_SLL

/SAPSLL/MATMAS_SLL

7.3 Document Types

All document types must be listed in Transaction /SAPSLL/TLES4_B_S4.

All document types that will be subject to legal control must have the “Transfer Legal”
indicator set.
We will not activate the “Dialog Legal” indicator.

8. Goods accompanying Documents (GTS Customs)

A number of different goods accompanying documents will be produced by the F8 (or newly
created version) Billing document type. The F8 was created to allow for consolidation of
multiple deliveries contained in one shipment onto one set of documents. These all output
was set up using BRF plus. The documents to be produced from the F8 are as follows

 Shippers Export Declaration – XSED output type – will be produced for all EU and PR
exports. The form XSD_EXPORT_FUSD was assigned. Please check relevant SAP notes
for SED form need to apply to allow the retrieval of the ECCN and license type
information and place on the line item of the document being produced.

 Shippers Letter of Instruction – XSLI output type – will be produced for all EU and PR
export. The form XSD_EXPORT_FUSI was assigned.

 Certificate of Origin – XCOO – Will be produced for specific destination countries or

customers which as for a certificate. The form ZSD_EXPORT_FUCO was assigned.

9. Background Jobs to be Scheduled

9.1 Required S/4 Jobs

9.1.1 Transfer changes to customer master records to GTS
Job Name: X_GTS_CUSTOMER
Program: RBDMIDOC
Variant: SLL_CUSTOMER
Message Type for Variant: /SAPSLL/DEBMAS_SLL
Timing: Every 10 – 60 minutes
Average run time: ~ 1 sec

9.1.2 Transfer changes to vendor master records to GTS

Job Name: X_GTS_MATERIAL

Program: RBDMIDOC
Variant: SLL_MATERIAL
Message Type for Variant: /SAPSLL/MATMAS_SLL
Timing: Every 10 – 60 minutes
Average run time: ~ 1 sec

9.1.3 Transfer changes to material master records to GTS

Job Name: X_GTS_VENDOR

Program: RBDMIDOC
Variant: SLL_VENDOR
Message Type for Variant: /SAPSLL/CREMAS_SLL
Timing: Every 10 – 60 minutes
Average run time: ~ 1 sec

9.2 GTS Jobs (optional jobs)

These four jobs should be configured as steps in a single job.

9.2.1 Reset SPL Buffers

Job Name: X_GTS_BUFF_RESET
Program: /SAPSLL/SPL_CUS_APP_BUFF_RESET
Variant: DEFAULT
Timing: Once per day ~ 11 PM
Average run time: ~ 1 sec

9.2.2 Create SPL Search Terms

Job Name: X_GTS_SPL_ST
Program: /SAPSLL/SPL_CREATE_SEARCHTADRC
Variant: DEFAULT
Timing: Once per day ~ 11:10 PM
Average run time: ~ 10 mts.

9.2.3 Index SPL Search Terms

Job Name: X_GTS_SPL_INDEX
 Program: /SAPSLL/SPL_INDEX_CREATE
Variant: DEFAULT
Timing: Once per day ~ 12 AM
Average run time: ~ 5 mts

9.2.4 Generate Index of BP Search Terms

Job Name: X_GTS_BP_INDEX
Program: /SAPSLL/SPL_CREATE_SEARCHTADRC
Variant: DEFAULT
Timing: Once per day ~ 1 AM
Average run time: ~ 5 mts

10. Data Sources

Data will be sourced from these sources:

(List source):

Regulatory:
Regulatory classes
License data

Export:
HTS
Schedule B
ECCN

Hope this blue print document will be helpful in your SAP GTS project delivery. API
configuration not included in the document as its too customer specific and can’t be
disclosed. If you need any information get in touch with me on my mail id
dee167@outlook.com .