Sap GTS 2023

User Guide | PUBLIC
2022-11-11
SAP Global Trade Services, edition for SAP HANA

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

Content
1 SAP Global Trade Services, edition for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Products and Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Manage Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Analyze Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Manage Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Customs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Legal Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
PGA Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
NCLO Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Master Data - Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Commodity Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Tariff Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Duty Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Measures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Control Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Licence Relevance Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
PGA Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Additional Tariff Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
FDA Product Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Excise Duty Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Number Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Compliance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Quick Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Compliance Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Business Partner Screening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.2 Legal Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
License Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Simulations of Compliance Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Legal Control - Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Legal Control - Re-Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
ITAR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Embargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 PUBLIC Content
Embargo Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4 Sanctioned Party Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Audit Trails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Master Data - Sanctioned Party Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Business Partner and Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4 Compliance Screening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Quick Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Compliance Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Business Partner Screening. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Sanctioned Party Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Audit Trails. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Master Data - Sanctioned Party List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
4.3 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
5 Customs Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1 Customs - Export. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Customs Broker. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.2 Customs- Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Ending of Transit Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Periodic Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Presentations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Pre-Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Special Customs Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.4 Customs EMCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Change Administrative Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Display Outbound Activities - Excise Duty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Monitor Confirmations - Administrative Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Create Administrative Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Display Outbound Documents - Administrative Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Display Inbound Documents: Administrative Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Display Inbound Activities - Excise Duty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Display Administrative Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Create Administrative Document with Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
6 Preference Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Content PUBLIC 3
6.1 Supplier’s Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Inbound Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Outbound Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
6.2 Preference Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Calculation - Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Calculation - Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
6.3 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Master Data - Preference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7 Intrastat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
7.1 Managing Providers of Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84
7.2 Managing Intrastat Declarations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.3 Manage Business Partners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4 PUBLIC Content
1 SAP Global Trade Services, edition for
SAP HANA
Product Information
Product SAP Global Trade Services, edition for SAP HANA
Version 2020 SP01
Based On Required Product Versions:
• SAP S/4HANA FOUNDATION 2020

• SAP FIORI FRONT-END SERVER
Documentation Published September 2021
Use
SAP Global Trade Services, edition for SAP HANA (SAP GTS, edition for SAP HANA) helps companies better
manage international trade operations, ensure ongoing trade compliance, and optimize the cross-border
supply chain.
The solution delivers automation and comprehensive functionality to speed trade functions and maximize
performance. With direct integration throughout the supply chain, customers can expect reduced costs, fewer
trade penalties and fines, and faster customs clearance, both outbound and inbound. The extensive functions
include the following:
• Products and Classification

• Compliance Management
• Customs Management
• Preference Management
• Intrastat
 Note
The term SAP GTS, edition for SAP HANA is used synonymously for the product and the system.

SAP Global Trade Services, edition for SAP HANA PUBLIC 5
2 Products and Classification
Classification describes the organization of goods into a nomenclature according to customs and foreign trade
law. The nomenclature lists all goods that appear as commercial goods in international traffic. This means that
each product can be uniquely assigned to a foreign trade classification number (FTC number).
In SAP Global Trade Services, edition for SAP HANA, for example, the following FTC numbers are used in the
application areas listed:
• Compliance Management
• Tariff numbers
• Commodity codes
• Control classes
• Customs Management
• Tariff numbers
• Commodity codes
• Preference Management
• Commodity codes
• Intrastat
• Commodity codes
Prerequisites
You have configured the products and classification in accordance with the information in the Configuration
Guide for SAP Global Trade Services, edition for SAP HANA.
For more information, see the Configuration Guide for SAP Global Trade Services, edition for SAP HANA.
2.1 Product
2.1.1 Manage Products

6 PUBLIC Products and Classification
2.1.1.1 Manage Products
With this app, classification specialists can manage products.
2.1.1.2 Manage Customs Commercial Descriptions
With this app, classification specialists can manage customs commercial descriptions.
2.1.1.3 Compare Customs Commercial Descriptions
With this app, classification specialists can compare customs commercial descriptions.
2.1.2 Analyze Products
2.1.2.1 Display Products
With this app, classification specialists can display products.
2.1.2.2 Display Product Catalog Based on Customs

Declaration
With this app, classification specialists can display a product catalog based on the customs declaration.
2.1.2.3 Display Products with Authority Codes
With this app, classification specialists can display products with authority codes.

Products and Classification PUBLIC 7
2.1.2.3.1 Display Classified Products
With this app, classification specialists can view classified products in legal control.
2.1.2.3.2 Display Products - Re-Export
With this app, classification specialists can display products in re-exports.
2.1.3 Manage Worklist
2.1.3.1 Manage Worklist for Products
With this app, classification specialists can manage the worklist for products.
2.1.3.2 Manage Products from Worklist
With this app, classification specialists can manage the products from the worklist.
2.2 Classification
2.2.1 Customs

2.2.1.1 Reclassify Products Manually
With this app, classification specialists can reclassify products manually.
2.2.1.2 Reclassify Products XML-Based
With this app, classification specialists can reclassify products XLM-based.
2.2.1.3 Classify Products
With this app, classification specialists can classify products.
2.2.1.4 Delete Product Classification
With this app, classification specialists can delete a product classification.
2.2.1.5 Check Product Classification
With this app, classification specialists can check a product classification.
2.2.2 Legal Control
2.2.2.1 Reclassify Products Manually - Legal Control
With this app, classification specialists can reclassify products in legal control.

2.2.2.2 Reclassify Products from XML File
With this app, classification specialists can reclassify products from an XML file.
2.2.2.3 Classify Products - Legal Control
With this app, classification specialists can classify products in legal control.
2.2.2.4 Delete Products - Legal Control
With this app, classification specialists can delete products in legal control.
2.2.2.5 Check Product Classification
With this app, classification specialists can check a product classification.
2.2.3 PGA Codes
2.2.3.1 Update Products - Authorization Codes
With this app, classification specialists can update authorization codes for products.
2.2.3.2 Change PGA Data for Products
With this app, classification specialists can change PGA data of products.

2.2.3.3 Assign PGA Code to Products
With this app, classification specialists can assign PGA codes to products.
2.2.4 NCLO Codes
2.2.4.1 Assign NCLO Codes to Products
With this app, classification specialists can assign NCLO codes to products.
2.2.4.2 Change NCLO Codes for Products
With this app, classification specialists can change NCLO code of products.
2.3 Master Data - Classification
2.3.1 Commodity Codes
2.3.1.1 Manage Commodity Codes
With this app, classification specialists can manage commodity codes.

2.3.1.2 Display Upload Logs Commodity Codes
With this app, classification specialists can display upload logs of commodity codes.
2.3.1.3 Upload Commodity Codes
With this app, classification specialists can upload commodity codes.
2.3.2 Tariff Numbers
2.3.2.1 Manage Tariff Numbers
With this app, classification specialists can manage tariff numbers.
2.3.2.2 Display Upload Logs Tariff Numbers
With this app, classification specialists can display upload logs of tariff numbers.
2.3.2.3 Upload Tariff Numbers
With this app, classification specialists can upload tariff numbers.
2.3.2.4 Manage Tariff Number Attributes
With this app, classification specialists can manage tariff number attributes.

2.3.3 Duty Rates
2.3.3.1 Manage Duty Rates
With this app, classification specialists can manage duty rates.
2.3.3.2 Upload Duty Rates
With this app, classification specialists can upload duty rates.
2.3.3.3 Display Upload Logs Customs Duty Rates
With this app, classification specialists can display upload logs of customs duty rates.
2.3.3.4 Determine Duty Rates for Tariff No.
With this app, classification specialists can determine duty rates for tariff numbers.
2.3.4 Measures
2.3.4.1 Edit Properties for a Measure Type
With this app , classification specialists can edit properties for a measure type.

2.3.4.2 Upload Measures
With this app, classification specialists can upload measures.
2.3.4.3 Display Upload Logs Measures
With this app, classification specialists can display upload logs of measures.
2.3.5 Control Classes
2.3.5.1 Manage Control Classes
With this app, classification specialists can manage control classes.
2.3.5.2 Manage Control Group for Products
With this app, classification specialists can manage control groups for products.
2.3.5.3 Manage Peculiarity Codes
With this app, classification specialists can manage peculiarity codes.
2.3.5.4 Upload Control Classes
With this app, classification specialists can upload control classes.

2.3.5.5 Display Upload Logs Control Classes
With this app, classification specialists can display upload logs of control classes.
2.3.6 Licence Relevance Codes
2.3.6.1 Manage License Relevance Codes
With this app, classification specialists can manage license relevance codes.
2.3.6.2 Upload License Relevance Codes
With this app, classification specialists can upload license relevance codes.
2.3.6.3 Display Upload Logs - License Relevance Codes
With this app, classification specialists can display upload logs of license relevance codes.
2.3.7 PGA Codes
2.3.7.1 Manage Authority Codes
With this app, classification specialists can manage authority codes.
2.3.8 Additional Tariff Numbers

2.3.8.1 Manage Additional Tariff Numbers
With this app, classification specialists can manage additional tariff numbers.
2.3.8.2 Upload Additional Tariff Numbers
With this app, classification specialists can upload additional tariff numbers.
2.3.8.3 Display Upload Logs Additional Tariff Numbers
With this app, classification specialists can display upload logs of additional tariff numbers.
2.3.9 FDA Product Codes
2.3.9.1 Manage FDA Product Codes
With this app, classification specialists can manage FDA product codes.
2.3.9.2 Upload FDA Product Codes
With this app, classification specialists can upload FDA product codes.
2.3.9.3 Display Upload Logs FDA Product Codes
With this app, classification specialists can display upload logs of FDA product codes.

2.3.10 Excise Duty Codes
2.3.10.1 Manage Excise Duty Codes
With this app, classification specialists can manage excise duty codes.
2.3.11 Number Sets
2.3.11.1 Manage Number Sets
With this app, classification specialists can manage number sets.

3 Compliance Management
Compliance Management helps ensure your compliance with international trade regulations in three main
areas:
• Sanctioned Party List Screening

• Legal control - export (including embargo checks and licenses)
• Legal control - import (including embargo checks and licenses)
Compliance Management helps you rationalize your extended logistics chain and automate the complicated
processes that are involved with international trade compliance issues, a primary prerequisite for successful
international trading activities. This minimizes the risk of having to pay penalties and fines. Your company can
considerably improve their sales by global sourcing and selling initiatives and owing to the higher customer
satisfaction the competitiveness of your organization can be facilitated.
 Note
