Gts200 en Col18

GTS200
Configuring SAP Global Trade

Services
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 18
Course Duration: 5 Day(s)
Material Number: 50161292
SAP Copyrights, Trademarks and
Disclaimers
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
American English is the standard used in this handbook.

The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
© Copyright. All rights reserved. iii

iv © Copyright. All rights reserved.
Contents
vii Course Overview
1 Unit 1: Basic Settings
3 Lesson: Setting up the Transfer of Master Data and Documents

11 Lesson: Making Basic Mapping Settings
21 Unit 2: Legal Regulations in Compliance Management
23 Lesson: Mapping Legal Norms in SAP GTS

27 Lesson: Using Legal Regulations in Processes
35 Unit 3: Embargo Check
37 Lesson: Maintaining Embargoes and Check Settings

41 Lesson: Checking and Releasing Documents
49 Unit 4: Sanctioned Party List Screening
51 Lesson: Managing Sanctioned Party Lists

57 Lesson: Analyzing Check Results
67 Unit 5: Legal Control
69 Lesson: Maintaining Goods Lists and Classifying Products

73 Lesson: Defining License Types
79 Lesson: Setting up License Determination
85 Lesson: Setting up Re-export Control
95 Unit 6: Legal Regulations and Nomenclatures in Customs Management
97 Lesson: Activating Legal Regulations for Customs Management

103 Lesson: Maintaining Commodity Codes and Customs Tariffs
113 Unit 7: Additional Settings for Customs Management
115 Lesson: Setting up the Integration into Feeder System Processes

125 Lesson: Managing Customs Code Lists and Data Defaulting
131 Lesson: Analyzing the Communication with Customs
137 Lesson: Connecting Customs Agents
147 Unit 8: Preference Processing
149 Lesson: Mapping Preferential Agreements in SAP GTS

153 Lesson: Mapping Rules of Origin
163 Lesson: Setting up Preference Determination
169 Lesson: Setting up Supplier’s Declaration Management
© Copyright. All rights reserved. v

179 Unit 9: Intrastat Declarations
181 Lesson: Submitting Intrastat Declarations

185 Lesson: Configuring Data Selection and Issue
vi © Copyright. All rights reserved.

Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Application Consultant
● Support Consultant
● Super / Key / Power User
● Help Desk/CoE Support
© Copyright. All rights reserved. vii

viii © Copyright. All rights reserved.
UNIT 1 Basic Settings
Lesson 1
Setting up the Transfer of Master Data and Documents 3
Lesson 2
Making Basic Mapping Settings 11
UNIT OBJECTIVES
● Set up master data transfer from the feeder system to SAP GTS
● Set up document transfer from the feeder system to SAP GTS
● Maintain mapping for document transfer from SAP ECC or SAP S/4HANA to SAP GTS
© Copyright. All rights reserved. 1

Unit 1: Basic Settings
2 © Copyright. All rights reserved.

Unit 1
Lesson 1
Setting up the Transfer of Master Data and
Documents
LESSON OVERVIEW
This lesson deals with the setup of regular master data and document transfer from the SAP
ECC or SAP S/4HANA feeder system.
Business Example
The IDES group has branches in the United States and in the EU. It manufactures products,
which it sells worldwide. Components and trading goods are procured from suppliers in
various third countries. The group intends to use SAP GTS in its branches in the United States
and Germany. It therefore checks the required system settings.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
Master Data Transfer

You transfer all customer, vendor, and material master records, and if applicable, bills of
material (BOMs) relevant for preference determination and re-export control, from your
feeder system to the SAP GTS system using Remote Function Calls (RFC).
A distinction must be made between the initial data transfer when the SAP GTS system is set
up and regular transfers of new or changed data during operation. For the initial data transfer
from SAP ECC or SAP S/4HANA, you use transactions Initial Transfer of Material Masters to
SAP GTS (transaction code /SAPSLL/MATMAS_DIRR3), Initial Transfer of Customers to SAP
GTS (transaction code /SAPSLL/DEBMAS_DIRR3), Initial Transfer of Vendors to SAP GTS
(transaction code /SAPSLL/CREMAS_DIRR3) and, if necessary, Initial Transfer of Bills of
Material (transaction code /SAPSLL/BOMMAT_DIRR3).

Figure 1: Master Data Transfer
You can find these and all other transactions for the initial master data transfer in the area
menu for the communication with SAP GTS on the Initial Transfer of Mast. Data tab. In an SAP
S/4HANA system, you can use SAP Fiori apps to schedule the transfer of master data for
background processing instead.
Note:
You can find the technical names of the required job catalog entries in the SAP
Fiori Apps Reference Library.
Following the initial data transfer, the product master data, business partner master data, and
where applicable, BOMs, are available in the SAP GTS system. These master data are
processed to some extent in SAP GTS.
After the initial transfer of all relevant master data, you use an Application Link Enabling (ALE)
service, the change pointers, for regular automated master data transfer. Change pointers
are used to transfer new and changed data regularly, as in traditional ALE master data
distribution.
Many application programs generate change documents for each change made to their
objects. These change documents track changes to the application objects (changed field
values, name of the person who made the change, and the time of the change). The change
documents can be used in ALE scenarios, but also for master data transfer to SAP GTS to set
additional change pointers in the database. Creating a master record also generates a change
document and, if the ALE service is active, a change pointer.

Lesson: Setting up the Transfer of Master Data and Documents
Figure 2: Change Pointers
For the purpose of ALE, most application programs for maintaining master data in SAP
systems are structured flexibly for processing inbound and outbound intermediate
documents (IDocs). This allows you to decide for each optional segment field of an IDoc
structure (IDoc basic type) whether it should be contained in an IDoc or not.
The change pointer creates a connection between change documents and the corresponding
message type. When creating or changing a master record, the application program checks
whether the change pointer function is activated. If the function is activated, the system saves
a change pointer to the database, together with the application document and the change
document.
If the entire master record is not to be sent to the respective target system in IDoc format, so-
called reduced message types are used. Message types denote the data that can be
exchanged between systems in ALE or EDI scenarios, for example, MATMAS for material
masters, CREMAS for vendor masters, and DEBMAS for customer masters. These message
types are assigned to IDoc basic types.
In the delivery Customizing of your SAP ECC or SAP S/4HANA system, you find the following
message types for the replication of master data relevant for SAP GTS using change pointers:
● /SAPSLL/BNKMAS_SLL (banks)
● /SAPSLL/BOMMAT_SLL (BOMs)
● /SAPSLL/CREMAS_SLL (vendors)
● /SAPSLL/DEBMAS_SLL (customers)
● /SAPSLL/MATMAS_SLL (materials)
For the purpose of re-export control and preference determination in SAP GTS you can
transfer material prices from the Accounting 1 view of the material master separately using

message type /SAPSLL/PRCMAT_SLL. In addition, you can use the message type /SAPSLL/
PSDMAT_SLL to transfer procurement indicators from the MRP 2 view of the material master
for preference processing.
Figure 3: Reduced Message Types for Master Data Transfer
If the change pointer function is used for a reduced message type, only changes made to the
selected fields generate change pointers.
In SAP ECC, you can activate the change pointer service as well as create, change, and display
reduced message types in the area menu for communication with SAP GTS. Perform the
following steps:
1. On the Basic Settings tab choose Activate Change Pointers Globally or use transaction
code BD61.
2. Set the Change pointers activated — generally indicator and save your changes.
3. On the Basic Settings tab enter a message type in the Reduced message type and choose
Activate change pointers. You can use transaction code BD53 instead.
4. To create, change or display a reduced message type, choose Create , Change , or

Display , respectively.
The change pointers are evaluated online using the Creating IDoc Type from Change Pointers
transaction (transaction code BD21) or in the background using the RBDMIDOC program. In
ALE scenarios, this program generates IDocs for all new and changed data records. The
function modules assigned to the reduced message types for master data transfer to SAP
GTS generate RFCs instead.

Figure 4: Transfer of New and Changed Master Data
By scheduling the RBDMIDOC program regularly as a periodic background job, you ensure that
all new master data and all relevant changes to existing master data are promptly available in
SAP GTS.
Note:
A detailed description of how change pointers can be used to regularly transfer
new and changed master data to SAP GTS is provided in the Integration Guide.
Document Transfer
Before you can use the application areas within Compliance Management and Customs
Management, the documents that are created in the feeder system prior to or during an
import or export process (such as purchase orders, sales orders, and billing documents)
require counterparts in the SAP GTS system. Therefore, these documents must be replicated
in SAP GTS in the form of customs documents, customs shipments, and customs
declarations, depending on the application area they are meant for.

Figure 5: Document Transfer Overview
To ensure that all documents required for the various application areas in SAP GTS are
transferred, you have to flag the respective document types as relevant for SAP GTS in the
SAP ECC or SAP S/4HANA feeder system. In the Customizing of the SAP ECC feeder system,
choose Sales and Distribution → Foreign Trade/Customs → SAP Global Trade Services - Plug-
In → Control Data for Transfer to SAP Global Trade Services → Configure Control Settings for
Document Transfer. In SAP S/4HANA, choose Integration with Other SAP
Components → Integration with Governance, Risk and Compliance → SAP Global Trade
Services → Control Data for Transfer to SAP Global Trade Services → Configure Control
Settings for Document Transfer.
Figure 6: Settings on Document Type Level in SAP ECC (Example)

In an SAP S/4HANA feeder system, you can restrict document transfer using the company
code in addition to the document type (Activation Level field). You specify the relevant
company codes in the Document Type/Company Codes subfolder.
You will find three application levels for each basic process: MM0A, MM0B, and MM0C for
inbound processes; and SD0A,SD0B, and SD0C for outbound processes. Each application
level groups together document categories according to their respective function in the
process. For example, MM0A is the application level of purchasing documents and SD0C is
the application level of billing documents.
From the details of each application level, you can see for which group of application areas in
SAP GTS the documents can be used. For example, you can transfer sales documents
(application level SD0A) to SAP GTS to allow the replicas to be checked in Compliance
Management. The option to transfer documents for Risk Management (letter of credit and
restitution application areas) is only relevant for SAP GTS 11.0.
Note:
A detailed description of how to set up document transfer from the feeder system
to SAP GTS is provided in the Integration Guide.
Lesson “Making Basic Mapping Settings” deals with the corresponding settings in SAP GTS.
LESSON SUMMARY
You should now be able to:


Unit 1
Lesson 2
Making Basic Mapping Settings
LESSON OVERVIEW
This lesson explains how to configure mapping settings for replicating documents from SAP
ECC or SAP S/4HANA to SAP GTS.
Business Example
IDES Germany intends to use SAP GTS in some of its branch offices. The company needs to
check the required system settings.
LESSON OBJECTIVES
Mapping Settings in SAP GTS

Customers and vendors, as well as banks, that you transfer from your feeder system to the
SAP GTS system are stored there automatically in the form of SAP business partners,
hereinafter referred to as business partners. SAP GTS copies the address data from the
feeder system. Business partners can be used in a number of different SAP systems. They are
part of the cross-application functions in SAP ECC and SAP S/4HANA, but they are also used
in SAP EWM, for example. With the exception of employees, business partners for SAP GTS
are always of the “organization” type.
You define the exact function that a business partner performs for your company by assigning
a business partner role to it in the system. A number of specific business partner roles are
supplied for SAP GTS in delivery Customizing.
For the purposes of document replication, you need to map your feeder system company
codes and plants that are relevant for SAP GTS as business partners. You create business
partners that represent company codes in the “Foreign Trade Organization” role (SLLFTO).
The foreign trade organization maps your company with regard to customs and foreign trade
law in SAP GTS. Plants relevant to SAP GTS correspond to business partners in the “Legal
Unit” role (SLLSIT).

Figure 7: Organizational Units and Their Mapping in SAP GTS
You define foreign trade organizations and legal units as business partners in the Maintain
Business Partner transaction (transaction code BP).
In Customizing for your SAP GTS system, you have to assign the business partners of the
foreign trade organizations to the company codes of the feeder system. According to the
same pattern, you have to assign the business partners of the legal units to the plants that
they represent in Customizing for the SAP GTS system (Global Trade Services → General
Settings → Organizational Structure → Assignment of Organizational Units from Feeder
System to Foreign Trade Org. and Global Trade Services → General Settings → Organizational
Structure → Assignment of Organizational Units from Feeder System to Legal Unit
respectively).
You mirror the assignment of the plants to be mapped in SAP GTS to company codes by
linking the corresponding legal units and foreign trade organizations to each other (menu
path: Global Trade Services → General Settings → Organizational Structure → Assign Legal
Unit to the Foreign Trade Organization).
In an SAP ECC or SAP S/4HANA feeder system, business partners are already assigned
specific functions or roles in the import or export process. For example, customers are sold-
to parties, ship-to parties, and payers. However, these functions are not always performed by
the same partner: A sold-to party may order goods from you for a third party.

Lesson: Making Basic Mapping Settings
Figure 8: Partner Functions
You have to define all feeder system partner functions that are used in documents, relevant to
the transfer, as partner functions in SAP GTS. When creating a partner function in SAP GTS,
you have to specify whether it can be used for inbound processes or outbound processes, or
both. In Customizing, choose Global Trade Services → General Settings → Partner
Structure → Define Partner Functions.
In the next step, you link the partner functions in the feeder system to the relevant partner
functions in SAP GTS. Choose SAP Global Trade Services, edition for SAP HANA → General
Settings → Partner Structures → Assignment of Partner Functions from Feeder Systems.
You group partner functions into partner groupings on specific to application areas. For
example, if you want to use the embargo check, you define a partner grouping for each
direction of goods movement (receipt/issue). Assign all check-relevant partner functions to
this partner grouping. This enables the SAP GTS system to identify whether it should check
the embargo situation only for the country of the ship-to party or also for the country of the
end customer.

Figure 9: Partner Groupings
In Customizing, choose SAP Global Trade Services, edition for SAP HANA → General
Settings → Partner Structures → Define Groups of Partner Functions. You will see an overview
of the preconfigured partner groupings for the individual application areas. Select the
grouping PGEMB2 (Partner Group for 'Embargo' Service – Export), for example. Then open
the Assign Partner Function folder in the dialog structure to check the assignment of partner
functions.
Partner groupings are assigned in Customizing for the respective application area at legal
regulation level.
To ensure that all documents relevant for your processes are replicated, you have to first flag
these document types as relevant to SAP GTS in the feeder system. In Customizing for the
SAP GTS system, you define document types as equivalents of the document types flagged in
the feeder system. You set control parameters such as number range intervals, text
determination procedures, and action profiles for communicating with the authorities on
document type level. You then assign the relevant document types for purchasing and sales
documents as well as deliveries to the applicable SAP GTS document types in Customizing.

