Professional Documents
Culture Documents
Sl4 s4cld1805 Set-Up en XX
Sl4 s4cld1805 Set-Up en XX
Sl4 s4cld1805 Set-Up en XX
1 Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5 Communication Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
The purpose of this document is to describe the general configuration steps required to manually set up the
integration for SAP S/4HANA with external system that has already been installed using the corresponding
installation or configuration guides for installation.
This document supplements the existing Customizing documentation in the Implementation Guide (IMG) and
provides additional information where required.
2.1 Prerequisites
Before you start installing this scenario, please check if following prerequisites are prepared.
In order to configure the integration, users require the following catalog roles in S/4HANA CLOUD:
SAP_BR_CONF_EXPERT_BUS_NET_INT
2. It is also mandatory that scope item Supplier Evaluation and Performance Monitor (SL4 Mandatory, 19E Optional,
1FM Optional for quality inspection lot and quality notification) is active. You can check this in the App Manage Your
Solution under View Solution Scope.
If the scope items are not active, please request the activation via BCP – Ticket Component: XX-S4C-OPR-SRV.
In S/4HANA Cloud the management of data integration is based on communication scenarios. The relevant
communication scenario for Operational Supplier Evaluation Score Integration is SAP_COM_0324. For the
communication scenario, a communication user is needed:
1. Log on to your SAP S/4HANA system with a user who has the business role:
SAP_BR_CONF_EXPERT_BUS_NET_INT.
2. Access the transaction using the following navigation path:
Communication Users
Table 1:
5. Choose Create.
Note
It is mandatory to assign an inbound communication user to a communication arrangement even if the
communication is purely outbound. This means you have to create a sort of dummy user. Create such a
dummy user so that you can later assign it to the communication system.
Communication system is used to define the host name of the HCI tenant and to assign users for the inbound and
outbound communication.
Additionally, a second communication system with the host name of the external system is needed to enable the
navigation from SAP S/4HANA to external system. A communication user is not needed here for access the
external system.
1. Log on to your SAP S/4HANA system with a user who has the business role:
SAP_BR_CONF_EXPERT_BUS_NET_INT.
2. Access the transaction using the following navigation path:
Communication Users
Table 2:
○ Choose Create.
○ On the Communication System screen, make the following entries:
Host Name: <External System Host Name> (provided from an external system account services or support
representative)
Logical System: <Logical System>
Business System: <Business System>
• In the User for Inbound Communication area, choose Add, then choose the user name created from the
previous step, choose OK.
• In the User for Outbound Communication area, choose Add and make the following entries:
Authentication Method: User Name and Password
User Name: the user name for the login on external system
Password: the password(license) for the login on external system
Choose Create.
○ Choose Save.
The Communication arrangement in S/4HANA system defines all relevant information for the communication with
Integration. For example, it contains the communication system, inbound and outbound authentication.
1. Log on to your SAP S/4HANA system with a user who has the business role:
SAP_BR_CONF_EXPERT_BUS_NET_INT.
2. Access the transaction using the following navigation path:
Arrangements
Table 3:
Create
Table 4:
Communication System select the communication system you have created in the
previous chapter (e.g. < ExternalService >)
Create
○ Choose Save. The communication arrangement will become active and all required configurations will be
generated.
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.
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.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.