To ensure end-to-end documentation of transactions for your own purposes and official controls, you can
archive objects from Compliance Management.
For more information, see Administration Guide for SAP Global Trade Services, edition for SAP HANA under
Data Archiving.
Prerequisites
You have configured Compliance Management in accordance with the information in the Configuration Guide
for SAP Global Trade Services, edition for SAP HANA.
Process
Sanctioned Party List Screening

18 PUBLIC Compliance Management
1. You create a sales document or document for materials management in the feeder system.
2. SAP GTS, edition for SAP HANA starts sanctioned party list screening automatically. Based on the rules
that you configured during implementation, the address data in the business documents is checked
against the available sanctioned party lists in SAP GTS, edition for SAP HANA. You can obtain these lists in
XML format from external data providers and upload them to SAP GTS, edition for SAP HANA. You can also
create your own lists.
3. The monitoring features of SAP GTS, edition for SAP HANA let you keep track of all screened addresses.
4. An employee with the appropriate authorizations can use the monitoring capabilities to release blocked
documents for further processing.
5. Periodic checks can be set up to check the current available master data. You can configure the sequence
that is used for checking the master data. It makes sense to set up the system so that all the master data is
checked automatically after every update of the sanctioned party lists.
6. All activities are logged in the area of sanctioned party list screening and can be archived for legal purposes
with the SPL audit trail function.
Import/Export Control and Embargo Check

Compliance Management PUBLIC 19
1. You create or change business document in the feeder system.
2. As a result, SAP GTS, edition for SAP HANA starts import/export control automatically. SAP GTS, edition
for SAP HANA checks if a license is required to export or import the product, based on the settings
configured in Customizing in SAP GTS, edition for SAP HANA.
3. If a license is required, SAP GTS, edition for SAP HANA assigns the appropriate license automatically to the
business transaction.
 Note
If the applicable combination of export control classification number and country of destination is not
permitted, the business transaction is blocked automatically.
Import and export controls are based on a combination of the following parameters:
• Export control classification number
• Country of destination
• Country groups
• Single products
• Special customers
• Quantities
• Values
The license itself contains information about the allowed imports and exports, particularly quantities
and/or values. When you post the business document in the feeder system, SAP GTS, edition for SAP
HANA depreciates the values or quantities of the licenses.

4. In addition, SAP GTS, edition for SAP HANA performs an embargo check for the specific business
transaction. The check is based on the combination of the country of departure and the country of
destination (or groups of countries). If SAP GTS, edition for SAP HANA detects an embargo situation, the
document is blocked for further processing.
Monitoring
You can use the reporting functions in SAP GTS, edition for SAP HANA to monitor all transactions throughout
your process chain, for example, by selecting blocked documents or displaying assigned licenses. You have an
overview of the entire process and full control over the individual transactions, and can ensure absolute
transparency.
3.1 Overview
3.1.1 Quick Access
3.1.1.1 Managing Blocked Documents
With this app, trade compliance specialists can display and edit a list of all blocked documents in SAP GTS,
edition for SAP HANA.
The Trade Compliance Specialist can search for a blocked compliance document regardless of its processing
status. The app also offers the option to perform operational analyses of existing blocked documents and
visualize the results graphically with different charts in addition to the list display.
The blocked documents are displayed for the following areas:
• Legal Controls
• Embargo Checks
Key Features
You can use this app for the following purposes:
Display and Resolve Blocked Documents
On the first detail screen, you can select the area for which you want to display further information about the
block. If a block only exists for one area, only this area is displayed.

More detailed information about the block is then displayed for each area in another detail screen, and it is
possible to process and release the blocked documents or confirm the block.
In addition, the app supports the following technical features and options:
• Analytical List Page Functions and Options
This app uses the CDS view C_CstmsCmplncDocBlkdItem.
Supported Device Types
• Desktop
3.1.1.2 Managing Blocked Partners
With this app, Trade Compliance Specialists can display and release all blocked business partners in a list that
are blocked owing to sanctioned party list screening.
The Trade Compliance Specialist can search for a specific blocked partner or display a list of blocked partners
according to various selection criteria.
Key Features
Display and Release Blocked Business Partners
You can display blocked business partners. After selecting a blocked business partner, you can release it
directly or display the details.
The detail screen then displays more detailed information about the sanctioned party list block and offers you
the option to check the blocked partners again, release them manually, or confirm the block.
• Desktop
3.1.2 Compliance Documents

3.1.2.1 Displaying Documents
With this app, trade compliance specialists can view a list of all documents. The system displays which check
status the documents have for the various compliance areas.
The following areas can be displayed:
• Legal Controls
• Embargo Checks
• Hazardous Substance Check
Key Features
Display Existing Documents
You can display existing documents for each foreign trade organization or display all existing documents for
each area. You can also display single documents and select them by using either the GTS document ID or the
reference ID from the feeder system.
This app uses the CDS view C_CustomsComplianceDocument.
• Desktop
3.1.2.2 Recheck Documents
With this app, trade compliance specialists can recheck compliance documents.
3.1.2.3 Check BOMs in Customs Documents
With this app, trade compliance specialists can check the bill of material of customs documents.

3.1.3 Business Partner Screening
3.1.3.1 Check General Addresses
With this app, trade compliance specialists can check general addresses.
3.1.3.2 Check External Addresses Offline
With this app, trade compliance specialists can check external addresses offline.
3.1.3.3 Display Positive List of Business Partners
With this app , trade compliance specialists can display the positive list of business partners.
3.1.3.4 Display Negative List of Business Partners
With this app , trade compliance specialists can display the negative list of business partners.
3.1.3.5 Manage Business Partners
With this app, trade compliance specialists can manage business partners.
3.2 Legal Control

3.2.1 License Management
3.2.1.1 Manage Licenses
With this app, trade compliance specialists can manage licenses.
3.2.1.2 Display Existing Licenses
With this app, trade compliance specialists can display existing licenses.
3.2.1.3 Display Assigned Documents
With this app, trade compliance specialists can display assigned documents.
3.2.1.4 Manage Period. Decl. for ELAN-K2
With this app , trade compliance specialists can manage periodic declarations for ELAN-K2.
3.2.1.5 Manage Determination Strategies
With this app, trade compliance specialists can manage determination strategies.
3.2.1.6 Display Determination Strategies
With this app, trade compliance specialists can display determination strategies.

3.2.1.7 Change Control Data for Documents
With this app, trade compliance specialists can change control data for documents.
3.2.2 Simulations of Compliance Checks
3.2.2.1 Review Business Transactions
With this app , trade compliance specialists can review business transactions.
3.2.2.2 Review Business Transactions - BOM
With this app , trade compliance specialists can review business transactions for BOMs.
3.2.3 Legal Control - Classification
3.2.3.1 Manage Control Classes
With this app, trade compliance specialists can manage control classes.
3.2.3.2 Manage Control Group for Products
With this app, trade compliance specialists can manage control groups for products.

3.2.3.3 Manage Peculiarity Codes
With this app, trade compliance specialists can manage peculiarity codes.
3.2.3.4 Display Classified Products - Legal Control
With this app, trade compliance specialists can view classified products in legal control.
3.2.4 Legal Control - Re-Export
3.2.4.1 Calculate Products for Re-Export
With this app, trade compliance specialists can calculate products for re-export.
3.2.4.2 Display Re-Export Calculation Log
With this app, trade compliance specialists can display calculation logs for re-exports.
3.2.4.3 Display Products - Re-Export
With this app, trade compliance specialists can display products for re-exports.
3.2.4.4 Display Re-Export BOM
With this app, trade compliance specialists can display bills of material for re-export.

3.2.5 ITAR
3.2.5.1 Manage Agreements
With this app, trade compliance specialists can manage agreements.
3.2.5.2 Display Agreements
With this app, trade compliance specialists can display agreements.
3.2.5.3 Display Assigned Documents/Licenses
With this app, trade compliance specialists can display assigned documents and licenses.
3.2.5.4 ITAR Tracking
With this app , trade compliance specialists can track International Traffic in Arms Regulations (ITAR).
3.2.5.5 Manage Projects
With this app, trade compliance specialists can manage projects.
3.3 Embargo

3.3.1 Embargo Checks
3.3.1.1 Display Released Embargo Documents
With this app, trade compliance specialists can display released embargo documents.
3.3.1.2 Analyze Embargo Release Reasons
With this app, trade compliance specialists can analyze embargo release reasons.
3.3.1.3 Display Partner in Embargo Countries
With this app, trade compliance specialists can display partners in embargo countries.
3.3.1.4 Manage Embargo Situations
With this app, trade compliance specialists can manage embargo situations.
3.4 Sanctioned Party Lists
3.4.1 Audit Trails

3.4.1.1 Display Audit Trail - Documents
With this app, trade compliance specialists can display audit trails for documents.
3.4.1.2 Display Audit Trail - Partners
With this app, trade compliance specialists can display audit trails for partners.
3.4.1.3 Display Audit Trail - External Addresses
With this app, trade compliance specialists can display audit trails for external addresses.
3.4.1.4 Display Audit Trail - General Addresses
With this app, trade compliance specialists can display audit trails for general addresses.
3.4.1.5 Analyze Reason for SPL Release
With this app, trade compliance specialists can analyze the reasons for releasing sanctioned party list
screening.
3.4.2 Master Data - Sanctioned Party Lists
3.4.2.1 Manage Sanctioned Party List Master Data
With this app, trade compliance specialists can manage sanctioned party list master data.

3.4.2.2 Display Sanctioned Party List Entities
With this app, trade compliance specialists can display sanctioned party list entries.
3.4.2.3 Display Expiring Sanctioned Parties
With this app, trade compliance specialists can display expiring sanctioned party list entries.
3.4.2.4 Display SPL Change History
With this app, trade compliance specialists can display the change history of sanctioned party list screening.
3.5 Master Data
3.5.1 Business Partner and Products
With this app, trade compliance specialists can manage business partners.
With this app, trade compliance specialists can manage products.

4 Compliance Screening
4.1 Overview
4.1.1 Quick Access
4.1.1.1 Manage Blocked Documents
With this app, trade compliance specialists for screening can manage blocked documents.
4.1.1.2 Manage Blocked Partners
With this app, trade compliance specialists for screening can manage blocked partners.
4.1.2 Compliance Documents
4.1.2.1 Display Documents
With this app, trade compliance specialists for screening can display compliance documents.

