GTS200 - Configuration SAP Global Trade Services

GTS200Configuration SAP Global Trade

Services

Date

Training Center

Instructors

Education Website

Participant HandbookCourse Version: 73Course Duration: 3 Day(s)Material Number: 50089356

An SAP course - use it to learn, reference it for work

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Copyright

Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Trademarks

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server areregistered trademarks of Microsoft Corporation.

IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX,S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation.

ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered

trademarks of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, MultiWin and other Citrix product names referenced herein are trademarksof Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, WorldWide 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. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countriesall over the world. All other products mentioned are trademarks or registered trademarks oftheir respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLYDISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDINGWITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTSCONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANYKIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOSTPROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDEDSOFTWARE COMPONENTS.

g20086295239

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal (in this documentation) and external (inother locations, such as SAPNet).

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2008 2008 SAP AG. All rights reserved. iii

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

About This Handbook GTS200

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor'spresentation.

iv 2008 SAP AG. All rights reserved. 2008

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

ContentsCourse Overview ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Course Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viiCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Unit 1: Connecting SAP ERP to SAP GTS ...... . . . . . . . . . . . . . . . . . . . . . 1System Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Configuration of the System Connection .. . . . . . . . . . . . . . . . . . . . . . . . . . .7

Unit 2: Basic Mapping Settings..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Mapping Settings in SAP ERP ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Mapping Settings in SAP GTS ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Unit 3: Definition and Use of Legal Regulations..... . . . . . . . . . . . . . 37Definition and Use of Legal Regulations... . . . . . . . . . . . . . . . . . . . . . . . . 38

Index ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

2008 2008 SAP AG. All rights reserved. v

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Contents GTS200

vi 2008 SAP AG. All rights reserved. 2008

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Course OverviewMain Business Scenario:

The model company has branch offices in different countries. The companymanufactures technical products that are sold throughout the world and procurescomponents and trading goods from vendors in various countries.

Target AudienceThis course is intended for the following audiences:

Project team members (technical department and IT) Consultants The training materials are not teach-yourself guides. They are complete only

in combination with the instructors explanations.

There may not be enough time to complete all the exercises during thecourse. The exercises are intended to be additional examples of the materialin the course. However, participants can also use them to deepen theirknowledge after the course.

Course PrerequisitesRequired Knowledge

Contents of GTS100 (SAP Global Trade Services Overview) or comparableknowledge

Basic knowledge of sales order processing and external procurement inSAP R/3 or SAP ERP

Basic knowledge of foreign trade law and customs law

Course GoalsThis course will prepare you to:

Make essential Customizing settings to use SAP Global Trade Services

Course ObjectivesAfter completing this course, you will be able to:

Set up communication between SAP R/3 or SAP ERP and SAP GTS Make all necessary generic mapping settings

2008 2008 SAP AG. All rights reserved. vii

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Course Overview GTS200

viii 2008 SAP AG. All rights reserved. 2008

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 1Connecting SAP ERP to SAP GTS

Unit OverviewThis unit covers the settings needed to connect an SAP R/3 or SAP ERP feedersystem to an SAP GTS system.

Unit ObjectivesAfter completing this unit, you will be able to:

Describe how SAP ERP and SAP GTS communicate Make all necessary Customizing settings to connect SAP ERP to SAP GTS

Unit ContentsLesson: System Architecture.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: Configuration of the System Connection ... . . . . . . . . . . . . . . . . . . . . . . . . . .7

2008 2008 SAP AG. All rights reserved. 1

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 1: Connecting SAP ERP to SAP GTS GTS200

Lesson: System Architecture

Lesson OverviewYou require a specific system architecture to use SAP GTS. In this lesson, you willbecome familiar with the elements of this system architecture.

Lesson ObjectivesAfter completing this lesson, you will be able to:

Describe how SAP ERP and SAP GTS communicate

Business ExampleIDES AG intends to use SAP GTS in some of its branch offices. The companyneeds to check the required system settings.

System Architecture and Data ExchangeSAP GTS is based on SAP NetWeaver Application Server technology. The actualSAP GTS software is an add-on to the SAP NetWeaver Application Server withthe technical name SLL-LEG. This software can be installed on the same SAPNetWeaver platform as SAP ERP. Normally, one client plays the role of the(logical) SAP ERP feeder system and another client plays the role of the (logical)SAP GTS system. There could also be several clients acting as different SAP ERPfeeder systems, for example, if each subsidiary company uses its own client. Theymight be connected to one or to several SAP GTS system(s).

Figure 1: System Architecture: Scenario 1


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: System Architecture

The SAP ERP feeder system(s) and the SAP GTS system are connected to eachother using standard interfaces. In this scenario, all functions are available inall clients of the physical system; only Customizing settings decide on the roleallocation.

The software packages for SAP ERP and SAP GTS are often installed on separateSAP NetWeaver platforms, usually on different machines. Again, two clients playthe roles of SAP ERP feeder system and SAP GTS system, respectively.

Figure 2: System Architecture: Scenario 2

Scenario 2 with its physical separation of feeder system and SAP GTS is oftenfavored over scenario 1 because of performance reasons. This argument isespecially relevant to customers who intend to implement the services of SAPCompliance Management.

The feeder system and the SAP GTS system exchange data directly by meansof Remote Function Calls (RFC). An RFC calls up a function module in anSAP system from within another system. RFCs allows you to set up connectionsbetween different SAP systems or between an SAP system and a third-partysystem.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 3: Data Exchange Between SAP ERP and SAP GTS

Before this can happen, you have to assign a logical system name for bothsystems. This name must be unique in the system landscape. In the next step,RFC destinations containing all data needed to locate and to log on to the partnersystem have to be defined (see lesson Configuration of the System Connection)..

Plug-in for SAP GTSFor feeder systems with release levels SAP R/3 4.0B up to and including 4.7 andSAP ERP 5.0 to be connected with SAP GTS 3.0, SAP GTS 7.0 or SAP GTS7.1, the plug-in PI_2004_1 is required in the relevant release-dependent version.This plug-in allows you to use SAP GTS functions in the feeder system, such asthe transfer of documents and master data to SAP GTS for customs processingor foreign trade law audits. In SAP ERP 6.0, the plug-in functions are part ofthe component SAP_APPL.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: System Architecture

Figure 4: Overview of Plug-in Versions for SAP GTS

