H42 BB Config Guide GTS

(1)

SAP ECC 6.00

August 2006

English

H42: Configuration SAP

Global Trade Services

(GTS)

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf

Germany

(2)

Copyright

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 PowerPointare 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 MultiWinare 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

(3)

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.

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

(4)

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

(9)

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 Note

Billing type YHF8

(10)

Field name Description User action and values Note No.range int.assgt. 19 SD document categ. U Transaction group 8 Output determination procedure 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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code 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:

Block 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

(11)

Procedure

1. Access the activity using one of the following navigation options: Transaction Code 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 User action and values Note

Sales document type 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

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…:

Sales document type YTAN

Description 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.

(12)

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 User action and values Note

Sales document type YOR

Item category group NORM

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.

Procedure

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

(13)

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

Procedure

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

(14)

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:

Type 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.

Procedure

IMG Menu Customizing  Materials Management  Purchasing 

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

(15)

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.

Procedure

1. Access the activity using the following navigation options: Transaction Code 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:

Country LR

Transportation zone 0000000001

(16)

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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code 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.

(17)

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.

Procedure

1. Access the activity using the following navigation options: Transaction Code 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:

Application Level MM0A

MMOB MM0C SD0A SD0B SD0C

3. Select each Application Level and enter the following data for different levels: Field name Description User action and values Note

Aplication Level MM0A

DT for Backend Sys. FYNB

Call Up SAP Risk Management Services

X

Generate Worklist for Vendor-Based Vendor Declarations

X

(18)

DT for Backend Sys. EL

Call Up SAP Customs Management Services

X

Aplication Level MM0C

DT for Backend Sys. 101B

Call Up SAP Risk Management Services

X

Generate Worklist for Vendor-Based Vendor Declarations

X

Application level SDOA Dispatch/ Export:

Sales document

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 This is a separate

pro-forma invoice document type needed for Customs Management Call Up SAP Risk

Management Services

X

Set Preference Indicator in Feeder System

X

(19)

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.

Procedure

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 User action and values Note Activate Transfer of Sales

Documents (SD0A) Activate Transfer of Billing Documents (SD0C) Activate Transfer of Inbound Delivery (MM0B) Activate Transfer of Goods Movement (MM0C) Activate Transfer of Purchasing Orders (MM0A)

Choose Execute for these IMG activities.

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.

Procedure

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

(20)

2. In the Change View “Control Settings for BOM Transfer – Global”: Overview choose New

entries and enter the following data:

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

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

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

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.

Procedure

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

(21)

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.

Procedure

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

IMG Menu Customizing  Cross-Application Components  Predefined ALE

Business Processes  Logistics  Logistics <-> External Systems

 External Transportation Planning System  Define Logical Non-SAP Systems

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

Log.System Logical System RS5CLNT037 <System>CLNT<Client>

Name <Logical System GTS>

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.

(22)

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:

Address tab

Last name RFC User

Logon data tab

Initial password initial

Repeat password initial

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.

(23)

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.

Procedure

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.

Procedure

SAP Menu /N/SAPSLL/MENU_LEGALR3  Basic Settings  Maintain

ALE Distribution Model

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.

(24)

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

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

(25)

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

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:

Address tab

Last name RFC User

Logon data tab

Initial password initial

Repeat password initial

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.

Procedure

IMG in SAP GTS SAP Global Trade Services  System Communication 

(26)

System

 ...

2. Enter the name of the logical system using the standard naming convention: <system name>CLNT<client number>.

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.

Procedure

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

SAP GTS /N/SAPSLL/MENU_LEGAL  System Communication/Workflow

(27)

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.

(28)

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.

Procedure

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.

(29)

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 time-dependent 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.

Procedure

(30)

IMG in SAP GTS SAP Global Trade Services  General Settings  Maintain System Time Zone

 ...

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.

Procedure

1. Access the activity using the following navigation options: Transaction Code /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:

No Number range number 01

From number 0000000001

To number 9999999999

Ext External number range flag

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

No Number range number AB

From number A

To number ZZZZZZZZZZ

Ext 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.

(31)

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.

Procedure

1. Access the activity using the following navigation options: Transaction Code /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:

From number 00000000000000000001

To number 99999999999999999999

Ext External number range flag 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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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.

From number 00100000000000000000

To number 00199999999999999999