Lesson: Making Basic Mapping Settings
Figure 10: Assign Document Types
Delivery Customizing already contains suitable proposals for document types. Separate
document types are required for Compliance Management and for Customs Management
application areas.
In Customizing, choose SAP Global Trade Services, edition for SAP HANA → General
Settings → Document Structures → Define Document Types for Application Areas to define
your own document types, if required. Then choose SAP Global Trade Services, edition for
SAP HANA → General Settings → Document Structures → Assignment of Document Types
from Feeder Systems to link feeder system document types to SAP GTS system document
types.
Document types must be activated for all application areas that work with documents of this
type. Choose SAP Global Trade Services, edition for SAP HANA → General
Settings → Document Structures → Activate Document Types for Application Areas.
For the application areas being part of Compliance Management, a similar mapping is
required at item category level. In SAP GTS, you only need a small selection of
item categories. If you do not intend to use the item categories provided in delivery
Customizing, you can define your own item categories. Choose SAP Global Trade Services,
edition for SAP HANA → General Settings → Document Structures → Define Item Categories
for Application Area. Then assign the item categories to their equivalents in the feeder system
(SAP Global Trade Services, edition for SAP HANA → General Settings → Document
Structures → Assignment of Item Categories from Feeder Systems.

Figure 11: Assign Item Categories
If the mapping of an item category is missing, the SAP GTS system creates a replica of the
feeder system document without the corresponding item data. The document is assigned the
status Technical Mapping Incomplete in SAP GTS. To avoid the creation documents that are
technically incomplete, choose the Automatically Transfer Item Category function when
maintaining the item category assignment. Specify the logical system of the feeder system or
the system group, the application level, and an SAP GTS-specific item category. The SAP GTS
system will then retrieve all item categories from the feeder system and automatically assign
the predefined SAP GTS-specific item category.
Note:
A detailed description of how to set up the mapping required for document
transfer from the feeder system to SAP GTS is provided in the Integration Guide.
LESSON SUMMARY

Unit 1
Learning Assessment
1. Which master data are transferred from the SAP ECC or SAP S/4HANA feeder system to
SAP GTS?
Choose the correct answers.
X A Materials
X B Customers
X C Info records
X D Banks
X E Bills of material
2. Which categories of documents can be transferred from SAP ECC or SAP S/4HANA
feeder systems to SAP GTS?
X A Purchase orders
X B Sales orders
X C Outbound deliveries
X D Inbound deliveries
X E Shipments
feeder systems to SAP GTS for checks in Compliance Management?
X A Purchase orders
X B Billing documents
X C Material documents
X D Sales orders
X E Inbound deliveries

Unit 1: Learning Assessment
4. Which feeder system objects have to be mapped to their equivalents in SAP GTS?
X A Document types
X B Plants
X C Partner functions
X D Sales organizations
X E Item categories

Unit 1
Learning Assessment - Answers
1. Which master data are transferred from the SAP ECC or SAP S/4HANA feeder system to
SAP GTS?
X A Materials
X B Customers
X C Info records
X D Banks
X E Bills of material
Correct. Materials, customers, banks, and bills of material are transferred from the feeder
system to SAP GTS.
feeder systems to SAP GTS?
X A Purchase orders
X B Sales orders
X C Outbound deliveries
X D Inbound deliveries
X E Shipments
Correct. Purchase orders, sales orders, outbound deliveries, and inbound deliveries can
be transferred from SAP ECC or SAP S/4HANA feeder systems to SAP GTS.

Unit 1: Learning Assessment - Answers
feeder systems to SAP GTS for checks in Compliance Management?
X A Purchase orders
X B Billing documents
X C Material documents
X D Sales orders
X E Inbound deliveries
Correct. Purchase orders, sales orders, and inbound deliveries can be transferred from
SAP ECC or SAP S/4HANA feeder systems to SAP GTS for checks in Compliance
Management.
4. Which feeder system objects have to be mapped to their equivalents in SAP GTS?
X A Document types
X B Plants
X C Partner functions
X D Sales organizations
X E Item categories
Correct. Document types, item categories, partner functions, and plants have to be
mapped to their equivalents in SAP GTS.

UNIT 2 Legal Regulations in
Compliance Management
Lesson 1
Mapping Legal Norms in SAP GTS 23
Lesson 2
Using Legal Regulations in Processes 27
UNIT OBJECTIVES
● Map legal norms in SAP GTS

● Create new legal regulations
● Activate legal regulations for the application areas of Compliance Management
● Explain the determination of legal regulations in the export process

Unit 2: Legal Regulations in Compliance Management

Unit 2
Lesson 1
Mapping Legal Norms in SAP GTS
LESSON OVERVIEW
Foreign trade law compliance depends largely on the completeness and correctness of the
mapping of relevant legal norms in SAP GTS. The delivery Customizing of your system
already performs key preparatory steps here, but is only a proposal. Therefore, you must
check the sample configuration in terms of your company-specific processes and adjust it as
required.
Business Example
The IDES group is checking which laws and regulations are relevant to its foreign trade
processes.
LESSON OBJECTIVES
Function of Legal Regulations in the System

From a technical perspective, legal regulations are alphanumeric keys that are defined in
Customizing of the SAP GTS system and are linked to a large number of control parameters.
Most of these control parameters depend on the application area in which the legal regulation
is to be used. Thus, for example, you define the scope and strictness of the address check at
the level of a legal regulation for sanctioned party list screening.
It is not always appropriate to use the legal regulations contained in delivery Customizing
without making changes to them. It is also possible that there is no model that meets your
requirements. In such cases, you create your own legal regulations in the customer
namespace. To do so, in Customizing of the SAP GTS system, choose the menu path SAP
Global Trade Services, edition for SAP HANA → General Settings → Legal
Regulations → Define Legal Regulation.
Delivery Customizing contains legal regulations, the configuration of which corresponds to
the legal situation at the time of delivery. Legal changes that take effect after this time may
result in changes to the system configuration. If a legal change has resulted in adjustments to
the program code, you can update your system by implementing support packages. Delivery
Customizing is also constantly adjusted in this way. In any case, you must ensure that
knowledgeable employees keep track of relevant legal changes and, if necessary, initiate
configuration changes or make configuration changes themselves.

Figure 12: Legal Regulations as Reference Plane of Customizing
In SAP ECC and SAP S/4HANA, organizational units such as company codes, plants, sales
organizations, or warehouse numbers are the main fundament of process-related system
configuration. Many Customizing settings in Logistics and Accounting are dependent on
organizational units.
There are no organizational units in SAP GTS. From the perspective of system configuration,
the legal regulations take the place of organizational units. Most of the Customizing settings
in SAP GTS are used to configure legal regulations for the individual application areas.
This fact is also evident in application transactions. For example, If a product is exported from
Germany and the United States, its export control relevance must be checked on the basis of
both German and US foreign trade law, and, if necessary, be recorded on the Legal Control tab
using suitable classification. If the product is exported from countries other than Germany
and the United States, the foreign trade law of these countries must also be mapped in SAP
GTS in the form of legal regulations, so that the system can determine any license
requirement for exports from these countries.
Grouping of Various Legal Norms as Legal Regulations

In the EU, foreign trade law is heavily influenced by Council and European Parliament
regulations. Nevertheless, the national legislation of the Member States still has a
considerable amount of freedom. Therefore, before you start an implementation in an EU
Member State, you have to decide the following for each application area of Compliance
Management:
● Whether you map the relevant legal standards on a country-specific or cross-country basis
● Whether you combine supranational and national legislation into a single legal regulation
To be able to model foreign trade regulations in SAP GTS in a way that is sufficiently
differentiated for the purposes of legal control, you also have to create a separate legal
regulation for each country in the EU. Delivery Customizing contains some templates for this:

Lesson: Mapping Legal Norms in SAP GTS
● AWV (German Foreign Trade Regulations) — German foreign trade law

● EAR (Export Administration Regulations) — US foreign trade law
● ECCH (Export Control - Switzerland) — Swiss foreign trade law
The extent to which the templates for the United States and Switzerland can be adopted must
always be checked on an individual basis.
For an EU Member State, it is usually necessary to create a new legal regulation to map the
relevant national foreign trade law in conjunction with the relevant EU regulations. In
individual cases, the separation of Union law and national foreign trade law into two separate
legal bases may be useful instead. In the training system, for example, the German Foreign
Trade and Payments Law, the German Foreign Trade Regulations, and Council Regulation
(EU) No. 2021/821 “setting up a Union regime for the control of exports, brokering, technical
assistance, transit and transfer of dual-use items” (Dual-Use Regulation) were combined into
the legal regulation ZDUDE (Dual-Use Regulation, German foreign trade law).
Figure 13: Mapping of Different Legal Norms as Legal Regulations
For the embargo check and the sanctioned party list screening, you can also combine several
legal norms into a single legal regulation. This means that it is not necessary to map each of
the many EU embargo regulations separately. Instead, the regulations for imposing country-
specific embargoes can be summarized as a single legal regulation for the purposes of the
embargo check. Delivery Customizing goes one step further here: The legal regulation
EMBUN (Embargo - United Nations) is to map all embargoes resulting from Security Council
decisions in a neutral form. It could therefore be used globally.

LESSON SUMMARY

Unit 2
Lesson 2
Using Legal Regulations in Processes
LESSON OVERVIEW
This lesson focuses on activating legal regulations for the Compliance Management
application areas and determining legal regulations in the documents.
Business Example
The IDES group wants to check which laws and regulations are relevant to its international
trade processes.
LESSON OBJECTIVES
Activation of Legal Regulations

A two-step activation always follows the definition of a new legal regulation and the decision
to use one of the legal regulations delivered:
1. General activation of the legal regulation

(Where do the legal standards that are mapped with the legal regulation apply?)
2. Specific activation of the legal regulation for an application area

(Which application area works with the legal regulation and to what extent?)
You can activate a legal regulation for validity in a specific country. This type of activation is
useful for legal control in many cases. The embargo regulations of the EU apply directly in all
Member States. You can therefore activate the summaries of these regulations defined in
SAP GTS for the purposes of the embargo check for a country group representing the EU.

Figure 14: Activate Legal Regulations on Country or Country Group Level
In Customizing for the SAP GTS system, you can freely define country groups and assign
countries to them in any combination (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Legal Regulations → Define Country Group and → Assign
Countries to Country Group respectively). On the one hand, country groups are used to
activate legal regulations that apply in the same way in several states, such as the EU
embargo regulations. On the other hand, you can define the determination of import or export
licenses on a country-group-dependent basis (see the “Defining License Types” lesson).
You can also activate legal regulations for combinations of countries or country groups. In
Compliance Management, this option is primarily relevant for US re-export control within the
framework of legal control (see the “Setting up Re-export Control” lesson).
You activate a legal regulation in general in the cross-application-area settings of SAP GTS
Customizing (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Legal Regulations → Activate Legal Regulations at Country/Country Group Level.
The views for the specific activation of legal regulations for specific application areas of
Compliance Management are located in the relevant Customizing sections.
Menu paths:
● SAP Global Trade Services, edition for SAP HANA → Compliance Management → Embargo
Checks → Activate Legal Regulations
● SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Sanctioned Party List Screenings → Activate Legal Regulations
● SAP Global Trade Services, edition for SAP HANA → Compliance Management → Legal
Controls → Activate Legal Regulations

Lesson: Using Legal Regulations in Processes
Figure 15: Activation of Legal Regulations at Application Area Level
From the general activation, SAP GTS adopts the country or country group, or the
combinations of both basic elements. Compliance Management differentiates between goods
movements within the EU (receipts and dispatches) and third-country transactions (imports
and exports). The option of having domestic transactions checked in addition to cross-border
goods movements is primarily intended for sanctioned party list screening.
Determination of Legal Regulations in the Export Process

After replicating the feeder system document data, SAP GTS attempts to determine at least
one legal regulation for each application area. In Compliance Management, the supplying
plant of the feeder system document item plays the key role in the determination of legal
regulations. SAP GTS takes the departure country of the export from the address of the
business partner in the “Legal Unit” role that is assigned to the plant in the mapping of the
organizational structures. Depending on the specifications in the determination procedure for
determining legal regulations, the system then determines the legal regulation for the checks
in the relevant application area.
Delivery Customizing contains a determination procedure for each of the nine application
areas being part of SAP GTS (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Legal Regulations → Define Determination Procedure for Active
Legal Regulations).
The determination procedures are already assigned to the application areas for which they
are intended. This assignment is available in Customizing for the relevant application area
(example: SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Embargo Check → Assign Determination Procedure for Determining Active
Legal Regulations).
Each determination procedure contains at least one determination strategy (folder
Assignment of Determination Strategy). Figure 16 shows the example of procedure LELDT,
which is intended for determining legal regulations for legal control.

Figure 16: Procedures for Determining Legal Regulations
The six determination strategies available for selection are rooted in the program code:
● ALRG01 (Det. Legal Regulation at Country Level)
● ALRG02 (Det. Legal Regulation at Country/Country Level)
● ALRG03 (Det. Legal Regulation at Country/Country Group Level)
● ALRG11 (Det. Legal Regulation at Country Group Level)
● ALRG12 (Det. Legal Regulation at Country Group/Country Level)
● ALRG13 (Det. Legal Regulation at Country Group/Country Group Level)
If a determination procedure contains several determination strategies, sequence numbers

define the access sequence. In the details of the determination procedure, you choose
between exclusive access (Determination Using First Successful Strategy) and determination
of multiple legal regulations (Determination Across All Strategies).
In the example of the determination procedure LELDT, the system first tries to find a legal
regulation for the legal control that has been activated for the departure country. If this
determination fails or if multiple access is intended, the system makes a second attempt
using a combination of the departure country and destination country group. It therefore
searches for a legal regulation that applies only in the internal relationship between the
departure country and the members of a specific country group. If necessary, the system
determines another legal regulation in the third attempt, using a combination of the country
group of departure country and the destination country.
The determination strategies ALRG02, ALRG03, ALRG12, and ALRG13 are suitable for
mapping prohibitions and restrictions that individual countries or country groups have
defined exclusively in relation to certain other countries or country groups. However, if legal
norms apply regardless of the destination country of the export, it is usually sufficient to
determine the corresponding legal regulations using the determination strategies ALRG01 or
ALRG11.

Lesson: Using Legal Regulations in Processes
You can check the result of the determination of legal regulations in the check log of the
customs document.
LESSON SUMMARY


Unit 2
Learning Assessment
1. Legal regulations form the basis for most of the Customizing settings in SAP GTS.
Determine whether this statement is true or false.
X True
X False
2. One legal regulation can be used for several application areas.

X True
X False

Unit 2
1. Legal regulations form the basis for most of the Customizing settings in SAP GTS.
X True
X False
Correct. Legal regulations form the basis for most of the Customizing settings in SAP
GTS.
2. One legal regulation can be used for several application areas.

X True
X False
Correct. Each application area requires at least one legal regulation.

UNIT 3 Embargo Check
Lesson 1
Maintaining Embargoes and Check Settings 37
Lesson 2
Checking and Releasing Documents 41
UNIT OBJECTIVES
● Maintain embargoes and check settings

● Set up the embargo check
● Check and release documents
● Release documents blocked by the embargo check

Unit 3: Embargo Check

Unit 3
Lesson 1
Maintaining Embargoes and Check Settings
LESSON OVERVIEW
Compliance Management separates the check of country-specific and country-independent
embargoes. You can use the embargo check to identify country-specific embargo situations
in your purchasing and sales processes. This lesson shows you how to set up the embargo
check in SAP GTS.
Business Example
The IDES group has some business partners in countries on which the Security Council has
imposed embargoes. To ensure that it does not inadvertently violate these embargoes, the
company decides to block all purchase orders from vendors as well as sales orders for
customers in embargo countries for the time being as a precautionary measure.
LESSON OBJECTIVES
Embargoes as Master Data

Many countries have imposed embargoes on a number of individual countries, political
groups, and natural or legal persons. These embargoes are often based on UN Security
Council resolutions. An embargo prohibits trade with the state, group, or person in question.
In many cases, capital transactions with and providing certain services to the state, group, or
person in question are also prohibited. The financial assets of the affected party can be
frozen.
The EU has three kinds of embargoes:
● Total embargoes
● Partial embargoes
● Arms embargoes
A total embargo prohibits any kind of trade with the country in question. This type of embargo
usually also includes services and financial transactions. In certain circumstances, this type of
embargo does allow for the supply of humanitarian goods in individual cases and subject to
authorization.
A partial embargo is intended to prohibit trade in specific goods only. These goods are
explicitly listed in the corresponding legal regulation. Arms embargoes, on the other hand,
apply only to armaments. In the past, the EU has imposed arms embargoes on the
Democratic Republic of the Congo, Rwanda, Somalia, and Sudan, for example. In many cases,
partial embargoes and arms embargoes may be imposed together. The United States have

partially implemented the same Security Council resolutions and therefore imposed similar
embargoes.
Figure 17: Embargoes at Legal Regulation Level
You always enter country-specific embargoes in SAP GTS as master data using the Manage
Embargo Situations app. You can choose between three differentiation levels:
● Blanket identification of a country as an embargoed country
● Identification of a country as an embargoed country for a specific legal regulation
● Identification of a country as an embargoed country in relation to another country for a
specific legal regulation
If you decide on the first level, SAP GTS blocks every customs document with a check-
relevant document partner in the embargo country without exception. The destination
country of the goods receipt and the departure country of the goods issue are not relevant.
This form of master data maintenance is therefore only applicable for embargoes with global
reach.
However, even embargoes based on Security Council resolutions do not automatically apply
in United Nations member states. Resolutions must first be transposed into national law – or,
in the case of the EU, supranational law. Therefore, it makes sense to differentiate according
to legal basis in SAP GTS not only when defining legal regulations, but also when maintaining
master data.
In most cases, the identification of a country as an embargoed country is sufficiently
differentiated at the level of a specific legal regulation. If a country has unilaterally imposed an
embargo on another country, the third option for master data maintenance is suitable. This
allows you to map the US embargo against Cuba correctly, for example.
You can find the Manage Embargo Situations in the SAP Fiori launchpad in the Compliance
space on the Embargo page. In the app, you can choose between all three embargo
maintenance variants.

Lesson: Maintaining Embargoes and Check Settings
Setting Up the Embargo Check

Setting up the embargo check requires little effort in relation to the configuration of the other
two application areas of Compliance Management. The legal regulation of the delivery
Customizing EMBUN (Embargo - United Nations) can be used as a template if required (menu
path: SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Embargo Checks → Control Settings for Embargo Check). You must make up
to four basic decisions in advance:
● Which partner functions should be included in the embargo check?
● Do you want to inform employees of a document block via e-mail?
● Do you want employees who release documents to enter a reason predefined in
Customizing and/or enter an explanation as free text?
● If you are also using Customs Management: Should the incompleteness check in customs
declarations react to an embargo situation with a warning message or an error message?
Figure 18 shows an example of the settings for the legal regulation ZEMEU (Country-specific
embargoes - EU) of the training system.
Figure 18: Embargo Control Settings
Partner groupings (synonym: partner groups) in the Partners To Check area determine which
partner functions are relevant for the embargo check. Delivery Customizing contains a
suitable partner grouping for the embargo check in goods receipt processes and in goods
issue processes (PGEMB1 and PGEMB2). If necessary, create your own partner groupings in
the customer namespace to adjust the composition of partner functions to suit the situation
in your company (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Partner Structures → Define Groups of Partner Functions).
SAP GTS checks the country code in the address of all document partners that occur in one of
the partner functions of the partner grouping. For a document block, it is sufficient for one of
the check-relevant partners to be located in an embargoed country. The arrangement of the
partner functions in the partner grouping is therefore irrelevant; their completeness is what is
decisive.
In the Workflow area, set the indicator E-Mail When Document Is Blocked if you want SAP GTS
to inform one or several users of a document block due to the embargo check via e-mail. You

use the Maintain User Groups transaction (transaction code SUGR) to create user groups for
notification control. This transaction is located in the area menu of system administration
(System Communication button, Notifications area).
Note:
The user master records of the group members must each contain an e-mail
address (Address data screen, Communication area).
In the next step, you assign the user group to a combination of foreign trade organization and
legal regulation (Assignment of User Groups to Legal Regulation/Foreign Trade Org. view,
transaction code /SAPSLL/USGR01). The e-mails are sent using SAPconnect (transaction
code SCOT).
SAP GTS can also perform an embargo check as part of the incompleteness check of the
customs declaration. If you use this additional function, you can react to changes to the legal
situation made at short notice. If the system detects an embargo situation when checking the
customs declaration, a corresponding entry appears in the incompleteness log. If the
indicator C Error Message is set in the Response to Doc. Block field in the control settings of
the legal regulation for the embargo check, the customs declaration is assigned the status
“Incomplete”. Therefore, no messages can be issued.
In Customizing for Compliance Management, you can define possible reasons for document
release in the embargo check and in the sanctioned party list screening (menu path: SAP
Global Trade Services, edition for SAP HANA → Compliance Management → Define Reasons
for Releasing Blocked Documents and Business Partners). When releasing documents or
business partners, users must select one of the predefined reasons from a list.
LESSON SUMMARY

Unit 3
Lesson 2
Checking and Releasing Documents
LESSON OVERVIEW
In this lesson, you will learn how to use the embargo check in logistics processes, and to
control incoming and outgoing payments.
Business Example
The IDES group has some business partners in countries on which the Security Council has
imposed embargoes. To ensure that it does not inadvertently violate these embargoes, the
company decides to block all purchase orders from vendors from embargo countries for the
time being as a precautionary measure.
LESSON OBJECTIVES
Scope of Check
The embargo check in Compliance Management is strictly country-specific. The traded
products and the persons involved in the transaction are not relevant for the check. If a
country is flagged as an embargoed country in SAP GTS, as a precautionary measure the
system blocks any document that contains a check-relevant business partner in this country.
This block can be removed manually by the user or automatically by the system if blocked
documents are regularly rechecked and the relevant embargo has been lifted in the
meantime.
Therefore, SAP GTS always forces a case-by-case check in a country-specific embargo
situation. Each transaction in which a business partner is involved in an embargoed country is
to be checked individually by a knowledgeable employee in the context of the respective
embargo regulations. If the employee finds that the transaction is not affected by the
embargo, they release the customs document in SAP GTS. The system logs this release and,
depending on the configuration, requires a reason to be entered.
Caution:
The release of a document blocked as a result of the embargo check cannot be
revoked. SAP GTS only checks a released document again if a partner or item
has been added to the feeder system document. A manual change of the country
indicator in the address of a document partner in the document itself also
triggers a recheck after a previous release.
Since EU embargo regulations apply in all Member States, it makes sense to activate a legal
regulation to map this regulation at the level of the country group EG provided in delivery
Customizing or a similar self-defined country group. Since the determination procedure

LEEMB delivered by SAP is only assigned the determination strategy ALRG01 (Determine
Legal Regulation at Country Level), the procedure must first be replaced with a user-defined
determination procedure with the determination strategy ALRG11 (Determine Legal
Regulation: Country Group Level) (menu path: SAP Global Trade Services, edition for SAP
HANA → Compliance Management → Embargo Checks → Assign Determination Procedure for
Active Legal Regulations).
When you activate a legal regulation for an embargo check, you must take into account that
SAP GTS always derives the destination country of a goods issue for the embargo check from
the document address of the business partner in the ship-to party partner function.
Therefore, the possible partner configurations in the check-relevant documents play an
important role in deciding as to which level a legal regulation is activated for the embargo
check.
If you supply dealers in other Member States or domestically who then resell your products
(with your knowledge or even on your behalf) to end customers in third countries, you must
activate the legal regulation for checking dispatches or for checking all goods issues.
Figure 19: Determination of Destination Country
You can identify the country of destination as well as the country of the ultimate consignee on
the Geography tab at document item level.
In the training system, the legal regulation ZEMEU is activated for exports only. Since the
ship-to party is domestic, the transaction remains unchecked. Only when the check
framework is extended to all goods issue processes by a corresponding change to the
activation, does the system recognize the embargo situation that arises from the end
customer’s country.
Check of Accounting Documents

In logistics, you can subject purchasing and sales documents as well as inbound and
outbound deliveries to an embargo check in SAP GTS. It does not matter how these
documents were created in the SAP ECC or SAP S/4HANA feeder system. It is also possible
to check accounting documents for incoming and outgoing payments. However, these
documents must be created using certain programs:
● Transaction Automatic Payment Transactions (transaction code F110)

Lesson: Checking and Releasing Documents
● Transaction Automatic Payment Transactions for Payment Requests (transaction code

F111)
● Transaction Payment with Print (transaction code FBZ4)
Figure 20: Replication of Accounting Documents
In the feeder system, you activate the transfer of accounting documents in Customizing for
Financial Accounting (menu path: Financial Accounting → Basic Settings for Financial
Accounting → Check in SAP GTS for FI → Activate Check in SAP GTS for FI).
In Customizing for the SAP GTS system, you have to make some application-specific mapping
settings for the replication of accounting documents.
Mapping objects
● Partner functions
● Document types for incoming and outgoing payments
● Item category
In contrast to the preparations for replicating logistics documents, this mapping does not
involve linking essential elements of feeder system documents with counterparts in SAP GTS.
Accounting documents have document types, but do not have item categories or partner
roles. The mapping settings at application level FI0A (FI Payment) are used in the SAP GTS
system to transfer the accounting document data which is transferred from the feeder
system to the structures of a customs document.
Delivery Customizing already contains suitable partner functions, document types, and an
item category. The document types FIIN (Incoming Payments) and FIOUT (Outgoing
Payments), and the document types for mapping the logistics feeder system document types,
are located in the Customs Document folder of the document type structure (menu path: SAP
Global Trade Services, edition for SAP HANA → General Settings → Document
Structures → Define Document Types for Application Areas).

The universal item category FI0A (Payment Item ) is provided in the folder Item Categories for
Customs Documents of the item category structure (menu path: SAP Global Trade Services,
edition for SAP HANA → General Settings → Document Structures → Define Item Categories
for Application Areas). All of the partner functions required for successful accounting
document replication are located in Customizing for the partner structure (menu path: SAP
Global Trade Services, edition for SAP HANA → General Settings → Partner
Structures → Define Partner Functions).
You can pseudo map these elements either at the level of logical feeder systems or at the level
of groups of logical systems. Figure 21 shows an example of the assignment of application-
specific partner functions to the notional partner roles of a group of logical systems (menu
path: SAP Global Trade Services, edition for SAP HANA → General Settings → Partner
Structures → Assignment of Partner Functions from Feeder Systems → Assign Partner
Function at Feeder System Group Level).
Figure 21: Partner Functions Payment
In this way, you assign the document types FIIN and FIOUT the document types (that do not
exist in the feeder system) FIIN and FIOUT, and the item category FI0A its notional equivalent
FI0A (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Document Structures → Assignment of Document Types from Feeder
Systems → Assign Document Type at Feeder System Level or → Assign Document Type at
Feeder System Group Level and SAP Global Trade Services, edition for SAP HANA → General
Settings → Document Structures → Assignment of Document Types from Feeder
Systems → Assignment of Item Categories from Feeder Systems → Assign Item Category at
Feeder System Level or → Assign Item Category at Feeder System Group Level).
Note:
The document types FIIN and FIOUT are not assigned to the accounting document
types defined in Financial Accounting in the SAP ECC or SAP S/4HANA feeder
system in this mapping.
In delivery Customizing, the document types FIIN and FIOUT and the item category FI0A are
already activated for the embargo check (menu path: SAP Global Trade Services, edition for
SAP HANA → General Settings → Document Structures → Activate Document Types for
Application Areas or → Activate Item Categories for Application Areas).

Lesson: Checking and Releasing Documents
LESSON SUMMARY


Unit 3
Learning Assessment
1. On which levels can you activate the embargo check in SAP GTS?
X A Country
X B Legal regulation and country of departure or destination
X C Legal regulation
X D Business partner
X E Legal regulation and combinations of countries of departure and destination
2. Which partner function is relevant for the determination of the destination country in
embargo check?
Choose the correct answer.
X A Payer
X B Ship-to party
X C Sold-to party
X D Ultimate consignee (end customer)

Unit 3
1. On which levels can you activate the embargo check in SAP GTS?
X A Country
X B Legal regulation and country of departure or destination
X D Business partner
X E Legal regulation and combinations of countries of departure and destination
Correct. You can activate the embargo check at country level, for a combination of legal
regulation and country of departure or destination, and for a legal regulation and
combinations of countries of departure and destination.
2. Which partner function is relevant for the determination of the destination country in
embargo check?
X A Payer
X B Ship-to party
X C Sold-to party
X D Ultimate consignee (end customer)
Correct. The country of the ship-to party is the destination country in embargo check.

UNIT 4 Sanctioned Party List
Screening
Lesson 1
Managing Sanctioned Party Lists 51
Lesson 2
Analyzing Check Results 57
UNIT OBJECTIVES
● Manage sanctioned party lists as master data in SAP GTS

● Generate comparison indexes for sanctioned party list screening
● Explain the substeps of sanctioned party list screening
● Configure a procedure for comparing addresses in SAP GTS

Unit 4: Sanctioned Party List Screening

Unit 4
Lesson 1
Managing Sanctioned Party Lists
LESSON OVERVIEW
The embargoes that are dealt with in the “Sanctioned Party List Screening” unit are aimed at
certain natural and legal persons listed in name lists, regardless of their whereabouts. This
lesson deals with mapping such name lists as master data in SAP GTS.
Business Example
In the future, the IDES group intends to check each time a purchasing or sales transaction is
performed whether the business partners involved are on a sanctioned party list.
LESSON OBJECTIVES
Sanctioned Party List Entries as Master Data

In SAP GTS, name lists consist of individual master records for each entry. You can create
such master records manually. However, due to the large (and still growing) number of list
entries, manual maintenance of entire name lists is not really possible in practice.
Therefore, various data providers offer these lists in the annexes of the EU embargo
regulations and the sanctioned party lists of other states in XML format for uploading to SAP
GTS for purchase. These offers are a kind of subscription. This means that the system first
provides you with name lists for the initial upload. Update files are then made available to you
at regular intervals. These update files contain either only new or changed entries, or the
complete dataset that has been extended to include new entries.
Note:
If persons are removed from a sanctioned party list on the basis of decisions made
by the sanctions committees of the Security Council, the European Council, or the
relevant national authority, the data providers generally set the date of withdrawal
as the validity end date of the data record.

Figure 22: Upload of Sanctioned Party List Entries
You can display sanctioned party list master data as lists or individually. There are two apps
available in the SAP Fiori launchpad:
● Display of individual list entries (Manage Sanctioned Party List Master)
● Display of entire lists or selected entries (Display Sanctioned Parties)
You can find both apps in the SAP Fiori launchpad in the Compliance Screening space on the
Sanctioned Party Lists page.
Sanctioned party list master data have a type of header segment from which you can extract
higher-level data, such as the legal regulation, the type of list, and the validity dates. Each
master record also contains a separate segment for the name, or names, and addresses of
the listed person.

Lesson: Managing Sanctioned Party Lists
Figure 23: Sanctioned Party List Entries as Master Data
If a person appears under different pseudonyms, the names in the master record are linked to
each other using a reference type. For example, the reference type AKA stands for “also
known as”, a link often used in the original entries of the name lists. The Address section lists
all known residences for the listed person. Often, however, this area of the master record
remains empty because the relevant committees and authorities do not know where the
person resides.
You can use the Upload SPL Master Data transaction (transaction code /SAPSLL/SPL_UL01)
to upload sanctioned party list entries to your SAP GTS system in XML format. In addition to a
legal regulation, you also have to specify the type of sanctioned party list on the initial screen
of the transaction.
You define the keys of these list types in the same way as you define the reference types for
linking pseudonyms in Customizing for sanctioned party list screening at legal regulation level
(menu path: SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Sanctioned Party List Screenings → Control Settings for Sanctioned Party List
Screening). Delivery Customizing provides a sample legal regulation for sanctioned party list
screening under the key SPLUS (Sanctioned Party List Screening). A larger number of list
types are already assigned to this sample. For example, it contains “Specially Designated
Nationals” (SDN) and “Global Terrorists” (SDGT and SDME respectively).
The legal regulation SPLUS is tailored to the legal situation in the United States. Even if you
want to check that your business partners match entries in the name lists of U.S. authorities,
it makes sense to define your own legal regulation that takes the relevant EU legislation into
account. In each case, you must clarify before the implementation whether you really want to
upload the entire offering from the relevant data provider to the SAP GTS system.
When you configure legal regulations for sanctioned party list screening, you always decide
whether, and to what extent, you take embargo measures from other countries into account.

In any case, you should always activate a legal regulation for sanctioned party list screening
for the screening of domestic business.
Comparison Indexes
Sanctioned party list screening is based on a calculation of the percentage match of
screening-relevant address components. If this percentage is above a threshold value defined
in the configuration, SAP GTS assumes that the business partner may have the identity of the
listed person. The “Analyzing Check Results” lesson covers these settings.
To calculate the percentage match of the screening-relevant address components, SAP GTS
splits the addresses of business partners and sanctioned party list entries into search terms
and then groups these search terms in comparison indexes. You use the programs /SAPSLL/
SPL_CREATE_SEARCHTADRC (business partner) and /SAPSLL/SPL_CREATE_SEARCHTERMS
(sanctioned party list entries) to generate comparison indexes. You can also execute both
programs online using the transactions Create Comparison Index for Business Partner
(transaction code /SAPSLL/SPL_STBP) and Create Comparison Index for Sanction List
(transaction code /SAPLL/SPL_ST01) respectively.
Figure 24: Comparison Indexes for SPL Screening
If you index a business partner address or sanctioned party list entry online, you can display
the result in an overview. This function is also useful when testing the configuration.
Example of a business partner address in the training system:
Table 1: Indexing a Business Partner Address (Example)

Name Food for You No. 1
Catering Service
Street/House Number Bertolt-Brecht-Strasse 55
Postal Code/City 10101 Berlin
Country DE

Lesson: Managing Sanctioned Party Lists
Log of the indexing of this business partner address:
Figure 25: Indexing of a Business Partner Address
SAP GTS has indexed the business partner address at the level of the self-defined legal
regulation ZSPEU (Personal sanctions - EU). List type DPLEU (Denied Persons Lists (EU))
assigned to the legal regulation has a minimum length of three characters for the address
element “Name”. The name components “No” and “1” are therefore eliminated before
indexing. The system does not include the company extension “Service” defined as an
exclusion text in the index either.
SAP GTS eliminates ligatures when setting up the index if it does not explicitly provide a
different configuration for the comparison procedure in Customizing. In addition, all
lowercase letters are automatically converted to uppercase letters. Different spellings of
address components are aligned in this way.
You influence the structure of the comparison indexes by configuring a comparison
procedure that is defined in Customizing and assigned to the legal regulation for sanctioned
party list screening (menu path: SAP Global Trade Services, edition for SAP
HANA → Compliance Management → Sanctioned Party List Screenings → Define Comparison
Procedure → Define Comparison Procedure for Address Comparison). For some settings, you
can also access this comparison procedure using transaction Manage SPL Comparison Terms
(transaction code /SAPSLL/VC_CMPAS).
It usually makes sense to include common components of the company, such as
“Corporation” or “Ltd” as exclusion texts in the comparison procedure. Often, these name
components significantly increase the number of obviously incorrect hits in sanctioned party
list screening, without making a significant contribution to the identification of a listed person.
You can use alias terms to replace different forms of the same name, for example, “Tom” as a
short form of “Thomas”. In the Normalization folder, you can replace individual letters or
sequences of letters with other letters, for example, the letter sequence “ue” with the umlaut
“ü”.
The characters collected in the Delimiter folder, which can separate name and other address
components, are crucial for the indexing of business partner addresses and sanctioned party
list entries. The system interprets the hyphens in the address of the business partner in the

example shown (“Bertolt-Brecht-Strasse”) as separators, and splits the street name into
three search terms (BERTOLT, BRECHT, and STRASE).
After each change to the comparison procedure or another Customizing setting that controls
sanctioned party list screening, and after each upload of a new or updated list, you have to
regenerate the comparison indexes. The comparison index for the sanctioned party list
entries must also be aggregated (transaction Aggregate Comparison Index of Sanction Lists,
transaction code /SAPSLL/SPL_ID01). Knowledge Base Article (KBA) 2074620 describes
the procedure.
Note:
When new or changed business partners are transferred, SAP GTS adjusts the
comparison index automatically.
Positive and Negative Lists

Even if sanctioned party list screening is configured appropriately, the system detects
matches between business partner addresses and sanctioned party list entries, which can be
identified as a mistake at first glance. The blocked business partners must then be released
manually. The system notes the release in the event of rescreening, but only until the next
upload of new or updated lists. The interim transfer of new or changed business partner
master data and changes to the relevant Customizing settings also result in “memory loss”.
This means that blocks occur again.
If you want to permanently exclude a business partner from sanctioned party list screening,
you can place the business partner on the positive list. This function is available in the lists of
screened and blocked business partners (Positive List button). Depending on the Customizing
settings, you must justify this decision using a predefined reason for release and/or a free-
text comment (see the “Checking and Releasing Documents” lesson). The system flags the
business partner as a positive list entry in its master record (SAP GTS tab, Flagged on
Positive/Negative List column). You can use the Display Positive List - BPs app to view the
positive list.
If you want to permanently block a business partner in SAP GTS regardless of an embargo
situation, that is, for any other reason, you can place it on the negative list. Negative list
entries are also excluded from sanctioned party list screening. The system flags the business
partner master record accordingly on the SAP GTS tab. You can use the Display Negative List
- BPs app to display the negative list.
You can also perform sanctioned party list screening for both lists from the respective app.
During the check of the positive list, at least a large majority of the business partners are likely
to be blocked again. In contrast, they are likely to be released during the check of the negative
list.
LESSON SUMMARY

Unit 4
Lesson 2
Analyzing Check Results
LESSON OVERVIEW
In this lesson, you will learn about the process of sanctioned party list screening and the
Customizing settings that you can use to influence how screening works.
Business Example
In the future, the IDES group intends to check each time a purchasing or sales transaction is
performed whether the business partners involved are on a sanctioned party list.
LESSON OBJECTIVES
Time of Sanctioned Party List Screening

The main function of sanctioned party list screening in Compliance Management is to
compare business partner addresses with sanctioned party list entities. If the system
identifies a match between a business partner address and a sanctioned party list entity, it
blocks the business partner in question. Replicas of feeder system documents that contain a
blocked business partner are also blocked. Any documents that existed before the screening
was run must be checked again.

Figure 26: SPL Screening in Purchasing and Sales Processes
When configuring sanctioned party list screening, you must first decide whether the address
comparison is to take place immediately after the transfer of a partner master record or
document (synchronous), or at a later point in time that can be determined on an individual
basis (asynchronously). For document screening, you make this decision at item category
level, and for master data screening you make it at business partner role level.
To define the time for screening business partner master data, in Customizing for Compliance
Management, choose SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Sanctioned Party List Screenings → Activate Business Partner at Business
Partner Function Level. In the Time of SPL Check field, select the indicator 1 (Synchronous -
When Object Is Updated) if you want the master data to be screened synchronously. For the
asynchronous screening, which is useful during the initial load, select the indicator 0
(Asynchronous - When Function Is Called) instead.
The indicator in the Type of SPL Block field is only relevant for asynchronous screening. If
indicator 1 (Process is interrupted - system removes block) is set, SAP GTS blocks new or
changed business partners until asynchronous screening as a precautionary measure (“soft”
block).
You define when document addresses are checked when you activate item categories for
sanctioned party list screening (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Document Structures → Activate Item Categories for Application
Areas). In the dialog structure, open the Activation for Sanctioned Party List Screening folder
and select the required item category. In the SPL Screening Time field, select the appropriate
screening time.
During the replication of feeder system documents, the system always checks the block
status of the document partners. If a partner is already blocked due to previous sanctioned
party list screening, SAP GTS also blocks the document. If a user changes the address of a
check-relevant business partner in the feeder system document, SAP GTS also blocks the
customs document during an asynchronous check as a precautionary measure. The check

Lesson: Analyzing Check Results
log of the customs document contains an entry with the text “Partner Address Was Changed
Manually” to justify the block.
To subject the changed document addresses to sanctioned party list screening, use the
Recheck Documents app or schedule the program /SAPSLL/CUHD_MASS_REFRESH_EXIM for
regular background processing. In synchronous screening, the system compares changed
addresses with sanctioned party list entries immediately after the documents have been
transferred.
Sanctioned Party List Screening Process

Sanctioned party list screening based on the standard SAP GTS search algorithm consists of
three substeps:
1. Determining the search terms that are relevant for comparison from all the search terms
for an address
2. Calculating the percentage match for each relevant search term
3. Calculating the percentage match for each address element (for example, for the name)
As a first step, SAP GTS checks each search term to see whether it is identical to or contained
in its comparison term. In delivery Customizing for sanctioned party list screening (control
settings for legal regulation SPLUS), a comparison of the terms is preset only from the
perspective of the sanctioned party list entry (Scope of Screening area, Search Strategy field,
SPL Entry Searches in Address Entry indicator). If you want SAP GTS to compare business
partners and sanctioned party list addresses in both directions when selecting the relevant
search terms, set the indicator A (SPL Entry Searches in Address Entry and Vice Versa) in the
Search Strategy field instead.
Figure 27: Audit Trail for a Business Partner
In the example in figure 27, the business partner address of customer 10983 (California
Motomarket Ltd.) was compared, amongst others, with the sanctioned party list entries
30540 (Omar Carillo), 36190 (Mark Belinic), and 36370 (Ali Chan). SAP GTS already sorted
out individual name components when indexing the addresses. Of the name components
contained in the comparison index, only the terms MOTOMARKET, CALIFORNIA, OMAR,
MARK, and ALI qualified for the second screening step from the first screening step. Tables 5
and 6 provide an overview of this filtering.

Table 2: Business Partner Address

Term Result
CALIFORNIA Contains comparison term ALI
MOTOMARKET Contains comparison terms MARK and OMAR
LTD Exclusion text (period is a delimiter)
Table 3: Sanctioned Party List Entries

Term Result
CARILO Not identical to or contained in comparison term
OMAR Contained in comparison term MOTOMARKET
BELINIC Not identical to or contained in comparison term
MARK Contained in comparison term MOTOMARKET
ALI Contained in comparison term CALIFORNIA
CHAN Not identical to or contained in comparison term
In the second screening step, SAP GTS calculates the percentage match of the search terms.
The system first counts the characters that make up the terms. It then determines the
number of identical letters. At the end of the screening step, the system divides the number of
matching characters by the total number of characters in the comparison term and multiplies
the result by one hundred to calculate the percentage match.
Table 7 contains an example of this calculation.
Table 4: Calculation of Percentage Match (Example 1)

Original business partner Original sanctioned party
address list entry
Term Motomarket Omar
Total number of characters 10 4
Number of matching characters 4
Percentage match (4 : 4) x 100 = 100
The term “Motomarket” consists of ten characters and the term “Omar” consists of four
characters. Four characters are the same in both terms. SAP GTS divides the number of
matching characters by the total number of characters of the comparison term “Omar” and
multiplies the result by 100. This calculation results in a hundred percent match between the
two terms.
Table 5: Calculation of Percentage Match (Example 2)

address list entry

Term Motomarket Omar

Total number of characters 10 4
Number of matching characters 4
In the second example, SAP GTS divides the number of matching characters by the total
number of characters of the comparison term “Motomarket” and multiplies the result by 100
again. The match percentage is now only 40.
In the third screening step, SAP GTS divides the number of matching search terms of an
address element by the total number of search terms for this element. When comparing
“California Motomarket” and “Omar Carrillo”, SAP GTS calculates a match percentage of 50:
the names of the business partner and the sanctioned party list entry each consist of two
terms. One term matches (“Omar”).
Table 6: Calculation of Percentage Match for Name Address Element

address list entry
Name California Motomarket Omar Carrillo
Total number of terms 2 2
Number of matching terms 1
According to the delivery Customizing settings for sanctioned party list screening, a 50
percent match of the name is sufficient to identify the business partner with the sanctioned
party list entry.
For the search term US – the country code in the business partner address – SAP GTS
assumes a hundred percent match, even though the address of the sanctioned party list entry
does not contain any country codes. In the case of sanctioned party list entries without a
country specification, the system always assumes that the listed person can be located
anywhere. According to the worst-case principle, the percentage match is therefore 100 for
each country.
Configuration of a Comparison Procedure

You can influence the determination of matches between business partners and sanctioned
party list addresses in a control procedure for the address comparison (menu path: SAP
Global Trade Services, edition for SAP HANA → Compliance Management → Sanctioned Party
List Screenings → Define Comparison Procedure → Define Comparison Procedure for SAP
GTS Search). In this comparison procedure, you first define which address elements are
included in the comparison.
The comparison procedure SPLUS in delivery Customizing consists of the address elements
country (C1), city (I1), name (N1), and street (S1). All four elements are relevant for the
address comparison (indicator Check Object set). A linking operator is assigned to each of the
four address elements. To identify a business partner address with a sanctioned party list
entry, the address elements “country” and “name” that are linked with a logical AND must
match in combination with at least one of the two address elements “city” or “street” linked

with a logical OR. If the address of the sanctioned party list entry contains the country and
name, these two address elements must not only match their counterparts in the business
partner address, but also either the address element “city” or the address element “street”.
Two percentages are assigned to each address element of the comparison procedure (folder
Detail Control in the dialog structure). The first value defines the minimum percentage match
of two search terms (screening step 2). The second value refers to the address element as a
whole. Address elements can consist of several search terms. For example, a name usually
consists of one or more first names and last names. The second percentage in the detail
control therefore determines the minimum match between two complete address elements
(screening step 3).
The figure 28 shows the settings for the comparison procedure SPLUS for the address
element “name”.
Figure 28: Specifications for Calculating Match Percentages
The search terms that make up the name must therefore match at least 70% of their
respective comparison term in order to be included in the third screening step (value in the
Search Term field). The match percentage is calculated from the perspective of the
sanctioned party list entry (indicator Basis for Comparison Exclusively from Sanctioned Party
List in the Search Term Origin) field.
In the first example (table 7, “Calculation of Match Percentage (Example 1)”), this
specification leads to the calculation of a hundred percent match of the search term “Omar”
with the search term “Motomarket”. The two search terms are therefore used to calculate the
match for the entire name in the third screening step. The same applies to the search terms
“Mark” (100% match with the comparison term “Motomarket”) and “Ali” (hundred percent
match with the comparison term “California”).
In the comparison procedure SPLUS, the name of the sanctioned party list entry is used as
the basis for calculating the percentage match (indicator Only Number of Terms for Each SPL
Name in the Display Base Value field). The threshold value for the address element Name is
50% (Originating Feature field). The match between the names in the example in table 9,
“Calculation of Match Percentage for Name Address Element”, is therefore high enough.
In practice, these settings in delivery Customizing often lead to a high number of blocks that
can be identified as unjustified at first glance. To reduce the number of obviously incorrect

hits without restricting the check, it makes sense to adjust the settings in a user-defined
comparison procedure.
The Search Term Origin field also contains the indicators 1 (Basis for Comparison Exclusively
from Business Partner) and 2 (Basis for Comparison the SPL and BP Addresses in Parallel) for
selection. With option 2, SAP GTS compares the business partner address with the
sanctioned party list entry’s address and vice versa, which means that it always calculates
two percentages for each term. SAP GTS only includes the search term in the third screening
step if both percentages match at least the value in the Search Term field. For the field Display
Base Value there is a comparable selection.
As a rule, it is recommended that you set the indicator 1 (Number of Terms in Each SPL List
Name and Partner Name) and enter the value 51 in the Originating Feature field. Since
calculating a percentage match twice places a higher load on system performance,
comparative tests are useful.
LESSON SUMMARY


Unit 4
Learning Assessment
1. You can upload sanctioned party lists from XML files purchased from a data provider or
maintain them manually in the system.
X True
X False
2. Bring the following steps into the correct order.

Arrange these steps into the correct sequence.
0 Calculating the match percentage for each address element (for example, for the
name)
0 Determining the search terms that are relevant for comparison from all the search
terms for an address
0 Calculating the match percentage for each relevant search term
0 Generating comparison index

Unit 4
1. You can upload sanctioned party lists from XML files purchased from a data provider or
maintain them manually in the system.
X True
X False
Correct. You can upload sanctioned party lists from XML files purchased from a data
provider or maintain them manually in the system.
2. Bring the following steps into the correct order.

Arrange these steps into the correct sequence.
4 Calculating the match percentage for each address element (for example, for the
name)
2 Determining the search terms that are relevant for comparison from all the search
terms for an address
3 Calculating the match percentage for each relevant search term
1 Generating comparison index
Correct. The correct order is 4, 2, 3, 1.

UNIT 5 Legal Control
Lesson 1
Maintaining Goods Lists and Classifying Products 69
Lesson 2
Defining License Types 73
Lesson 3
Setting up License Determination 79
Lesson 4
Setting up Re-export Control 85
UNIT OBJECTIVES
● Create numbering schemes for product classification

● Manage goods lists in the system
● Define license types
● Configure the determination of license types and licenses
● Set up license determination in Customizing
● Explain license determination at document level
● Set up reexport control
● Perform a re-export calculation

Unit 5: Legal Control

Unit 5
Lesson 1
Maintaining Goods Lists and Classifying
Products
LESSON OVERVIEW
The lessons in the “Legal Control” unit deal with restrictions in the form of license
requirements that are a direct result of the properties or possible use of the goods to be
exported. This lesson focusses on the preparation of license management at the level of the
goods in question.
Business Scenario
The IDES group intends to export new ball bearings to various countries. However, ball
bearings of this type are categorized as dual-use items in the Dual-Use Regulation of the EU
and in the EAR.
LESSON OBJECTIVES
Numbering Schemes for Mapping Goods Lists

If you want to use the legal control for exports, you have to classify all products affected by
the control measures in accordance with the corresponding list or lists of goods. On the one
hand, this classification is a prerequisite for a product-related document check; on the other
hand, it is required for the administration of export licenses in the SAP GTS system.
Both the list of dual-use items in Annex I of the Dual-Use Regulation and the Commerce
Control List (CCL) in Supplement No. 1 to §774.1 of the EAR consist of subgroups that are
classified with alphanumerical character combinations. Thus, codes 3A to 3E stand for
“general electronics”, and 4A to 4E for “computers”, for example. The first digit indicates the
category and the second digit indicates the class of the listed items.
This coding is specified in the Wassenaar Arrangement. The first two digits of the items are
therefore identical in all states signatory to the Wassenaar Arrangement. The actual items are
assigned five-digit keys and are defined in more detail in the national lists of goods. There may
therefore be national differences for the last three digits.

Figure 29: Lists of Goods for Export Control
If you want to use legal control because you export dual-use items from EU Member States,
you must first define both a numbering scheme and a numbering scheme content to map the
list of dual-use items in Annex I of the Dual-Use Regulation in SAP GTS. The numbering
scheme content forms the framework for the upload or manual maintenance of dual-use
items. The numbering scheme to which it is assigned is the basis for the classification, that is,
the assignment of dual-use items to products.
You create numbering schemes and numbering scheme contents for legal control in
Customizing (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Numbering Schemes → Control Classes → Define Numbering Scheme for Control
Classes and → Define Numbering Scheme Content for Control Classes).
The delivery Customizing for the SAP GTS system contains templates in the form of the
numbering scheme DEALN and the numbering scheme content DEALN. The numbering
scheme DEALN (Export List) was originally intended for mapping the export list in the annex
to the German Foreign Trade and Payments Ordinance. However, when dual-use items are
exported from the EU, the list of dual-use items in Annex I to the Dual-Use Regulation must be
checked. When implementing legal control, it therefore makes sense to replace the
numbering scheme DEALN with a customer-specific numbering scheme for mapping the list
of dual-use items.
Since the numbering scheme content DEALN_CT already contains the three-part structure of
the list of dual-use items, you can use it as a copy template when defining a new numbering
scheme content and modify settings as required. Delivery Customizing for SAP GTS also
provides a numbering scheme content for the CCL (USECC_CT) for the maintenance of
Export Control Classification Numbers (ECCN).

Lesson: Maintaining Goods Lists and Classifying Products
Figure 30: Numbering Scheme and Numbering Scheme Content
Goods list numbers are master data that are each assigned to a numbering scheme content.
You can purchase complete goods lists in the form of XML files from various data providers
and upload them to your SAP GTS system. However, you can also create goods list numbers
manually. To upload entire goods lists, use the Upload Control Classes app. You can use the
Manage Control Classes app to create individual dual-use items or ECCNs manually instead.
If you upload a complete list to the SAP GTS system from an XML file, it is no longer possible
to change the numbers manually, or the actual numbering scheme content. If you create
goods list numbers manually, you can change them to a limited extent. You can only delete a
number if it is not assigned to any master data or documents.
Product Classification
Before you can assign goods list numbers to the product master records of your dual-use
items, you have to link the numbering scheme of the goods list with the legal regulation for
legal control. To do so, in Customizing for the SAP GTS system, choose the menu path SAP
Global Trade Services, edition for SAP HANA → General Settings → Numbering
Schemes → Assign Numbering Schemes to Legal Regulations. In the dialog structure, first
open the folder Assign Scheme for ECCNs and add entries for all relevant legal regulations and
numbering schemes. Repeat this step in the folder Assign Scheme for Numbers in Legal
Control.
You can then assign goods list numbers to your products. If you want to process individual
products specifically, you can use the Manage Products app. As an alternative, you can use
the Classify Products - Legal Control app. This app is useful if you want to assign the same
goods list number to several products, or if you want to flag several products as not relevant
for control.
You manage the classification of your products at the level of the legal regulation for legal
control. For each of these legal regulations, you must decide whether each product is to be
relevant for export control or whether the system is to assume the opposite (menu path: SAP
Global Trade Services, edition for SAP HANA → Compliance Management → Legal

Controls → Control Settings for Legal Control). The figure below shows the settings for the
legal regulation ZDUDE.
Figure 31: Control of Product Classification
Two indicators are available for the field Maintain Product Master:
● A Each Product is Relevant for Checks
● B Only Specifically Selected Products Are Relevant for Checks
If the indicator A is selected, each product master record must be maintained. If it is a control-
relevant product, knowledgeable users enter the relevant goods list number on the Legal
Control tab. Otherwise, the No Control indicator must be set. If a product is not processed at
all after it has been created in SAP GTS, the system responds according to the worst-case
principle, with a precautionary block of all document items that contain this product.
The use of control groupings and peculiarity codes to classify products for legal control is
optional. You can freely define keys and descriptions in the Manage Control Groups for
Products and the Manage Peculiarity Codes app respectively. Control groupings are primarily
used to group products for the purpose of license determination. You can also use peculiarity
codes in license determination. However, the codes may also be required for notifications
about the use of certain types of licenses (see also SAP Note 1811765).
In the control settings of most legal regulations that the delivery Customizing contains as a
template for legal control, indicator A is selected in the Maintain Product Master field. An
exception is the legal regulation ITAR, which is delivered for mapping the International Traffic
in Arms Regulations (ITAR). Products that are listed on the U.S. Munitions List must therefore
be explicitly flagged as control-relevant on the Legal Control tab by setting the Individual
Maintenance indicator. Therefore, the classification with a code is not sufficient. All products
that are not on the U.S. Munitions List can remain unprocessed for the legal regulation ITAR.
LESSON SUMMARY

Unit 5
Lesson 2
Defining License Types
LESSON OVERVIEW
The focal point of legal control is the product-related check to see whether a license
requirement exists, and the management of licenses. This lesson explains the definition and
configuration of license types using exporting dual-use items as an example.
Business Example
The IDES group intends to export new ball bearings to various countries. However, ball
bearings of this type are categorized as dual-use items in the Dual-Use Regulation. As a result,
exports of these ball bearings from the EU require a license.
LESSON OBJECTIVES
License Types
Licenses are master data in SAP GTS that you can create, change, and display in the Manage
Licenses app. Each license is assigned to a legal regulation and a license type. Users must
therefore specify which of the forms of license provided by the legislature is appropriate when
they create a license data record. The license type controls, among other things, which
entries are possible in the data record of a license and which of these specifications influence
license determination in the document. You define license types in Customizing for
Compliance Management (menu path: SAP Global Trade Services, edition for SAP
HANA → Compliance Management → Legal Controls → Approvals → Define Import- and
Export License Types). The figure 32 shows license types provided for in the Dual-Use
Regulation.
Figure 32: License Types in the EU

The individual export license is the standard export license type in the EU. It applies to only
one goods supply to one end user. The national authority in charge of export control may also
issue global export licenses to reliable exporters. This license type allows exporters to export
dual-use items to multiple end users. General export licenses are not issued for individual
applicants, but are valid for specific dual-use items and destination countries once they have
been published. There are eight Union general export licenses (EU001 to EU008). National
legislation in the Member States may grant additional general export licenses in accordance
with the Dual-Use Regulation.
Figure 33 gives a similar overview for the EAR.
Figure 33: License Types in the US
Exports that do not require a license are flagged accordingly in the export declaration (No
License Required, abbreviated to NLR). If an export does require a license, the exporter has to
check whether a license exception applies. The exceptions are specified in detail in the EAR
and linked to the listed goods in the CCL. An export license is not required, for example, if a
shipment does not exceed a specific value (Shipments of Limited Value, abbreviated to LVS).
Exceptions can also apply for export shipments to civil end-users (CIV), for example. If
required, the Bureau of Industry and Security (BIS) can issue a license on application.
For the mapping of the Dual-Use Regulation in combination with German foreign trade law,
the legal regulation AWV in delivery Customizing comprises four sample license types:
● General license (AG)
● Individual export license (EAG)
● Individual export license – partner-function-specific (EAGP)
● Collective export license (SAG)
These license types are intended to be used as templates. If, for example, you use different
Union general export licenses as well as national general licenses in a Member State, you
usually need several license types for general licenses with different configurations in SAP
GTS, due to the different conditions and requirements for use.
The configuration of a license type in the Customizing for SAP GTS is subdivided into several
areas. The most important settings are grouped together under the following headers:

Lesson: Defining License Types
● Determination - Objects to be Checked

● Update (value and/or quantity)
● Objects That Can be Maintained in License
● Military/Civilian Use and Classification
An essential component of the control of a license type is the Objects To Be Checked area.
This is where you define the criteria for license determination. SAP GTS could, for example,
check the responsible foreign trade organization, the goods list number (“Control Class”) of
the product, and the destination country to find and to assign licenses to export-control-
relevant document items. The system only assigns the two data records to each other if this
information matches in the document and in the license.
A prerequisite for license determination is that the objects to be checked are contained in the
license master record. Therefore, in the license type, you must specify for each of the objects
to be checked whether, or to what extent, users can enter data in a license. In the Objects That
Can Be Maintained in License area, you assign one of the three indicators available for
selection to each of the listed objects.
Options for controlling license maintenance:
● A Precisely One Possible Attribute
● B Unlimited Number of Possible Attributes
● No Possible Attributes
Objects to which option B is assigned appear in the license master record in the Attributes
with Multiple Specifications area.
The document number check during license assignment ensures that SAP GTS only uses an
individual export license for exactly one export or shipment. Therefore, in the Objects That
Can Be Maintained in License area, indicator A (Precisely One Possible Attribute) is assigned
to the field Document Number. This means that users can only enter one document number in
a license.
If during the check of the sales order replica, SAP GTS determines that an individual export
license is required to process the export or shipment, it also searches for an individual export
license again during the check of the outbound delivery replica, unless the product or
destination country have changed. Since the document number check is activated in the
license type, the system assigns a license only if the document number of the feeder system
document and the document number entered in the license match.
However, SAP GTS can also use the license assigned to the sales order for the outbound
delivery replica if the indicator Check First Doc. in Document Flow is set in the Objects to be
Checked areas for the license type. With this setting, SAP GTS uses the document flow to
determine the number of the sales order to which the outbound delivery refers, and compares
the document number of the order with the document number of the license again when
assigning the license.
The Union general export licenses, as well as national general licenses, explicitly preclude use
for certain purposes. For example, the use of the goods for nuclear or military purposes can
be precluded. If you anticipate that the goods to be delivered may be used in a way that is not
covered by the licenses, you can activate additional checks in the settings for the license
types. You can find these options in the Military/Civilian Use and Classification area.
In the Usage Check Level field, you define whether the purpose is checked at all, or whether it
is checked at the level of the license type or the specific license. If a check is activated, you

must enter a partner grouping for determining the check-relevant business partner on
document level in the Partner Usage in Partner Group field.
In the Military/Civilian Use field, you decide on the permitted use. The system links licenses of
the license type civilian use of control-relevant goods only, to those with documents whose
check-relevant business partners are flagged as civilian users on the SAP GTS tab (Usage and
Military/Civil Use area). This means that you have to classify your business partners with
regard to the use of your products. For the use of legal control based on the EAR, an
additional check of the classification of an export with regard to the end use of the goods is
available.
Individual and collective export licenses usually contain a maximum value that the individual
export or the total of the exports must not exceed. A value update must therefore be
activated in the license types for mapping such licenses. The basis for the value update is the
goods value transferred from the feeder system document to the export document.
In the Update area, you also control whether the maximum value entered in the license
master record can still be changed after a document assignment (Value Change field) and
whether exceeding or falling short of the maximum value is allowed.
Note:
You can activate a quantity update additionally or alternatively as required, and
control it according to the same pattern.
If you activate the value or quantity update in a license type, you must also control this update
at item category level (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Document Structures → Activate Item Categories for Application
Areas). If necessary, assign the relevant item categories the depreciation group applicable for
the application level contained in the delivery Customizing SD0A01 (Sales Level: Sales
Documents) or SD0B01 (Sales Level: Outbound Deliveries). Then use the fields Value
Depreciation or Qty Depreciation to determine whether depreciation takes place at all and
whether it is in the form of an issue posting or a receipt posting.
For license determination and management, you must define the possible statuses of a
license. The bandwidth of these statuses is defined in the form of categories in the program
code. When you configure a legal regulation for legal control, you decide which of the statuses
available for selection are actually used (menu path: SAP Global Trade Services, edition for
SAP HANA → Compliance Management → Legal Controls → Control Settings for Legal
Control).
In the Allowed Status folder, enter the status values together with a description of your choice,
such as “applied for” or “granted”. In the detailed settings of each status, you assign the
relevant category (for example, License Applied For). Based on this categorization, during the
document check, SAP GTS recognizes whether it can link a license to a document item.
You assign the statuses defined at legal regulation level to the license types of this legal
regulation (menu path: SAP Global Trade Services, edition for SAP HANA → Compliance
Management → Legal Controls → Approvals → Define Import- and Export License Types,
folder Allowed Status). In the detailed settings for the status, you determine whether the fields
Value, Quantity, Validity, and Ext. Number in a license are ready for input, and whether it is
mandatory to enter a field value.

Lesson: Defining License Types
LESSON SUMMARY


Unit 5
Lesson 3
Setting up License Determination
LESSON OVERVIEW
In legal control in SAP GTS, you have to enter all the licenses that you require for exporting or
transporting your products as data records in the system. The system checks for each
document item, whether the import or export of the product requires a license and, as the
case may be, tries to find a suitable license to assign it to the item or items concerned. This
lesson explains how to set up the determination of licenses in goods issue processes.
Business Example
The IDES group has ascertained that the ball bearings it intends to export to various countries
are considered dual-use items in accordance with the list of dual-use items and the CCL. The
relevant codes for dual-use items and ECCNs have already been assigned to the products in
question. The company now wants to set up the determination of licenses in its export
processes.
LESSON OBJECTIVES
License Determination
Licenses are of master data character in SAP GTS. You usually create general licenses once
and extend the validity as necessary. If you require an individual export license, the data
record in SAP GTS documents the transaction from the creation of the application to the
issue of the license or rejection of the application. In the SAP Fiori lauchpad, you can find the
Manage Licenses app for creating, changing, and displaying licenses.
If a document contains an item with a product that is flagged as dual-use item in its product
master record, SAP GTS attempts to find a suitable export license. If this attempt is
successful, the system links the document item to the license. If the determination fails, SAP
GTS blocks the document item instead. This block can only be removed by assigning a
license.

Figure 34: License Determination in the Sales Process
License determination in legal control is based on an SAP GTS-specific condition technique.

The system first determines a license type and then determines a license of this license type.
Therefore, when you export dual-use items to Switzerland to a civil end-user, for example,
SAP GTS should find a license type for general export licenses and then a license master
record for the Union general export license no. EU001.
The basis of license determination is a determination procedure that you can copy from the
delivery Customizing or define yourself (menu path: SAP Global Trade Services, edition for
SAP HANA → Compliance Management → Legal Controls → Define Determination Procedure
to Automatically Determine License Types). Each determination procedure contains at least
one determination strategy. Determination strategies bundle criteria on which license
determination is based. They are anchored in the program code. If you define your own
determination procedure, you customize the compilation of delivered determination
strategies.
The determination procedure CTRY1 (License Type Determination: Country Level - Maximum),
for example, consists of four determination strategies that have been brought into an access
sequence using the sequence numbers 10 to 40. SAP GTS should therefore first determine
the appropriate license type based on the destination country of the goods issue in
combination with the goods list number of the product (determination strategy CD02 At
Country/Control Class Level).
If the determination fails, the system should make a second attempt based on the destination
country in combination with the grouping of the goods list number assigned to the product
(determination strategy CD01 At Country/Control Grouping Level). The next access uses only
the destination country (determination strategy CD05 At Country Level). A final attempt is
made at legal regulation level (determination strategy CD09). The system therefore performs
up to four determination attempts with different search criteria. If none of the attempts are
successful, it blocks the document item.

Lesson: Setting up License Determination
Figure 35: Example of a Determination Procedure
You assign one of the determination procedures for license type determination copied from
delivery Customizing, or defined by you, to each legal regulation for legal control (menu path:
SAP Global Trade Services, edition for SAP HANA → Compliance Management → Legal
Controls → Control Settings for Legal Control, field License Type Det. Procedure).
The detailed settings for legal regulation for legal control contain some indicators for
influencing license type determination. If you do not want SAP GTS to stop searching for a
license type that matches the document item after the first successful determination
attempt, choose either option A (Check in All Determination Strategies) or X (Check in One
Determination Strategy) in the Check Multiple License Types field. SAP GTS may then find
more than one license for a document item.
This setting is useful if the legal regulation maps legal norms for which the adherence to these
is monitored by different authorities. Licenses from different authorities may then be required
for the export of a product. These authorities must be created in SAP GTS as business
partners with the role “Government Agency” (SLLAUT), and then be entered in the Issuing
Authority field in the relevant license type (Default Document for Customs Management area).
If you export dual-use items from the EU, you must first always check whether one of the
Union general export licenses can be applied. If none of these licenses come into question,
you will have to check the applicability of the national general licenses in the next step. You
can only apply for an individual export license if the planned export is not covered by a general
license.
If SAP GTS determines more than one license type for a document item, it uses the first
license type in alphabetical order for license determination. To be able to specify a different
check sequence, you must set the indicator Cascade Within Approval Type Determination
Activated in the settings for the legal regulation.
If you use country groups in legal control and the destination country of the export is assigned
to several country groups, SAP GTS uses the first country group in alphabetical order for
license type determination. If you want the system to use all the country groups assigned to
the legal regulation, set the indicator Check Multiple Country Groups When Determining
License Types.

In the Partner Group to Determine Country of Destination field, enter the partner grouping for
determining the destination country of the export for the purposes of license determination.
The partner functions EN (Ult. Consignee), WE (Ship-to Party), and AG (Sold-To Party) with
the sequence numbers 10 to 30 are assigned to the partner grouping PGLDT2 provided in the
delivery Customizing (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Partner Structures → Define Groups of Partner Functions).
Therefore, the system first uses the ultimate consignee to determine the destination country
in the export document. If no partner exists in this partner function, the system makes a
second attempt with the ship-to party. If this does not exist either, SAP GTS attempts to
determine the destination country from the address of the sold-to party.
If you do not want only one partner to be taken into account when determining the destination
country, set the indicator Check All Partner Functions in Partner Group and Document. The
system then determines a license for all partner functions of the assigned partner grouping
and, if necessary, also considers partners in partner functions that are not contained in the
partner grouping but are contained in the document.
You have to fill the determination procedure that you have assigned to a legal regulation with
content in the application of your SAP GTS system. To do this, you have to create
determination strategies using the Manage Determination Strategies app. The term
“determination strategy” has two meanings in SAP GTS.
On the one hand, it describes the combination of search criteria for license type
determination in Customizing. On the other hand, the term represents the specific
configurations of these search criteria in the form of master data. The system prepares the
criteria for license type determination according to the determination strategies of the
determination procedure for the legal regulation specified on the selection screen of the
transaction. You can now individually compile the criteria for determining a specific license
type into determination strategies by selecting the relevant entry. You can check the result in
the Display Determination Strategies app.
If a license type is determined successfully and the determination strategy is not flagged as
control-free, SAP GTS searches for a license of this license type that matches the document
item. Figure 36 provides an overview of the system procedure.
Figure 36: License Determination Process

Lesson: Setting up License Determination
System Procedure for License Determination (Export):

● The relevant legal regulation is determined on the basis of the departure country of the
export. The departure country is the country of the legal unit that corresponds to the
delivering plant of the sales order item (address data of the business partner).
● If the product is relevant for control, the system takes the determination procedure for the
license type from the control settings of the legal regulation.
● Based on the determination strategies assigned to the determination procedure, the
system determines a condition record for license type determination. If different license
types are possible, they are checked in alphabetical order. However, it is also possible to
number the determination strategies for a different access sequence.
● If the license type is determined, the system searches for a license that matches the
relevant data of the document item or items and assigns it to the document item or items.
If there is no license (yet), SAP GTS blocks the item.
Document Check and Determination Analysis

In goods issue processes, you can transfer both sales documents and outbound deliveries to
SAP GTS, where you can check them with regard to foreign trade restrictions. If legal control
is active, SAP GTS uses the product master data to check whether the export requires a
license, and searches for a license where applicable.
In the process example in figure 37, a Swiss customer orders ball bearings from a German
company, which due to their technical specification are listed under the dual-use item code
2A001 in Annex I of the EU Dual-Use Regulation. The Union general export license no. EU001
is to be applied to this export. The SAP ECC or SAP S/4HANA feeder system transfers the
order from the Swiss customer to SAP GTS for checking in Compliance Management. Since
the product to be exported is a dual-use item, SAP GTS searches for a suitable license for the
transaction. You can trace the procedure for each document item in a log. Figure 37 shows an
excerpt from the check log of the export document for the order of a Swiss customer.
Figure 37: Excerpt from a Check Log

First, SAP GTS determines the legal regulation or regulations for legal control. In the example
shown, the system used the country indicator in the business partner address of the
supplying legal unit to find the legal regulation ZDUDE. The system used the address of the
ship-to party to identify Switzerland as the destination country for the export (log text
Country/region “CH” determined as relevant country).
Since the product’s classification with code 2A001A identifies it as a dual-use item, SAP GTS
searches for a license type that matches the data of the document item on the basis of the
Dual-Use Regulation in connection with the German foreign trade law (legal regulation
ZDUDE). The determination procedure ZGTS2 assigned to the legal regulation ZDUDE
specifies the search criteria.
The first access using the determination strategy of the procedure (CD02 At Country/Control
Class Level) was successful. License type ZAGEU for Union general export licenses matches
the combination of the destination country Switzerland and dual-use item code 2A001A. The
last step is to determine a license of license type ZAGEU. In addition to the license status, the
determination criteria are the foreign trade organization, the goods list number, and the
destination country (log text Selection criteria for import/export license).
The relevant check date is the confirmed delivery date of the sales order item or the date of
the first schedule line. Depending on the configuration of the license type, the system also
performs value and/or quantity depreciation. If the maximum value and/or maximum
quantity is not sufficient in the license found, it is not possible to make an assignment.
In the example shown, SAP GTS finds the data record for the Union general export license no.
EU001 and links it to the export document item. You can see this assignment in the export
document on the Control Data tab on item level.
LESSON SUMMARY

Unit 5
Lesson 4
Setting up Re-export Control
LESSON OVERVIEW
The first three lessons in the “Legal Control” unit deal with the functions of the application
area in connection with direct export. This lesson focuses on controlling the reexport of goods
that had previously been imported into the EU from the United States.
Business Example
The European subsidiaries of the IDES group regularly import goods from the United States.
Some of these goods are used in the manufacturing of products these subsidiaries supply to
customers inside and outside Europe. As the US business is of particular importance to the
IDES group, the managing board decided to establish a process to ensure global compliance
with the EAR.
LESSON OBJECTIVES
Configuration of Re-export Control

U.S. legislation claims the universality of the EAR for goods of U.S. origin. The actual location
of the goods is irrelevant. They may even have been incorporated into other goods outside the
United States. The EAR also claim validity for goods manufactured outside the United States
using export-control-relevant technologies or software originating in the United States.
According to the EAR, a license might be required for the re-exports of control-relevant
goods.
In legal control, additional functions are available for re-export control. These are country-
independent, but are primarily aimed at the EAR rules. If you use re-export control, SAP GTS
always performs up to three checks as part of legal control:
1. Is a license required based on the foreign trade law of the departure country of the export
and does a suitable license already exist?
2. Is there a re-export that requires a license from the perspective of the EAR?
3. If this is the case, has a corresponding license already been entered in the system?
For re-export control, you set up legal control on the basis of both national foreign trade law
and the EAR. You also have to make some settings for checking cross-border goods issues for
re-export control relevance. For these settings, you can use the delivery Customizing as it is,
or as a template for your own configuration. In each case, application-specific master data
maintenance is added.
As a signatory state of the Wassenaar Arrangement, the United States have based the
national list of export-control-relevant goods, the CCL, on the nomenclature of this treaty.

Like the list of goods in Annex I to the Dual-Use Regulation, you map the CCL as a numbering
scheme and numbering scheme content in SAP GTS (see the “Maintaining Goods Lists and
Classifying Products” lesson). The ball bearing, which is used as a product example in this
course, is classified as a dual-use item in the training system, both on the basis of the Dual-
Use Regulation and on the basis of the EAR.
Each of the ten categories of the CCL additionally includes the code EAR99 at the end of each
section of the list. This code indicates items that are not explicitly listed in the CCL, but are
still subject to the EAR (“items subject to the EAR that are not specified elsewhere in this CCL
category or in any other category in the CCL”). The EAR cover all items that fall under the
responsibility of the BIS.
Due to this broad definition, code EAR99 in the EAR is also referred to as a “basket”. The code
collects all items that are not relevant for export control based on their properties. Export
control may be relevant for these items as a result of the destination country of the export,
the end user, or the intended end use.
SAP GTS checks the product master record to decide whether an export or dispatch inside
the EU is a re-export that requires a license. When you activate a legal regulation for re-export
control, the system processes an additional Re-Export tab in the product master data. On this
tab, you can make entries with information about the re-export control relevance of the
product, if required.
Delivery Customizing for SAP GTS contains two country groups for re-export control:
● USREX_CRIT (Critical Countries for U.S. Re-Export)
● USREX_UNCR (Non-Critical Countries for U.S. Re-Export)
These country groups are used to map the de minimis rules of § 734.4 EAR. These rules are
relevant when export control-relevant items, including software and technology originating in
the United States, are incorporated into other items or, in the case of software, form a
combination (“bundle”) with other items, such as the driver software of a printer, outside of
the United States.
If the value share of the control-relevant items with U.S. origin in the product to be exported
does not exceed a certain percentage, re-export is “not subject to the EAR”. There is
therefore no need to check the license requirement on the basis of the EAR. The EAR contain
two de minimis rules, but individual ECCNs are explicitly excluded from their application:
● Value share of control-relevant goods originating in the United States ≤ 10%
● Value share of control-relevant goods originating in the United States ≤ 25 %
The second rule applies to re-exports to countries that are not members of the country
groups E:1 (“Terrorist Supporting Countries”) and E:2 (“Unilateral Embargo”) of Annex 1 to
Section 740 EAR. In SAP GTS, these countries must be assigned to the country group
USREX_CRIT. The country group USREX_UNCR contains all other countries that were defined
in the system when the respective SAP GTS version was delivered — with the exception of the
United States.

Lesson: Setting up Re-export Control
Figure 38: Application of De Minimis Rules
The percentages of the two de minimis rules are already assigned to the country groups
USREX_CRIT and USREX_UNCR in delivery Customizing (menu path: SAP Global Trade
Services, edition for SAP HANA → Compliance Management → Legal Controls → Re-
Export → Configure Country Group of Legal Regulation for Re-Export).
The price type PROD_PRICE (Material Price) is also already contained in delivery Customizing
(menu path: SAP Global Trade Services, edition for SAP HANA → General Settings → Define
Price Types). It is only relevant if you want to transfer the valuation of the components for re-
export calculation from the feeder system to the Prices and Values tab of the product master
in SAP GTS.
The re-export calculation, which is covered in the second section of this lesson, is based on
the BOM of the product to be exported. You transfer the BOMs of the products that are
relevant for re-export control from the feeder system to SAP GTS. Program /SAPSLL/
BOMMAT_DISTRIBUTE_R3 is intended for the initial transfer. You can also use the Initial
Transfer of Bills of Material to SAP GTS transaction to transfer bills of material online
(transaction code /SAPSLL/BOMMAT_DIRR3) or — in an SAP S/4HANA feeder system — the
Schedule Transfer of Bill of Material - Global Trade Services app. In SAP GTS, you can check
the result of the replication using the Display BOMs for Re-Export app.
Note:
If you already transfer your BOMs to SAP GTS for preference determination, the
system automatically uses the replicas for re-export calculation.
You can enter the values for calculating the proportion of a BOM component in the finished
product either manually in the product, or copy them from the material in the feeder system
from the Accounting 1 tab to the product in SAP GTS. When you enter values manually on the
Re-Export tab, you can differentiate between hardware, software, and technology. For the
initial transfer of material prices from the feeder system, you use the program /SAPSLL/

PRCMAT_DISTRIBUTE_R3, which you can also execute online using the Initial Transfer of
Material Prices to SAP GTS transaction (transaction code /SAPSLL/PRCMAT_DIRR3) or — in
an SAP S/4HANA feeder system — the Schedule Transfer of Product Prices - Global Trade
Services app.
Depending on the price control, the feeder system transfers either the moving average price
or the standard price of the material to SAP GTS.
In the settings for the country groups for re-export control, four indicators are available for
selection in the field Calculation Reaction:
● A Set Check Relevance for All Higher-Level Assemblies
● B Ignore Component for Value Share
● C Use Price from Plant Segment as Share, Check if Missing
● D Use Price from Plant Segment as Share, Ignore if Missing
The first two options are to be used if product prices are maintained in SAP GTS on the Re-
Export tab. Options C and D, on the other hand, are useful if the material prices are
transferred from the feeder system. If you choose options A or B, SAP GTS ignores any
entries on the Prices and Values tab. For options C and D, price specifications in the column
Predefined Hardware Share on the Re-Export tab take priority over the prices transferred from
the feeder system. If this column is empty, SAP GTS adopts the information from the Prices
and Values tab.
Options A and C are based on the worst-case principle. If there is no price in the product
master record of a component, this component is included in the re-export calculation with
the maximum value for the price field. The finished product is therefore always relevant for re-
export control. Therefore, if there are gaps in the product master maintenance with regard to
the prices, they are immediately detected during re-export calculation. Options B and D follow
the opposite principle. If the price of a component is missing, this component is not
considered relevant for re-export calculation (value 0). If products were overlooked during
master data maintenance or material price transfer, an incorrect picture may arise. However,
in delivery Customizing, the “basket” code EAR99 is assigned to the country group
USREX_UNCR as an “exclusion number”. Therefore, the system ignores components
classified with this code on their Legal Control tab in re-export calculation.
Re-export Calculation and Document Check

You can execute the re-export calculation for an individual product or for a large number of
products using the Calculate Products for Re-Export app or schedule the program /SAPSLL/
REX_VALUE_CALC_RNG for background processing. SAP GTS logs every re-export
calculation. However, a simulation mode is also available. You can display logs using the
Display Re-Export Calculation Logs app.
SAP GTS always performs the calculation for both country groups of the legal regulation
USREX. The yellow triangle in the Calculation Status column indicates that the re-export
control relevance of the product depends on its sales price. The total value of the control-
relevant components with U.S. origin is displayed in the Calculated Hardware Share column).
The basis for calculating the percentage share of these components is the material price
transferred from the feeder system or, as the case may be, the price entered manually on the
Re-Export tab.
Products whose value are not to be included in the re-export calculation must be explicitly
excluded by means of indicators on the Re-Export tab. Some components might also be sold
as spare parts. In the case of a direct export or dispatch within the EU, SAP GTS should
perform a check for re-export control relevance, but not if the products are used as

Lesson: Setting up Re-export Control
components in other products. Therefore, the Ignore as Component indicator is available on

the Re-Export tab.
If you want products for which a BOM exists in SAP GTS to be excluded from re-export
calculation as main parts, set the No Calculation indicator. If you never want to include
products in the re-export calculation, regardless of their function in the BOM, choose the
entry Do Not Check/Control in the Re-Export Control Relevance column. This indication is
particularly useful for components that you or your suppliers never purchase from the United
States. Components without entries on the Re-Export tab are included in the calculation with
their price.
Note:
The country of origin of a product is not relevant for re-export control in SAP GTS.
According to the worst-case principle, you should include all components that you
or your vendors procure in the United States, at least occasionally, and that have
an ECCN in the re-export calculation. The same applies for trading goods.
The results of the re-export calculation are included in the document check, in the context of
legal control.
Figure 39: Reexport Checks
Unlike the legal regulations ZDUDE and EAR, the legal regulation USREX does not map an
independent legal norm, rather it groups all provisions of the EAR that affect re-export
control. The Reexport indicator in the control settings for this legal regulation tells SAP GTS
that USREX is a legal regulation for checking the re-export control relevance of a transaction,
and not for license determination (menu path: SAP Global Trade Services, edition for SAP
HANA → Compliance Management → Legal Controls → Control Settings for Legal Control). If
the re-export indicator is set, the Reference Legal Regulation field must contain the legal
regulation for license determination in the case of a transaction being relevant for re-export.

The legal regulation EAR is already assigned to the legal regulation USREX in delivery
Customizing.
In addition to the license requirement in accordance with the regulations of the relevant
national foreign trade law of the departure country of the export or dispatch, SAP GTS also
checks the re-export control relevance of the transaction based on the legal regulation
USREX. If the planned export or shipment is subject to the EAR, the system checks whether
an export license is required. If necessary, the search for a suitable license record follows.
LESSON SUMMARY

Unit 5
Learning Assessment
1. At which level do you have to make the decision whether all of your products are
potentially sensitive goods (“relevant for control”) or not?
X A License type
X B Foreign trade organization
X C Legal unit
X D Legal regulation
2. Which license types are provided for in the EU Dual-Use Regulation?

X A General export licenses
X B Collective export licenses
X C Global export licenses
X D Individual export licenses
3. Which criteria are available for license type determination in the determination strategies
provided in SAP GTS?
X A Country
X B Country group
X D Product
X E Goods list number (“control class”)

4. The No Control indicator on the Legal Control tab should be set in the master data of
products that do not have an ECCN.
X True
X False

Unit 5
1. At which level do you have to make the decision whether all of your products are
potentially sensitive goods (“relevant for control”) or not?
X A License type
X B Foreign trade organization
X C Legal unit
X D Legal regulation
Correct. You have to make the decision whether all of your products are potentially
sensitive goods ("relevant for control") at legal regulation level.
2. Which license types are provided for in the EU Dual-Use Regulation?

X A General export licenses
X B Collective export licenses
X C Global export licenses
X D Individual export licenses
Correct. The Dual-Use Regulation provides for general export licenses, global export
licenses and individual export licenses.

3. Which criteria are available for license type determination in the determination strategies
provided in SAP GTS?
X A Country
X B Country group
X D Product
X E Goods list number (“control class”)
Correct. SAP GTS can use, amongst others, country, country group, legal regulation, and
goods list numbers for license type determination.
4. The No Control indicator on the Legal Control tab should be set in the master data of
products that do not have an ECCN.
X True
X False
Correct. If the product is subject to the EAR, the code EAR99 must be entered in the
Export Control Classification Number field. Only if the product is subject to another legal
regulation, the No Control indicator is the right choice.

UNIT 6 Legal Regulations and
Nomenclatures in Customs
Management
Lesson 1
Activating Legal Regulations for Customs Management 97
Lesson 2
Maintaining Commodity Codes and Customs Tariffs 103
UNIT OBJECTIVES
● Explain the function of legal regulations in Customs Management

● Activate legal regulations for the application areas of Customs Management
● Maintain numbering schemes for commodity codes and customs tariff numbers
● Classify products for customs processing

Unit 6: Legal Regulations and Nomenclatures in Customs Management

Unit 6
Lesson 1
Activating Legal Regulations for Customs
Management
LESSON OVERVIEW
You map customs-related legislation in SAP GTS in the form of legal regulations. Unlike in
Compliance Management and Preference Management, it makes sense to copy the legal
regulations contained in the delivery Customizing for Customs Management unchanged to
your development system. As a rule, the settings for these legal regulations are coordinated
with the national customs authorities in certification procedures. Changes, if any, should
therefore be made with caution.
Business Example
The IDES group checks which customs-related laws and regulations are relevant to its
international trade processes.
LESSON OBJECTIVES
Function of Legal Regulations in Customs Management

From a technical perspective, legal regulations are alphanumeric keys that are defined in
Customizing of the SAP GTS system and are linked to a large number of control parameters.
Most of these control parameters depend on the application area in which the legal regulation
is to be used. For example, you define the scope and strictness of address screening at the
level of a legal regulation for sanctioned party list screening.
You can get an overview of the legal regulations delivered for both application areas of
Customs Management in the general settings in Customizing for SAP GTS (menu path SAP
Global Trade Services, edition for SAP HANA → General Settings → Legal
Regulations → Define Legal Regulation).
The delivery Customizing contains legal regulations whose configuration corresponds to the
legal situation at the time of delivery. Legal changes that take effect after this time may result
in changes to the system configuration. If a legal change has resulted in adjustments to the
program code, you can update your system by implementing Support Packages. Delivery
Customizing is also constantly adjusted in this way.
In any case, you must ensure that competent employees keep track of relevant legal changes
and, if necessary, initiate configuration changes or make configuration changes themselves.
In Customs Management, experience shows that the control of communication with the
national customs authorities and the coding of accompanying documents are particularly
affected.

Figure 40: Legal regulations as the carrier of Customizing
In SAP ECC and SAP S/4HANA, organizational units such as company codes, plants, sales
organizations, or warehouse numbers, are the main objects of the process-related system
configuration. Many Customizing settings in logistics and accounting depend on
organizational units. There are no organizational units in SAP GTS. From the perspective of
system configuration, the legal regulations take the place of the organizational units. Most of
the Customizing settings in SAP GTS are used to configure legal regulations for the individual
application areas.
Basically, due to technical reasons, Customs Management consists of two application areas:
customs processing and transit/presentation. For the EU and Switzerland, customs
processing includes all customs procedures except the transit procedure. If your company
wants to use SAP GTS for both the transit procedure and other customs procedures, you
have to implement both application areas.
For the United States, the transit/presentation application area supports the transfer of
goods from the point of unlading in the territory of the port of entry, to a foreign-trade zone
inside or outside this territory, as well as goods movements between two foreign-trade zones
(transportation under permit to transfer and transportation in-bond).
Note:
The transit/presentation application area also contains functions for participating
in the Excise Movement and Control System (EMCS) for transporting excise
goods in the tax suspension procedure. Customs processing has been enhanced
to include pre-declarations as part of Importer Security Filing (ISF) in the United
States.

Lesson: Activating Legal Regulations for Customs Management
Figure 41: Examples of Legal Regulations for Customs Management in the EU
For customs processing in Australia, China, some European countries, New Zealand, and the
United States, delivery Customizing provides legal regulations that you should use. In SAP
GTS, these legal regulations represent all customs-related legislation and provisions that
apply in the respective country.
In the case of the EU Member States, for example, the individual legal regulations for customs
processing cover both EU customs law, that is, the Union Customs Code (UCC) and its
implementing provisions, as well as national law, administrative rules, and technical
specifications for electronic communication with the customs authorities. The legal
regulations delivered for opening and/or discharging a transit procedure in some of the
Member States also include the Convention on a Common Transit Procedure with the EFTA
States, Macedonia, Serbia, Turkey, and the United Kingdom.
Activation and Determination of Legal Regulations in Customs Management

A two-step activation always follows the definition of a new legal regulation or, in the case of
Customs Management, the decision to use one of the legal regulations provided in the
delivery Customizing.
1. General activation of the legal regulation

(Where do the legal norms that are mapped using the legal regulation apply?)
2. Specific activation of the legal regulation for an application area

(Which application area works with the legal regulation – to what extent, if applicable?)
You have to activate legal regulations for the two application areas of Customs Management
at country level. Country groups that are available in the application areas of Compliance
Management and in Preference Management are not used in Customs Management.

Figure 42: Activation of Legal Regulations at Application Area Level
You activate a legal regulation generally in the cross-application area settings in Customizing
for SAP GTS (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Legal Regulations → Activate Legal Regulations at Country/Country Group Level).
You can find the views for the specific activation of legal regulations in Customizing for the
two application areas.
Menu paths:
● SAP Global Trade Services, edition for SAP HANA → Customs Management → Activate
Legal Regulation for Transit/Presentation and Excise Duty
● SAP Global Trade Services, edition for SAP HANA → Customs Management → Activate
Legal Regulation for Customs Processing and Pre-Declaration
After replicating a feeder system document, SAP GTS attempts to determine a legal
regulation for the relevant application area. In Customs Management, the company code of
the feeder system document is always decisive for this determination. SAP GTS takes the
country of destination of the import, or the country of departure of the export, from the
address of the business partner in the “Foreign Trade Organization” role that is assigned to
the company code in the mapping of the organizational structures (menu path: SAP Global
Trade Services, edition for SAP HANA → General Settings → Organizational
Structures → Assignment of Organizational Units from Feeder System to Foreign Trade
Org. → Assign Company Code at Feeder System Level or → Assign Company Code at Feeder
System Group Level).
The delivery Customizing contains a determination procedure for each of the nine application
areas of the SAP GTS solution (menu path: SAP Global Trade Services, edition for SAP
HANA → General Settings → Legal Regulations → Define Determination Procedure for Active
Legal Regulations). The determination procedures are already assigned to the application
areas for which they are intended. You can find this assignment in Customizing for Customs
Management by choosing SAP Global Trade Services, edition for SAP HANA → Customs
Management → Assign Determination Procedure for Active Legal Regulations:
● Customs Processing: Determination procedure LECUS

Lesson: Activating Legal Regulations for Customs Management
● Transit Procedure/Excise Duty Monitoring: Determination procedure LETRS
Unlike in Compliance Management and Risk Management, determination of legal regulations

in Customs Management is only possible at the level of the country of departure or country of
destination. The two determination procedures in Customs Management therefore only
contain the determination strategy ALRG01 (Determine Legal Regulation at Country Level).
LESSON SUMMARY


Unit 6
Lesson 2
Maintaining Commodity Codes and Customs
Tariffs
LESSON OVERVIEW
As a rule, before you can import goods, you have to classify them in accordance with the
provisions of the customs tariff of the respective destination country. Based on the customs
tariff number that you specify in the import declaration, the national customs authorities
determine the customs duty and any other duties to be applied to the goods.
In export declarations, however, the specification of a commodity code might be required for
foreign trade statistical purposes only. This lesson deals with mapping of nomenclatures for
commodity codes and customs tariffs in SAP GTS.
Business Example
The IDES group wants to import goods from various countries into the EU and the United
States. However, the corresponding products in SAP GTS must first be classified according to
the relevant customs tariffs.
LESSON OBJECTIVES
Numbering Schemes for Customs Processing

Unlike in Foreign Trade in SAP ECC (subcomponent SD-FT), commodity codes and customs
tariff numbers are master data in SAP GTS that can be created manually using apps in the
SAP Fiori launchpad or uploaded from XML files of different data providers. Commodity codes
and customs tariff numbers are always included in a combination of numbering schemes and
numbering scheme content.
The numbering schemes and numbering scheme contents are defined in Customizing to map
entire nomenclatures of goods or customs tariffs. Numbering scheme contents define the
structure of commodity codes or customs tariff numbers. Each numbering scheme is
assigned to one of the 13 categories (type of numbering scheme) anchored in the program
code. The types of numbering schemes 101 to 108 are intended for the use in the application
areas of Customs Management:
● 101 — Tariff Numbers (ECT, HS)
● 102 — Commodity Codes (Schedule B, CN)
● 103 — Additional Codes (ECT, HTS, CN, Schedule B)
● 104 — Authority Codes (PGA, NZE)

● 105 — Additional Customs Tariff Numbers

● 106 — License Relevance Codes (Conditions, BSPC)
● 107 — FDA Product Codes
● 108 — Excise Duty Codes
Note:
For a complete overview, see the value range of the domain /SAPSLL/CTSTY.
The most important types of numbering schemes are 101 for customs tariffs and 102 for
commodity codes. Additional codes and/or additional tariff numbers might be necessary for
customs processing in individual countries such as, for example, the product classification of
the Food and Drug Administration (FDA) of the United States.
If you want to use SAP GTS in for both import and export processing, you have to define at
least one numbering scheme and one numbering scheme content each:
● Export declaration or transit declaration: Numbering scheme/numbering scheme content
for mapping a nomenclature of commodity codes usually for foreign trade statistics
● Import Declaration: Numbering scheme/numbering scheme content for mapping the
national customs tariff of the importing country
Figure 43: Numbering Scheme and Numbering Scheme Content for the CN
To create or edit a numbering scheme for commodity codes, choose the menu path SAP
Global Trade Services, edition for SAP HANA → General Settings → Numbering
Schemes → Commodity Codes → Define Numbering Scheme for Commodity Codes. To define
numbering schemes for customs tariffs, choose SAP Global Trade Services, edition for SAP
HANA → General Settings → Numbering Schemes → Tariff Numbers → Define Numbering
Scheme of Tariff Numbers instead.

Lesson: Maintaining Commodity Codes and Customs Tariffs
You define the corresponding numbering scheme contents using the menu path SAP Global
Trade Services, edition for SAP HANA → General Settings → Numbering
Schemes → Commodity Codes → Define Numbering Scheme Content for Commodity Codes
and SAP Global Trade Services, edition for SAP HANA → General Settings → Numbering
Schemes → Tariff Numbers → Define Numbering Scheme Content for Tariff Numbers.
The delivery Customizing for SAP GTS contains, among others, numbering schemes and
numbering scheme contents for mapping the CN and some customs tariffs. You can use
these numbering schemes and numbering scheme contents either directly or as templates
for your own numbering schemes and numbering scheme contents.
The structure of the numbering scheme contents delivered corresponds to the actual
structure of the nomenclature of goods or the respective customs tariff. If you decide to
upload the commodity codes, you should check the formatting in one of the XML files of your
data provider.
If your data provider structures the data differently, you should copy the delivered numbering
scheme to the customer namespace and adjust the copy accordingly. The same applies if you
create a new numbering scheme for a customs tariff that is not contained in delivery
Customizing and therefore have to define the structure yourself.
Note:
Some Member States use the Integrated Tariff of the European Union (TARIC,
after the original French name “Tarif Integré Communautaire”) as customs tariff.
Delivery Customizing provides the numbering scheme and the numbering scheme
content TARIC and TARIC_CT for the manual maintenance of TARIC codes.
Figure 44: Structure of a Numbering Scheme Content for the CN
The numbering scheme EUSTA (Commodity Codes - EU) contained in delivery Customizing
represents the CN. This numbering scheme is assigned to the legal regulations for customs
processing and for the transit procedure in different Member States (menu path: SAP Global
Trade Services, edition for SAP HANA → General Settings → Numbering Schemes → Assign

Numbering Schemes to Legal Regulations). The assignment of numbering schemes to legal

regulations in Customs Management is required for classifying products in nomenclatures of
commodity codes and customs tariffs.
For the purposes of Intrastat declarations, the numbering scheme EUSTA can be assigned to
the legal regulation ENSEU (Numbering System - European Union).
Among others, delivery Customizing contains numbering schemes and numbering scheme
contents for mapping the German customs tariff and the Harmonized Tariff Schedule (HTS)
of the United States (DEEZT/DEEZT_CT and USHTS/USHTS_CT, respectively). These
numbering schemes are already assigned to the legal regulation ATLAS and ACE, respectively
(Assign Scheme for Tariff Numbers folder).
If you want to use SAP GTS to process imports into other Member States, you have to define
your own numbering schemes to map the respective national customs tariffs.
Note:
In delivery Customizing, you can also find numbering schemes and numbering
scheme contents for the Swiss Customs Tariff (Tares) and for the Chinese and
New Zealand customs tariffs.
You decide at numbering scheme content level which chapters of the Harmonized System
(HS) are created during an upload from XML files to SAP GTS. This type of preselection is
useful due to the large volume of data for the nomenclatures of commodity codes and
customs tariffs, not least for performance reasons. In Customizing, choose SAP Global Trade
Services, edition for SAP HANA → General Settings → Numbering Schemes → Commodity
Codes → Define Numbering Scheme Content for Commodity Codes or → Tariff
Numbers → Define Numbering Scheme Content for Tariff Numbers and open the Chapter
Restriction folder in the dialog structure to enter the required chapters. During the data
upload, the system only posts the numbers assigned to these chapters to the database.
The delivered numbering scheme contents contain a unit of measure/measurement system
each (System for Units of Measurement field in the control settings of the numbering scheme
content). The unit of measurement systems are used to map SAP-internal codes for units of
measure to their equivalents used by the customs authorities.
In the External UoM column, the unit of measurement systems EU_0001 (Units of Measure for
CN/TARIC), for example, contains a selection of EDIFACT measurement unit codes
recommended by the United Nations Economic Commission for Europe (UNECE). You have
to assign the internal units of measurement that you use in your SAP systems to these codes
accordingly (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Numbering Schemes → Define Unit of Measurement System, folder Unit of
Measurement Codes).
Note:
If required, you must add missing codes. A compilation of all EDIFACT
measurement unit codes is available on the UNECE website in “Recommendation
No. 20”.
You can assign exactly one internal unit of measurement to each EDIFACT unit of
measurement code. If an internal unit of measure corresponds to several external unit of
measurement codes, flag one of these codes as the primary unit of measure (Prim. UoM).

Product Classification and its Retransfer

You can recognize the assignment of numbering schemes to legal regulations directly in the
application when you display or change a product using the Manage Products app,
Classification tab).
The delivery Customizing contains legal regulations for customs processing or the transit
procedure for all Member States in which SAP GTS is certified or approved in some form as
software for participating in electronic procedures. The numbering scheme EUSTA is already
assigned to all these legal regulations. In addition, these legal regulations are activated in
delivery Customizing for the relevant application area of Customs Management.
Therefore, if you copy client 000 to set up your SAP GTS system landscape, you should
deactivate the legal regulations that are currently not required in the copy. When processing
product master data, users then see only the legal regulations that are actually used and the
numbering schemes assigned to them.
Since the world of goods is constantly changing, the nomenclatures for commodity codes and
customs tariffs are also subject to regular changes. For example, customs tariff numbers
must be defined for new products. Other products disappear from the market as a result of
technical innovations, making their customs tariff numbers superfluous. Therefore, once a
year, the European Commission publishes the CN in its current form in the form of a
Regulation. The updated version shall apply from 1 January of the following year. The TARIC is
also subject to constant changes.
Data suppliers provide these updates in XML file form. First, you receive files for the upload of
new and changed commodity codes or customs tariff numbers with which you update the
corresponding numbering schemes in SAP GTS. Some data suppliers provide additional XML
files for the exchange of obsolete numbers with valid numbers in the product master
(“reclassification”). You upload these reclassification files to your SAP GTS system using the
Reclassify Products XML-Based app. However, manual reclassification is also possible
(Reclassify Products Manually app).
The upload of the current version of the CN or customs tariff automatically adjusts the validity
of obsolete numbers in the respective numbering scheme content. After successful
reclassification, the Classification tab of the product master records contains a history of the
number assignments. This means that you can always see which commodity code or which
customs tariff number was valid at a certain point in time.
If an obsolete number corresponds to exactly one new number, SAP GTS can reclassify the
products independently. However, in quite frequent cases where a number is replaced by at
least two other numbers, a competent user must make a decision. You select the number that
applies in the future directly using the Reclassify Products XML-Based app.
In the SAP ECC subcomponent SD-FT, you can assign commodity codes or customs tariff
numbers on the Foreign Trade: Export Data or Foreign Trade: Import Data tab of the material
master. This view is plant-dependent. From the material master, SAP ECC transfers the
commodity codes and customs tariff numbers respectively as default values to the foreign
trade data of purchasing documents, deliveries, and billing documents. The numbers can be
used for output on the commercial invoice or other documents.
Therefore, many companies want to retain commodity codes and customs tariff numbers in
the feeder system even after SAP GTS has been implemented. However, due to the
considerable risk of causing inconsistencies, you should avoid maintaining the commodity
codes or customs tariff numbers and their assignment to materials/products in the feeder
system and SAP GTS in parallel.