As of SAP GTS 7.2, the new plug-in SLL_PI 720 is available in release-specificversions for SAP R/3 4.6C and SAP R/3 4.7 as well as for SAP ERP 5.0 andSAP ERP 6.0. It is independent of the plug-in PI_2004_1 and the componentSAP_APPL and is downward as well as upward compatible with lower SAPGTS releases. As the new plug-in contains only SAP GTS related functions anddoes not affect other SAP solutions or components, it makes SAP GTS upgradesconsiderably easier.

Note: See SAP Note 858706 for additional information about the plug-in.You can find out in this note which version of the plug-in is requiredfor which feeder system release and SAP GTS release. Regarding theinstallation of plug-in SLL_PI 720, see SAP note 1104470.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Describe how SAP ERP and SAP GTS communicate


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: Configuration of the System Connection

Lesson: Configuration of the System Connection

Lesson OverviewThis lesson covers the settings needed to connect an SAP ERP ton an SAP GTSsystem.


Make all necessary Customizing settings to connect SAP ERP to SAP GTS


Settings in SAP ERPTo set up communication between the SAP ERP feeder system and SAP GTS onthe side of the feeder system, use the area menu for SAP GTS in SAP ERP. Calltransaction /SAPSLL/MENU_LEGALR3 and select the Basic Settings tab page.

Figure 5: Area Menu for SAP GTS in SAP ERP

Once you have determined which parts of the enterprise should use SAP GTS,define logical system names for every client acting as either an SAP ERP feedersystem or as an SAP GTS system (if this has not already been done earlier forother solutions using RFC). The logical system name uniquely identifies the clientof an SAP system or non-SAP system in the system landscape.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 6: Define and Assign Logical Systems

If you do not want to work with the SAP GTS area menu in the feeder system youcan define logical system names in Customizing for SAP NetWeaver. In the SAPReference IMG, choose SAP NetWeaver Application Server IDoc Interface /Application Link Enabling (ALE) Basic Settings Logical Systems DefineLogical System. You can also call the table of logical system names directly,using transaction code BD54.

If the name refers to a client, assign the name to the client. You can find the tablefor the assignment of logical system names either the in the SAP GTS area menuin the feeder system or in the IMG, via SAP NetWeaver Application ServerIDoc Interface / Application Link Enabling (ALE) Basic Settings LogicalSystems Assign Logical System to Client. You can also call this table directlyby using transaction code SCC4.

Hint: Both tables are cross-client.

To guarantee that the logical system name is unique and to simplify the assignment,SAP recommends using the naming convention CLNT. However, in certain cases, it could be useful not to use the recommendedconvention. The training clients for this course have descriptive names: Thelogical system name for the SAP ERP feeder system is FEEDER, the SAP GTSsystem is called SAPGTS.

In the next step, RFC destinations containing all data needed to locate and to logon to the partner system have to be defined.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 7: Define RFC Destination

To create new RFC destinations or to change existing ones, call transaction SM59(Configuration of RFC Connections) or choose Maintain RFC Destinations forRFC Calls in the Basic Settings tab page of the SAP GTS area menu in thefeeder system. You can also define RFC destinations in Customizing for SAPNetWeaver. In the SAP Reference IMG, choose SAP NetWeaver ApplicationServer IDoc Interface / Application Link Enabling (ALE) Communication Create RFC Connections.

In the RFC destinations, specify a target host, IP address, and (if applicable) thesystem number and user and logon data for remote logon in the target system. TheRFC destination contains all the technical information that the calling systemneeds to call the partner from within the network.

Hint: If the clients acting as SAP ERP feeder and as SAP GTS belong tothe same physical system, you do not need to maintain a target host.

For SAP GTS, you do not need to give the RFC destination the same name as thelogical target system. However, for Application Link Enabling (ALE) scenariosfor which you might want to use the RFC destination, too, it is advantageous todo so because you can have the system carry out certain settings automatically ata later time.

Although SAP GTS is not based on ALE, it uses the ALE distribution modelto enable the SAP ERP feeder system to identify its SAP GTS partner system.Whenever a user in the SAP ERP feeder system carries out a transaction involvinga call of SAP GTS functions (for example, creating a sales order that is to bechecked by the services of SAP Compliance Management), the applicationprogram determines the receiver of the call by querying the distribution model.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 8: ALE Distribution Model View

In the training system landscape, the sales order is created in the SAP ERPfeeder system FEEDER. To transfer its data to the SAP GTS system, theapplication program in FEEDER checks the local distribution model, identifiesSAPGTS as the receiver, and searches for a suitable RFC destination. Thusthe only purpose of the Business Application Programming Interface (BAPI)CustomsDocumentIF.SynchronizelfR3 is to use the distribution model fordetermination of the RFC receiver.

To maintain a distribution model view for communication with SAP GTS, chooseMaintain ALE Distribution Model in the SAP GTS menu, tab page Basic Settings,or call transaction BD64. Alternatively, choose SAP NetWeaver ApplicationServer IDoc Interface / Application Link Enabling (ALE) Modelling andImplementing Business Processes Maintain Distribution Model and DistributeViews.

When the logical system name of the SAP GTS system to which the data is to betransferred is known, the application program of the calling SAP ERP feedersystem determines the RFC destination for the SAP GTS system from a tablecontaining RFC destinations for synchronous method calls.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 9: Assign RFC Destination for Synchronous Method Calls

You can find this table by calling the transaction BD97. In the IMG, choose SAPNetWeaver Application Server IDoc Interface / Application Link Enabling(ALE) Communication Determine RFC Destinations for Method Calls. Youcan also call the transaction from the SAP GTS area menu in SAP ERP, tab pageBasic Settings (Maintain RFC Destinations for Method Calls).

Settings in SAP GTSIf the client acting as SAP GTS system is located in another physical system, theinitial steps for the setup of the system communication have to be repeated in thatsystem. You need to define the logical system names for SAP ERP feeder systemand SAP GTS system and assign the latter to its client.

In addition to these general settings, you need to define a so-called group oflogical systems. This group comprises feeder systems with similar properties, forexample, identical material or partner data. Such a system group is also requiredto connect only one feeder system to the SAP GTS system.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 10: Logical Systems and System Groups

If you assign several feeder systems to a system group, you need to transfer amaterial or a partner master record only from one of these feeder systems. Themaster record in SAP GTS will always be created on the system group level, forexample, one product master per system group.

