H42 BB Config Guide GTS

SAP ECC 6.00 August 2006 English

H42: Configuration SAP Global Trade Services (GTS) Building Block Configuration Guide

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

H42: Configuration Global Trade Services (GTS)

Copyright

© Copyright 2006 SAP AG. 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 AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. ®

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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 AG

Page 2 of 113

SAP Best Practices


Icons Icon

Meaning Caution Example Note or Tip Recommendation Syntax

Typographic Conventions Type Style

Description

Example text

Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG

Page 3 of 113

SAP Best Practices


Contents H42: Configuration Global Trade Services (GTS) ..................................................................... 8 1

Purpose .............................................................................................................................. 8

2

Preparation ......................................................................................................................... 8 2.1

3

2.1.1

Implementing SAP Notes ..................................................................................... 8

2.1.2

Adobe Document Services (ADS) ....................................................................... 9

Configuration ERP system/client ........................................................................................ 9 3.1

SD Basic Settings in mySAP ERP ........................................................................... 9

3.1.1

Defining Billing Document Type ........................................................................... 9

3.1.2

Defining Blocking Reasons for Billing Document Type ..................................... 10

3.1.3

Defining Sales Document Type ......................................................................... 10

3.1.4

Defining Item Categories ................................................................................... 11

3.1.5

Assigning Item Categories in SAP ERP ............................................................ 11

3.1.6

Specifying Copy Control for Deliveries .............................................................. 12

3.1.7

Assign Schedule Lines....................................................................................... 12

3.2

MM Basic Settings in mySAP ERP ........................................................................ 14

3.2.1

Defining Purchasing Document Type YNB ........................................................ 14

3.2.2

Assigning Partner Schemas to Document Types .............................................. 14

3.2.3

Defining Transportation Zone for Customer in Liberia ....................................... 15

3.3

Settings in GTS Plug In in mySAP ERP ................................................................ 16

3.3.1

Implementing User Exit ...................................................................................... 16

3.3.2

Configure Control Settings for Transfer ............................................................. 17

3.3.3

Activate BADIs for Transfer of Documents (ERP) ............................................. 19

3.3.4

Preference: Control Settings for Bill of Materials Transfer ................................ 19

3.3.5

Control Settings for Vendor Based Vendor Declaration Worklists .................... 20

3.4

4

Prerequisites ............................................................................................................ 8

System Communication in mySAP ERP ................................................................ 21

3.4.1

Defining Logical System for GTS (ERP) ............................................................ 21

3.4.2

Checking RFC User (ERP) ................................................................................ 21

3.4.3

Maintaining RFC Destinations for RFC Calls (ERP) .......................................... 22

3.4.4

Maintaining RFC Destinations for Method Calls (ERP) ..................................... 23

3.4.5

Maintaining the ALE Distribution Model (ERP) .................................................. 23

3.4.6

Activating Change Pointers (ERP) ..................................................................... 24

Configuration in GTS system/client .................................................................................. 25 4.1

System Communication in SAP GTS ..................................................................... 25

4.1.1

Creating RFC User ............................................................................................ 25

4.1.2

Defining the Logical Systems ............................................................................ 25

4.1.3

Assigning the Logical System ............................................................................ 26

4.1.4

Maintaining RFC Destination for RFC Calls (SAP GTS) ................................... 26

© SAP AG

Page 4 of 113

SAP Best Practices


4.1.5

Maintaining RFC Destination for Method Calls (SAP GTS)............................... 27

4.1.6

Defining Logical System Group (SAP GTS) ...................................................... 27

4.1.7

Assigning Logical Systems to a Group of Logical Systems (SAP GTS) ........... 28

4.2

General Settings in GTS ........................................................................................ 29

4.2.1

Maintaining Time Zones (SAP GTS) ................................................................. 29

4.2.2

Number Ranges ................................................................................................. 30

4.2.2.1

Defining Number Ranges for Business Partners ...................................... 30

4.2.2.2

Defining Number Ranges for Product Masters ......................................... 31

4.2.2.3

Defining Number Ranges for Licenses ..................................................... 31

4.2.2.4

Defining Number Ranges for Customs Documents .................................. 32

4.2.2.5

Defining Number Ranges for Supplementary Customs Declaration......... 33

4.2.2.6

Defining Number Ranges for Internal Package Numbers ......................... 34

4.2.2.7

Defining Number Ranges for EDI Messages ............................................ 34

4.2.2.8

Defining Number Ranges for Vendor Declarations ................................... 35

4.2.2.9

Defining Number Ranges for Preference Models ..................................... 35

4.2.3

Organizational Structure .................................................................................... 36

4.2.3.1

Maintaining Business Partner Roles for foreign trade .............................. 36

4.2.3.2

Maintaining Business Partners: Foreign Trade Organizations ................. 39

4.2.3.3

Maintaining Business Partners: Employee Customs Manager ................. 39

4.2.3.4

Maintaining Business Partners: Legal Units ............................................. 40

4.2.3.5

Assigning Company Codes ....................................................................... 41

4.2.3.6

Assigning Plants ........................................................................................ 42

4.2.3.7

Defining Organizational Structure for Customs and Foreign Trade .......... 45

4.2.4

Legal Regulations .............................................................................................. 45

4.2.4.1

Defining Legal Regulations ....................................................................... 45

4.2.4.2

Defining Procedure for Determining Active Legal Regulations ................. 47

4.2.4.3

Activating Legal Regulations ..................................................................... 48

4.2.4.4

Defining Groups for Value and Quantity Depreciation of Licenses........... 49

4.2.4.5

Maintaining Tariff Code Numbers ............................................................. 49

4.2.4.6

Maintaining Commodity Codes ................................................................. 51

4.2.4.7

Defining External Country Codes for Data Upload ................................... 52

4.2.4.8 Server)

