Set-Up Instructions | PUBLIC

SAP S/4HANA Cloud Public Edition

2025-01-29

Setting Up Third-Party Shop Floor Execution - Process

Industry (3W3)
© 2025 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

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

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Required Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SAP Cloud Connector for Integration with SAP S/4HANA Cloud Private Edition MES Systems. . . . . . . 4
Master Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1 Create Technical Communication User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Create Communication System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.3 Create Communication Arrangement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.4 Assigning Recipients for AIF Message Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
3.5 Monitoring Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 Ticket Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

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 to start the guided CIAS workflow.

This document describes additional configuration steps that you must carry out in the productive system
on customer site to activate the Integration of Manufacturing Execution - Order and Confirmation Integration
(SAP_COM_0522) scope item. As these configuration steps are company-specific, they cannot be delivered by SAP,
and must be carried out by the company setting up the SAP solution.

This communication scenario provides end points (inbound and outbound), which are needed to integrate an
SAP S/4HANA Cloud Private Edition third-party MES solution (Manufacturing Execution System) to production
operation through SOAP and OData.

For more information, refer to the Prerequisites section.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

Purpose PUBLIC 3
2 Preparation

2.1 Required Information

During the course of the activities described in this guide, you are required to enter or provide system-specific
information. To ensure a smooth and efficient integration to SAP S/4HANA Cloud Public Edition, we recommend
that you have the information listed in the table below at hand prior to starting the integration process.

Type of Information Required: Your Data

SAML Local identity provider certificate of Jam instance Recommendation: Create a zip file

SAML Local identity provider issuer of certificate of Jam in-

stance

Communication user ID starting with CC Refer to the Create Technical Communication User section.

SAP S/4HANA Cloud Public Edition system

URL and system ID of your Manufacturing Execution system

2.2 Prerequisites

2.2.1 General

It's mandatory that the Third-Party Shop Floor Execution - Process Industry (3W3) scope item is active. You can
check this in the Manage Your Solution app. To get there, log on to the SAP Fiori launchpad as a Configuration
Expert - Business Process Configuration (for example, SAP_BR_BPC_EXPERT) and search for the app name.

If the scope item is not active, please raise an incident via BCP to request the activation using the following ticket
component: XX-S4C-OPR-SRV.

2.2.2 SAP Cloud Connector for Integration with SAP S/4HANA

Cloud Private Edition MES Systems

For all scenarios integrating SAP S/4HANA Cloud Public Edition with SAP S/4HANA Cloud Private Edition
scenarios, the SAP_COM_0574 - SAP BTP Connectivity Service - SAP S/4HANA Cloud Private Edition integration
communication arrangement must be activated. This is a prerequisite for all other communication arrangements.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

4 PUBLIC Preparation
To check if the SAP_COM_0574 - SAP BTP Connectivity Service - SAP S/4HANA Cloud Private Edition 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 SAP S/4HANA Cloud Private Edition
Systems.

2.2.3 Master Data Integration

Depending on the prerequisites of your third-party shop floor system, it may be mandatory to integrate master
data to transfer a production order successfully.

The following master data communication scenarios are available and shall be activated if needed:

• Product Integration (SAP_COM_0009)

Additionally, the following scenarios can be implemented:

• Product Lifecycle Management - Core Master Data Integration (SAP_COM_0150)

• Product Lifecycle Management - Master Data Integration (SAP_COM_0105)
• Classification Systems Integration (SAP_COM_0160)
• Production Planning Master Data Integration (SAP_COM_0519)
• Classification Systems OData Integration

 Note

The BOM will not be distributed to the SAP Shop Floor system automatically since this integration is not yet
available. To run the process, you may need to create the applicable BOMs in your shop floor system on your
own depending on the prerequisites of your shop floor system.

One of the following scope items is a prerequisite for running the 3W3 scope item. However, the described
master data in the test script do fit BJ8 scope item.

• Make-to-Stock - Process Manufacturing Based on Process Order (BJ8)

• Inbound Storage Tank Management - Process Manufacturing (3UK)
• Tank Trailer Filling with Residuals (42N)
• Make-to-Order Production - Process Manufacturing (3OK)
• Make-to-Stock with Co- and By-Products - Process Manufacturing (3L7)
• Make-to-Stock with Silo Material - Process Manufacturing (3UL)

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

Preparation PUBLIC 5
3 Configuration

 Note