You can define system groups in Customizing. Choose SAP Global Trade Services System Communication Define Group of Logical Systems. In the next step,assign the logical system name(s) of the SAP ERP feeder system(s) to groups bychoosing SAP Global Trade Services System Communication Assign LogicalSystem to a Group of Logical Systems.

To enable communication with the SAP ERP feeder system, you need to createan RFC destination for that system containing information on target host, systemnumber (if applicable), and logon details (transaction SM59). You can find therelevant transaction in the SAP GTS menu in the SAP GTS system (transaction/SAPSLL/MENU_LEGAL). In the System Administration area, choose SystemCommunication/Workflow and, in the next screen, choose Maintain Target Systemfor RFC Calls.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 11: RFC Destinations

In the next step, assign the RFC destination to the logical system name of theSAP ERP feeder system. Again, you can call the relevant table using transactionBD97. You can find this transaction in the SAP GTS menu, too. In the SystemAdministration area, choose System Communication/Workflow and, in the nextscreen, choose Maintain RFC Destinations.

Figure 12: Assign RFC Destination for Synchronous Method Calls

If you see a folder symbol to the left of the logical system name of the targetsystem, then an RFC destination is already assigned. If not, select the systemname and choose the button Standard BAPI destination. Enter the appropriateRFC destination in the RFC destination for BAPI calls field, confirm your entrywith Enter and save your changes.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Make all necessary Customizing settings to connect SAP ERP to SAP GTS


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Unit Summary

Unit SummaryYou should now be able to: Describe how SAP ERP and SAP GTS communicate Make all necessary Customizing settings to connect SAP ERP to SAP GTS


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit Summary GTS200


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 2Basic Mapping Settings

Unit OverviewIn this unit you will learn about general mapping settings in SAP ERP and SAPGTS. These settings are needed irrespective of your choice of SAP GTS services.


Explain the use of change pointers in master data distribution and set themup in the system

Set up the transfer of documents to SAP GTS Customize settings needed to map documents transferred from SAP ERP

Unit ContentsLesson: Mapping Settings in SAP ERP.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Exercise 1: Mapping of Document Types - Feeder System ... . . . . . . . . 23Lesson: Mapping Settings in SAP GTS.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Exercise 2: Mapping of Document Types - SAP GTS system.... . . . . . 33


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 2: Basic Mapping Settings GTS200

Lesson: Mapping Settings in SAP ERP

Lesson OverviewIn the SAP ERP feeder system, you need to maintain settings for the transfer ofmaster data and documents to SAP GTS. This lesson explains these settings.


Explain the use of change pointers in master data distribution and set themup in the system

Set up the transfer of documents to SAP GTS


Master Data Transfer Using Change PointersTo be able to use SAP GTS in your foreign trade processes, you need to forwardall relevant business partner records and material master records from your SAPERP feeder system to the SAP GTS system. As your users may create or changemaster data at any time, you need to ensure that any changes relevant to SAPGTS are promptly transferred. Although the SAP ERP system does not generateIntermediate Documents (IDocs) for data distribution to SAP GTS, certain settingsfrom the IDoc Interface can be used for regular master data transfer: messagetypes and change pointers.

Many application programs create change documents for each change madeto their objects (master data and documents). These change documents recordchanges to the application objects and usually specify the person who made thechange and the time of the change. These change documents can be used in ALEand EDI scenarios but can also be used for SAP GTS to set what are known aschange pointers, which allow the sending system to select all changed data recordsand send only these to the target systems.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: Mapping Settings in SAP ERP

Figure 13: Change Pointers

You can specify in Customizing whether a message type works with the changepointer function. Message types are keys that indicate data that can be exchangedbetween systems in ALE or EDI scenarios, for example, MATMAS for materialmasters, CREMAS for vendor masters, and DEBMAS for customer masters.They are linked to IDoc basic types defining the formatting structure of the datarecords that are to be sent. The change pointer creates a connection betweenchange documents and the corresponding message type, for example the changedocument for the creation or change of a material master and the message typeMATMAS. When it creates or changes a master record, the application programqueries whether the change pointer mechanism is activated or not. If the functionis active, a change pointer is saved to the database together with the applicationdocument and the change document.

You can evaluate change pointers by using program RBDMIDOC. This programis usually scheduled as a periodic background job but can also be executed directlyusing transaction code BD21. You can call this transaction from the ALE areamenu via Tools ALE ALE Administration Services Change Pointers Evaluate. In ALE and EDI scenarios, the program creates IDocs for newand changed master records. For data transfer from SAP ERP to SAP GTS, itgenerates RFCs instead.

Hint: Change pointers are stored in the data base of the SAP ERP system.You should delete processed and obsolete change pointers at regularintervals using program RBDCPCLR. You can execute this programfrom the ALE area menu via Tools ALE ALE AdministrationServices Change Pointers Reorganize (transaction code BD22).


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Some applications have such flexible programs for inbound and outboundprocessing that you can choose whether or not each optional segment field of therelevant IDoc basis type is to be transferred. To do this, you create what is knownas a reduced message type as a copy of a standard message type. Then you selectthe fields from the IDoc basis type linked to this message type whose content youwant to be transferred to a particular target system.

Figure 14: Reduced Message Types for Master Data Transfer

You can create, change and display reduced message types from the SAP GTSarea menu in the SAP ERP feeder system. Choose Activate Change Pointers forReduced Messages on the Basic Settings tab page, enter the reduced messagetype, and select Create , Change or Display . The menu path in SAPNetWeaver Customizing is SAP NetWeaver Application Server IDoc Interface/ Application Link Enabling (ALE) Modelling and Implementing BusinessProcesses Master Data Distribution Scope of Data for DistributionMessage Reduction Create Reduced Message Type (transaction code BD53).

When you create a new reduced message type, it is based on the most currentIDoc basis type. First the required segments are selected and then only the fieldsin these segments that are marked in a standard SAP system as required fields.These segments and fields are marked with a green background. Select a segmentby highlighting it and clicking on the Select button.

Note: When you select a segment, only fields that are defined in astandard SAP system as required fields will be selected.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


To select additional fields for a selected segment, navigate to the detail view.In the detail view, first select the additional fields, then click on Select again.Optional segments or fields that have not yet been selected are marked with ared background. Optional segments or fields that have already been selected arecolored white.

Caution: You have to click on the Select button before you can exit thedetail screen by selecting Enter. If you select fields and then click onEnter immediately, your selection is not saved.