Activating HTTP Services for Document Storage (Using SAP Content 52

4.2.5

Partner Structure................................................................................................ 52

4.2.5.1

Define Groups of Partner Functions / Assign Partner Function ................ 52

4.2.5.2

Grouping Partner Functions ...................................................................... 53

4.2.5.3

Assigning Partner Functions ..................................................................... 54

4.2.6

Numbering Schemes ......................................................................................... 55

4.2.6.1

Defining Numbering Scheme of Export Lists ............................................ 55

4.2.6.2

Assigning Numbering Scheme of Export List for License Maintenance ... 56

© SAP AG

Page 5 of 113

SAP Best Practices 4.2.6.3 4.3


Assigning Numbering Scheme for License Determination ....................... 57

Compliance Management ...................................................................................... 57

4.3.1

General Settings ................................................................................................ 57

4.3.1.1

Defining Document Types ......................................................................... 57

4.3.1.2

Activating Document Type ........................................................................ 58

4.3.1.3

Assigning Document Types ...................................................................... 59

4.3.1.4

Defining Item Categories ........................................................................... 60

4.3.1.5

Activating Item Category ........................................................................... 61

4.3.1.6

Assigning Item Categories ........................................................................ 62

4.3.2

Legal Control Service......................................................................................... 64

4.3.2.1


4.3.2.2

Defining Control Procedures for Text Comparison – Export ..................... 64

4.3.2.3

Assigning Control Procedure for Text Comparison to Export Lists ........... 65

4.3.2.4

Assigning Determination Procedure for Active Legal Regulations ........... 66

4.3.2.5

Defining Determination Scheme to Automatically Determine License Types 66

4.3.2.6

Defining Control Settings for License Determination Service ................... 67

4.3.2.7

Defining License Types ............................................................................. 69

4.3.3

Embargo Check Service .................................................................................... 71

4.3.3.1

Activating Document Type ........................................................................ 71

4.3.3.2

Activating Item Categories ........................................................................ 71

4.3.3.3


4.3.3.4

Assigning Determination Procedure to Determine Active Legal Regulations 73

4.3.3.5

Activating the Embargo Service Control ................................................... 73

4.3.4

Sanctioned Party List Screening ........................................................................ 74

4.3.4.1

Activating Business Partner at Business Partner Role Level ................... 74

4.3.4.2


4.3.4.3

Assigning Determination Procedure to Determine Active Legal Regulations 75

4.3.4.4

Defining Control Procedure for Address Comparison ............................... 76

4.3.4.5

Controlling Sanctioned Party List Screening ............................................. 77

4.4

Customs Management ........................................................................................... 80

4.4.1

Prerequisite Settings in ERP ............................................................................. 80

4.4.2


4.4.3

General Settings for Customs Management ..................................................... 80

4.4.3.1

Defining Country Groups ........................................................................... 80

4.4.3.2

Defining Conditions and Output Parameters for Messages (PPF Actions) 80

4.4.3.3

Define Message for Communication Process ........................................... 81

4.4.3.4

Control Settings for Communication Processes ....................................... 81

© SAP AG

Page 6 of 113

SAP Best Practices


4.4.3.5

Assigning Document Type at Feeder System Group Level ...................... 82

4.4.3.6

Assigning Item Category at Feeder System Group Level ......................... 83

4.4.3.7

Assigning Packaging Material Type at Feeder System Group Level........ 85

4.4.3.8

Defining Default Data for Date Fields ....................................................... 85

4.4.3.9

Defining Determination Procedure for Defaulting Data ............................. 85

4.4.3.10

Defining Default Data for Partners ............................................................ 86

4.4.3.11

Maintaining Code Lists .............................................................................. 87

4.4.4

Authorization Management ................................................................................ 87

4.4.5

Application Settings (GTS) ................................................................................ 88

4.4.5.1

Maintaining Business Partner Person Responsible for Processing .......... 88

4.4.5.2 Number

Creating Customs Offices and Assigning to Official Customs Office 88

4.4.5.3

License Master: ......................................................................................... 89

4.4.5.4

Maintaining Trader Identification Number (TIN) ........................................ 92

4.4.5.5

Maintening Business Identification Number (BIN) .................................... 92

4.4.5.6 Message Determination Transit & Message Determination Customs Declaration 93 4.4.5.7 4.4.6

Determining Printer ................................................................................... 94

ALE Settings ...................................................................................................... 95

4.4.6.1

Maintaining EDI Port Definition (GTS) ...................................................... 95

4.4.6.2

Maintaining EDI Partner Profile / Header .................................................. 95

4.5

Risk Management .................................................................................................. 97

4.5.1

Defining Groups of Partner Functions ............................................................... 97

4.5.2


4.5.2.1

Defining Country Groups ........................................................................... 98

4.5.2.2

Assigning Countries to Preference Zones ................................................ 98

4.5.2.3

Defining Legal Regulation ......................................................................... 99

4.5.2.4

Defining Determination Procedure for Active Legal Regulations .............. 99

4.5.2.5

Activating Legal Regulations ................................................................... 100

4.5.3

Preference Processing Service ....................................................................... 100

4.5.3.1

Organizational Structure ......................................................................... 100

4.5.3.2

Activation ................................................................................................. 101

4.5.3.3

Preference Agreement ............................................................................ 103

© SAP AG

Page 7 of 113

SAP Best Practices


H42: Configuration Global Trade Services (GTS) 1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually. If you do not want to configure manually and prefer an automated installation process using eCATTs and BC Sets, use the SAP Best Practices Installation Assistant.

SAP Best Practices for High Tech GTS is set up in two independent clients: One client represents in this case the feeder system for Master Data and Order Processing (ERP client), the other client represents the SAP Global Trade Services system where Compliance Management is processed (GTS client). Therefore this guide is also divided up in two parts: o

Configuration in ERP system/client: Here the SD and MM settings for example the creation of a new order type and billing type are described. Also the settings for system connectivity and the necessary settings for transferring documents to GTS have to be done in the ERP client.

o

Configuration in GTS system/client: Here the GTS general settings (Connectivity, organizational data and so on) as well as the necessary configuration settings for the parts Compliance, Customs and Risk are described.

2 Preparation 2.1 Prerequisites Building Blocks Before you start installing this building block, you must install prerequisite building blocks. For more information, see the Building Block Prerequisites Matrix for High Tech. Only install the mentioned building blocks in the SAP ERP system or client. They are not required for the GTS system or client. For the GTS client a copy of client 000 after the installation of the GTS AddOn is sufficient.

2.1.1

Implementing SAP Notes

Use The following SAP Notes need to be implemented for GTS 7.0 Support Package 700 and PI BASIS 2005_1_700.

Procedure Implement the following SAP Notes (see E00 Installation Guide for Details): ERP Plug – In: 579357 Plug-IN: Area: SD sales order processing 944614 GTS: Plugin: Preference indicator is not set 829932 PLUGIN: Preference indicator redistribution GTS

© SAP AG

Page 8 of 113

SAP Best Practices


GTS Add-On: 936562 Preference: Component with incorrect price and quantity 946576 Update termination during cross-plant determination – prerequisite for 935854 934139 Different preference (mass costing and unit costing) – prerequisite for 935854 935854 Update termination: SAPSQL_ARRAY_INSERT_DUPREC 942889 Preference: SQL array insert, duplicate records 940046 Preference: Negative statement due to missing bill of products 930872 Preference: Bill of product display - Plant and plant group 946703 Preference KMAT: Component with incorrect preference indicator 947422 Incompleteness check for item is incorrect 972003 Incorrect Display on tab page Preference EU and NAFTA

2.1.2

Adobe Document Services (ADS) Be aware that you need to have set up ADS (Adobe Document Services) to be able to display the forms for Customs Management and Risk Management (customs ducuments and vendor declarartions). A connection to ADS must exist from you GTS system or client. See note 682619 for details of the ADS configuration.

3 Configuration ERP system/client 3.1 SD Basic Settings in mySAP ERP 3.1.1

Defining Billing Document Type

Use For the GTS sales order process a new billing document type is created. YHF8 is a copy of F8.

Procedure 1. Access the activity using one of the following navigation options: Transaction Code

VOFA

IMG Menu

Customizing  Sales and Distribution  Billing  Billing Documents  Define Billing Types

2. Choose Define Billing Types. 3. On the Change View “Billing: Document Types”: Overview screen, choose New Entries and maintain the following data: Field name

Description

User action and values

Billing type

YHF8

Description

Invoice GTS

© SAP AG

Note

Page 9 of 113

SAP Best Practices

Field name


Description


No.range int.assgt.

19

SD document categ.

U

Transaction group

8

Output determination procedure

Note

V10000

Application

V3

Output Type

RD00

Header Partners

FK

Item Partners

FP

Text DetermProcedure

03

Text determ.proc.item

04

4. Save your entries.

3.1.2

Defining Blocking Reasons for Billing Document Type

Use For the new billing document type the blocking reasons have to be assigned.


SPRO

IMG Menu

Customizing  Sales and Distribution  Billing  Billing Documents  Define Blocking Reason for Billing

2. Choose Assign blocking reasons to billing types. 3. On the Change View “Billing: Blocking Reasons”: Overview screen, choose New Entries and maintain the following data: Field name

Description


Block

Note

01

Billing type

YHF8


3.1.3

Defining Sales Document Type

Use Before you can call the Legal Control – Export, Legal Control – Import, Sanctioned Party List Screening services, Transit Procedure Service, or Customs Processing Service, you have to transfer the document data to SAP Global Trade Services (SAP GTS). You need to specify which document types of a specific application level you want to transfer from the backend system to SAP GTS so that the relevant customs documents can be created. A sales document type is created only for the GTS scenarios. YOR is a copy of OR.

© SAP AG

Page 10 of 113

SAP Best Practices



VOV8

IMG Menu

Customizing  Sales and Distribution  Sales  Sales documents  Sales document header  Define sales document type

2. On the Change View “Maintain sales order types”: Overview screen, select sales order document type OR and choose Copy as…: Field name

Description


Sales document type

Note

YOR

Description

Standard order (GTS)

3. Confirm the dialog box and save your entries.

3.1.4

Defining Item Categories

Use To control what services the system executes for the customs document, you define the customs item categories involved in the services. An own item category is created for this scenarios as follows:

Procedure 1. Access the activity using the following navigation option: Transaction Code

SPRO

IMG Menu

Customizing  Sales and Distribution  Sales  Sales documents  Sales document item  Define item categories

2. On the Change View “Maintain item categories”: Overview screen, select item category TAN, and choose Copy as…: Field name Sales document type Description

Description


Note

YTAN Standard item (GTS)

3. Confirm the dialog box. 4. Save your entries.

3.1.5

Assigning Item Categories in SAP ERP

Use You can specify what item categories the system proposes during document processing for each sales document type and item category group.

Procedure

© SAP AG

Page 11 of 113

SAP Best Practices


1. Access the activity using the following navigation option: Transaction Code

SPRO

IMG Menu

Customizing  Sales and Distribution  Sales  Sales documents  Sales document item  Assign item categories

2. On the Change View “Item category assignment”: Overview screen, select sales document type YOR, item category group NORM, usage blank and replace default item category TAN with YTAN: Field name

Description


Sales document type

YOR

Item category group

NORM

Note

Usage Item category on higher level Default item category

YTAN

Replace TAN


3.1.6

Specifying Copy Control for Deliveries

Use To prevent that deliveries can be created for blocked sales orders you have to assign copy routine 901 as order requirements to the item category YTAN in sales document type YOR

Note 579357 must have been implemented before executing this step. The note covers also copy routines for Picking, Packing and Goods Issue. In this Best Practices Scenario only the copy routine for Deliveries is assigned.


SPRO

IMG Menu

Customizing  Logistics Execution  Shipping  Copying Control  Specify Copy Control for Deliveries

2. On the Display View “Header”: Overview screen, select the entry LF (target) and YOR (source) and double click on Item. 3. On the Display View “Item”: Overview screen choose the entry YTAN and then Details. 4. On the Display View “Item”: Details assign copy routine 901 in field Order requirements. 5. Save your entries.

3.1.7

Assign Schedule Lines

Use

© SAP AG

Page 12 of 113

SAP Best Practices


To be able to deliver the configurable material it’s necessary to assign schedule lines differently to the item types.


SPRO

IMG Menu

Sales and Distribution  Sales  Sales Documents  Schedule Lines -> Assign Schedule Line Categories

2. On the Change View “Assign Schedule Line Categories”: Overview screen, choose New Entries and create the following two entries: Item Category

MRP Type

PropSchdLineCat

ManSchedLineCat

TAC

PD

CT

CN

TAE

PD

CN

CT


© SAP AG

Page 13 of 113

SAP Best Practices


3.2 MM Basic Settings in mySAP ERP 3.2.1

Defining Purchasing Document Type YNB

Use For the GTS scenarios a new purchasing document type is created. YNB is a copy of NB.

Procedure 1. Access the activity using the following navigation options: Transaction Code

SPRO

IMG Menu

Customizing  Materials Management  Purchasing  Purchase Order  Define Document Types

2. On the Document Types Purchase order Change screen, select the entry with type NB. 3. Choose Copy As… 4. Change the new entry according to the following table: Field name

Description


Type

Note

YNB

Doc. type descript.

Document type description

GTS Standard PO

5. Confirm the Specify object to be copied dialog box with copy all. 6. Confirm the information dialog box with Yes. 7. Save your entries.

3.2.2

Assigning Partner Schemas to Document Types

Use In this step you assign the partner schema to document type YNB.


SPRO

IMG Menu

Customizing  Materials Management  Purchasing  Partner Determination  Partner Settings in Purchasing Documents  Assign Partner Schemas to Document Types

© SAP AG

Page 14 of 113

SAP Best Practices


2. On the Change View “Assignment of Partner Schema to Document Type”: Overview screen, search for the purchase order with type YNB. 3. Assign partner schema 0002 (Standard PO) to type YNB. 4. Save your entries.

3.2.3

Defining Transportation Zone for Customer in Liberia

Use In this activity, you can define transportation zones according to the country and depending on your company's needs. Transportation zones represent delivery recipient (ship-to party) regions or delivery shipper (vendor) regions.

You only need to execute this activity if you are implementing the scenarios for Compliance Management.


SPRO

IMG Menu

Logistics Execution  Transportation  Basic transportation functions  Routes  Route determination  Define transportation zones

2. On the Change view “Customers: Transportation zones:” Overview screen, choose New entries: Field name

Description


Country

LR

Transportation zone

0000000001

Description

Liberia

© SAP AG

Note

Page 15 of 113

SAP Best Practices


3.3 Settings in GTS Plug In in mySAP ERP 3.3.1

Implementing User Exit

Use You need to implement the User Exit EXIT_SAPLSLL_LEG_CDPIR3_002 to create an outbound customs document in Service Transit required for the outbound scenario for Customs Management. The user exit must be registered in transaction CMOD. For this reason, a project has to be created with the assignment of SAP component SLLLEG01. Read also note 526256.

You only need to implement the user exit if you are using the Customs Management scenario.


CMOD

SAP Menu

Tools  ABAP Workbench  Utilities  Enhancements  Project Management

2. On the Project Management of SAP Enhancements screen, create a project to register the user exit and name it for example: SLLLEG01. 3. Enter also a short text to describe the project, e.g. User Exit for Customs Management GTS 4. Choose Enhancements Assignments and enter the enhancement SLLLEG01. 5. The package name is blank. Click on local object. 6. Choose Save. 7. Choose Components. 8. Double click the function module EXIT_SAPLSLL_LEG_CDPIR3_002. 9. Choose Change. 10. Double click ZXSLLLEGCDPIR3U02 and enter the following coding: Example coding for creation of a customs document in Service Transit: *&---------------------------------------------------------------------* *& Include ZXSLLLEGCDPIR3U02 *&---------------------------------------------------------------------* * *For Billing Documents IF IV_BUSINESS_OBJECT = 'VBRK'. *Creation of document in Service Transit & Declaration Type T1 CS_API6800-HEADER-CSD-SRVLL = 'LECTPR'. CS_API6800-HEADER-CSD-DCTYP = 'T1'. ENDIF.

11. Choose Save. 12. The package name is blank. Choose local object.

© SAP AG

Page 16 of 113

SAP Best Practices


13. Do not assign the changes to a transport request. 14. Activate ZXSLLLEGCDPIR3U02 and the function module. 15. Go back to the previous screen and activate the project.

Depending on the needs of a customer, additional coding has to be designed and implemented.

3.3.2

Configure Control Settings for Transfer

Use Before calling the Legal Control – Export, Legal Control – Import, Sanctioned Party List Screening services, Transit Procedure Service, or Customs Processing Service, you need to transfer the document data to SAP Global Trade Services (SAP GTS). You need to specify what document types of a specific application level you want to transfer from the backend system to SAP GTS so that the relevant customs documents can be created.


SPRO

IMG Menu

Sales and Distribution -> Foreign Trade / Customs -> SAP Global Trade Services – Plug-In -> Control Data for Transfer to SAP Global Trade Services -> Configure Control Settings for Transfer

2. In the Change View “Application Level”: Overview screen, choose New Entries and enter the following data: Field name

Description

Application Level


Note

MM0A MMOB MM0C SD0A SD0B SD0C

3. Select each Application Level and enter the following data for different levels: Field name

Description


Aplication Level

MM0A

DT for Backend Sys.

FYNB

Call Up SAP Risk Management Services

X

Generate Worklist for Vendor-Based Vendor Declarations

X

Application Level

MM0B

© SAP AG

Note

Page 17 of 113

SAP Best Practices

Field name


Description


Note

DT for Backend Sys.

EL

Call Up SAP Customs Management Services

X

Aplication Level

MM0C

DT for Backend Sys.

101B


X


X

Generate Worklist for Vendor-Based Vendor Declarations

X

Application level

SDOA

Document type

YOR

Call up SAP Compliance Management Service

X

Call up Risk Management Services

X

Output GTS Dialog

X

Set Preference Indicator in Feeder System

X

Check Configurable Materials

X

Application level

SDOB

Dispatch/ Export: Outbound delivery

Document type

LF

Outbound delivery

Call SAP Compliance Management Service

X

Output GTS Dialog

X

Aplication Level

SD0C

DT for Backend Sys.

YHF8


X


X

Set Preference Indicator in Feeder System

X

Check Configurable Materials

X

© SAP AG

Dispatch/ Export: Sales document

This is a separate pro-forma invoice document type needed for Customs Management

Page 18 of 113

SAP Best Practices



3.3.3

Activate BADIs for Transfer of Documents (ERP)

Use You need to activate BADIs to be able to transfer Sales and Purchasing Documents to GTS.


SPRO

IMG Menu

Sales and Distribution -> Foreign Trade / Customs -> SAP Global Trade Services – Plug-In -> Control Data for Transfer to SAP Global Trade Services

2. In the IMG execute the following activities: IMG Activity

Description

Activate Transfer of Sales Documents (SD0A)


Note

Choose Execute for these IMG activities.

Activate Transfer of Billing Documents (SD0C) Activate Transfer of Inbound Delivery (MM0B) Activate Transfer of Goods Movement (MM0C) Activate Transfer of Purchasing Orders (MM0A) 3. The Transfer of the relevant documents into GTS is activated.

3.3.4

Preference: Control Settings for Bill of Materials Transfer

Use You need to enter Control settings for the Transfer of the Bill of Materials.


SPRO

IMG Menu

Sales and Distribution -> Foreign Trade / Customs -> SAP Global Trade Services – Plug-In -> Preference: Control Transfer of Bills of Material

© SAP AG

Page 19 of 113

SAP Best Practices


2. In the Change View “Control Settings for BOM Transfer – Global”: Overview choose New entries and enter the following data: Field name

Description


BOM Category

1 BOM Category: Static

Application

PP01

Model

WG Cross-Plant Preference Determination

Rule Set Type

B Rule Set Type for EU Preference

Type of BOM Explosion

Top-Down Method

Production BOMs

X

Note

3. Save you entries and go back to the previous screen. 4. Choose New Entries again and enter the following: Field name

Description


BOM Category

2 BOM Category: Configurable

Application

SD01

Model

WG Cross-Plant Preference Determination

Rule Set Type

B Rule Set Type for EU Preference

Type of BOM Explosion

Top-Down Method

Note

5. Save your entries. 6. For both of the entries select Control Settings for Transfer – Country Level and enter DE. 7. For both of the entries select Control Settings for Transfer – Plant Level and enter your plant, for example BP01.

3.3.5

Control Settings for Vendor Based Vendor Declaration Worklists

Use In this step you enter the countries where your vendors are located and where you get the vendor declarations from.


SPRO

IMG Menu

Sales and Distribution -> Foreign Trade / Customs -> SAP Global Trade Services – Plug-In -> Preference: Define Worklist for Vendor-Based Long-Term Vendor Declarations

© SAP AG

Page 20 of 113

SAP Best Practices


2. In the Change View “GTS: Control Settings for Vendor-Based Vend. Decl. Worklist” screen choose New Entries and make the following entries: Country Organization

Worklist Country

Name

DE

DE

Germany

DE

FR

France


3.4 System Communication in mySAP ERP Prerequisites The logical system in ERP is defined and has been asssigned to your client. This is done with the Baseline Installation in building block B32.

3.4.1

Defining Logical System for GTS (ERP)

Use In this step you define the logical system for GTS in the ERP system.


OMTX

IMG Menu

Customizing  Cross-Application Components  Predefined ALE Business Processes  Logistics  Logistics <-> External Systems  External Transportation Planning System  Define Logical NonSAP Systems

2. On the Change View “Logical Systems”: Overview screen, choose New Entries: Field name

Description

Log.System

Logical System

Name

User action and values RS5CLNT037

Note CLNT


3.4.2

Checking RFC User (ERP)

Use The RFC user is already created when implementing E04. Check whether this is the case. If the user RFCUSR doesn’t exist create him with the following procedure.

Procedure

© SAP AG

Page 21 of 113

SAP Best Practices


1. Access the activity using one of the following navigation options:



SAP ERP

Tools  Administration  User Maintenance  Users

Transaction Code

SU01

...

2. On the User Maintenance: Initial Screen, enter the RFCUSR user and choose Create. 3. On the Maintain User screen, maintain the following data: Field name

Description


Note

Address tab Last name

RFC User

Logon data tab Initial password

initial

Repeat password

initial

4. Save your entries. 5. Go back to the transaction SU01. In the group box User Type, set the RFC user on the logon data tab page to Communication Data.

3.4.3

Maintaining RFC Destinations for RFC Calls (ERP)

Use To enable communication between two systems or more, you establish a technical connection between them – in this case, a connection between your backend system and SAP Global Trade Services (SAP GTS). You create a system connection by maintaining Remote Function Call (RFC) destinations for RFC calls.

Prerequisites You have created an RFC user in SAP GTS.

Procedure 1. Access the activity using the following navigation option:



SAP ERP

/N/SAPSLL/MENU_LEGALR3  Basic Settings  Maintain RFC Destinations for RFC Calls

Transaction Code

SM59

...

2. Create a new SAP ERP connection (connection type 3 , ERP Connection). 3. Enter the name of the target logical system (in this case SAP GTS) as the name of the RFC destination. 4. Specify the IP address of SAP GTS. 5. Specify the RFC user, client and password to be used for logging on to SAP GTS with RFC calls. Use the functions Remote Logon and Test Connections to test the connection.

If the name of your SAP GTS logical system is JDVCLNT100, you need to specify the RFC destination ‘JDVCLNT100’, the connection type ‘3’, the IP address, and the RFC user ‘USERRFC’ with the appropriate password in client 100.

© SAP AG

Page 22 of 113

SAP Best Practices

3.4.4


Maintaining RFC Destinations for Method Calls (ERP)

Use To define the standard connection for method calls, you assign the Remote Function Call (RFC) destination you defined in the previous step to SAP Global Trade Services (SAP GTS) as the standard Business Application Programming Interface (BAPI) destination for the SAP GTS logical system.




SAP Menu

/N/SAPSLL/MENU_LEGALR3  Basic Settings  Maintain RFC Destinations for Method Calls

Transaction Code

BD97

...

2. Assign the previously defined RFC destination as standard BAPI destination for SAP GTS logical system.

If both your SAP GTS logical system and the RFC destination you defined have the value JDVCLNT100, assign as follows: Backend System: JDLCLNT900 SAP GTS: JDVCLNT100 Standard RFC Destination for BAPI Calls: JDVCLNT100

3.4.5

Maintaining the ALE Distribution Model (ERP)

Use Application Link Enabling (ALE) technology ensures distributed but integrated application communication. To regulate the data flow between your backend system and SAP Global Trade Services (SAP GTS), you need to maintain an ALE distribution model. If you need to create a new distribution model, assign an object or interface, together with its method, to the logical systems of both the backend system and SAP GTS.




SAP Menu

/N/SAPSLL/MENU_LEGALR3  Basic Settings  Maintain ALE Distribution Model

Transaction Code

BD64

...

2. Choose Create Model View to create a new distribution model. Short text: Global Trade Services. Technical name: SLL-LEG. 3. Choose Add BAPI. 4. Enter the name of your backend system (sender), for example KSCLNT046. 5. Enter the name of SAP GTS (recipient), for example KSCLNT061. 6. Assign CustomsDocumentIF as the object/interface. 7. Assign SynchronizeIfR3 as the method.

© SAP AG

Page 23 of 113

SAP Best Practices



Example You created a new distribution model called SLL-LEG. Within this distribution model, you assign the object or interface CustomsDocumentIF, the method SynchronizeIfR3 to the sender system JDLCLNT900 (backend system) and the recipient system JDVCLNT100 (SAP GTS).

3.4.6

Activating Change Pointers (ERP)

Use Customer master data, vendor master data, and material master data has to be transferred from the backend system to SAP Global Trade Services (SAP GTS). Initially, this master data is uploaded. However, if any changes are made to the master data records in the backend system, these changes have to be recorded in SAP GTS. Changes to master data records are written automatically to a change pointer table in the backend system. However, not all the fields containing changes in the tables are of relevance to SAP GTS processes. To avoid unnecessary data transfers, you need to select the fields you specifically require to be included in the change pointer table in your backend system. Once you activate the ALE change pointers in the backend system, this system automatically distributes the changed data (customers, vendors, materials). A smaller number of message types ensures that only the fields relevant to SAP GTS and changed in the backend system are transferred from a batch job to SAP GTS.

Procedure 1. First, activate change pointers globally: a) Access the activity using the following navigation option:



SAP Menu

/N/SAPSLL/MENU_LEGALR3  Basic Settings  Activate Change Pointers Globally

Transaction Code

BD61

...

b) Select Change pointers activated – generally. c) Save your entries. 2. Activate change pointers for reduced messages: a) Access the activity using the following navigation option: SAP Menu

/N/SAPSLL/MENU_LEGALR3  Basic Settings  Activate Change Pointers for Reduced Messages

Transaction Code

BD53

b) Enter /SAPSLL/DEBMAS_SLL /SAPSLL/CREMAS_SLL /SAPSLL/MATMAS_SLL and choose Activate change pointers.

© SAP AG

Page 24 of 113

SAP Best Practices


4 Configuration in GTS system/client 4.1 System Communication in SAP GTS 4.1.1

Creating RFC User