Ext External number range flag 3. Save your entries.

(32)

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.

Procedure

1. Access the activity using the following navigation options: Transaction Code /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:

Year Current year (e.g. 2006)

4. Choose Insert interval again.

(33)

4.2.2.5 Defining Number Ranges for Supplementary

Customs Declaration

Use

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

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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.

(34)

4.2.2.6 Defining Number Ranges for Internal Package

Numbers

Use

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

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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:

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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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

From number 00000000000000000001

To number 99999999999999999999

(35)

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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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:

Year Current year, for example 2005

From number 00000000000200500001

To number 00000000000200599999

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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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

(36)

From number 00000000001000000001

To number 00000000001000000999

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

02 00000000002000000001 00000000002000000999

03 00000000003000000001 00000000003000000999

04 40000000000000000000 49999999999999999999

4.2.3 Organizational Structure

4.2.3.1 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

(37)

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 remarks

BP Role SLLAUT

Title Government Agency

Description GTS: Government Agency

BP Role Cat. SLLAUT Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLAUT

4. Choose next entry.

BP Role SLLBNK

Title Bank for L/C

Description GTS: Bank for Documentary Payment

BP Role Cat. SLLBNK Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLBNK

BP Role SLLCOF

Title Customs Office

Description GTS: Customs Office

BP Role Cat. SLLCOF Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLCOF

BP Role SLLCPC

Title Customs Bus. Partner

Description GTS: Customs Business Partner (Cus.)

BP Role Cat. SLLCPC Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLCPC

(38)

Field Field Value remarks Title Customs BP (Vendor)

Description GTS: Customs Business Partner (Vendor)

BP Role Cat. SLLCPS Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLCPS

BP Role SLLDAP

Title Data Provider Description GTS: Data Provider

BP Role Cat. SLLDAP Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLDAP

BP Role SLLFTO

Title FT Organization

Description GTS: Foreign Trade Organization

BP Role Cat. SLLFTO Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLFTO

BP Role SLLMGR

Title Admin. Unit VD

Description GTS: Administr.Unit Vend.Decl.

BP Role Cat. SLLMGR Flag: Std Assignment BP Role -> BP Role Cat

BP View SLLMGR

BP Role SLLSIT

Title Legal Unit

(39)

BP Role Cat. SLLSIT Flag: Std Assignment BP Role -> BP Role Cat

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.

Procedure

1. Access the activity using one of the following navigation options: Transaction Code /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:

Business partner OBP01

Create in role SLLFTO Foreign trade

organization

Name Foreign trade organization

OBP01

Search term 1 BP01

Search term 2 SAP BEST PRACTICES

Country DE

3. Choose More fields.

Time Zone 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.

H42 BB Config Guide GTS

SAP ECC 6.00

August 2006

English

H42: Configuration SAP

Global Trade Services

(GTS)

Copyright

Icons

Typographic Conventions

Contents

H42: Configuration Global Trade Services (GTS)

1 Purpose

2 Preparation

2.1 Prerequisites

Building Blocks

2.1.1

Implementing SAP Notes

Use

Procedure

2.1.2

Adobe Document Services (ADS)

3 Configuration ERP system/client

3.1 SD Basic Settings in mySAP ERP

3.1.1

Defining Billing Document Type

Use

Procedure

3.1.2

Defining Blocking Reasons for Billing Document Type

Use

Procedure

3.1.3

Defining Sales Document Type

Use

Procedure

3.1.4

Defining Item Categories

Use

Procedure

3.1.5

Assigning Item Categories in SAP ERP

Use

3.1.6

Specifying Copy Control for Deliveries

Use

Procedure

3.1.7

Assign Schedule Lines

Procedure

3.2 MM Basic Settings in mySAP ERP

3.2.1

Defining Purchasing Document Type YNB

Use

Procedure

3.2.2

Assigning Partner Schemas to Document Types

Use

Procedure

3.2.3

Defining Transportation Zone for Customer in Liberia

Use

Procedure

3.3 Settings in GTS Plug In in mySAP ERP

3.3.1

Implementing User Exit

Use

Procedure

3.3.2

Configure Control Settings for Transfer

Use

Procedure

3.3.3

Activate BADIs for Transfer of Documents (ERP)

Use

Procedure

3.3.4

Preference: Control Settings for Bill of Materials

Transfer

Use