If the change pointer function is used for a reduced message type, only changesmade to selected fields generate change pointers. You could thus create your ownreduced message type(s) containing only the fields whose content is transferredto SAP GTS in addition to the required fields of the IDoc basis type. Thus onlychanges relevant for SAP GTS result in a re-transfer of a material, a vendor, or acustomer master record from the SAP ERP feeder system.

Figure 15: Re-Transfer of Changed Master Data

By scheduling program RBDMIDOC as a periodic background job, you canensure that new master records as well as changes to existing ones are promptlyavailable in SAP GTS.

Note: In your SAP ERP feeder system, youwill find three reducedmessagetypes for master data transfer to SAP GTS (/SAPSLL/CREMAS_SLL,/SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SLL).


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Settings on Document Type LevelBefore you can use SAP GTS functions, the logistics documents that are createdin the SAP ERP feeder system needed for an import or an export process (forexample, purchase orders, orders, and billing documents) require counterparts inthe SAP GTS system.

Figure 16: Document Types: Settings (Example)

To ensure that relevant documents are replicated for all your processes, you haveto flag the corresponding document types as relevant to SAP GTS in the SAP ERPfeeder system. To do so, choose Sales and Distribution Foreign Trade/Customs SAP Global Trade Services - Plug-In Control Data for to Transfer SAPGlobal Trade Services Configure Control Settings for Document Transfer inthe IMG.

You will find three so-called application levels for each basic process: MM0A,MM0B, and MM0C for goods receipts; and SD0A, SD0B, and SD0C forgoods issues. Each application level groups together document types or goodsmovements according to their respective function in the process. For example,MM0A is the application level of purchase orders, and SD0C the application levelof billing documents.

The details of each application level indicate for which groups of services it can beused. For example, sales orders (application level SD0A) can be transferred toSAP GTS for the use of the services of SAP Compliance Management and SAPRisk Management; billing documents (application level SD0C) can be transferredfor the services of SAP Customs Management and SAP Risk Management.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 1: Mapping of Document Types -Feeder System

Exercise ObjectivesAfter completing this exercise, you will be able to: Link document types in the SAP ERP feeder system to document types in the

SAP GTS system to use SAP GTS functions in import and export processes.

Business ExampleSome goods receipt and goods issue processes in the model company are toundergo a foreign trade law audit.

Task:Make sure that all orders entered using sales document type ZA## in yourSAP ERP feeder system are transferred to the SAP GTS system for screeningin SAP Compliance Management and for preference calculation in SAP RiskManagement.

1. In Customizing, assign sales document type ZA## to application level SD0A(Dispatch / Export: Sales Document).

2. Flag the document type as being relevant to SAP Compliance Managementand SAP Customs Management. The system should display a message if adocument is blocked. You also want SAP GTS to set a preference indicatorin sales documents of document type ZA##, where applicable.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 1: Mapping of Document Types -Feeder SystemTask:Make sure that all orders entered using sales document type ZA## in yourSAP ERP feeder system are transferred to the SAP GTS system for screeningin SAP Compliance Management and for preference calculation in SAP RiskManagement.

1. In Customizing, assign sales document type ZA## to application level SD0A(Dispatch / Export: Sales Document).

a) In the IMG, choose Sales and Distribution Foreign Trade/Customs SAP Global Trade Services - Plug-In Control Data for Transferto SAP Global Trade Services Configure Control Settings forDocument Transfer.

b) Select the application level SD0A (Dispatch/Export: Sales Document)and double-click Document Types in the dialog structure.

c) Choose New Entries and enter document type ZA## in the DT fr.Backend Syst. field.

2. Flag the document type as being relevant to SAP Compliance Managementand SAP Customs Management. The system should display a message if adocument is blocked. You also want SAP GTS to set a preference indicatorin sales documents of document type ZA##, where applicable.

a) Set the indicators for Call Up SAP Compliance Management Services,Call Up SAP Risk Management Services, Output Dialog in SAP GlobalTrade Services and Set Preference Indicator in Feeder System.

b) To create the new entry, choose Save and exit the table.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Explain the use of change pointers in master data distribution and set them

up in the system Set up the transfer of documents to SAP GTS


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson: Mapping Settings in SAP GTS

Lesson OverviewIn the SAP GTS system, you need to maintain settings for the mapping ofdocuments transferred from the SAP ERP feeder system. This lesson deals withthese settings.


Customize settings needed to map documents transferred from SAP ERP


Document Types and Item CategoriesIn Customizing for SAP GTS, you define document types as correspondingdocuments for the document types flagged in the SAP ERP feeder system (a setof model document types is supplied by SAP in client 000). You then need toassign these SAP-GTS-specific document types to the corresponding feedersystem document types.

Figure 17: Assign Document Types


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: Mapping Settings in SAP GTS

SAP Compliance Management and SAP Customs Management each have tohave their own sets of document types defined for them. SAP Risk Managementuses the document types from the other two subsolutions (menu path inthe IMG: SAP Global Trade Services SAP Compliance ManagementGeneral Settings Document Structure Define Document Types and SAPGlobal Trade Services SAP Customs Management General Settings Document Structure Define Document Types respectively). The SAPGTS-specific document type is assigned the control parameters that are essentialfor foreign trade processes (for example, number range keys, text determinationprocedures, and action profiles for communication with the authorities).To assign document types from the feeder system to their equivalents in SAPGTS, choose SAP Global Trade Services SAP Compliance ManagementGeneral Settings Document Structure Assignment of Document Types fromFeeder Systems and SAP Global Trade Services SAP Customs ManagementGeneral Settings Document Structure Assignment of Document Types fromFeeder Systems respectively.

For some of the application levels, the same procedure is also necessary at itemcategory level. First, you have to define SAP-GTS-specific item categories. Youthen assign these to the corresponding item categories from the SAP ERP feedersystem. In SAP GTS, you usually need a smaller selection of item categories thanthose available in the feeder system.

Figure 18: Assign Item Categories

If there is no SAP GTS-specific item category for the item category transferredfrom the SAP ERP feeder system, the SAP GTS system creates the document forthe feeder system document without the corresponding item data. The documentin SAP GTS has the status Technical Mapping Incomplete but is not blocked.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


The user in the feeder system receives a message (Item Type Mapping notMaintained). To avoid this, opt for the function Automatically Transfer ItemCategory when maintaining the table for the assignment of item categories fromthe feeder system. Enter the logical system of the feeder system (or the systemgroup, if there are several similar feeder systems), the application level, andthe SAP-GTS-specific item category you want to use to summarize the itemcategories of the feeder system. The SAP GTS system will then retrieve all itemcategories from the feeder system and automatically assign the default SAPGTS-specific item category.

