Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2021-12-22

Setting Up Customs Management with SAP Global

Trade Services (2U1)
© 2021 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 SAP Cloud Connector Installation and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

5 SAP S/4HANA Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5.1 Maintain Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
5.2 Create Communication Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3 Create Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

6 Communication Set-up in SAP GTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

6.1 Creating an RFC Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
6.2 Defining a Logical System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.3 Defining Group of Logical Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
6.4 Assigning a Logical System to a Group of Logical Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
6.5 Defining RFC Destinations for Method Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Setting Up Customs Management with SAP Global Trade Services (2U1)

2 PUBLIC Content
1 Purpose

 Tip

We recommend setting up this integration scenario using the Cloud Integration Automation Service (CIAS).
CIAS provides a guided workflow that features:

● Customer-specific system information (for example, target URLs)

● Reusable configuration settings between tasks
● Automated execution capabilities

With the included project management tool and complementary support information, CIAS helps reduce the
time you need for manual tasks. For more information, see the product page on the SAP Help Portal.

Navigate directly to the Maintenance Planner.

The purpose of this document is to enable the SAP S/4HANA Cloud customer to set up the integration with their
on-premise SAP Global Trade Services (GTS).

Setting Up Customs Management with SAP Global Trade Services (2U1)

Purpose PUBLIC 3
2 Prerequisites

It is mandatory that this particular scope item is active.

Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options to
check the status:

● Manage Your Solution:

In the SAP S/4HANA Cloud system, in the SAP Fiori launchpad, open the Manage Your Solution app and go to
View Solution Scope.
● SAP Central Business Configuration:
In the Scope and Organizational Structure phase, navigate to the Activities tab. Search for Define Scope and
choose Open.

If the scope item is not active, please request the activation via BCP – Ticket Component: XX-S4C-OPR-SRV.

Setting Up Customs Management with SAP Global Trade Services (2U1)

4 PUBLIC Prerequisites
3 Preparation

Before you start installing this scenario, please check if following prerequisites are prepared.

1. The kernel release of your SAP GTS system has to be on 749 or above.
2. Your SAP Cloud Connector is supposed to be integrated with Cloud Foundry Environment, hence the
component SAP_BASIS of your SAP GTS system has to be on 7.54 or a higher version. If your SAP Cloud
Connector is integrated with Neo Environment, the version of SAP_BASIS is not a must.
3. The administrator user who will access the SAP S/4HANA Fiori launchpad requires either the business role
SAP_BR_ADMINISTRATOR or the business role containing the business catalog SAP_CORE_BC_COM
(Communication Management).

Setting Up Customs Management with SAP Global Trade Services (2U1)

Preparation PUBLIC 5
4 SAP Cloud Connector Installation and
Configuration

Setting Up Integration with On-Premise Systems

For all scenarios integrating SAP S/4HANA Cloud with SAP On-Premise scenarios, the SAP_COM_0574 – SAP BTP
Connectivity Service - On Premise Integration communication arrangement must be activated. This is a prerequisite
for all other communication arrangements.

To check if the SAP_COM_0574 – SAP BTP Connectivity Service - On Premise Integration communication
arrangement is active in your system, go to the Communication Arrangements app. If it is not active, you must set it
up.

To set up the communication scenario, follow the procedure under Integrating On-Premise Systems.

 Note

SAP Cloud Connector is supposed to integrate with Cloud Foundry Environment. In the past, SAP Cloud
Connector was integrated with Neo Environment and the communication scenario SAP_COM_0200 – SAP
Cloud Connector Integration was required to be activated. Now this communication scenario is deprecated.

 Note

When configuring the access control list for the cloud to on-premise scenario, you must specify function
modules (resources) that can be invoked on the on-premise host. The SAP Cloud Connector uses very strict
whitelists for its access control.

 Note

Use /SAPSLL as function module name for the communication scenario SAP_COM_0084 (SAP S/4HANA Cloud
integration with SAP Global Trade Services). Also, add the function module ARFC_DEST_SHIP for
asynchronous call, which is relevant for the scope item 2U1 - Customs Management with SAP Global Trade
Services.

Setting Up Customs Management with SAP Global Trade Services (2U1)

6 PUBLIC SAP Cloud Connector Installation and Configuration
5 SAP S/4HANA Configuration