32 PUBLIC Compliance Screening
4.1.2.2 Recheck Documents
With this app , trade compliance specialists for screening can recheck compliance documents.
4.1.3 Business Partner Screening
4.1.3.1 Check General Addresses
With this app, trade compliance specialists for screening can check general addresses.
4.1.3.2 Check External Addresses
With this app, trade compliance specialists for screening can check external addresses.
4.1.3.3 Display Positive List - BPs
With this app, trade compliance specialists for screening can display positive lists for business partners.
4.1.3.4 Display Negative List - BPs
With this app, trade compliance specialists for screening can display negative lists for business partners.
With this app, trade compliance specialists for screening can manage business partners.

Compliance Screening PUBLIC 33
4.2 Sanctioned Party Lists
4.2.1 Audit Trails
4.2.1.1 Display Audit Trail - Documents
With this app, trade compliance specialists for screening can display audit trails for documents.
4.2.1.2 Display Audit Trail - Partners
With this app, trade compliance specialists for screening can display audit trails for partners.
4.2.1.3 Display Audit Trail - External Addresses
With this app, trade compliance specialists for screening can display audit trails for external addresses.
4.2.1.4 Display Audit Trail - General Addresses
With this app, trade compliance specialists for screening can display audit trails for general addresses.
4.2.1.5 Analyze Reason for SPL Release
With this app, trade compliance specialists for screening can analyze the reasons for releasing sanctioned party
list screening.

4.2.2 Master Data - Sanctioned Party List
4.2.2.1 Manage Sanctioned Party List Master Data
With this app, trade compliance specialists for screening can manage sanctioned party list master data.
4.2.2.2 Display Sanctioned Party List Entries
With this app, trade compliance specialists for screening can display sanctioned party list entries.
4.2.2.3 Display Expiring Sanctioned Parties
With this app, trade compliance specialists for screening can display expiring sanctioned party list entries.
4.2.2.4 Display SPL Change History
With this app, trade compliance specialists for screening can display the change history of sanctioned party list
screening.
4.3 Master Data

Compliance Screening PUBLIC 35
With this app, trade compliance specialists for screening can manage business partners.
With this app, trade compliance specialists for screening can manage products.

5 Customs Management
SAP GTS, edition for SAP HANA helps your company automate and standardize import and export processes
with the customs authorities.
SAP GTS, edition for SAP HANA enables you to speed up the import and export of goods and reduce the total
costs for processing customs-relevant transactions. One essential prerequisite for this is electronic
communication with the customs authorities in the individual countries that use computerized procedures.
Electronic customs processing with the application helps companies meet the stringent requirements of the
legal regulations, accelerating the release of their goods by the customs authorities.
You can handle customs processes and administrative files by exchanging electronic messages with the
customs authorities, as well as printing out the necessary forms. The automated handling and monitoring of
cross-border and control-relevant goods traffic helps you ensure compliant process handling and standardize
communications with the authorities. This simplifies and accelerates customs clearance and administration. In
addition to electronic communication, you can use additional simplifications for customs declarations,
provided you have been granted the necessary authorizations by the customs authorities.
Prerequisites
You have configured Customs Management in accordance with the information in the Configuration Guide for
SAP Global Trade Services, edition for SAP HANA.
5.1 Customs - Export
5.1.1 Messages
5.1.1.1 Export Declarations

Customs Management PUBLIC 37
5.1.1.1.1 Manage Export Declarations
With this app, customs specialists for exports can manage export declarations.
5.1.1.1.2 Display Export Declarations
With this app, customs specialists for exports can display export declarations.
5.1.1.1.3 Display Overdue Exit Confirmations
With this app, customs specialists for exports can display overdue exit confirmations.
5.1.1.1.4 Display Documents for Customs Export

Declarations
With this app, Customs specialists for exports can display documents for customs export declarations.
5.1.1.2 Transit Declarations
5.1.1.2.1 Manage Transit Declarations
With this app, customs specialists for exports can manage transit declarations.
5.1.1.2.2 Display Transit Declarations
With this app, customs specialists for exports can display transit declarations.

38 PUBLIC Customs Management
5.1.1.2.3 Display Overdue Transit Confirmations
With this app, customs specialists for exports can display overdue transit confirmations.
5.1.1.3 Periodic Declarations
5.1.1.3.1 Create Supplementary Customs Declarations
With this app, Customs specialists for exports can create supplementary customs declarations.
5.1.1.3.2 Display Supplementary Customs Declarations
With this app, customs specialists for exports can display supplementary customs declarations.
5.1.1.3.3 Change Supplementary Customs Declaration
With this app, Customs specialists for exports can change supplementary customs declarations.
5.1.1.3.4 Display Export Supplementary Customs

Declarations
With this app, Customs specialists for exports can display supplementary customs declarations for export.
5.1.2 Customs Broker

5.1.2.1 Monitoring
5.1.2.1.1 Display Messages in Communication
With this app, Customs specialists for exports can display messages in communication.
5.1.2.1.2 Display Performance Rating
With this app, Customs specialists for exports can display performance ratings.
5.1.3 Master Data
5.1.3.1 Authorizations and Securities
5.1.3.1.1 Manage Export Declarations
With this app, customs specialists for exports can manage export declarations.
5.1.3.1.2 Display Export Declarations
With this app, customs specialists for exports can display export declarations.
5.1.3.1.3 Display Overdue Exit Confirmations
With this app, customs specialists for exports can display overdue exit confirmations.

5.1.3.1.4 Display Transit Docs for Securities
With this app, Customs specialists for exports can display transit documents for securities.
5.1.3.1.5 Manage Transit Securities
With this app, Customs specialists for exports can manage transit securities.
5.1.3.1.6 Monitor Transit Securities
With this app, Customs specialists for exports can monitor transit securities.
5.1.3.1.7 Monitor Simplified Procedures Authorizations
With this app, customs specialists for exports can monitor simplified procedures authorizations.
5.1.3.2 Geography
5.1.3.2.1 Edit Issue/Destination Nodes
With this app, customs specialists for exports can edit issue/destination nodes.
5.1.3.3 Business Partners

5.1.3.3.1 Manage Business Partners
With this app, customs specialists for exports can manage business partners.
5.1.3.3.2 Manage Products
With this app, customs specialists for exports can manage products.
5.1.3.4 Product Catalog
5.1.3.4.1 Display Product Catalog Based on Customs

Declarations
With this app, Customs specialists for exports can display a product catalog based on customs declarations.
5.2 Customs- Import
5.2.1 Ending of Transit Operations
5.2.1.1 Display Inbound Activities
With this app, customs specialists for imports can display inbound activities.

5.2.1.2 Display Customs Shipments Import
With this app, customs specialists for imports can display customs shipments in imports.
5.2.1.3 Display Ending of Transit Operations
With this app, Customs specialists for imports can display ending of transit operations.
5.2.1.4 Change Ending of Transit Operations
With this app, Customs specialists for imports can change ending of transit operations.
5.2.1.5 Create Ending of Transit Operations
With this app, Customs specialists for imports can create ending of transit operations.
5.2.1.6 Fast Entry: Deregister Transit Notifications
With this app, customs specialists can use fast entry to deregister transit declarations for imports.
5.2.1.7 Create End of Transit Ops w/Template
With this app, Customs specialists for imports can create ending of transit operations with a template.
5.2.2 Periodic Declarations

5.2.2.1 Postprocess Supplementary Customs Declarations
With this app, Customs specialists for imports can postprocess supplementary customs declarations.
5.2.2.2 Create Supplementary Customs Declarations
With this app, Customs specialists for imports can create supplementary customs declarations.
5.2.2.3 Display Supplementary Customs Declaration
With this app, Customs specialists for imports can display supplementary customs declarations.
5.2.2.4 Change Suppl. Customs Declaration
With this app, Customs specialists for imports can change supplementary customs declarations.
5.2.2.5 Display Suppl. Customs Decl. in Import
With this app, customs specialists for imports can display supplementary customs declarations in imports.
5.2.3 Presentations
5.2.3.1 Display Import Activities in Import
With this app, customs specialists for imports can display inbound activities in imports.

5.2.3.2 Display Presentations
With this app, customs specialists for imports can display presentations.
5.2.3.3 Display Safekeeping Overview
With this app, customs specialists for imports can display safekeeping overviews.
5.2.3.4 Create Presentation
With this app, Customs specialists for imports can create presentations.
5.2.3.5 Display Presentations
With this app, customs specialists for imports can display presentations.
5.2.3.6 Change Presentation
With this app, Customs specialists for imports can change presentations.
5.2.3.7 Create Presentation with Template
With this app, Customs specialists for imports can create presentations with a template.
5.2.4 Pre-Declarations

5.2.4.1 Display Pre-Declarations
With this app, customs specialists for imports can display pre-declarations.
5.2.4.2 Display Inbound Activities - Pre-Declaration
With this app, Customs specialists for imports can display inbound activities in the pre-declaration.
5.2.4.3 Create Pre-Declarations
With this app, customs specialists for imports can create pre-declarations.
5.2.4.4 Change Pre-Declaration
With this app, Customs specialists for imports can change pre-declarations.
5.2.4.5 Create Pre-Declaration with Template
With this app, customs specialists for imports can create pre-declarations with a template.
5.3 Special Customs Procedures
5.3.1 Messages

5.3.1.1 Customs Import Declarations
5.3.1.1.1 Create Import Declarations
With this app, Customs specialists for special customs procedures can create import declarations.
5.3.1.1.2 Display Import Declarations
With this app, customs specialists for special customs procedures can display import declarations.
5.3.1.1.3 Change Import Declarations
With this app, customs specialists for special customs procedures can change import declarations.
5.3.1.1.4 Create Customs Declaration After Goods Rcpt
With this app, Customs specialists for special customs procedures can create customs declarations after goods
receipt.
5.3.1.1.5 Create Customs Decls Before GR
With this app, Customs specialists for special customs procedures can create customs declarations prior to
goods receipt.
5.3.1.1.6 Display Inbound Activities Import
With this app, Customs specialists for special customs procedures can display inbound activities for imports.

5.3.1.1.7 Display Import Declarations
With this app, Customs specialists for special customs procedures can display import declarations.
5.3.1.1.8 Display Documents for Customs Import

Declarations
With this app, Customs specialists for special customs procedures can display documents for customs import
declarations.
5.3.1.1.9 Create Customs Import Declarations w/Template
With this app, customs specialists for special customs procedures can create customs import declarations with
a template.
5.3.1.2 Periodic Declarations
5.3.1.2.1 Postprocess Supplementary Customs