Organizational UnitsIn SAP GTS, you map your own company using the organizational units foreigntrade organization and legal unit. These organizational units represent yourcompany in regard to customs and foreign trade law. They are required to enableyou to transfer documents from the SAP ERP system and to determine the legalregulation on which the functions of the services to be used are based.

Figure 19: Organizational Units

You define foreign trade organization and legal units as SAP business partnersin SAP GTS (transaction code BP). It is imperative that you assign the correctbusiness partner roles of Foreign Trade Organization (SLLFTO) and Legal Unit(SLLSIT), respectively. For the preference processing service in SAP RiskManagement, there is the additional business partner role, Administrative UnitVendor Declarations (SLLMGR).


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


The foreign trade organization is assigned to at least one company code in theSAP ERP feeder system. If the foreign trade organization represents more thanone company code to the authorities, you can also make multiple assignments.A company code, on the other hand, can be linked to only one foreign tradeorganization. Likewise, a legal unit can be assigned to multiple plants, but a plantcan be linked to only one legal unit. A foreign trade organization and legal unit(s)are linked to each other in Customizing for SAP GTS (SAP Global Trade Services General Settings Organizational Structure Assign Legal Unit to theForeign Trade Organization).

Note: If you want to use the Preference Processing service in SAPRisk Management, SAP recommends that you assign a legal unit in yourSAP GTS system to each plant of your SAP ERP feeder system (seeSAP Note 891338).

The two organizational units are required to enable you to transfer documents fromthe feeder system, among other things. If a foreign trade organization or legal unitor both cannot be identified in SAP GTS when you are attempting to transfer adocument, you can create the document or save your changes in the feeder system.However, the document will either not be replicated at all (services of SAPCustoms Management) or replicated incompletely (services of SAP ComplianceManagement and SAP Risk Management). You will find incomplete replicatesin SAP GTS calling transaction Display Technically Incomplete Documents(transaction codes /SAPSLL/CUHD_IC_EXP and /SAPSLL/CUHD_C_IMPrespectively).

Partner Functions and Partner GroupingsYou must define all the partner roles in the SAP ERP feeder system that arerelevant for SAP GTS as partner functions in SAP GTS. When creating a partnerfunction, you have to specify whether this function is to be used for goods receipts,goods issues, or both.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 20: Partner Functions

In the Customizing of the SAP GTS system, choose SAP Global Trade Services General Settings Partner Structure Define Partner Functions (the keysof the delivered partner functions correspond in part to the German partner roles inSAP ERP). Then choose Assignment of Partner Roles from Feeder SystemsAssign Partner Function at Feeder System Level Manually Assign PartnerFunction. In this table, the SAP ERP feeder system partner roles are linked to theSAP GTS-specific partner functions.

To ensure that all partner roles used in inbound and outbound processes in theSAP ERP feeder system are known in the SAP GTS system, it is advisable tochoose Automatically Transfer Partner Function when maintaining the assignmenttable. Set the Excl. Partn. Role indicator for all partner roles that should not betransferred from the SAP ERP feeder system at the time of document replication.Not all partner functions in SAP GTS need to be linked to partner roles in the SAPERP feeder system. In client 000, you will find a few partner functions for thepurpose of customs processing that do not require an equivalent in the feedersystem, for example, customs offices.

You then assign the partner functions to partner groupings, which aresubsequently linked to individual services in SAP GTS. For example, if youintend to use the Embargo Check service, you define a partner grouping for eachdirection of goods movement (receipt/issue) and assign to it the partner functionsthat are linked to the SAP ERP feeder system partner roles. In this way, the systemrecognizes whether it has to screen the country of the immediate ship-to-partyonly, or also the country of the ultimate consignee.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Figure 21: Groups of Partner Functions

In Customizing, choose SAP Global Trade Services General SettingsPartner Structure Define Groups of Partner Functions. The system displaysa list of preconfigured partner groupings for each of the SAP GTS services. Forexample, select the grouping PGEMB2 (Partner Group for 'Embargo' Service -Export), and in the dialog structure, choose Assign Partner Function.

To activate partner groupings for the Embargo Check service, choose SAPGlobal Trade Services SAP Compliance Management Embargo CheckService Control Settings for Embargo Check Service. Assign the two partnergroupings PGEMB1 and PGEMB2 for the Embargo Check service to the legalregulation you defined for that service. Other services use similar tables for theassignment of partner groupings.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly



Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 2: Mapping of Document Types -SAP GTS system

Exercise ObjectivesAfter completing this exercise, you will be able to: Link document types in the SAP ERP feeder system to document types in the

SAP GTS system to use SAP GTS functions in import and export processes.

Business ExampleSome goods receipt and goods issue processes in the model company are toundergo a foreign trade law audit.

Task:In the SAP GTS system, assign the feeder system document type to the appropriatedocument type for SAP Compliance Management.

1. In Customizing for SAP Compliance Management, there already is adocument type to which you can assign sales document types. Make a noteof the document type key.

___________

2. In Customizing for SAP Compliance Management, assign feeder systemdocument type ZA## to the appropriate SAP GTS-specific document type.SAP GTS uses the same application levels as those used in the feeder system(in this case, SD0A).


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 2: Mapping of Document Types -SAP GTS systemTask:In the SAP GTS system, assign the feeder system document type to the appropriatedocument type for SAP Compliance Management.

1. In Customizing for SAP Compliance Management, there already is adocument type to which you can assign sales document types. Make a noteof the document type key.

___________

a) Choose SAP Global Trade Services SAP Compliance Management General Settings Document Structure Define Document Types.

b) The appropriate document type is the one with the key EXPORD(Export document - sales order level).

2. In Customizing for SAP Compliance Management, assign feeder systemdocument type ZA## to the appropriate SAP GTS-specific document type.SAP GTS uses the same application levels as those used in the feeder system(in this case, SD0A).

a) Choose SAP Global Trade Services SAP Compliance Management General Settings Document Structure Assignment ofDocument Types from Feeder Systems Assign Document Type atFeeder System Level.

b) Choose Manually Assign Document Type and then New Entries.

c) In the Application Level field, choose the key SD0A (Dispatch/Export:Sales Document).