As an alternative, SAP GTS provides a program for the regular retransfer of commodity codes
and customs tariff numbers as well as their assignment to products to the SAP ECC or SAP
S/4HANA feeder system. You start the retransfer of new or changed codes and assignments
in SAP GTS using the program /SAPSLL/COMCO_RETRANSFER.
Figure 45: Retransfer of Commodity Codes
The selection of the data relevant for the retransfer is based on the evaluation of change
pointers (see lesson “Setting up the Transfer of Master Data and Documents”).
Before you start to use a regular retransfer of commodity codes to SAP ECC or SAP S/
4HANA feeder systems, you must transfer existing codes and their assignments initially. For
this initial transfer, you use the program /SAPSLL/COMCO_RETRANSFER_INIT.
The program /SAPSLL/COMCO_RETRANSFER fills a worklist in the plug-in of the SAP ECC
feeder system. You can display this worklist in the area menu for the communication with SAP
GTS on the Master Data tab using the Display Worklist for Transfer of Commodity Codes
transaction (transaction code /SAPSLL/SWNAV_DISP). The program /SAPSLL/
SWNAV_RETRANSFER_R3 processes the worklist to update the database of the feeder system.
You can also execute this program online using the transaction of the same name
(transaction code /SAPSLL/SWNAV_RTR_R3).
If you execute the program /SAPSLL/COMCO_RETRANSFER, SAP GTS evaluates the change
pointers for the message types /SAPSLL/CLSMD_SLL (Change of Classification Master Data)
and /SAPSLL/PRCLS_SLL (Classification Changes), and transfers the assignment of the
commodity codes or customs tariff numbers of all classified or reclassified products to the
feeder system via RFC.
In an SAP ECC feeder system, the program /SAPSLL/SWNAV_RETRANSFER_R3 updates the
database tables T604 (Foreign Trade: Commodity Code / Import Code Number), T604T
(Foreign Trade: Commodity Code/Import Code No. Description ), and MARC (Plant Data for
Material). Existing number assignments in table MARC are overwritten by the retransfer.
The program determines the relevant plants using the country of the legal regulation to which
the numbering scheme affected by the retransfer is assigned. The legal regulation ATLAS is