5.1 Maintain Communication User

Use

The communication user defined in the SAP S/4HANA system is used for inbound communication and message
processing in the system.

Prerequisite

To perform the following activity, a business user with a business role must exist. The business role must contain
the business catalog SAP_CORE_BC_COM (Communication Management). For example, the business role
SAP_BR_ADMINISTRATOR (Administrator) is required.

Procedure

1. Log onto the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open Maintain Communication Users.
3. Choose New to create a new user.
4. Make the following entries and choose Create:
User Name: <user name>, for example, GTS_INBOUND
Description: <description>, for example, GTS_INBOUND
Password: <password>
5. Make a note of user data. This is required when you create the communication arrangement.

Result

The communication user is created.

Setting Up Customs Management with SAP Global Trade Services (2U1)

SAP S/4HANA Configuration PUBLIC 7
5.2 Create Communication Systems

Use

A communication system is used to define the host name of the on-premise GTS system and to assign users for the
inbound (from GTS to SAP S/4HANA) and outbound communication (from SAP S/4HANA to GTS).

Procedure

1. In the upper left corner, choose Home.

2. Open Communication Systems.
3. On the Communication Systems screen, choose New.
4. Make the following entries and choose Create:
System ID: GTS_SAP
System Name: GTS_SAP
5. In the General Data area, keep the System ID and System Name unchanged.
6. In the Technical Data – General area, make the following entries:
Host Name: <virtual host name for SAP GTS system>
Use Cloud Connector: Selected

 Note

Leave the other fields in this section with their default values.

 Note

The virtual hostname maps to the physical hostname of the on-premise GTS system. It is created in the
SAP Cloud Connector access control list of the Cloud to on-premise.

7. In the Technical Data – Cloud Connector Settings area, make the following entries:
Instance Number: <instance number of your SAP GTS system>
Client: <client of your SAP GTS system>
8. In the User for Inbound Communication area, choose ＋.
9. On the New Inbound Communication User dialog box, make the following entries and choose OK:
User Name: <user name>, for example, GTS_INBOUND (from Maintain Communication User [page 7])
Authentication Method: User Name and Password
10. In the User for Outbound Communication area, choose ＋.
11. On the New Outbound User dialog box, make the following entries and choose Create:
Authentication Method: User Name and Password
User Name: <user name>
Password: <password>

Setting Up Customs Management with SAP Global Trade Services (2U1)

8 PUBLIC SAP S/4HANA Configuration
  Note

This user is used to log onto the on-premise GTS system. Ensure that the proper authorizations are
assigned.

12. Choose Save.

Result

The communication system is created.

5.3 Create Communication Arrangement

Use

The communication arrangement in the SAP S/4HANA system defines all relevant information for the
communication with the on-premise GTS system.

 Note

This note is relevant for the transfer of business partners with multiple addresses, which is only supported by
SAP Global Trade Services, edition for SAP HANA. If the multiple address handling functionality is not activated
in your SAP S/4HANA system, skip this note.

When you activate the multiple address handling functionality for business partner data in your SAP S/4HANA
Cloud system, and your SAP GTS system is SAP Global Trade Services, edition for SAP HANA, you need to
additionally create the communication arrangement for the communication scenario SAP_COM_0008 –
Business Partner, Customer and Supplier Integration. You can refer to the chapter Configuration for Business
Partner Data Integration from S/4HANA Cloud to SAP On-Premise Systems via SOAP Services in the set-up
guide of the scope item 1RO - Master Data Integration. Please also pay attention to the following for the
communication arrangement creation of SAP_COM_0008:

● It's similar to the setup of the communication scenario SAP_COM_0084, the SAP Cloud Connector is
needed for SAP_COM_0008 as well. So, besides the virtual host of RFC protocol, you have to create
another virtual host with HTTPS protocol for your SAP GTS system in the SAP Cloud Connector. You can
use the same virtual host name for both protocol types, which allows you to use the same communication
system for both communication arrangement creation of SAP_COM_0084 and SAP_COM_0008.
● Make sure the Business System and Logical System are correctly maintained in the communication system,
which is crucial for SAP_COM_0008.
● When creating the communication arrangement, note down the Own System in Common Data area. This
Own System is given by the system and it represents your SAP S/4HANA Cloud system, which is used as
Business System of SAP S/4HANA Cloud when performing the configurations in SAP GTS system.