d) Enter the logical system name FEEDER and the feeder systemdocument type ZA##. Add an explanatory text for this document type.

e) Then assign the customs document type EXPORD to these data. Tocreate the new entry, choose Save and exit the table.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Customize settings needed to map documents transferred from SAP ERP


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit Summary GTS200

Unit SummaryYou should now be able to: Explain the use of change pointers in master data distribution and set them

up in the system Set up the transfer of documents to SAP GTS Customize settings needed to map documents transferred from SAP ERP


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 3Definition and Use of Legal

Regulations

Unit OverviewIn this unit, you will learn how to map the laws and regulations relevant to yourforeign trade processes in general form as legal regulations in SAP GTS.


Define legal regulations for SAP GTS services Make all cross-service settings for the use of a legal regulation

Unit ContentsLesson: Definition and Use of Legal Regulations ... . . . . . . . . . . . . . . . . . . . . . . . . 38

Exercise 3: Define and Activate a Legal Regulation.. . . . . . . . . . . . . . . . . . . 43


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit 3: Definition and Use of Legal Regulations GTS200

Lesson: Definition and Use of Legal Regulations

Lesson OverviewThis lesson explains how to define a legal regulation. It covers the settings youwill need to make irrespective of the service(s) you want to use in SAP GTS.


Define legal regulations for SAP GTS services Make all cross-service settings for the use of a legal regulation

Business ExampleIDES AG wants to check which laws and regulations are relevant to its foreigntrade processes.

Definition of legal regulationsIn the SAP GTS system, you have to map all the laws and regulations that youmust comply with for export and import control or for customs processing aslegal regulations and activate them for the country or group of countries in whichthey apply.

You need to define separate legal regulations for each of the SAP GTS servicesyou intend to implement. In Customizing, choose SAP Global Trade ServicesGeneral Settings Legal Regulations Define Legal Regulation.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Lesson: Definition and Use of Legal Regulations

Figure 22: Define Legal Regulations

Flag each legal regulation with a two-character, numerical code that specifies itspurpose. The assignment of a legal regulation to a so-called legal code determineshow the legal regulation is used in SAP GTS:

00 (Foreign Trade Laws): SAP Compliance Management services 01 (Customs Processing): Customs Processing service (SAP Customs

Management) 03 (Prohibitions and Restrictions): SAP Compliance Management services 06 (Preference Law): Preference Processing service (SAP Risk

Management) 07 (Transit Process: Import/Export): Transit Procedure service (SAP

Customs Management) 08 (Restitution): Restitution service (SAP Risk Management) 09 (Letter of Credit Processing): Letter of Credit Processing service (SAP

Risk Management) 10 (External Application): Intrastat declarations (SAP Electronic

Compliance Reporting)

Assign appropriate so-called deadline types to the legal regulation. In most cases,these will be VALFRO (Valid-from date) and VALTO (Valid-to date) for thecheck of the validity of licenses, authorizations, securities and Sanctioned PartyList entries. All deadline types you can choose from using the input help forthe field Type of Date are predefined.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Determination of legal regulationsAs of SAP GTS 7.0, the determination of legal regulations in a process is moredifferentiated than in earlier releases. A legal regulation can now be determinedbased on either a country, or a country group, or a combination of both. This newfeature facilitates the mapping of legal regulations, especially for EC memberstates. SAP supplies six corresponding determination strategies (ALRG01 toALRG03 for individual countries and ALRG11 to ALRG13 for country groups).These determination strategies are to be assigned to one or more service-specificdetermination procedure(s), for example LELDT for the Legal Control service.You can assign several determination strategies to one determination group. Thesystem will use them in the process in the order of their sequence numbers. Ifan attempt to determine a legal regulation for a service is successful the systemwill stop searching.

Figure 23: Determination Procedures and Determination Strategies

Country groups can be used in cases where the same legal requirements applyto a number of different countries. Such legal situation might exist becauseof supranational law (such as in the EC) or because of treaties (for example,preference agreements). You define country groups in Customizing (SAP GlobalTrade Services General Settings Legal Regulations Define CountryGroup). As of SAP GTS 7.2, the assignment of countries to country groups is alsoperformed in Customizing (SAP Global Trade Services General SettingsLegal Regulations Assign Countries to Country Group). In releases up to andincluding SAP GTS 7.1, you will find this assignment in the application menu(transaction code /SAPSLL/CTYGPA).

For the services of SAP Compliance Management and SAP RiskManagement, SAP GTS determines the legal regulation to be appliedin a particular process based on the country in the address data of the


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


SAP business partner of the legal unit that imports or exports the goods.In SAP Customs Management, you cannot make use of country groups orcombinations of countries for the purpose of legal regulation determination.The country in the address data of the SAP business partner of the foreign tradeorganization importing or exporting the goods decides the legal regulation tobe applied in the individual process.

Activation of legal regulationsActivate each legal regulation for general use for at least one country or countrygroup. For example, the Export Administration Regulations are effective in theU.S. You thus activate the corresponding legal regulation in SAP GTS for the U.S.

Figure 24: Activate Legal Regulations: General Level

To activate a legal regulation for general use, choose SAP Global Trade Services General Settings Legal Regulations Activate Legal Regulations atCountry/Country Group Level in Customizing. Select the legal regulation anddouble-click the appropriate folder in the dialog structure. Then choose NewEntries and enter the country or country group of your choice.

If you make use of determination strategies that are based on combinations ofcountries or country groups, you need to make two entries in the activation table.For example, you could maintain two legal regulations meant for exports from theEC. The first should only be taken into account if the country of destination is theU.S., and the second only if the country of destination is Libya. You thus activatethe first legal regulation for the country group EC and the country of destinationUS. The second legal regulation you activate for the country group EC and the


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


country of destination LY. In both cases, first enter the country group EC. Thenselect this entry, double-click the folder Country Group/Country and choose NewEntries to add the appropriate country of destination.

After activating a legal regulation for general use, you need to activate itspecifically for an SAP GTS service. In the example above, the legal regulationEC embargo regulation has been defined for the Embargo Check service andhas been generally activated for the country group EC. In the next step, choose SAPGlobal Trade Services SAP Compliance Management Embargo CheckService Activate Legal Regulations. As the service should only check importsinto and exports from the EC, the legal regulation is activated with the indicatorsCheck: Import (Exclusively) and Check: Export (Exclusively) respectively.

Figure 25: Activate Legal Regulations: Service Level