Use In this step you create the RFC user in the GTS system / client.

Procedure 1. Access the activity using one of the following navigation options:



SAP ERP

Tools  Administration  User Maintenance  Users

Transaction Code

SU01

...

4. On the User Maintenance: Initial Screen, enter the RFCUSR user and choose Create. 5. On the Maintain User screen, maintain the following data: Field name

Description


Note

Address tab Last name

RFC User

Logon data tab Initial password

initial

Repeat password

initial

6. Save your entries. 7. Go back to the transaction SU01. In the group box User Type, set the RFC user on the logon data tab page to Communication Data.

4.1.2

Defining the Logical Systems

Use To set up communication between the backend system and SAP GTS, you define the logical system of your backend system and the logical system of SAP GTS.

Please note: In case you have one system installation (ERP and GTS running on the same Web Application Server as two clients) the definition and assignment of the Logical System has to be done only once, since the tables are cross-client.


SPRO

IMG in SAP GTS

SAP Global Trade Services  System Communication  System Connection to Feeder System  Define Logical

© SAP AG

Page 25 of 113

SAP Best Practices

H42: Configuration Global Trade Services (GTS) System



...

2. Enter the name of the logical system using the standard naming convention: CLNT.

If your backend system runs in client 900 of the JDL system, and SAP GTS runs in client 100 of the JDV system, define the logical systems for them as follows: Backend system: JDLCLNT900 SAP GTS: JDVCLNT100

4.1.3

Assigning the Logical System

Use To set up communication between SAP Global Trade Services (SAP GTS) and your backend system, you assign the logical system of SAP GTS to its own client.

Prerequisite The logical system in GTS is defined and has been asssigned to the GTS client.




Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  System Communication  System Connection to Feeder System  Assign Logical System

...

2. Assign the logical system of your GTS system to its own client. If there is no suitable client available, create one.

If your SAP GTS runs in client 100 of the JDV system, assign the logical system JDVCLNT100 to client 100.

4.1.4

Maintaining RFC Destination for RFC Calls (SAP GTS)

Use To set up a technical connection between SAP Global Trade Services (SAP GTS) and your backend system, define the target system for RFCs.

Prerequisites You have created an RFC user in the backend system as well as in the GTS system.

Procedure 1. Access the activity using one of the following navigation options: SAP GTS

© SAP AG

/N/SAPSLL/MENU_LEGAL  System Communication/Workflow  Maintain Target System for RFC Calls

Page 26 of 113

SAP Best Practices

Transaction Code 


SM59

...

2. Create a new SAP ERP connection (connection type 3, ERP Connection). 3. Enter the name of the target logical system (in this case the logical system of the backend system) as the name of the RFC destination. 4. Specify the IP address of the backend system. 5. Specify the RFC user, client and password to be used for logging on to the backend system with RFC calls. 6. Use the Remote Logon and Test Connections functions to test the connection.

If the name of your backend system’s logical system is JDLCLNT900, you need to specify the RFC destination JDLCLNT900, the connection type 3, the IP address, and the RFC user USERRFC with the appropriate password in client 900.

4.1.5

Maintaining RFC Destination for Method Calls (SAP GTS)

Use To define the standard connection for method calls, you assign the RFC destination you defined in the previous step to the backend system as the standard BAPI destination for the logical system of the backend system.

Procedure 1. Access the activity using one of the following navigation options: SAP GTS /N/SAPSLL/MENU_LEGAL  System Communication/Workflow Maintain RFC Destinations Transaction Code 

BD97

...

2. Assign the previously defined RFC destination as the standard BAPI destination for the logical system of the backend system.

If both the logical system of your backend system and the RFC destination you defined have the value JDLCLNT900, assign as follows: SAP GTS: JDVCLNT100 Backend system: JDLCLNT900 Standard RFC destination for BAPI calls: JDLCLNT900 3. Save your entries.

4.1.6

Defining Logical System Group (SAP GTS)

Use If you want to connect several backend systems with matching or partly matching characteristics to SAP Global Trade Services (SAP GTS), you can group the backend systems into logical system groups.

Procedure

© SAP AG

Page 27 of 113

SAP Best Practices


1. Access the activity using the following navigation option:



Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  System Communication  Logical System Group  Define Logical System Group

...

2. Enter the names of the logical system groups you want to group and save your entries.

4.1.7

Assigning Logical Systems to a Group of Logical Systems (SAP GTS)

Use You assign logical systems that have matching or partly matching characteristics to one logical system group. These characteristics include the following: identical/matching material numbers, customer numbers, vendor numbers, company codes, plants and storage locations.

Even if you want only to connect one backend system to SAP GTS, you still have to define a logical system group for this single backend system.

Prerequisites You can only group several logical systems into a logical system group if each master data record is unique across all backend systems.

The material numbers, customer numbers and vendor numbers that you assign must be unique across all systems.




Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  System Communication  Logical System Group  Assign Logical System to a Group of Logical Systems

...

2. Assign the logical system group to the logical systems you want to include.

Example If your master data is maintained centrally using a specially designated master data server, all of the systems involved can be grouped into a single logical system group.

© SAP AG

Page 28 of 113

SAP Best Practices


4.2 General Settings in GTS 4.2.1

Maintaining Time Zones (SAP GTS)

Use In SAP Global Trade Services (SAP GTS), the system time zone determines all timedependent data, such as sanctioned party list (SPL) master records, customs records, determination data, and time stamps in documents. Therefore, when you set up your system, one of the first steps hast to be the checking or selecting the system time zone.

We strongly recommend not to change the system time zone after entering the application data since this will lead to major data inconsistencies. In this activity, you configure the following settings for the time zones: 

System time zone



Standard time zone for users

System time zone The system time zone is comparable to the time zone of your operating system. It applies to all clients. If you change the system time zone in one client, the new value is automatically copied to all other clients. If you specify the system time zone, the SAP system can calculate the local time from a UTC time. Standard time zone for users Using the standard time zone, you specify the local time zone of a user in a client. However, this specification is only used if no personal time zone is maintained in the user defaults. The standard time zone is not changed on a cross-client basis. It can vary from client to client.

During your first login to an SAP system, the system time zone is determined automatically. However, we recommend checking this value, since a unique assignment is sometimes not possible. To activate the time zone function, the system automatically sets the indicator Time Zone Active.

Prerequisites You have checked whether the time zone you require exists before configuring your settings in the system. Go to the Implementation Guide (IMG) for SAP GTS and choose General Settings  Maintain Time Zones. If the required time zone does not exist, you can make a new entry in the Maintain Time Zones activity, and send a customer message to SAP.


© SAP AG

SPRO

Page 29 of 113

SAP Best Practices

H42: Configuration Global Trade Services (GTS) SAP Global Trade Services  General Settings  Maintain System Time Zone

IMG in SAP GTS 

...

2. Make your settings for the system time zone. 3. Make your settings for the user’s default time zone.

4.2.2

Number Ranges

4.2.2.1

Defining Number Ranges for Business Partners

Use To enable the system to transfer customer or vendor master data from the backend system, you have to maintain number ranges for customs business partners. This is standard Customizing. Chek if the following settings are made.


/N/SAPSLL/SNUM_PARTNER

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Business Partners

2. On the SAP Business Partner screen, choose Display intervals to check whether internal and external number ranges are defined. 3. Value 01 is an internal number range and AB is an external number range. If necessary, choose Edit  Insert interval to define a new number range or choose Change intervals to change the existing entries: Field name

Description

No

Number range number

User action and values 01

From number

0000000001

To number

9999999999

Ext

Note

External number range flag

4. If the external interval 02 exists, delete it and create the external number range AB instead. Field name

Description

No

Number range number

From number

Note

AB A

To number Ext


ZZZZZZZZZZ External number range flag

X

5. Use the transaction buc2 to check the business partner grouping and assign the number ranges you have defined. The internal number range 01 has be assigned to grouping 0001 and the external number range AB has be assigned to grouping 0002.

© SAP AG

Page 30 of 113

SAP Best Practices

4.2.2.2


Defining Number Ranges for Product Masters

Use To enable the system to transfer material data from the backend system, you need to maintain number ranges for customs product masters.


/N/SAPSLL/SNUM_PROD

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Customs Products

2. On the Product masters for legal and logistics services screen, choose Display intervals to check whether an internal number range is defined. If necessary, choose Edit  Insert interval to define a new number range or choose Change intervals to change existing entries: Field name

Description

No

Number range number


From number

00000000000000000001

To number

99999999999999999999

Ext

Note


3. Confirm the dialog box and save your entries.

4.2.2.3

Defining Number Ranges for Licenses

Use This number range is relevant for Customs Management and Compliance, also set in standard. This is standard Customizing. Check if the following settings are there.


/n/SAPSLL/SNUM_LCLIC

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Licenses

2. On the GTS: Licenses for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range. Field name

Description

No

Number range number


From number

00100000000000000000

To number

00199999999999999999

Ext

Note



© SAP AG

Page 31 of 113

SAP Best Practices

4.2.2.4


Defining Number Ranges for Customs Documents

Use To enable the system to transfer document data from the backend system, you need to maintain number ranges for customs documents.


/N/SAPSLL/SNUM_LEGAL

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Documents

2. On the GTS: customs document for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range: Field name

Description

No

Number range number

Year

User action and values 01 Current year (e.g. 2006)

From number

0100000000

To number

0199999999

Ext

Note


3. Save your entries. 4. Choose Insert interval again. Field name

Description

No

Number range number

Year


From number

1100000000

To number

1199999999

Ext

Note



Description

No

Number range number

Year


From number

1200000000

To number

1299999999

Ext

© SAP AG

Note


Page 32 of 113

SAP Best Practices



Description

No

Number range number

Year


From number

1300000000

To number

1399999999

Ext

Note



Description

No

Number range number

Year


From number

1400000000

To number

1499999999

Ext

Note



4.2.2.5

Defining Number Ranges for Supplementary Customs Declaration

Use This number range is necessary if you use the Customs Management scenarios.


/n/SAPSLL/SNUM_CUPED

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Supplementary Customs Declaration

2. On the GTS: Periodic Reporting for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range. Field name

Description

No

Number range number


From number

0100000000

To number

0199999999

Ext

© SAP AG

Note


Page 33 of 113

SAP Best Practices



4.2.2.6

Defining Number Ranges for Internal Package Numbers

Use This number range is necessary if you use the Customs Management scenarios.


/n/SAPSLL/SNUM_PGE

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Internal Package Numbers

2. On the GTS: Internal Package Numbers for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range: Field name

Description

No

Number range number


From number

0100000000

To number

0199999999

Ext

Note



4.2.2.7

Defining Number Ranges for EDI Messages

Use To enable the system to transfer data from the backend system, you need to maintain number ranges for EDI messages.


/N/SAPSLL/SNUM_EDINR

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for EDI Messages

2. On the GTS: EDI message number for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range: Field name

Description

No

Number range number


From number

00000000000000000001

To number

99999999999999999999

Ext

© SAP AG

Note


Page 34 of 113

SAP Best Practices



4.2.2.8

Defining Number Ranges for Vendor Declarations

Use To enable the system to assign numbers for vendor declarations, you need to maintain number ranges. This number range is necessary if you use the Risk Management scenario.


/n/SAPSLL/SNUM_PREVD

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Vendor Declarations

2. On the GTS: Vendor Declarations in Preference Processing (GTS) screen, choose Change intervals and choose Insert interval to define a new number range: Field name

Description

No

Number range number

Year


Note

01 Current year, for example 2005

From number

00000000000200500001

To number

00000000000200599999

Ext



4.2.2.9

Defining Number Ranges for Preference Models

Use To enable the system to assign numbers for preference models, you need to maintain number ranges. This number range is necessary if you use the Risk Management scenario.


/n/SAPSLL/SNUM_PREMOD

IMG in SAP GTS

SAP Global Trade Services  General Settings  Number Ranges  Define Number Ranges for Preference Models

2. On the GTS: Preference Model for Global Trade Services screen, choose Change intervals and choose Insert interval to define a new number range: Field name

Description

No

Number range number

© SAP AG


Note

01

Page 35 of 113

SAP Best Practices

Field name


Description


From number

00000000001000000001

To number

00000000001000000999

Ext

Note


3. Repeat the step and create a second, a third and fourth number range: Number range

From number

02

00000000002000000001

00000000002000000999

03

00000000003000000001

00000000003000000999

04

40000000000000000000

49999999999999999999

4.2.3 4.2.3.1

To number

Organizational Structure Maintaining Business Partner Roles for foreign trade

Before defining the Foreign Trade Organization as described below, the needed roles have to be created.

1. Go to IMG.

Transaction Code

/NSPRO

IMG in SAP GTS

Cross Application Components  SAP Business Partner  Business Partner  Basic Settings  Business Partner Roles  Define BP Roles

2. Check in the menu tree if the BP Role Categories are existing:

Role Cat.

Title

Description

SLLAUT SLLBNK SLLCOF SLLCPC SLLCPS SLLDAP SLLFTO SLLMGR SLLSIT

© SAP AG

Page 36 of 113

SAP Best Practices


3. If not, go to Business Partner Role by double-click on the line in the left menu tree. Choose new entry. Field

Field Value

BP Role

SLLAUT

Title

Government Agency

Description

GTS: Government Agency

BP Role Cat.

SLLAUT

BP View

SLLAUT

remarks

Flag: Std Assignment BP Role -> BP Role Cat

4. Choose next entry. Field

Field Value

BP Role

SLLBNK

Title

Bank for L/C

Description

GTS: Bank for Documentary Payment

BP Role Cat.

SLLBNK

BP View

SLLBNK

remarks



Field Value

BP Role

SLLCOF

Title

Customs Office

Description

GTS: Customs Office

BP Role Cat.

SLLCOF

BP View

SLLCOF

remarks



Field Value

BP Role

SLLCPC

Title

Customs Bus. Partner

Description

GTS: Customs Business Partner (Cus.)

BP Role Cat.

SLLCPC

BP View

SLLCPC

remarks



Field Value

BP Role

SLLCPS

© SAP AG

remarks

Page 37 of 113

SAP Best Practices


Field

Field Value

remarks

Title

Customs BP (Vendor)

Description

GTS: Customs Business Partner (Vendor)

BP Role Cat.

SLLCPS

BP View

SLLCPS



Field Value

BP Role

SLLDAP

Title

Data Provider

Description

GTS: Data Provider

BP Role Cat.

SLLDAP

BP View

SLLDAP

remarks



Field Value

remarks

BP Role

SLLFTO

Title

FT Organization

Description

GTS: Foreign Trade Organization

BP Role Cat.

SLLFTO

BP View

SLLFTO



Field Value

remarks

BP Role

SLLMGR

Title

Admin. Unit VD

Description

GTS: Administr.Unit Vend.Decl.

BP Role Cat.

SLLMGR

BP View

SLLMGR



Field Value

BP Role

SLLSIT

Title

Legal Unit

Description

GTS: Legal Unit

© SAP AG

remarks

Page 38 of 113

SAP Best Practices


Field

Field Value

remarks

BP Role Cat.

SLLSIT


BP View

SLLSIT

12. Choose Save.

4.2.3.2

Maintaining Business Partners: Foreign Trade Organizations

Use Foreign trade organizations, such as corporate groups, represent the company as a whole. The organizational structure of the company is mapped according to the legal and customs law requirements.


/N/SAPSLL/BP_FTORG

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Define Foreign Trade Organizations

2. On the Maintain business partner screen, choose Create organization: Field name

Description


Business partner

OBP01

Create in role

SLLFTO

Name

Note

Foreign trade organization

Foreign trade organization OBP01

Search term 1

BP01

Search term 2

SAP BEST PRACTICES

Country

DE

3. Choose More fields. Field name Time Zone

Description


Note

CET


4.2.3.3

Maintaining Business Partners: Employee Customs Manager

Use You need to define an employee customs manager if you use the Customs Management scenario.

© SAP AG

Page 39 of 113

SAP Best Practices



/N/SAPSLL/BP_FTORG

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Define Foreign Trade Organizations

2. On the Maintain business partner screen, choose Create organization: Field name

Description


Business partner

CUSMANAGER

Create in role

Business partner (GEN.)

Name

Customs manager of company

Street

e.g.: Company street

Postal Code / City

e.g.: 61124 Frankfurt

Country

DE

Language

English

Note

5. Choose More fields. Field name

Description


Time Zone

Note

CET


4.2.3.4

Maintaining Business Partners: Legal Units

Use The legal units divide an organizational unit into several areas to provide you with a detailed view of the unit. An organizational unit (company code) consists of several legal units (plants). The system uses the country in the address of the legal unit to determine the departure country for exports and the destination country for imports. The active legal regulations are then determined on the basis of that country.