active in Germany, for example. When processing the retransferred assignments of

commodity codes or customs tariff numbers to products, the feeder system automatically
adds data for all German plants if necessary. This decision is based on the country code of the
plant addresses.
In an SAP S/4HANA feeder system, the assignment of commodity codes or customs tariff
numbers to materials transferred from SAP GTS is not visible on the user interface. SAP S/
4HANA stores the commodity codes or customs tariff numbers and the corresponding texts
in the database tables /SAPSLL/CLSNR (Trade Classification Number) and /SAPSLL/
CLSNRT (Description of Trade Classification Number) respectively. The assignment of
numbers to materials can be found in the database table /SAPSLL/MARITC (Material Trade
Classification).
You can display commodity codes in SAP S/4HANA using the Manage Commodity Codes app.
Customs tariff numbers can be displayed using the Manage Customs Tariff Numbers app. The
assignment of commodity codes and customs tariff numbers to materials can be displayed
using the Display Classified Products - International Trade app.
LESSON SUMMARY


Unit 6
Learning Assessment
1. Which of the strategies for the determination of legal regulations in Customs Management
is assigned to the determination procedures LECUS and LETRS?
X A ALRG01
X B ALRG02
X C ALRG03
X D ALRG11
X E ALRG12
X F ALRG13
2. Which numbering scheme is provided for the CN in delivery Customizing?