Declarations
With this app, Customs specialists for special customs procedures can postprocess supplementary customs
declarations.
5.3.1.2.2 Create Supplementary Customs Declarations
With this app, Customs specialists for special customs procedures can create supplementary customs
declarations.

5.3.1.2.3 Display Supplementary Customs Declarations
With this app, customs specialists for special customs procedures can display supplementary customs
declarations.
5.3.1.2.4 Change Supplementary Customs Declaration
With this app, Customs specialists for special customs procedures can change supplementary customs
declarations.
5.3.1.2.5 Display Supplementary Customs Declarations for

Imports
With this app, customs specialists for special customs procedures can display supplementary customs
declarations for imports.
5.4 Customs EMCS
5.4.1 Change Administrative Document
With this app, Customs specialists for EMCS can change administrative documents.
5.4.2 Display Outbound Activities - Excise Duty
With this app, customs specialists for EMCS can display outbound activities for excise duties.
5.4.3 Monitor Confirmations - Administrative Documents
With this app, Customs specialists for EMCS can monitor confirmations for administrative documents.

5.4.4 Create Administrative Document
With this app, Customs specialists for EMCS can create administrative documents.
5.4.5 Display Outbound Documents - Administrative

Documents
With this app, customs specialists for EMCS can display outbound documents for administrative documents.
5.4.6 Display Inbound Documents: Administrative

Documents
With this app, customs specialists for EMCS can display inbound documents for administrative documents.
5.4.7 Display Inbound Activities - Excise Duty
With this app, customs specialists for EMCS can display inbound activities for excise duties.
5.4.8 Display Administrative Document
With this app, Customs specialists for EMCS can display administrative documents.
5.4.9 Create Administrative Document with Template
With this app, customs specialists for imports can create administrative documents with a template.

6 Preference Management
Preference Processing supports you as an exporter to meet the legal requirements for preferential customs
treatment and document your products as eligible for preferential treatment.
Based on this documented eligibility for preferential treatment, the exporter's customers can import these
products duty-free or at a reduced rate of import duty, giving the exporter a decisive competitive advantage.
Prerequisites
You have configured Preference Management in accordance with the information in the Configuration Guide for
SAP Global Trade Services, edition for SAP HANA.

Preference Management PUBLIC 51
Process
1. The feeder system transfers information on supplier-product relationships to the GTS system for
Preference Management. The GTS system can create proposals for further processing from this data.
2. Based on the business documents, the system can create proposals for requesting long-term supplier’s
declarations for which you do not have an LTSD. During creation, current supplier data, for example, the
communication method and the request relevance, is taken into account. You can now send the request for
long-term supplier’s declarations to your supplier.

52 PUBLIC Preference Management
3. When you receive a long-term supplier declaration from your suppliers, you have to enter and release them
in the GTS system.
4. The system aggregates products based on existing goods receipts and released long-term supplier’s
declarations.
5. The system uses the threshold value from preference determination. In this process, it combines the
statements for each material, based on the rules and procedures of the preference agreement, regardless
of whether valid or invalid supplier’s declarations are available. The system archives the results of
preference determination to enable further monitoring and audits.
6. When you create or change an order or billing document in the feeder system, the system compares the
threshold value with the ex works price from the order or billing document.
7. If the product is eligible for preferential treatment, the system sets the preference indicator.
8. You can issue long-term supplier’s declarations to your customers. The system can create proposals based
on business documents.
Key Features
On the SAP Fiori launchpad, open the Preference group. You can choose between the following pages:
• Supplier’s Declarations [page 53]

• Preference Determination [page 71]
• Master Data [page 77]
6.1 Supplier’s Declarations
6.1.1 Inbound Declarations
6.1.1.1 Manage Requests – Long-Term Supplier’s

Declarations
With this app, Preference specialists can display, change, delete, create, and send requests for long-term
supplier’s declarations to their suppliers.
The preference specialist can manage requests for long-term suppliers’ declarations that are created on the
basis of purchasing documents and material documents from the feeder system, or create requests manually.

Features
View Requests
A request contains the following elements that you can display:
• LTSD Issuer
The LTSD issuer is the recipient of the request and is to issue the long-term supplier’s declaration on its
behalf.
 Recommendation
With the Manage Preference Properties - Suppliers [page 59] app, you can define an alternative LTSD
issuer.
• Requisition Period
Period for which you require a long-term suppliers’ declaration.
• Products
List of products for which you need a long-term suppliers’ declaration.
• Prod. Supplier
Product description of your supplier, provided this has been defined in the product master for partner-
related data.
• Source
The source tells you why the product is included in the request. If it was included in the request based on a
purchase order, the source purchasing document is displayed. If it was included based on a goods receipt,
the source material document is displayed. If the product was added manually, the source manual is
displayed.
A detail screen is displayed for each product. The Purchasing Document Items and Material Document
Items tab pages display the documents in the respective feeder system. The Agreement Status tab page
displays the current processing status of the respective agreement.
• Preference Agreements
The preference agreements are determined based on the active agreements and the LTSD types that are
relevant for the request process.
• Communication Method
The communication type shows how the request to your LTSD recipient is processed.
• Contact Details
Depending on the communication type, the address of the LTSD recipient is displayed for post, and a
contact card with name and e-mail address is displayed for each contact person for e-mail.
• Actions
In addition to the preview, you can display both the processing status and the processing log for each
action.
Creating Requests Manually

You can manually create a request for long-term suppliers’ declarations independently of the list, regardless of
the tab page.
Choose Create and then enter the administrative unit and the LTSD issuer for which you want to create the
request. You can then add the request period and the products you want to request to the request.

Depending on the status of the request, you can also do the following:
Status is Ready to Be Sent
• Send Requests
You have the following options for sending a request:
• Select one or more requests in the overview list and send them.
• Send a single request from the detail screen.
The communication type defined in the request is used for sending.
• Delete Requests
You have the following options for deleting a request:
• Select and delete one or more requests in the overview list.
• Delete a single request from the detail screen.
• Edit Requests
To edit a request, choose Edit on the detail screen.
You can then edit the requirement period and add products to the existing requirement or delete products
from it.
Status is Failed
• Send Requests Again

If the previous sending of the request failed, you can send it again. You have the following options:
• Select one or more requests in the overview list and send them again
• Send a single request again from the detail screen.
To send the request again, the communication type is determined again.
• Complete Requests
If you no longer want to take failed requests into consideration, you can complete the request. You have the
following options:
• Select one or more requests in the overview list and close them.
• Complete a single request from the detail screen.
Status is Sent
• Send Requests Again

If you want to send a request already sent successfully again, you have the following options:
• Select one or more requests in the overview list and send them again
• Send a single request again from the detail screen.
To send the request again, the communication type is determined again.
• Complete Requests
If you do not want to keep track of a request that has already been sent successfully and do not want to
include it in follow-on processes, you have the following options:
• Select one or more requests in the overview list and close them.
• Complete a single request from the detail screen.
Status is Completed
• View Requests
Requests in Completed status are available in display mode.

 Note
You can have the system propose requests for long-term supplier’s declarations based on purchase orders
and goods receipts. To do this, you can use the program Create LTSD Requests or Create Annual LTSD
Requests. Based on purchase order documents and material documents that were transferred from the
feeder system, the system creates proposals if the LTSD issuer or the products are request-relevant. This
can be determined with the Manage Preference Properties - Suppliers [page 59] app.
Products and document items in a request are updated if the request is in status Ready to Send. Requests
that have already been sent are not updated.
The request period always corresponds to a full calendar year.
This app uses the C_LTSDRequestTP CDS view.
• Desktop
6.1.1.2 Manage Long-Term Supplier’s Declarations –

Inbound
With this app, preference specialists can create, display, change, release, delete, or cancel inbound long-term
supplier’s declarations that you receive from your suppliers.
Features
Displaying Long-Term Supplier’s Declarations

A long-term supplier’s declaration contains the following elements that you can display:
• LTSD Issuer
The LTSD issuer is the supplier who issued the long-term supplier’s declaration to you.
 Note
You can define an alternative LTSD issuer in the Manage Preference Properties – Suppliers app.
• Period of Issue
Period for which the long-term supplier’s declaration was issued.
• Date of Issue
Date on which the long-term supplier’s declaration was issued.

• LTSD Reference
Reference number of the LTSD issuer for the long-term supplier’s declaration.
• Products
List of products for which a long-term supplier’s declaration was issued.
• Product Supplier
Product description of your suppliers, provided this has been defined in the product master in the
Partner-Related Data view.
• Last GR Date
Date of the last goods receipt.
• Predecessor LTSD
A predecessor LTSD is displayed if a long-term supplier’s declaration already exists for the product, the
administrative unit, and the LTSD issuer for an overlapping period.
• LTSD Request
If one or more submitted requests exist for the product during the issue period, the request sent last is
displayed.
• Display preference statements for a product
In the detail view, the system displays all preference statements for a product for each product. The detail
view lists the preference statement for all agreements that are assigned to an LTSD type.
Creating Long-Term Supplier’s Declarations
You can create a long-term supplier’s declaration manually.
Choose Create and then enter the administrative unit and the LTSD issuer for which you want to create a
declaration. Based on the country of departure and the country of destination of the supplier and on the
country of the administrative unit, the long-term supplier’s declaration types activated for the administrative
unit are determined and made available for selection in the input help. You can then add to the declaration the
issue period and the products that you want to create.
To complete the creation of a declaration, you must specify the period of issue and the date of issue. Enter the
preference statements of the agreements contained in the declaration for each product.
Editing Long-Term Supplier’s Declarations
To edit a declaration, choose Edit in the detailed view. Depending on the release status of the declaration, you
can edit the following elements:
• Release Status – Not Ready for Release and Ready to Be Released

You can edit the period of issue, the date of issue, and the LTSD reference. You can also add products to the
declaration or remove them.
• Release Status – Partially Released and Released
In this case, restricted processing is still possible. You have the option of editing the LTSD reference. You
can still add products to the declaration. However, you cannot edit products that have the status Released.
 Note
To be able to release products of a declaration even though the processing of the declaration has not been
completed completely, you have the option of adding products even after the release. Note, however, that
the period of issue and the date of issue can no longer be edited.

Deleting Long-Term Supplier’s Declarations
If a long-term supplier’s declaration has not yet been released, you can delete it. You have the following options:
• Select and delete one or more declarations in the overview list