The Third-Party Shop Floor Execution - Process Industry (3W3) scope item does not include a complete
business process for the integration of a shop floor system with SAP S/4HANA Cloud Public Edition. It
only includes the definition of the interface. To implement a complete business scenario end to end that is
applicable to the customer’s needs, additional customizing might be necessary. This needs to be done by the
customer or with the help of a consultant.

The following sections describe all settings required for this scope item.

The communication arrangements, named in the table, must be activated in SAP S/4HANA Cloud Public Edition
for communication with web services.

Communication Arrangement ID Name of Communication Arrangement

SAP_COM_0522 Manufacturing Execution - Order and Confirmation Integration

3.1 Create Technical Communication User

Prerequisite

To carry out 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).

Procedure

1. Log on to the SAP Fiori launchpad as an Administrator in the SAP S/4HANA Cloud Public Edition system.
2. Open the Maintain Communication Users app.
3. Choose New to create a new user (for example, USER_NAME) or select an existing user.
4. Enter a description for the user.
5. Enter a password for the user.
6. Choose Create.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

6 PUBLIC Configuration
 7. Note user data. This is required when you create the communication arrangement.

 Note

For using certificates in the interface, you have to upload a certificate. Therefore, choose Upload Certificate and
browse for the file. Choose Upload.

If you want to use an SSL Client Certificate, you need to upload the public key certificate that has been provided
by your communication partner. If your communication partner can't provide a certificate, you can create and
download a PKCS#12 key pair file. This file is password-encrypted and contains a public key certificate and a
private key. You need to provide the PKCS#12 file to your communication partner.

3.2 Create Communication System

Procedure

1. Log on to the SAP Fiori launchpad as an Administrator in the SAP S/4HANA Cloud Public Edition system.
2. Open the Communication Systems app.
3. Choose New to create a new system.
4. Enter a system ID and a system name.
5. Choose Create.
6. In the Technical Data section, enter information regarding the system you wish to integrate.
7. In the Hostname field, enter the URL of your shop floor system without HTTPS.
8. In the Business System field, enter the system ID for your shop floor system.
9. In the User for Inbound Communication section, choose Add.
Here, you define how the external system authenticates itself when it sends business documents to your
solution. You can choose one of the following authentication methods depending on the authentication method
of the selected user:
• User name and password
• SSL Client Certificate
Select the communication user from the Create Technical Communication User section using the value
help.

 Note

If you want to create a new communication user, choose New User.

10. In the User for Outbound Communication section, choose Add.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

Configuration PUBLIC 7
  Note

Here, you define how your solution authenticates itself when it sends business documents to the external
system. You can choose between the following authentication methods:

• User name and password

• SSL Client Certificate
If you want to use an SSL Client Certificate, you may either use the default certificate of your solution or a
trusted third-party key pair.
Select an authentication method and enter the user name that calls the shop floor system. If you choose User
Name and Password for the authentication method, enter the user and the password for the user. If you choose
SSL Client Certificate, enter the certificate type.
11. Choose Save.

3.3 Create Communication Arrangement

Procedure

1. Log on to the SAP Fiori launchpad as an Administrator in the SAP S/4HANA Cloud Public Edition system.
2. Open the Communication Arrangements app.
3. Choose New to create a new communication arrangement.
4. Select SAP_COM_0522 (Manufacturing Execution - Order and Confirmation Integration).
5. The Arrangement Name field is filled automatically as the name of the selected Manufacturing Execution -
Order and Confirmation Integration scenario. Adapt the arrangement name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System that was created in the Create Communication
System section. Use the value help.
8. The technical user that was created in the Create Technical Communication User section is automatically
added to the Inbound Communication section.
The included inbound services are listed in the Inbound Services section.

SAP S/4HANA
Cloud Public
Interaction Edition Format SAP S/4HANA Cloud Public Edition Interface

Production Order Con- Inbound OData API_PROD_ORDER_CONFIRMATION_2_SRV

firmation

Production Order (Ver- Inbound OData API_PRODUCTION_ORDER_2_SRV

sion 2)

Process Order Confir- Inbound OData API_PROC_ORDER_CONFIRMATION_2_SRV

mation

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

8 PUBLIC Configuration
 SAP S/4HANA
Cloud Public
Interaction Edition Format SAP S/4HANA Cloud Public Edition Interface

Process Order (Version Inbound OData API_PROCESS_ORDER_2_SRV

2)