X A USHTS
X B DESTA
X C TARIC
X D EUSTA

Unit 6
1. Which of the strategies for the determination of legal regulations in Customs Management
is assigned to the determination procedures LECUS and LETRS?
X A ALRG01
X B ALRG02
X C ALRG03
X D ALRG11
X E ALRG12
X F ALRG13
Correct. ALRG01 is the determination strategy assigned to the determination procedures

LECUS and LETRS.
2. Which numbering scheme is provided for the CN in delivery Customizing?

X A USHTS
X B DESTA
X C TARIC
X D EUSTA
Correct. The numbering scheme EUSTA represents the CN in delivery Customizing.

UNIT 7 Additional Settings for
Customs Management
Lesson 1
Setting up the Integration into Feeder System Processes 115
Lesson 2
Managing Customs Code Lists and Data Defaulting 125
Lesson 3
Analyzing the Communication with Customs 131
Lesson 4
Connecting Customs Agents 137
UNIT OBJECTIVES
● Set up document replication for Customs Management

● Set up inventory management for special procedures
● Manage customs code lists in SAP GTS
● Set up the procedure for defaulting data
● Configure output control in Customs Management
● Submit customs declarations from SAP GTS
● Describe the process flow of communication with customs agents
● Set up the mapping required to connect customs agents to your SAP GTS system

Unit 7: Additional Settings for Customs Management

Unit 7
Lesson 1
Setting up the Integration into Feeder System
Processes
LESSON OVERVIEW
This lesson deals with the interaction between the SAP ECC or SAP S/4HANA feeder system
and the SAP GTS system in Customs Management.
Business Example
The IDES group intends to use SAP GTS for import and export in various countries. The
purchasing and sales processes are handled in SAP ECC and SAP S/4HANA.
LESSON OBJECTIVES
Replication of Inbound Deliveries and Material Documents for Imports

For feeder system integration in the import process, you can choose between two integration
scenarios.
Integration Scenarios in the Goods Receipt Process
● Customs declaration before goods receipt based on purchasing documents

● Customs declaration after goods receipt based on material documents
The integration scenario “customs declaration before goods receipt” is primarily suitable for
SAP GTS customers in countries whose customs laws do not provide for a transit procedure.
The import procedure will therefore be started immediately after the transfer to the customs
territory of the respective destination country. In the EU, the scenario is used if the
declaration for releasing goods for free circulation is to be submitted to the border customs
office. A prerequisite for the “customs declaration after goods receipt” scenario is the
completion of a transit procedure before the goods imported are released for free circulation
or placed under another customs procedure.

Figure 46: Customs Declaration Before Goods Receipt
In the “customs declaration before goods receipt” scenario, the customs declaration is
always based on a purchasing document transferred from the SAP ECC or SAP S/4HANA
feeder system. This purchasing document is replicated to SAP GTS as an import document.
The data from the purchasing document fills a worklist for customs declarations before the
goods receipt. You access this worklist to create customs declarations. If you work with
inbound deliveries in your procurement processes in SAP ECC or SAP S/4HANA, you can use
the data of these documents to correct the data resulting from the transfer of purchasing
documents in the worklist.
In the “customs declaration after goods receipt” scenario, the inbound delivery plays a central
role. It is replicated as a customs shipment in SAP GTS. This document is the basis for
communication with the customs authorities in the EU, Great Britain and Switzerland when
completing a transit procedure. The customs shipment is the document basis for the arrival
notification and the unloading comment that you submit as part of the communication in the
New Computerised Transit System (NCTS).

Lesson: Setting up the Integration into Feeder System Processes
Figure 47: Replication of Inbound Deliveries
Based on the previous document type entered in the inbound delivery header, SAP GTS
recognizes the customs status of the goods transported in the transit procedure:
● T1: Non-Union goods (duty unpaid)
● T2: Union goods (duty paid)
● T-: Mixed shipment (both Union and non-Union goods)
SAP GTS copies the Master Reference Number (MRN) of the transit procedure entered in the
document header of the inbound delivery to the customs shipment (Transportation tab, MRN
field).
Subsequent goods receipt posting for the inbound delivery generates a material document
that documents the stock change in the feeder system. The feeder system transfers the
customs-relevant data from the material document to SAP GTS. There, the material
document data fills a worklist for customs declarations after goods receipt. From this
worklist, users can create customs declarations for release for free circulation or for placing
the goods under another customs procedure. However, automatic replication of the material
document data in the form of a customs declaration is also possible.

Figure 48: Customs Declaration After to Goods Receipt
The customs declaration created from the data of the material document is the document
basis for communication with the customs authorities in all customs procedures that can
follow the completion of the transit procedure.
Note:
It is mandatory for the replication of the material document that the goods
receipt posting refers to an inbound delivery. A goods receipt posting for a
purchase order does not cause any data transfer.
Depending on the integration scenario you opt for, you have to make the following settings in
the Customizing for document transfer from the feeder system to SAP GTS:
Application area Indicators on document type or movement type level

MM0A (Receipt/Import: Pur- Transfer Documents for Customs Management (Scenar-
chasing Document) io “customs declaration before goods receipt”)
MM0B (Receipt/Import: Inbound Transfer Documents for Customs Management
Delivery Document)
Optional: Placement into Customs Status Before GR
(Scenario “customs declaration before goods receipt”)
Optional: Hold Goods Receipt if Unloading Permission Is
Missing (Scenario “customs declaration after goods re-
ceipt”)

MM0C (Receipt/Import: Material Transfer Documents for Customs Management (Scenar-

Document) io “customs declaration after goods receipt”)
Category of Goods Movement: Standard Goods Move-
ment
You can find the view for maintaining these settings in the Customizing of an SAP ECC feeder
system choosing Sales and Distribution → Foreign Trade/Customs → SAP Global Trade
Services - Plug-In → Control Data for Transfer to SAP Global Trade Services → Configure
Control Settings for Document Transfer. In an SAP S/4HANA feeder system choose
Integration with Other SAP Components → Integration with Governance, Risk and
Compliance → SAP Global Trade Services → Control Data for Transfer to SAP Global Trade
Services → Configure Control Settings for Document Transfer.
Note:
If you set the Hold Goods Receipt if Unloading Permission Is Missing indicator,
make sure that you activate the standard BAdI implementation Hold Goods
Receipt if NCTS Unloading Permission Is Missing (/SAPSLL/
DELV_CUS_U_GR_CHECK) using the Customizing activity Activate Hold of GR
Posting from Inb. Delivery if No Unloading Permission (menu path: Sales and
Distribution → Foreign Trade/Customs → SAP Global Trade Services - Plug-In and
Integration with Other SAP Components → Integration with Governance, Risk and
Compliance → SAP Global Trade Services respectively).
No mapping of document types and/or movement types is required in the SAP GTS system.
Replication of Billing Documents for Exports

You issue electronic or paper-based export declarations in SAP GTS based on customs
declarations. You can create these documents manually in the export procedure. However, it
makes sense to have customs declarations created automatically as replicates of suitable
billing documents in the SAP ECC or SAP S/4HANA feeder system. During this replication,
SAP GTS transfers all the essential data from the sales process to the customs declaration. If
required, you can change or complete data in the customs declaration before sending the
electronic message to the responsible customs office.

Figure 49: Sales Processes and Export Processing
Before you set up export process integration, you have to decide which feeder system
documents are relevant for transfer to SAP GTS. You select the document types in
Customizing in the feeder system, in the control settings for document transfer (menu path in
SAP ECC: Sales and Distribution → Foreign Trade/Customs → SAP Global Trade Services -
Plug-In → Control Data for Transfer to SAP Global Trade Services → Configure Control
Settings for Document Transfer; menu path in SAP S/4HANA: Integration with Other SAP
Settings for Document Transfer).
You set up the billing document replication control in application level SD0C (Dispatch/
Export: Billing Document). Unlike in Compliance Management, you do not have to configure a
document type and item category mapping in Customs Management. The document type
CULOEX (Customs Declaration: Export) contained in delivery Customizing is already assigned
to the relevant activity sequences (see the “Analyzing the Communication with Customs”
lesson).
Usually, it makes sense to define a separate billing type for export processing in the feeder
system and flag only this type as relevant for transfer to SAP GTS. Since billing documents
that are used as the basis for customs declarations often have to be created at an early stage,
this billing type is usually a pro forma invoice (sales document category U). Pro forma
invoices are not relevant for accounting.
However, the decisive factor for the replication to SAP GTS is not the accounting relevance,
but the delivery reference of a billing document. The feeder system only transfers billing
documents that refer to outbound deliveries. If you have flagged several billing document
types as relevant for transfer to SAP GTS, only the first billing document created for an
outbound delivery is replicated in the form of an export declaration in SAP GTS. This also
applies if several pro forma invoices of the same billing type are created for the same
outbound delivery.

Note:
The feeder system transfers only billing documents for export deliveries to SAP
GTS. The country of the supplying plant and the country of the ship-to party must
therefore be different. In addition, only one of the two countries may be flagged as
an EU Member State in database table T005 (Countries).
The transfer of inbound deliveries, material documents, and billing documents to SAP GTS
always takes place asynchronously. This means that the documents are first created in the
database of the feeder system and then transferred to SAP GTS via RFC. There are no
technically incomplete replicas in Customs Management. If mapping settings are missing or
other serious deficiencies exist, the replication fails. Therefore, SAP GTS does not create the
customs shipment or customs declaration for the feeder system document.
However, failed replication attempts are logged. If a customs declaration or customs
shipment is missing for a feeder system document, check the transfer log for this document
in SAP GTS. To track billing document replication, use the Display Transfer Log for Export
transaction (transaction code /SAPSLL/EXPORT_TLOG). For the tracking of inbound delivery
and material document replication, you can use the transactions Display Transfer Logs for
Inbound Deliveries (transaction code /SAPSLL/APITIBD_TLOG) and Display Transfer Logs for
Material Documents (transaction code /SAPSLL/APICUWL_TLOG).
If you have corrected the cause, or causes, for the document replication to fail in Customizing
or at master data level, you can trigger the transfer of document data in the feeder system
again. To do this, start the Transactional RFC transaction (transaction code SM58). Specify a
display period and execute the selection. In the results display, select the entry for the RFC
with errors and choose Edit → Execute LUW.
Note:
Depending on the configuration of the RFC destination for the data transfer to SAP
GTS, the feeder system repeats the transfer attempt at regular intervals. In this
case, you do not have to manually trigger the retransfer of the billing data.
SAP GTS replicates each billing document separately as a customs declaration. It is not
possible to group several customs declarations for a new document in SAP GTS. If goods
from several outbound deliveries are transported together for the same consignee in a third
country, it usually makes sense to create a collective billing document for these outbound
deliveries for transfer to SAP GTS.
In the SAP ECC or SAP S/4HANA feeder system, you can find a suitable transaction in the
area menu for communication with SAP GTS on the Documents tab (Shipment Consolidation:
Generate Customs Declarations from Sales Docs, transaction code /SAPSLL/CUS_INV_R3).
Alternatively, you can use the Maintain Billing Due List transaction (transaction code VF04).
Note:
In SAP S/4HANA, on-premise edition, the right to use the functions provided in
the Logistics Execution (LE) subcomponent LE-TRA (Transportation) is limited to
Dec 31, 2030 (see SAP Note 2269324).
When the billing document is replicated, SAP GTS always decides on the variant of the export
procedure and creates the customs declaration either for a normal procedure or for a

simplified procedure, where applicable. Users cannot influence or revise this system decision.
If the other procedure variant is to be processed, the billing document must first be canceled
in the feeder system or, in the case of a pro forma invoice, completed.
SAP GTS always opts for the simplified procedure during billing document replication if the
legal prerequisites for processing this procedure variant are met, that is, a suitable
authorization for the simplification exists in the system.
Figure 50: Normal Procedure and Simplified Procedure
If the data entered in the authorization for the simplified procedure (foreign trade
organization, legal unit with authorized location of goods, commodity code) does not match
the document data, or if the authorization is not yet valid or is no longer valid, the system
automatically chooses the standard procedure during billing document replication.
The decision for the normal procedure or the simplified procedure is the result of the activity
sequence determination that SAP GTS performs when replicating the billing document. An
activity sequence usually represents a procedure variant in the configuration of
communication with the customs authorities. The activity sequence defines the substeps
(activities) of a process – that is, the transfer to a customs procedure – and the sequence in
which these activities must be executed. The actual message determination is based on this
basic decision. It is covered in the “Analyzing the Communication with Customs” lesson.
Inventory Management for Special Procedures and Foreign-Trade Zones

The essential prerequisite for legal compliance in certain special procedures in the EU
(customs warehousing and processing) as well as in the use of foreign-trade zones in the
United States is the recording of all relevant goods receipts and issues. The same applies to
movements to, within, and from a foreign-trade zone. Inventory management in SAP GTS
must always be consistent with inventory management in the SAP ECC or SAP S/4HANA
feeder system.
The reference level of inventory management in SAP GTS is the customs ID, a freely definable
alphanumeric string of up to ten characters (menu path: SAP Global Trade Services, edition
for SAP HANA → General Settings → Organizational Structures → Define Customs ID for

Customs Procedures with Economic Impact). The customs ID must be created with the same
key in Customizing in the feeder system (menu path: Sales and Distribution → Foreign Trade/
Customs → SAP Global Trade Services - Plug-In → Customs Procedure with Economic Impact
- Define Customs ID in SAP ECC or Integration with Other SAP Components → Integration with
Governance, Risk and Compliance → SAP Global Trade Services → Customs Procedures with
Economic Impact - Define Customs ID in SAP S/4HANA).
Figure 51: Assignment of the Customs ID in Feeder System and in SAP GTS
In SAP GTS, you assign the customs ID to the foreign trade organization of the responsible
company code (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Organizational Structures → Control Customs ID for Customs Procedures with
Economic Impact). For customs IDs used for managing foreign-trade zone stock, you have to
make additional settings like the assignment of a FIRMS code or a fabric calendar (menu path:
SAP Global Trade Services, edition for SAP HANA → General Settings → Organizational
Structures → Control Customs ID for a Foreign-Trade Zone).
In the feeder system, you link the customs ID to the storage locations whose stocks are in the
customs warehouse, in inward processing, or in a foreign-trade zone (menu path: Sales and
Distribution → Foreign Trade/Customs → SAP Global Trade Services - Plug-In → Customs
Procedures with Economic Impact - Assign Customs ID in SAP ECC or Integration with Other
SAP Components → Integration with Governance, Risk and Compliance → SAP Global Trade
Services → Customs Procedures with Economic Impact - Assign Customs ID in SAP S/
4HANA).
For customs warehousing, ensure that you flag all movement types used in inventory
management in the feeder system as relevant for Customs Management and categorize them
according to their significance for the customs warehousing procedure. In addition to
Standard Goods Movement for goods receipts and goods issued, the following categories are
available in SAP ECC and SAP S/4HANA feeder systems for the integration of SAP GTS into
their inventory management:
Indicator Description Movement type (examples)

1 Scrapping 551
2 Returns 122, 651
3 Inventory Difference 701, 711
4 Undefined 501, 561

5 Transfer Posting 301, 311

6 Material to Material 309
Depending on the category of the movement type, SAP GTS stores the material documents in
different worklists. You can find these worklists in the SAP Fiori launchpad in the Customs
Special Procedures space on the Monitoring page. Additionally, a separate page for
monitoring and, where applicable, worklist processing is provided for each special procedure.
Similar settings might be required for managing stock in a foreign-trade zone. If your
company manufactures products in a foreign-trade zone entirely or in parts from imported
components (“foreign merchandise”), you must set the Relevance Work in Process indicator
in the entry for movement type 261 (GI for order) or its customer-specific equivalent. When
the goods issue is posted for the components of a work order in the feeder system, SAP GTS
automatically adjusts the stock of these components in the inventory of the foreign-trade
zone assigned to the relevant combination of issuing plant and storage location. In the stock
overview, the product quantities consumed in the manufacturing process are displayed in a
separate column titled Work in Process.
Additionally, set the Goods Receipt from Production indicator in the entry for movement type
101 (GR goods receipt), movement indicator F (Goods movement for production order). When
the goods receipt for the finished product is posted in the feeder system, the corresponding
quantities are displayed in the stock overviews of the foreign-trade zone if the In-House
Production indicator is set in the selection screen of the apps.
When the finished product is entered for consumption to be sold to a domestic customer, the
work-in-process stock of its components is reduced accordingly based on the goods issue
posting for the outbound delivery in the feeder system, provided that movement type 601 (GD
goods issue:delvy) with movement indicator L (Goods movement for delivery note) is flagged
as relevant for Customs Management.
LESSON SUMMARY

Unit 7
Lesson 2
Managing Customs Code Lists and Data
Defaulting
LESSON OVERVIEW
Before issuing the electronic import or export declaration, users can still edit the customs
declaration to add or change missing data. This lesson discusses options for proposing
document data in SAP GTS in a meaningful and comprehensive manner.
Business Example
The IDES group wants to file customs declarations in various countries using SAP GTS.
LESSON OBJECTIVES
Customs Code Lists

Numerous fields in the customs declaration must be filled with codes that are contained in
code lists published by the national customs administrations or, in the EU, by the European
Commission. Examples of such code lists are:
● Declaration type
● Customs status
● Customs procedure
● Mode of transport at the border
● Range of Goods
Delivery Customizing for SAP GTS already contains numerous customs code lists for different
countries (menu path: SAP Global Trade Services, edition for SAP HANA → Customs
Management → Customs Code Lists). Since the European Commission and national customs
authorities repeatedly make changes to the code lists, however, occasional manual
postprocessing of the delivered data is required. Delivery Customizing is also updated in
support packages. By comparing the affected maintenance views with the settings in client
000, the code lists can also be updated to the current status after you implement support
packages.
Note:
If you know the RFC destination for client 000, you can perform this adjustment
directly from the menu of the maintenance view (Utilities → Adjustment).

Figure 52: Customs Code Lists in SAP GTS
Most of the code lists are included in country-specific procedures in delivery Customizing. In
Germany, for example, you primarily use the procedure CUCDE (Customs Processing:
Germany), in the United States the procedure CUSUS (Customs Processing: United States),
and so on. The procedures are already assigned to the respective legal regulations (menu
path: SAP Global Trade Services, edition for SAP HANA → Customs Management → Customs
Code Lists → Assign Customs Code Lists Procedure to Legal Regulations).
The procedures bundle the categories of code lists (code list objects) required for filing
customs declarations. To check or supplement the codes for an object, choose SAP Global
Trade Services, edition for SAP HANA → Customs Management → Customs Code
Lists → Maintain Customs Code Lists for Legal Regulation.
For most fields of the customs declaration, there is only one code list for all customs
procedures. However, there are customs procedure-dependent code lists for individual fields
of the customs declaration, for example, for the Mode of Transport field on the Transportation
tab on header level. In the export and transit procedures, different codes are to be specified in
this field than in the other customs procedures.
Delivery Customizing therefore contains a code list procedure SAP (SAP: Code Lists), which is
assigned to the combination of different legal regulations and code list object MOTBC (Means
of Transport Type). The code list contains twelve codes that are to be entered in the
documents as placeholders for the respective customs procedure-dependent codes. Based
on a predefined conversion in delivery Customizing, SAP GTS replaces the placeholder in the
outbound IDoc for the customs declaration with the appropriate code (menu path: SAP Global
Trade Services, edition for SAP HANA → Customs Management → Customs Code
Lists → Reassign Values from Customs Code Lists).
In SAP ECC and SAP S/4HANA, packaging materials that are used for packing in deliveries
have to be grouped by assigning a packaging material type according to their physical
properties, such as boxes of a certain size or crates of a certain type (Sales: General Plant
Data view in the material master). Packaging material types are defined in Customizing for
shipping (menu path: Logistics Execution → Shipping → Packing → Define Packaging Material
Types).