• Delete a single declaration using the detailed view
Releasing Long-Term Supplier’s Declarations
Once you have completely or partially processed an LTSD, you can release the assigned products. You have the
following options:
• Select one or more declarations in the overview table and release them
• Release a single declaration using the detailed view
• Release one or more products that have the status Ready for Release in the detailed view
 Note
The aggregation takes into account only products and their preference statements with the status
Released.
Canceling Long-Term Supplier’s Declarations
If an LTSD has already been released, you can cancel it. You have the following options:
• Select one or more declarations in the overview table and delete them
 Note
Cancelled long-term supplier’s declarations are also taken into account in aggregation. Preference
statements that have already been evaluated are corrected.
 Note
The agreement status in sent requests for the LTSD issuer, product, and agreement is updated according
to the release status from the declaration if the request period overlaps with the validity period of the
declaration.
The request status in the request is set to completed if there is full feedback from one or more declarations
for the entire request.
• Desktop

6.1.1.3 Manage Preference Properties - Suppliers
With this app, preference specialists can create, edit, or delete properties in Preference Management for your
suppliers.
The preference specialist can use the app to enter and manage exceptions for suppliers for each administrative
unit. If there is no exception for a supplier, the properties predefined for the administrative unit for creating and
sending requests for long-term suppliers’ declarations are used.
You can define properties both for suppliers and products for a supplier. In principle, the levels with more
detailed entries are given priority.
Features
Manage preference properties for a supplier for each administrative unit

You can define the following properties for each administrative unit and supplier:
• Define Request Relevance

You can use request relevance to control whether a request for long-term suppliers’ declarations is to be
created for a supplier or for products for the supplier. You can choose from the following values:
• Preset
You do not want to define an exception. The default request relevance of the administrative unit is
used.
• Yes
Supplier/products for a supplier are relevant for requests.
• No
Supplier/products for a supplier are not relevant for requests.
 Note
To ensure that long-term suppliers’ declarations can only be requested from authorized suppliers, the
system checks whether the supplier is relevant for at least one agreement according to the country of
departure (country of LTSD issuer) and country of destination (country of administrative unit). If the
supplier is not relevant for any agreement, it is classified as a third-country supplier. In this case, you
can only specify the preference properties for the supplier to a limited extent.
In the list view, the request relevance you defined is interpreted and displayed by the request relevance
status.
Request Relevance Status
The request relevance status determines whether a supplier receives requests for long-term supplier’s
declarations from your administrative unit and which products can be requested from your supplier. This
results from the request relevance for the following:
• The administrative unit
• The supplier
• The products of the supplier

The following cases can occur:
• Yes
The administrative unit requests for all of the supplier's products.
• Yes, with Exceptions
• No
The administrative unit does not request any products from the supplier. The supplier does not receive
a request.
The administrative unit always requests for all of the supplier's products. However, certain products of
the supplier are excluded from the request.
• No, with Exceptions
The administrative unit does not request any products from the supplier. However, certain products
are requested from the supplier. The supplier can only receive a request with these products.
Overview Request Relevance Status

Request Relevance at Ad Request Relevance at Sup Request Relevance at
Request Relevance Status ministrative Unit Level plier Level Product Level
Yes Yes Preset Preset*
Yes Yes Yes Yes*
Yes No Yes Yes*
Yes, with Exceptions Yes Preset No**
Yes, with Exceptions Yes Yes No**
Yes, with Exceptions No Yes No**
No No Preset Preset*
No No No No*
No Yes No No*
No, with Exceptions No Preset Yes***
No, with Exceptions No No Yes***
No, with Exceptions Yes No Yes***
Legend
* This setting is optional and an entry for a supplier product is not mandatory.
** At least one product of the supplier must be specified at product level with request relevance “No”
*** At least one product of the supplier must be specified at product level with request relevance “Yes”
• Define Communication Method

You can use the communication method to control how you want to communicate with your supplier.
• Preset
You do not want to define an exception. The default communication method of the administrative unit
is used.
• E-Mail
You want to send the requests by e-mail.
• Post
You want to print the requests and send them by post.

 Note
If you have defined the communication method E-Mail , you have to define the e-mail address of the
employee responsible for the preference of your supplier in the business partner master of the LTSD
issuer.
• Define Product Retention Period

You can use the product retention period to control how many calendar days each goods receipt is to be
taken into account within preferential determination of origin (aggregation). You can define this
characteristic both for your supplier and the products for the supplier.
 Example
You have defined a product retention period of 150 days for the supplier IDES China Ltd., who is
classified as a third-country supplier for your administrative unit. As a result, each goods receipt from
your supplier IDES China Ltd. is aggregated negatively for 150 calendar days each. After the 150
calendar days have passed, the respective goods receipts are no longer taken into account in the
aggregation.
• Specify LTSD Issuer

The LTSD issuer is the business partner who you want to issue you a long-term suppliers’ declaration.
If the supplier for whom you define the preference properties differs from the LTSD issuer, you specify a
different business partner as the LTSD issuer. To do this, select the value "Customer is not an LTSD issuer"
and enter the new LTSD issuer. Purchasing and material documents of this supplier will be included in
future in requests for the new LTSD issuer.
If one or more suppliers are assigned to the same LTSD issuer, the additional suppliers are displayed in the
preference properties of this supplier. This means that all purchasing and material documents for this
supplier and all additional suppliers are grouped together in one request.
 Example
You have a business relationship with a corporate group that supplies you with 5 plants. The corporate
group wants to issue the long-term suppliers’ declaration on behalf of all supplying plants. For this
reason, all purchasing and material documents of the 5 plants and the corporate group head office
should be grouped together in one requisition. The corporate headquarters should be the issuer of the
long-term suppliers’ declaration.
For all vendors that represent the respective plants, define the group head office as the LTSD issuer in
the preference properties. In the preference properties of the corporate headquarters, all plants are
listed as additional suppliers.
• Create Notes
You can create notes to document your decisions.
Delete preference properties for a supplier for each administrative unit
You can delete the exceptions of the preference properties for your suppliers.
 Note
If you delete the stored preference properties in the app, the predefined properties of the administrative
unit are used for all subsequent future processes, such as request and aggregation.

• Desktop
6.1.1.4 Analyzing the Relevance of Products for Requesting

Long-Term Supplier’s Declarations
With this app, preference specialists can analyze the relevance of products for requesting supplier’s
declarations.
The Preference Processing area includes an analysis tool to help you optimize your processes for determining
preference eligibility. The goal of this analysis is to only request long-term declarations for your purchased
products whose preference statements influence the preference eligibility of a product produced in-house or a
product of mixed origin. This lets you minimize the effort required for requesting long-term supplier’s
declarations. We recommend running the analysis before your annual request run.
Prerequisites
You have limited the validity of the request relevance up to the next analysis in the product. If you set the
validity as Permanent, the system excludes this product from the analysis. In this case, it only interprets the
flag in the product that you set manually to Relevant for Request or Not Relevant for Request to calculate the
request relevance.
The analysis considers the occurrence and significance of the selected products in all BOMs for the active
preference agreements. In the process, it analyzes the preference-specific product data, such as procurement
indicator and saleability.
The system determines the request relevance according to the following criteria:
• Procurement Indicators
The system only considers products produced in-house and products procured externally in the analysis.
• Validity flag for request relevance in the product
The system only includes products in the analysis whose statement for request relevance has the validity
Temporary until next analysis. This flag is the default value, but can be overwritten manually with
Permanent in the product.
• Saleability
The system only includes products in the analysis that are flagged as saleable in the product. You only need
a preference statement at the time of sale for saleable products, and can derive it from your supplier's
preference statement in long-term supplier’s declarations. The system therefore excludes products that
are contained only as components in BOMs.
• Use in BOM
The system only analyzes products that actually occur in a BOM for preference determination.
• BOM evaluation
The system evaluates the following criteria within a BOM:
• Tariff number for leading part of BOM

The system only includes products in the analysis that you have already classified as the leading parts
of a BOM.
• Tariff shift
Is a preference statement for a product possible through a tariff shift within the BOM? If a product
achieves preference eligibility through a tariff shift, it is not necessary to request a long-term supplier’s
declaration for that product, and the system marks it as not relevant for request.
• Preference rule
If a product already achieves preference eligibility through conditions that are defined in the preference
rules, the system excludes that product from further analysis of request relevance.
• Value limits
You can define the following values in the selection screen for analyzing request relevance:
• Minimum absolute value in the currency unit of the administrative unit
• Minimum value in percent
The minimum value in percent corresponds to the unit price of the product, independently of how
often it is used in a BOM.
The system only analyzes the request relevance of products that exceed the specified absolute value
limit or whose component price exceeds the percentage share of the total value of the leading part in a
BOM.
Key Features
• Processing variants
You can execute the analysis of the request relevance for one or more products in dialog mode.
• Output of results
• After an analysis in dialog mode, the system displays a result list that shows whether the product is
relevant for requests. You can see the analysis steps in the log.
• The system also saves the results for each product in the product, on the Preference Properties tab.
See Also
The relevance analysis is useful for the following apps:
• Manage Requests – Long-Term Supplier’s Declarations [page 53]

• Manage Products [page 83]
6.1.2 Outbound Declarations

6.1.2.1 Manage Long-Term Supplier’s Declarations –
Outbound
With this app, preference specialists can create, display, change, delete, and send outbound long-term
supplier’s declarations to their customers.
The preference specialist can also manage outbound long-term supplier’s declarations that were created on
the basis of billing documents from the feeder system, or create long-term supplier’s declarations manually. In
addition, long-term supplier’s declarations can be checked and, if required, processed before submission.
Features
Display long-term supplier’s declarations

A long-term supplier’s declaration contains the following elements that you can display:
• LTSD Recipient
The LTSD recipient is the customer to whom you issue the long-term supplier’s declaration.
 Note
You can define an alternative LTSD recipient in the Manage Preference Properties – Customers app.
• Period of Issue
Period for which you want to issue the long-term supplier’s declaration.
• Products
List of products for which you issue a long-term supplier’s declaration.
• Prod. Cust.
Product description of your customer, provided this has been defined in the product master in the
Partner-Specific Data view.
• Summarized Status
The aggregated preference status of a product results from merging all agreement-related preference
statements into one overall statement. If all individual statements are consistently positive or negative,
the aggregated preference status is also positive or negative. If there are both positive and negative
preference statements at agreement level, the aggregated preference status is Positive/Negative.
• Source
The source tells you why the product is included in the long-term supplier’s declaration. If the product
was included on the basis of a billing document, Invoice Documents is displayed as the source. If
assigned invoices were canceled, Billing Document Canceled is displayed as the source. If the product
was added manually, Added Manually is displayed as the source.
• Agreement
List of the preference agreements that are assigned to the long-term supplier’s declaration type.
• Output Details
In the output details, you can see the communication type (mail or email) and the name of the
contact within the company. The Actions area provides you with an overview of the files that have
been sent or are yet to be sent.