Setting Up Customs Management with SAP Global Trade Services (2U1)

SAP S/4HANA Configuration PUBLIC 9
 You only need to activate the following outbound services for our scope item:
○ Business Partner - Replicate from SAP S/4HANA Cloud to Client
○ Business Partner Relationship - Replicate from SAP S/4HANA Cloud to Client
Make sure the paths of outbound services are correct. The details on how to maintain the paths are given in
the set-up guide of the scope item 1RO - Master Data Integration.
Under Additional Properties of the outbound service Business Partner - Replicate from SAP S/4HANA Cloud
to Client, you can maintain the following properties:
○ Replication Model: <enter the name of any replication model that you want to
create for replications>
○ Replication Mode: C
○ System Filter: X (the filter can be defined before starting the replication.)
○ Output Mode: D (If the Job Execution is specified, you have to choose output mode P.)
Download the WSDL files for the following inbound services, which are used for SOAMANAGER
configurations in your SAP GTS system:
○ Business Partner - Receive Confirmation from Client to SAP S/4HANA Cloud
○ BP Relationship - Receive Confirmation from Client to SAP S/4HANA Cloud

To generate the logical ports for the consumer proxies of the services
BusinessPartnerSUITEBulkReplicateConfirmation_Out and
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out, perform SOAMANAGER
configurations for the services BusinessPartnerSUITEBulkReplicateConfirmation_In and
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_In, and the service group
MDG_BS_SUPPLIERREPLICATECONF in your SAP GTS system.

● The details can be referred to the chapter Configuration for Business Partner Data Integration from SAP On-
Premise Systems to S/4HANA Cloud via SOAP Services in the set-up guide of the scope item 1RO - Master
Data Integration, but you have to change the services and service group accordingly. It means when you
refer to the set-up guide of the scope item 1RO - Master Data Integration, the service
BusinessPartnerSUITEBulkReplicateRequest_In has to be replaced with
BusinessPartnerSUITEBulkReplicateConfirmation_In, the service
BusinessPartnerRelationshipSUITEBulkReplicateRequest_In has to be replaced with
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_In, and the service group
MDG_BS_SUPPLIERREPLICATEREQ has to be replaced with MDG_BS_SUPPLIERREPLICATECONF.
● Once the integration scenario is activated for the services
BusinessPartnerSUITEBulkReplicateConfirmation_In and
BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_In, and the service group
MDG_BS_SUPPLIERREPLICATECONF, the logical ports for the consumer proxies will be generated.

Procedure

1. In the upper left corner, choose Home.

2. Open Communication Arrangements.
3. On the Maintain Communication Arrangements screen, choose New.
4. On the New Communication Arrangement dialog box, make the following entries and choose Create:
Scenario: SAP_COM_0084

Setting Up Customs Management with SAP Global Trade Services (2U1)

10 PUBLIC SAP S/4HANA Configuration
  Note

The Arrangement Name field is automatically populated.

5. In the Common Data area, make the following entries:

Arrangement name: <keep the default value>
Communication System: <communication system from prior step>
6. In the Inbound Communication area, make the following entries and choose Save:
User name: <keep the default value> (should be the same as Maintain Communication User [page 7])

Result

The communication arrangement is created. The required authorization role is assigned to the inbound
communication user.

Setting Up Customs Management with SAP Global Trade Services (2U1)

SAP S/4HANA Configuration PUBLIC 11
6 Communication Set-up in SAP GTS

The following steps need to be performed in your SAP Global Trade Services system to set up the outbound
communication from the SAP Global Trade Services system to the SAP S/4HANA Cloud system.

6.1 Creating an RFC Destination

Use

In this activity, you create the RFC destination to the SAP S/4HANA Cloud system.

Procedure

1. In the GTS system, access the transaction by choosing one of the following navigation options:

SAP Menu Tools Administration Administration RFC Destinations

Transaction Code SM59

2. On the Configuration of RFC Connections screen, choose Create.

3. On the RFC Destination screen, make the following entries and choose Save:

Field name User action and values Comment

Destination <the ID of SAP S/4HANA Cloud

system>

Connection Type W Here your SAP Cloud Connector is supposed to