Lesson: Managing Customs Code Lists and Data Defaulting
Figure 53: Mapping Packaging Material Types to Package Types
If you want to copy packaging data from the handling units that are assigned to outbound
deliveries to customs declarations in SAP GTS, you have to map the relevant packaging
material types of the feeder system to package types of the applicable customs code list
(menu path in Customizing for SAP GTS: SAP Global Trade Services, edition for SAP
HANA → Customs Management → Customs Code Lists → Assignment of Packaging Material
Types from Feeder Systems). As for other mapping settings in SAP GTS, you can choose
between an assignment at logical system level or at logical system group level.
Defaulting Data
Not all data relevant for a customs declaration can or should be copied from the feeder
system documents. To keep the manual processing effort in SAP GTS as low as possible, you
can fill numerous fields of the customs declaration using the defaulting data scheme. This
scheme uses an SAP GTS-specific condition technique that is based on rules for defaulting
field values. For example, if the country of destination of the export is India, the system should
propose “Air” as the mode of transport at the border.
The contents of source fields in the customs declaration represent the condition, or
conditions, for filling target fields in the same document. As in the classic condition technique
in SAP ECC or SAP S/4HANA, you define access sequences that bring data defaulting rules
into a specific sequence. When you create a customs declaration, the system processes the
rules contained in an access sequence one after the other. If it can fill a target field with the
first default rule of an access sequence, it ends the search.

Figure 54: Structure of Data Defaulting
The delivery Customizing already contains a large number of templates for default
procedures (menu path: SAP Global Trade Services, edition for SAP HANA → Customs
Management → Procedures for Defaulting Data → Define Default Data for Document Fields,
Messages, and Documents). Most of these default procedures are country-specific. They
group together target fields of the customs declaration. An access sequence is assigned to
each target field in a default rule. Each access sequence consists of at least one field
combination. Field combinations correspond to the condition tables in the condition
technique in SAP ECC and SAP S/4HANA. If required, you can create new field combinations
by grouping together up to eight source fields.
You can use procedures for defaulting data for different areas of application:
Scope of Application
● Dates
● Document partner
● Document fields
● Message determination
● Determination of recipients of e-mails with file attachments
You assign the default procedures to combinations of legal regulation, document type, and
process activity (menu path: SAP Global Trade Services, edition for SAP HANA → Customs
Management → Procedures for Defaulting Data → Define Determination Procedures for
Defaulting Data). The system checks for each customs declaration whether the defaulting of
data is possible. If the feeder system document contains foreign trade data that can be copied
directly to the corresponding fields in the customs declaration, these data take precedence
over the default data.
Users can fill the default rules prepared in Customizing with content. The maintenance of
attributes of default rules as master data corresponds to the creation of condition records, for

Lesson: Managing Customs Code Lists and Data Defaulting
example, for pricing, in SAP ECC or SAP S/4HANA. Three transactions are available for this
master data maintenance:
● Define Attributes of Default Data Rules for Document Fields (transaction code /SAPSLL/
DPDATA_MNTN)
● Define Attributes of Default Data Rules for Messages (transaction code /SAPSLL/
DPDATA_MSG)
● Define Attributes of Default Data Rules for E-Mail Notifications (transaction code /SAPSLL/
DP_MAIL_MNTN)
You can export data defaulting rules to XML files for reimport into another SAP GTS system
(Menu path in the transaction: Default Data → Export Data and → Import Data).
LESSON SUMMARY


Unit 7
Lesson 3
Analyzing the Communication with Customs
LESSON OVERVIEW
Based on the customs declaration that SAP GTS generates from the data of a feeder system
document, you send the electronic customs declaration and, if necessary, print documents
such as certificates of origin or send e-mails to externals. The system also links the response
messages from the customs authorities with the customs declaration. This lesson discusses
the Customizing settings that underlie this message exchange.
Business Example
The IDES group plans to file import and export declarations electronically using SAP GTS.
However, the legal and technical prerequisites must be clarified in advance.
LESSON OBJECTIVES
Data Exchange in the Export Procedure (EU)

Based on the UCC and its implementing provisions, the customs administrations in the EU
specify the process of electronic data exchange in the respective national IT procedure in
detail. As part of the eCustoms project, the EU established a standardized electronic export
procedure. The Export Control System/Automated Export System (ECS/AES) provides a
common platform for the electronic submission and processing of export declarations, and
for electronic data exchange between the economic operators and the customs offices.
The AES provides for a variety of procedures. This lesson explains the settings required for
processing an export in the EU using the example of the two-step procedure in both the
normal procedure and in the simplified procedure (simplified declaration).

Figure 55: Message Exchange in the Export Procedure in the AES (EU)
Regardless of the procedure variant, an export declaration is at the start of the data
exchange. The message is checked automatically in the IT system of the national customs
administration. If the declaration is error-free, the customs office of export accepts it. The
customs office of export informs about functional or technical errors in a specific message. In
both cases, you have to resend the export declaration after correcting the error.
AES assigns an MRN to the transaction. This number uniquely identifies the transaction in the
entire AES. To notify the receipt of the export declaration, the customs office of export sends
a status message. In the normal procedure, the goods to be exported now have to be
presented at the customs office of export. In the simplified procedure, presentation takes
place at a location specified in the authorization (authorized location).
After checking the data filed in the export declaration, the customs office of export usually
approves it and informs the sender about this decision in a new status message. However, the
customs office can also order an examination or other control measures. In the simplified
procedure, the receipt and acceptance of the export declaration coincide in the status
message.
If the check results are satisfactory, the customs office of export then releases the goods
automatically and sends a corresponding message. In connection with the release
notification, the customs office of export sends an export accompanying document (EAD) as
an attachment in PDF format. Economic operators are free to carry the EAD on paper when
transporting the goods to the border of the customs territory of the EU and to submit it to the
office of exit. In each case, the MRN is required as plain text and as a bar code.
The customs office of export notifies the export/declarant of the physical issue of the goods
in a final message.
Control of Communication with Customs Authorities

In delivery Customizing, the data exchange with the customs administrations of different
countries is already largely preconfigured and, in the case of electronic communication, in
most cases coordinated with the authorities in certification procedures. Changes to the
delivered configuration should therefore be made with great caution, if at all.

Lesson: Analyzing the Communication with Customs
Note:
In this context, SAP Note 1989009 also warns against interference with the
program source code. If adjustments to the system settings are required due to a
release upgrade in the IT procedure of a national customs administration, you will
find corresponding instructions in SAP Notes.
When replicating the billing document, SAP GTS determines, among other things, the foreign
trade organization responsible for the export. The system takes the country whose customs
legislation is to be applied from the address of the business partner in this role. Therefore, if
the billing document was created for a French company code, for example, SAP GTS finds the
country code FR in the business partner address of the foreign trade organization assigned to
the company code. The legal regulation activated in delivery Customizing for processing
exports from France is CUSFR (Customs Processing - France).
In Customs Management, a process template is assigned to each legal regulation (menu path:
SAP Global Trade Services, edition for SAP HANA → Customs Management → Control
Settings for Application Areas by Legal Regulation of a Legal Code). Process templates are
always country-specific and form the framework on which communication with the customs
authorities is based. You can see the structure of a process template in the communication
control in Customs Management (menu path: SAP Global Trade Services, edition for SAP
HANA → Customs Management → Communication Processes → Define Control Settings for
Communication Processes).
Figure 56: Output Control in Customs Management
As a rule, the processes of a process template represent the customs procedures under
which you can place goods using SAP GTS. The process CUSEX of the process templates for
EU Member States basically represents the export procedure, but, as the case may be, also
re-exporting and outward processing. It consists of a variety of process activities. Process
activities represent individual substeps of the respective customs procedure. Some substeps
of the export procedure can be represented by several process activities.

In the process template for Germany (CUSDE), for example, activity EXNVA represents the
issue of an export declaration in the normal procedure (standard customs declaration),
whereas activity EXZAA is the same step in the simplified procedure (simplified declaration).
Some activities are flagged as optional substeps of the export procedure.
Messages are assigned to each activity of a process. Depending on the function of the activity,
it is a combination of outbound and inbound messages, or else just one or the other. For
example, an activity for the export declaration includes an outbound message and one or
several inbound messages for the answers to be received from the customs office of export.
The process activities of the process CUSEX are included in activity sequences in the delivery
Customizing. Activity sequences are assigned to process templates and comprise several
process activities of a process and define the sequence in which these activities must be
executed. As a rule, there are separate activity sequences for the normal procedure and for
the simplified procedure. It is also possible to differentiate between complete and incomplete
customs declarations, or between customs declarations prior to the presentation of goods
and customs declaration filed at the time of presenting the goods to customs.
Note:
The simplified declaration without a formal authorization replaces the incomplete
export declaration. Submission of a supplementary export declaration is still
required.
If electronic data exchange with the customs authorities is temporarily not possible for
technical reasons, a fallback procedure can be used in some Member States. In this
procedure, customs allows the customs declaration in question to be submitted in paper
form. The process flow of the fallback procedure is always controlled in a separate activity
sequence.
Message Determination
As you learned in the “Setting Up the Integration into Feeder System Processes” lesson, the
SAP GTS system decides which activity sequence is used as the basis for the customs
declaration during billing document replication. The simplified procedure always takes
precedence over the normal procedure. If there is a master record for a suitable authorization
for the transaction, SAP GTS chooses the simplified procedure. If there is no authorization or
if the existing authorization cannot be used, the system opts for the normal procedure
instead. A key prerequisite for the replication of the billing document is therefore a successful
determination of the activity sequence.
You can influence the determination of activity sequences in a Customizing maintenance
view, which you can call choosing the menu path SAP Global Trade Services, edition for SAP
HANA → Customs Management → Communication Processes → Define Determination for
Activity Sequence. The delivery Customizing already contains entries for the export (target
procedure 04). Some entries are provided for the determination of the normal procedure,
others for the determination of a simplified procedure.
Some of the entries contain the indicator S1 in the Special Trade column. This indicator
represents chain transactions in which the declarant delivers goods to a consignee in a third
country on behalf of another person (customs representation). SAP GTS recognizes this
constellation from a program-internal indicator of the billing data transferred from the feeder
system. If the sold-to party and supplying plant are in the same country, the system sets the
S1 indicator at the time of replicating the billing document. Based on this indicator, SAP GTS
can determine a specific activity sequence for customs representation.

Lesson: Analyzing the Communication with Customs
The actual message determination that is based on the activity sequence is part of the
procedure for defaulting data, which was discussed in the “Managing Customs Code Lists and
Data Defaulting” lesson. Delivery Customizing contains, among other things, country-specific
default procedures for message determination in export declarations. These procedures
contain a single target field: $MESSAGE (Message). You can use these procedures directly as
the basis for defining determination records or as a template for a procedure that you have
defined yourself in the customer namespace.
You use the Define Attributes of Default Data Rules for Messages transaction (transaction
code /SAPSLL/DPDATA_MSG) to create the output determination rules for message
determination in customs declarations.
Figure 57: Output Control in SAP GTS
SAP GTS uses the Post Processing Framework (PPF) to generate IDocs for the customs
declarations in an SAP-specific format and to transfer these documents to the EDI converter.
The PPF is a solution-independent tool for application development within the SAP
NetWeaver. As the technical successor to message control in SAP ECC, the PPF generates
condition-dependent actions. Data output in IDoc format is only one of several options: You
can also use PPF actions to print document data on forms or to send e-mails.
In Customs Management, an action definition is assigned to each outbound message. The
action definitions are grouped into country-specific action profiles. You can find all the action
profiles required for communication with the customs authorities by choosing SAP Global
Trade Services, edition for SAP HANA → Customs Management → Communication
Processes → Define Technical Medium for Messages (PPF Actions) for General Documents
and → Define Technical Medium for Messages (PPF Actions) for Supp. Customs Decl..
LESSON SUMMARY


Unit 7
Lesson 4
Connecting Customs Agents
LESSON OVERVIEW
As you have learned, SAP GTS has been certified by the national customs authorities of
various countries to participate in electronic procedures. But how can you use SAP GTS for
customs processing in the rest of the world? This lection introduces the functions provided
for integrating customs service providers using export as an example. However, you can also
use these functions for imports.
Business Example
Some subsidiaries of the IDES group decided to engage customs agents to handle the
communication with the respective national customs authorities. They want to use SAP GTS
to provide the customs agents with the data required for filing customs declarations on their
behalf.
LESSON OBJECTIVES
Process Flow of Communication with Customs Agents

In countries where you cannot, or do not want to, communicate directly with the national
customs authorities, you usually commission specialized service providers to handle customs
formalities during import and/or export. Your carrier may also offer this service in connection
with the transportation of the goods. You can provide your customs agent with the
information he needs to submit customs declarations electronically from your SAP GTS
system. In return, the customs agent notifies you electronically of the status of customs
clearance.
The basis for communication with the customs agent is a customs declaration. That is, a
document that is either created by replicating a feeder system document or created manually
in SAP GTS. The customs declaration contains all the planned import or export data that the
agent needs to submit a customs declaration on your behalf. SAP GTS can use the data
defaulting procedure to supplement the data provided by the feeder system.
Based on the customs declaration, SAP GTS then issues either message MB001 (Request
Customs Import Declaration) or message MB010 (Request Customs Export Declaration),
depending on the transaction. Both messages are assigned a PPF action definition for
generating an XML file using a Web service. The XML files contain the commissioning of the
agent in connection with the provision of the relevant information.
The Web services that SAP GTS provides for data exchange with customs service providers
are located in the Enterprise Services Repository, whose contents you can display using the
Enterprise Repository Browser. To call the browser, use transaction code SPROXY. All service

groups and definitions delivered for SAP GTS are created in the namespace HTTP://
SAP.COM/XI/GTS/GLOBAL2.
Note:
You can find additional SOA documentation for the enterprise services used in
the communication with customs agents in SAP Notes 2548730, 2562230,
2562315, and 2562324.
Based on the data transferred in the XML file, the agent submits a customs declaration to the
customs authorities and receives all responses from this authority. You receive information
from the agent regarding the current procedure, such as the release notification, via other
Web services in the form of messages IB001 (Notification of Customs Import Declaration) or
IB010 (Notification Customs Export Declaration). In the export procedure, you then receive
message IB015 (Notification Exit from Customs Area) via Web service. In the import
procedure, you can use message IB020 (Authorization Import Duty Statement) to obtain
information about the import duties.
Figure 58: Process Flow of Communication with Customs Agents (Export EU)
The inbound processing of the XML files updates some data of the customs declaration in
SAP GTS, for example, the customs offices involved. The agent can also use the IB001 or
IB010 messages to request additional data or the correction of inconsistent data. You correct
the customs declaration and then resend message MB001 or MB010. In the customs
declaration, you can also rate the agent on the basis of a freely definable scale.
During import, the customs agent can also use accompanying documents provided outside
the SAP GTS system, such as bill of lading, air waybill, commercial invoice, and freight list, in
order to submit a customs declaration on your behalf. After completing the customs
formalities, the agent sends you an XML file. The inbound processing of this file in SAP GTS
creates a customs declaration exclusively to document the transaction. Therefore, you can no
longer change the data of this document. To create such customs declarations, document
type CURPIM (Replicate of Customs Declaration - Import) is available in delivery Customizing.

Lesson: Connecting Customs Agents
Note:
The procedure described in the above paragraph is also referred to as broker-
centric scenario.
Configuration of Data Exchange with Customs Agents

The control of communication with customs agents is basically the same as the control of
direct data exchange with national customs authorities. You can find the required messages
in the delivery Customizing using the menu path SAP Global Trade Services, edition for SAP
HANA → Customs Management → Integration with Customs Agents → Messages for
Communication with Customs Agents.
Compared to messages for direct communication with customs authorities, the settings of
both messages for the integration of service providers contain only a few fields. The
assignment of the action definition for the generation of an XML file, with the declaration-
relevant data of the customs declaration and the call of the Web service in the Action
Definition field, are decisive.
The two action definitions for customs agent integration are each assigned to their specific
action profiles BRT_CU_IM (Customs Processing Through Customs Broker - Import) and
BRT_CU_EX (Customs Processing Through Customs Broker - Export). In delivery
Customizing, neither profile is assigned to a document type or to a combination of document
type and legal regulation. If necessary, you have to make this assignment yourself (menu
path: SAP Global Trade Services, edition for SAP HANA → General Settings → Document
Structures → Define Document Types for Application Areas, folder Customs Declaration,
subfolder Control Settings by Legal Regulation).
Make sure that you assign the partner function CUSLCB (Customs Broker) to your self-
defined partner groupings for connecting customs agents.
You can find the communication control for customs agent integration via the menu path SAP
Global Trade Services, edition for SAP HANA → Customs Management → Integration with
Customs Brokers → Define Activity Sequences. The process template CUBRT (Customs
Processing - Communication with Customs Brokers) comprises the two processes CUSEX
(Export) and CUSIM (Free Circulation). The activities CUSEX (Request Customs Export
Declaration) and CUSXT (Exit from Customs Area) are assigned to the process CUSEX.
The activity sequence of the same name is made up of these two activities. Message MB010,
in which you commission the agent to issue an export declaration, is assigned to the process
activity CUSEX in delivery Customizing. Message IB010 is also assigned to receive
confirmations from the agent. The process activity CUSXT is used only to receive the exit
confirmation in message IB015.
You have to add mapping settings to complete the configuration contained in delivery
Customizing for the following entries in the customs declaration:
Mapping Required for Connecting Customs Agents
● Identification or registration numbers of involved partners

● Partner functions
● Amount types
● Text types

The mapping is necessary because identification numbers, partner functions, amount types,
and text types are freely definable keys whose meanings are defined in SAP GTS Customizing.
Therefore, you have to make agreements with your customs agent how to interpret these
keys and store these agreements in your SAP GTS system.
For this purpose, SAP recommends the use of codes provided by different national and
international organizations for electronic data exchange and refers in this context to the UN/
EDIFACT data element 3055 (“Code list responsible agency code”). Data element 3055
consists of a list of institutions (“agencies”) that provide codes for different purposes. The
delivery Customizing already contains some codes for institutions (AgencyID) that are listed
in data element 3055 (menu path: SAP Global Trade Services, edition for SAP
HANA → Customs Management → Integration with Customs Agents → Define AgencyID).
You first agree with your customs agent which code lists you use in your electronic
communication to denote partner functions, amount types, and text types. You enter these
agreements in Customizing in the form of CodeListIDs using the menu path SAP Global Trade
Services, edition for SAP HANA → Customs Management → Integration with Customs
Agents → Define CodeListID.
You then assign the combinations of CodeListID and AgencyID to the agent in connection with
the mapping object (code list type). You make this assignment in the application menu of
Customs Management (Master Data button, Partner tab). You can also call the Assign Code
Lists to Customs Broker view directly using transaction code /SAPSLL/LCB_CL_MAIN.
You maintain the mapping for partner functions, amount types, and text types in Customizing
by choosing SAP Global Trade Services, edition for SAP HANA → Customs
Management → Integration with Customs Agents → Assign External Partner Role and
→ Assign External Amount Types and → Assign External Text Types respectively.
As a rule, you maintain identification or registration numbers of your company in the
respective business partners (foreign trade organizations) in connection with specific
identification types. To connect customs agents, you link these identification types with the
agency IDs of the institutions that assign the identification or registration numbers (menu
path: SAP Global Trade Services, edition for SAP HANA → Customs
Management → Integration with Customs Brokers → Assign BP ID Type to an External
Identification Scheme). The FDA Establishment Indicator (identification type SLLFEI), for
example, is assigned by the FDA (agency ID 27).
If an agency assigns more than one identification number, you agree on additional keys
(Scheme ID) with your customs agents to differentiate between these identification numbers
in XML files. The German customs administration, for example, is responsible for assigning
several identification numbers in Germany. To enter the AEO certificate number, EORI
number, and branch number of a foreign trade organization in its business partner master
record, you use the identification types SLLAEO, SLLEOR, and SLLBRA. To be able to link
these three identification types to the same AgencyID, self-defined IDs must be added in the
Scheme ID field.
The customs agent may update or add data that you have sent in messages MB001 or MB010
in the actual import or export declaration. A typical example is a change of the customs office
of exit, because the forwarding agent responsible for transporting the goods chose a different
route. Messages IB001 and IB010 contain the contents of the actual import or export
declarations. However, the inbound processing of these messages does not have to transfer
all changes to the customs declarations in SAP GTS. To enable the system to determine and
evaluate critical deviations between the contents of the outbound and inbound messages, you
can implement the BAdIs /SAPSLL/BADI_BRKR_MNTRG_IMPRT (Monitor Communication
with a Customs Broker During Import) and/or /SAPSLL/BADI_BRKR_MNTRG_EXPRT (Monitor
Communication with Customs Broker in Export).

Lesson: Connecting Customs Agents
For the assessment of the deviations detected in the BAdIs, you define degrees of message
severity in Customizing, such as, “slight error” or “serious error”, and message categories,
such as, “information” or “error” (menu path: SAP Global Trade Services, edition for SAP
HANA → Customs Management → Integration with Customs Agents → Define Message
Severity or → Define Message Category). If you have implemented the BAdIs accordingly, the
system displays any deviations and their assessment in the Customs Broker view at
document header level of the affected customs declaration.
In the BAdI implementation, the result of the evaluation of the message content can also be
used to rate the services of the customs agent. For this performance rating, you define a scale
in Customizing (menu path: SAP Global Trade Services, edition for SAP HANA → Customs
Management → Integration with Customs Agents → Define Performance Rating Scale). In the
Customs Broker view of the customs declaration header, you can rate the agent manually. In
the Display Performance Evaluations - Customs Broker app (export) and in the Display
Performance Rating - Customs Broker app (import), you can display an overview of the rating
of a customs agent.
LESSON SUMMARY


Unit 7
Learning Assessment
1. For which of the special procedures in the EU do you need a customs ID in the feeder
system and in SAP GTS?
X A Transit
X B Customs warehousing
X C Inward processing
X D Outward processing
X E End-use
2. Which customs code list object is used for codes for documents of all kinds?
X A CUIND
X B EXART
X C MESNO
X D PAPTY
X E PGETY
3. The processes assigned to a process template represent customs procedures.

X True
X False

4. For which objects do you have to set up mapping for connecting customs agents to SAP
GTS?
X A Text types
X B Identification numbers
X C Document types
X D Partner functions
X E Amount types

Unit 7
1. For which of the special procedures in the EU do you need a customs ID in the feeder
system and in SAP GTS?
X A Transit
X B Customs warehousing
X C Inward processing
X D Outward processing
X E End-use
Correct. You need a customs ID for customs warehousing, inward processing, and
outward processing.
2. Which customs code list object is used for codes for documents of all kinds?
X A CUIND
X B EXART
X C MESNO
X D PAPTY
X E PGETY
Correct. The customs code list object PAPTY (Type of Previous Document/Document/
Certificate) is used for document codes.
3. The processes assigned to a process template represent customs procedures.

X True
X False
Correct. The processes assigned to a process template represent customs procedures.

4. For which objects do you have to set up mapping for connecting customs agents to SAP
GTS?
X A Text types
X B Identification numbers
X C Document types
X D Partner functions
X E Amount types
Correct. You have to maintain mapping settings for identification numbers, text types,
partner functions, and amount types.

UNIT 8 Preference Processing
Lesson 1
Mapping Preferential Agreements in SAP GTS 149
Lesson 2
Mapping Rules of Origin 153
Lesson 3
Setting up Preference Determination 163
Lesson 4
Setting up Supplier’s Declaration Management 169
UNIT OBJECTIVES
● Opt for or against manual maintenance of agreements and rules of origin

● Create and activate legal regulations for mapping preferential agreements
● Map rules of origin for preference determination in SAP GTS
● Define preference models
● Set up the retransfer of preference indicators to the feeder system
● Set up supplier’s declaration management

Unit 8: Preference Processing

Unit 8
Lesson 1
Mapping Preferential Agreements in SAP GTS
LESSON OVERVIEW
The EU has concluded preferential agreements with a large number of countries. Further
agreements are in preparation. Most of these agreements contain a protocol specifying the
conditions under which a product is considered to be the originating product of the
contracting party. This lesson deals with mapping these agreements in SAP GTS.
Business Example
Subsidiaries of the IDES group in the EU regularly supply pumps to customers in countries
with which the EU has concluded preferential agreements. These subsidiaries intend to check
in SAP GTS whether these customers can import the pumps as EU originating goods at a
preferential customs duty rate. They also want the system to check whether they are entitled
to issue the corresponding proofs of origin.
LESSON OBJECTIVES
Cumulation Zones
You map the EU's preferential agreements with countries that are of interest to your sales
processes as legal regulations in SAP GTS. However, you do not have to define a separate
legal regulation for each relevant agreement. Instead, you can group agreements with
identical rules of origin into a single legal regulation. This legal regulation then represents a
cumulation zone, that is, a network of countries with identical rules of origin. For example, you
can take advantage of the system of the Pan-Euro-Mediterranean (PEM) cumulation in this
grouping of agreements. In this cumulation zone, materials originating in one of the
participating countries may be used without sufficient working or processing if the originating
product produced from these materials is exported to another country in the network.
As a prerequisite for the development and extension of this cumulation system, the EU and its
partner states in the PEM area have already largely harmonized the rules of origin in bilateral
preferential agreements.

Figure 59: Examples of Preferential Arrangements
With the Regional Convention, the EU intended to standardize the rules of origin in the PEM
area to facilitate cumulation. This convention, adopted in the EU on 1 May 2012, will
successively replace the approximately 60 bilateral origin protocols within the scope of the
PEM cumulation zone. Some EU partner states are already applying the Convention. A
corresponding reference has been included in the origin protocols of the affected bilateral
preferential agreements. The rules of origin defined in the Convention basically represent the
intersection of the rules contained in the bilateral origin protocols within the PEM area.
The Convention is also intended to modernise and simplify the existing rules of origin within
the PEM area. As not all partner states were willing to accept the simplified rules of origin
suggested by the EU in a revised version of the Convention, the EU implemented an
alternative set of rules of origin (transitional rules). These transitional rules correspond to the
simplified rules in the draft of the revised Convention. They may be applied instead of the
rules of the Convention, on a bilateral basis pending the adoption of the revised Convention.
Note:
You can find out about the current status of the applicability of the Regional
Convention and the transitional rules on the website of the European
Commission, Directorate General Taxation and Customs Union (https://
ec.europa.eu/taxation_customs).
Some data providers sell complete lists of working and processing in XML format for upload
to SAP GTS. This upload largely saves you the system configuration described in this unit.
However, you cannot influence the mapping of the agreements and their rule sets in the
system. As a rule, the upload creates a separate legal regulation for each preferential
agreement. In the application transactions for preference determination and the management
of supplier's declarations, the number of entries to be analyzed or processed can therefore
become large and confusing.

Lesson: Mapping Preferential Agreements in SAP GTS
Note:
You can restrict the selection of agreements on the selection screens of the
programs for preference determination.
To upload preferential agreements and their rules of origin from XML files to your SAP GTS
system, you can use the Load Preference Rules from XML File transaction (transaction code /
SAPSLL/PREF_RLS_UPL).
If you decide to map preferential agreements manually, you first create the corresponding
legal regulations in Customizing for SAP GTS (menu path: SAP Global Trade Services, edition
for SAP HANA → General Settings → Legal Regulations → Define Legal Regulation). In the
Legal Code field, select 06 (Preference Law), and 3 (Import/Arrival and Export/Dispatch) in
the Import/Export field.
The delivery Customizing contains two legal regulations that you can use as templates for
mapping the Pan-European and PEM cumulation zones. The legal regulation PANEG
represents all agreements in which Pan-European cumulation can be used. The PNMED legal
regulation is provided as a template for mapping the PEM cumulation zone.
Note:
The Pan-European cumulation zone comprises the EU, the members of the
European Free Trade Area (EFTA), and Turkey.
In the training system, some of the preferential agreements the EU has concluded with other
countries were mapped individually as legal regulations to be used in the exercise for this
lesson.
The rule sets of some of the newer preferential agreements differ significantly from the rule
set of the Regional Convention and the older bilateral agreements. In this respect, the
Agreement between the European Union and Japan for an Economic Partnership (EPA) and
the Trade and Cooperation Agreement (TCA) between the European Union and the United
Kingdom of Great Britain and Northern Ireland play an important role.
Activation of Preferential Agreements