/N/SAPSLL/BP_FTVBS

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Define Legal Units

2. On the Maintain Business Partner screen, choose Create organization: Field name

Description


Business partner

LBP01

Create in role

SLLSIT

Name

Legal unit

Legal Unit LBP01

Search term 1

BP01

Search term 2

SAP BEST PRACTICES

© SAP AG

Note

Page 40 of 113

SAP Best Practices


Field name

Description


Country

Note

DE

3. Choose More fields. Time Zone

CET


4.2.3.5

Assigning Company Codes

Use The company codes from the backend system are mapped to the organizational units. Note that more than one company code can be assigned to an organizational unit, but only one company code can be assigned to exactly one organizational unit at a time. If only one backend system exists, or if several backend systems have different organizational structures, it is best to assign the company codes at backend system level. If several backend systems have the same organizational structures, you can assign the company codes at backend system group level.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Assignment of Organizational Units from Feeder Systems to Foreign Trade Org  Assign Company Code at Feeder System Level

2. In the upcoming dialog box, choose Manually assign Company Code. 3. On the Change view “GTS: Assignment of backend system company code” screen, choose New entries: Field name

Description

Logical system


Note

Name of the logical system (ERP)

BS Org.

Company code from backend system

Description

Description of company code

FT Organ.


BP01

SAP Best Practices OBP01

4. Repeat step 3: Field name

Description

Logical system BS Org.

© SAP AG


Note

Name of the logical system (ERP) Company code from backend system

BP0X

Page 41 of 113

SAP Best Practices


Field name

Description

Description


FT Organ.



Note

Best Pract. Intercompany OBP01

5. Save your entries. 6. Access the activity using the following navigation options: Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Assignment of Organizational Units from feeder system to Foreign Trade Org  Assign Company Code at Feeder System Group Level

7. In the upcoming dialog box, choose Manually Assign Company Code. 8. On the Change view “GTS: Assignment of company code at system group level” screen, choose New entries: Field name

Description

Group of logical systems


Note

Name of the logical system group (ERP)

BS Org.


Description


FT Organ.


BP01

SAP Best Practices OBP01


Description



Note


BS Org.


Description


FT Organ.


BP0X Best Pract. Intercompany OBP01


4.2.3.6

Assigning Plants

Use The plants in the backend system are mapped to the legal units. There are two possible combinations. If only one backend system exists or if several backend systems have different organizational structures, it is best to assign the plants at backend system level. If a number of backend systems have the same organizational structures, the plants can be assigned at backend system group level.

© SAP AG

Page 42 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Assignment of Organizational Units from Feeder Systems to Legal Units  Assign Plant at Feeder System Level

2. In the upcoming dialog box, choose Manually Assign Plant. 3. On the Change view “GTS: Assignment of backend system plant to legal unit” screen, choose New entries: Field name

Description

Logical system


Note


BS Org.

Plant from backend system

Description

Plant description

Legal unit

BP01 Production Plant LBP01


Description

Logical system


Note


BS Org.


Description

Plant description

Legal unit

BP02 Distribution center LBP01


Description

Logical system


Note


BS Org.


Description

Plant description

Legal unit

BP03 Regional warehouse LBP01


Description

Logical system

Note


BS Org.


Description

Plant description

Legal unit


BP0X Intercompany processing plant LBP01


© SAP AG

Page 43 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Assignment of Organizational Units from Feeder Systems to Legal Units  Assign plant at Feeder System Group Level

9. In the upcoming dialog box, choose Manually Assign Plant. 10. On the Change view “GTS: Assignment of plant group BS to legal unit” screen, choose New entries: Field name

Description



Note


BS Org.


Description

Plant description

Legal unit

BP01

Production plant LBP01


Description



Note


BS Org.


Description

Plant description

Legal unit

BP02 Distribution center LBP01


Description



Note


BS Org.


Description

Plant description

Legal unit

BP03 Regional warehouse LBP01


Description


Note


BS Org.


Description

Plant description

Legal unit


BP0X

Intercompany processing plant LBP01


© SAP AG

Page 44 of 113

SAP Best Practices

4.2.3.7


Defining Organizational Structure for Customs and Foreign Trade

Use This activity is needed for Customs Management.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Organizational Structure  Assign Legal Unit to Foreign Trade Organization

2. On the Change view “GTS: Customs Organizational Structure”: Overview screen, choose New Entries and enter the following data: Field name

Description

Legal Unit


Note

0BP01

Name1


Legal unit LBP01

Foreign Trade Unit

Plant description

OBP01


4.2.4

Legal Regulations

4.2.4.1

Defining Legal Regulations

Use Legal regulations are the central control element for service performance. In this step, you define what laws are to be checked for exports and imports.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal Regulations  Define Legal Regulations

2. On the Change view “Legal regulation”: Overview screen, check if the following entry is created: Field name

Description

Legal reg.

Legal regulation

Law code Description


Note

AWV 00 German foreign trade laws German foreign trade regulations

3. On the Change view “Legal regulation”: Overview screen, select the legal regulation and choose Details:

© SAP AG

Page 45 of 113

SAP Best Practices


Field name

Description


Import/Export

Note

2 Export/Dispatch

Origin ctry-Leg

Country of origin of legal regulation

DE

4. On the Change view “Legal regulation”: details screen, choose Assign deadline types and then check if the following entries are created: Field name

Description


Note

Type of date

VALFRO

Valid from date

Type of date

VALTO

Valid to date


Note

Type of date

CHECK

Relevant check date

Type of date

DISCHA

Transferred and changed

Type of date

DISCRE

Transferred and created

Type of date

DISDEL

Transferred and deleted

Type of date

DISTRI

Transferred unchanged

Type of date

ETYADD

Date of inclusion

5. Choose New entries: Field name

Description


Description

Legal reg.

Legal regulation

Law code


Note

EMBUN 00 German foreign trade laws

Description

Embargo

7. On the Change view “Legal regulation”: Overview screen, select the legal regulation EMBUN and choose Details: Field name

Description


Import/Export Origin ctry-Leg

Note

2 Export/Dispatch Country of origin of legal regulation

DE

8. On the Change view “Legal regulation”: details screen, choose Assign deadline types and check if the following entry is created: Field name

Description

Type of date


Note

CHECK

Relevant check date


Description

Legal reg.

Legal regulation

User action and values SPLUS

Law code

00 German foreign trade laws

Description

Sanctioned party list screening

© SAP AG

Note

Page 46 of 113

SAP Best Practices


10. On the Change view “Legal regulation”: Overview screen, select the legal regulation SPLUS and choose Details: Field name

Description


Import/Export Origin ctry-Leg

Note

2 Export/Dispatch Country of origin of legal regulation

DE

Overwrite other entries with DE

11. On the Change view “Legal regulation”: details screen, choose Assign deadline types and check if the following entries are created: Field name

Description


Note

Type of date

ETYADD

Date of inclusion

Type of date

VALFRO

Valid from date

Type of date

VALTO

Valid to date


Note

CHECK

Relevant check date

12. Choose New entries: Field name

Description

Type of date 13. Save your entries.

4.2.4.2

Defining Procedure for Determining Active Legal Regulations

Use Standard setting: In this step you check if the determination procedure to establish the active legal regulations for a service is created. You have to assign a determination table to this determination procedure. Use the departure country (export) and the destination country (import) to determine the legal regulations.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal Regulations  Define Determination Procedure for Active Legal Regulations

2. On the Change view “Procedure for determining active legal regulations”: Overview screen, check if the following entry is created: Field name

Description

Det. procedure

Determination procedure

Description


Note

LEEMB GTS: Determination of legal regulation embargo

3. On the Change view “Procedure for determining active legal regulations”: Overview screen, select the entry LEEMB and choose Assignment of determination strategy. 4. Check if the following entry is created:

© SAP AG

Page 47 of 113

SAP Best Practices

Field name


Description


Sequence number

Note

10

Determ. Strategy

ALRG01 Determine legal regulation at country level


Description

Det. procedure


Description


Note

LELDT GTS: Determination of legal regulation licenses

5. On the Change view “Procedure for determining active legal regulations”: Overview screen, select the entry LELDT, choose Assignment of determination strategy and check if the following entry is created: Field name

Description


Sequence number

Note

10

Determ. Strategy



Description

Det. procedure

Determinatio n procedure

Description


Note

LESPL GTS: Determination of legal regulation "SPL"

7. On the Change view “Procedure for determining active legal regulations”: Overview screen, select the entry LESPL, choose Assignment of determination strategy and check if the following entry is created: Field name

Description


Sequence number

10

Determ. Strategy

4.2.4.3

Note


Activating Legal Regulations

Use In this step, you check if the relevant legal regulations for each departure country (export) or destination country (import) are created. For Germany these settings are standard.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal

© SAP AG

Page 48 of 113

SAP Best Practices

H42: Configuration Global Trade Services (GTS) Regulations  Define Legal Regulations  Activate Legal Regulations

2. On the Change view “GTS: Activate legal regulation at country level”: Overview screen, check if the following entries are created: Field name

Description

Legal reg.

Note

AWV

Ctry. of Dep/Des

DE

Legal reg.

EMBUN

Ctry. of Dep/Des

DE

Legal reg.

SPLUS

Ctry. of Dep/Des

4.2.4.4


DE

Defining Groups for Value and Quantity Depreciation of Licenses

Use If value and quantity depreciation are to take place during license determination, you have to create depreciation groups.


SPRO

IMG in GTS

SAP Global Trade Services  General Settings  Legal Regulations  Define Groups for Value and Quantity Depreciation of Licenses

2. On the Change view “GTS: Depreciation groups”: Overview screen, check if the following entries are created: Field name Depreciation group Description Depreciation group Description

4.2.4.5

Description


Note

SD0A01 Sales level: Sales documents SD0B01 Sales level: Outbound deliveries

Maintaining Tariff Code Numbers

Use In this step, you create tariff code numbers that you assign to products during the customs management process.

Procedure

© SAP AG

Page 49 of 113

SAP Best Practices


1. Access the activity using one of the following navigation options: Transaction Code

/n/SAPSLL/LLNS_101

SAP GTS

/n/SAPSLL/MENU_LEGAL  SAP Customs Management  Classification  Tariff Code Numbers  Maintain Tariff Code Numbers

2. On the Maintain Import Code Numbers screen, enter DEEZT in the Numbering Scheme field and choose Maintain Numbers. 3. Choose Chapter and in the GTS: Create Structure Level dialog box enter the following data: Field name

Description


Note

Chapter

10

Valid To

30.12.9999

English -Official Description

Electronic Customs Tariff number 1

Chapter

20

Valid To

30.12.9999


Electronic Customs Tariff number 2

4. Choose Enter and Copy Data after each chapter. 5. Select chapter 10. 6. In the lower group frame, in the middle, choose Create Import Code Number and enter the following data: Field name

Description


Import Code Number

10000001000

Country Key

DE

Validity to

30.12.9999

Note

7. Choose Enter and make the following entries: Field name

Description

English – Official Description


Note

Test classification 1 Germany

8. Select chapter 20. 9. In the lower group frame, in the middle, choose Create CN Code and enter the following data: Field name

Description


Import Code Number

20000001000

Country Code

FR

Validity to

30.12.9999

Note

10. Choose Enter and make the following entries: Field name English – Official Description

Description


Note

Test classification 1 France


© SAP AG

Page 50 of 113

SAP Best Practices

4.2.4.6


Maintaining Commodity Codes

Use In this step you create commodity codes, which you assign during the process to the products.


/n/SAPSLL/LLNS_102

SAP GTS

/SAPSLL/MENU_LEGAL  SAP Risk Management  Preference Processing – Master Data  Numbering Scheme  Maintain Commodity Codes  Execute

2. In the Maintain Commodity Codes enter DESTA in field Numbering Scheme and choose Maintain Numbers. 3. Choose Chapter and in the GTS: Create Structure Level dialog box enter the following data: Field name

Description


Note

Chapter

10

Valid To

30.12.9999


Commodity number Best Practices 1

Chapter

20

Valid To

30.12.9999


Commodity number Best Practices 2

4. Choose Enter and Copy Data. 5. Select chapter 10. 6. In the lower group frame, in the middle, choose Create CN Code and enter the following: Field name

Description


CN Code

10000001

Validity to

30.12.9999

Note

7. Choose Enter and make the following entries: Field name

Description



Note

Best Practices Material 1

8. Select chapter 20. 9. In the lower group frame, in the middle, choose Create CN Code and enter the following data: Field name

Description


CN Code

20000001

Validity to

30.12.9999

Note

10. Choose Enter and add the description:

© SAP AG

Page 51 of 113

SAP Best Practices

Field name


Description



Note

Best Practices material 1


4.2.4.7

Defining External Country Codes for Data Upload You need to define additional countries if these do not exist in T005, for example Palestine, for the data upload from external data provider. You can find this activity under SAP Global Trade Services  General Settings  Legal Regulations  Define External Country Codes for Data Upload.

4.2.4.8

Activating HTTP Services for Document Storage (Using SAP Content Server) It is necessary to activate http services when an external converting system is connected. You can make these settings in Customizing under the path SAP Global Trade Services  General Settings  Activate HTTP Services for Document Storage (Using SAP Content Server).

4.2.5 4.2.5.1

Partner Structure Define Groups of Partner Functions / Assign Partner Function

Use An additional partner function has to be assigned to the partner group PGCTRI.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings -> Partner Structure -> Define Groups of Partner Functions

2. On the Change view “Legal Services: Partner Groups”: Overview screen, select the partner group PGCTRI – Partner Group for ‘Transit’ Service – Import and choose Assign Partner Function. 3. On the Change View “Assign Partner Function”: Overview screen, choose New Entries and make the following entries: Field name Sequence number Partner Function

Description


Note

For example 60 CUSHAV


© SAP AG

Page 52 of 113

SAP Best Practices

4.2.5.2


Grouping Partner Functions

Use You can group all the partner functions you defined previously. When the system performs the individual services, it checks all partner functions that exist in the grouping and in the customs document.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Partner Structure  Define groups of partner functions

2. On the Change view “Legal services: Partner groupings”: Overview screen, choose the partner grouping you want to work with. If there is no suitable entry, create one: Field name

Description

Partner grouping


Note

PGEMB2 Group of partner function Embargo Export

Description

3. On the Change view “Legal services: Partner groupings”: Overview screen, select the partner grouping and choose Assign partner function: Field name

Description


Sequence number

10

Partner func.

AG

Sequence number

20

Partner func.

RE

Sequence number

30

Partner func.

RG

Sequence number

40

Partner func.

WE

Note

4. On the Change view “Legal services: Partner groupings”: Overview screen, choose the partner grouping you want to work with. If there is no suitable entry, create the following one: Field name

Description

Partner grouping


Note

YPGLT2 Group of partner function License Determination Export

Description


Description


Sequence number

10

Partner func.

AG

© SAP AG

Note

Page 53 of 113

SAP Best Practices

Field name


Description


Sequence number

20

Partner func.

WE

Note

6. On the Change view “Legal services: Partner groupings”: Overview screen, choose the partner grouping you want to work with. If there is no suitable entry, create one: Field name

Description


Partner grouping

Note

PGSPL2 Group of partner function SPL Export

Description


Description


Sequence number

10

Partner func.

AG

Sequence number

20

Partner func.

RE

Sequence number

30

Partner func.

RG

Sequence number

40

Partner func.

WE

Note

8. Save your entries and go back to the previous screen. 9. Select the partner group PGCTRI Partner Group for 'Transit' Service – Import and choose Details. 10. In the Change View: “Assign Partner Function”: Overview choose New Entries. 11. Enter the following data. Field name

Description


Sequence Number Partner Function

Note

60 CUSHAV


4.2.5.3

Assigning Partner Functions

Use To enable the system to transfer documents, you need to assign the partner functions in the backend system to those in SAP Global Trade Services (SAP GTS). If only one backend system exists, or if several backend systems have different document structures, you need to assign the partner functions at backend system level. If several backend systems have the same document structure, you can assign the partner functions at backend system group level.

Procedure

© SAP AG

Page 54 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Partner Structure  Assignment of partner roles from feeder systems  Assign partner role at feeder system level

2. In the upcoming dialog, choose the Manually Assign Partner Function. 3. On the Change view “GTS: Assignm. of BackendSys.Partner Role to Customs PartnF screen choose New Entries and create the entries according to the following table. Logical system

BS Partner Role

Partner Func.

Description

QFJCLNT300