• A detailed view is displayed for each product, allowing you to view all preference statements for the
product.
The detailed view contains a list of the preference statements for all agreements that are assigned to the
long-term supplier’s declaration. The system determines preference statements depending on the period
of issue of the declaration and the preference statements from the product master data. These preference
statements are used to issue the long-term supplier’s declaration.
The details of the preference statement, such as the method of comparison, are derived from the
preference data in the detailed view for the product and the agreement that the preference statement
represents.
• A detailed view is displayed for each agreement, allowing you to view all preference statements for an
agreement.
The preference statement in the header corresponds to the preference statement at agreement level for
the product. This preference statement is achieved by valuating all preference statements on the
Preference Data tab. If no preference data is available, the system applies a negative preference statement.
You also have the option of setting the preference statement manually. To do this, use the Change
Preference Statement action and select the preference statement. The status Changed Manually is set to
Yes. Manually set preference statements are no longer changed automatically as a result of preference
determination by the system.
• Preference Data
List of all preference data that exists for the issue period, the product, and the agreement.
• Analysis Period
Period for a preference statement that lies within the validity of the declaration.
The system displays periods only if preference statements exist in the product master or invoices
exist for the analysis period.
• Comparison Method
If, for the analysis period, there are several possible comparison methods from the product
master, the comparison method with the best preference statement is used. If the comparison
method is not specified, only billing documents exist for the analysis period.
• Threshold Value Comparison
If a threshold value comparison was required to determine the preference statement, the details
are displayed.
• Billing documents
List of all billing document items that the system used for preference determination.
Billing document items are assigned to the analysis period using their date of services rendered,
provided a threshold value comparison is necessary. If there are several billing documents for a
threshold value comparison within the same period, the billing document value is determined
depending on the comparison method, for example, the worst billing document value.
Creating long-term supplier’s declarations
You can create a long-term supplier’s declaration manually.
Choose Create and then enter the administrative unit and the LTSD recipient for which you want to create a
declaration. Based on the country of departure and the country of destination of the customer and on the
country of the administrative unit, the long-term supplier’s declaration types activated for issue for the
administrative unit are determined and made available for selection in the input help. You can then add to the
declaration the issue period and the products that you want to issue. Once you have saved your entries, the GTS
system checks whether relevant billing documents exist for the declaration. If so, these are automatically
assigned to the relevant product and used to determine the preference statement.

Depending on the status of the declaration, you can also do the following:
Status is Ready to Be Sent
• Sending Long-Term Supplier’s Declarations

When the declaration is sent, the system automatically creates a PDF form with the clarification that you
have sent to your customer. This PDF is added automatically on the Attachments tab. You have the
following options for sending a declaration:
• Select and send one or more declarations in the overview list
• Send a single declaration using the detailed view
 Note
You can define an alternative communication type in the Manage Preference Properties – Customers
app.
• Deleting Long-Term Supplier’s Declarations

You have the following options for deleting a declaration:
 Note
If a declaration to which the system has already assigned invoices is deleted, the invoices remain in the
system. These invoices can then be assigned to new declarations.
• Editing Long-Term Supplier’s Declarations

To edit a declaration, choose Edit in the detailed view. You can then edit the issue period and add products
to the declaration or delete products from it.
 Note
When you save a declaration, the system performs preference determination again.
Status is Failed
• Resending Long-Term Supplier’s Declarations

If the previous sending of a declaration failed, you can send it again. You have the following options:
• Select one or more declarations in the overview list and resend them
• Resend a single declaration using the detailed view
 Note
When the declaration is resent, the communication type is determined again.
• Deleting Long-Term Supplier’s Declarations

You have the following options for deleting a declaration:

 Note
If a declaration to which the system has already assigned invoices is deleted, the invoices remain in the
system. These invoices can then be assigned to new declarations.
Status is Sent
• Display long-term supplier’s declarations
Long-term supplier’s declarations with the status Sent are available in display mode.
 Note
Billing documents that were transferred from the feeder system remain in the system until they are
archived and are used to determine the preference statement as part of the threshold value comparison.
This is independent of whether you use billing documents to propose explanations or create declarations
manually.
 Note
You can have the system propose requests for long-term supplier’s declarations based on billing
documents.
To do this, you can schedule the program Issue of LTSDs. Based on billing documents that were transferred
from the feeder system, the system creates proposals if the LTSD issuer or the products are relevant for
issue.
You can determine this with the Manage Preference Properties - Customers [page 69] app.
Products and billing document items in a request are updated if the request is in status Ready to Send. The
issue period depends on your Customizing settings and the maximum permitted validity of the original
document.
If proposals for long-term supplier’s declarations are created using transaction Annual Issue of LTSDs (/
SAPSLL/LTSDOUT_2), these proposals are based on billing documents that have already been transferred
and LTSDs that have already been issued. The preference statements are then redetermined for the new
issue period. If it is not possible to determine uniquely the preference statements for the new issue period,
the preference statements of the most recently valid long-term supplier’s declarations are used.
Billing documents with a different document address are not taken into account by the annual run.
• Desktop

6.1.2.2 Manage Re-Issue Reasons – Long-Term Supplier’s
Declarations
With this app, preference specialists can display, edit, and close reasons for re-issuing long-term supplier’s
declarations at product level, as well as send a new long-term supplier’s declaration to their customers.
The system creates re-issue reasons on the basis of issued long-term supplier’s declarations if changes occur
in the preference statement due to the following events:
• New billing documents

• New preference determination
• New aggregation
• New preference statement entered manually in the product master
You can decide if you want to use a reissue reason to
• send a new long-term vendor declaration to your customer

or
• complete it
Features
Show Re-Issue Reason

A re-issue reason contains the following elements that you can display:
• Validity Period
Period for which the re-issue reason was checked and is valid.
• Preference Statements Affected
List of all preference agreements for which the preference statement was changed.
By comparing both preference statements, you can identify the change while taking the validity period into
account.
You can use the detail view to display the logs for the preference agreement. These show which events have
led to the change in the preference statement since the re-issue reason was created.
Edit Re-Issue Reason

You can edit the valid-from date proposed by the system. This may cause preference statements to be
switched (for example, from positive to negative or from C2 to C2E). In this case, the system adjusts the list of
affected preference statements.
Complete Re-Issue Reason

If you decide not to re-issue a long-term supplier’s declaration, you can close the re-issue reason. A new long-
term supplier’s declaration is not created and the reason can no longer be edited.
Send Long-Term Supplier’s Declarations

You can send long-term supplier’s declarations on the basis of an open re-issue reason.

The declaration to be sent is sent using the Manage Long-Term Supplier’s Declarations – Outbound [page 64]
app and is displayed there in the app after being sent successfully. If an explanation cannot be sent, this is
documented in the error log in the Manage Re-Issue Reasons app.
If multiple validities exist for a re-issue reason, a long-term supplier’s declaration is sent for each validity
period. The valid-to date of sent declarations corresponds to the valid-to date of the original declaration.
 Note
For the creation of re-issue reasons, it is necessary to schedule the program Process Triggers for the
Creation of Re-issue Reasons at regular intervals. Long-term supplier’s declarations that have the status
Sent and that are valid at the time of execution form the basis for a check.
• Desktop
6.1.2.3 Manage Preference Properties - Customers
With this app, preference specialists can create, edit, or delete properties in Preference Management for your
customers.
The preference specialist can use the app to enter and manage exceptions for customers for each
administrative unit. If there is no exception for a customer, the properties predefined for the administrative unit
for creating and sending issues for long-term suppliers’ declarations are used.
You can define properties both for customers and products for a customer. In principle, the levels with more
detailed entries are given priority.
Features
Manage preference properties for a customer for each administrative unit

You can define the following properties for each administrative unit and customer:
• Define Issue Relevance

You can use issue relevance to control whether an issue for long-term suppliers’ declarations is to be
created for a customer or for products for the customer. You can choose from the following values:
• Preset
You do not want to define an exception. The default issue relevance of the administrative unit is used.
• Yes
Customers/products for a customer are relevant for issue.

• No
Customers/products for a customer are not relevant for issue.
In the list view, the issue relevance you defined is interpreted and displayed by the issue relevance status.
• Status of Issue Relevance

The issue relevance status determines whether a customer receives requests for long-term supplier’s
declarations from your administrative unit and which products can be issued for your customers. This
results from the issue relevance for the following:
• The administrative unit
• The customer
• The customer's products
The following cases can occur:
• Yes
The administrative unit issues the following for all of the customer's products:
• Yes, with Exceptions
The administrative unit always issues for all of the customer's products. However, certain products of
the customer are excluded from the long-term suppliers’ declaration.
• No
The administrative unit does not issue products to the customer. The supplier does not receive a long-
term supplier’s declaration.
• No, with Exceptions
The administrative unit does not issue any of the customer's products. However, certain products of
the customer are issued. The customer can only receive a long-term suppliers’ declaration with these
products.
Overview Status of Issue Relevance

Issue Relevance at Adminis Issue Relevance at Supplier Issue Relevance at Product
Status of Issue Relevance trative Unit Level Level Level
Yes Yes Preset Preset*
Yes Yes Yes Yes*
Yes No Yes Yes*
Yes, with Exceptions Yes Preset No**
Yes, with Exceptions Yes Yes No**
Yes, with Exceptions No Yes No**
No No Preset Preset*
No No No No*
No Yes No No*
No, with Exceptions No Preset Yes***
No, with Exceptions No No Yes***
No, with Exceptions Yes No Yes***
Legend
* This setting is optional and an entry is not mandatory.
** At least one product of the customer must be specified at product level with issue relevance No”.

*** At least one product of the customer must be specified at product level with issue relevance Yes.
• Define Communication Method

You can use the communication method to control how you want to communicate with your customer.
• Preset
You do not want to define an exception. The default communication method of the administrative unit
is used.
• E-Mail
You want to send the long-term supplier’s declaration by e-mail.
• Postal Service
You want to print the long-term supplier’s declaration and send it by post.
 Note