You always activate legal regulations for preference processing for combinations of country
groups. Each of these country groups represents a party to the agreement. For example, the
legal regulation ZEEA for mapping the European Economic Area (EEA) agreement is activated
for the combination of a country group for the EU and another country group for the European
Free Trade Association (EFTA). Both country groups are assigned to the legal regulation
(dialog structure of the definition of legal regulations, folder Assignment of Country Groups).
Regardless of which preferential agreements you map in SAP GTS, you have to create country
groups for the respective signatory states and assign these country groups to the appropriate
legal regulations for the preferential agreements. This also applies if a single state is a
contracting party to the EU. For example, if you want to map the EU's free trade agreement
with the Republic of Korea as a legal regulation, you define a new country group whose only
member is the Republic of Korea.
The delivery Customizing already contains some country groups for different combinations of
partner states. The country group PANEUROPA, for example, comprises the four EFTA
countries (Iceland, Liechtenstein, Norway, Switzerland). However, since Switzerland has not
ratified the EEA agreement, there is also the EFTA country group consisting only of the
members Iceland, Liechtenstein and Norway. If required, you can define additional country

groups (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Legal Regulations → Define Country Group).
You also assign countries to country groups in Customizing (menu path: SAP Global Trade
Services, edition for SAP HANA → General Settings → Legal Regulations → Assign Countries
to Country Group). You can display the assignment of countries to country groups using the
Display Country for Country Groups and Agreement app.
The delivery Customizing provides the determination procedure LEPRE (GTS: Determ. of Leg.
Reg. for 'Preference Processing' Serv.) for the determination of preferential agreements in
preference processing. The determination strategy ALRG13 (Determine Legal Regulation:
Country Group/Country Group Lvl) is assigned to this determination procedure (menu path:
SAP Global Trade Services, edition for SAP HANA → General Settings → Legal
Regulations → Define Determination Procedure for Active Legal Regulations). You should keep
this assignment unchanged.
You first activate each legal regulation that represents a preferential agreement or an
agreement group in the general settings (menu path: SAP Global Trade Services, edition for
SAP HANA → General Settings → Legal Regulations → Activate Legal Regulations at Country/
Country Group Level). In doing so, you define where the agreements apply. To activate a legal
regulation for a combination of two country groups, select the legal regulation and open the
Country Group folder in the dialog structure. Choose New Entries and add the country groups
for which you want to activate the legal regulation. Then select one of the country groups and
open the Country Group/Country Group folder in the dialog structure. Choose New Entries
again to add the partner country group, or groups. Repeat this step for the other country
groups.
At Preference Management level, you activate legal regulations in the same way for all
combinations of country groups from general activation (menu path: SAP Global Trade
Services, edition for SAP HANA → Preference Management → Activate Preference
Agreements). First select the legal regulation to be activated and open the Country Group
folder in the dialog structure. Then select one of the country groups and open the Country
Group/Country Group folder. In the Export Preference column, select the relevant indicator. In
the example of the EEA agreement, only exports are relevant for the country group
combination ZEU/EFTA (indicator 2 Check: Export (Exclusively)). To be able to request and to
issue supplier's declarations domestically and in the rest of the EU, the legal regulation ZEEA
has been activated for the country group combination ZEU/ZEU with the indicators 4 Check:
Receipt/Import (Including Domestic) and 4 Check: Dispatch/Export (Including Domestic)
respectively.
LESSON SUMMARY

Unit 8
Lesson 2
Mapping Rules of Origin
LESSON OVERVIEW
In the preferential agreements of the EU, the rules of origin, that is, the specifications for the
sufficient working and processing of materials without preferential origin, are arranged in
table form in lists. This lesson shows you how to map rules of origin in SAP GTS.
Business Example
LESSON OBJECTIVES
Lists of Working and Processing

Each preferential agreement contains, among other things, a protocol that specifies the
conditions under which a product is regarded as an originating product of the signatory
states. On the one hand, originating products are products that have been wholly obtained or
manufactured in the country or group of countries of the parties to the agreement. This
definition primarily applies to raw materials and agricultural, forestry, and fisheries products.
On the other hand, originating products are “products obtained in the Contracting Party
incorporating materials which have not been wholly obtained there, provided that such
materials have undergone sufficient working or processing in that Contracting Party” (Article
2 of Appendix I to the Regional Convention). This definition is relevant for most industrially
manufactured products. Therefore, in the production of an originating product materials may
be used that are not originating products. The preferential agreements specify what is
considered to be sufficient working or processing of these materials.
In the agreements, the requirements for the sufficient working or processing of the materials,
referred to as rules of origin, are arranged in lists in tabular form. The reference level of the
rules of origin is the HS chapter or HS heading of the product whose originating status is to be
established.
Note:
In the EU's Comprehensive Economic and Trade Agreement (CETA) with Canada,
in the EU-Japan-EPA and in the TCA, many rules of origin refer to the HS sub-
heading of the products.

However, the rules of origin do not always apply to the entire chapter or to the entire HS
heading. The description of goods in the second column of the list of sufficient working or
processing is then decisive. Columns 3 and 4 contain information on how materials without
preferential origin must be processed in order to give preferential origin to the products
mentioned in the first two columns. Figure 60 shows an example from the Regional
Convention:
Figure 60: Example of Rules of Origin
The list entry in the example in the figure refers to rotary positive displacement pumps of HS
heading 8413. The specifications in column 3 are two-part. On the one hand, the HS headings
of the non-originating materials must differ from the HS heading of the pumps manufactured.
Therefore, if a company in the EU produces rotary positive displacement pumps for export to
a state signatory to the Convention, it must not use non-originating materials of HS heading
8413.
On the other hand, the value of all non-originating materials must not exceed 40% of the ex-
works price of the pumps produced. If both requirements are met in the manufacturing
process, the pumps that are exported to a state signatory to the Convention are considered
originating products of the EU. The same rules of origin shall apply when the pumps are
manufactured in a state signatory to the Convention and exported to the EU.
Column 4 of the example also contains a specification for the sufficient processing of non-
originating materials. This specification is an alternative to the specifications in column 3. It
refers exclusively to the value of non-originating materials in the rotary positive displacement
pumps. If this proportion is not more than 25% of the ex-works price of the pumps, they are
considered originating products of the EU when exported to Iceland, Liechtenstein, or Norway
(and vice versa). The HS position of the non-originating materials used is therefore irrelevant.
For the granting of the originating status, it is sufficient that the rules of origin of one of the
two columns are fulfilled. In many list entries, only column 3 contains a text.
The set of rules in the EPA consists of only two columns. In the first column, the goods are
placed in HS chapters or HS headings. The second column contains “product-specific rules of
origin”.
In preference processing, SAP GTS determines for each product whether the specifications of
the preferential agreements are met with regard to the sufficient working or processing of
non-originating materials. Therefore, the texts in columns 3 and 4 of all list entries relevant for
your products must be “translated” into Customizing settings.

Lesson: Mapping Rules of Origin
Rules of origin are integrated into rule sets in SAP GTS. The delivery Customizing contains the
rule set PANEG (Rule Set for Pan-European Agreement (EC/EFTA/CEEC)) for mapping the
rules of origin in the agreements the EU has concluded with other countries (menu path: SAP
Global Trade Services, edition for SAP HANA → Preference Management → Define Rule Set).
The choice you make in the Rule Set Type field is decisive for the applicability of a rule set in
preference processing. This classification defines the instruments anchored in the program
code for mapping rules of origin in SAP GTS. There are two categories of rule sets:
● A Rule Set for Agreements with Non-EU-Based Concept
● B Rule Set for Agreements with EU-Based Concept
You must also assign a numbering scheme to each rule set. When checking the HS chapters
and HS headings in preference determination, SAP GTS refers to this numbering scheme. The
numbering scheme EUSTA (Commodity Code - EU) is already assigned to the rule set PANEG.
This numbering scheme is provided in delivery Customizing as a framework for the manual
maintenance or upload of CN codes (see the “Maintaining Commodity Codes and Customs
Tariffs” lesson).
In the next step, you have to assign the rule set for rules of origin in preferential agreements to
all legal regulations for these agreements (menu path: SAP Global Trade Services, edition for
SAP HANA → Preference Management → Assign Preference Agreement to Rule Set).
With the definition and assignment of a rule set, you have established the framework for the
mapping of rules of origin in the system. Depending on the indicator opted for in the Rule Set
Type field, a specific selection of preference procedures is now available. The term
“procedure” refers to the checks contained in the program code on which preference
determination is based. In preference determination, SAP GTS calculates the minimum price
of the manufactured products based on a BOM explosion (see the “Setting Up Preference
Determination” lesson).
You can find the procedure selection for mapping rules of origin in preferential agreements of
the EU in the delivery Customizing by choosing SAP Global Trade Services, edition for SAP
HANA → Preference Management → Define Rule Set Attribute for Preference Processing
(Manual) → Define Procedure for Rule Sets with EU-Based Concept.
The numbering and description of the procedures is arbitrary. The decisive factor is the
specification of the check logic of each of the procedures of a rule set by selecting one of the
predefined radio buttons, such as Heading Change. For the manual maintenance of rules of
origin in most of the preferential agreements in the EU, you can use the rule set PANEG
including the assigned procedures provided in the delivery Customizing.
Note:
To map specific rules of origin of the EPA, SAP GTS provides an additional
procedure Origin (RVC) for taking into account the regional value share of the
manufactured products.
Procedure Groups and Rule Groups

The contents of columns 3 and 4 of a list entry are represented in SAP GTS in the form of
procedure groups. A procedure group contains one or more procedures of a rule set (menu
path: SAP Global Trade Services, edition for SAP HANA → Preference Management → Define
Rule Set Attribute for Preference Processing (Manual) → Define Preference Rules - Group
Together Procedures).

The first example of the mapping of requirements for sufficient processing of non-originating
materials is the text in column 3 of figure 60. Procedure group ZPG01 was created in the
training system to “translate” the contents of this column into Customizing settings. This
procedure group consists of two procedures that are linked with a logical AND.
Figure 61: Mapping of Rules of Origin in a Procedure Group - Column 3
The first part of the text in column 3 stipulates that all non-originating materials must fall
under a different HS heading than the manufactured goods. In the PANEG rule set, the
procedure 00002 intended for mapping the specification of the first text section of column 3
has the description Heading Change.
If you want to assign several procedures to a procedure group, enter the sequence number in
the Seq.No. Proced. field. According to the rule of origin, the comparison of the commodity
codes of the non-originating materials and the manufactured product refers to the HS
heading, that is, to the first four digits of the commodity codes (indicator XXXX 4-Place
Heading in the Masking field). The heading change required in the first section of the text in
column 3 includes all non-originating materials, that is, 100%. Therefore, in the Percentage
field, the value 100 must be entered. The applicable operator is EQ Equal to.
The second section of the text of column 3 limits the value of the non-originating materials to
40% of the ex works price of the manufactured product. You always use the Third Country
procedure (procedure 00001 in the PANEG rule set) to map limits based on the value. This
procedure is assigned to procedure group ZPG01 with sequence number 2.
If you use the Third Country procedure in a procedure group, you only have to fill the
Operation Code and Percentage fields. In this procedure, the operator is always LE Smaller
than or equal to. In the Percentage field, you enter the percentage indicated in the relevant
column text, so 40 in our example. In the Third Country procedure, SAP GTS sums up the
value of all non-originating materials and calculates a rule of three. The result of this
calculation is the minimum ex works price or, in the case of the EPA, the minimum FOB price
for the manufactured product (“Threshold Value”).

Note:
The only comparison method relevant for rules assigned to the PANEG rule set is 1
Transaction Value Method. You therefore do not have to specify a comparison
method in the Comp. Method field.
Procedure group ZPG02 was created in the training system to map the contents of column 4
of the example from figure 60 in SAP GTS.
Figure 62: Mapping of Rules of Origin in a Procedure Group - Column 4
Only the Third Country procedure is assigned to procedure group ZPG02. In the Percentage
field, 25 was entered. The operator is again LE Smaller than or equal to.
In the training system and in the exercise for this lesson, you will find examples of how to use
the procedures 00003 (No Heading Change), 00004 (HS Heading), and 00005 (50:50).
As in the example in figure 60, in column 1 of the lists of sufficient working and processing,
many entries for HS chapters or headings are prefixed with “ex” (Latin for “from”). Therefore,
the rules of origin in columns 3 and 4 do not apply to all products of the respective chapter or
heading, but only to the products described in column 2. Figure 63 shows another example
from protocol 4 to the Regional Convention.

Figure 63: Condition Use Cases
The specifications in column 3 therefore do not apply to all products of HS heading 2530
(“Mineral substances, not elsewhere specified or included”), but only to the earth colors
specified in column 2. Therefore, you must ensure that SAP GTS recognizes the restriction of
the applicability of the rule of origin in column 3 to calcined or powdered earth colors. If the
description of goods in column 2 corresponds to an HS subheading or a CN code, you can
refer to the subheading or CN code when assigning the respective procedure group. However,
calcined or powdered earth colors do not have their own subheading or CN code. In the
example, the restriction contained in addition “ex” was therefore mapped using the Condition
procedure (00006) in SAP GTS.
You can also use conditions to map rules of origin that cannot be formalized in SAP GTS. In
column 3, you can repeatedly find descriptions of specific working or processing steps, such
as in the example (“Calcination or grinding of earth colours”). The goods described in
columns 1 and 2 acquire originating status by executing these working or processing steps in
the manufacturing process. Conditions can represent such steps in SAP GTS.
To use the Condition procedure, you must have defined at least one condition in Customizing
for preference processing. You create conditions within a rule set as alphanumeric keys with a
description of your choice (menu path: SAP Global Trade Services, edition for SAP
HANA → Preference Management → Define Rule Set Attribute for Preference Processing
(Manual) → Define Conditions).
To map the rule of origin in the example in figure 63 in the training system, the Condition
procedure was assigned to a separate procedure group ZPG07. After selecting the procedure
in the Pref. Procedure field, only the Addl.Condition field is ready for input.
SAP GTS cannot independently determine whether a product is an earth color, nor whether it
was produced by calcining or grinding earth colors. By assigning and activating conditions at
product level, you have to tell the system whether a description of goods applies to a product
or whether the processing of non-originating materials prescribed in column 3 takes place
during its production. To maintain conditions, use the Manage Products app (Classification
tab).

If you create several procedure groups to map the contents of a column in the list of sufficient
working or processing activities, you must group these procedure groups together in a rule
group. You can define rule groups in the same way as procedure groups within a set of rules.
In Customizing, choose SAP Global Trade Services, edition for SAP HANA → Preference
Management → Define Rule Set Attribute for Preference Processing (Manual) → Define
Preference Rules - Link Rule Groups.
In the example in figure 60, it must be taken into account in SAP GTS that the rules of origin in
columns 3 and 4 do not refer to all pumps of HS heading 8413, but only to rotary positive
displacement pumps. Since these rules of origin are often used in EU agreements, they were
mapped in the training system in a neutral form as procedure groups ZPG01 (column 3) and
ZPG02 (column 4). To map the restriction in the addition “ex” before HS heading 8413, a
separate procedure group ZPG06 was created with the Condition procedure, and the
condition ZCONDEX8413 previously defined in the rule set PANEG was assigned.
Figure 64: Conditions as Separate Procedure Groups
In the next step, the rule groups ZRG01 and ZRG02 were created to assign the procedure
groups ZPG01 and ZPG06, and ZPG02 and ZPG06 respectively. Both procedure groups were
each linked with a logical AND.
Figure 65: Group Procedure Groups into Rule Groups
To complete the rule set, you still have to link your procedure groups and rule groups with HS
chapters, headings, subheadings, or CN codes (menu path: SAP Global Trade Services,
edition for SAP HANA → Preference Management → Define Rule Set Attribute for Preference
Processing (Manual) → Assign Rules to Agreement and Classification).

You always assign rules of origin to commodity codes at the level of the legal regulation for
the respective preferential agreement, or agreement group, in connection with the rule set. In
the Number field, enter the HS chapter or HS heading from column 1 of the list of sufficient
working and processing activities. If required, you can also refer to the HS subheading or CN
code. The Strd Rule field is intended for the contents of column 3. If column 4 also contains a
rule, enter the relevant procedure group or rule group in the Alternat. Rule field. In the Periods
area, you enter the start and end of validity for the assignment. If the rules of origin for an HS
chapter or HS heading change, you can define the validity of the new rules in an additional row
in the Periods area.
As an alternative to using the rule groups ZRG01 and ZRG02, the procedure groups ZPG01
and ZPG02 are assigned to HS subheading 841360 (“Other rotary positive displacement
pumps”) in the training system, to map the restriction contained in the “ex” without the use of
a condition in the system.
Figure 66: Assignment of Procedure Groups to Commodity Codes
You can display the mapping of the rules of origin in Customizing using the Display Preference
Rules app.
Some of the EU’s preferential agreements contain a “general tolerance”. This rule is to be
applied if the non-originating component products used in the manufacture of a product do
not fulfill the conditions set in the list of working or processing. In the example, a rotary
positive displacement pump could be exported to a state signatory of the Convention as
originating in the EU, even though a non-originating component that comes under 8413 is
used in its manufacture, provided this component’s value does not exceed 10% of the ex-
works price of the pump.
A similar tolerance also applies to sets of goods consisting of originating and non-originating
products.
Table 7: Basic Rules: General Tolerance

Article 5

1. For the purposes of Article 2, products which are not wholly obtained shall considered to
be sufficiently worked or processed when the conditions set out in the list in Annex II are
fulfilled. (...)
2. Notwithstanding paragraph 1, non-originating materials which, according to the condi-

tions set out in the list in Annex II, shall not be used in the manufacture of a product may
nevertheless be used, provided that:
a. their total value does not exceed 10 % of the ex-works price of the product; (...)
Table 8: Basic Rules: Sets of Goods

Article 9
Sets, as defined in General Rule 3 of the Harmonised System, shall be regarded as originat-
ing when all component products are originating. Nevertheless, when a set is composed of
originating and non-originating products, the set as a whole shall be regarded as originating,
provided that the value of the non-originating products does not exceed 15 % of the ex-
works price of the set.
You can map these tolerances in preference processing as base rules (menu path: SAP Global
Trade Services, edition for SAP HANA → Preference Management → Define Rule Set Attribute
for Preference Processing (Manual) → Assign Base Rules to an Agreement). In the example of
the general tolerance, you first have to create a procedure group for the procedure “Third
Country” with operator LE and percentage 10 and assign this procedure group to the rule set
of the preference agreement. Select 4 General Tolerance and 3 Set of Goods respectively in
the Rule Type field.
Note:
Products representing sets of goods in SAP GTS have to be flagged accordingly
using the Manage Products app (Preference Properties tab).
If a particular rule of origin applies to the majority of the HS chapters or headings relevant to
your company, you can define the corresponding procedure group or rule group for this rule
of origin as base rule of the rule type 1 Basic Rule. If SAP GTS does not find a specific
procedure group or rule group for an HS chapter or heading in preference determination, it
applies the basic rule to the product.
LESSON SUMMARY


Unit 8
Lesson 3
Setting up Preference Determination
LESSON OVERVIEW
An important part of preference processing in SAP GTS is preference determination, that is,
the calculation of a minimum ex-works or FOB price for the produced goods based on the
rules of origin specified in each agreement. In this lesson, you learn how to set up this
calculation in SAP GTS and how to use its results in the SAP ECC or SAP S/4HANA feeder
system.
Business Example
LESSON OBJECTIVES
Preference Models and BOM Transfer

Preference determination in SAP GTS is based on the BOM of the product whose originating
status is to be determined. Therefore, you have to transfer the BOMs of all products for which
SAP GTS is to perform preference determination from the feeder system. Before you can
transfer fixed BOMs, you have to define at least one preference model in Customizing for SAP
GTS. In a preference model, you define whether SAP GTS performs preference determination
for an individual plant or for a group of plants (menu path: SAP Global Trade Services, edition
for SAP HANA → General Settings → Organizational Structures → Define Plant-Based BOM
Evaluation and → Define Cross-Plant BOM Evaluation respectively).
If you want to set up cross-plant preference determination, you first have to group your plants
into one or more plant groups. You create plant groups in connection with the definition of a
preference model for cross-plant preference determination. In cross-plant preference
determination, SAP GTS first calculates a minimum ex-works or FOB price for each plant in
the plant group. It then compares these prices and adopts the highest price for the entire
group according to the worst-case principle.

Figure 67: Preference Models for Fixed BOMs
Preference determination for configurable materials is also based on a preference model.

However, this model is anchored in the program code so that no Customizing settings are
required.
During preference determination, the SAP GTS system checks for all components of a BOM
that, due to lack of other information, it considers as non-originating materials, whether the
rules of origin that apply to the final product have been met and/or calculates the minimum
sales price of this product.
Figure 68: System Procedure for Preference Determination
You set up the transfer of BOMs to SAP GTS in the Customizing of the feeder system. In SAP
ECC, choose Sales and Distribution → Foreign Trade/Customs → SAP Global Trade Services -
Plug-In → Control Data for Transfer to SAP Global Trade Services → Control Transfer of Bills of
Product for Preference and Re-Export. In an SAP S/4HANA feeder system, choose Integration
with Other SAP Components → Integration with Governance, Risk and Compliance → SAP
Global Trade Services → Control Data for Transfer to SAP Global Trade Services → Control
Transfer of Bills of Product for Preference and Re-Export instead.

Lesson: Setting up Preference Determination
You can control the transfer of BOMs at three levels. In each case, you have to make settings
at global level (Control Settings for BOM Transfer - Global folder in the dialog structure). If
required, you can also make additional settings for individual countries (Control Settings for
Transfer - Country Level folder). If this differentiation is not sufficient, you can control the
BOM transfer at plant level (Control Settings for Transfer - Plant Level folder). The selection of
the control parameters is the same at each level.
You must always decide on the BOM category in transfer control. If you want to transfer fixed
BOMs, choose category 1 (BOM Category: Static). Category 2 (BOM Category: Configurable)
is used to transfer order-dependent BOMs of configurable materials.
In the control settings for the transfer of fixed BOMs, enter the BOM application for discrete
manufacturing or – if you are using PP-PI – for process manufacturing in the BOM Application
field. In the control settings for transferring configurable BOMs, select the BOM application
for sales and distribution.
Note:
You can define BOM applications in Customizing for production (menu path:
Production → Shop Floor Control → Operations → Bill of Material
Selection → Define Applications).
If you set an indicator for the BOM usage, the feeder system discards the BOM items that are
not flagged for this usage during the transfer to SAP GTS. For example, if you set the
Production BOM indicator, only BOM items flagged as relevant for production in the
Status/Lng Text view of the item details can be transferred to SAP GTS.
Note:
You define BOM usages in Customizing for production (menu path:
Production → Basic Data → Bill of Material → General Data → BOM
Usage → Define BOM Usages).
In transfer control, you can set up additional filters for selecting BOMs that are relevant for
transfer. The configuration of these filters is the same on all three transfer levels. For
example, if you enter individual BOM usages in the BOM Usage folder of the dialog structure,
the feeder system only transfers BOMs of these usages to SAP GTS.
Preference Indicator
Once preference determination has been completed successfully, the SAP GTS system sets a
corresponding indicator (preference indicator) in the master record of the product for which
preference determination was performed (Preference Statement tab). If a sales document or
billing document is then created in the SAP ECC or SAP S/4HANA feeder system, SAP GTS
can compare the net value of the export document or customs declaration item with the
threshold value of the product to be exported. If the net value is equal to or greater than the
threshold value, SAP GTS considers the product as being entitled to preferential duty.
If the retransfer of the preference indicator is configured for the sales order type and/or the
billing document type in Customizing, the feeder system transfers the net value of the line
items via RFC to the SAP GTS system for comparison with the threshold value of the product,
or for determination of the preference indicator if the value of the product does not matter.
Based on the information received from SAP GTS, the feeder systems sets the indicator Pref.
available (SAP ECC) or Preference (SAP S/4HANA) in the item details (Sales A tab in a sales
order, Item Detail tab in a billing document),

Figure 69: Preference Indicator in SAP GTS and Feeder System
To retransfer the preference determination results from SAP GTS to the SAP ECC feeder
system, you must implement SAP Notes 379269 and 829932. In SAP S/4HANA feeder
systems, you implement SAP Note 2476880 instead. You also have to set the Set Preference
Indicator in Feeder System indicator in the control settings for the transfer of all relevant sales
document types and billing document types.
The third prerequisite for retransferring the preferential status of a product is the information
in the feeder system about which preference agreements are active for which country
combinations in SAP GTS. The feeder system can retrieve this information using the
program /SAPSLL/PREF_AGREEMNTS_SYNC_R3 scheduled for regular background
execution. You can use the Replicate Preference Agreement Determination from SAP GTS
transaction (transaction code /SAPSLL/PREF_AGR_R3) instead.
In addition to the information on active preferential agreements, the SAP S/4HANA feeder
system requires the information contained in the preference models as to which plants are
included in preference management, This information is required for the transfer of purchase
prices for preference determination and for the transfer of document data that form the basis
of system proposals for requesting supplier’s declarations. You can transfer this information
from SAP GTS to SAP S/4HANA scheduling the program /SAPSLL/PRE_SETTINGS_DISTR
or using the Distribute Settings to S/4HANA Systems transaction (transaction code /
SAPSLL/PRE_SET_DIST).
You can use the preference indicator in the billing document item to control the printing of
proofs of origin, in particular to output an invoice declaration. Printing the commercial invoice
on the basis of the billing document is part of output control on the feeder system. In delivery
Customizing in the feeder system, for example, output type RD00 is provided for the output
of the commercial invoice. However, the standard forms for invoice printing do not contain a
text module for the invoice declaration. To ensure that the declaration is only issued for
originating products, you can make the output of a suitable text module dependent on the
preference indicator in the billing document item. The standard print programs do not check
the indicator, which means that a customer-specific adjustment is required here.

Lesson: Setting up Preference Determination
LESSON SUMMARY


Unit 8
Lesson 4
Setting up Supplier’s Declaration Management
LESSON OVERVIEW
If you purchase materials from suppliers in the EU, it can be useful to ask these suppliers to
issue a long-term supplier’s declaration for goods with preferential origin. This lesson deals
with the Customizing settings required to request, receive and issue long-term supplier’s
declarations.
Business Example
Some EU subsidiaries of the IDES group want to use SAP GTS to request supplier’s
declarations for some materials used as components in manufacturing. They also want to be
able to issue supplier’s declarations to domestic customers and customers in other Member
States.
LESSON OBJECTIVES
Managing Supplier’s Declarations in SAP GTS

In a supplier’s declaration, suppliers make a statement about the preferential origin of their
goods in accordance with the prescribed wording of Commission Implementing Regulation
(EU) 2015/2447. The requesting exporter primarily uses this declaration as a previous
document when issuing proofs of preferential origin such as a movement certificate EUR.1 or
invoice declaration.
If you resell purchased goods unchanged, the supplier's declaration you received is the basis
for issuing a supplier’s declaration to your customer. As a rule, supplier’s declarations are
used in intra-Union trade. For cumulation purposes, however, they can also be used in the
trade with certain third countries.
A long-term supplier's declaration is valid for a maximum of 24 months from the start date of
its validity period. It can also be made out retroactively for goods delivered before the making
out of the declaration for a validity period of up to 12 months prior to the date of issue. In this
case, the validity period shall end no later than six months after the date of issue.
The management of inbound long-term supplier's declarations (LTSD) in SAP GTS follows a
process predefined by the system:
● Requests (optional)
● Recording of declarations received (with or without reference to requests)
● Aggregation of all information at product level according to the worst-case principle