AG

AG

Sold-To Party

QFJCLNT300

LF

LF

Vendor

QFJCLNT300

RE

RE

Bill-to Party

QFJCLNT300

RG

RG

Payer

QFJCLNT300

WE

WE

Ship-to Party


4.2.6

Numbering Schemes

4.2.6.1

Defining Numbering Scheme of Export Lists

Use You need to create numbering schemes for products you want to export so that you can classify the products in accordance with export lists. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Numbering Schemes  Defining Numbering Scheme of Export Lists

2. On the Change view “Rule set for export control list” Overview screen, check if the following entry is created: Field name

Description


Number scheme

DEALN

Description

Export list

Note

3. On the Change view “Rule set for export control list” Overview screen, select the number scheme DEALN, choose Details and check if the settings are as follows: Field name Text Official Description

© SAP AG

Description


Note

X

Page 55 of 113

SAP Best Practices


4. On the Change view “Rule set for export control list” details screen, choose Structure of Export List : Field name

Description


Level

10

Length

1

Maintenance

0 exact length

Text

Category

Level

20

Length

2

Maintenance

0 exact length

Text

Class

Level

30

Length

5

Maintenance

0 exact length

Text

Export list number

4.2.6.2

Note

Assigning Numbering Scheme of Export List for License Maintenance

Use For each legal regulation, you have to define the numbering scheme you want to use for maintaining export control numbers in the license or for classifying products in the customs product master. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Numbering Schemes  Assigning Numbering Scheme of Export List for License Maintenance

2. On the Change view “GTS: License maintenance: Assign export list” Overview screen, check if the following entries are created: Field name

Description


Legal regulation

AWV

Customs TS Export

DEALN

© SAP AG

Note

Page 56 of 113

SAP Best Practices

4.2.6.3


Assigning Numbering Scheme for License Determination

Use For each legal regulation, you have to define numbering scheme that is to be used for determining license types. This setting is only relevant if the determination tables for license types contain the attribute Export Control Number. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Numbering Schemes  Assigning numbering scheme to Export List for Legal Control

2. On the Change view “GTS: License type determination: Export rule set” Overview screen, check if the following entry is created: Field name

Description


Legal regulation

AWV

Customs TS Export

DEALN

Note

4.3 Compliance Management 4.3.1

General Settings

4.3.1.1

Defining Document Types

Use When you transfer documents from the backend system, the system creates a customs document for each document type. In the following activities, you maintain all the relevant structures for the customs document.


SPRO

IMG in SAP GTS

SAP Global Trade Services SAP Compliance Management  General Settings  Document Structure  Define Customs Document Types

2. On the Change view “GTS: Customs document type” screen, choose the document types you want to work with. If there is no suitable entry, create one:

© SAP AG

Page 57 of 113

SAP Best Practices

Field name


Description


Customs doc. type

Note

EXPDLV

Description

Customs document (export) - delivery document level

3. On the Change view “GTS: Customs document type” screen, select the customs document type and choose Details: Field name

Description


Import/Export

2 Export/Dispatch

Number range number

01

Service log

Note

Save current log and delete old logs

4. On the Change view “GTS: Customs document type” screen, choose the document types you want to work with. If there is no suitable entry, create one: Field name

Description


Customs doc. type

Note

EXPORD

Description

Customs document (export) - sales document level

5. On the Change view “GTS: Customs document type” screen, select the customs document type and choose Details: Field name

Description


Import/Export

2 Export/Dispatch

Number range number

01

Service log

4.3.1.2

Note

Save current log and delete old logs

Activating Document Type

Use To enable the system to carry out the determination procedure for license types, you need to activate the ‘License Determination’ service at both customs document type level and item category level. You need to maintain the determination rules for each legal regulation to determine what license types are used for a particular business transaction. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  License determination service  Activation  Activate document types

© SAP AG

Page 58 of 113

SAP Best Practices


2. On the Change view “GTS: Activate service license determination” screen, check if the following document types are created: Field name

Description


Note

Customs doc. type

EXPDLV

Deliveries

Customs doc. type

EXPORD

Sales orders

4.3.1.3

Assigning Document Types

Use When you transfer documents from the backend system, the system maps the document type from the backend system to the document type in SAP Global Trade Services (SAP GTS). You can assign these document types either at backend system level or at backend system group level. If only one backend system exists, or if several backend systems have different documents, it is best to assign the document types at backend system level. If several backend systems have the same document structure, the documents can be assigned at backend system group level.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  General Settings  Document Structure  Assignment of document types from feeder systems  Assign document type at feeder system level

2. In the upcoming dialog box, choose Manually assign Document Types . 3. On the Change view “GTS: Assignment of backend system doc. type to cust. doc” screen, choose New entries: Field name

Description

Application level


Note

SD0A: Dispatch/Export: Sales document

Log. System

Logical system (ERP)

Doc. type backend sys.

YOR

Customs doc. Type

EXPORD

4. On the Change view “GTS: Assignment of backend system doc. type to cust. doc” screen, choose New entries: Field name

Description


Application level

SD0B: Dispatch/Export: Outbound delivery document

Log. System



© SAP AG

Note

LF

Page 59 of 113

SAP Best Practices

Field name


Description


Customs doc. Type

Note

EXPDLV

5. Save your entries. 6. Access the activity using the following navigation option: GTS Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  General settings  Document structure  Assignment of document types from feeder systems  Assign document type at feeder system group level

7. In the upcoming dialog box, choose Manually Assign Document Types . 8. On the Change view “GTS: Assignment of group backend systems doc. type to cust. doc” screen, choose New entries: Field name

Description

Application level


Note


LS Group

Logical system group (ERP)


YOR

Customs doc. Type

EXPORD


Description


Application level


LS Group



LF

Customs doc. Type

EXPDLV

Note


4.3.1.4

Defining Item Categories

Use In this step, you define customs item categories involved in the services in order to control what services the system executes for the customs document. These settings are standard settings. Please check if the following entries are there.


© SAP AG

SPRO

Page 60 of 113

SAP Best Practices

H42: Configuration Global Trade Services (GTS) SAP Global Trade Services  SAP Compliance Management  General settings  Document structure  Define customs item categories

IMG in SAP GTS

2. On the Change view “GTS: Item category of customs document” screen, choose the item categories you want to work with. If there is no suitable entry, create one: Field name

Description


Customs doc. item cat.

Note

EXDLV1

Description

Customs Doc. Item (Export) - Delivery Doc. Item Cat. Level

3. On the Change view “GTS: Item category of customs document” screen, choose the item categories you want to work with. If there is no suitable entry, create one: Field name

Description



EXORD1

Description

4.3.1.5

Note

Customs Doc. Item (Export) - Sales Doc. Item Cat. Level

Activating Item Category

Use To enable the system to carry out the determination procedure for license types, you need to activate the ‘License Determination’ service at both customs document type level and item category level. You need to maintain the determination rules for each legal regulation to control which license types are used for a particular business transaction. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  License determination service  Activation  Activate item categories

2. On the Change view “GTS: Activate service license determination” screen, check if the item categories are created: Field name Customs doc. item category

Description


Note

EXDLV1


3. On the Change view “GTS: Activate service license determination” screen, select the item category, choose Details and check if the settings are as follows:

© SAP AG

Page 61 of 113

SAP Best Practices

Field name


Description


Note

Customs doc. item category

EXDLV1


Value depreciation

- Allocation: Deduct from license

Quantity allocation


Depreciation group

SD0B01

Deliveries

4. On the Change view “GTS: Activate service license determination” screen, check if the item categories are created: Field name

Description



Note

EXORD1


5. On the Change view “GTS: Activate service license determination” screen, select the item category, choose Details and check if the settings are as follows: Field name

Description


Note


EXORD1

Customs Doc. Item (Export) – Sales Doc. Item Cat. Level

Value depreciation


Quantity allocation


Depreciation group

SD0A01

Sales orders


4.3.1.6

Assigning Item Categories

Use To enable the system to transfer documents from the backend system, you need to assign the item categories in the backend system to the item categories in SAP Global Trade Services (SAP GTS). If only one backend system exists, or if several backend systems have different documents, it is best to assign the item categories at backend system level. If several backend systems have the same document structure, the item categories can be assigned at backend system group level.

Procedure

© SAP AG

Page 62 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  General settings  Document structure  Assignment of item categories from feeder systems  Assign item category at feeder system level

2. In the upcoming dialog box, choose Manually Assign Item Category: 3. On the Change view “GTS: Assignment of backend system item category to cust. item category” screen, choose New entries: Field name

Description


Application level


Log. System


Backend sys. item cat.

YTAN


EXORD1

Note


Description


Application level


Log. System



YTAN


EXDLV1

Note

5. Save your entries. 6. Access the activity using the following navigation option: Transaction Code

SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  General settings  Document structure  Assignment of item categories from feeder systems  Assign item category at feeder system group level

7. In the upcoming dialog box, choose Manually Assign Item Category. 8. On the Change view “GTS: Assignment of item category at group backend systems” screen, choose New entries: Field name

Description


Application level


LS Group



YTAN


EXORD1

© SAP AG

Note

Page 63 of 113

SAP Best Practices


9. On the Change view “GTS: Assignment of item category at group backend systems” screen, choose New entries: Field name

Description


Note

Application level


LS Group



YTAN


EXDLV1


4.3.2

Legal Control Service

4.3.2.1


Use Here you can define the precise scope of the check of the legal regulations the system carries out for your import/export documents.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Legal control Service  Activate legal regulations

2. On the Change view “GTS: Activate service license determination” screen, select the legal regulations you want to check your documents against: Field name

Description


Legal regulation

AWV

Country

DE

Legal control import

Check: Not activated

Legal control export

2 Check: Export (exclusively)

Note

Replace other entries with 2 check


4.3.2.2

Defining Control Procedures for Text Comparison – Export

Use

© SAP AG

Page 64 of 113

SAP Best Practices


To set up the classification help for export lists, you need to define control procedures for text comparison. To enable the product classification according to the text comparison, you need to define a control procedure. In this procedure, the texts assigned to an export control classification number are compared to texts pertaining to a product master. These settings are standard settings. Please check if the following entries are there.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Numbering Schemes  Classification Help  Define control procedure for text comparison

2. On the Change view “GTS: Tariff assignment: Text comparison rule set” Overview screen, check if the following entry is created: Field name

Description


Comparison procedure

DEALT

Description

Control Procedure Prod. Class. Help Export List Numbers DE

Note

3. On the Change view “GTS: Tariff assignment: Text comparison rule set” Overview screen, select the comparison procedure, choose Details and check if the following settings are as follows: Field name Language for compare

Description

User action and values EN

Note Replace other languages with EN


4.3.2.3

Assigning Control Procedure for Text Comparison to Export Lists

Use To set up the product classification, you need to assign the control procedure for text comparison. These control procedures apply comparison rules which are language-specific. Depending on the language of the texts assigned to an export control classification number, different control procedures are to be assigned. These settings are standard settings. Please check if the following entries are there.

Procedure © SAP AG

Page 65 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Numbering Schemes  Classification Help  Assign control procedure for text comparison to export lists

2. On the Change view “GTS: Assignment of control procedure for text comparison to export lists” screen, assign the comparison procedure: Field name

Description


Scheme

DEALN

Language

EN


DEALT

Note


4.3.2.4

Assigning Determination Procedure for Active Legal Regulations

Use You need to maintain a determination procedure to establish active legal regulations for a service. You have to assign a determination table to this determination procedure. These settings are standard settings. Please check if the following entries are there


SPRO

IMG in GTS

SAP Global Trade Services  SAP Compliance Management  Legal Control Service  Assign determination procedure for active legal regulations

2. On the Change view “GTS: Service license determination” screen, check if the following entry is created: Field name

Description



LELDT

Description

GTS: Determination of legal regulation licenses

4.3.2.5

Note

Defining Determination Scheme to Automatically Determine License Types

Use

© SAP AG

Page 66 of 113

SAP Best Practices


The procedure for determining license types controls the determination of license types that are relevant for a legal regulation.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Legal Control Service  Define determination scheme to automatically determine license types

2. On the Change view “Procedure for determining license types” Overview screen, choose New entries: Field name

Description



YHBP1

Description

License Type Determination Country and control class

Note

3. On the Change view “Procedure for determining license types” Overview screen, select the determination procedure, choose Assignment of determination strategy and choose New entries : Field name

Description


Sequence number

10

Determination strategy

CD05 At country level

Sequence number

20

Determination strategy

CD08 At control class level

Note


4.3.2.6

Defining Control Settings for License Determination Service

Use Here you have to make the following settings for each legal regulation: Product Master Maintenance: There are two options regarding the scope of the customs products check. You can either specify that every product is subject to legal control or that no products are subject to legal control. If all products are to be checked, you can set individual products in the customs product master to No Control. If you have specified that no products are subject to the legal check, you can activate the check in the customs product master by setting the Individual Maintenance indicator.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Legal Control Service  Control settings for license determination Service

© SAP AG

Page 67 of 113

SAP Best Practices


2. On the Change view “Control settings for license determination service” Overview screen, select the legal regulation AWV and choose Details: Field name

Description


Product master maintenance

B Only specific selected product is subject to legal control

Control grouping activated

x

Partner group country of departure

PGLDT1

Partner group country of destination

YPGLT2

Procedure for determining license types

YHBP1

Transfer of legal control data

Do not transfer license

Note

3. On the Change view “Control settings for license determination service” Overview screen, select the legal regulation AWV, choose Allowed statuses and check if the settings are as follows: Field name

Description


Note

Status

0001

Description

License created

Status

0002

Description

License application submitted to authorities

Status

0003

Description

License application rejected by authorities

Status

0004

Description

License active

Status

0005

Description

License submitted to authorities for extension/renewal

Status

0006

Description

License expired

4. On the Change view “Allowed statuses” Overview screen, choose Assign time zone to deadline type and check if the settings are as follows: Field name

Description


Type of date

Valid-from date

VALFRO

Time zone Type of date Time zone

Note

CET Valid-to date

VALTO CET


© SAP AG

Page 68 of 113

SAP Best Practices

4.3.2.7


Defining License Types

Use In this step, you determine license types you want to use in the license determination service.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Legal Control Service  Define license types

2. On the Change view “Legal control: License type” Overview screen, choose New entries: Field name

Description


Legal regulation

AWV

License type

EAGP

Note

Indiv. Export license - partner function specific (Germany)

3. On the Change view “Legal control: License type” Details screen, select the legal regulation and choose Details: Field name Import/Export

Description

User action and values 2 Export/Dispatch

Foreign trade organization unit

X

Business Partner

X

Partner function

X

Control class

X

Document number

X

Country of Dept./Dest.

X

Partner Grp Functions

YPGLT2

Quantity update

Note

X

Basis for quantity update

QUAITM document item quantity

Foreign Trade Org. Unit

B Unlimited number of possible attributes

Legal Unit

No possible attributes

Business Partner


Country of Dept. / Dest.


© SAP AG

Page 69 of 113

SAP Best Practices

Field name


Description


Document number

A Precisely one possible attribute

Product number

No possible attributes

Control class


Text determination procedure

SLL_LCLIC1 License texts

License type

EAGP

Note

4. On the Change view “Legal control: License type” Details screen, choose Allowed statuses: Field name

Description


Sequence

1

Status

0001

Note

Point of access Description

License Created

Sequence

2

Status

0002


License application submitted to authorities

Sequence

3

Status

0003

Point of access

2

Description


Sequence

4

Status

0004


License Active

Sequence

5

Status

0005

Point of access

4

Description

License submitted to authorities for extension/renewal

Sequence

6

Status

0003

Point of access

5

Description


Sequence

7

© SAP AG

Page 70 of 113

SAP Best Practices

Field name


Description


Status

Note

0006


License expired


4.3.3

Embargo Check Service

4.3.3.1

Activating Document Type

Use First, you need to activate the embargo check service at customs document level. These settings are standard settings. Please check if the following entries are there


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Document Structure  Activate Document types

2. On the Change view “GTS: Activate service embargo” Overview screen, check if the following document types are created: Field name

Description


Note

Customs doc. type

EXPDLV

Deliveries

Customs doc. type

EXPORD

Sales orders

4.3.3.2

Activating Item Categories

Use To enable the system to carry out the embargo check service, you have to activate the service both at document type level and item category level. Activating the service at only one of these levels will not suffice. These settings are standard settings. Please check if the following entries are there


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Document Structure  Activate Item categories

© SAP AG

Page 71 of 113

SAP Best Practices


2. On the Change view “GTS: Activate service embargo” Overview screen, check if the following item categories are created: Field name

Description


Note

Customs document item category

EXDLV1


Customs document item category

EXORD1


4.3.3.3


Use In this step, you can define the precise scope of the embargo check service.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Embargo check service  Activate legal regulations

2. On the Change view “GTS service embargo: Activate legal requirements” Overview screen, select the legal regulations you want to check your documents against and check if the settings are as follows: Field name

Description


Legal regulation

EMBUN

Country

DE




3 Check: Dispatch/Export (Excluding Domestic)

Note


© SAP AG

Page 72 of 113

SAP Best Practices

4.3.3.4


Assigning Determination Procedure to Determine Active Legal Regulations

Use By using the determination procedure for active legal regulations, you can select legal regulations that are to be checked by the system. At present, legal regulations can be determined at country of departure/destination level (country of the legal unit). These settings are standard settings. Please check if the following entries are there


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Embargo check service  Legal regulations  Assign determination procedure to determine active legal regulations

2. On the Change view “GTS service embargo: Determine active legal regulations” Overview screen, check if the determination procedure is created: Field name

Description



LEEMB

Description

GTS: Determination of legal regulation embargo

4.3.3.5

Note

Activating the Embargo Service Control

Use To define which partners are to be checked during the embargo check, you have to assign the partner groupings you want to include. These settings are standard settings. Please check if the following entries are there


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Embargo check service  Legal regulations  Control embargo check

2. On the Change view “GTS legal requirement: Control service embargo” Overview screen, check if the settings are as follows: Field name

Description


Legal regulation

EMBUN

Partner group for import

PGEMB1

© SAP AG

Note

Page 73 of 113

SAP Best Practices

Field name


Description

Partner group for export

4.3.4 4.3.4.1


Note

PGEMB2

Sanctioned Party List Screening Activating Business Partner at Business Partner Role Level

Use In this step, you determine business partners to be checked by the SPL service.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Sanctioned party list screening Service  Activate business partner at business partner role level

2. On the Change view “GTS: Business partner control:” Overview screen, check if the entries are as follows: Field name

Description


Application object

BUPA

Partner function

SLLCPC

Application object

BUPA

Partner function

SLLCPS

Note

Customer

Supplier

3. On the Change view “GTS: Business partner control:” Overview screen, select the partner role and choose Details: Field name

Description


Note

Partner function

SLLCPC

Customer

Type of SPL block

0 Process is not blocked – service activates block

Time of SPL check

1 Synchronous – when document is updated

Partner function

SLLCPS

Type of SPL block

0 Process is not blocked – service activates block

Time of SPL check

1 Synchronous – when document is updated

Supplier


© SAP AG

Page 74 of 113

SAP Best Practices

4.3.4.2



Use You need to activate legal regulations for each country (import country and export country) so that the system can determine legal regulations that are require for an SPL check.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Sanctioned party list screening Service  Activate legal regulations

2. On the Change view “GTS: Service: Sanctioned party list: Activate legal regulations” screen, select the legal regulations you want to check your documents against and check if the settings are as follows: Field name

Description


Legal regulation

SPLUS

Country

DE




4 Check: Dispatch/Export (including domestic)

Note


4.3.4.3

Assigning Determination Procedure to Determine Active Legal Regulations

Use For each legal regulation, you need to define which procedure is to be used for determining the area of validity. These settings are standard settings. Please check if the following entries are there


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Sanctioned party list screening Service  Assign determination procedure to determine active legal regulations

2. On the Change view “GTS: Service sanctioned party list: Determine active legal regulations” screen, check if the determination procedure is created: Field name Determination procedure

© SAP AG

Description


Note

LESPL

Page 75 of 113

SAP Best Practices

Field name


Description

Description

4.3.4.4


Note

GTS: Determination of legal regulation "SPL"

Defining Control Procedure for Address Comparison

Use To enable the system to carry out SPL checks you have to determine the rules for documents’ screening.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Sanctioned party list screening Service  Define control procedure for address comparison

2. On the Change view “GTS: Sanctioned party list screening:” screen, check if the comparison procedure is created: Field name

Description



SPLUS

Description


Language for compare

EN

Search term orgin

Basis for comparison is string from comparison index

Note

3. On the Change view “GTS: Sanctioned party list screening:” screen, choose GTS: Rule set address/string comparison: Detailed: Field name

Description


Note

Search term origin

C1 Keyword generated from country

Check object

X

Linking operator

0 Logical or (at least one OR operation satisfied)

Search term origin

N1 Keyword generated from name

Check object

X

Linking operator

1 Logical and

4. On the Change view “GTS: Rule set address/string comparison: Details” screen, select the search term Origin and choose Details: Field name Search term origin

© SAP AG

Description


Note

C1 Keyword generated from country

Page 76 of 113

SAP Best Practices

Field name


Description


Note

Search term origin: Scope of check

Basis for comparison is string from comparison index

Relational operator

B Comparison index and keyword from address are identical

Search term

100

Original form

100

Search term origin

N1 Keyword generated from name

Search term origin: Scope of check

2 Basis for comparison is string from comparison index and address

Relational operator

A Comparison index contained in keyword from address

Search term

80

Recommende d to increase it.

Original form

65

Recommende d to increase it.

5. On the Change view “GTS: Rule set address/string comparison: Details” screen, choose GTS: Assignment of address fields to rule set and select the address fields: Field name

Description


Address compare object

ADRC object for comparison: address

Field name

Country



Field name

Name1



Field name

Name2



Field name

Name3



Field name

Name4

Note

6. If the City and Street fields are created, delete them. 7. Save your entries.

4.3.4.5

Controlling Sanctioned Party List Screening

Use

© SAP AG

Page 77 of 113

SAP Best Practices


In this step, you assign a rule set to a legal regulation. Under List Types you define the boycott lists to be used in an SPL check.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Compliance Management  Sanctioned party list screening Service  Control Settings for Sanctioned party list screening Service

2. On the Change view “Control settings for SPL service:” Overview screen, select the legal regulation and choose List type: Field name

Description


Legal regulation

SPLUS

Description


Note

3. On the Change view “List type:” Overview screen, choose New entries: Field name

Description


Type of list

YHBPM

Description

Sanctioned party list Best Practices

Note

Maintained manually Maximum number of index entries per object Name

5

Minimum length of index entries Name

4

4. On the Change view “List type:” Details screen, choose Reference type and check if the settings are as follows: Field name

Description


Type of reference

AKA

Description

Also known as

Type of reference

FKA

Description

Formerly known as

Type of reference

NKA

Description

Not known as

Note

5. On the Change view “Reference type:” Overview screen, choose Assign time zone to deadline type and add the time zone: Field name

Description


Type of date

ETYADD

Qualifier text

Date of inclusion

Time zone

CET

© SAP AG

Note

Page 78 of 113

SAP Best Practices

Field name


Description


Type of date

VALFRO

Qualifier text

Valid-from date

Time zone

CET

Type of date

VALTO

Qualifier text

Valid-to date

Time zone

CET

Note


© SAP AG

Page 79 of 113

SAP Best Practices


4.4 Customs Management 4.4.1

Prerequisite Settings in ERP

Check if the following settings are made. For Outbound Scenario: 

A separate Proforma invoice for customs document interface has been created. See the chapter Defining Billing Document Type in ERP in this guide



Billing document type YHF8 must be activated on ERP side for application level SDOC. See the chapter Transferring Documents to SAP Global Trade Services (ERP) in this guide

For Inbound Scenario: 

Inbound Delivery type EL must be activated on ERP side for application level MMOB. See the chapter Transferring Documents to SAP Global Trade Services (ERP) in this guide



Mapping of relevant standard document types & item categories has been carried out. See the chapter Transferring Documents to SAP Global Trade Services (ERP) in this guide

4.4.2

Legal Regulations

4.4.3

General Settings for Customs Management

4.4.3.1

Defining Country Groups Country groups for duty determination come via Data Provider or by manual input. For the Best Practices scenario, country groups defined in Risk Management will suffice. See the chapter Define Country Group in Risk Management in this guide.

4.4.3.2

Defining Conditions and Output Parameters for Messages (PPF Actions)

Use The purpose of this Customizing activity is to define a standard printer in a standard action template.


/SAPSLL/PPFDETC

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Communication Processes  Define Conditions and Output Parameters for Messages (PPF Actions)

2. On the Conditions for Actions: Change screen, choose Technical Names.

© SAP AG

Page 80 of 113

SAP Best Practices


3. Double-click the action profile LLS_DE_CU_EX on the left hand side of the screen. 4. In the right part of the screen, double click the action definition GTS_PRN_EU_SAD_001. 5. In the lower group frame, select the Processing Details tab page. 6. On the Printer tab page, make the following entries: Field name

Description


OutputDevice

For example: LP01

Number of copies

1

Print immediately

X (select)

Note

7. Save your entries and leave the activity.

4.4.3.3

Define Message for Communication Process

Use The purpose of this Customizing activity is to create a new message for the Communication Process.


/SAPSLL/PPFDETC

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Communication Processes  Define Messages for Communication Processes

2. On the Change View “GTS: Messages for Activity”: Overview choose New Entries. 3. In the New Entries: Details of Added Entries make the following settings: Field name

Description


Message

YD041

Description

EU: Dispatch Note Model T1 / T2 (0735 / 0736) with Layout

Responsibility

A Active

Action Definition

GTS_PDF_EU_SAD_T_L

Message Type

1 Final Status: Activity Has Been Successfully Completed

Note

4. Save your entries and leave the activity.

4.4.3.4

Control Settings for Communication Processes

Use The purpose of this IMG activity is to define the communication processes with the customs authorities and to assign messages to each process.

Procedure © SAP AG

Page 81 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings -> Communication Processes -> Define Control Settings for Communication Processes

2. On the Change View “Process Template”: Overview screen, select the entry TRSDE and choose Process. 3. In the Change View “Process”: Overview screen select the entry TRSO and choose Activities. 4. In the Change View “Activities”: Overview screen select the entry TRDCV and choose Messages. 5. In the Change View “Message”: Overview screen choose New Entries and enter the following data: Field name

Description


Message

YD041

Code List Procedure

TRSDE

Note


4.4.3.5

Assigning Document Type at Feeder System Group Level

Use The purpose of this activity is to map document types from the feeder system to the corresponding documents in the GTS system.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Document Structure  Assignment of Document Types from Feeder Systems  Assign Document Type at Feeder System Group Level

2. In the Determine Work Area: Entry dialog box, enter the Work Area MMOB and choose Continue. 3. On the Change View “GTS: Assign Docmt Type BSyst. Group to Customs Shpmt Type screen, enter the following data: Field name

Description


Logical System Group

The logical system group you have defined in the beginning, for example, KS7 Group

Feeder System Doc. Type

EL

© SAP AG

Note

Page 82 of 113

SAP Best Practices

Field name


Description

Customs Doc. Type


Note

TRLOIM

Customs Shipment (Transit): Arrival / Presentation

4. Save your entries and go back to the IMG menu. 5. Choose the transaction again and enter the Work Area SDOC. 6. On the Change View “GTS: Assign Docmt Type BSyst. Group to Customs Shpmt Type screen, enter the following data. Field name

Description



The logical system group you have defined in the beginning, for example KS7 Group

Feeder System Doc. Type

YHF8

Customs Doc. Type

TRLOEX

Note

Customs Shipment (Transit): Export


The additional required document types have already been mapped during Configuration of the Compliance Management scenario. See the chapter Assign Document at Feeder System Group Level in Compliance Management.

4.4.3.6

Assigning Item Category at Feeder System Group Level

Use The purpose of this activity is to map item categories from the feeder system to the corresponding documents in the GTS system.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Document Structure  Assignment of Item Categories from Feeder Systems  Assign Item Categories at Feeder System Group Level

2. In the Determine Work Area: Entry dialog box, enter the Work Area SDOC and choose Continue. 3. On the Change View “GTS: Assign BS Group Item Cat. to Custms Shipment Item Ca screen, enter the following data:

© SAP AG

Page 83 of 113

SAP Best Practices

Field name


Description



The logical system group you have defined in the beginning, for example, KS7 Group

Feeder System Item Cat.

YTAN

Customs Doc. Item Cat.

CLPOS

Note

Item for customs shipment


The additional required item categories have already been mapped during the configuration of the Compliance Management scenario. See the chapter Assign item Categories at Feeder System Group Level in Compliance Management.

© SAP AG

Page 84 of 113

SAP Best Practices

4.4.3.7


Assigning Packaging Material Type at Feeder System Group Level This activity has to be carried out only after integration of packaging data is completed. This is not the case in this SAP Best Practices scenario.

4.4.3.8

Defining Default Data for Date Fields

Use In this IMG activity, you specify procedures and rules for automatically filling in date fields at application header level, for example, on the Transport and Logistics Costs tab pages.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Procedures for Defaulting Data  Define Default Data for Date Fields

2. On the Change View “Default Procedure”: Overview screen, choose New Entries and enter the following data: Field name Description User action and values Note Procedure

TRSC

Description

NCTS transit inbound

3. Save your entries. 4. Select the entry you have just created, choose Default Rules and enter the following data: Field name

Description


Targ. Fld.

Declaration date / presentation date

Src. Field

Current date

Description

NCTS transit inbound

Default Data Active

X

Note

5. Save the entry.

4.4.3.9

Defining Determination Procedure for Defaulting Data

Use In this IMG activity you assign your procedures for defaulting data to unique processes in the application..


© SAP AG

SPRO

Page 85 of 113

SAP Best Practices

IMG in SAP GTS

H42: Configuration Global Trade Services (GTS) SAP Global Trade Services  SAP Customs Management General Settings  Procedures for Defaulting Data  Define Determination Procedure for Defaulting Data

2. On the Change View “GTS: Procedure for Determining Default Data Provider”: Default Procedure”: Overview screen, choose New Entries (or modify the existing entry) and enter the following data: Field name Description User action and values Note Legal Regulation

TRSDE

Doc. Type

TRLOIM

Process

TRSC

Proced. (Data)

TRSC

Proced (Partner)

No entry here

Proced. (General)

No entry here


4.4.3.10

Defining Default Data for Partners

Use In this IMG activity you specify procedures and rules for automatically filling in partner fields at application header level.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Procedures for Defaulting Data  Define Default Data for Partners

2. On the Change View “Default Procedure”: Overview screen, choose New Entries and enter the following data: Field name Description User action and values Note Procedure

TRSC

Description

NCTS Inbound

3. Save your entries. 4. Select the entry you have just created, choose Default Rules and enter the following data: Field name

Description


Note

Targ. Fld.

CUSSTL

Processor

Src. Field

CUSVBS

Legal Unit

Sequence Number

1

5. Save the entry.

© SAP AG

Page 86 of 113

SAP Best Practices

4.4.3.11


Maintaining Code Lists

Use For the Customs Shipment documents you need to maintain entries for the Code Lists and assign them to legal regulations. This enables you to restrict the selection options in the application's services to the relevant information and to control the default values for the input helps


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Customs Management General Settings  Customs Code Lists -> Maintain Customs Codes Lists for Legal Regulation

2. On the Maintain Customs Code Lists screen, choose New Entries and enter the legal regulation ATLAS. 3. Choose Execute. 4. In the GTS: Maintain Customs Code Lists screen enter the Customs Code Lists ADPRO Additional Procedure via input help. 5. Choose the button Start Maintainance. 6. On the Change “View GTS Additional Procedure Overview “ screen choose New Entries and make the following entries. Field name

Description


Additional Procedure

5F0

Description

Registration for Import Turnover Tax only

Note

7. Choose Go To -> Translation. 8. Choose language DE. 9. In the Maintain Text in Other Languages window enter the German text Anmeldung nur hinsichtlich der EUSt. 10. Save your entries.

4.4.4

Authorization Management In this Best Practices scenario no settings for Authorization Management have been made. Several templates are provided for the customer. You can find and maintain these templates in the Customizing under the following path: SAP Global Trade Services  SAP Customs Management  Authorization Management  Define Authorizations.

© SAP AG

Page 87 of 113

SAP Best Practices

4.4.5 4.4.5.1


Application Settings (GTS) Maintaining Business Partner Person Responsible for Processing

Use In this activity, you create a business partner for Customs Management.


BP

SAP GTS

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Master Data  Maintain Business Partner

2. On the Maintain Business Partner screen, enter a name for the business partner (for example, H95CUSMAN) and choose Create Person. Choose the role BUP003 (employee) and make the following entries: Field name

Description


First name

Customs manager of company

Last name

Responsible

Street

Company street

Postal Code

For example: 12345