9. In Outbound Communication, the user which is associated with the Communication System is shown by default
in the value help for the User Name field. By choosing this user, the Authentication Method is defaulted with the
same authentication method associated with this user.
10. In the Outbound Services section for Manufacturing Order - Send, Version 2, you must make sure that the
Service Status checkbox is selected for Manufacturing Order - Send, Version 2, which makes the service Active.
The included outbound service is:

SAP S/4HANA
Cloud Public
Interaction Edition Format SAP S/4HANA Cloud Public Edition Interface

Manufacturing Order- Outbound SOAP CO_PPINT_MFGORD_EXECT_REQ_OUT_V2_SPRX

Send, Version 2

 Note

In the SAP S/4HANA Cloud Public Edition solution, the delivered order types are set by default to shop
floor distribution if a communication scenario is created and activated. Therefore, by activating this
integration scenario, all orders will automatically be distributed to your shop floor system if you do not
define special filter criteria. Consequently, order confirmation can no longer be carried out within the SAP
S/4HANA Cloud Public Edition system but needs to be carried out in your shop floor system and sent back
to the SAP S/4HANA Cloud Public Edition system.

11. In the Additional Properties section, enter the following data:

Property Name Property Value Note

Material <your material> Select the material for which produc-

tion orders shall be distributed to your
 Note shop floor system.

For the demo data used within

this scope item, please refer to the
master data overview document.

Order Type <your order type> Select the order type of the production
orders that shall be distributed to your
shop floor system.

Plant <your plant> Select your plant using the value help.

 Note

The system evaluates the filter criteria using the following logic:
• If several filter criteria are applied to the same attribute (for example, material), the system applies the
filter if any filter criterion is true. For example, material is Test1 or material is Test2.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

Configuration PUBLIC 9
 • If several filter criteria are applied to different attributes (for example, material and order type), the
system applies the filter if all filter criteria are true. For example, material is Test1 and order type is
YBM1.
• Empty fields are not considered and thus don't have an impact on the result.

12. Choose Save.

Result

The communication arrangement has been activated.

3.4 Assigning Recipients for AIF Message Monitoring

Procedure

1. Access the SAP Fiori launchpad and log on as a Configuration Expert - Business Network Integration
(SAP_BR_CONF_EXPERT_BUS_NET_INT).
2. Open Assign Recipients to Users.
3. Select Add User.
4. In the dialog box that displays, enter the user name or user ID.
5. Choose Add.
6. In the dialog box that displays, enter the following namespace and recipient for alerts:

Namespace Recipient Name

/LOGPE MANUFACTURING_ORDER_RECEIVER_2

7. Choose Assign Recipient.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

10 PUBLIC Configuration
3.5 Monitoring Messages

Procedure

1. Access the SAP Fiori launchpad and log on as a Configuration Expert - Business Network Integration
(SAP_BR_CONF_EXPERT_BUS_NET_INT).
2. Choose Message Dashboard - SAP Application Interface Framework.
3. This launches the Message Dashboard page.
4. Use the Calendar Monitor to select the date range for viewing the triggered messages and choose Search.
5. In the Result List, view the messages and check for the log details.
6. Select the entry for which you wish to check the log. Customers communicating with SAP do so via the SAP
ticketing system.

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

Configuration PUBLIC 11
4 Appendix

4.1 Ticket Component

If you're facing issues during configuration, create a ticket under the following ACH components:

Enter the application component in which the customer should create a ticket in case of issues during
configuration.

In case of issues during the configuration, open an SAP support ticket for the following component.

Implementation Step Component Comment

Prerequisite XX-S4C-OPR-SRV For activating scope items

PP-CNT For issues concerning content

PP-SFC-ES For issues concerning

OData:

• API_PROD_ORDER_CONFIRMATION_2_SRV
• API_PRODUCTION_ORDER_2_SRV
• API_PROC_ORDER_CONFIRMATION_2_SRV
• API_PROCESS_ORDERS_2_SRV

SOAP:

• CO_PPINT_MFGORD_EXECT_REQ_OUT_V2_SPRX

Setting Up Third-Party Shop Floor Execution - Process Industry (3W3)

12 PUBLIC Appendix
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 Third-Party Shop Floor Execution - Process Industry (3W3)

Important Disclaimers and Legal Information PUBLIC 13
[Link]/contactsap

© 2025 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 [Link] for

additional trademark information and notices.

THE BEST RUN