If you have defined the communication method E-Mail , you have to define the e-mail address of the
employee responsible for the preference of your customer in the business partner master of the LTSD
recipient.
• Specify LTSD Recipients

The LTSD recipient is the business partner to whom you want to issue a long-term suppliers’ declaration.
If the customer for whom you define the preference properties differs from the LTSD recipient, you specify
a different business partner as the LTSD recipient. To do this, select the value Customer Is Not LTSD
Receiver and enter the new LTSD recipient. In the future, invoice documents for this customer will be
included in long-term suppliers’ declarations for the new LTSD recipient.
If one or more customers are assigned to the same LTSD recipient, the additional customers are displayed
in the preference properties of this customer. This means that all invoice documents for this customer and
all additional customers are grouped together in one long-term suppliers’ declaration.
• Create Notes
You can create notes to document your decisions.
• Delete preference properties for a customer for each administrative unit
You can delete the exceptions of the preference properties for your customers.
 Note
If you delete the stored preference properties in the app, the predefined properties of the administrative
unit are used for all subsequent future processes, such as issue and re-issue.
• Desktop
6.2 Preference Determination

6.2.1 Aggregation
6.2.1.1 Determination of Preferential Origin of Externally

Procured Products (Aggregation)
If you purchase products from suppliers, you can have several long-term supplier’s declarations with different
preference statements for the same product. Your products can be both of mixed origin and from external
procurement.
Based on long-term supplier’s declarations from suppliers and goods receipts,
• for each product in the product master, as long as the product has mixed or external procurement and
released or canceled LTSDs or goods receipts or canceled goods receipts exist,
• each preference model of the administrative unit,
• each active agreement of the administrative unit,
a preferential origin is determined by aggregation.
The result of aggregation is stored in the preference statements of the product master and is used for the
following:
• Preference determination, if the product is a component for a product produced in-house,

• Issuing a long-term supplier’s declaration for customers,
• The transfer of preference statements to feeder systems to create shipment-related proof of origin.
 Note
To determine the preferential origin of externally procured products (aggregation), regularly schedule
transaction Aggregation of LTSDs (transaction /SAPSLL/LTSD_AGG).
Method of Aggregation
In aggregation, LTSDs and goods receipts are taken into account as follows for a product that is aggregated on
the specified key date:
• Products in the LTSDs that were released after the key date,
• Products in the LTSDs that were canceled after the key date,
• Goods receipt purchase orders that were either transferred from the feeder system after the key date or
were canceled after the key date.
Goods receipts are valuated based on existing LTSDs under the following conditions:
• The entry date of the goods receipt is within the validity period of an LTSD,
• The LTSD is valid for the goods supplier based on the LTSD issuer,
• The goods receipt is relevant for the administrative unit.
If no products exist in LTSDs for the valuation of a product in the goods receipt, the product is valuated as not
eligible for preference in the goods receipt.

 Note
Preference statements for products in LTSDs of the same LTSD issuer are determined by the most recent
issue date based on the issue date if validity periods overlap.
The valuated product of a goods receipt is taken into account in aggregation for the period of the product
retention period. The product retention period starts with the entry date of the goods receipt.
The preference statements for a product result from the worst preference statement of all LTSDs and goods
receipts that exist for the product in accordance with their validity periods.
For products of mixed origin, the worst preference statement is also determined from preference
determination (determination of the preferential origin of products produced in-house) together with the
preference statement from aggregation.
Prerequisites
• You have configured the Preference Management business scenario.

• You have defined the product retention period.
• You have released LTSDs from your suppliers.
• You transfer goods receipts from your feeder systems.
6.2.2 Calculation - Products
6.2.2.1 Perform Preference Determination - Products
With this app, preference specialists can perform preference determination for products.
6.2.2.2 Perform Preference Determination for a Product
With this app, preference specialists can perform preference determination for a product.
6.2.2.3 Perform Preference Determination for New

Products
With this app, preference specialists can perform preference determination for new products.

6.2.2.4 Display Preference Determination Logs
With this app, preference specialists can display preference determination logs for products.
6.2.2.5 Display Preference Determination Logs from

Simulation
With this app, preference specialists can display preference determination logs for products from the
simulation.
6.2.3 Calculation - Documents
6.2.3.1 Displaying the Worklist
With this app, preference specialists can display the worklist for configurable BOMs.
The worklist for configurable BOMs contains entries for all order-related BOMs of configurable products that
you have transferred from the feeder system to Preference Processing for preference determination. Based on
the status of the entries in this worklist, you can determine which process steps the system has already carried
out for calculating preference statements for configurable BOMs.
In addition to the display of transferred configurable BOMs and their processing status for automated process
handling, you can perform the following steps manually:
• Start preference determination

• Start preference determination again
Key Features
• View entries for transferred BOMs, including their processing status, in the worklist.
You can see transferred configurable BOMs and determine their processing state based on the following
statuses:
• 10 Ready for Determination
All configurable BOPs that you have transferred from the feeder system to Preference Processing have
status Ready for Determination. The system can select all entries with this status for the next
determination run. If you want to start preference determination for specific BOMs quickly, you can
select the items with this status.

• 20 Determination Performed
All configurable BOMs that the system has already processed automatically or for which you started
preference determination manually are set to status Calculation Performed. If you have configurable
BOMs with this status and they have changed parameters, you can start determination again.
• 30 Result Transferred to Feeder System
If the system has already sent the result of preference determination for a configurable BOM back to
the feeder system, the worklist item is set to status Result Transferred to Feeder System in Preference
Processing.
• 90 Marked for Deletion
If the deletion was initiated in the feeder system, the entries in the worklist of the GTS system are set to
the status 90 Marked for Deletion. When you start the transaction Display Worklist of Configured BOMs
in the GTS system, the Delete button is displayed. You can use this button to delete the entries with
status 90. The entries with other statuses are ignored.
• Start preference determination
You have manually transferred a configurable BOM from the feeder system and want to generate a
preference statement quickly, without waiting for the results of the periodically scheduled background
processing. Preference Processing lets you start preference calculation directly.
• Start preference determination again
If parameters have changed since the last BOM transfer for preference calculation you can start preference
determination again. The parameters that can make this step necessary include:
• New long-term supplier’s declarations entered in the system with a positive preference statement
• Change to a tariff number due to originally incorrect classification
• You can see worklist entries in accordance with the following selection criteria for the feeder system:
• Logical System
• Reference Application
• Document Number
• Item
• You can also select and display entries according to their Status.
• When you choose Execute, the system displays the document items that match your search criteria and
contain configurable BOMs.
• When you set the selection flag for a line in the list, you can carry out the following functions:
• For individual list items that have status Ready for Determination or Determination Performed, you can
choose Calculate Worklist Item to start preference determination. The system opens the selection
screen for preference determination and adopts the known data form the worklist. You can restrict the
selection criteria further and choose Execute.
• When BOPs have determination status Calculated, you can transfer the status for preference
determination for each item to the feeder system by choosing Transfer Determination Status. The
system determines the relevant data from the worklist in the GTS system and sets the determination
status in the worklist for configurable BOMs in the feeder system.
Under the default settings, the system sends the determination status to the feeder system as soon as
preference determination for a configurable BOM is completed. If the corresponding entry is blocked in
the feeder system, the status transfer is canceled and the calculation status in the GTS system
remains Calculated. Therefore, you can send the determination status to the feeder system again for
entries with this status in the worklist. To see the details of why the transfer terminated after
preference terminated, call transaction code SM58.

• If you want to display the results of preference determination for entries with status Calculated choose
Display Result. The system uses the data from the worklist as the selection criteria and goes directly to
the Display of Document-Specific Results. See Display Preference Determination Results [page 76].
• You can also see the results of preference determination in the display of document-specific results in
preference determination. See: Display Preference Determination Results [page 76]
6.2.3.2 Perform Preference Determination
With this app, preference specialists can perform preference determination for documents.
6.2.3.3 Display Preference Determination Logs
With this app, preference specialists can display prices for documents.
6.2.3.4 Display Preference Determination Logs from

Simulation
With this app , preference specialists can display preference determination logs from the simulation for
documents.
6.2.3.5 Display Preference Determination Results
With this app, preference specialists can display the results of preference determination on a document-
specific basis.
As a rule, you have to document the results of preference determination in customs logs for the customs
authorities. These customs logs contain the detailed results for each determination run, listed by product. You
can also display the results of preference determination for specific documents in Preference Management.
This function lets you select orders from the feeder system, for which the system determines the preference
results for the document items.
Prerequisites
You have already performed preference determination for the relevant order items.

Key Features
• You can display the document-specific results of preference determination for each feeder system.
• You can also limit the search results by entering selection criteria for the Document number of the order
and Item number from the feeder system.
• When you choose Execute, the system lists an overview of the parameters for preference determination for
each document and document item, for example:
• Preference model
• Details for the preference model, such as plant and plant group
• The system lists the preference statement in accordance with the results from preference determination,
together with the relevant details:
• Preference Indicators
• Aggregation result of long-term supplier’s declarations
• Statement whether the preference result is price-dependent or whether the system determined the
preference result based on conditions
• Threshold value (where applicable)
6.3 Master Data
6.3.1 Master Data - Preference
6.3.1.1 Displaying BOMs
With this app, preference specialists can display bills of material.
You can use this function to display all the BOMs that you have transferred from your feeder system for
preference determination and legal control of re-exports. You can display both static and order-related BOMs
for configurable products for preference processing. The system transfers the information indicating whether
the BOM is multilevel in both cases and displays this structure information of the BOM. The BOM display also
contains details for the individual BOM components. You can use the BOM information to display the data that
is used in preference determination to determine the preference eligibility of a product or for legal control of the
re-export-relevant share values of a product.

Prerequisites
You transferred BOMs from your feeder system to SAP GTS, edition for SAP HANA.
Key Features
• You can display the transferred BOMs in this app.

• You can display the BOMs for each logical feeder system and product.
• You can also use the following criteria to make your search more precise:
• BOM Usage
• Alternative BOM
• If you specify a preference model in preference processing, you can enter additional selection criteria
depending on the model.
Plant-based or cross-plant preference model
• Plant or plant group
• Explosion method for the BOM
Order-related preference model
• Application
• Document number from the feeder system
• Item of the product with configurable BOM in the document in the feeder system
• When you choose Execute, the system displays the BOMs that match your search criteria.
• If you selected only one product, and the product only has one BOM, the system displays the BOM
overview directly.
• If you selected multiple products, the system displays an overview list of the BOMs for the products along
with general BOM information, such as:
• Product number
• Product description
• Bill of material number
• Alternative bill of material
• Bill of material usage
• Low-level codes of the bills of material
You can select a product from the overview list for the system to display the details.
 Note