In SAP Customs Management, activation depends on whether the functions of theservice are to be used in goods receipt as well as in goods issue processes. In SAPCompliance Management and SAP Risk Management, you always need to decidewhether the service is to check all processes, or only cross-border trade, andwhether intra-community movements of goods are included in the checks or not.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Exercise 3: Define and Activate a LegalRegulation

Exercise ObjectivesAfter completing this exercise, you will be able to: Map the laws and regulations that have to be complied with in foreign trade

as legal regulations in the SAP GTS system.

Business ExampleYour IDES subsidiaries import and export goods on a daily basis. The maincustoms and foreign trade law regulations must be entered as legal regulations inthe SAP GTS system.

Task:In the SAP GTS system, create a new legal regulation for foreign trade law checksand activate this regulation for use in a combination of countries.

1. In Customizing for the SAP GTS system, create a legal regulation with thekey GTS## and a description of your choice. You can use the existing tableentry for the German Foreign Trade and Payments Act (AWG) as a reference.

2. Assign appropriate deadline types to the legal regulation. Make sure thatthe system checks the validity of export licenses based on your new legalregulation. The deadline types VALFRO (Valid-from date) and VALTO(Valid-to date) are provided for this purpose. Assign these two deadlinetypes to your legal regulation, GTS##.

3. Activate the legal regulation for general use. The regulation will be usedfor exports from Germany to the country provided for your group (see listbelow).

Group Country01 Argentina (AR)02 Brazil (BR)03 Costa Rica (CR)04 Chile (CL)05 China (CN)06 Algeria (DZ)07 Ecuador (EC)

Continued on next page


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Group Country08 Egypt (EG)09 Indonesia (ID)10 Israel (IL)11 Iran (IR)12 Jordan (JO)13 Kuwait (KW)14 Sri Lanka (LK)

15 Morocco (MA)16 Mexiko (MX)17 Namibia (NA)18 Singapore (SG)19 Turkey (TR)20 India (IN)

4. Activate your legal regulation GTS## for the Legal Control service. Theservice should check exports only.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Solution 3: Define and Activate a LegalRegulationTask:In the SAP GTS system, create a new legal regulation for foreign trade law checksand activate this regulation for use in a combination of countries.

1. In Customizing for the SAP GTS system, create a legal regulation with thekey GTS## and a description of your choice. You can use the existing tableentry for the German Foreign Trade and Payments Act (AWG) as a reference.

a) Choose SAP Global Trade Services General Settings LegalRegulations Define Legal Regulation.

b) Choose New Entries. Enter the key for the new legal regulation,GTS##, and add a description of your choice.

c) Assign the new legal regulation to legal code 00 (Foreign Trade Laws).In the Import/Export field, choose key 2 Export/Dispatch. ChooseSave to create the legal regulation.

2. Assign appropriate deadline types to the legal regulation. Make sure thatthe system checks the validity of export licenses based on your new legalregulation. The deadline types VALFRO (Valid-from date) and VALTO(Valid-to date) are provided for this purpose. Assign these two deadlinetypes to your legal regulation, GTS##.

a) Select the table entry you created in the last step, double-click AssignDeadline Types in the dialog structure, and choose New Entries.

b) You can now assign the VALFRO key using input help for the Type ofDate field. Repeat this step for VALTO and save your changes.

3. Activate the legal regulation for general use. The regulation will be usedfor exports from Germany to the country provided for your group (see listbelow).

Group Country01 Argentina (AR)02 Brazil (BR)03 Costa Rica (CR)04 Chile (CL)05 China (CN)06 Algeria (DZ)

Continued on next page


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Group Country07 Ecuador (EC)08 Egypt (EG)09 Indonesia (ID)10 Israel (IL)11 Iran (IR)12 Jordan (JO)13 Kuwait (KW)14 Sri Lanka (LK)

15 Morocco (MA)16 Mexiko (MX)17 Namibia (NA)18 Singapore (SG)19 Turkey (TR)20 India (IN)

a) Choose SAP Global Trade Services General Settings LegalRegulations Activate Legal Regulations at Country/Country GroupLevel.

b) Select the table entry for GTS##, double-click Country in the dialogstructure, then choose New Entries and enter DE in the Country field.

c) Select the new entry, double-click Country/Country in the dialogstructure, and then choose New Entries again. Enter the country codefor your group according to the list above in the Partn. Ctry field.Save the new entry.

4. Activate your legal regulation GTS## for the Legal Control service. Theservice should check exports only.

a) Choose SAP Global Trade Services SAP Compliance Management Legal Control Service Activate Legal Regulations.

b) Select the entry for legal regulation GTS## from the last step anddouble-click Country in the dialog structure.

c) Select the entry for country DE and double-click Country/Country inthe dialog structure.

d) In the LegCtrExp. field, select the indicator 2 Check: Export(Exclusively) for your group-specific partner country. Save the change.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly


Lesson Summary

You should now be able to: Define legal regulations for SAP GTS services Make all cross-service settings for the use of a legal regulation


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Unit Summary GTS200

Unit SummaryYou should now be able to: Define legal regulations for SAP GTS services Make all cross-service settings for the use of a legal regulation


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

GTS200 Course Summary

Course SummaryYou should now be able to:

Set up communication between SAP R/3 or SAP ERP and SAP GTS Make all necessary generic mapping settings


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Course Summary GTS200


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

IndexAApplication level, 22Application Link Enabling(ALE), 9

BBusiness partner role, 28CChange pointer, 18Country group, 40DDeadline type, 39Determination procedure, 40Determination strategy, 40Distribution model, 9Document type, 22, 26FFeeder system, 2Foreign trade organization,28, 40

IIDoc basis type, 19

Item category, 27LLegal code, 39Legal regulation, 38Legal unit, 28, 40Logical system, 7Logical system name, 7MMessage type, 19PPartner function, 29Partner grouping, 30Partner role, 29Plug-in, 4RRemote Function Call (RFC),3

RFC destination, 4, 8SSAP business partner, 28, 40


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Index GTS200


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

FeedbackSAP AG has made every effort in the preparation of this course to ensure theaccuracy and completeness of the materials. If you have any corrections orsuggestions for improvement, please record them in the appropriate place in thecourse evaluation.


Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

Fo

r

in

te

rn

al

u

se

b

y

CS

C

on

ly

sample.pdfsterling.comWelcome to Sterling Software

