Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud

2023-12-08

Setting Up Procurement of Services (22Z)

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

THE BEST RUN

Content

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

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Communication Management Configuration (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 Communication Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Related Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5 Suppliment Information (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Setting Up Procurement of Services (22Z)

2 PUBLIC Content
1 Purpose

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.

Setting Up Procurement of Services (22Z)

Purpose PUBLIC 3
2 Preparation

2.1 Prerequisites

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

1. External system is already set up.

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 22Z- Procurement of Services is active.
• 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 Procurement of Services (22Z)

4 PUBLIC Preparation
3 Communication Management
Configuration (Optional)

3.1 Communication User

Use

In S/4HANA Cloud the management of data integration is based on communication scenarios. The relevant
communication scenario for Service Entry Sheet Process Integration is SAP_COM_0237. For the communication
scenario, a communication user is needed:

Procedure

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:

Launchpad Navigation

Communication Management -> Maintain Communication Users

3. Choose New to create a new communication user

4. On the Create Communication User screen, make following entries:

Field Name Entry Value and user action

User Name For example：<DUMMY_USER>

Description For example：<DUMMY_USER>

Password For example：<Initial1!>

5. Choose Create.

Setting Up Procurement of Services (22Z)

Communication Management Configuration (Optional) PUBLIC 5
  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.

3.2 Communication Systems

Use

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.

Procedure

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:

Launchpad Navigation

Communication Management -> Communication Systems

3. Communication System For communication arrangement SAP_COM_0237

In S/4HANA Cloud the management of data integration is based on communication scenarios. The
relevant communication scenario for Service Entry Sheet Process Integration is SAP_COM_0237. For the
communication scenario, a communication system is needed:
1. Choose New to create a new communication system.
2. On the New communication system screen, make following entries:

Field Name Entry Value and user action

ID For example：<ExternalService>

System Name For example：<ExternalService>

3. Choose Create.
4. On the Communication System screen, make the following entries:

Setting Up Procurement of Services (22Z)

6 PUBLIC Communication Management Configuration (Optional)
 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.
5. Choose Save.

3.3 Communication Arrangement

Use

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.

Procedure

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:

Launchpad Navigation

Communication Management -> Communication Arrangements

3. Communication System For communication arrangement SAP_COM_0237

In S/4HANA Cloud the management of data integration is based on communication scenarios. The
relevant communication scenario for Service Entry Sheet Process Integration is SAP_COM_0237. For the
communication scenario, a communication arrangement is needed:
1. Choose New.On the New communication system screen, make following entries:

Field Name Entry Value and user action

Scenario Select SAP_COM_0237(Service Entry Sheet Process Inte-

gration)

Arrangement Name Arrangement name of this Communication Arrangement

Setting Up Procurement of Services (22Z)

Communication Management Configuration (Optional) PUBLIC 7
 Field Name Entry Value and user action

Create

On the Communication Arrangements screen, make following entries:

Field Name Entry Value and user action

Communication System select the communication system you have created in the
previous chapter (e.g. < ExternalService >)

User Name/Certificate The User Name of Inbound Communication and User

Name of Outbound Communication will be assigned auto-
matically after the Communication System is selected.

Create

For outbound service “Service Entry Sheet Status Notification”, enter the following data:

Field Name Entry Value and user action

Service Status Service Status is active

Path Provided from an external system account services or

support representative

Choose Save. The communication arrangement will become active and all required configurations will be
generated.

Setting Up Procurement of Services (22Z)

8 PUBLIC Communication Management Configuration (Optional)
4 Related Scenarios

The following scope items cover other scenarios related to service procurement. More details can be found in these
scope items.

SI Link

4AZ-Contract Management with SAP Ariba Contracts Please refer to 4AZ test script in SAP Best Practice Ex-
plorer .

42K-Automation of Source-to-Pay with SAP Business Network Please refer to 42K test script in SAP Best Practice Ex-
plorer .

2NV-Guided Buying Capability with SAP Ariba Buying Please refer to 2NV test script in SAP Best Practice Ex-
plorer .

3EN-Guided Buying for Central Procurement with SAP Ariba Please refer to 3EN test script in SAP Best Practice Ex-
Buying plorer .

22K-External Workforce Procurement via SAP Fieldglass Please refer to 22K test script in SAP Best Practice Ex-
plorer .

4R2-Service Procurement with SAP Business Network and SAP Please refer to 4R2 test script in SAP Best Practice Ex-
Fieldglass plorer .

4BL-Sourcing with SAP Ariba Sourcing Please refer to 4BL test script in SAP Best Practice Ex-
plorer .

4B0-Contract for Central Procurement with SAP Ariba Please refer to 4B0 test script in SAP Best Practice Ex-
Contracts plorer .

Setting Up Procurement of Services (22Z)

Related Scenarios PUBLIC 9
5 Suppliment Information (Optional)

Description /Compo-
Topic nent Notes Component Supported in

Migraiton : Following Tool to download MM- For details, please re- MM-SRV-MD (Master SAP ECC
tools and docuemnts SRV related master Data)
fer to the specific
are available for migra- data and contracts
tion from SAP ECC MM- SAP Note 2906140
SRV or external ERP - Service Migration
Systems objects - Products,
Info Record and Con-
tracts(lean and item hi-
erarchies).

Migraiton cockpit in Service objects For service product, LO-MD SAP S/4HANA Public
SAP S/4HANA sup- Cloud/ SAP S/4HANA
the material or prod-
ports following objects Private Cloud/ SAP S/
uct master contains
4HANA
information about all
physical materials that
are procured, produced,
stored and sold. It’s also
used to manage infor-
mation about services,
for example for buying
and selling services in
hours.

Please refer to Service

Product for details.

Purchasing contracts With item hierarchies, MM-PUR SAP S/4HANA Public

with/ without item hier- buyers can logically Cloud/ SAP S/4HANA
archies structure external pro- Private Cloud/ SAP S/
curement demand in 4HANA
their master data,
contracts, and transac-
tional documents. For
more information about
mapping structure hi-
erarchy, please refer
to MM - Purchase con-
tract.

Setting Up Procurement of Services (22Z)

10 PUBLIC Suppliment Information (Optional)
 Description /Compo-
Topic nent Notes Component Supported in

Model Product Specifi- Migration objects are MM-PUR-MPS SAP S/4HANA Public
cation Cloud only
built for your initial
data migration to your
SAP S/4HANA Cloud
system.

Regarding migration of
model product specifi-
cation from MM-SRV
Model Service Specifi-
cation to S/4 Model
Product Specification,
please refer to Model
product Specification
for details.

Setting Up Procurement of Services (22Z)

Suppliment Information (Optional) PUBLIC 11
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 an 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 Procurement of Services (22Z)

12 PUBLIC Important Disclaimers and Legal Information
Setting Up Procurement of Services (22Z)
Important Disclaimers and Legal Information PUBLIC 13
www.sap.com/contactsap

© 2023 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