To simplify the display, you can hide the overview list that contains all the products matching your
selection criteria and show it again, as required.
• You can display additional details for each BOM component. To do so, select the required row and choose
Details. The detail display contains specific information about the component and its position within the
BOM, for instance:
• BOM structure information

• BOM level
• Low-level codes of the transferred bills of material
• Sequence number of the BOM level
• Sequence number of the component on the next highest BOM level on which the component is
dependent
• BOM component details, such as:
• Quantity used on the BOM level
• Net price
• Tariff number
• If you click the product number of a displayed BOM, the system forwards the product data for the BOM.
You can display general product data as well as any classification data and preference-specific product
data. You can also switch to change mode.
 Note
For more information about the product data you can display and its significance, see Manage
Products [page 83] app.
• To return to the BOM overview, choose Back.
6.3.1.2 Display Preference Data
With this app, preference specialists can display preference data for products.
Functional Scope
You can restrict the display for the Product Selection and General Data areas to display only the data that is
relevant for you.
Product Selection
• Logical System Group

Enter the group of logical systems here.
• Product
Enter a range of products you want to display.
• Validity Period
Enter the validity area to be displayed.
• Agreements
Enter the agreements to be displayed.
• Preference Indicator
Enter the internal preference indicator to be displayed.
General Data

• Product Created On
• Product Changed On
• Product Created By
• Product Changed By
• Product Status
6.3.1.3 Displaying Prices
With this app, preference specialists can display prices for products.
Key Features
On the next screen, you see the Product Selection and General Data areas, which you can use to restrict the
display.
Product Selection
• Logical Systems Group

Enter the group of logical systems here.
• Product
Enter a range of products you want to display.
• Price Type
Enter the price types to be displayed.
General Data
• Product Created On
• Product Changed On
• Product Created By
• Product Changed By
• Product Status
6.3.1.4 Displaying Procurement Indicators
With this app, preference specialists can display the procurement indicators.
Determination of the preferential origin of a product depends on its procurement type. You can see the
procurement indicators for all BOP components at product level.
Preference Management distinguishes between the following procurement types:
• In-house production: Finished products that you produce completely at your company

• External procurement: Trading goods that you purchase from a supplier and sell unchanged to a customer
• Finished products with mixed origin: Consist of externally procured parts and parts from in-house
production
• Group-internal purchase: Products that you purchase from a plant group within your corporate group.
Depending on the procurement indicators, the system calculates whether it is sufficient for you to request and
enter the supplier-based long-term supplier’s declarations to make a preference statement for the
corresponding finished product based on the aggregation results. If the products are from in-house production
or mixed origin with at least one part produced in-house, you have to perform preference determination to
determine the preference authorization of a product in addition to requesting, entering, and aggregating long-
term supplier’s declarations for externally procured BOM components.
Prerequisites
You have activated the transfer of procurement indicators to the system for Global Trade Services in the feeder
system plug-in.
Key Features
• Enter the selection criteria to define the product and feeder system for which you want to display the
procurement indicators.
• When you choose Execute, the system displays the procurement indicators at product level, as well as
other product details.
6.3.1.5 Displaying Country for Country Groups and

Agreements
With this app, preference specialists can display the country assignment to country group and agreements.
You can display the assigned country groups and relevant preference agreements for a country. The system
also displays which checks are active. You can also see if the country is defined as a member of a country group
in the system and/or whether it is partner to an agreement. If the country is partner to an agreement, the Own
Group field is not selected, indicating a country group with which the entered country has a preference
agreement.
In addition, you see the setting status with regard to the relevant preference agreements in the Export
Preference and Import Preference fields.

Key Features
• In the list view, under Data Selection, you can define a Country of Departure and a Country Grouping.
6.3.1.6 Display Preference Rules
With this app, preference specialists can display preference rules for agreements.
In Preference Management, you can create preference rules manually or upload them to your system from a
data provider. You can display all the preference rules for a given agreement in an overview. The system also
lists the countries to which the corresponding preference agreement applies in the overview.
Prerequisites
The preference rules are defined in the system. You have either uploaded these preference rules from a data
provider as master data or defined them manually, in Customizing for Preference Management.
You have also defined country groups in the general settings in Customizing and assigned countries to them in
master data maintenance.
Procedure
• Use the input help to select the preference agreement whose preference rules you want to display.
• The system displays an overview with the following levels:
• In the Preference Zones area, the system lists all the countries for which the preference agreement and
its rules are valid.
• In the Preference Rules area, the system lists the existing preference rules for each tariff number.
• To display details for a preference rule, select the appropriate line and choose Details.
With this app, preference specialists can manage business partners.

With this app, preference specialists can manage products.

7 Intrastat
You use Intrastat declarations for the statistical recording of goods movements that cross national borders
between member states of the European Union.
You can create Intrastat declarations for the following countries:
• AT (Austria)
• BE (Belgium)
• BG (Bulgaria)
• CY (Cyprus)
• CZ (Czech Republic)
• DE (Germany)
• DK (Denmark)
• EE (Estonia)
• ES (Spain)
• FI (Finland)
• FR (France)
• GB (United Kingdom)
• GR (Greece)
• HR (Croatia)
• HU (Hungary)
• IE (Ireland)
• IT (Italy)
• LT (Lithuania)
• LU (Luxembourg)
• LV (Latvia)
• NL (Netherlands)
• PL (Poland)
• PT (Portugal)
• RO (Romania)
• SE (Sweden)
• SI (Slovenia)
• SK (Slovakia)
7.1 Managing Providers of Information
With this app, Intrastat specialists can create, change, and display providers of information to then be able to
declare Intrastat-relevant data to the authorities of a country.

84 PUBLIC Intrastat
A country of declaration and a business partner of the category Organization and the role Provider of
Information (technical name of role SLLPOI) must always be assigned to a provider of information.
To enter data on a contact person, such as name, address, and e-mail address, you must create a business
partner of the Person category and Person Responsible role (technical name of role SLLSTL).
 Note
The address data and the VAT registration number of the provider of information must be entered in the
business partner of the category Organization and role Provider of Information.
Key Features
• Create providers of information

• Display providers of information
• Entering the data for the provider of information, such as contact data
• Enter data about the basic settings for the Intrastat declarations of the provider of information
• Delete providers of information
7.2 Managing Intrastat Declarations
With this app, Intrastat specialists manage your Intrastat declarations for your providers of information and to
enter the required statistical data of a month for the following transactions:
• Receipts to your company from other member states of the European Union
• Dispatches from your company to other member states of the European Union
Key Features
• Creating Intrastat declarations manually

• Entering receipts to your company from other member states of the European Union
• Entering dispatches from your company to other member states of the European Union
• Create Intrastat declarations in a country-specific file format
 Note
The required statistical data can either be entered manually or created based on integration in the feeder
system.

Intrastat PUBLIC 85
7.3 Manage Business Partners
With this app , Intrastat specialists can create business partners with the following categories and roles:
• Category Organization and role Provider of Information (technical name SLLPOI)

• Category Person and role Administrator (technical name SLLSTL)
• Category Organization and role Third Party Declarant (technical name SLLTPD)
You can assign these business partners in the Manage Providers of Information app.

86 PUBLIC Intrastat
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Important Disclaimers and Legal Information PUBLIC 87
www.sap.com/contactsap
© 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. The information contained herein may be changed
without prior notice.
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 are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP 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.
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. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Sap GTS 2023

Uploaded by

Copyright:

Available Formats

Sap GTS 2023

Uploaded by

Document Information

Original Title

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

Sap GTS 2023

Uploaded by

Copyright:

Available Formats

User Guide | PUBLIC

SAP Global Trade Services, edition for SAP HANA

THE BEST RUN

1 SAP Global Trade Services, edition for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Products and Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

SAP Global Trade Services, edition for SAP HANA

SAP Global Trade Services, edition for SAP HANA

SAP Global Trade Services, edition for SAP HANA

Product SAP Global Trade Services, edition for SAP HANA

Version 2020 SP01

Based On Required Product Versions:

• SAP S/4HANA FOUNDATION 2020

Documentation Published September 2021

• Products and Classification

SAP Global Trade Services, edition for SAP HANA

2.1.1 Manage Products

SAP Global Trade Services, edition for SAP HANA

With this app, classification specialists can manage products.

2.1.1.2 Manage Customs Commercial Descriptions

2.1.1.3 Compare Customs Commercial Descriptions

2.1.2 Analyze Products

2.1.2.1 Display Products

With this app, classification specialists can display products.

2.1.2.2 Display Product Catalog Based on Customs

2.1.2.3 Display Products with Authority Codes

SAP Global Trade Services, edition for SAP HANA

2.1.2.3.2 Display Products - Re-Export

With this app, classification specialists can display products in re-exports.

2.1.3 Manage Worklist

2.1.3.1 Manage Worklist for Products

2.1.3.2 Manage Products from Worklist

SAP Global Trade Services, edition for SAP HANA

With this app, classification specialists can reclassify products manually.

2.2.1.2 Reclassify Products XML-Based

With this app, classification specialists can reclassify products XLM-based.

2.2.1.3 Classify Products

With this app, classification specialists can classify products.

2.2.1.4 Delete Product Classification

With this app, classification specialists can delete a product classification.

2.2.1.5 Check Product Classification

With this app, classification specialists can check a product classification.

2.2.2 Legal Control

2.2.2.1 Reclassify Products Manually - Legal Control

SAP Global Trade Services, edition for SAP HANA

2.2.2.3 Classify Products - Legal Control

2.2.2.4 Delete Products - Legal Control

2.2.2.5 Check Product Classification

With this app, classification specialists can check a product classification.

2.2.3 PGA Codes

2.2.3.1 Update Products - Authorization Codes

2.2.3.2 Change PGA Data for Products

SAP Global Trade Services, edition for SAP HANA

2.2.4 NCLO Codes

2.2.4.1 Assign NCLO Codes to Products

2.2.4.2 Change NCLO Codes for Products

2.3 Master Data - Classification

2.3.1 Commodity Codes

2.3.1.1 Manage Commodity Codes

With this app, classification specialists can manage commodity codes.