Country

DE

Time Zone

CET

Comments

Responsible for export

Note

3. Save the business partner.

4.4.5.2

Creating Customs Offices and Assigning to Official Customs Office Number

In this step you create the Customs Offices Border DE005874 and Reception DE005866 as business partner and then you assign them to Official Customs Office number.

Use In this activity, you create customs offices for border and reception.


BP

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Master Data  Customs Offices  Maintain Customs Offices

2. On the Maintain Business Partner screen, enter the following data. Field name Business partner

© SAP AG

Description


Note

DE005874

Page 88 of 113

SAP Best Practices

Field name


Description


Create in Role

SLLCOF - customs office

Name

Customs office of destination

Street


House Number

1

Postal Code

12345

City


Country

DE

Time zone

CET

Language

English

Address Valid from

Today’s date

Address Valid to

End of a following year

Note

3. Save your entries. 4. Repeat the steps for the reception DE005866 using the following name: Customs Office of Reception / Departure. 5. Assign the customs offices you just have created to an official customs office. Access the activity using one of the following navigation options: Transaction Code

/SAPSLL/BP_MAIN_DNR

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Master Data  Customs Offices  Customs Office Number

6. On the GTS: Business Partner: Maintain Office Numbers screen, enter the following data: Field name

Description


Legal Regulation

ATLAS – customs processing system

Business partner

DE005866

Note

7. Choose Execute. 8. In ERP you can create customs offices only with 6 characters. Therefore, you normally assign the official number of a customs office that has more characters in the field OFN. In this example, the same number DE005866 is assigned as it is already the official one. 9. Repeat step 8 for the Customs Office of Destination and assign the same number. 10. Repeat steps 6 – 8 for the legal regulation TRSDE (NCTS) Transit Procedure Germany – ATLAS Transit.

4.4.5.3

License Master:

Use In this activity, you create the license master for Authorizations and Guarantees in transit procedures and the license master for Authorizations in customs procedures.

Procedure Create Authorizations in Transit Procedures 1. Access the activity using one of the following navigation options:

© SAP AG

Page 89 of 113

SAP Best Practices


Transaction Code