ACNA03_Instructor.pdftocIcons in Body Text1 3 Lesson:Document Parking - definedWhat kind of documents can you park?Entering and changing parked documentsDemonstration: Create a Parked Document8 Changing parked documentsPosting a parked documentDemonstration: Changing and posting a parked documentDeleting a parked documentDisplaying change documentsReporting on parked documentsDemonstration: Execute a report with parked documentsAuthorizations and Workflow13

25 Lesson:Demonstration: User-Specific MemoryDemonstration: Setting User ParametersDemonstration: Default Values in the SystemDemonstration: Create Screen Variant (Vendor Invoice)31

Lesson:Demonstration: Changing Posted DocumentsDemonstration: Displaying Document ChangesDemonstration: Document Change Rules for the Document HeaderDemonstration: Document Change Rules for the Line Items Demonstration: Canceling Changeability (for Line Items)39

Lesson:Demonstration: Show Terms of Payment in the Customer Master RecoDemonstration: Defining Terms of Payment in the Vendor Master ReDemonstration: Posting Vendor InvoicesDemonstration: Customer Invoice with Subsequent Credit MemoDemonstration: Defining Terms of PaymentDemonstration: Day Limits for Terms of Payment 0009Demonstration: Installment PaymentsDemonstration: Defining Terms for Installment PaymentsDemonstration: Terms of Payment for Each InstallmentDemonstration: Defining Cash Discount Base for Outgoing InvoicesDemonstration: Posting Customer Invoices Gross Demonstration: Defining Accounts for Cash Discount ExpenseDemonstration: Defining Accounts for Cash Discount Revenue Demonstration: Defining the Vendor Net Document TypeDemonstration: Defining Cash Discount Clearing AccountsDemonstration: Posting Vendor Invoices with Document Type KN Demonstration: Case 1: Payment within Cash Discount PeriodDemonstration: Case 2: Payment after Cash Discount Period (ManuaDemonstration: Defining the Cash Discount Loss Account 55

Lesson:Demonstration: Defining Tax Calculation ProceduresDemonstration: Defining Condition Types (Show if Necessary)Demonstration: Defining Tax Codes for Sales and PurchasesDemonstration: Assigning Tax Codes for Transactions That Are NotDemonstration: Providing Certain Tax Codes in the Input Help or Demonstration: Transaction Keys Demonstration: Defining Tax AccountsDemonstration: Defining Accounts for Exchange Rate DifferencesDemonstration: Changing Foreign Currency TranslationDemonstration: Defining Accounts for Exchange Rate Difference PoDemonstration: Posting with Acquisition Tax Code 81

Lesson:Demonstration: Configuring Prerequisites in CustomizingDemonstration: Defining Clearing Accounts for Cross-Company CodeDemonstration: Posting the Example in Figure 115Demonstration: Displaying Cross-Company Code Transactions97

109 Lesson:Demonstration: Posting an Incoming PaymentDemonstration: Account clearingDemonstration: Checking Clearing TransactionsDemonstration: Defining Accounts and Additional Criteria for AutDemonstration: Show the Sort Key Field in the Master Record117

Lesson:Demonstration: Posting an Incoming Payment - Payment HeaderDemonstration: Posting an Incoming Payment: Bank DataDemonstration: Posting an Incoming Payment - Open Item SelectionDemonstration: Check before PostingDemonstration: Clearing Transaction for Cross-Company Code TransDemonstration: Defining Cash Discount Expense (Customer) and CasDemonstration: Defining Cash Discount Clearing Accounts Demonstration: Defining the Cash Discount Loss Account Demonstration: Resetting ClearingDemonstration: Payment History Demonstration: Credit Limit135

Lesson:Demonstration: Defining Tolerances (Customers)Demonstration: Entering the Tolerance Group in the Customer MastDemonstration: Defining Tolerance Groups for EmployeesDemonstration: Assign Users/Tolerance Groups (Employees)Configuration of tolerance groupsDemonstration: Incoming Payments with Differences Demonstration: Account DeterminationDemonstration: Incoming Payments: Manual Cash Discount AdjustmenDemonstration: Partial PaymentDemonstration: Residual Payment for Partial PaymentDemonstration: Residual ItemsDemonstration: Writing Off DifferencesDemonstration: Defining Reason Codes Demonstration: Defining Accounts for Payment Differences 147

Lesson:Demonstration: Posting Exchange Rate DifferencesDemonstration: Defining Accounts for Realized Exchange Rate Diff155

159 Lesson:Lesson:Demonstration: Creating Periodic Account Statements169

183 Lesson:Lesson:Demonstration: Accessing Payment Program Configuration in the SyDemonstration: Settings in the Payment Program for All Company C199

Lesson:Payment Medium Workbench215

Lesson:231

Lesson:

247 Lesson:255

271 Lesson:275

Lesson:Demonstration: Entering a Dunning Procedure in the Master RecordDemonstration: Creating a Dunning ProcedureDemonstration: Dunning Procedure OverviewDemonstration: Dunning LevelsDemonstration: Expenses and ChargesDemonstration: Minimum AmountsDemonstration: Setting Up the Environment287

Lesson:Demonstration: Creating a Dunning Run: Run Date/Identification299

Lesson:Dunning Run315

Lesson:325

Lesson:Scheduling Printing335 337

351 Lesson:363

369 Lesson:Lesson:Interest Calculation ConfigurationDemonstration: Interest Calculation Types/IndicatorsDemonstration: Calculating Interest for Open Customer ItemsDemonstration: Further Configuration Settings379

387 Lesson:R/3 give you two tools to use when executing reports: variants 391

GTS200_EN_Col73_FV_Part_A4.pdftocIcons in Body TextConnecting SAP ERP to SAP GTSLesson:System Architecture and Data ExchangePlug-in for SAP GTS

Lesson:Settings in SAP ERPSettings in SAP GTS

Basic Mapping SettingsLesson:Master Data Transfer Using Change PointersSettings on Document Type LevelExercise 1: Mapping of Document Types - Feeder System

Lesson:Document Types and Item CategoriesOrganizational UnitsPartner Functions and Partner GroupingsExercise 2: Mapping of Document Types - SAP GTS system

Definition and Use of Legal RegulationsLesson:Definition of legal regulationsDetermination of legal regulationsActivation of legal regulationsExercise 3: Define and Activate a Legal Regulation

GTS200 - Configuration SAP Global Trade Services

Documents

Transcript of GTS200 - Configuration SAP Global Trade Services