Figure 70: Processing Inbound Supplier’s Declarations in SAP GTS
A request based on system proposals for supplier's declarations is useful if you have not yet
entered any supplier's declaration for a particular combination of supplier and product in SAP
GTS. The SAP ECC or SAP S/4HANA feeder system provides such proposals from purchase
orders and material documents for goods receipt postings.
You activate this data transfer in the feeder system in Customizing in the control settings for
document transfer at application level MM0A for all relevant purchasing document types and
at application level MM0C for all relevant movement types. In the detail control of the
document type or movement type, set the Generate Worklist of supplier's-Based Long-Term
supplier's Declarations indicator (menu path in SAP ECC: Sales and Distribution → Foreign
Trade/Customs → SAP Global Trade Services - Plug-In → Control Data for Transfer to SAP
Global Trade Services → Configure Control Settings for Document Transfer; menu path in SAP
S/4HANA: Integration with Other SAP Components → Integration with Governance, Risk and
Compliance → SAP Global Trade Services → Control Data for Transfer to SAP Global Trade
Services → Configure Control Settings for Document Transfer).
You can decide to use only purchasing documents as the basis for requesting supplier's
declarations. However, to ensure that goods receipts from third country suppliers are not
ignored, you must also transfer material documents data.
Based on these data, SAP GTS generates proposals for requesting supplier's declarations.
You can use the Creation of LTSD Requests transaction (transaction code /SAPSLL/
LTSDREQ_1) to create requests based on these proposals. However, the /SAPSLL/
CREATE_LTSD_REQUESTS program is intended for background processing.
If you have already entered supplier's declarations in SAP GTS, you can use the annual run
instead of evaluating system proposals for the following years. You schedule the Annual
Creation of LTSD Requests program (program name /SAPSLL/CREATE_ANNUAL_LTSD_REQ)
for background processing or execute it in dialog mode using the transaction of the same
name (transaction code /SAPSLL/LTSDREQ_2). The annual run program uses the supplier's

Lesson: Setting up Supplier’s Declaration Management
declarations entered in the current fiscal year as the basis for requesting supplier's
declarations for the following year.
When issuing long-term supplier's declarations, SAP GTS primarily uses the results of
preference determination for your products. When you resell purchased goods, the system
uses the aggregated supplier's statements in the product master instead.
Types of Issue:
● With reference (based on system proposals)
● Without reference
The SAP ECC or SAP S/4HANA feeder system can transfer billing data extracts to provide the
SAP GTS system with proposals for the issue of supplier’s declarations. When issuing
supplier's declarations based on these proposals, SAP GTS evaluates shipments of goods to
the requesting customers. For each product produced in-house, the system compares the net
price of the billing item with the threshold value of the product according to preference
determination. You can only submit a supplier's declaration for products having preferential
origin status if the net price of the products was equal or superior to the threshold value in the
entire analysis period.
If you have resold purchased products to the requesting customers, SAP GTS checks the
preference status of the products. If the aggregation of the suppliers statements and the
goods receipt data has shown that a product is originating in the EU, you can issue a
supplier's declaration for this product in SAP GTS.
Figure 71: Issuing Supplier’s Declarations to Customers
To transfer billing data from the feeder system as a basis of proposals for outbound supplier’s
declarations, set the Generate Worklist of Long-Term Vendor Declarations for Customers’
Purpose indicator for all relevant billing document types in Customizing (menu path in SAP
ECC: Sales and Distribution → Foreign Trade/Customs → SAP Global Trade Services - Plug-
In → Control Data for Transfer to SAP Global Trade Services → Configure Control Settings for
Document Transfer; menu path in SAP S/4HANA: Integration with Other SAP

Settings for Document Transfer).
Documents of Origin
In SAP GTS, supplier’s declarations are documents of origin. These documents store the
essential information contained in the actual (paper) declaration. Documents of origin can be
created with or without reference to requests.
Before you can create supplier’s declarations in your SAP GTS system, you first have to
define at least one document of origin type as a framework for the maintenance of individual
documents (menu path in Customizing: SAP Global Trade Services, edition for SAP
HANA → Preference Management → Supplier's Declarations → Documents of Origin → Define
Documents of Origin).
On document of origin type level, you map the requirements of Article 62 (2) of Implementing
Regulation (EU) 2015/2447 (referred to as UCC IA in figure 72) with regard to the validity
period of long-term supplier’s declarations. In the Assign Country Groups folder in the dialog
structure of the Define Long-Term Supplier’s Declaration Types view, you enter a country
group for the EU. In the Assign Preference Agreement folder, you enter all relevant preferential
agreements that the EU has concluded with third countries.
You can also map the origin declaration defined in the protocol on rules of origin and origin
procedures to the CETA, as well as the statement on origin defined in the EU-Japan EPA in the
form of documents of origin types. Based on these definitions, you can request, receive, and
issue origin declarations and statements on origin using your SAP GTS system.
Figure 72: Documents of Origin Types (Examples)
You can influence the request, issue, and subsequent management of supplier's declarations
within certain limits in Customizing for Preference Management (menu path: SAP Global
Trade Services, edition for SAP HANA → Preference Management → Supplier's
Declarations → Define Settings for the LTSD Process).
If the majority of vendors transferred from the feeder system are goods suppliers, it makes
sense to set the Request All Suppliers indicator. All business partners in the business partner
role “Customs Bus.Partner (Sup)” (SLLCPS) located in the EU are then relevant for
requesting supplier's declarations. All vendors located in third countries are considered
relevant for aggregating goods receipt. You must therefore explicitly flag goods suppliers as
not relevant for requests or aggregation in the Manage Preference Properties - Suppliers app.
Similar settings are required for customers (Issue to All Customers indicator).

Lesson: Setting up Supplier’s Declaration Management
In the Goods Retention Period field, you enter the average retention period of purchased
products in your feeder system stocks. For example, purchased products usually leave the
warehouse no later than 90 days after the goods receipt posting – either to supply your own
production with components or to deliver to customers. The product retention period is a
value based on past experience that can be exceeded or fallen short of in individual cases.
SAP GTS uses this value to retain the originating status of a product even after the supplier’s
declarations entered in the system have expired. They remain valid in the system until the
first new goods receipt or until a new supplier’s declaration is received. If there are still
remaining stocks after the validity period of the supplier’s declarations has expired, you can
continue to use or sell these as originating products until the end of the respective product
retention period, as long as no new goods receipt is posted in the feeder system.
In the Manage Preference Properties - Suppliers app, you can adjust the retention period of a
product individually for individual suppliers.
The basis for issuing the text of the supplier's declaration with product lists and a letter is the
assignment of the appropriate action profiles and text modules to the administrative unit in
Customizing (menu path: SAP Global Trade Services, edition for SAP HANA → Preference
Management → Supplier’s Declarations → Output Management → Assign Action Profiles and
→ Assign Text Modules). Delivery Customizing for SAP GTS provides two action profiles for
long-term supplier’s declarations:
● LLS_PRE_LTSD_EU_REQUEST Request Long-Term Supplier's Declaration (EU)
● LLS_PRE_LTSD_EU_ISSUE Issue Long-Term Supplier's Declaration (EU)
Note:
At the time of publication of this handbook, SAP GTS did not provide action
profiles for the request or issue of origin declarations and statements on origin
respectively.
The communication medium (mail or e-mail) depends on the administrative unit requesting
or issuing the supplier’s declarations.
To use the communication mode e-mail, you must create the recipients of the e-mails as
business partners of the type “Person” in the business partner role “Respons. for Preference”
(BUP008) and enter the e-mail addresses in the master data of these business partners. With
the relationship category BUR008 (for the employee of a supplier) or SLLBUR (for the
employee of a customer, description in both cases Is the Employee Responsible for
Preference), you can link the business partner of the e-mail recipient with the business
partner of the supplier or customer using the Relationships button.
Revocation of Supplier’s Declarations

The Implementing Regulation (EU) 2015/2447 in article 62 (3) obliges the supplier to inform
all affected economic operators immediately if the long-term supplier's declaration is invalid
for one or more consignment(s) of goods. For example, if you have sold a product produced
in-house for which you have issued a long-term supplier's declaration to the recipient at a
price below the threshold value, you have to revoke the supplier's declaration immediately
because the product has lost its originating status.
On the other hand, you may have received a supplier's declaration for goods with preferential
origin for a trading good after a longer waiting time. You now want to inform your customers
of this positive change in a new supplier's declaration. Another possible reason for revoking or

re-issuing a supplier's declaration is a BOM change that leads to an increase or decrease in

the threshold value in preference determination.
SAP GTS enables the largely automated revocation or re-issue of supplier's declarations that
have already been issued and are still valid scheduling the Processing of Triggers for the
Creation of Reissue Reasons program (/SAPSLL/PROCESS_RIR_TRIGGERS).
System proposals for the revocation or re-issue of supplier's declarations are created in
different ways: The net price of a billing item falls below the threshold value of the product in
the validity period of the supplier's declaration for this product. Changes to the BOM, the
procurement type, or the value of the components change the threshold value of a product in
a new preference determination in such a way that the supplier's declarations issued for the
product no longer apply. A change in the preference status of a product after a supplier's
declaration has been issued also results in the creation of a re-issue reason. Finally, manual
processing of a product in the Preference Statement view triggers the creation of a system
proposal for the re-issue of all supplier’s declarations concerned.
LESSON SUMMARY

Unit 8
Learning Assessment
1. Each preferential agreement has to be mapped individually in the form of a legal

regulation.
X True
X False
2. Which of the procedures below can be used to calculate a minimum ex-works price for the
manufactured product?
X A 50:50
X B Third Country
X C Heading Change
X D No Heading Change
3. You can use up to three preference models for preference processing in SAP GTS.
X True
X False
4. What is the maximum validity of a long-term supplier’s declaration?

X A 6 months
X B 12 months
X C 24 months
X D 36 months

Unit 8
1. Each preferential agreement has to be mapped individually in the form of a legal

regulation.
X True
X False
Correct. You can create individual legal regulations for each of the preferential
agreements relevant to your company’s processes. However, it might make more sense to
group agreements with identical rules of origin into one legal regulation.
2. Which of the procedures below can be used to calculate a minimum ex-works price for the
manufactured product?
X A 50:50
X B Third Country
X C Heading Change
X D No Heading Change
You can use the “50:50” procedure, the “Third Country” procedure and the “No Heading
Change” procedure to calculate a minimum ex-works price for the manufactured product.
3. You can use up to three preference models for preference processing in SAP GTS.
X True
X False
Correct. SAP GTS provides for three preference models: Plant-based preference model,
cross-plant preference model, and preference model for configurable BOMs.

4. What is the maximum validity of a long-term supplier’s declaration?

X A 6 months
X B 12 months
X C 24 months
X D 36 months
Correct. The maximum validity of a long-term supplier’s declaration is 24 months.


UNIT 9 Intrastat Declarations
Lesson 1
Submitting Intrastat Declarations 181
Lesson 2
Configuring Data Selection and Issue 185
UNIT OBJECTIVES
● Explain Intrastat declaration processing

● Configure data selection for Intrastat declarations

Unit 9: Intrastat Declarations

Unit 9
Lesson 1
Submitting Intrastat Declarations
LESSON OVERVIEW
This lessons gives an overview of the processing of Intrastat declarations in the SAP ECC or
SAP S/4HANA feeder system and SAP GTS.
Business Example
IDES Germany regularly delivers goods to other Member States and purchases goods from
other Member States. In the future, the company intends to generate the monthly Intrastat
declarations from SAP GTS.
LESSON OBJECTIVES
Data to be Reported
The EU Member States form the European Single Market in which goods, services, people,
and capital may move freely. In the days before the establishment of the European Single
Market, customs declarations had to be submitted for goods movements between Member
States. These customs declarations were also used for the retrieval of statistical data on
intra-Community trade. Since these data are of particular importance for trade policy, the EU
established the permanent statistical retrieval system Intrastat as a replacement for the intra-
Community customs declarations that had ceased to exist.
Note:
In the European Single Market, supplies from another Member State are referred
to as receipts (and not imports). Supplies to another Member States are referred
to as dispatches (and not exports).
With limited exceptions, Intrastat declarations only concern the movements of Union goods
between the Member States. Receipts and dispatches are to be declared separately.
As a rule, only companies are required to submit information. A requirement to submit
information only arises when receipts and dispatches in the previous year have exceeded a
reporting threshold to be set by the national authorities. The reporting period or the reference
period is generally the calendar month of the dispatch or the receipt of the goods.
The following data must be provided in an Intrastat declaration:
Basic Data to be Reported (Selection)
● Provider of information

● Identification number of provider of information

● Description of goods and commodity code as per the CN
● Receiving and dispatching Member State
● Country of origin
● Region of origin or region of destination
● Nature of transaction
● Net mass in kilograms and (if applicable) supplementary unit as per the CN
● Invoice amount without value added tax
● Statistical value, if applicable
The Member States may also request information on the terms of delivery (Incoterms), the
mode of transport, and the statistical procedure, among others.
Unlike other Member States, Italy also collects data on the supply of services to or from other
Member States as a part of the Intrastat declaration. To report the supply of services, the
providers of information have to use codes from the nomenclature in the Annex to Council
Regulation (EC) No. 451/2008 establishing a new statistical classification of products by
activity (CPA). This classification is also referred to as CPA 2008.
You can submit Intrastat declarations for services in Italy using SAP S/4HANA. SAP S/
4HANA for international trade provides a numbering scheme and a numbering scheme
content for the maintenance of CPA codes and the classification of products that represent
Intrastat-relevant services.
Issue of Intrastat Declarations

In the SAP GTS system and in the SAP S/4HANA feeder system, you have to define a provider
of information for each company code of the feeder system that submits Intrastat
declarations. Providers of information are master data which you create, change, and display
using the Manage Providers of Information app in the SAP Fiori launchpad of both the SAP
GTS system and the SAP S/4HANA feeder system. In SAP S/HANA, the provider of
information has to be specified in the programs that select data for Intrastat declarations.
SAP ECC uses the company code for data selection.
SAP GTS, edition for SAP HANA, introduces a new business partner role for the provider of
information (SLLPOI). You can assign this role to a business partner representing a company
code in addition to the “Foreign Trade Organization”(SLLFTO) role. Tax numbers are copied
from the business partner's master record to the master data of the provider of information.
In the master record of the provider of information, you maintain general data, such as the
exact address, the value added tax registration number, and the declaration currency as well
as information on the file format of the declaration (for example, ASCII or XML). The provider
of information has no direct connection to the company code of the feeder system it
represents.

Lesson: Submitting Intrastat Declarations
Figure 73: Provider of Information
After successful document data selection in the feeder system and data transfer to SAP GTS,
you can process the data of the Intrastat declarations in SAP GTS using the Manage Intrastat
Declarations app. If mandatory data are missing in a line item of the declaration, the system
issues an incompleteness log in the line item’s details. You can add missing data or, if
required, change data.
After completing the data, you can release the Intrastat declaration. In the next step, you
create a file containing the data of the declaration and save the file on a computer in your
company’s network. The system automatically formats the data according to the file format
specified in the master record of the provider of information.
LESSON SUMMARY


Unit 9
Lesson 2
Configuring Data Selection and Issue
LESSON OVERVIEW
The first part of this lesson deals with the selection of feeder system documents to be
extracted for Intrastat declarations. This lesson further explains how to maintain the official
codes to be used in Intrastat declarations.
Business Example
IDES Germany regularly delivers goods to other Member States and purchases goods from
other Member States. In the future, the company intends to generate the monthly Intrastat
declarations from SAP GTS.
LESSON OBJECTIVES
Data Selection in the Feeder System

Unlike in Compliance Management and Customs Management, there is no document
replication for Intrastat in SAP GTS. The declaration-relevant data extracted from the feeder
system are instead stored on the database in SAP GTS. The system automatically retrieves
these data for the Intrastat declaration.
The SAP ECC feeder system uses the following programs to extract document data for the
transfer to SAP GTS for Intrastat declarations. These programs collect the relevant data from
purchasing documents and billing documents respectively:
● Intrastat: Transfer Documents for Receipts (transaction code /SAPSLL/IS_MM)
● Intrastat: Transfer Documents for MM Returns and MM Credit Memos (transaction code /
SAPSLL/IS_MM_RET)
● Intrastat: Transfer Documents for Dispatches (transaction code /SAPSLL/IS_SD)
● Intrastat: Transfer Documents for Intercompany Billing (SD) (transaction code /SAPSLL/
IS_SD_IB)
In an SAP S/4HANA feeder system, there are only two selection programs:
● Intrastat: Transfer Receipts and Returns to Supplier To SAP GTS (transaction code /
SAPSLL/IS_MM)
● Intrastat: Transfer Dispatches and Customer Returns to SAP GTS (transaction code /
SAPSLL/IS_SD)
All selection programs are intended for background processing.

As a rule, Intrastat declarations of receipts are based on purchasing documents, whereas
Intrastat declarations of dispatches are based on billing documents. However, in case of

returns to vendors in another Member State, the feeder system selects the relevant data for
reporting the corresponding dispatches based on the purchasing documents for the previous
receipts. In intra-Union intercompany sales, the feeder system selects the data for declaring
both the dispatch from the Member State of departure and the receipt in the Member State of
destination from the intercompany billing documents.
For reports of receipts, the feeder system selects purchase orders for which the goods
receipt has been posted in the reference period, that is, the calendar month of the Intrastat
declaration. If the incoming invoice is not posted in the month of the goods receipt, the
system selects the purchase order in the following month, whether the invoice has then been
posted or not. It is also possible to have the system select only purchase orders for which the
incoming invoice has been posted in accounting. The declaration month is thus always the
month of the invoice posting. Instead, the system can also ignore the incoming invoice in data
selection. Purchase orders are thus always selected in the month of the goods receipt
posting.
For report of dispatches, the system selects billing documents in the month of their billing
date. You can opt for the goods issue date of the outbound delivery instead.
The decision on the selection logic is always country-specific. To set up data selection in the
Customizing for SAP ECC, choose Sales and Distribution → Foreign Trade/
Customs → Periodic Declarations → Control Data → Data Selection Control → Data Selection
Control. Make new entries for each relevant Member State and the direction of the goods
movement. In Customizing for SAP S/4HANA, choose Governance, Risk and
Compliance → International Trade → Intrastat → Data Selection → Define Data Selection
Control for Sales and → Define Data Selection Control for Purchasing respectively.
Figure 74: Data Selection for Intrastat Declarations
In some areas belonging to the territory of EU, the Directive 2006/112/EC on the common
system of value added tax (“VAT Directive”) does not apply. The movement of goods between
the Member States and these areas is not subject to the Intrastat declaration. This exclusion
from Intrastat declarations applies to the following areas:

Lesson: Configuring Data Selection and Issue
● Canary Islands (Spain)

● Overseas departments (France)
● Mount Athos (Greece)
● Åland Islands (Finland)
On the other hand, goods movements between the Member States and Northern Ireland are
still subject to the Intrastat declaration although the United Kingdom left the EU with effect
from 1 January 2021.
In SAP ECC and SAP S/4HANA, you can exclude most of these areas from data selection for
Intrastat declarations or — as in the case of Northern Ireland — include them in the selection
using their respective region codes. In the Customizing for SAP ECC, choose Sales and
Distribution → Foreign Trade/Customs → Periodic Declarations → Control Data → Special
Rule Country / Region. In SAP S/4HANA, choose Governance, Risk and
Compliance → International Trade → Intrastat → Data Selection → Define Exceptions for
Inclusion and Exclusion of Countries and Regions instead.
Since 1963, Monaco is part of the customs territory of the EU. For VAT purposes, Monaco is
considered as French territory. Therefore, the movement of goods between the Member
States and Monaco is subject to the Intrastat declaration. Deliveries from Belgium to Monaco,
for example, have to be reported as dispatches to France. To enable the system to select
documents for business partners in Monaco for reporting receipts from and dispatches to
France, you have to assign Monaco to France in the Customizing for Intrastat declarations.
In an SAP S/4HANA feeder system, the settings are provided in delivery Customizing (menu
path: Governance, Risk and Compliance → International Trade → Intrastat → Basic
Data → Partner Countries → Define Exceptions for Conversion of Partner Countries). In the
Customizing for SAP ECC, chooseSales and Distribution → Foreign Trade/
Customs → Periodic Declarations → Control Data → Special Rule Country / Region, set the
Convert Country indicator and enter FR in the Altern.cntry key field in the entry for country
code MC.
In both SAP ECC and SAP S/4HANA, you can exclude sales document item categories from
data selection for Intrastat declarations, for example third-party items (item category TAS).
To do so in SAP ECC, you first have to define an exclusion indicator. You then assign this
indicator to all relevant item categories (menu path in Customizing: Sales and
Distribution → Foreign Trade/Customs → Periodic Declarations → Control Data → Inclusion
and Exclusion Indicators → Define Exclusion/Inclusion Indicators and → Assign to Item
Categories for SD Sales Orders or → Assign to Item Categories for SD Deliveries).
In SAP S/4HANA, you just enter the relevant item categories in the Exclusion of Sales
Document Item Category view (menu path in Customizing: Governance, Risk and
Compliance → International Trade → Intrastat → Data Selection → Define Exclusion of Sales
Document Item Categories). You can exclude item categories for services in the Define Sales
Document Item Categories for Services view (menu path: Governance, Risk and
Compliance → International Trade → Intrastat → Data Selection → Define Sales Document
Item Category for Services).

Note:
Unlike in SAP ECC, you cannot further restrict the search for Intrastat-relevant
documents in the selection screens for the selection programs in SAP S/4HANA.
These selection screens only contain fields for the provider of information, the
declaration year, and the declaration month.
Definition of Data to be Reported

Numbering schemes represent nomenclatures for different purposes in international trade.
Together with numbering scheme contents, they serve as frameworks for the manual
maintenance or the upload of different types of codes, and for the assignment of these codes
to products (classification).
In Intrastat declarations, you have to specify the goods received from or dispatched to
another Member State using the appropriate CN codes. You learned about this nomenclature
in the “Maintaining Commodity Codes and Customs Tariffs” lesson. If your company uses
SAP GTS for submitting export declarations or transit declaration to customs offices in the
EU, the CN has already been mapped for Customs Management in the form of the numbering
scheme EUSTA and the numbering scheme content EUSTA_CT (or customer-specific
copies).
Figure 75: Numbering Scheme and Content for the CN
In delivery Customizing for SAP GTS, you can find the legal regulation ENSEU (Numbering
System - European Union) provided for Intrastat declarations (menu path: SAP Global Trade
Services, edition for SAP HANA → General Settings → Legal Regulations → Define Legal
Regulation). This legal regulation is already activated for most of the Member States (menu
path: SAP Global Trade Services, edition for SAP HANA → General Settings → Legal
Regulations → Activate Legal Regulations at Country/Region Group Level and SAP Global
Trade Services, edition for SAP HANA → Intrastat → Activate Legal Regulations).

Lesson: Configuring Data Selection and Issue
The numbering scheme EUSTA is assigned to the legal regulation ENSEU, so that the
classification carried out for customs processing can also be used for Intrastat declarations
and vice versa (menu path: SAP Global Trade Services, edition for SAP HANA → General
Settings → Numbering Schemes → Assign Numbering Schemes to Legal Regulations, Assign
Scheme for Commodity Codes folder).
In SAP GTS, most of the codes to be used in Intrastat declarations are predefined in the
delivery Customizing. However, you should check these codes regularly and update them, if
necessary (menu path: SAP Global Trade Services, edition for SAP HANA → Intrastat → Basic
Data). Some of the codes are identical in all Member States, others are specific to individual
Member States.
The following lists give an overview of the codes applied in all Member States:
Information to be Provided in Coded Form
● Country
● Region
● Nature of transaction (business transaction type)
● Procedure
● Mode of transport at the border
● Incoterms
The following codes supplied in the delivery Customizing are required only for Intrastat
declarations in the Member States specified in brackets:
● Movement (Czech Republic)
● Port/airport (Portugal, Spain)
● Collection center (Italy, Poland)
The country codes predefined in delivery Customizing for SAP GTS are required for indicating
the reporting country, the respective partner countries of departure or destination, and the
country of origin. The codes to be used in Intrastat declarations may differ from the ISO 3166
country codes defined in database table T005 (Countries).
Something similar applies to the region codes stored in database table T005S (Taxes: Region
(Province) Key). If the region codes to be used in Intrastat declarations differ from the region
codes defined in database table T005S, a conversion is required. The delivery Customizing
for SAP GTS therefore provides the necessary code assignments in the Define Exceptions for
Conversion of Regions view (menu path: SAP Global Trade Services, edition for SAP
HANA → Intrastat → Basic Data → Regions → Define Exceptions for Conversion of Regions).
LESSON SUMMARY


Unit 9
Learning Assessment
1. Which of the data listed below have to be included in an Intrastat declaration?

X A Product description of the goods delivered
X B Goods quantity in gross mass
X C Commodity codes of the goods as per the CN
X D Total amount invoiced value added tax
2. Which categories of documents does the feeder system select for Intrastat reporting?
X A Outbound deliveries
X B Purchase orders
X C Inbound deliveries
X D Billing documents

Unit 9
1. Which of the data listed below have to be included in an Intrastat declaration?

X A Product description of the goods delivered
X B Goods quantity in gross mass
X C Commodity codes of the goods as per the CN
X D Total amount invoiced value added tax
Correct. Product description and commodity codes as per the CN of the goods delivered
have to be included in the Intrastat declaration. The goods quantity has to be specified in
net mass and the total amount invoice without value added tax.
2. Which categories of documents does the feeder system select for Intrastat reporting?
X A Outbound deliveries
X B Purchase orders
X C Inbound deliveries
X D Billing documents
Correct. The feeder system selects purchase orders and billing documents for Intrastat
reporting.

Gts200 en Col18

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gts200 en Col18

Uploaded by

Copyright:

Available Formats

GTS200

Configuring SAP Global Trade

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

American English is the standard used in this handbook.

This information is displayed in the instructor’s presentation

Related or Additional Information

User interface control Example text

Window title Example text

© Copyright. All rights reserved. iii

vii Course Overview

1 Unit 1: Basic Settings

3 Lesson: Setting up the Transfer of Master Data and Documents

21 Unit 2: Legal Regulations in Compliance Management

23 Lesson: Mapping Legal Norms in SAP GTS

35 Unit 3: Embargo Check

37 Lesson: Maintaining Embargoes and Check Settings

49 Unit 4: Sanctioned Party List Screening

51 Lesson: Managing Sanctioned Party Lists

67 Unit 5: Legal Control

69 Lesson: Maintaining Goods Lists and Classifying Products

95 Unit 6: Legal Regulations and Nomenclatures in Customs Management

97 Lesson: Activating Legal Regulations for Customs Management

113 Unit 7: Additional Settings for Customs Management

115 Lesson: Setting up the Integration into Feeder System Processes

147 Unit 8: Preference Processing

149 Lesson: Mapping Preferential Agreements in SAP GTS

© Copyright. All rights reserved. v

181 Lesson: Submitting Intrastat Declarations

vi © Copyright. All rights reserved.

© Copyright. All rights reserved. vii

© Copyright. All rights reserved. 1

2 © Copyright. All rights reserved.

Master Data Transfer

© Copyright. All rights reserved. 3

Figure 1: Master Data Transfer

4 © Copyright. All rights reserved.

Figure 2: Change Pointers

© Copyright. All rights reserved. 5

Figure 3: Reduced Message Types for Master Data Transfer

4. To create, change or display a reduced message type, choose Create , Change , or

6 © Copyright. All rights reserved.

Figure 4: Transfer of New and Changed Master Data

© Copyright. All rights reserved. 7

Figure 5: Document Transfer Overview

Figure 6: Settings on Document Type Level in SAP ECC (Example)

8 © Copyright. All rights reserved.

© Copyright. All rights reserved. 9

10 © Copyright. All rights reserved.

Mapping Settings in SAP GTS

© Copyright. All rights reserved. 11

Figure 7: Organizational Units and Their Mapping in SAP GTS

12 © Copyright. All rights reserved.

Figure 8: Partner Functions

© Copyright. All rights reserved. 13

Figure 9: Partner Groupings

14 © Copyright. All rights reserved.

Figure 10: Assign Document Types

© Copyright. All rights reserved. 15

Figure 11: Assign Item Categories

16 © Copyright. All rights reserved.

© Copyright. All rights reserved. 17

18 © Copyright. All rights reserved.

Learning Assessment - Answers

© Copyright. All rights reserved. 19