/n/SAPSLL/LCLICA01 (Create), *02 (Change), *03 (Display

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Transit / Presentation  Securities and Authorizations  Authorization  Create

2. On the GTS: Transit Procedure: Create Authorization screen, enter the following data and choose Enter. Field name

Description


Note

Legal Regulation

TRSDE (NCTS) Transit Procedure Germany – ATLAS Transit

Authorization Type

ZE – Authorized Consignee

Recipient

3. On the GTS: Transit Procedure: Create Authorization screen, enter the following data: Field name

Description


Authorization

Note Internal number assignment: 1100000000000000001

External number

DE5864ZE0079

Holder

OBP01

Valid from

Beginning of the current year

to


Authorization active

X

Set the flag for the activation of the authorization

4. On the left hand side, select Foreign Trade Organization, insert a new row and enter OBP01. 5. On the left hand side, select Legal Units, insert a new row and enter LBP01 and BP01 in the Transfer / Presentation Lt Field. 6. Save your entries and go back to the first screen. 7. Repeat steps 1-3 with the authorization type ZV – Authorized Consignor (sender) and for the external number DE5864ZE0078 (internal number assignment: 1100000000000000002).

Create Securities 1. Access the activity using one of the following navigation options: Transaction Code

/SAPSLL/LCLICB01(Create), *02 (Change), *03 (Display)

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management v Transit / Presentation  Securities and Authorizations  Security  Create

2. On the GTS: Transit Procedure: Create Guarantee screen, enter the following data and choose Enter: Field name

Description


Note

Legal Regulation

TRSDE (NCTS) transit procedure Germany – ATLAS transit

Security Type

1 – comprehensive guarantee

3. On the GTS: Transit Procedure: Create Authorization screen, enter the following data:

© SAP AG

Page 90 of 113

SAP Best Practices

Field name


Description


Note

Security

Internal number assignment: 1300000000000000000

External number

DE/9550/GE/0101

Valid from


to


Security active

X


Enter also a comment in the text field. Attributes  Customs Office

DE005866

Customs office of reception / departure /


Create Authorizations in Customs Procedures 1. Access the activity using one of the following navigation options: Transaction Code

/SAPSLL/LCLICC01 (Create), *02 (Change), *03 (Display)

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Customs Processing Import / Export  Authorizations for Simplified Procedure  Create

2. On the GTS: Customs Processing: Create Authorizations screen, enter the following data and choose Enter. Field name

Description


Note

Legal Regulation

ATLAS customs processing system Germany

Authorization Type

VV – simplified customs declaration procedure

3. On the GTS: Transit Procedure: Create Authorization screen, enter the following data: Field name

Description


Security

Note Internal number assignment: 1200000000000000000

External number

5864A10157

Holder

OBP01

Valid from


to


Authorization active

X


Attributes  Customs Office

DE005866

Customs office of reception / departure /

4. On the left hand side, select Foreign Trade Organization, insert a new row and enter OBP01. 5. On the left hand side, select Legal Units, insert a new row and enter LBP01. 6. Save your entries.

© SAP AG

Page 91 of 113

SAP Best Practices

4.4.5.4


Maintaining Trader Identification Number (TIN)

Use A trader identification number is assigned to a business partner that represents a legal unit or organization. It is used to uniquely identify the legal unit or organization when exchanging messages with a customs authority.


/SAPSLL/BP_MAIN_COMP

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Master Data  Maintain Trader Identification Number

2. In the GTS: Business partner: Maintain Own Trader Data screen enter the following data: Field name

Description


Legal Regulation

ATLAS – ATLAS customs processing system - Germany

Business Partner (in group frame Foreign Trade Organization)

OBP01

Note

3. Choose Execute. 4. On the Maintain Data for Legal Unit / Org. screen, enter the TIN number, for example 9001786. 5. Save your entry.

4.4.5.5

Maintening Business Identification Number (BIN)

Use The business identification number is assigned to a legal unit (business partner). It represents a code with which users sign declarations to customs authorities, similar to a signature.


/SAPSLL/BP_MAIN_BIN (BIN)

GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Master Data  Maintain Business Identification Number

2. On the GTS: Business partner: Maintain Business Identification Number screen, enter the following data: Field name Legal Regulation

© SAP AG

Description


Note

ATLAS – ATLAS customs processing system - Germany

Page 92 of 113

SAP Best Practices


Field name

Description

Business Partner (in group frame Foreign Trade Organization)


Note

OBP01

3. Choose Execute. 4. On the Maintain Business Identification Number screen, enter the BIN number, for example 2003051409873218122032901. 5. Save your entry.

4.4.5.6

Message Determination Transit & Message Determination Customs Declaration

Use In this activity you define messages for Customs Declaration.


/SAPSLL/PRNDT1

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Customs Processing Import/Export  Message Determination

2. In the Change View “GTS: Determine Message for Action”: Overview screen choose New Entries and enter the following data.

Document Type

Legal Regulation

Activity Message

Name of table/view

CULOIM

ATLAS

M0040

/SAPSLL/V_PRNDT1

TRLOIM

TRSDE

M0160

/SAPSLL/V_PRNDT1

TRLOIM

TRSDE

M0140

/SAPSLL/V_PRNDT1

CULOIM

ATLAS

M0010

/SAPSLL/V_PRNDT1

CULOIM

ATLAS

M0170

/SAPSLL/V_PRNDT1

CULOIM

ATLAS

M0150

/SAPSLL/V_PRNDT1

CULOEX

ATLAS

P0120

/SAPSLL/V_PRNDT1

TRLOIM

TRSDE

M0120

/SAPSLL/V_PRNDT1

TRLOEX

TRSDE

M0110

/SAPSLL/V_PRNDT1

TRLOEX

TRSDE

M0100

/SAPSLL/V_PRNDT1

TRLOIM

TRSDE

M0130

/SAPSLL/V_PRNDT1

CULOEX

ATLAS

P0010

/SAPSLL/V_PRNDT1

CULOEX

ATLAS

P0080

/SAPSLL/V_PRNDT1


© SAP AG

Page 93 of 113

SAP Best Practices

4.4.5.7


Determining Printer

Use In this activity you determine a standard printer.


/SAPSLL/PRNDT2

SAP GTS Menu

/N/SAPSLL/MENU_LEGAL  SAP Customs Management  Customs Processing Import/Export

2. On the SAP Customs Management: Customs Processing for Import / Export screen choose Printer Determination -> Execute. 3. In the Change View “Determine Output Device for Foreign Trade Documents”: Overview screen choose New Entries and make the following entries. Field name

Description


Message

P0080

Legal Unit

LBP01

Output Device

Enter your own printer which is pdf enabled

Note Custom Shipment document with layout

Note that the standard system printer LP01 is not configured for pdf forms


© SAP AG

Page 94 of 113

SAP Best Practices

4.4.6


ALE Settings

4.4.6.1

Maintaining EDI Port Definition (GTS)

Use For the Customs Management scenario you need to create an EDI communication port.




Transaction Code

WE21

SAP GTS menu path

SAP Global Trade Services  System Communication / Workflow  EDI Communication  EDI Port Definition  EDI Port Definition  Execute

...

2. On the Port in IDoc processing screen, select Transaction RFC and choose Create. 3. In the Ports in IDoc processing dialog box, select your own port name and enter the port BP HT GTS in the the Name field. Choose Enter. 4. On the Creating a tRFC port screen, enter the followin data: Field name

Description

Description


Note

GTS Converter

RFC destination

AC

Template

5. Save your entires.

4.4.6.2

Maintaining EDI Partner Profile / Header

Use For the Customs Management scenario you need to maintain the partner profile. However, in this step you only create a pro forma EDI connection to be able to release customs documents. The integration with an external communication system (e.g. Seeburger) is not shown in this Best Practices scenario.




Transaction Code

WE20

SAP GTS menu path

SAP Global Trade Services  System Communication / Workflow  EDI Communication  EDI Port Definition  EDI Partner Profile  Execute

...

2. On the Partner Profils screen, select the Partner type GP and choose Create. 3. Enter the following data: Field name Partner no.

Description

User action and values DE005866

Type

US

Agent

© SAP AG

Note

Enter the user with which you are logged in.

Page 95 of 113

SAP Best Practices

Field name


Description


Language

Note

EN

4. In the Outbound parameter group box, choose the required icon to add outbound parameters. 5. On the Partner profiles: Outbound parameters screen, enter the following data: Field name

Description


Message type

/SAPSLL/CUS_AWB

Receiver port

BP HT GTS

Transfer IDoc Immediately

X

Pack Size

1

Basic type

/SAPSLL/CCECUS02

Cancel Processing after Syntax Error

Note

X

6. Save the outbound parameters and go back to the previous screen. 7. Repeat the steps 4 – 7 for the following message types: Message type /SAPSLL/TRS_AN /SAPSLL/TRS_DEC /SAPSLL/TRS_UR 8. Save your entries.

Note that for a complete integration with a customs system you need to set up additional message types.

© SAP AG

Page 96 of 113

SAP Best Practices


4.5 Risk Management 4.5.1

Defining Groups of Partner Functions

Use In this step the partner functions are assigned to a group.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Partner Structure  Define Groups of Partner Functions

2. On the Change View “Legal Services”: Partner Groups”: Overview screen, choose New Entries and enter the following Partner Group: Field name

Description


Partner Grouping

YHPREF

Description

Partner Group for Preference Management

Note

3. Save your entries. 4. Select the entry you just created and choose Assign Partner Functions. 5. Choose New Entries and enter the following data: Field name

Description


Sequence Number

1

Partner Function

LF

Import/Export

Import/Arrival

Note

Vendor

6. In the second line enter the following data: Field name

Description


Sequence Number

2

Partner Function

WE

Import/Export

Export / Dispatch

Note

Ship-to-party


© SAP AG

Page 97 of 113

SAP Best Practices

4.5.2


Legal Regulations

4.5.2.1

Defining Country Groups

Use In this step the countries used in this scenario are assigned to a group.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal Regulations  Define Country Group

2. On the Change View “GTS”: Country Group”: Overview screen, choose New Entries and enter the following data: Field name

Description


Country Group

YH_EU

Country Group

YH_EFTA

Country Group

YH_OTHERS

Note


4.5.2.2

Assigning Countries to Preference Zones

Use In this step the countries are assigned to a preference zone.


/SAPSLL/CTYGPA

SAP GTS

/n/sapsll/menu_legal  SAP Global Trade Services  SAP Risk Management  Preference Processing Service – Master Data  Preference Zones  Assign Countries to Preference Zone  Execute

2. On the Change Legal Services: Assignment of a Country to Country Group screen, make the following entries: Country

Country Group

Description (generated automatically)

Country Grouping (generated automatically)

DE

YH_EU

Germany

European Community

FR

YH_EU

France

European Community

CH

YH_EFTA

Switzerland

EFTA countries

LI

YH_EFTA

Lichtenstein

EFTA countries

IS

YH_EFTA

Iceland

EFTA countries

NO

YH_EFTA

Norway

EFTA countries

© SAP AG

Page 98 of 113

SAP Best Practices


Country

Country Group

Description (generated automatically)

Country Grouping (generated automatically)

RO

YH_OTHERS

Romania

Other countries

BG

YH_OTHERS

Bulgaria

Other countries


4.5.2.3

Defining Legal Regulation

Use In this step you define the legal regulations used in the preference scenario.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal Regulations  Define Legal Regulation  Execute

2. On the Change View “Legal Regulation”: Overview screen, choose New Entries and make the following entries for Legal Regulation: Field name

Description


Legal Regulation

YHEFT

Legal Regulation

YHOTH

Note

3. Select the newly created entries, choose Assign Country Groups and assign the country groups as shown in the following table: Field name

Description


Legal Regulation

YHEFT

Country Group

YH_EU

Country Group

YH_EFTA

Legal Regulation

YHOTH

Country Group

YH_EU

Country Group

YH_OTHERS

Note


4.5.2.4

Defining Determination Procedure for Active Legal Regulations

Use In this step you maintain a determination procedure to establish the active legal regulations for a service.


© SAP AG

SPRO

Page 99 of 113

SAP Best Practices

IMG in SAP GTS

H42: Configuration Global Trade Services (GTS) SAP Global Trade Services  General Settings  Legal Regulations  Define Determination Procedure for Active Legal Regulations

2. On the Change View “Procedure for Determining Active Legal Regulations”: Overview screen, choose New Entries and make the following entries for Legal Regulations: Field name

Description


Determination Procedure

Note

YHPRE

3. Save your entries. 4. Select the entry you just created, choose Assignment of Determination Strategy and make the following entry: Field name

Description


Determination Strategy

Note

ALRG01


4.5.2.5


Use In this step you activate the legal Regulations for each deaparture country.


SPRO

IMG in SAP GTS

SAP Global Trade Services  General Settings  Legal Regulations  Activate Legal Regulations at Country/Country Group Level

2. Choose New Entries and make the following entries for Legal Regulation: Field name

Description


Legal Reg.

YHEFT

Country of Dep/Des

DE

Legal Reg.

YHOTH

Country of Dep/Des

DE

Note


4.5.3 4.5.3.1

Preference Processing Service Organizational Structure

4.5.3.1.1 Defining Administrative Unit for Vendor Declarations Use

© SAP AG

Page 100 of 113

SAP Best Practices


In this step you define the administratrive unit for vendor declarations as a business partner.


BP

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  ‘Preference Processing’ Service  Organizational Structure  Define Administrative Unit for Vendor Declarations

2. On the Create Organization screen enter in fields Business Partner H96_FTO in BP role SLLMGR Business Partner (Gen.): Field name

Description


Name

Internal foreign trade organization

Country

DE

Time Zone

CET

Address Valid From

Today’s date

Address Valid to

31.12.9999

Note

3. Save the administrative unit for vendor declarations.

4.5.3.2

Activation

4.5.3.2.1

Activating Document Types

Use In this step you activate the document types needed for Risk Management.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  General Settings  Activate Document Type

2. Choose New Entries and enter the following Customs Doc. Type: Field name

Description


Customs Document Types

EXPORD

Customs Document Types

IMPORD

Note


4.5.3.2.2

Activating Item Categories

Use In this step you activate the item categories needed for Risk Management.

© SAP AG

Page 101 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  General Settings  Activate Item Categories

2. On the Change View “Activate ‘Preference Processing’ Service”: Overview screen, choose New Entries and enter the following data. Field name

Description


Item Catgy

EXORD1

Item Catgy

IMORD1

Item Catgy

CLPOS

Note

3. Save your entries

4.5.3.2.3

Activating Preference Agreements

Use In this step you activate the preference agreements.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Activate Preference Agreements

2. On the Change View “Preference Processing: Activation of Preference Agreement screen, assign the following Preference Processing Types to the existing agreements YHEFT and YHOTH. Field name

Description


Agreement

YHEFT

Preference Processing – Export Active


Agreement

YHOTH

Preference Processing – Export Active


Note


© SAP AG

Page 102 of 113

SAP Best Practices


4.5.3.3

Preference Agreement

4.5.3.3.1

Determination Procedures

4.5.3.3.1.1 Assigning Determination Procedure for Active Preference Agreements Use In this step you assign the determination procedure for active preference agreements.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management Preference Processing Service  Assign Determination Procedure for Active Preference Agreements

2. On the Change View “Preference Processing: Determine Active Preference Agreement screen, choose New Entries and enter the following data: Field name

Description

Pref. Agreemt Determin. Procedure


Note

YHPRE

3. Save your entries

4.5.3.3.2 Control Settings for `Preference Processing` Service 4.5.3.3.2.1

Defining Rule Set

Use In a rule set, you combine all the preference agreements that apply to a jurisdiction. You define the preference procedures and preference rules for each of the agreements at rule set level. You can then assign the rules and procedures to the individual agreements. To prevent an overlap between different jurisdictions (for example, NAFTA and the EU) from adversely affecting the ‘Preference Processing’ service in the application, you can separate the settings for the various jurisdictions when you are defining rule sets. In addition to a name, you also have to enter the following details for each rule set to allow the rules and procedures to be uniquely assigned. • Type of rule set A rule set groups preference agreements by jurisdiction. There can be multiple rule sets within a jurisdiction. You therefore have to specify whether each rule set is a rule set for preference agreements within the EU or NAFTA. • Numbering scheme You use a numbering scheme to choose the customs tariff that forms the basis for all the rules in the preference agreement that you want to group in this rule set.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management 

© SAP AG

Page 103 of 113

SAP Best Practices

H42: Configuration Global Trade Services (GTS) Preference Processing Service  Control Settings for ‘Preference Processing’ Service  Define Rule Set

2. On the Change View “Rule Set for Preference Agreement”: Details screen, choose New Entries and enter the following data: Field name

Description


Rule Set

YHEU

Rule Set Type

B

Number Scheme

DESTA

Note

3. Save your entry.

4.5.3.3.2.2 Control Settings for `Preference Processing` Service Use In the application, all processes take the rule set into account. In a rule set, you combine all the preference agreements that are valid in a specific jurisdiction. For each jurisdiction, you have to define a rule set and assign the respective preference agreements. You also have to specify the Currency for the threshold value and the Exchange Rate Type for translations (for example, for translations between the threshold value currency and the document currency).


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management Preference Processing Service  Control Settings for ‘Preference Processing’ Service  Control Settings for ‘Preference Processing’ Service

2. On the Change View “Control Settings for Preference Processing”: Overview screen, select the relevant preference agreement, choose Details and make the following assignments: Field name

Description


Peference Agreement

YHEFT

Rule Set

YHEU

Preference Agreement

YHOTH

Rule Set

YHEU

Note


4.5.3.3.2.3 Defining Rule Set Attribute for Preference Processing (Manual) 4.5.3.3.2.3.1

Defining Procedures

Use © SAP AG

Page 104 of 113

SAP Best Practices


If you wish to manually create and define preference agreements, you have to configure the system as described below. The concept of manually defining preference rules for each agreement is based on the similarities between the various preference agreements that apply within a given jurisdiction. In SAP Risk Management – Preference Processing, rules are therefore defined at two levels. At the first level, you define the procedures and rules for the jurisdiction level only; that is, for a rule set. This allows you to group preference rules that apply to more than one preference agreement and to minimize data maintenance. At the second level, you assign the defined rules to the various agreements in a rule set. You also specify the base rules within an agreement that the system is to use in specific circumstances.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Define Rule Set Attribute for Preference Processing (Manual)  Define Procedure for EU Rule Set

2. On the Change View “Preference: Define Procedure”: Overview screen, select the relevant preference agreement, choose New Entries and enter the rule set with procedures: Field name

Description


Rule Set

YHEU

Procedure

YH001

Description

Third Country

ThirdCtry

X

Rule Set

YHEU

Procedure

YH002

Description

HS Heading

HS Heading

X

Note


4.5.3.3.2.3.2

Defining Preference Rules - Group Together Procedures

4.5.3.3.2.3.2.1 Defining Procedure Group Use Procedures are the smallest unit of a preference rule. A procedure is a specific test method for a product with a defined HS heading. You can enter one or more procedures in a procedure group. The next biggest unit of a preference rule is a rule group, which combines one or more procedures or procedure groups. There are many different types of procedures in a preference agreement, for example: 

50-50 check (originating value greater than/equal to non-originating value)



Additional condition



Third-country proportion (check of non-originating proportion of product)



HS heading (check of proportion of a specific HS code in a product)

© SAP AG

Page 105 of 113

SAP Best Practices




No heading change (check of non-originating proportion with the same HS heading as the product)



Heading change (check of non-originating proportion with a different HS heading from the product) In this step, you define all the procedures you require for preference processing.

In this step, you define all the procedures you require for preference processing.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Define Rule Set Attribute for Preference Processing (Manual)  Group Together Procedures

2. On the Change View “Procedure Group Definition”: Overview screen, enter the rule sets and assign them to procedures as shown in the table below. Field name

Description


Rule Set

YHEU

Proced./Rule Grp

YHP001

And

X

Rule Set

YHEU

Proced./Rule Grp

YHP002

And

X

Note

3. Save your entries. 4. Select each rule set and choose Procedures within the group. 5. On the Change View “Procedures Within the Group”: Overview screen, make the following entries: Field name

Description


Rule Set

YHEU

Rule Group

YHP001

Seq. No. Proced.

1

Pref. Procedure

YH001

Operation Code

LE

Perc. Share

40,00

Rule Set

YHEU

Rule Group

YHP001

Seq. No. Proced.

2

Pref. Procedure

YH002

Seq. No. TariffNo

1

From Tariff No.

1000

To Tariff No.

2000

© SAP AG

Note

Page 106 of 113

SAP Best Practices


Field name

Description


Note

Incl./Excl.

I

Interval Selection Included

Perc. Share

0

Rule Set

YHEU

Rule Group

YHP002

Seq. No. Proced.

1

Pref. Procedure

YH001

Operation Code

LE

Perc. Share

5,00


4.5.3.3.2.3.3

Defining Preference Rules – Link Rule Groups

4.5.3.3.2.3.3.1 Defining Rule Group Use This section describes how you map preference rule hierarchies with SAP Risk Management – Preference Processing. You require hierarchies to map the complicated AND or OR operations for preference rules. Using rule group links, you can map preference rules, such as rules that refer to partial quantities of HS headings. In preference agreements these partial quantities are indicated with the prefix “ex” and only apply if the goods listed in column 2 are affected. You therefore have to link the content of column 2 as a condition to the procedures from columns 3 and 4. You link rule groups in two steps. First, you decide for which rule set you want to define the rule group and you assign a name for the rule group. You then assign the procedure groups or rule groups to the defined rule group.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Define Rule Set Attribute for Preference Processing (Manual)  Link Rule Groups

2. On the Change View “Rule Group Definition”: Overview Preference: Define Procedure”: Overview screen, select the relevant preference agreement, choose New Entries and enter the following rule set with the procedure: Field name

Description


Rule Set

YHEU

Proced./Rule Grp

YHG001

Or

X

Note

3. Select this new entry and choose Rule Group Link. 4. On the Change View “Rule Group Link”: Overview screen, enter the following subordinated groups:

© SAP AG

Page 107 of 113

SAP Best Practices

Field name


Description


Subord. Grp.

Note

YHP001 YHP002


4.5.3.3.2.3.3.2 Assigning Rules to Agreement and Classification Use As well as the rules for specific HS headings, preference agreements contain additional rules that each apply to whole agreements. You can save these rules as base rules in SAP Global Risk Management – Preference Processing. You define base rules at preference agreement level. Base rules can have the following specifications: 

Basic rule



Minimal operations rule



Set of goods

General tolerance rule You can use base rules to determine a product’s preference eligibility in the following cases: 

There are no specific preference rules for the goods in an HS heading in the agreements.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Define Rule Set Attribute for Preference Processing (Manual)  Assign Rules to Agreement and Classification

2. On the Change View “Preference: Agreement-Tariff Code Rule Group” Overview screen, choose New Entries and enter the following data: Rule Set

Agreement

Customs Tariff No

Start Date

End Date

Strd. Rule

Atlernat. Rule

YHEU

YHEFT

10000001

Today’s date

30.12.2007

YHG001

YHP002

10000001

Today’s date

30.12.2007

YHG001

YHP002

20000001

Today’s date

30.12.2007

YHG001

YHP002

20000001

Today’s date

30.12.2007

YHG001

YHP002

YHEU YHOTH YHEU YHEFT YHEU YHOTH 3. Save you entries.

© SAP AG

Page 108 of 113

SAP Best Practices

4.5.3.3.2.4


Preference Determination

4.5.3.3.2.4.1

Control Settings for Cross-Plant-Preference Determination

Use You have to decide at which organizational level the system is to aggregate vendor declarations and perform preference determination. The preference model for cross-plant preference determination aggregates the vendor declarations for a plant group and performs preference determination for cross-plant bills of material. It aggregates the results for all a product’s bills of material on a cross-plant basis. To configure cross-plant preference determination, you require as control parameters the names of the plant and plant group from the feeder system. You also need the name of the feeder system.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Organziational Structure  Define Cross-Plant Preference Model

2. On the Change View “Preference Model: Cross-Plant Determination”: Overview screen, choose New Entries and enter the Grouping of Org. Unit FS: Field name

Description

Grouping of Org. Unit FS


Note

YHGRP

3. Select this entry and choose Assignment of Plants. 4. On the Change View “Assignment of Plants”: Overview screen, choose New Entries and enter the following logical systems: Field name

Description


Note

Logical System

The locial system of your ERP system / client

For example KS7CLNT046

Plant

BP01

Logical System

The locial system of your ERP system / client

Plant

BP02

For example KS7CLNT046


4.5.3.3.2.5

Vendor Declarations

Use Vendor-based vendor declarations form the start of the preference processing cycle, and vendor declarations for customer’s purposes end the cycle. To edit and define all the required documents for vendor declarations for customer’s purposes and vendor-based vendor declarations, you have to make settings in the areas below: • Administrative unit • Control settings for data scope • Form control

© SAP AG

Page 109 of 113

SAP Best Practices

4.5.3.3.2.5.1


Defining Administrative Unit Attributes

Use SAP Risk Management – Preference Processing allows you to combine multiple organizational units, which the system then uses for preference processing. You can therefore group these units, irrespective of their position in the company structure or hierarchy. This allows you to create a unified representation of your company to request, dun, issue, and cancel vendor declarations. This reduces to a minimum the groupwide effort in communicating with vendors and customers about vendor declarations. The administrative unit represents your group as a single unit (for example, in dealings with vendors) because you only have to request or dun a vendor declaration for a delivered product once. Plantbased correspondence with the vendor is redundant and is replaced with correspondence from the administrative unit.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Organizational Structure  Define Administrative Attributes

2. On the Change View “Administrative Units”: Details screen, choose New Entries and make the following entries: Field name

Description


Administr. Unit

H96_FTO

Plant Group

YHGRP

Note


4.5.3.3.2.5.2

Control Settings for Data Scope in Vendor Declaration

Use With these control settings, you can configure the system to automatically assign all partners to the respective vendor declaration process or you can configure it in such a way that you manually start the processes for specific business partners, using the partner master. You can make these detailed settings for the following processes: 

Requesting and dunning vendor-based long-term vendor declarations



Issuing and canceling long-term vendor declarations for customer’s purposes



Issuing detailed declarations of dutiable product components (for customer’s purposes)

For each administrative unit and partner grouping, you define these processes by setting indicators. If you do not set any indicators, the system selects all the partners in a partner grouping when requesting or dunning long-term vendor declarations. If you set these indicators, you can set an additional indicator in the business partner master to choose the partners for which you want to start the individual processes. The specific selection of business partners in the master data is therefore known as Specific Activation.

Procedure

© SAP AG

Page 110 of 113

SAP Best Practices



SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management  Preference Processing Service  Vendor Declarations  Control Settings for Data Scope in Vendor Declaration

2. On the Change View “Preference: Control Settings for Vendor Declaration”: Details screen, choose New Entries and make the following entries: Field name

Description


Admin. Unit

H96_FTO

Partner Grouping

YHPREF

Note


4.5.3.3.2.5.3

Form Control for Vendor-Based Vendor Declaration

4.5.3.3.2.5.3.1 Form Data for Vendor-Based Long-Term Vendor Declaration Use To allow the system to automatically choose the correct forms and texts for the actual process that you perform in the application, you have to define appropriate control parameters. To request and dun vendor-based long-term vendor declarations and to issue and cancel longterm vendor declarations for customer’s purposes, you have to define the following form data for each administrative unit: 

Document type



Form name



Form text



Letter text

For vendor-based long-term vendor declarations, you also have to define additional details for the dunning procedure. In addition to a maximum number of dunning levels, you can assign a specific text to each dunning level. You have to define dunning levels in conjunction with the end of the validity period for the existing vendor declaration. The system then automatically issues each dunning notice on the defined date. For more information on the relationship between dunning levels and the end of the validity period for a vendor-based long-term vendor declaration, see the detailed description in the IMG activity Form Control for VendorBased Vendor Declaration.

Procedure 1. Access the activity using the following navigation option: Transaction Code SPRO IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management Preference Processing Service  Preference Agreement  Controll Settings for ‘Preference Processing’ Service  Vendor Declarations  Form Control for Vendor-Based Vendor Declaration

2. On the Change View “Form Data for Vendor-Based Long-Term Vendor Declaration”: Detail screen, choose New Entries and make the following entries:

© SAP AG

Page 111 of 113

SAP Best Practices


Field name

Description


Administr. Unit

H96_FTO

Type of Document

VDDC

Max. Dunn. Level

1

Form Name

/SAPSLL/SF_EU_VD_1

Form Text

/SAPSLL/SF_EU_VD_1207_2001

Note

3. Go back, select the entry and choose Dunning Levels. 4. On the Change View “Dunning Levels”: Overview screen, choose New entries and enter the following data: Field name Description User action and values Note Dunning Level

0

Reminder Days

-60

Text for LTVD Letter

/SAPSLL/SF_EU_VD_LETTER_REMIND

Dunn. Level

1

Reminder Days

30

Form Name

/SAPSLL/SF_EU_VD_LETTER

5. Save your data.

4.5.3.3.2.5.4

Form Control for Vendor Declaration for Customer’s Purposes

Use You also have the possibility to create a form control for customer’s purposes.


SPRO

IMG in SAP GTS

SAP Global Trade Services  SAP Risk Management Preference Processing Service  Preference Agreement  Controll Settings for ‘Preference Processing’ Service  Vendor Declarations  Form Control for Vendor Declaration for Customer’s Purposes

2. On the Change View “Form Data for LTVD for Customer’s Purposes”: Details screen, choose New Entries and make the following entries: Field name

Description


Administr. Unit

H96_FTO

Type of Document

CUDC vendor declaration for customer’s purposes

Form Name

/SAPSLL/SF_EU_VD_1207_2001

Form Text

/SAPSLL/SF_EU_VD_LETTER_OUT

Letter Text

/SAPSLL/SF_EU_VD_LETTER_OUT

Note

3. Save your data.

© SAP AG

Page 112 of 113

SAP Best Practices

4.5.3.3.2.5.5


Control Settings for Generating Vendor-Based LTVD Worklist in ERP

Use You also need to make control settings in your ERP system. These settings are necessary for the creation of the Long Term Vendor Declaration Worklist in GTS. In this step you define the countries where your vendors are located.


SPRO

IMG in mySAP ERP

Sales and Distribution  Foreign Trade / Customs  SAP Global Trade Services – Plug In  Preference: Define Worklist for Vendor-Based Long-Term Vendor Declarations

2. On the Change View “GTS: Control Settings for Vendor-Based Vend.Decl.Worklist screen, choose New Entries and make the following entries: Field name

Description


Country Organization

DE

Worklist Country

DE

Country Organization

DE

Worklist Country

FR

Note


© SAP AG

Page 113 of 113

H42 BB Config Guide GTS

Recommend Documents