be integrated with Cloud Foundry Environment.
If it's integrated with Neo Environment, choose
connection type 3 instead of W.

Description <the name of SAP S/4HANA Cloud

system>

4. Choose the Technical Settings tab.

Setting Up Customs Management with SAP Global Trade Services (2U1)

12 PUBLIC Communication Set-up in SAP GTS
 5. Make the following entries and choose Save:

Field name User action and values Comment

Target Host Target SCC System Host For example, the full qualified hostname of SCC

System Number Target SCC instance number

6. Choose the Logon & Security tab.

7. Make the following entries and choose Save:

Field name User action and values Comment

Client Target SAP S/4HANA Cloud system

client

 Note
In your SAP S/4HANA Public Cloud envi­
ronment, the client number is 100.

User RFC Connection User

Password Connection User’s password

 Note

The RFC connection user is the User Name of the SAP S/4HANA communication user created in section
Maintain Communication User [page 7].

8. To verify that the connection works, choose the Connection Test button. If the connection test is not successful,
you must perform analysis and troubleshooting.

6.2 Defining a Logical System

Use

In this activity, you define the logical system for the SAP S/4HANA Cloud system.

Setting Up Customs Management with SAP Global Trade Services (2U1)

Communication Set-up in SAP GTS PUBLIC 13
Procedure

1. To perform the activity in the SAP GTS system, choose one of the following navigation options:

IMG Menu SAP Global Trade Services System Communication

Define Logical System

Transaction Code SPRO

2. If the Caution: The table is cross-client dialog box displays, choose Continue.
3. Choose New Entries.
4. On the New Entries: Overview of Added Entries screen, make the following entries and then choose Save:

Field Name User Action and Values Comment

Log.System <ID of SAP S/4HANA Cloud  Caution

system> The logical system must be identi­
cal to the ID of your own system in
the SAP S/4HANA Cloud system.

Name <Name of SAP S/4HANA Cloud

system>

5. Save your entry.

6.3 Defining Group of Logical Systems

Use

In this step, you create a new group of logical systems. If you decide to use an existing group, you can skip this step.

Procedure

1. In the GTS system, access the transaction choosing the following navigation option:

IMG SAP Global Trade Services System Communication Define Group of Logical Systems
menu

Setting Up Customs Management with SAP Global Trade Services (2U1)

14 PUBLIC Communication Set-up in SAP GTS
 2. If the Caution: The table is cross-client dialog box displays, choose Continue.
3. Choose New Entries.
4. On the Change View "Logical System Group": Details screen, make the following entries and choose Save:

Field name User action and values Comment

Logical System Group Name of logical system

group

Description Description of logical

system group

Role of Logical System Group Role of logical system

group

5. Save your entry.

6.4 Assigning a Logical System to a Group of Logical Systems

Use

In this step, you assign the logical system to the logical system group.

Procedure

1. In the GTS system, access the transaction choosing the following navigation option:

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

2. If the Caution: The table is cross-client dialog box displays, choose Continue.
3. Choose New Entries.
4. On the Change View "Logical System Grouping: Assign Logical System": Details screen, make the following
entries and choose Save:

Setting Up Customs Management with SAP Global Trade Services (2U1)

Communication Set-up in SAP GTS PUBLIC 15
 Field name User action and values Comment

Logical System Logical system of SAP S/

4HANA Cloud system

Logical System Group Logical system group

5. Save your entry.

6.5 Defining RFC Destinations for Method Calls

Use

In this step, you assign RFC destinations for method calls in the SAP GTS system.

Procedure

1. In the Command field, enter BD97 and press Enter .

2. On the Assign RFC Destinations for Synchronous Method Calls screen, choose the logical system of the SAP S/
4HANA Cloud system.
3. Choose Standard BAPI destination.
4. In the Assign RFC Destinations for Synchronous Method Calls dialog box, make the following entries and then
choose Continue:

Field name User action and values Comment

RFC destination for BAPI calls RFC destination connection

of SAP S/4HANA Cloud
system

5. Choose Save.

Setting Up Customs Management with SAP Global Trade Services (2U1)

16 PUBLIC Communication Set-up in SAP GTS
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

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

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Setting Up Customs Management with SAP Global Trade Services (2U1)

Important Disclaimers and Legal Information PUBLIC 17
www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN