Integration Guide | PUBLIC

Document Version: 2305 – 2023-05-19

SAP Digital Manufacturing Integration Guide

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

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 SAP Digital Manufacturing for execution Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1 Integration with SAP S/4HANA or SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Minimum Version Requirements and Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Overview Integration with SAP S/4HANA / SAP ERP for Discrete Industries. . . . . . . . . . . . . . . . .12
Overview Integration with SAP S/4HANA / SAP ERP for Process Industries. . . . . . . . . . . . . . . . . 13
Technical Integration with SAP S/4HANA or SAP ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Business Integration with SAP S/4HANA or SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Customizing the Integration Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Upgrade Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Restrictions and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
2.2 Integration with SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Minimum Version Requirements and Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Overview Integration with SAP S/4HANA Cloud for Discrete Industries. . . . . . . . . . . . . . . . . . . 236
Overview Integration with SAP S/4HANA Cloud for Process Industries. . . . . . . . . . . . . . . . . . . 237
Technical Integration with SAP S/4HANA Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Business Integration with SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Restrictions and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
2.3 Integration with SAP Business Network Asset Collaboration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Verification and Troubleshooting for SAP Business Network Asset Collaboration. . . . . . . . . . . . 316
2.4 Integration with EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
Minimum Version Requirements and Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . .318
Connecting to EWM in SAP S/4HANA 1909 to 2020. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Connecting to EWM in SAP S/4HANA 2021. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Mapping Plants (Plant Conversion). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Technical Restrictions and Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
2.5 Troubleshooting Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Troubleshooting for the Integration with SAP S/4HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
2.6 Extensibility Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

3 Shop Floor Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

3.1 Integration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Digital Twin Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Machine Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Production Process Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Production Process Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

SAP Digital Manufacturing Integration Guide

2 PUBLIC Content
3.2 Integrate with Production Connector / SAP Plant Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Enable Communication from Production Connector / SAP Plant Connectivity to Cloud. . . . . . . 358
Minimum Version Requirements and Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Assignment of Production Connector / SAP Plant Connectivity Role to IAS User Groups. . . . . . 360
3.3 Integration with SAP MII. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
3.4 Troubleshooting for Configure Production Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Connectivity Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Internal Server Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
User Authentication Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

4 Resource Orchestration Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

4.1 Overview Characteristics-Based Sequencing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368
Integration with SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
4.2 Integration with SAP Manufacturing Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372
Minimum Version Requirements and Supported Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Integrating SAP Manufacturing Execution On-Premise to Resource Orchestration (Inbound)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Integrating Resource Orchestration to SAP Manufacturing Execution On-Premise (Outbound)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Configuring Master Data for Resource Orchestration in SAP ME System. . . . . . . . . . . . . . . . . . 386
Maintain Custom Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
4.3 Data Engineering Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Data Engineering - An Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

SAP Digital Manufacturing Integration Guide

Content PUBLIC 3
1 Introduction

This Integration Guide provides you with information on the available integration options and gives you step-by-
step instructions to integrate your business system with SAP Digital Manufacturing.

Overview

SAP Digital Manufacturing is a fully cloud-based manufacturing execution system that focuses on the
execution, data analysis, control, and integration of manufacturing processes. SAP Digital Manufacturing
connects the shop floor with your business system to optimize resources and execution.

This Integration Guide gives you an overview of the existing integration scenarios and provides you with
detailed information on the steps required to integrate your business system with SAP Digital Manufacturing.
The guide covers the technical as well as the business aspects of your integration project. You’ll learn how to
enable the data exchange between systems and how to make sure that the right business data are transferred.

Example of a Hybrid Digital Manufacturing Landscape

• https://go.sap.corp/UA [https://go.sap.corp/UA]

SAP Digital Manufacturing can be integrated with the following business systems:

SAP Digital Manufacturing Integration Guide

4 PUBLIC Introduction
 • SAP ERP
• SAP S/4HANA
• SAP S/4HANA Cloud
• SAP Manufacturing Execution
• SAP Manufacturing Integration and Intelligence
• SAP Plant Connectivity
• SAP Overall Equipment Effectiveness Management
• SAP Digital Manufacturing for edge computing
• SAP Business Network Asset Collaboration
• SAP Extended Warehouse Management

This integration enables the exchange of transaction data, master data, and machine data between the
customer-level business systems and SAP Digital Manufacturing for execution or SAP Digital Manufacturing for
insights.

Integration Options

The following integration scenarios are available:

• SAP Digital Manufacturing for execution Integration [page 7]

• Shop Floor Integration [page 351]
• Resource Orchestration Integration [page 368]

 Recommendation

The business scenarios presented in this Integration Guide are examples of how you might use SAP
software in your company. The business scenarios are intended only as models and may not run in your
specific system landscape exactly as they’re described here. Be sure to check your requirements and
systems to determine whether these scenarios can be used productively at your site. Also, we recommend
that you test these scenarios thoroughly in your test systems to ensure they’re complete and free of errors
before going live.

This Integration Guide primarily discusses the overall technical implementation of SAP Digital
Manufacturing and not its subcomponents. This means that additional software dependencies might exist
that aren’t mentioned explicitly in this document.

Minimum Version Requirements and Supported Scenarios

Here you'll find detailed information on the minimum version requirements and supported scenarios:

• Minimum Version Requirements and Supported Scenarios for Integration with SAP ERP / SAP S/4HANA
[page 10]
• Minimum Version Requirements and Supported Scenarios for Integration with SAP S/4HANA Cloud [page
234]

SAP Digital Manufacturing Integration Guide

Introduction PUBLIC 5
• Minimum Version Requirements and Supported Scenarios for Integration with SAP Manufacturing
Execution [page 373]
• Minimum Version Requirements and Supported Scenarios for Integration with SAP Plant Connectivity
[page 360]
• Minimum Version Requirements and Supported Scenarios for Integration with SAP Extended Warehouse
Management [page 318]

SAP Digital Manufacturing Integration Guide

6 PUBLIC Introduction
2 SAP Digital Manufacturing for execution
Integration

SAP Digital Manufacturing for execution supports various integration scenarios for both discrete and process
industries. The supported ERP systems include on-premise and cloud systems.

The following diagram provides an overview of the possible integration scenarios. This is an interactive image,
hover over each area for more information.

• [page 9]
• Integration with SAP S/4HANA Cloud [page 234]
• Integration with SAP Business Network Asset Collaboration [page 313]
• [page 357]
• [page 372]

Business Scenarios

You can integrate SAP Digital Manufacturing for execution with SAP ERP, SAP S/4HANA, and SAP S/4HANA
Cloud to implement business scenarios for process and discrete industries. For more information, see:

• Overview Integration with SAP S/4HANA / SAP ERP for Discrete Industries [page 12]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 7
• Overview Integration with SAP S/4HANA / SAP ERP for Process Industries [page 13]
• Overview Integration with SAP S/4HANA Cloud for Discrete Industries [page 236]
• Overview Integration with SAP S/4HANA Cloud for Process Industries [page 237]

Integration Scenarios

You can integrate SAP Digital Manufacturing for execution with various systems. The following table provides
an overview of the integration scenarios and their constituent components:

Integration Scenario

Integration Integration
Integration with SAP with SAP
Integration Integration with SAP Business Extended
Integrated Sys­ Integration with SAP S/ with SAP S/ Manufacturing Network Asset Warehouse
tems with SAP ERP 4HANA 4HANA Cloud Execution1 Collaboration Management2

SAP ERP * * *

SAP S/4HANA * * *

SAP S/4HANA * * *
Cloud

SAP *
Manufacturing
Execution

SAP Business * * * *
Network Asset
Collaboration

SAP Extended * * * *
Warehouse
Management

Cloud Connec­ * * * *
tor

SAP Cloud * * * *
Integration

• 1 Integration with SAP Manufacturing Execution is limited to Resource Orchestration.

• 2Integration with SAP Extended Warehouse Management is limited to on-premise systems that are either
standalone or embedded with SAP S/4HANA.

Related Information

Integration with SAP S/4HANA or SAP ERP [page 9]

Integration with SAP S/4HANA Cloud [page 234]
Integration with SAP Manufacturing Execution [page 372]

SAP Digital Manufacturing Integration Guide

8 PUBLIC SAP Digital Manufacturing for execution Integration
Integration with SAP Business Network Asset Collaboration [page 313]
Integration with EWM [page 317]

2.1 Integration with SAP S/4HANA or SAP ERP

SAP Digital Manufacturing for execution uses SAP Cloud Integration to communicate with integrated SAP
S/4HANA or SAP ERP systems. You can connect multiple ERP systems, for example one system per plant or
country. The global SAP Digital Manufacturing for execution system is used across all plants.

 Note

If you integrate SAP Digital Manufacturing for execution with multiple SAP S/4HANA or SAP ERP systems,
these systems need to have unique system IDs. Systems are identified at the client level.

 Note

If you need to maintain multiple plants, each plant needs to have a unique plant name across the tenant.

 Note

If you integrate multiple SAP Digital Manufacturing tenants with ERP systems, you need multiple SAP
Cloud Integration tenants. For example, you need one SAP Cloud Integration tenant for your SAP Digital
Manufacturing quality tenant and another one for your SAP Digital Manufacturing production tenant. You
can use both SAP Cloud Integration tenants for other cloud products and applications, too.

After you've completed the onboarding procedures as described in Onboarding and User Management, you
can continue with the configurations required to establish connectivity between SAP Digital Manufacturing and
SAP S/4HANA or SAP ERP systems.

Integration with SAP S/4HANA or SAP ERP enables the data transfer from and to these systems. The data
transfer can be broadly categorized into master data and transactional data. To transfer data, you need to
make sure all prerequisites are met and the required configurations are set up. For more information, see
Technical Integration with SAP S/4HANA or SAP ERP [page 14] and Business Integration with SAP S/4HANA
or SAP ERP [page 115].

Related Information

Minimum Version Requirements and Supported Scenarios [page 10]

Restrictions and Limitations [page 233]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 9
2.1.1 Minimum Version Requirements and Supported
Scenarios

This topic describes the minimum release requirements, supported scenarios, and limitations for integrating
SAP Digital Manufacturing with SAP ERP and SAP S/4HANA.

Minimum Release Requirements

To use all features provided by SAP Digital Manufacturing, you require:

• SAP ERP 6.0 EHP7 or higher

• SAP S/4HANA 1709 onwards

 Note

For some integration message types, there are higher version requested. For more information on the
supported message types, see 3050090 .

Supported Scenarios

Scenario SAP ERP SAP S/4HANA

Production order Yes Yes

Process order Yes Yes

Planned order Yes Yes

Material Yes Yes

Bill of materials Yes Yes

Routing Yes Yes

Recipe Yes Yes

Work center Yes Yes

Equipment PRT Yes Yes

Work instruction at order header level Yes Yes

Yield/scrap Yes Yes

Inventory Yes Yes

SAP Digital Manufacturing Integration Guide

10 PUBLIC SAP Digital Manufacturing for execution Integration
Scenario SAP ERP SAP S/4HANA

Return inventory Yes Yes

Scrap inventory Yes Yes

Use Resource Orchestration for Yes Yes

scheduling

Middleware Requirements

• SAP Cloud Integration and Cloud Connector are required as middleware

• SAP Cloud Integration in the Neo environment is supported

Supported IDocs

IDoc SAP ERP SAP S/4HANA

Yes Yes
MATMAS03

BOMMAT04 Yes No

BOMMAT05 No Yes

Yes Yes
LOIROU04

Yes Yes
LOIPRO05 (production and process
orders)

LOIPLO02 (planned order) Yes Yes

Yes No
INVCON02

Yes Yes
INVCON03

Yes Yes
LOIWCS03

Yes Yes
EQUIPMENT_CREATE02

Limitations

Inventory transfer between storage locations from SAP Digital Manufacturing isn't supported.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 11
2.1.2 Overview Integration with SAP S/4HANA / SAP ERP for
Discrete Industries

The following diagram provides an overview of the integration of SAP Digital Manufacturing for execution and
SAP ERP or SAP S/4HANA for discrete industries. Select highlighted areas for more detailed information.

• Work Center Integration [page 138]

• Bill of Material Integration [page 125]
• Routing Integration [page 142]
• Production Version [page 128]
• Transfer of QM Defect Code Groups and Codes [page 141]
• Tool Integration [page 145]
• Production Order Integration [page 148]
• Transferring a Process Order with Inspection Lot (type 03) [page 174]
• Transfer of Floor Stock Data [page 194]
• Material Integration [page 117]
• Production Order Status Confirmation [page 162]
• Inspection Results Recording (Process Order and Order-Based Production Order) [page 193]
• Configure Inspection Points
• Transfer of Floor Stock Return and Scrap Data [page 200]
• Integration with EWM [page 317]
• Staging Request Upon Order Release
• Material Consumption (Order POD)

SAP Digital Manufacturing Integration Guide

12 PUBLIC SAP Digital Manufacturing for execution Integration
• Goods Receipt (Work Center POD)
• Goods Receipt (Order POD)
• Component Removal
• Transferring a Planned Order [page 181]
• Planned Order Integration [page 180]
• Activity Confirmation [page 171]
• Quantity Confirmation [page 172]

2.1.3 Overview Integration with SAP S/4HANA / SAP ERP for

Process Industries

The following diagram provides an overview of the integration of SAP Digital Manufacturing for execution and
SAP ERP or SAP S/4HANA for process industries. Select highlighted areas for more detailed information.

• Material Integration [page 117]

• Work Center Integration [page 138]
• Bill of Material Integration [page 125]
• Recipe Integration [page 144]
• Production Version [page 128]
• Transfer of QM Defect Code Groups and Codes [page 141]
• Tool Integration [page 145]
• Process Order Integration [page 173]
• Transferring a Process Order with Inspection Lot (type 03) [page 174]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 13
• Transfer of Floor Stock Data [page 194]
• Process Order Status Confirmation [page 175]
• Batch Creation [page 191]
• Batch Characteristics Update [page 190]
• Configure Inspection Points
• Transfer of Floor Stock Return and Scrap Data [page 200]
• Staging Request Upon Order Release
• Component Consumption (Work Center POD)
• Material Consumption (Order POD)
• Goods Receipt (Work Center POD)
• Goods Receipt (Order POD)
• Inspection Results Recording (Process Order and Order-Based Production Order) [page 193]
• Component Removal
• Integration with EWM [page 317]

2.1.4 Technical Integration with SAP S/4HANA or SAP ERP

Here are the administrative configurations that need to be set up to enable communication between SAP
Digital Manufacturing for execution and SAP S/4HANA or SAP ERP.

Integration Overview

As the On-Premise Enterprise Network environment is protected by a firewall, an asymmetrical communication

design connects SAP Digital Manufacturing for execution to SAP S/4HANA or SAP ERP.

SAP Digital Manufacturing Integration Guide

14 PUBLIC SAP Digital Manufacturing for execution Integration
• Build HTTP Connection [page 31]
• Data Replication Framework [page 36]
• Connect SAP Cloud Integration to SAP Digital Manufacturing [page 64]
• Connect SAP Digital Manufacturing to SAP Cloud Integration [page 85]
• Setting Up the Cloud Connector [page 22]
• Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 104]
• Configure SAP Digital Manufacturing for Outbound Integration [page 106]

From SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for execution, HTTPS is used to connect SAP
Cloud Integration (previously called CPI). SAP Cloud Integration parses and sends the transaction to SAP
Digital Manufacturing for execution for processing. Transaction examples: material import and production
import.

From SAP Digital Manufacturing for execution to SAP S/4HANA or SAP ERP, an RFC is used to call SAP S/
4HANA or SAP ERP BAPI from the SAP Cloud Connector. Transaction examples: production yield confirmation
and production scrap confirmation.

In certain scenarios, you can also use OData for direct outbound calls to SAP S/4HANA to connect the
systems. This doesn't apply for SAP ERP. For more information, see Enable Direct Communication To SAP
S/4HANA [page 107].

 Note

For more information on the supported message types and needed integration artifacts, see
0003050090 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 15
  Note

• Plant names need to be unique across the different ERP systems at the client level.
• Integration is possible with one Digital Manufacturing system.
• The XSLT customization is shared across all plants. You can add if-else conditions to differentiate
between plant values.

 Note

You can check your integration scenario using the Check Integration Configuration functionality provided by
the Integration Message Dashboard app.

After choosing Check Integration Configuration, you select an integration message to start an automated
test of the integration configuration that covers the full integration scenario from SAP Digital
Manufacturing to the connected ERP system and back. The following tests are performed:

• Destination check
• SAP Cloud Integration parameter check
• SAP Cloud Integration artifact check
• Inbound connectivity check

In case of an error, a message will point you to the solution.

 Tip

If you're an integration developer and want to learn more about how to design integration flows, you
can refer to the Integration Flow Design Guidelines. You'll find there lots of information on the underlying
concepts as well as practical examples that will help you deepen your knowledge. For more information, see
Integration Flow Design Guidelines.

If you're particularly interested in optimizing workflow performance, you can jump right to this topic:
Optimize Performance.

Overview Integration Steps

For the technical integration of SAP Digital Manufacturing for execution with SAP S/4HANA or SAP ERP,
perform the tasks described in the following topics:

1. Before You Start [page 17]

2. Setting Up the Cloud Connector [page 22]
3. Build HTTP Connection [page 31]
4. Data Replication Framework [page 36]
5. Prepare Credentials for Initial Parameter Deployment [page 51]
6. Connect SAP Cloud Integration to SAP Digital Manufacturing [page 64]
7. Connect SAP Digital Manufacturing to SAP Cloud Integration [page 85]
8. Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 104]

SAP Digital Manufacturing Integration Guide

16 PUBLIC SAP Digital Manufacturing for execution Integration
9. Configure SAP Digital Manufacturing for Outbound Integration [page 106]
10. Enable Direct Communication To SAP S/4HANA [page 107]

Related Information

Asynchronous Connection to SAP Cloud Integration [page 109]

Troubleshooting Overview [page 342]

2.1.4.1 Before You Start

This page shows you the prerequisite steps that must be completed before configuring integration with SAP
S/4HANA or SAP ERP.

Before you start, you must have performed the following steps:

• Complete the onboarding process

 Note

This includes the configuration of the S4H_INTEGRATION_OAUTH destination. The destination data
is used by SAP Digital Manufacturing to provide authentication and authorization for internal system
communication. You also require it to integrate with SAP ERP, SAP S/4HANA, and SAP S/4HANA
Cloud.

• Download SAP Cloud Integration package. For more information on SAP Cloud Integration, see SAP Cloud
Integration.
• Create a separate subaccount for your SAP Cloud Integration tenant in SAP BTP cockpit in addition to
your SAP Digital Manufacturing subaccount. Without two separate subaccounts, the direct communication
scenarios that you might want to use now or in the future aren't supported. For more information, see
Enable Direct Communication To SAP S/4HANA [page 107].
• Upload SSL certificates [page 18]
• Create a Technical User for SAP S/4HANA [page 19]
• Know how to get the SAP Cloud Integration Management URL [page 20]
• Know how to get the SAP Cloud Integration Runtime URL [page 21]
• The following business functions, which are the technical basis for the Data Replication Framework (DRF),
have been implemented in SAP S/4HANA or SAP ERP:
• LOG_PP_MES_INT_01
• LOG_PP_MES_INT_02
• LOG_PP_MES_INT_03
• You've implemented BADI CO_MES_INT_REDISTRIBUTION in SAP S/4HANA or SAP ERP. This BADI
makes sure that the integrated ERP system doesn't communciate an order change to SAP Digital
Manufacturing after receiving the release notification (RMES). For more information, see 2165261 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 17
Next Steps

• Setting Up the Cloud Connector [page 22]

• Build HTTP Connection [page 31]
• Set Up Data Replication Framework (DRF) [page 36]
• Connect SAP Cloud Integration to SAP Digital Manufacturing [page 64]
• Connect SAP Digital Manufacturing to SAP Cloud Integration [page 85]
• Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 104]
• Configure SAP Digital Manufacturing for Outbound Integration [page 106]
• Enable Direct Communication To SAP S/4HANA [page 107]

2.1.4.1.1 Upload SSL Certificates

This page shows you how to upload SSL certificates to build the trust between the systems.

The certificate uploading processes mentioned below apply to SAP Cloud Integration in both Neo and Cloud
Foundry environments.

Upload SSL Certificate of SAP Cloud Integration to SAP ERP or SAP S/

4HANA

Download SAP Cloud Integration Certificate

1. Go to the SAP Cloud Integration management URL, which you can find in the service key of your api plan
service instance in your SAP Cloud Integration subaccount in SAP BTP cockpit. You can ignore any 404
error when accessing the URL. For details, see How to Get SAP Cloud Integration Management URL [page
20].
2. Choose  in the address bar to download the SSL certificate of SAP Cloud Integration. Save the certificate
in file format base-64 encoded X.509 (.cer).

Upload Certificate to SAP ERP or SAP S/4HANA

1. Log on to the SAP ERP or SAP S/4HANA system as an Administrator.
2. Use the transaction STRUST to access Trust Manager.
3. Upload the certificate you saved in previous steps to SSL client SSL Client (Standard) node.

SAP Digital Manufacturing Integration Guide

18 PUBLIC SAP Digital Manufacturing for execution Integration
Upload SSL Certificate of SAP Digital Manufacturing to SAP Cloud
Integration

Download SAP Digital Manufacturing Certificate

1. Log on to SAP BTP cockpit and go to your SAP Digital Manufacturing subaccount.
2. Under Instances and Subsriptions Subscriptions , choose your SAP Digital Manufacturing application
in the Application column.
3. Choose  in the address bar to download the certificate. Save the certificate in file format base-64
encoded X.509 (.cer).

Upload Certificate to SAP Cloud Integration

For more information, see Importing a Certificate.

2.1.4.1.2 Create a Technical User for SAP S/4HANA

To connect SAP S/4HANA with SAP Cloud Integration and Cloud Connector, you need to create a technical
user.

Prerequisites

• Access to transaction SU01

• Authorization to create technical users in the system

Context

You need a technical user for SAP S/4HANA to set up a connection between SAP S/4HANA, SAP Cloud
Integration, and Cloud Connector.

Procedure

1. Log on to SAP S/4HANA.

2. Open transaction SU01.
3. Enter the name for the technical user and choose  Technical User to create the user.
4. As User Type, choose System from the dropdown menu.
5. Assign a password for the user.
6. In the Documentation tab, enter a description for the user.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 19
7. In the Profiles tab, assign SAP_ALL or SAP_NEW to your user.
8. Choose Save.

Results

You have created a technical user for SAP S/4HANA.

2.1.4.1.3 How to Get SAP Cloud Integration Management

URL

This page shows how to get the management URL of SAP Cloud Integration.

Prerequisites

You need to be a member of the global account in order to access the instances and subscriptions of SAP
Cloud Integration tenant and get the management URL.

Get SAP Cloud Integration Management URL (Cloud Foundry Environment)

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount and then choose Instances and
Subscriptions.
2. In the Instances tab, choose an instance with api as Plan.
3. In the Service Keys tab, choose the service key.
4. In the Credentials window, you find the SAP Cloud Integration management URL in the url field.

 Example

https://<Cloud Integration tenant>.hana.ondemand.com

 Note

This instance is created during the integration process. For more information, see Create a Service
Instance and Key with Authorization Code [page 61].

SAP Digital Manufacturing Integration Guide

20 PUBLIC SAP Digital Manufacturing for execution Integration
Get SAP Cloud Integration Management URL (Neo Environment)

1. In SAP BTP cockpit, select your subaccount and then choose Applications Subscriptions .
2. In the Subscribed Java Applications section, choose the <Cloud Integration tenant>tmn application.
3. In the Application URLs section, you see the management URL named https://<Cloud Integration tenant>-
tmn.<…>.eu1.hana.ondemand.com.

Related Information

How to Get SAP Cloud Integration Runtime URL [page 21]

2.1.4.1.4 How to Get SAP Cloud Integration Runtime URL

This page shows how to get the runtime URL of SAP Cloud Integration.

Prerequisites

You need to be a member of the global account in order to access the instances and subscriptions of Cloud
Integration tenant and get the runtime URL.

Get SAP Cloud Integration Runtime URL (Cloud Foundry Environment)

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount and then choose Instances and
Subscriptions.
2. In the Instances tab, find the instance for the Process Integration Runtime service, which has integration-
flow as plan, and choose the link to the key in the Credentials column.
3. In the key credentials pop-up, under JSON, you can see the runtime URL under the url tag.

 Note

This instance is created during the integration process. For more information, see Create Instances in SAP
Cloud Integration Subaccount [page 95].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 21
Get SAP Cloud Integration Runtime URL (Neo Environment)

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount and then choose Applications
Subscriptions .
2. In the Subscribed Java Applications section, choose the <Cloud Integration tenant>iflmap application.
3. In the Application URLs section, you will see the runtime URL named https://<Cloud Integration tenant>-
iflmap.avtsbhf.eu1.hana.ondemand.com.

Related Information

How to Get SAP Cloud Integration Management URL [page 20]

2.1.4.2 Setting Up the Cloud Connector

Configure a Cloud Connector that acts as a reverse invoke proxy between an on-premise network and the SAP
Business Technology Platform. The Cloud Connector comes standard as part of the SAP Cloud Integration
service and serves as a link between the SAP Business Technology Platform and on-premise systems such as
SAP S/4HANA.

In SAP Digital Manufacturing, the following integration scenarios use a Cloud Connector:

• Scenario 1 - Execution2S4 [page 9]: SAP Digital Manufacturing (execution) → SAP Cloud Integration →
Cloud Connector → SAP S/4HANA
• Scenario 2 - REO2ME [page 372]: SAP Digital Manufacturing (resource orchestration) → SAP Cloud
Integration → Cloud Connector → SAP Manufacturing Execution
• Scenario 3 - PPD/Insights/MM2PCo [page 357]: SAP Digital Manufacturing (Production Process
Designer / insights / Production Connectivity Model) → Cloud Connector → Production Connector / SAP
Plant Connectivity

SAP Digital Manufacturing Integration Guide

22 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.2.1 Install Cloud Connector

Find out how to install the Cloud Connector.

Context

The installation files for the Cloud Connector are located at SAP Development Tools.

For prerequisites and instructions for installing the Cloud Connector, see the user assistance for SAP BTP
Connectivity.

After the installation, an Administrator user account is automatically created. The initial password is
manage. You're required to change the initial password when you log in for the first time.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 23
2.1.4.2.2 Configure Subaccounts in Cloud Connector

For each SAP Business Technology Platform subaccount that you want to connect with an on-premises
system, configure a tenant / customer subaccount in the Cloud Connector.

Prerequisites

• You need a user account for the subaccount to establish the connection between the SAP Business
Technology Platform subaccount and the Cloud Connector. For Cloud Foundry and Neo environments, the
requirements vary for this user.
• For a subaccount in the Cloud Foundry environment, the subaccount user must be a security
administrator of the subaccount.
• For a subaccount in the Neo environment, the subaccount user must have the scope
manageSCCTunnels. You can assign the user to the predefined role Cloud Connector Admin or
Administrator, or assign the user to a custom role that includes the scope.
• You have configured an HTTP proxy for the Cloud Connector to access the Internet. The proxy must
support SSL communication.

 Note

With the Cloud Connector installed, you can configure the first subaccount and proxy. To do this, on the
initial configuration page look for the proxy settings in Connector Configuration .

Context

You always have two separate subaccounts: one for SAP Digital Manufacturing and one for SAP Cloud
Integration.

For the following scenarios, configure the Neo or Cloud Foundry subaccount for SAP Cloud Integration in the
Cloud Connector:

• Execution2S4
• REO2ME

For the following scenario, configure the Cloud Foundry subaccount for SAP Digital Manufacturing in the Cloud
Connector:

• PPD/insights/MM2PCo

For more information about these scenarios, see Setting Up the Cloud Connector [page 22].

SAP Digital Manufacturing Integration Guide

24 PUBLIC SAP Digital Manufacturing for execution Integration
Procedure

1. 1. Using a web browser, log on to the Cloud Connector by using https://<hostname>:<port> as

Administrator.

 Note

<hostname> is the hostname of the machine on which the Cloud Connector is installed. If you access
the Cloud Connector locally from the same machine, enter localhost. For <port>, enter the port
that you specified during the installation.

The initial password for Administrator is manage.

2. Choose Connector Add Subaccount .

3. In the Add Subaccount screen, enter the following information:

Field Description

Region Select the data center in which the SAP Business Technology Platform subaccount
is hosted.

Subaccount • [Cloud Foundry]: Enter the subaccount ID.

• [Neo]: Enter the technical name of the subaccount.

 Note
You can find the subaccount ID and technical name in the subaccount list in the
global account or on the overview page of each subaccount.

Subaccount User • [Cloud Foundry]: Enter the email address a subaccount user uses to log in to
the SAP Business Technology Platform cockpit.
• [Neo]: Enter the P- or S- ID of a subaccount user.

Password Enter the password that the subaccount user uses to log in to the SAP Business
Technology Platform cockpit.

Location ID If you use more than one Cloud Connector to connect to the same subaccount,
define a unique location ID per Cloud Connector for the subaccount.

4. Save the subaccount.

5. On the Subaccount Dashboard, in the Actions column, choose  (Connect this subaccount) for this
subaccount.

Results

The status of the subaccount is displayed as Connected in the Cloud Connector.

You can also verify the connection status of the subaccount in the SAP Business Technology Platform cockpit.
In the subaccount, choose Connectivity Cloud Connectors . The status should be Connected.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 25
Related Information

Configure trust to SAP Digital Manufacturing by defining an allowlist of cloud applications that can use the
Cloud Connector.
Initial Configuration
Cloud Foundry: Add Organization Members Using the Cockpit
Neo: Add Members to Your Subaccount

2.1.4.2.3 Configure Access Control

Expose an on-premise system to the cloud and specify the resources accessible from the cloud.

Context

To expose an on-premise system, create a virtual system in the Cloud Connector and then map it to an internal
on-premise system. When making the configuration, you need to define a virtual host and a virtual port for the
virtual system. The virtual host and port are used to identify the on-premise system when creating destinations
in the corresponding SAP Business Technology Platform subaccount.

In addition, you must specify the resources that are accessible from the cloud. This step is required even if you
don’t limit access to resources. In other words, you need to explicitly specify that all resources are accessible.

For more information about the different integration scenarios, see Setting Up the Cloud Connector [page 22].

Procedure

1. In the Cloud Connector administration console, choose <Subaccount> Cloud To On-Premise

ACCESS CONTROL .
2. In the Mapping Virtual To Internal System section, choose  (Add).

A wizard appears that guides you through all the required settings.
3. In the wizard, enter the information according to the protocol used for communication and the specific
on-premise system.
• To communicate with SAP S/4HANA using RFC, follow the instructions at Configure Access Control
(RFC).
Applicable scenario: Execution2S4
• To communicate with SAP S/4HANA, SAP Manufacturing Execution, or Production Connector / SAP
Plant Connectivity using HTTPS, follow the instructions at Configure Access Control (HTTP).
Applicable scenarios: REO2ME, PPD/Insights/MM2PCo

For the back-end type and principal type system, see the following table:

SAP Digital Manufacturing Integration Guide

26 PUBLIC SAP Digital Manufacturing for execution Integration
 On-Premise System Back-end Type Principal Type

SAP S/4HANA ABAP System None

SAP Manufacturing Execution SAP Application Server None

Java

Production Connector / SAP Plant Other SAP System None

Connectivity

 Note

The virtual host and virtual port can be freely defined. However, you can't edit the virtual host or virtual
port after you’ve added the mapping.

4. To specify resources that are accessible from the cloud, add the resources for the system.

You can find detailed instructions at Configure Accessible Resources. In addition, for the required
configurations for each integration scenario, see the following table:

Scenario Field Description

Execution2S4 Resource 1 Function Name Enter

CO_MES_PRODORDCONF_
CREATE_TT.
Enabled Select the checkbox.

Naming Policy Select Exact Name.

Resource 2 Function Name Enter

CO_MES_SVK_WITH_LAN
GUAGE.
Enabled Select the checkbox.

Naming Policy Select Exact Name.

Resource 3 Function Name Enter

MB_MES_GOODSMVT_CRE
ATE
Enabled Select the checkbox.

Naming Policy Select Exact Name.

Resource 4 Function Name Enter

QIRF_SEND_CATALOG_D
ATA2
Enabled Select the checkbox.

Naming Policy Select Exact Name.

Resource 5 Function Name Enter BAPI.

Enabled Select the checkbox.

Naming Policy Select Prefix.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 27
 Scenario Field Description

PPD/Insights/MM2PCo URL Path Enter /cloudservices.

Enabled Select the checkbox.

Access Policy Select Path and all sub-

paths.

REO2ME URL Path Enter /.

Enabled Select the checkbox.

Access Policy Select Path and all sub-

paths.

 Note

For more information on the supported message types and available BAPIs, see 0003050090 .

The following BAPIs aren't used directly by SAP Digital Manufacturing but are used by SAP Cloud
Integration. Therefore, you must configure them in the cloud connector:

BAPI_TRANSACTION_COMMIT

BAPI_TRANSACTION_ROLLBACK

Results

In the SAP Business Technology Platform cockpit for the corresponding subaccount, you can find
the accessible resource configuration. Choose Connectivity Cloud Connectors Exposed Back-End
Systems .

2.1.4.2.4 Set Up Mutual Authentication with On-Premise

Systems

To set up mutual authentication between the Cloud Connector and an on-premise system, import an X.509
client certificate into the Cloud Connector.

Context

The certificate must be issued for the fully qualified domain name (FQDN) of the machine on which you've
installed the Cloud Connector. The Cloud Connector uses the so-called system certificate for all HTTPS
requests to back-end systems that request or require a client certificate.

SAP Digital Manufacturing Integration Guide

28 PUBLIC SAP Digital Manufacturing for execution Integration
Related Information

Install a System Certificate for Mutual Authentication

2.1.4.2.5 Configure User Authentication Against On-

Premise Systems

To secure the communication with an on-premise system, apply different user authentication methods
depending on the integration scenario you use.

Context

For more information about the integration scenarios, see Setting Up the Cloud Connector [page 22].

Scenario Authentication Method

Execution2S4 Basic authentication using destinations

For more information about how to create the destinations,

see Set Up Connection Between SAP Cloud Integration,
Cloud Connector, and SAP S/4HANA or SAP ERP [page
104].

REO2ME Basic authentication using destinations

For more information about how to create the destinations,

see Integrating Resource Orchestration to SAP Manufactur­
ing Execution On-Premise (Outbound) [page 380].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 29
Scenario Authentication Method

PPD/Insights/MM2PCo Principal propagation using an X.509 CA certificate.

 Note
Principal propagation is possible but not required from
15.4 SP2 onwards.

The certificate must be issued for the fully qualified domain

name (FQDN) of the machine on which you've installed the
Cloud Connector.

If you use a self-signed certificate, place the public key in the

Trusted store location in the file system of the Production
Connector / SAP Plant Connectivity server:

SAP Plant Connectivity

C:\ProgramData\SAP\PCo\CertificateStores
\CloudServicesHost\Trusted\certs.

Production Connector

C:\ProgramData\SAP\ProdCon\CertificateSt
ores\CloudServicesHost\Trusted\certs

You can obtain the public key by choosing Connector

Configuration ON PREMISE Download certificate in DER

format .

For more information, see Configure a CA Certificate for

Principal Propagation.

Related Information

Authenticating Users Against On-Premise Systems

SAP Digital Manufacturing Integration Guide

30 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.3 Build HTTP Connection

If you want to allow SAP S/4HANA or SAP ERP to access data from SAP Cloud Integration, you need an HTTP
connection for the communication.

Prerequisites

• You've got the SAP Cloud Integration runtime URL, which can be found in the provisioning email that is
sent when the space is created. For more information, see How to Get SAP Cloud Integration Runtime URL
[page 21].
• Depending on your environment and your preferred authentication method, you've got one of the following
users:

Environment User Password Comment

Cloud Foundry P-User* authorized in SAP P-User password Basic authentication

Cloud Integration

Cloud Foundry SAP Cloud Integration Cli­ SAP Cloud Integration Cli­ Recommended authentica­
ent ID ent Secret tion because no need to
change the password peri­
odically. Same security level
as with basic authentication

Neo P-User* authorized in SAP P-User password Basic authentication

Cloud Integration

Neo SAP Cloud Integration Cli­ SAP Cloud Integration Cli­ Recommended authentica­
ent ID ent Secret tion because no need to
change the password peri­
odically. Same security level
as with basic authentication

 Note

*For more information on how to obtain a P-user and on how grant it access to SAP Cloud Integration,
see Granting Your P-User Access to SAP Cloud Integration in Neo Environment [page 33] or Granting
Your P-User Access to SAP Cloud Integration in Cloud Foundry Environment [page 35].

To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 31
  Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

• If you want to use a P-user, it has been authorized for SAP Cloud Integration. For more information see,
Granting Your P-User Access to SAP Cloud Integration in Neo Environment [page 33] or Granting Your
P-User Access to SAP Cloud Integration in Cloud Foundry Environment [page 35].

Procedure

1. In SAP S/4HANA or SAP ERP, run transaction code SM59 to enter the Configuration of RFC Connections
screen.
2. Choose Edit Create
3. Enter the following general data:
• RFC Destination: Name of the HTTP connection, for example DME_INT
• Connection Type: G (HTTP Connection to External Server)
4. In the Technical Settings tab, enter data for the fields as follows:

Field Example Description

Target Host <Cloud Integration tenant>-ifl- SAP Cloud Integration runtime URL
map.avtsbhf.eu1.hana.ondemand.com that is sent by the provisioning email
when the space is created.

Alternatively, you can get the runtime

URL in the SAP BTP cockpit. For more
information, refer to How to Get SAP
Cloud Integration Runtime URL [page
21].

 Note
Do not paste https:// as it is auto­
matically added.

Port 443

Path Prefix /cxf/GenericMessageProcessor_00 The service implemented on SAP

Cloud Integration to receive the mes­
sage/IDOC from SAP S/4HANA or
SAP ERP.

SAP Digital Manufacturing Integration Guide

32 PUBLIC SAP Digital Manufacturing for execution Integration
 Field Example Description

Proxy Host  Example The proxy host for the external sys­
tem connection.
proxy.wdf.sap.corp

Proxy Service  Example The proxy service for the external sys­
tem connection.
8080

5. In the Logon & Security tab, complete the following settings.

1. Choose Basic Authentication, and enter the User and Password. For more information about the
available authentication methods and users, see in the prerequisites.
2. Activate SSL, and in SSL Certificate field, keep the default value DFAULT SSL Client (Standard).
6. Choose Connection Test to test the connection between SAP S/4HANA or SAP ERP and SAP Cloud
Integration.

 Note

If the GenericMessageProcessor iFlow has been deployed in SAP Cloud Integration, the Status HTTP
Response shows the value 500, which, contrary to what is normally expected, indicates a successful
connection. Otherwise, an error message is displayed.

2.1.4.3.1 Granting Your P-User Access to SAP Cloud

Integration in Neo Environment

Learn how to authorize your P-user for SAP Cloud Integration in Neo environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount.

• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 33
  Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Overview, choose Members.
3. Choose Add Members.
4. In the User IDs field, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predefined role) and Developer (predefined role).
6. Choose Add Members.

7. Choose Security Authorizations .

8. On the Users tab, enter your P-user ID and choose Show Assignments.
9. Choose Assign in the area for individual assignment, not group assignment.

The Assign Roles to User popup opens.

10. Go through the available subaccounts and applications to assign the following roles and save them:

ESBMessaging.send

AuthGroup.BusinessExpert

AuthGroup.Administrator

AuthGroup.IntegrationDeveloper

Results

Your P-user has now access to SAP Cloud Integration.

SAP Digital Manufacturing Integration Guide

34 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.3.2 Granting Your P-User Access to SAP Cloud
Integration in Cloud Foundry Environment

Learn how to authorize your P-user for SAP Cloud Integration in Cloud Foundry environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount in SAP BTP cockpit.
• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Security Users , choose Create.

3. Under User Name, enter the e-mail address belonging to your P-user.
4. Choose Default Identity Provider.
5. Choose Create.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 35
6. Choose Security Role Collections .
7. Choose  .
8. Give your collection a name, for example My_RoleCollection, and choose Create.
9. Select your collection and choose Edit.
10. On the Roles tab, under Role Name, choose  and add the following roles to your collection:

MessagingSend

MessagePayloadsRead

AuthGroup_BusinessExpert

If you want to use the CPI Async Mode, there a some additional roles required. For more information, see
Asynchronous Connection to SAP Cloud Integration [page 109].

11. Under Security Users , choose your user.

12. In the detail view, choose Assign Role Collection to make the following assignments:

My_RoleCollection

PI_Integration_Developer (predefined)

PI_Administrator (predefined)

Results

Your P-user has now access to SAP Cloud Integration.

2.1.4.4 Data Replication Framework

You can use the Data Replication Framework (DRF) to send master and transactional data from SAP S/4HANA
or SAP ERP to SAP Digital Manufacturing for execution using IDocs.

Use
You can use the Data Replication Framework (DRF) to send master and transactional data from SAP ERP or
SAP S/4HANA to SAP Digital Manufacturing for execution using IDocs. An IDoc is a data container with a
standardized structure that is used to exchange data. Several message types (for example, production order
or work center) can be sent from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution using
IDocs.

To control the distribution of messages more precisely, you create replication models in which you can define
filter criteria for the business objects (for example, production order or work center) to be sent to SAP Digital
Manufacturing for execution.

 Note

For more information on the Data Replication Framework (DRF), see ERP-MES Integration (PP-MES).

SAP Digital Manufacturing Integration Guide

36 PUBLIC SAP Digital Manufacturing for execution Integration
General Overview of the Procedure
To use the Data Replication Framework (DRF), you must first set up ALE communication (Application Link
Enabling), which is the technical basis for data exchange between your systems. You need to define the
following elements in SAP ERP or SAP S/4HANA:

• Logical systems representing the communcation partners

• Document type (IDoc) and communication protocol
• IDoc message types to be exchanged
• Distribution model to control the distribution of IDoc messages

After setting up the ALE communication, you can make the necessary configurations for the Data Replication
Framework (DRF) that enables you to send messages in specific business contexts (for example, release of a
production order in SAP ERP or SAP S/4HANA).

To set up the Data Replication Framework (DRF), you need to configure the following elements in SAP ERP or
SAP S/4HANA:

• Assign business object types to your business system

• Filter critera for the replication model that control the distribution of business objects (for example, Plant,
Order Type, or Material as criteria to transfer all production orders belonging to a specific plant, specific
order type, or specific material.)
• Replication model that defines which business objects (for example, production order or work center) are
sent to which system

Overview Setup Steps

To set up the Data Replication Framework (DRF), perform the tasks described in the following topics:

1. Before You Start [page 37]

2. Create Logical Systems [page 38]
3. Assign a Logical System to a Client [page 39]
4. Defining Outbound Communication in SAP S/4HANA or SAP ERP [page 40]
5. Define Outbound Messages for Partner Systems [page 41]
6. Define a Distribution Model [page 43]
7. Assign Business Objects to Your Business System [page 45]
8. Define Filter Criteria [page 47]
9. Define Replication Models and Outbound Implementations [page 49]

2.1.4.4.1 Before You Start

Here you find the requirements that must be met before you can start setting up the Data Replication
Framework (DRF).

To set up the Data Replication Framework (DRF), the following requirements must be met:

• You have the Administrator role for SAP S/4HANA or SAP ERP.
• You have set up a HTTP connection. For more information, see Build HTTP Connection [page 31].
• The following business functions have been implemented in SAP S/4HANA or SAP ERP:
• LOG_PP_MES_INT_01

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 37
 • LOG_PP_MES_INT_02
• LOG_PP_MES_INT_03

2.1.4.4.2 Set Up Application Link Enabling (ALE)

2.1.4.4.2.1 Create Logical Systems

As administrator, you need to create logical systems in your SAP S/4HANA or SAP ERP client to set up the
Data Replication Framework (DRF).

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

To use the Data Replication Framework (DRF) for the transfer of master data from SAP S/4HANA or SAP ERP
to SAP Digital Manufacturing for execution, you need to create two logical systems in your SAP S/4HANA or
SAP ERP client. The first represents your SAP S/4HANA or SAP ERP system, the second your SAP Digital
Manufacturing for execution system.

Procedure

Define the logical system.

1. Use transaction BD54 and define the logical system in the cross-client for SAP S/4HANA or SAP ERP.

 Note

Creating a logical system is a cross-client activity, that is, all changes also affect all other clients in the
system. You need the authorization S_TABU_CLI in order to do it.

2. Use transaction BD54 and define the logical system for SAP Digital Manufacturing for execution.
Add a logical system for the distribution of production orders.
3. Use transaction SPRO and choose SAP Reference IMG.

4. Choose Production Integration with a Manufacturing Execution System Integrate Production Orders
with a Manufacturing Execution System Maintain Logical System for Distribution of Production Orders .
5. Choose New Entries to add a logical system.

SAP Digital Manufacturing Integration Guide

38 PUBLIC SAP Digital Manufacturing for execution Integration
  Example

Determ. Method Logical

Plant Order Type System Logical System

<Plant number>, for <Order type>, for ex­ Data Replication DMETest
example, 1010 ample, * Framework
(DRF) Controls
Distribution

6. Choose Save.

Results

You have created two logical systems representing your source and target system.

2.1.4.4.2.2 Assign a Logical System to a Client

As administrator, you need to assign a logical system to a client in SAP S/4HANA or SAP ERP to set up the
Data Replication Framework (DRF).

Prerequisites

• You have the Administrator role.

• You have defined a logical system for the SAP S/4HANA or SAP ERP system using transaction BD54. For
more information, see Create Logical Systems [page 38].

Context

Setting up the Data Replication Framework (DRF) to enable data exchange between SAP S/4HANA or SAP ERP
and SAP Digital Manufacturing for execution requires you to assign a logical system to your SAP S/4HANA or
SAP ERP client.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 39
Procedure

1. Log on to SAP S/4HANA or SAP ERP as an Administrator.

2. Access the activity using one of the following navigation options:

Option Description

Transaction code SCC4

Initial screen of the SAP SAP Menu Tools Administration Administration Client Administration
system Client Maintenance

3. On the Display View "Clients": Overview screen, choose Edit.

4. Confirm the information message Caution: The table is cross client.
5. Select your SAP S/4HANA or SAP ERP client (for example, client 100) to be connected to the SAP Digital
Manufacturing for execution system, and choose Details.
6. In the Logical System field, select the newly created logical system of your SAP S/4HANA or SAP ERP
client using the value help.
7. Choose Save ( Ctrl + S ) and confirm the message Be careful when changing the logical system.
8. Choose Back ( F3 ) twice.

Results

You have successfully assigned the logical system to your client.

2.1.4.4.2.3 Defining Outbound Communication in SAP S/

4HANA or SAP ERP

As administrator, you define a port for outbound communication, the IDoc format as container for messages
and the SOAP protocol in SAP S/4HANA or SAP ERP to enable data transfer between your system and SAP
Digital Manufacturing for execution using the Data Replication Framework (DRF).

Prerequisites

You have the Administrator role in SAP S/4HANA or SAP ERP.

SAP Digital Manufacturing Integration Guide

40 PUBLIC SAP Digital Manufacturing for execution Integration
Context

To transfer master data from SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for execution using the
Data Replication Framework (DRF), you define a port for outbound communication in SAP S/4HANA or SAP
ERP. Moreover, you choose the IDoc format as a container for your messages and SOAP as protocol for the
data exchange.

Procedure

1. Use transaction WE21.

2. In XML HTTP, choose the RFC destination that you have created using SM59 as described in Build HTTP
Connection [page 31].
3. Choose Application/x-sap.idoc and SOAP Protocol.
4. Choose Save.

Results

You have defined a port for outbound communication.

2.1.4.4.2.4 Define Outbound Messages for Partner Systems

As administrator, you define outbound messages for partner systems in SAP S/4HANA or SAP ERP to enable
data transfer to SAP Digital Manufacturing for execution using the Data Replication Framework (DRF).

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

To set up the Data Replication Framework (DRF) to enable data transfer from SAP S/4HANA or SAP ERP to
SAP Digital Manufacturing for execution, you navigate to the Partner Profiles and assign the logical system
representing SAP Digital Manufacturing for execution to the SAP Digital Manufacturing for execution system.
Moreover, you define outbound message types for the transfer of data from SAP S/4HANA or SAP ERP to SAP
Digital Manufacturing for execution through a synchronized RFC.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 41
Procedure

1. In transaction WE20, choose Partner Type LS.

2. Choose  to create a new logical partner system.
3. In Partner No., enter the logical system representing SAP Digital Manufacturing for execution that you have
created under Create Logical Systems [page 38] . Enter US in Ty., <SAP ERP user> in Agent, and EN in
Lang.
4. In the Outbound table, choose Create outbound parameter.
5. On the Partner Profiles: Outbound Parameters screen, select Pass IDoc Immediately and Cancel Processing
After Syntax Error, and enter data in the following fields:

Field Value

Message Type BOMMAT

Receiver port HCI_DME

Pack. Size 1

Basic type BOMMAT05

 Note

HCI_DME ist just a placeholder. You can define the receiver port's name as you please, but make sure
that all message types defined here have the same receiver port name.

6. Repeat steps 3 and 4 to add the following parameters:

Message Type Receiver Port Basic Type

INVCON HCI_DME INVCON03

LOIPRO HCI_DME LOIPRO05 (production order and

process order)

LOIPLO HCI_DME LOIPLO02 (planned order)

LOIROU HCI_DME LOIROU04

LOIWCS HCI_DME LOIWCS03

MATMAS HCI_DME MATMAS03

SAP Digital Manufacturing Integration Guide

42 PUBLIC SAP Digital Manufacturing for execution Integration
 Message Type Receiver Port Basic Type

EQUIPMENT_CREATE HCI_DME EQUIPMENT_CREATE02

 Note
For more information, see Tool In­
tegration [page 145].

 Note

For more information on the supported IDoc versions, see 0003050090 .

For more information on how to enable LOIPRO05 version 2, see 3115603 .

Results

You have enabled the data transfer from SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for
execution.

2.1.4.4.2.5 Define a Distribution Model

As administrator, you need to define a distribution model in SAP S/4HANA or SAP ERP when setting up
the Data Replication Framework (DRF) to control the data transfer between your system and SAP Digital
Manufacturing for execution.

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

To control the data transfer from SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for execution via the
Data Replication Framework (DRF), you need to define a distribution model in SAP S/4HANA or SAP ERP. The
distribution model defines which message types can be sent to SAP Digital Manufacturing for execution. The
distribution model does not define in which business context a message should be sent because we're still on
the ALE level where the technical settings are defined that are required to make the communication happen.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 43
Procedure

1. Use transaction BD64.

2. On the Display Distribution Model screen, choose Switch Between Display and Edit Mode.
3. Choose Create Model View and enter data in the following fields:

Field Example Description

Short Text DMEModel The name of the model

Technical Name DMEModel The technical name of the model

Start Date The current date

End Date 31.12.9999

4. Choose the model view you created in the Model Views list and then choose Add Message Type. Make the
following entries:

Field Example Description

Model View DEMMODEL Technical

Sender S4HCLNT100 Your sending logical system.

Receiver DMETest Your receiving logical system. For

more information, see Create Logical
Systems [page 38].

Message Type BOMMAT

5. Choose Continue.
6. Repeat steps 4 and 5 to add the following message types:

Message Type Description

INVCON Inventory controlling

LOIPRO Production / process order

LOIPLO Planned order

LOIROU Routing

LOIWCS Work center

MATMAS Material master

SAP Digital Manufacturing Integration Guide

44 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

To add message type EQUIPMENT_CREATE, in step d, select the model view you created and choose
Add BAPI instead of Add Message Type. Enter the values described in step d for Model View, Sender /
Client and Receiver / Server. Select Equipment in Objcct / Interface and Create in Method.

7. Choose Save.

Results

You have defined a distribution model.

2.1.4.4.3 Set Up Data Replication Framework

2.1.4.4.3.1 Assign Business Objects to Your Business System

As administrator, you assign business objects in SAP S/4HANA or SAP ERP (business system) to SAP Digital
Manufacturing for execution to exchange data using the Data Replication Framework (DRF).

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

To transfer data from SAP S/4HANA or SAP ERP (business system) to SAP Digital Manufacturing for execution
using a replication model within the Data Replication Framework (DRF), you need to assign your business
system to a logical system and an RFC destination. Moreover, you need to add business objects to your
business system, so that you can control the distribution of business objects using a replication model within
the DRF.

Procedure

1. Use the DRFIMG transaction and choose Define Custom Settings for Data Replication Define Technical
Settings Define Technical Settings for Business Systems .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 45
2. On the Change View "Define Business Systems": Overview screen, choose New Entries.

If you don't use the System Landscape Directory (SLD), an error message may be displayed because the
business system can't be fetched from SLD. In this case, enter your logical system manually and ignore the
error message for manual entry. Press Enter to save your entry.
3. On the New Entries: Overview of Added Entries screen, choose Unicode, and enter data in the following
fields to create a business system:

Field Value

Business System DMESystem

Logical System DMETest (For more information, see Create Logical Sys­
tems [page 38])

RFC Destination DME_INT (For more information, see Build HTTP Con­
nection [page 31])

4. Choose Save.
5. Choose the business system DMESystem you created and double-click Define Bus.System, BO in Dialog
Structure on the side menu.
6. Choose New Entries and add the following business object types:

Field Value Description

BO Type 97 Production Order

BO Type 92 Planned Order

BO Type 194 Material

BO Type 223 Production Bill of

Operations

BO Type 493 Work Center

BO Type 467 Goods Movement

BO Type 183 Individual Material

7. Choose Save.

Results

You have assigned your business system to SAP Digital Manufacturing for execution.

SAP Digital Manufacturing Integration Guide

46 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.4.3.2 Define Filter Criteria

As administrator, you define filter criteria for the Data Replication Framework (DRF) to control the distribution
of business objects from SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for execution.

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

When you set up the Data Replication Framework (DRF) to enable the transfer of data from SAP S/4HANA
or SAP ERP to SAP Digital Manufacturing for execution, you can define filter criteria for business objects (for
example, production order or material) that belong to a replication model. With these filter criteria, you control
the distribution of business objects to SAP Digital Manufacturing for execution. For example, you can use plant,
order type, or material as criteria to transfer all production orders belonging to a specific plant, specific order
type, or specific material.

 Note

In this procedure, the values in the value help depend on the Customizing settings. For different
parameters, define the DRF Customizing settings accordingly.

Procedure

1. Log on to the SAP S/4HANA or SAP ERP system as an Administrator.

2. Access the activity using one of the following navigation options:

Option Description

Transaction code DRFF

Initial screen of the SAP SAP Menu Cross Application Components Processes and Tools for Enterprise
system Applications Master Data Governance Data Replication Define Filter Criteria

Replication

3. On the Define Filter Criteria screen, select the Goods Movement line of the relevant SAP Digital
Manufacturing replication model and choose Create.

The Create Filter Criteria screen is displayed.

4. On the Create Filter Criteria screen, make the following entries in the Filter Criteria to Include Business
Objects area:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 47
 1st Column 2nd Column 3rd Column Note

Plant is <Plant number>, for ex­ Choose  to create a sec­

ample, 1010 ond line.

Movement type is 311

5. Choose Save.
6. Choose Close.
7. Repeat steps 3 to 6 for the following business objects of the replication model and make the corresponding
entries:
a. Production Order:

1st Column 2nd Column 3rd Column

Plant is <Plant number>, for example,

1010

b. Planned Order:

1st Column 2nd Column 3rd Column

Production Plant is <Plant number>, for example,

1010

c. Product:

1st Column 2nd Column 3rd Column

Plant is <Plant number>, for example,

1010

d. Production Bill of Operations:

1st Column 2nd Column 3rd Column

Plant is <Plant number>, for example,

1010

e. Workcenter:

1st Column 2nd Column 3rd Column

Plant is <Plant number>, for example,

1010

SAP Digital Manufacturing Integration Guide

48 PUBLIC SAP Digital Manufacturing for execution Integration
Results

You have successfully created the filter criteria for the various objects.

2.1.4.4.3.3 Define Replication Models and Outbound

Implementations

As administrator, you define replication models and outbound implementations to control the data transfer
from SAP S/4HANA or SAP ERP to SAP Digital Manufacturing for execution using the Data Replication
Framework (DRF).

Prerequisites

You have the Administrator role for SAP S/4HANA or SAP ERP.

Context

You define replication models and outbound implementations in SAP S/4HANA or SAP ERP to control the
transfer of business objects from your system to SAP Digital Manufacturing for execution using the Data
Replication Framework (DRF).

Procedure

1. Use transaction SPRO and choose SAP Reference IMG.

2. Choose Cross-Application Components Processes and Tools for Enterprise Applications Master Data
Governance Central Governance General Settings Data Replication Define Custom Settings for Data
Replication Define Replication Models .
3. Choose New Entries and complete the following fields:

Field Example

Replication Model DMEModel

Description DMEModel

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 49
 Field Example

Log Days 10

4. Choose Save.
5. Choose the replication model you created and double-click Assign Outbound Implementation in Dialog
Structure on the side menu.
6. Choose New Entries and add the following outbound implementations:

Field Value Description

Outbound Implementation 97_1 Production Order IDoc

Outbound Implementation 92_1 Planned Order (Repetitive Manufac­

turing) via IDoc

Outbound Implementation 194_1 Material via IDoc (ME - enhanced Fil­

ter Object)

Outbound Implementation 223_1 Routing via IDoc (ME)

Outbound Implementation 467_1 Goods Movement via IDoc

Outbound Implementation 493_1 Workcenter via IDoc

Outbound Implementation 183_1 Equipment via IDoc (ME)

 Note

For more information on the supported IDoc versions, see 0003050090 .

7. Choose Save.
8. Choose the outbound implementation 97_1 and double-click Assign Target Systems for Repl. Model /
Outb.Impl in Dialog Structure on the side menu.
9. Choose New Entries to add the business system.
10. Repeat steps 8 and 9 to add the business system for other outbound implementations that you have
created.
11. Choose Save.
12. Double-click Define Replication Model in Dialog Structure on the side menu, choose the replication model
and then choose Activate.

Results

You've defined and activated a replication model with its outbound implementations.

SAP Digital Manufacturing Integration Guide

50 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.5 Prepare Credentials for Initial Parameter
Deployment

For the deployment of the Initial Parameters integration flow, you can choose between basic
authentication with P-User or OAUTH 2.0 authentication with authorization code.

Use

To make sure that all integration flows in SAP Cloud Integration can use all the integration parameters, you
must enable SAP Cloud Integration to write initial parameters to SAP Cloud Integration. For this deployment of
parameters, you create a security material in SAP Cloud Integration. With regards to authentication, you have
two options:

• Basic authentication with your P-user and password

• OAUTH 2.0 authorization code authentication based on a service key with grant type authorization code
(Recommended)

In a later step, this security material is needed to configure the Initial Parameters iFlow in SAP Cloud
Integration.

To prepare the credentials for initial parameter deployment, follow one of the two approaches:

• Basic Authentication with P-User for Initial Parameter Deployment (Neo and Cloud Foundry) [page 51]
• OAuth 2.0 Authentication with Authorization Code for Initial Parameter Deployment (Cloud Foundry) [page
60]
• OAuth 2.0 Authentication with Authorization Code for Initial Parameter Deployment (Neo) [page 56]

2.1.4.5.1 Basic Authentication with P-User for Initial

Parameter Deployment (Neo and Cloud Foundry)

Create a security material based on your P-user in SAP Cloud Integration. This material is needed to write initial
parameters to SAP Cloud Integration in Neo or Cloud Foundry environment.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've got a P-user ID and have granted it access to SAP Cloud Integration. For more information, see
Granting Your P-User Access to SAP Cloud Integration in Neo Environment [page 53]or Granting Your
P-User Access to SAP Cloud Integration in Cloud Foundry Environment [page 54].

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 51
 to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage My Account app. Under Accounts, you find your users.

Context

You need to create a security material based on your P-user and password in SAP Cloud Integration. You'll
use this security material, called here PD_DEPLOYER_USER, later when configuring the Initial Parameters
integration flow in SAP Cloud Integration. The PD_DEPLOYER_USER security material is needed to ensure that
SAP Cloud Integration can write the integration parameters to SAP Cloud Integration, so that all iFlows can
access them.

Procedure

1. Log on to SAP Cloud Integration and choose Monitor.

2. Choose the Security Material app.
3. Choose Create, and select User Credentials for basic authentication.
4. Complete the following fields:

Field PD_DEPLOYER_USER with P-user and password

Name PD_DEPLOYER_USER

 Note
You can choose a random name, but you need to use
this name later for the Tenant Credentials in the Initial
Parameters iFlow.

User P-user ID

Password P-user password

5. Choose Deploy.

Results

You've created a security material for basic authentication.

SAP Digital Manufacturing Integration Guide

52 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.5.1.1 Granting Your P-User Access to SAP Cloud
Integration in Neo Environment

Learn how to authorize your P-user for SAP Cloud Integration in Neo environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount.

• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Overview, choose Members.
3. Choose Add Members.
4. In the User IDs field, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predefined role) and Developer (predefined role).
6. Choose Add Members.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 53
7. Choose Security Authorizations .
8. On the Users tab, enter your P-user ID and choose Show Assignments.
9. Choose Assign in the area for individual assignment, not group assignment.

The Assign Roles to User popup opens.

10. Go through the available subaccounts and applications to assign the following roles and save them:

ESBMessaging.send

AuthGroup.BusinessExpert

AuthGroup.Administrator

AuthGroup.IntegrationDeveloper

Results

Your P-user has now access to SAP Cloud Integration.

2.1.4.5.1.2 Granting Your P-User Access to SAP Cloud

Integration in Cloud Foundry Environment

Learn how to authorize your P-user for SAP Cloud Integration in Cloud Foundry environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount in SAP BTP cockpit.
• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on

SAP Digital Manufacturing Integration Guide

54 PUBLIC SAP Digital Manufacturing for execution Integration
 to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Security Users , choose Create.

3. Under User Name, enter the e-mail address belonging to your P-user.
4. Choose Default Identity Provider.
5. Choose Create.

6. Choose Security Role Collections .

7. Choose  .
8. Give your collection a name, for example My_RoleCollection, and choose Create.
9. Select your collection and choose Edit.
10. On the Roles tab, under Role Name, choose  and add the following roles to your collection:

MessagingSend

MessagePayloadsRead

AuthGroup_BusinessExpert

If you want to use the CPI Async Mode, there a some additional roles required. For more information, see
Asynchronous Connection to SAP Cloud Integration [page 109].

11. Under Security Users , choose your user.

12. In the detail view, choose Assign Role Collection to make the following assignments:

My_RoleCollection

PI_Integration_Developer (predefined)

PI_Administrator (predefined)

Results

Your P-user has now access to SAP Cloud Integration.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 55
2.1.4.5.2 OAuth 2.0 Authentication with Authorization
Code for Initial Parameter Deployment (Neo)

Use OAuth 2.0 authentication with authorization code for the deployment of initial parameters in SAP Cloud
Integration.

Overview

To make sure that all integration flows in SAP Cloud Integration can use all the integration parameters, you
must enable SAP Cloud Integration to write initial parameters to SAP Cloud Integration. For this deployment
of parameters, you create a client with authorization code in the SAP Cloud Integration subaccount in
SAP BTP cockpit (Neo environment). You then create a security material in SAP Cloud Integration, called
PD_DEPLOYER_CLIENT. In a later step, this material is needed to configure the Initial Parameters iFlow in SAP
Cloud Integration, so that all integration flows can access all integration parameters.

Overview Setup Steps

To create the PD_DEPLOYER_CLIENT security material, perform the tasks described in the following topics:

1. Create a Client with Authorization Code [page 56]

2. Create a Security Material with OAuth 2.0 Authorization Code in SAP Cloud Integration [page 58]

2.1.4.5.2.1 Create a Client with Authorization Code

To enable authentication without user and password, you need to create a client with authorization code grant
type in your SAP BTP cockpit (Neo Environment) .

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Cloud Integration subaccount in SAP BTP cockpit (Neo Environment).

Context

To enable authentication without user and password for the SAP Cloud Integration to SAP Cloud Integration
communication, you need to create a client with authorization code grant type in your SAP Cloud Integration
subaccount (Neo Environment).

SAP Digital Manufacturing Integration Guide

56 PUBLIC SAP Digital Manufacturing for execution Integration
Procedure

1. In SAP BTP cockpit, go to your SAP Cloud Integration subaccount.

2. Go to Security OAuth Clients and choose Register New Client.

The client creation menu opens.

3. Enter the following fields to create client:

Field

Name Client name

 Note
You can choose a random name, for example
OAuth_Client.

Subscription Choose the subscription ending with tmn.

ID The Client ID is generated automatically by the system,

but you can choose Regenerate ID, if needed.

 Note
You need the Client ID later when configuring the au­
thorizations.

Authorization Grant Authorization Code

Confidential Do not check this field.

Skip Consent Screen Do not check this field.

Redirect URI Application URL of SAP Integration

Cloud

 Note

To find it, go to Applications Subscriptions

and choose the Application ending with tmn. Add /
itspaces/odata/api/v1/OAuthTokenFromCode
to this URI. You can also find the full Redirect URI
when creating a security material with OAuth2 author­
ization code.

 Example

https://
{…}tmn.hci.eu1.hana.ondemand.com/itspaces/
odata/api/v1/OAuthTokenFromCode.

Token Lifetime 1 hours

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 57
 Field

Refresh Token Lifetime 1 hours

4. Go to Security Authorizations Users and enter a user name according to this format:
clientName_{client ID}, for example OAuth_Client_123456-a123-a123-a123-a123445678.
5. Choose Show Assignments.
6. In the Roles area, choose Assign.
7. Enter the following fields:

Field

Subaccount Choose the subaccount which the application ending with

tmn is in.

Application Choose the application ending with tmn.

Role AuthGroup.TenantPartnerDirectoryConfigurator

8. Choose Save.

Results

You've created a client with OAUTH 2.0 authentication with authorization code grant type.

2.1.4.5.2.2 Create a Security Material with OAuth 2.0

Authorization Code in SAP Cloud Integration

Create a security material with OAuth 2.0 authorization code in SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've created a client with OAuth 2.0 authorization code in your SAP Cloud Integration subaccount in SAP
BTP cockpit (Neo environment). For more information, see Create a Client with Authorization Code [page
56].

Context

You've created a client with OAuth 2.0 authorization code in your SAP Cloud Integration subaccount (Neo
environment). Now you create and activate a security material based on authentication information found in

SAP Digital Manufacturing Integration Guide

58 PUBLIC SAP Digital Manufacturing for execution Integration
the client. The security material, called here PD_DEPLOYER_CLIENT, is needed later to configure the Initial
Parameters integration flow in SAP Cloud Integration. The PD_DEPLOYER_CLIENT security material is needed
to ensure that SAP Cloud Integration can write the integration parameters to SAP Cloud Integration, so that all
iFlows can access them.

Procedure

1. In SAP Cloud Integration, go to the Monitor section and choose the Security Material app.
2. Choose Create and then OAuth2 Authorization Code.

The Create OAuth2 Authorization Code popup opens.

3. Enter the following fields:

Field

Name PD_DEPLOYER_Client

 Note
You can choose a random name, but you need to use
this name later for the Tenant Credentials in the Initial
Parameters iFlow.

Provider Generic

Authorization URL You'll find the Authorization URL endpoint in your

SAP Cloud Integration subaccount, under Security
OAUTH Branding , for example https://
{…}hana.ondemand.com/oauth2/api/v1/authorize

Token Service URL You'll find the Token Service URL endpoint in your
SAP Cloud Integration subaccount, under Security
OAUTH Branding , for example https://
{…}hana.ondemand.com/oauth2/api/v1/token

Client ID Client ID, which was generated in your SAP

Cloud Integration subaccount, for example 123456-
a123-a123-a123-a123445678

For more information, see Create a Client with Authoriza­

tion Code [page 56].

Client Secret This field is mandatory but you can put in a random value.

Send as Body Parameter

4. Choose Deploy.

Your security material has been created and has status Unauthorized.
5. Authorise your security material by choosing  and Authorize.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 59
Results

You've created and authorized a security material with OAuth 2.0 authorization code.

2.1.4.5.3 OAuth 2.0 Authentication with Authorization

Code for Initial Parameter Deployment (Cloud
Foundry)

Use OAuth 2.0 authentication with authorization code for the deployment of initial parameters in SAP Cloud
Integration.

Use

To make sure that all integration flows in SAP Cloud Integration can use all the integration parameters,
you must enable SAP Cloud Integration to write initial parameters to SAP Cloud Integration. For this
deployment of parameters, you create a service instance in the SAP Cloud Integration subaccount in SAP
BTP cockpit (Cloud Foundry environment). Then you create a service key for this instance, which is of grant
type authorization code. With this key, you then create a security material in SAP Cloud Integration, called
PD_DEPLOYER_CLIENT. In a later step, this material is needed to configure the Initial Parameters iFlow in SAP
Cloud Integration, so that all integration flows can access all integration parameters.

Overview Setup Steps

To create the PD_DEPLOYER_CLIENT security material, perform the tasks described in the following topics:

1. Create a Service Instance and Key with Authorization Code [page 61]
2. Create a Security Material with OAuth 2.0 Authorization Code in SAP Cloud Integration [page 63]

SAP Digital Manufacturing Integration Guide

60 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.5.3.1 Create a Service Instance and Key with
Authorization Code

To enable authentication without user and password, you need to create a service instance and a service key
with authoriziation code grant type.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got the Administrator role for SAP Cloud Integration.
• You've got access to the SAP Cloud Integration subaccount in SAP BTP cockpit (Cloud Foundry
environment).

Context

To enable authentication without user and password for the SAP Cloud Integration to SAP Cloud Integration
communication, you need to create a service instance and a service key with authoriziation code grant type.

Procedure

1. In SAP BTP cockpit, go to your SAP Cloud Integration subaccount.

2. Go to Services Instances and Subscriptions and choose Create.

The New Instance or Subscription popup opens.

3. Enter the following fields to create a service instance:

Field

Service Process Integration Runtime

Plan api

Space Name of your space

Instance Name Instance Name

 Note
You can choose a random name.

4. Choose Next and enter the following fields:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 61
 Field

Configure instance paramters Form

Roles AuthGroup_TenantPartnerDirectoryConfigurator

Grant-types Authorization Code

Redirect-urls

5. Choose Next and Create.

6. Under Instances, choose the instance that you've just created.
7. On the Service Key tab, choose Create.

The New Service Key popup opens.

8. Enter the following fields:

Field

Service Key Name Service Key

 Note
You can choose a random name.

Configure Binding Parameters Form

Key Type Clientid/Secret

9. Choose Create.

 Note

You can access the service key content by choosing  and then View.

Results

You've created a service instance and a service key with authorization code grant type.

SAP Digital Manufacturing Integration Guide

62 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.5.3.2 Create a Security Material with OAuth 2.0
Authorization Code in SAP Cloud Integration

Create a security material with OAuth 2.0 authorization code in SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've created a service instance and a service key with OAuth 2.0 authorization code in your SAP Cloud
Integration subaccount in SAP BTP cockpit (Cloud Foundry environment). For more information, see
Create a Service Instance and Key with Authorization Code [page 61].

Context

You've created a service key with OAuth 2.0 authorization code in your SAP Cloud Integration subaccount. Now
you create and activate a security material based on authentication information found in this service key in SAP
Cloud Integration. The security material, called here PD_DEPLOYER_CLIENT, is needed later to configure the
Initial Parameters integration flow in SAP Cloud Integration. The PD_DEPLOYER_CLIENT security material is
needed to ensure that SAP Cloud Integration can write the integration parameters to SAP Cloud Integration, so
that all iFlows can access them.

Procedure

1. In SAP Cloud Integration, go to the Monitor section and choose the Security Material app.
2. Choose Create and then OAuth2 Authorization Code.

The Create OAuth2 Authorization Code popup opens.

3. Enter the following fiels:

Field

Name PD_DEPLOYER_Client

 Note
You can choose a random name, but you need to use
this name later for the Tenant Credentials in the Initial
Parameters iFlow.

Provider Generic

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 63
 Field

Authorization URL Authorization URL to be found in

service key

To be found in the service key created in SAP Cloud

Integration subaccount. For more information, see Create
a Service Instance and Key with Authorization Code [page
61].

Token Service URL Token service URL to be found in

service key

To be found in the service key created in SAP Cloud

Integration subaccount.

Client ID Client ID to be found in service key

To be found in the service key created in SAP Cloud

Integration subaccount.

Client Secret Client secret to be found in service

key

To be found in the service key created in SAP Cloud

Integration subaccount.

Send as Body Parameter

4. Choose Deploy.
5. Activate your security material by choosing  and Activate.

Results

You've created and activated a security material with OAuth 2.0 authorization code.

2.1.4.6 Connect SAP Cloud Integration to SAP Digital

Manufacturing

Connect SAP Cloud Integration to SAP Digital Manufacturing using iFlows.

Use

The communication from SAP Cloud Integration to SAP Digital Manufacturing is based on predefined
integration flows (iFlow) that control the data transfer between both partner systems. These iFlows are
contained in packages, such as the SAP S/4HANA Integration with SAP Digital Manufacturing package, and
are configured in SAP Cloud Integration.

SAP Digital Manufacturing Integration Guide

64 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

It's recommended to deploy all iFlows contained in the SAP S/4HANA Integration with SAP Digital
Manufacturing package. For more information on the required artifacts for all integration message types,
see 3050090 .

Overview of the Procedure

To enable this iFlow-based communication between your systems, you've to perform the following tasks:

1. Prepare the credentials for the initial parameter deployment. For more information, see Prepare
Credentials for Initial Parameter Deployment [page 51].
2. Set up one of the two authorization methods:
1. OAUTH 2.0 client credential authorization. For more information, see Connection with OAuth 2.0 Client
Credential Authorization [page 65].
2. OAUTH 2.0 client certificate authorization (x.509). For more information, see Connection with Client
Certificate Authorization (X.509) [page 75].

2.1.4.6.1 Connection with OAuth 2.0 Client Credential

Authorization

Set up an OAuth 2.0 client credential (client ID / client secret) connection from SAP Cloud Integration to SAP
Digital Manufacturing.

Use

By enabling OAuth 2.0 client credential authentification for the communication from SAP Cloud Integration to
SAP Digital Manufacturing, you benefit from the fact that you don't need a user and a password anymore.

Overview

To set up OAuth 2.0 client credential authentication from SAP Cloud Integration to SAP Digital Manufacturing,
you need to create a service instance with a service key that supports OAuth 2.0 client credential authorization
(client ID / client secret) in your SAP Digital Manufacturing subaccount. Then you create a security material
that uses the authentication information found in the service key. As last step, you configure the relevant
integration flow package in SAP Cloud Integration.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 65
  Note

If you're already using client credential authorization, you can switch over from client credential
authorization to OAuth 2.0 client certificate authorization (x.509). For more information about this
procedure and on how to switch to the INBOUND_PROCESSOR iFlow, see 3231128 .

Step Overview

To set up security parameters with authorization code, perform the tasks described in the following topics:

1. Create a Service Instance and Service Key in SAP Digital Manufacturing Subaccount [page 66]
2. Create an OAuth 2.0 Client Credential Security Material [page 68]
3. Configure Inbound Processor iFlow [page 69]
4. Configure Initial Parameters iFlow [page 71]

2.1.4.6.1.1 Create a Service Instance and Service Key in SAP

Digital Manufacturing Subaccount

Create a service instance and a service key supporting OAUTH 2.0 client credential authentication (client ID /
client secret) in your SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Context

To enable OAUTH 2.0 client credential authentication from SAP Cloud Integration to SAP Digital
Manufacturing, you need to create a service instance and a service key supporting OAUTH 2.0 client credential
authentication (client ID / client secret) in your SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Go to Services Instances and Subscriptions and choose Create.

SAP Digital Manufacturing Integration Guide

66 PUBLIC SAP Digital Manufacturing for execution Integration
 The New Instance or Subscription popup opens.
3. Enter the following fields to create a service instance:

Field

Service SAP Digital Manufacturing Cloud Services

Plan execution

Runtime Environment Cloud Foundry

Space Name of your space

4. Choose Next and leave the Parameters popup empty.

5. Choose Next and Create.
6. Under Instances, choose the instance that you've just created.
7. On the Service Keys tab, choose Create.

The New Service Key popup opens.

8. Enter the following fields to create a service key supporting client ID / client secret:

Field

Service Key Name Service Key

 Note
You can choose a random name.

9. Choose Create.

 Note

You can access the service key content by choosing  and then View.

Results

You've created a service instance and a service key supporting OAuth 2.0 client credential authentication.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 67
2.1.4.6.1.2 Create an OAuth 2.0 Client Credential Security
Material

Create a security material named CF_AUTH in SAP Cloud Integration that you need for the configuration of the
integration flow.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've created a service instance and a service key supporting OAuth 2.0 client credential authorization
in your SAP Digital Manufacturing subaccount in SAP BTP cockpit. For more information, see Create a
Service Instance and Service Key in SAP Digital Manufacturing Subaccount [page 66].

Context

You need to create a security material supporting OAuth 2.0 client credentials, called for example CF_AUTH, in
SAP Cloud Integration that enables SAP Cloud Integration to send requests to SAP Digital Manufacturing. In a
later step, you'll use this security material to configure the INBOUND_PROCESSOR integration flow in SAP Cloud
Integration.

Procedure

1. Log on to SAP Cloud Integration and choose Monitor.

2. Choose the Security Material app.
3. Choose Create, and select User Credentials.

The Create User Credentials popup opens.

4. Complete the following fields:

Field CF_AUTH

Name CF_AUTH

You can choose a random name, but you need to

use this name later for the DMC_Credentials in the
INBOUND_PROCESSOR iFlow.

Type User Credentials

SAP Digital Manufacturing Integration Guide

68 PUBLIC SAP Digital Manufacturing for execution Integration
 Field CF_AUTH

User <clientid of service key>

To be found in SAP Digital Manufacturing subaccount. For

more information, see Create a Service Instance and Serv­
ice Key in SAP Digital Manufacturing Subaccount [page
66].

Password <clientsecret of service key>

To be found in SAP Digital Manufacturing subaccount.

 Note

Here's how to find the <clientid of Service Key> and the <clientsecret of Service Key>:
In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount. Go to Services Instances
and Subscriptions. In the Instances tab, choose the key in the Credentials column. You find the
<clientid of Service Key> and the <clientsecret of Service Key> in the JSON box of
the Credentials popup.

5. Choose Deploy.

Results

You've created a security material.

2.1.4.6.1.3 Configure Inbound Processor iFlow

You configure the INBOUND PROCESSOR iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAuth 2.0 client credential authorization.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• The INBOUND PROCESSOR integration workflow is available in your SAP S/4HANA Integration with SAP
Digital Manufacturing package in SAP Cloud Integration. If not, an update of your package is required. For
more information, see Upgrade Information [page 231].
• You've created a security material supporting OAuth 2.0 client credential authorization. For more
information, see Create an OAuth 2.0 Client Credential Security Material [page 68].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 69
Context

In this step, you configure the INBOUND PROCESSSOR integration flow SAP Cloud Integration. To connect SAP
Cloud Integration to SAP Digital Manufacturing, you enter the name of the security material that gives access
to SAP Digital Manufacturing, called here CF_AUTH, into the DMC_CREDENTIAL field. Moreover, you leave the
DMC_PRIVATE_KEY_ALIAS field empty to use the OAUTH 2.0 client credential authorization.

After you've deployed the INBOUND PROCESSOR iFlow, you must activate it by setting a parameter to TRUE
in the Initial Parameters iFlow in SAP Cloud Integration. Without this configuration step, the INBOUND
PROCESSOR iFlow won't be activated.

 Note

If you're already using client credential authorization, you can switch over from client credential
authorization to OAUTH 2.0 client certificate authorization (x.509). For more information about this
procedure and on how to switch to the INBOUND PROCESSOR iFlow, see 3231128 .

 Note

For planned orders integration, you need to use the INBOUND PROCESSOR integration workflow.

Procedure

1. In SAP Cloud Integration, go to the Design section.

2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. In the Artifacts tab, search for the INBOUND PROCESSOR integration workflow and choose  , then
Configure.

The Configure "INBOUND PROCESSOR" popup opens.

4. Enter the following parameters:

Parameter Value

DMC_API_URL public-api-endpoint
To be found in the service key in SAP Digital
Manufacturing subaccount. For example:

• https://api.eu10.dmc.cloud.sap (pro­
duction system)

• https://api.test.eu10.dmc.cloud.sap
(quality system)

For more information, see Create a Service Instance and

Service Key in SAP Digital Manufacturing Subaccount
[page 66].

DMC_CREDENTIAL CF_AUTH

SAP Digital Manufacturing Integration Guide

70 PUBLIC SAP Digital Manufacturing for execution Integration
 Parameter Value

The name of the security material that you've created. For

more information, see Create an OAuth 2.0 Client Creden­
tial Security Material [page 68].

DMC_PRIVATE_KEY_ALIAS Leave this field empty.

DMC_TOKEN_URL Enter the <URL of Service Key>/oauth/token,

taken from the service key in your SAP Digital
Manufacturing subaccount, for example https://
<...>.authentication.eu10.hana.ondemand.com/
oauth/token.

For more information, see Create a Service Instance and

Service Key in SAP Digital Manufacturing Subaccount
[page 66].

ENDPOINT_ID 00

5. Choose Save.
6. To deploy the INBOUND PROCESSOR integration workflow, choose  , then Deploy.

Results

You've configured and deployed the INBOUND PROCESSOR iflow.

2.1.4.6.1.4 Configure Initial Parameters iFlow

You configure the Initial Parameters iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAuth 2.0 client credential authorization.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've created a security material for initial parameter deployment. For more information, see Prepare
Credentials for Initial Parameter Deployment [page 51].
• You've configured the INBOUND PROCESSOR integration workflow. For more information, see Configure
Inbound Processor iFlow [page 69].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 71
Context

With this procedure, you configure the Initial Parameters integration flow in SAP Cloud Integration.
To enable SAP Cloud Integration to write parameters to SAP Cloud Integration, so that all integration flows
can access them, you enter the credential that you've prepared for your initial parameter deployment,
for example PD_DEPLOYER_USER or PD_DEPLOYER_CLIENT, under TENANT_CREDENTIALS. Then you set
ENABLE_INBOUND_OAUTH to TRUE to activate the INBOUND PROCESSOR integration flow. The first three
parameters at the top of the table below are then ignored.

Procedure

1. In SAP Cloud Integration, go to the Design section.

2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. In the Artifacts tab, search for the Initial Parameters integration workflow and choose  , then Configure.

The Configure "Initial Parameters" popup opens.

4. Enter the following parameters:

Parameter Name Description Value

COMMON_DME_IDENTITY_ZONE_SUBD The subdomain that allows SAP Cloud Go to the subaccount in the SAP
OMAIN Integration to access web services of BTP cockpit that you use to sub­
SAP Digital Manufacturing. scribe to SAP Digital Manufacturing
for execution. You can find the subdo­
main in the General section.

COMMON_DME_INT_URL The URL of the back-end integration- Go to the subaccount in the SAP
ms application. BTP cockpit that you use to sub­
scribe to SAP Digital Manufacturing
for execution.

Choose Services Instances and

Subscriptions . Under Instances

display the service key for SAP
Digital Manufacturing Services. You
can find the URL under the
tag manufacturing-execution-
integration.

 Note
Remember to add the prefix
https:// to the URL.

SAP Digital Manufacturing Integration Guide

72 PUBLIC SAP Digital Manufacturing for execution Integration
 Parameter Name Description Value

COMMON_DME_SB_URL Service broker URL for token fetching. Go to the subaccount in the SAP
BTP cockpit that you use to sub­
scribe to SAP Digital Manufacturing
for execution.

Choose Services Instances and

Subscriptions . Under Instances dis­

play the service key for SAP Digital
Manufacturing Services. You can find
the URL under the tag uaa and then
url.

ENABLE_PLANT_CONVERSION Define if you want to enable plant Enter TRUE to enable this function.
conversion function to connect mul­ For more information, see Mapping
tiple ERP plants to SAP Digital Plants (Plant Conversion) [page 224].

Manufacturing.

PID - DME_Generic_Processing_00

TENANT_CREDENTIALS The SAP Cloud Integration user PD_DEPLOYER_USER or

credential created in the Security PD_DEPLOYER_CLIENT
Material app.
For more information, see Prepare
Credentials for Initial Parameter De­
ployment [page 51].

TENANT_URL SAP Cloud Integration management Use the SAP Cloud Integration man­
URL used for iFlow deployment. agement URL in the email you re­
ceived after successful SAP Cloud
Integration tenant provisioning. If you
haven't access to this mail, see How
to Get SAP Cloud Integration Manage­
ment URL [page 20].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 73
 Parameter Name Description Value

ENABLE_INBOUND_OAUTH Set ENABLE_INBOUND_OAUTH to TRUE

TRUE to use the INBOUND
PROCESSOR iflow, which is recom­
mended. If set to TRUE, the first three
parameters at the top of the table dis­
appear.

 Note
For planned orders integra­
tion, you need to set
ENABLE_INBOUND_OAUTH to
TRUE.

 Note
The default setting is FALSE.
This means that the INBOUND
PROCESSOR iFlow isn't called,
but integration works neverthe­
less using a lower OAuth security
level.

5. Choose Save.
6. To deploy the Initial Parameters integration workflow, choose  , then Deploy.

Results

You've configured and deployed the Initial Parameters iFlow.

SAP Digital Manufacturing Integration Guide

74 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.6.2 Connection with Client Certificate Authorization
(X.509)

Connect SAP Cloud Integration to SAP Digital Manufacturing using OAUTH 2.0 client certificate authentication
(X.509).

Use

You can make the data exchange from SAP Cloud Integration to SAP Digital Manufacturing more secure by
using an X.509 certificate.

General Overview of the Procedure

To enable OAUTH 2.0 client certificate authentication (X.509) from SAP Cloud Integration to SAP Digital
Manufacturing, you need to create a service key with credential type x.509 in your SAP Digital Manufacturing
subaccount and create an x.509 certificate that will enable secure communication between the systems. You
upload the x.509 certificate in SAP Digital Manufacturing and SAP Cloud Integration. In SAP Cloud Integration,
you then create a security material based on the authentication information found in the service key. In the
last two steps, you configure the INBOUND_PROCESSOR integration flow and the Initial Parameters in SAP
Cloud Integration.

Overview Setup Steps

To set up OAUTH 2.0 client certificate authentication (X.509) from SAP Digital Manufacturing to SAP Cloud
Integration, perform the tasks described in the following topics:

1. Before You Start [page 76]

2. Create an X.509 Service Key in SAP Digital Manufacturing [page 76]
3. Create an X.509 Certificate [page 77]
4. Create a Key Pair and Upload the X.509 Certificate File to SAP Cloud Integration [page 78]
5. Create a Security Material with User Credentials in SAP Cloud Integration [page 79]
6. Configure Inbound Processor iFlow [page 80]
7. Configure Initial Parameters iFlow [page 82]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 75
2.1.4.6.2.1 Before You Start

This page shows you the prerequisites that are required to connect SAP Cloud Integration to SAP Digital
Manufacturing using an x.509 certificate.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got the Administrator role for SAP Digital Manufacturing.
• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've got software to create certificate files of type .pfx, such as openSSL.

2.1.4.6.2.2 Create an X.509 Service Key in SAP Digital

Manufacturing

Create a service key that supports X.509 credentials in your SAP Digital Manufacturing subaccount.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Context

To set up communication from SAP Digital Manufacturing to SAP Cloud Integration or from SAP Cloud
Integration to SAP Digital Manufacturing using an X.509 certificate, you need to create a service key that
supports X.509 credentials in your SAP Digital Manufacturing subaccount.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Under Instances and Subscriptions, choose your SAP Digital Manufacturing instance.
3. In the Service Keys tab, choose Create to create a service key.
4. In the New Service Key popup, enter a Service Key Name of your choice.

SAP Digital Manufacturing Integration Guide

76 PUBLIC SAP Digital Manufacturing for execution Integration
5. Paste {"xsuaa":{"credential-type":"x509"}} as parameter into the JSON format field.

 Note

You can also specify the validity period, for example: {"credential-type": "x509","x509": {"validity":
4,"validity-type": "MONTHS"}. The default setting is 7 days. The maximum duration is 1 year.

Be aware that you need to create a new service key before the x.509 certificate of the current service
key expires.

6. Choose Create.

You've created a service key supporting X.509 credentials.

2.1.4.6.2.3 Create an X.509 Certificate

Create an X.509 certificate that's needed for X.509 certificate-based data transfer between SAP Digital
Manufacturing and SAP Cloud Integration.

Prerequisites

• You've the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've created a service key supporting OAUTH 2.0 client certificate authorization for your SAP Cloud
Integration instance. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing
[page 76].
• You've software to create certificate files of type .pfx, such as openSSL.

Context

To enable communication between SAP Digital Manufacturing and SAP Cloud Integration using X.509
credentials, you need to create an X.509 certificate based on information that can be found in the service
key.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Under Instances and Subscriptions, choose your SAP Cloud Integration instance.
3. Open the service key.
4. In the JSON box, go to the key field, which is under the "uaa" tag, and copy the content of the key field into
a new file of type .pem, for example key.pem, and save it.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 77
5. In the JSON box, go to the certificate field, which is under the "uaa" tag, and copy the content of the
certificate field into a new file of type .pem, for example certificate.pem, and save it.
6. Create a certificate file of type .pfx, for example service.pfx, combining key.pem and
certificate.pem, and assign a password to it.

If you're using OpenSSL to create the .pfx file, use this command: openssl pkcs12 -export -out
service.pfx -in key key.pem -in certificate.pem.

2.1.4.6.2.4 Create a Key Pair and Upload the X.509

Certificate File to SAP Cloud Integration

Create a key pair in SAP Cloud Integration and upload the X.509 certificate file to SAP Cloud Integration to
enable data transfer from SAP Digital Manufacturing to SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've got an X.509 certificate with a password. For more information, see Create an X.509 Certificate
[page 77].

Context

To set up communication from SAP Digital Manufacturing to SAP Cloud Integration or from SAP Cloud
Integration to SAP Digital Manufacturing using an X.509 certificate, you need to create a key pair in SAP
Cloud Integration and upload the X.509 certificate into the system. Then you need to download the certificate
to your computer to use it later in the integration process.

Procedure

1. In SAP Cloud Integration, go to Operate and monitor integration scenarios and choose the Keystore tile.
2. Choose Add.
3. Choose Key Pair.
4. In the Add Key Pair popup, enter an Alias for the key pair, for example DMC_KEY_PAIR. You can choose a
random name.
5. Upload the .pfx file, for example service.pfx, by using the Browse function.
6. Enter the password that you've defined for the .pfx file.
7. Choose Add.

SAP Digital Manufacturing Integration Guide

78 PUBLIC SAP Digital Manufacturing for execution Integration
8. Right-click the newly created key pair and choose Download Certificate.

A certificate of type .cer has been created, for example dmc_service.cer, and downloaded to your
computer. You need it for the next step.

2.1.4.6.2.5 Create a Security Material with User Credentials

in SAP Cloud Integration

Create a security material with OAuth authorization code in SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've created a service instance and a service key that supports client credentials with x.509 certificate
in your SAP Digital Manufacturing. For more information, see Create an X.509 Service Key in SAP Digital
Manufacturing [page 76].

Context

You've created a service key that supports client credentials with x.509 certificate in your SAP Digital
Manufacturing in your SAP Digital Manufacturing subaccount. Now you create and activate a security material
with client credentials based on authentication information found in the service key.

Procedure

1. In SAP Cloud Integration, go to the Monitor section and choose the Security Material app.
2. Choose Create and then User Credentials.

The Create User Credentials popup opens.

3. Enter the following fiels:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 79
 Field

Name CF_AUTH

 Note
You can choose a random nam, but you need to
use this name later for the DMC_Credentials in
INBOUND_PROCESSOR iFlow.

Type User Credentials

User Client ID

To be found in the service key of the service instance in

your SAP Digital Manufacturing subaccount. For more in­
formation, see Create an X.509 Service Key in SAP Digital
Manufacturing [page 76].

Password Leave this field empty

Repeat Password Leave this field empty

4. Choose Deploy.
5. Activate your security material by choosing  and Activate.

Results

You've created and activated a security material that supports OAuth 2.0 client certificate authorization
(x.509).

2.1.4.6.2.6 Configure Inbound Processor iFlow

You configure the INBOUND PROCESSOR iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAUTH 2.0 client certificate authorization (x.509).

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• The INBOUND PROCESSOR integration workflow is available in your SAP S/4HANA Integration with SAP
Digital Manufacturing package in SAP Cloud Integration. If not, an update of your package is required. For
more information, see Upgrade Information [page 231].
• You've created a security material with user credentials supporting OAUTH 2.0 client certificate
authorization. For more information, see Create a Security Material with User Credentials in SAP Cloud
Integration [page 79].

SAP Digital Manufacturing Integration Guide

80 PUBLIC SAP Digital Manufacturing for execution Integration
• You've created a key pair with user credentials in SAP Cloud Integration. For more information, see Create a
Key Pair and Upload the X.509 Certificate File to SAP Cloud Integration [page 78].

Context

In this step, you configure the INBOUND_PROCESSSOR integration flow in SAP Cloud Integration. To connect
SAP Cloud Integration to SAP Digital Manufacturing, you enter the name of the security material that gives
access to SAP Digital Manufacturing Cloud, called here CF_AUTH, into the DMC_CREDENTIAL field. To use the
OAUTH 2.0 client certificate authentication (x.509), you copy the alias name of the certificate from the Manage
Keystore app in SAP Cloud Integration into the DMC_PRIVATE_KEY_ALIAS field.

 Note

If you're already using client credential authoriziation, you can switch over from client credential
authorization to OAUTH 2.0 client certificate authorization (x.509). For more information about this
procedure and on how to switch to the INBOUND_PROCESSOR iFlow, see 3231128 .

Procedure

1. In SAP Cloud Integration, go to the Discover section.

2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. In the Artifacts tab, search for the INBOUND PROCESSOR integration workflow and choose  , then
Configure.

The Configure "INBOUND PROCESSOR" popup opens.

4. Enter the following parameters:

Parameter Value

DMC_API_URL public-api-endpoint
To be found in the service key in SAP Digital
Manufacturing subaccount. For example:

• https://api.eu10.dmc.cloud.sap (pro­
duction system)

• https://api.test.eu10.dmc.cloud.sap
(quality system)
For more information, see Create an X.509 Service Key in
SAP Digital Manufacturing [page 76].

DMC_CREDENTIAL CF_AUTH

Enter the name of the security material that you've cre­

ated in SAP Cloud Integration. For more information, see

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 81
 Parameter Value

Create a Security Material with User Credentials in SAP

Cloud Integration [page 79].

DMC_PRIVATE_KEY_ALIAS DMC_KEY_PAIR

Enter the alias of your certificate from the Manage

Keystore app in SAP Cloud Integration. For more informa­
tion, see Create a Key Pair and Upload the X.509 Certifi-
cate File to SAP Cloud Integration [page 78].

DMC_TOKEN_URL certurl/oauth/token

To be found in the service key in your SAP Digital

Manufacturing subaccount. For more information, see
Create an X.509 Service Key in SAP Digital Manufacturing
[page 76].

ENDPOINT_ID 00

5. Choose Save.
6. To deploy the INBOUND PROCESSOR integration workflow, choose  , then Deploy.

Results

You've configured and deployed the INBOUND PROCESSOR iflow.

Related Information

Create a Security Material with User Credentials in SAP Cloud Integration [page 79]

2.1.4.6.2.7 Configure Initial Parameters iFlow

You configure the Initial Parameters iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAuth 2.0 client certificate authorization (x.509).

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've configured the INBOUND PROCESSOR integration workflow. For more information, see Configure
Inbound Processor iFlow [page 80].

SAP Digital Manufacturing Integration Guide

82 PUBLIC SAP Digital Manufacturing for execution Integration
• You've created a service key supporting OAUTH 2.0 client certificate authorization in SAP Digital
Manufacturing. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing [page
76].

Context

With this procedure, you configure the Initial Parameters integration flow in SAP Cloud Integration.
To enable SAP Cloud Integration to write parameters to SAP Cloud Integration, so that all integration flows
can access them, you enter the credential that you've prepared for your initial parameter deployment,
for example PD_DEPLOYER_USER or PD_DEPLOYER_CLIENT, under TENANT_CREDENTIALS. Then you set
ENABLE_INBOUND_OAUTH to TRUE to activate the INBOUND_PROCESSOR integration flow. The first three
parameters at the top of the table below are then ignored.

Procedure

1. In SAP Cloud Integration, go to the Discover section.

2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. In the Artifacts tab, search for the Initial Parameters integration workflow and choose  , then Configure.

The Configure "Initial Parameters" popup opens.

4. Enter the following parameters:

Parameter Name Description Value

COMMON_DME_IDENTITY_ZONE_SUBD The subdomain that allows SAP Cloud Go to SAP BTP Cockpit (of SAP
OMAIN Integration to access web services of Digital Manufacturing for execution),
SAP Digital Manufacturing. choose the Execution SaaS tenant,
and you can find the Subdomain in the
Subaccount Details section.

COMMON_DME_INT_URL The URL of the back-end integration- Go to SAP BTP Cockpit (of SAP
ms application. Digital Manufacturing for execution)

Subaccounts Services Service

Instances Service Key . You

can find the URL under the
tag manufacturing-execution-
integration.

 Note
Remember to add the prefix
https:// for the URL.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 83
 Parameter Name Description Value

COMMON_DME_SB_URL Service broker URL for token fetching. Go to SAP BTP Cockpit (of SAP
Digital Manufacturing for execution)

Subaccounts Services Service

Instances Service Key . You can

find the URL by choosing the tag url
under the tag uaa.

ENABLE_PLANT_CONVERSION Define if you want to enable plant Enter TRUE to enable this function.
conversion function to connect mul­ For more information, see Mapping
tiple ERP plants to SAP Digital Plants (Plant Conversion) [page 224].

Manufacturing.

PID - DME_Generic_Processing_00

TENANT_CREDENTIALS The user credential created in the PD_DEPLOYER_USER or

Security Material app. PD_DEPLOYER_CLIENT

For more informations, see Prepare

Credentials for Initial Parameter De­
ployment [page 51].

TENANT_URL SAP Cloud Integration management Use the SAP Cloud Integration man­
URL used for iFlow deployment. agement URL in the email you re­
ceived after successful SAP Cloud
Integration tenant provisioning. If you
haven't access to this mail, see How
to Get SAP Cloud Integration Manage­
ment URL [page 20].

ENABLE_INBOUND_OAUTH Set ENABLE_INBOUND_OAUTH TRUE

to TRUE to use the
INBOUND_PROCESSOR iFlow, which is
recommended. If set to TRUE, the
first three parameters at the top of the
table disappear.

 Note
The default setting is FALSE.

5. Choose Save.
6. To deploy the Initial Parameters integration workflow, choose  , then Deploy.

SAP Digital Manufacturing Integration Guide

84 PUBLIC SAP Digital Manufacturing for execution Integration
Results

You've configured and deployed the Initial Parameters iFlow.

2.1.4.7 Connect SAP Digital Manufacturing to SAP Cloud

Integration
To enable communication from SAP Digital Manufacturing to SAP Cloud Integration, you configure destinations
and choose an authentication method.

Use

To enable communication from SAP Digital Manufacturing to SAP Cloud Integration, you need to configure
SAP Cloud Integration destinations in your SAP BTP cockpit. Moreover, you need to choose an authentication
method to build a connection between the systems. The procedure to set up authorization varies depending on
the environment you're in. These are your options:

• Connection with Basic Authentication (Neo and Cloud Foundry) [page 85]
• Connection with Client Credential Authentication in Neo Environment [page 90]
• Connection with Client Credential Authentication in Cloud Foundry Environment [page 93]
• Connection with X.509 certificate-based Authorization in Cloud Foundry Environment [page 96]

2.1.4.7.1 Connection with Basic Authentication (Neo and

Cloud Foundry)
Connect SAP Digital Manufacturing to SAP Cloud Integration using basic authentication in Neo or Cloud
Foundry environment.

Prerequisites

• You've got a P-user with access to SAP Cloud Integration. For more information, see Granting Your P-User
Access to SAP Cloud Integration in Neo Environment [page 87] or Granting Your P-User Access to SAP
Cloud Integration in Cloud Foundry Environment [page 89].

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 85
• You've got the SAP Cloud Integration runtime URL. For more information, see How to Get SAP Cloud
Integration Runtime URL [page 21].

 Example

For SAP Cloud Integration in the Cloud Foundry environment, the URL is https://<Cloud
Integration tenant>.it-accd002-rt.cfapps.sap.hana.ondemand.com.

 Example

For SAP Cloud Integration in Neo environment, the URL is https://<Cloud Integration
tenant>-iflmap.avtsbhf.eu1.hana.ondemand.com.

• You've got the SAP Cloud Integration management URL. For more information, see How to Get SAP Cloud
Integration Management URL [page 20].

 Example

For SAP Cloud Integration in Cloud Foundry environment, the URL is https://<Cloud Integration
tenant>.it-accd002.cfapps.sap.hana.ondemand.com.

 Example

For SAP Cloud Integration in Neo environment, the URL is https://<Cloud Integration
tenant>-tmn.avt.eu1.hana.ondemand.com.

Context

To enable communication from SAP Digital Manufacturing to SAP Cloud Integration, you need to configure
SAP Cloud Integration destinations in your SAP BTP cockpit. The CPI_DESTINATION_IFLMAP enables SAP
Digital Manufacturing access the endpoints exposed by SAP Cloud Integration. The CPI_DESTINATION_TMN
destination enables SAP Digital Manufacturing to access information such as SAP Cloud Integration logs.

 Note

Instead of basic authentication, you can also enable client credential authentication
(OAuth2ClientCredentials) for technical users. There are specific methods for the Neo and SAP
Cloud Integration environment. For more information, see Connection with Client Credential Authentication
in Neo Environment [page 90] or Connection with Client Credential Authentication in Cloud Foundry
Environment [page 93].

 Note

The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workflows app as
well as for the Fetch CPI Logs functionality available in the Integration Message Dashboard app. For more
information, see Integration Message Dashboard.

SAP Digital Manufacturing Integration Guide

86 PUBLIC SAP Digital Manufacturing for execution Integration
Procedure

1. Log on to SAP BTP cockpit of SAP Digital Manufacturing and choose Connectivity Destinations in
the side menu bar.
2. Choose New Destination and enter the following fields to create two SAP Cloud Integration destinations.

Field CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Name CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Type HTTP HTTP

URL Enter the SAP Cloud Integration run­ Enter the SAP Cloud
time URL. The part to enter here ends Integration management URL.
with .com. For example, https:// The part to enter here ends
<Cloud Integration with .com. For example, https://
tenant><...>ondemand.com. <Cloud Integration
For more information, see above in the tenant><...>ondemand.com.
prerequisites section. For more information, see above in the
prerequisites section.

Proxy Type Internet Internet

Authentication BasicAuthentication BasicAuthentication

User P-user P-user

Password Password Password

2.1.4.7.1.1 Granting Your P-User Access to SAP Cloud

Integration in Neo Environment

Learn how to authorize your P-user for SAP Cloud Integration in Neo environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount.

• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 87
 • Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Overview, choose Members.
3. Choose Add Members.
4. In the User IDs field, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predefined role) and Developer (predefined role).
6. Choose Add Members.

7. Choose Security Authorizations .

8. On the Users tab, enter your P-user ID and choose Show Assignments.
9. Choose Assign in the area for individual assignment, not group assignment.

The Assign Roles to User popup opens.

10. Go through the available subaccounts and applications to assign the following roles and save them:

ESBMessaging.send

AuthGroup.BusinessExpert

AuthGroup.Administrator

AuthGroup.IntegrationDeveloper

Results

Your P-user has now access to SAP Cloud Integration.

SAP Digital Manufacturing Integration Guide

88 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.7.1.2 Granting Your P-User Access to SAP Cloud
Integration in Cloud Foundry Environment

Learn how to authorize your P-user for SAP Cloud Integration in Cloud Foundry environment to enable basic
authentication.

Prerequisites

• You've got the Administrator role for the subaccount in SAP BTP cockpit.
• You've got the user IDs of the members that you want to add.
• You've got a P-user and password.
To obtain a P-User ID, go to www.sap.com and register a new user using their email address.
If a user has already been registered with the SAP ID service (for example, at SAP Community or SAP
Developer Center) using the same email address, the user doesn't need to register again.
To find an existing P-user, you've got two options:
• Log on to your account at www.account.sap.com using your email address. In your profile, under
Accounts, you find your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your profile. Under
Personal Info Personal Data , you find your P-user ID under User ID.

 Note

Your P-user and the corresponding email address must not be bound to SAP Universal ID. To check
whether or not your P-user and the corresponding email are already bound to SAP Universal ID, log on
to your account at www.sap.com and go to the Personal Info tab. Choose Access SAP Universal ID
account manager to access the Manage my Account app. Under Accounts, you find your users.

Context

To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration first.

Procedure

1. In SAP BTP cockpit, select your SAP Cloud Integration subaccount.

2. Under Security Users , choose Create.

3. Under User Name, enter the e-mail address belonging to your P-user.
4. Choose Default Identity Provider.
5. Choose Create.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 89
6. Choose Security Role Collections .
7. Choose  .
8. Give your collection a name, for example My_RoleCollection, and choose Create.
9. Select your collection and choose Edit.
10. On the Roles tab, under Role Name, choose  and add the following roles to your collection:

MessagingSend

MessagePayloadsRead

AuthGroup_BusinessExpert

If you want to use the CPI Async Mode, there a some additional roles required. For more information, see
Asynchronous Connection to SAP Cloud Integration [page 109].

11. Under Security Users , choose your user.

12. In the detail view, choose Assign Role Collection to make the following assignments:

My_RoleCollection

PI_Integration_Developer (predefined)

PI_Administrator (predefined)

Results

Your P-user has now access to SAP Cloud Integration.

2.1.4.7.2 Connection with Client Credential Authentication

in Neo Environment

Connect SAP Digital Manufacturing to SAP Cloud Integration using client credential authentication
(OAuth2ClientCredentials) in Neo environment.

Prerequisites

• You have the SAP Cloud Integration runtime URL. For more information, see How to Get SAP Cloud
Integration Runtime URL [page 21].

 Example

For SAP Cloud Integration in Neo environment, the URL is https://<Cloud Integration
tenant>-iflmap.avtsbhf.eu1.hana.ondemand.com.

SAP Digital Manufacturing Integration Guide

90 PUBLIC SAP Digital Manufacturing for execution Integration
• You have the SAP Cloud Integration managment URL. For more information, see How to Get SAP Cloud
Integration Management URL [page 20].

 Example

For SAP Cloud Integration in Neo environment, the URL is https://<Cloud Integration
tenant>-tmn.avt.eu1.hana.ondemand.com.

Context

To enable client credential communication (OAuth2ClientCredentials) from SAP Digital Manufacturing

to SAP Cloud Integration, you need to create two OAuth clients in your SAP Cloud Integration subaccount.
SAP Digital Manufacturing can access these clients using an authentication token provided by SAP Cloud
Integration through its token endpoint. Moreover, you need to create destinations in SAP Digital Manufacturing
that point towards SAP Cloud Integration. The CPI_DESTINATION_IFLMAP enables SAP Digital Manufacturing
access the endpoints exposed by SAP Cloud Integration. The CPI_DESTINATION_TMN destination enables
SAP Digital Manufacturing to access information such as SAP Cloud Integration logs.

 Note

The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workflows app as
well as for the Fetch CPI Logs functionality available in the Integration Message Dashboard app. For more
information, see Integration Message Dashboard.

Procedure

1. In SAP BTP cockpit, log on to your SAP Cloud Integration subaccount and then choose
Security OAuth . In Branding section, note down the Token Endpoint, for example https://
{…].hana.ondemand.com/oauth2/api/v1/token.
2. Choose the Clients tab, and register two clients: one for ifmap and another one for tmn. You can randomly
define the Name and Secret of the client, for example oauth_client_ifmap and oauth_client_tmn.
In Subscription, select the one ending with ifmap or tmn. In Authorization Grant, select Client Credentials.
Note down the client IDs that are automatically generated.

3. Choose Security Authorization Users in the side menu bar.

4. Create two users: oauth_client_ifmap_<client ID of ifmap> and oauth_client_tmn_<client
ID of tmn> by choosing Show Assignments, for example oauth_client_ifmap_123456-a123-a123-
a123-a123445678.
5. In the Roles section, assign the following roles to the Application ending with tmn:
• AccessPoliciesArtifacts.AccessAll
• AuthGroup.TenantPartnerDirectoryConfigurator
• AuthGroup.BusinessExpert
• AuthGroup.IntegrationDeveloper

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 91
6. Assign the following role to the Application ending with ifmap: ESBMessaging.send.

7. Navigate to your SAP Digital Manufacturing subaccount in SAP BTP cockpit and choose Connectivity
Destinations in the side menu bar.
8. Choose New Destination and enter the following fields to create two SAP Cloud Integration destinations.

Field CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Name CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Type HTTP HTTP

URL Enter the SAP Cloud Integration run­ Enter the SAP Cloud Integration man­
time URL. agement URL.

For example: https://<Cloud For example: https://<Cloud

Integration tenant>- Integration tenant>-
iflmap.avtsbhf.eu1.hana.o tmn.avt.eu1.hana.ondemand
ndemand.com. .com

Proxy Type Internet Internet

Authentication OAuth2ClientCredentials OAuth2ClientCredentials

Client ID Enter the <client ID of iflmap> that's Enter the <client ID of tmn> that's
noted down in Step 2. noted down in Step 2.

Client Secret Enter the secret you used to register Enter the secret you used to register
clients in Step 2. clients in Step 2.

Token Service URL Type Select Dedicated. Select Dedicated.

Token Service URL Enter the token endpoint that's noted Enter the token endpoint that's noted
down in Step 1. down in Step 1.

Token Service User Enter the same value as the one en­ Enter the same value as the one en­
tered in the Client ID field. tered in the Client ID field.

Token Service Password Enter the secret you used to register Enter the secret you used to register
clients in Step 2. clients in Step 2.

9. Choose Save.

SAP Digital Manufacturing Integration Guide

92 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.7.3 Connection with Client Credential Authentication
in Cloud Foundry Environment

Connect to SAP Cloud Integration using client credential authentication (OAuth2ClientCredentials) in Cloud
Foundry environment.

Prerequisites

• You have the SAP Cloud Integration runtime URL. For more information, see How to Get SAP Cloud
Integration Runtime URL [page 21].

 Example

For SAP Cloud Integration in the Cloud Foundry environment, the URL is https://<Cloud
Integration tenant>.it-accd002-rt.cfapps.sap.hana.ondemand.com.

• You have the SAP Cloud Integration management URL. For more information, see How to Get SAP Cloud
Integration Management URL [page 20].

 Example

For SAP Cloud Integration in Cloud Foundry environment, the URL is https://<Cloud Integration
tenant>.it-accd002.cfapps.sap.hana.ondemand.com.

• In the SAP Cloud Integration subaccount in SAP BTP cockpit, you've created two service instances that
each have a service key. The first instance is used for the IFLMAP destination and requires the integration-
flow service plan. The second instance is used for the TMN destination and requires the api service plan. For
more information, see Create Instances in SAP Cloud Integration Subaccount [page 95].

Context

To enable client credential communication (OAuth2ClientCredentials) from SAP Digital Manufacturing to SAP
Cloud Integration, you need to create two destinations in SAP Digital Manufacturing that point towards
SAP Cloud Integration. Each of these two destinations refers to its own SAP Cloud Integration service
instance with its own client ID and client secret that can be found in the respective service key. The
CPI_DESTINATION_IFLMAP enables SAP Digital Manufacturing access the endpoints exposed by SAP Cloud
Integration. The CPI_DESTINATION_TMN destination enables SAP Digital Manufacturing to access information
such as SAP Cloud Integration logs.

 Note

The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workflows app as
well as for the Fetch CPI Logs functionality available in the Integration Message Dashboard app. For more
information, see Integration Message Dashboard.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 93
Procedure

1. In SAP BTP cockpit, log on to your SAP Cloud Integration subaccount and then choose Services
Instances and Subscriptions to find the two service instances you created. Note down the clientid, the
clientsecret, and the url of the service key of each instance.

2. In SAP BTP cockpit, log on to your SAP Digital Manufacturing subaccount and choose Connectivity
Destinations in the side menu bar.
3. Choose New Destination and enter the following fields to create two SAP Cloud Integration destinations.

Field CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Name CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN

Type HTTP HTTP

URL Enter the SAP Cloud Integration run­ Enter the SAP Cloud Integration man­
time URL. agement URL.

For example: https://<Cloud For example: https://<Cloud

Integration tenant>.it- Integration tenant>.it-
accd002- accd002.cfapps.sap.hana.ondem
rt.cfapps.sap.hana.ondemand.c and.com
om

Proxy Type Internet Internet

Authentication OAuth2ClientCredentials OAuth2ClientCredentials

Client ID Enter the <clientid of Enter the <clientid of

Service key> of instance 1, which Service key> of instance 2, which
has the integration-flow service plan. has the api service plan.

Client Secret Enter the <clientsecret of Enter the <clientsecret of

Service key> of instance 1, which Service key> of instance 2, which
has the integration-flow service plan. has the api service plan.

Token Service URL Type Select Dedicated. Select Dedicated.

Token Service URL Enter the <URL of Service Enter the <URL of Service
Key>/oauth/token, taken from Key>/oauth/token, taken from
the service key of instance 1, which the service key of instance 2, which
has the integration-flow service plan. has the api service plan.

Related Information

Creating Service Instance and Service Key for Inbound Authentication

SAP Digital Manufacturing Integration Guide

94 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.7.3.1 Create Instances in SAP Cloud Integration
Subaccount

Create two instances with a service key in your SAP Cloud Integration subaccount in Cloud Foundry
environment.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to your SAP Cloud Integration subaccount in SAP BTP cockpit.

Context

To set up client credential communication from SAP Digital Manufacturing to SAP Cloud Integration in Cloud
Foundry environment, you need to create two instances with a service key in your SAP Cloud Integration
subaccount. The first one, where integration-flow is chosen, is used later for CPI_DESTINATION_IFLMAP. The
second one, where API is chosen, is used later for CPI_DESTINATION_TMN.

Procedure

1. In SAP BTP cockpit, go to your SAP Cloud Integration subaccount.

2. Go to Services Instances and Subscriptions .

3. Choose Create to create an instance.
4. In the New Instance or Subscription popup, enter the following parameters:

Field Value

Service Process Integration Runtime

Plan integration-flow

Runtime Environment Cloud Foundry

Space Name of your subaccount's space

Instance Name Name

5. Choose Next.
6. Under Configure instance parameters, enter the following parameters:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 95
 Field Value

Roles ESBMessaging.send

Grant-types Client Credentials

Redirect-urls

7. Choose Next.
8. Choose Create.
9. Choose the instance that you've created.
10. In the Service Key tab, choose Create to create a service key.
11. In the New Service Key popup, enter a Service Key Name of your choice.
12. Under Key Type, choose ClientId/Secret.
13. Choose Create.

Under Service Keys, you can see the new key.

14. Repeat the whole procedure to create another instance. This time, choose API as Plan and select the
following roles:
• AccessAllAccessPoliciesArtifacts
• AuthGroup_Administrator
• AuthGroup_TenantPartnerDirectoryConfigurator
• MonitoringArtifactsDeploy
• MonitoringDataRead
• SecurityMaterialDownload
If you want to use the CPI Async Mode, there a some additional roles required. For more information, see
Asynchronous Connection to SAP Cloud Integration [page 109].

2.1.4.7.4 Connection with X.509 certificate-based

Authorization in Cloud Foundry Environment
Connect SAP Digital Manufacturing to SAP Cloud Integration using X.509 certificate-based authentication in
Cloud Foundry environment.

Use

You can make the data exchange from SAP Digital Manufacturing to SAP Cloud Integration more secure by
using a X.509 certificate.

General Overview of the Procedure

To enable X.509 certifficate-based communication from SAP Digital Manufacturing to SAP Cloud Integration,
you need to create a service key in SAP Digital Manufacturing and create a certificate that will enable secure

SAP Digital Manufacturing Integration Guide

96 PUBLIC SAP Digital Manufacturing for execution Integration
communication between the systems. You upload the x.509 certificate in SAP Digital Manufacturing and SAP
Cloud Integration. Then you create two destinations in SAP Digital Manufacturing that points towards SAP
Cloud Integration. The CPI_DESTINATION_IFLMAP destination enables SAP Digital Manufacturing to access
the endpoints exposed by SAP Cloud Integration. The CPI_DESTINATION_TMN destination enables SAP Digital
Manufacturing to access information such as SAP Cloud Integration logs.

Overview Setup Steps

To set up the X.509 certificate-based communication from SAP Digital Manufacturing to SAP Cloud Integration
in Cloud Foundry environment, perform the tasks described in the following topics:

1. Before You Start [page 97]

2. Create an X.509 Service Key in SAP Digital Manufacturing [page 98]
3. Create an X.509 Certificate [page 99]
4. Create a Key Pair and Upload the X.509 Certificate File to SAP Cloud Integration [page 100]
5. Create Instances with an X.509 Service Key in your SAP Cloud Integration subaccount [page 101]
6. Create Destinations in SAP Digital Manufacturing [page 102]

2.1.4.7.4.1 Before You Start

This page shows you the prerequisites that are required to connect SAP Digital Manufacturing to SAP Cloud
Integration using an x.509 certificate.

Prerequisites

• You've the Administrator role for SAP BTP cockpit.

• You've the Administrator role for SAP Cloud Integration.
• You've the Space Developer role in Cloud Foundry environment.
• You've access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've software to create certificate files of type .pfx, such as openSSL.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 97
2.1.4.7.4.2 Create an X.509 Service Key in SAP Digital
Manufacturing

Create a service key that supports X.509 credentials in your SAP Digital Manufacturing subaccount.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Context

To set up communication from SAP Digital Manufacturing to SAP Cloud Integration or from SAP Cloud
Integration to SAP Digital Manufacturing using an X.509 certificate, you need to create a service key that
supports X.509 credentials in your SAP Digital Manufacturing subaccount.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Under Instances and Subscriptions, choose your SAP Digital Manufacturing instance.
3. In the Service Keys tab, choose Create to create a service key.
4. In the New Service Key popup, enter a Service Key Name of your choice.
5. Paste {"xsuaa":{"credential-type":"x509"}} as parameter into the JSON format field.

 Note

You can also specify the validity period, for example: {"credential-type": "x509","x509": {"validity":
4,"validity-type": "MONTHS"}. The default setting is 7 days. The maximum duration is 1 year.

Be aware that you need to create a new service key before the x.509 certificate of the current service
key expires.

6. Choose Create.

You've created a service key supporting X.509 credentials.

SAP Digital Manufacturing Integration Guide

98 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.7.4.3 Create an X.509 Certificate

Create an X.509 certificate that's needed for X.509 certificate-based data transfer between SAP Digital
Manufacturing and SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've created a service key supporting OAuth 2.0 client certificate authorization for your SAP Cloud
Integration instance. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing
[page 98].
• You've software to create certificate files of type .pfx, such as openSSL.

Context

To enable communication between SAP Digital Manufacturing and SAP Cloud Integration using X.509
credentials, you need to create an X.509 certificate based on information that can be found in the service
key.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Under Instances and Subscriptions, choose your SAP Cloud Integration instance.
3. Open the service key.
4. In the JSON box, go to the key field, which is under the "uaa" tag, and copy the content of the key field into
a new file of type .pem, for example key.pem, and save it.
5. In the JSON box, go to the certificate field, which is under the "uaa" tag, and copy the content of the
certificate field into a new file of type .pem, for example certificate.pem, and save it.
6. Create a certificate file of type .pfx, for example service.pfx, combining key.pem and
certificate.pem, and assign a password to it.

If you're using OpenSSL to create the .pfx file, use this command: openssl pkcs12 -export -out
service.pfx -in key key.pem -in certificate.pem.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 99
2.1.4.7.4.4 Create a Key Pair and Upload the X.509 Certificate
File to SAP Cloud Integration

Create a key pair in SAP Cloud Integration and upload the X.509 certificate file to SAP Cloud Integration to
enable data transfer from SAP Digital Manufacturing to SAP Cloud Integration.

Prerequisites

• You've got the Administrator role for SAP Cloud Integration.

• You've got an X.509 certificate with a password. For more information, see Create an X.509 Certificate
[page 99].

Context

To set up communication from SAP Digital Manufacturing to SAP Cloud Integration or from SAP Cloud
Integration to SAP Digital Manufacturing using an X.509 certificate, you need to create a key pair in SAP
Cloud Integration and upload the X.509 certificate into the system. Then you need to download the certificate
to your computer to use it later in the integration process.

Procedure

1. In SAP Cloud Integration, go to Operate and monitor integration scenarios and choose the Keystore tile.
2. Choose Add.
3. Choose Key Pair.
4. In the Add Key Pair popup, enter an Alias for the key pair, for example DMC_KEY_PAIR. You can choose a
random name.
5. Upload the .pfx file, for example service.pfx, by using the Browse function.
6. Enter the password that you've defined for the .pfx file.
7. Choose Add.
8. Right-click the newly created key pair and choose Download Certificate.

A certificate of type .cer has been created, for example dmc_service.cer, and downloaded to your
computer. You need it for the next step.

SAP Digital Manufacturing Integration Guide

100 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.4.7.4.5 Create Instances with an X.509 Service Key in
your SAP Cloud Integration subaccount

Create two instances with a service key using X.509 credentials in your SAP Cloud Integration subaccount.

Prerequisites

• You've the Administrator role for SAP BTP cockpit.

• You've access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've a certificate file of type .cer that you've downloaded from SAP Cloud Integration. For more
information, see Create a Key Pair and Upload the X.509 Certificate File to SAP Cloud Integration [page
100].

Context

To set up the X.509 certificate-based communication from SAP Digital Manufacturing to SAP Cloud Integration
in Cloud Foundry environment, you need to create two instances with a service key using X.509 credentials
in your SAP Cloud Integration subaccount. The first one, where integration-flow is chosen, is used later for
CPI_DESTINATION_IFLMAP. The second one, where API is chosen, is used later for CPI_DESTINATION_TMN.

Procedure

1. In SAP BTP cockpit, go to your SAP Cloud Integration subaccount.

2. Go to Services Instances and Subscriptions .

3. Choose Create to create an instance.
4. In the New Instance or Subscription popup, enter the following parameters:

Field Value

Service Process Integration Runtime

Plan integration-flow

Runtime Environment Cloud Foundry

Space Name of your subaccount's space

Instance Name Name

5. Choose Next.
6. Under Configure instance parameters, enter the following parameters:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 101
 Field Value

Roles ESBMessaging.send

Grant-types Client Credentials

Redirect-urls

7. Choose Next.
8. Choose Create.
9. Choose the instance that you've created.
10. On the Service Keys tab, choose Create to create a service key.
11. In the New Service Key popup, enter a Service Key Name of your choice.
12. Under Key Type, choose External Certificate.
13. Under External Certificate, paste the content of the certificate file that you've downloaded from SAP Cloud
Integration, for example dmc_service.cer, into the empty box.
14. Choose Create.

Under Service Keys, you can see the new key.

15. Repeat the whole procedure to create another instance and choose API as Plan.

2.1.4.7.4.6 Create Destinations in SAP Digital Manufacturing

Create two destinations in SAP Digital Manufacturing pointing towards SAP Cloud Integration.

Prerequisites

• You've the Administrator role for SAP BTP cockpit.

• You've access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've an X.509 certificate of type .pfx. For more information, see Create an X.509 Certificate [page 99].

Context

To set up the X.509 certificate-based communication from SAP Digital Manufacturing to SAP Cloud
Integration in Cloud Foundry environment, you need to create two destinations in SAP Digital Manufacturing
pointing towards SAP Cloud Integration. The CPI_DESTINATION_IFLMAP destination enables SAP Digital
Manufacturing to access the endpoints exposed by SAP Cloud Integration. The CPI_DESTINATION_TMN
destination enables SAP Digital Manufacturing to access information such as SAP Cloud Integration logs.

SAP Digital Manufacturing Integration Guide

102 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workflows app as
well as for the Fetch CPI Logs functionality available in the Integration Message Dashboard app. For more
information, see Integration Message Dashboard.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Under Destinations, choose Certificates and upload the .pfx file, for example service.pfx to the system.
3. Choose New Destination to create two destinations, one of type CPI_DESTINATION_IFLMAP and one of
type CPI_DESTINATION_TMN. You can also modify existing destinations.
4. Under Destination Configuration enter the following values:

CPI_DESTINATION_IFLMA
Field P CPI_DESTINATION_TMN

Name CPI_DESTINATION_IFLMA CPI_DESTINATION_TMN

P

Type HTTP HTTP

Description Description Description

URL SAP Cloud Integration run­ SAP Cloud Integration man­
time URL to be found in agement URL to be found
the SAP Cloud Integration in the SAP Cloud Integration
subaccount under Instances subaccount under Instances
in the Credentials column. in the Credentials column.
Choose the Key that be­ Choose the Key that be­
longs to your instance with longs to your instance with
integration-flow plan. Under API plan. Under url, you find
url, you find the runtime the management URL.
URL.

Proxy Type Internet Internet

Authentication OAuth2ClientCredentials OAuth2ClientCredentials

Use mTLS for token retrieval Tic box. Tic box.

Client ID To be found under clientid in To be found under clientid in

your certificate file, for ex­ your certificate file, for ex­
ample service.pfx. ample service.pfx.

Token Service Key Store Choose your certificate file, Choose your certificate file,
Location for example service.pfx. for example service.pfx.

Token Service Key Store Enter the password that Enter the password that
Password you defined for your cer­ you defined for your cer­
tificate file, for example tificate file, for example
service.pfx. service.pfx.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 103
 CPI_DESTINATION_IFLMA
Field P CPI_DESTINATION_TMN

Token Service URL Type Dedicated Dedicated

Token Service URL To be found under tokenurl To be found under tokenurl

in the certificate. in the certificate.

Token Service User

Token Service Password

5. Choose Save.

2.1.4.8 Set Up Connection Between SAP Cloud Integration,

Cloud Connector, and SAP S/4HANA or SAP ERP

Configure the Cloud Connector to make it operational for connections between your SAP BTP applications and
on-premise systems.

Prerequisites

• You've got a technical user for SAP S/4HANA or SAP ERP. For more information, see Create a Technical
User for SAP S/4HANA [page 19].
• You've got the Administrator role in SAP S/4HANA or SAP ERP.
• You've installed the Cloud Connector. For more information, see Setting Up the Cloud Connector [page 22].

Context

To enable communication from SAP Cloud Integration to SAP S/4HANA or SAP ERP, you need to configure
the Cloud Connector, which acts as a reverse invoke proxy between your on-premise network and SAP Cloud
Integration.

In your SAP Cloud Integration subaccount in SAP BTP cockpit, you create RFC destinations pointing towards
SAP S/4HANA or SAP ERP.

Procedure

Configure the Cloud Connector

1. Initial configuration
After installing and starting the Cloud Connector, log on to the administration UI and perform the required
configuration to make your Cloud Connector operational. For more information, see Initial Configuration.

SAP Digital Manufacturing Integration Guide

104 PUBLIC SAP Digital Manufacturing for execution Integration
2. Add and connect your SAP Cloud Integration subaccount to the Cloud Connector. For detailed procedures,
see Configure Subaccounts in Cloud Connector [page 24].
3. Add system mapping to SAP S/4HANA or SAP ERP and configure access control. For more information,
see Configure Access Control [page 26].

Add RFC Destinations to SAP Cloud Integration Subaccount

Add RFC destinations of SAP S/4HANA or SAP ERP in the SAP Cloud Integration subaccount in SAP BTP
cockpit.

1. In SAP BTP cockpit, go to your SAP Cloud Integration subaccount and choose Connectivity
Destinations in the side menu bar.
2. Choose New Destination, and enter the following fields to create the destination:

Name Type Proxy Type User Password Location ID

Enter a destina­ RFC OnPremise Enter the name Enter the pass­ If you've main­
tion name. of your technical word to access tained a location
user to access SAP S/4HANA / ID in the Cloud
 Note SAP S/4HANA / SAP ERP.
Connector, enter
SAP ERP.
You use this the location ID
destination here.
name later in
the Manage
Business
Settings app
in SAP Digital
Manufacturin
g.

3. Add the following Additional Properties:

Property Description Value

jco.client.ashost The Virtual Host of SAP S/4HANA /  Example

SAP ERP defined in the Cloud Con­
<virtual host>
nector

jco.client.client The client number of SAP S/4HANA /  Example

SAP ERP
100

jco.client.lang The language of SAP S/4HANA / SAP  Example

ERP
EN

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 105
 Property Description Value

jco.client.sysnr The system number of SAP S/  Example

4HANA / SAP ERP
22

jco.destination.pool_capacity The connection number  Example

5

4. Check the availability of the destination connection.

2.1.4.9 Configure SAP Digital Manufacturing for Outbound

Integration

You need to make configurations in SAP Digital Manufacturing to connect plants and enable integration with
SAP ERP or SAP S/4HANA.

Prerequisites

You've got the Manufacturing_Admin role in SAP Digital Manufacturing.

Context

To integrate your on-premise system with SAP Digital Manufacturing, you need to create a plant in SAP Digital
Manufacturing that represents your existing plant in SAP ERP or SAP S/4HANA. To make sure that integration
messages can be sent from SAP Digital Manufacturing to SAP ERP or SAP S/4HANA, you map collaboration
links to collaboration directives in the Manage Collaborations Links app.

Procedure

1. Define the SAP ERP or SAP S/4HANA plant you want to integrate with.
1. Log on to SAP Digital Manufacturing using the Fiori Launchpad and choose the Manage Plants app.
2. On the initial screen, choose Create to add the plant defined in SAP S/4HANA that you want to
integrate with SAP Digital Manufacturing.
3. Complete the fields on the Create Plant screen.
4. Choose the Manage Business Settings app and complete the fields. Use the destination name that
you've defined in your SAP Cloud Integration subaccount in SAP BTP cockpit. (For more information,

SAP Digital Manufacturing Integration Guide

106 PUBLIC SAP Digital Manufacturing for execution Integration
 see Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP
ERP [page 104].)
For more information about the fields, see Manage Plants and Manage Business Settings.
2. Define the mapping of collaboration links with collaboration directives for outbound integration. For more
information, see Manage Collaboration Links.
3. To verify whether the outbound communication was successful, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check
the status of the outbound integration messages. For more information, see Integration Message
Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of the outbound
integration messages. For more information, see Monitoring Message Processing.

2.1.4.10 Enable Direct Communication To SAP S/4HANA

Enable the direct outbound communication from SAP Digital Manufacturing to Cloud Connector and then to
SAP S/4HANA, without calling SAP Cloud Integration.

Prerequisites

• Cloud Connector is installed.

• The subaccount in your SAP BTP cockpit is connected to the Cloud Connector. More information, see
Setting Up the Cloud Connector [page 22].
• SAP Digital Manufacturing and SAP Cloud Integration are in different subaccounts of your SAP BTP
cockpit.

Context

For some integration scenarios, you need to enable the direct outbound communication using an OData
connection from SAP Digital Manufacturing to Cloud Connector and then to SAP S/4HANA, without calling
SAP Cloud Integration.

 Note

Plant mapping (plant conversion) isn't compatible with the direct communciation scenarios described
below.

The following are the scenarios where direct communication to SAP S/4HANA is required:

 Note

For more information on the supported message types and needed integration artifacts, see
0003050090 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 107
• Order Discard
When you discard an order in the Manage Orders app, the order status is updated to DISC in the integrated
ERP systems.
• Defect Recording
When you log nonconformances with the Work Center POD, the defect recording can be transferred to
SAP S/4HANA. For this scenario, you need to use the following integration directives / links in the Manage
Integration Workflows app:
• COLLABORATION_DEFECT_RECORD and ERP_DEFECT_RECORD (ODATA V2) requireSAP S/4HANA
2021 FPS0
• COLLABORATION_DEFECT_RECORD and ERP_DEFECT_RECORD_V2 (ODATA V4) require SAP S/4HANA
2022 FPS0
You need to activate the Direct Access SAP S/4 HANA switch of your collaboration directive in the Manage
Collaboration Directives app.
• ERP Stock Read in Consolidated Inventory Management Mode
When you've enabled the consolidated inventory management mode in the Manage Business Settings app
in integration with SAP S/4HANA, a submessage ERP Stock Read is triggered with Inventory Download
message to sync back latest ERP data.
The direct communication is only needed for consolidated inventory management mode in integration with
SAP S/4HANA.
• QM Group Synchronization
If you want to download the quality management groups from your integrated ERP system into the Manage
Nonconformance Groups app using the Sync QM Groups functionality, you normally use collaboration
directive ERP_FETCH_DEFECT_CODE with the Direct Access SAP S/4HANA flag set to Off (=default setting)
in the Manage Collaboration Directives app.
But there are S/4HANA systems where the necessary BAPI (BAPI_CODEGROUP_CODE_GETLIST) is
obsolete, so that the data exchange between SAP Digital Manufacturing, SAP Cloud Integration, and SAP
S/4HANA isn't working. In this case, you need to activate the direct access to SAP S/4HANA by setting the
Direct Access SAP S/4HANA flag to ON. Moreover, you need to create a destination as described below to
enable direct communication (OData) between SAP Digital Manufacturing and SAP S/4HANA.
• Backward Update with Resource Orchestration
To allow the Resource Orchestration tool to write back the changes in the schedule and
dispatch operations to the same work centers hosted in SAP S/4HANA, you use the
ERP_UPDATE_REO_BACK_SCHEDULE directive in the Manage Collaboration Directives app. The Direct
Access SAP S/4HANA flag must be set to ON. Moreover, you need to create a destination as described
below to enable direct communication (OData) between SAP Digital Manufacturing and SAP S/4HANA.
In SAP S/4HANA, you need to enable the API_PRODUCTION_ORDERS service. For more information, see
How to Enable ODATA SERVICES. The REO Shop Order Schedule Update (S4) integration message requires
at least SAP S/4HANA 2020.

 Note

You switch on the backward update feature in the settings of the Dispatching and Monitoring 2.0 app.

Procedure

1. Define the destination name.

SAP Digital Manufacturing Integration Guide

108 PUBLIC SAP Digital Manufacturing for execution Integration
 Go to the Manage Business Settings app to find the specific plant, and note down the ERP destination. It
would be the destination name.
2. Map SAP S/4HANA to Cloud Connector.
1. Log on to Cloud Connector and choose your SAP Digital Manufacturing subaccount. Note down the
location ID.
2. Choose Cloud To On-Premise settings, and add a virtual system mapping with below information.
• Back-end Type: ABAP System
• Protocol: HTTPS
• Internal Host: SAP S/4HANA internal host
• Internal Port: SAP S/4HANA internal port for HTTPS
• Virtual Host and Port: You can specify it freely. It's recommended to use a virtual (cloud-side) name
that is different from internal name. Make sure to note it down.
3. Add accessible resource for above virtual system mapping.
• URL Path: /sap/opu/odata4/sap (ODATA V4) and /sap/opu/odata/sap (ODATA V2)
• Active: Make sure it's checked.
• Access Policy: Select Path And All Sub-Paths.
4. Log on to SAP Digital Manufacturing (Execution SaaS tenant) in SAP BTP Cockpit and choose
Connectivity Destinations in the side menu bar.
5. Create a new destination with the following information:
• Name: <the ERP destination name from Step 1>
• Type: HTTP
• URL: http://<virtual host from Step 2>:<virtual port from Step 2>
• Proxy Type: OnPremise
• Authentication: BasicAuthentication
• Location ID: <Location ID from Step 2>
• User: User from SAP S/4 HANA
• Password: Password for above user
• Additional Properties: sap-client and <client for SAPS/4HANA>

2.1.4.11 Asynchronous Connection to SAP Cloud Integration

Learn how to establish an asynchronous connection from SAP Digital Manufacturing to SAP Cloud Integration
(Cloud Foundry environment) using the CPI Async mode. Using this mode, which is available for EWM Goods
Receipt, you benefit from increased stability for long-running transactions in SAP ERP or SAP S/4HANA.

Prerequisites

• You've implemented the steps required for the technical integration. For more information, see Technical
Integration with SAP S/4HANA or SAP ERP [page 14].
• If you're using Basic Authentication between SAP Digital Manufacturing and SAP Cloud Integration, you
need to assign the following roles to your P-user in your SAP Cloud Integration subaccount in SAP BTP
cockpit:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 109
 • DataStoresAndQueuesRead
• DataStoresAndQueuesDelete
• DataStorePayloadsRead
For more information, see Granting Your P-User Access to SAP Cloud Integration in Cloud Foundry
Environment [page 54].
• If you're using Client Credential Authentication (OAuth2ClientCredentials) between SAP Digital
Manufacturing and SAP Cloud Integration, you need to go to your SAP Cloud Integration subaccount
in SAP BTP cockpit and update the instance that the CPI_DESTINATION_TMN is pointing to with the
following roles:
• DataStoresAndQueuesRead
• DataStoresAndQueuesDelete
• DataStorePayloadsRead
For more information, see Create Instances in SAP Cloud Integration Subaccount [page 95] and Updating
a Service Instance.
• You've deployed the following integration artifacts from your SAP S/4HANA Integration with SAP Digital
Manufacturing package in SAP Cloud Integration (Cloud Foundry):
• Async Request Producer
This iFlow receives the SAP Digital Manufacturing request message and puts the request message into
the request JMS queue.
• Async Request Consumer
This iFlow gets the request message from the JMS request queue and consumes the request message.
It sends the message to the integrated ERP system and gets a response.
• Async Response Producer
This iFlow puts the response from the integrated ERP system into the response JMS queue.
• Async Response Consumer
This iFlow consumes the response message from the response JMS queue and sends the response to
SAP Digital Manufacturing.
If your business case requires a modification of the default settings, see Advanced CPI Async Settings
[page 112].

 Note

If you don't deploy one of the artifacts, the following error is displayed
in the Integration Message Dashboard: 500 Internal Server Error
- ...tvm.DirectVmConsumerNotAvailableException: No consumers available on
endpoint: {Artifcat Name}. Exchange[].

SAP Digital Manufacturing Integration Guide

110 PUBLIC SAP Digital Manufacturing for execution Integration
Context

In integration scenarios with SAP ERP or SAP S/4HANA, the asynchronous connection to SAP Cloud
Integration (CPI Async), helps you achieve increased stability for long-running transactions on the ERP side.
Once you've implemented the CPI Async mode, outbound integration messages are processed asynchronously
in SAP Cloud Integration (Cloud Foundry environment).

After SAP Cloud Integration has received an outbound message coming from SAP Digital Manufacturing, it
sends back a message to SAP Digital Manufacturing to confirm the reception of the integration message.
In the Integration Message Dashboard of SAP Digital Manufacturing, the status of the integration message
changes from In Process to Delivered. The Request Producer iFlow puts the request message into the Request
JMS Queue, where the message is stored until it's called by the Request Consumer iFlow (asynchronous
processing). The Request Consumer iFlow processes the request message and sends the message to the
integrated SAP ERP or SAP S/4HANA system. Once the message has been sent successfully, the Response
Producer iFlow sends the Completed or Failed message to the JMS Response Queue. The Response Consumer
iFlow calls the message from the Response JMS Queue and sends it to SAP Digital Manufacturing. Then the
message status in the Integration Message Dashboard changes to Completed or Failed.

After modifying your integration setup as described in the prerequisites, you need to activate the CPI Async
mode, which is explained in this procedure:

Procedure

1. Navigate to the Manage Collaboration Directives app.

2. Choose the collaboration directive for which you want to enable the CPI Async mode.

The CPI Async mode is currently available for EWM Goods Receipt.
3. Switch on the CPI Async mode using the toggle switch.

Results

You've activated the CPI Async mode for your integration message.

As a check, perform the action that corresponds to the collaboration directive for which you've activated the
CPI Async mode. In the Integration Message Dashboard, you can now see that the status of your integration

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 111
message changes from In Process to Delivered and then to Completed or Failed. Depending on the processing
speed, you might not see the status Delivered, though.

In the Integration Message Dashboard, automatic retry and manual retry aren’t supported for messages in
status Delivered.

For more information on your monitoring options, see Monitoring CPI Async [page 114].

2.1.4.11.1 Advanced CPI Async Settings

Learn more about how to configure the integration artifacts needed for an asynchronous connection to SAP
Cloud Integration.

If the standard settings of the following integration artifacts don't suit your business needs, you'll find some
information here on the key parameters that can be modified.

Async Request Producer

You can modify the settings below, to be found in SAP Cloud Integration in your SAP S/4HANA Integration with
SAP Digital Manufacturing package, by choosing the Configure option for the artifact:

• Retention Threshold for Alerting (in d)

• Expiration Period (in d)

To know more about these settings, see Configure the JMS Receiver Adapter.

Async Request Consumer

You can modify the settings below, to be found in SAP Cloud Integration in your SAP S/4HANA Integration with
SAP Digital Manufacturing package, by choosing the Configure option for the artifact:

• Number of Concurrent Processes

• Retry Interval (in min)
• Maximum Retry Interval (in min)
• RetryCount

To know more about these settings, see Configure the JMS Sender Adapter.

JMS Request Queue

In SAP Cloud Integration, you find the JMS Request Queue (SAP_DM_INT_REQ_00) in your SAP S/4HANA
Integration with SAP Digital Manufacturing package as part of the Async Request Consumer artifact. You can
modify the following settings:

SAP Digital Manufacturing Integration Guide

112 PUBLIC SAP Digital Manufacturing for execution Integration
• Retry Interval
• Maximum Retry Interval

 Example

To illustrate the retry mechanism, the following values have been defined:

• Retry Interval is 3
• Exponential Backoff is selected
• Maximum Retry Interval is 15
• RetryCount is 6 (You make this setting in the configuration section of the Async Request Consumer
artifact.)

Given these settings, retry will happen after 3 min, 6 min, 12 min, 15 min, 15 min, and 15 min.

If RetryCount in the Async Request Consumer artifcact is set to 3 times, retry happens after 3 min, 6 min,
and 12 min. In this case, the Maximum Retry Interval interval isn't reached.

To know more about these settings, see Configure the JMS Sender Adapter.

Async Response Producer

You can modify the settings below, to be found in SAP Cloud Integration in your SAP S/4HANA Integration with
SAP Digital Manufacturing package, by choosing the Configure option for the artifact:

• Retention Threshold for Alerting (in d)

• Expiration Period (in d)

To know more about these settings, see Configure the JMS Receiver Adapter.

Async Response Consumer

You can find the settings below in SAP Cloud Integration in your SAP S/4HANA Integration with SAP Digital
Manufacturing package by choosing the Configure option for the artifact:

• Number of Concurrent Processes

• Retry Interval
• RetryCount

To know more about these settings, see Configure the JMS Receiver Adapter.

Related Information

Configure Asynchronous Messaging with Retry Using JMS Adaptor

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 113
2.1.4.11.2 Monitoring CPI Async

Learn how you can monitor the asynchronous connection from SAP Digital Manufacturing to SAP Cloud
Integration (Cloud Foundry environment).

Here an overview of the integration scenario:

You've got the following options for your monitoring:

Integration Message Dashboards

In the Integration Message Dashboard of SAP Digital Manufacturing, the status Delivered indicates that an
integration message for which CPI Async is activated has been received by SAP Cloud Integration, but not yet
processed or sent to the integrated SAP ERP or SAP S/4HANA system. Once SAP Cloud Integration has sent
the message to the integrated ERP system, the message status in the Integration Message Dashboard changes
to Completed. If the transmission wasn't successful the message changes to Failed.

Messages with status Delivered don't support automatic and manual retry.

The CPI Correlation ID of your message that you can find on the Message Information tab of Integration
Message Dashboard for outbound messages supporting CPI Async mode can help you to monitor your
integration scenario in SAP Cloud Integration.

SAP Cloud Integration

In the Operate and Monitor Integration Scenarios area ( ) of SAP Cloud Integration, you can monitor CPI
Async integration scenarios with regards to these aspects:

• The internal messages of SAP Cloud Integration that are related to your integration message
• The JMS queues used by SAP Cloud Integration to implement the asynchronous processing

Internal Integration Messages in SAP Cloud Integration

Under Monitor Message Processing All Integration Flows , enter the CPI Correlation ID of your integration
message under ID to find the internal messages that are related to your integration message. You can find the
CPI Correlation ID of your integration message in the Integration Message Dashboard.

SAP Digital Manufacturing Integration Guide

114 PUBLIC SAP Digital Manufacturing for execution Integration
If a message fails to be sent from the JMS Queue to the Request Consumer iFlow, the message is retried as
configured in the sender channel of the JMS queue. You can find detailed information about errors and the
retries in the message processing log. For more information, see Advanced CPI Async Settings [page 112].

JMS Queues

Under Manage Stores Message Queues , you'll find the following JMS queue messages that are used for
the asynchronous processing of messages:

• SAP_DM_INT_REQ_00, which represents the Request JMS Queue

• SAP_DM_INT_RESP_00, which represents the Response JMS Queue

By choosing Details next to JMS Resources, you can get information, such as Number of Queues, Capacity,
Queue Status.

By choosing a JMS queue message, you can access processing-relevant information and retry or delete JMS
queue messages.

 Note

There's a dead letter queue implemented for the JMS Request Consumer and the JMS Response
Consumer. For more information, see Configure the JMS Sender Adapter and Dead Letter Handling in
JMS Adapter .

2.1.5 Business Integration with SAP S/4HANA or SAP ERP

As an administrator, you set up the exchange of master data and transaction data between SAP S/4HANA or
SAP ERP. Moreover, if you have multiple ERP plants with the same identifier that represent different plants in
the real world, you can map these ERP plants to distinct plants in SAP Digital Manufacturing for execution using
the plant conversion feature.

SAP S/4HANA or SAP ERP is the system of record for master data, and SAP Digital Manufacturing for
execution is the system of record for all work-in-process (WIP) data.

• Integration of Master Data

You can transfer master data such as materials, BOMs, routings and work centers from SAP S/4HANA or
SAP ERP to SAP Digital Manufacturing.
• Integration of Transaction Data
You can enable bidirectional transfer of transaction data such as orders, inventory, batch and quality
inspection information.
• Plant Conversion
If you use the same plant identifier in multiple SAP ERP or SAP S/4HANA systems, you can use plant
conversion to map each plant identifier to one distinct plant in SAP Digital Manufacturing, so that
integration messages are transferred correctly.

 Example

You've got a plant A in ERP system 1 and a plant B in ERP system 2. They each represent a different
plant in the real world, but they have the same identifier. With plant conversion, you can perform the
following mapping to make sure that integration messages are transferred correctly:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 115
 Identifier in SAP ERP / SAP S/ Identifier in SAP Digital
Plant 4HANA Manufacturing

Plant A in ERP 1 1000 1000-A

Plant B in ERP 2 1000 1000-B

Related Information

Integration of Master Data [page 116]

Integration of Transaction Data [page 146]
Mapping Plants (Plant Conversion) [page 224]

2.1.5.1 Integration of Master Data

You can transfer master data from an SAP ERP or an SAP S/4HANA system to SAP Digital Manufacturing for
execution.

Use

The ERP system is the system of record for the master data and SAP Digital Manufacturing for execution is the
system of record for all WIP data.

You can transfer the following master data:

SAP ERP / SAP S/4HANA SAP Digital Manufacturing for execution

Material (incl. characteristics) Material

BOM BOM

Work center Work center

Routing Routing

Production version Material, recipe, BOM

QM defect code and group Nonconformance code and group

Usage Decision Code Usage Decision Code

Tool Equipment, tool

Recipe Recipe

Classification Classification

SAP Digital Manufacturing Integration Guide

116 PUBLIC SAP Digital Manufacturing for execution Integration
Prerequisites

The material of the BOM as well as the materials of the components and the work center are in SAP Digital
Manufacturing for execution.

Sequence Considerations

You must transfer materials before BOMs.

Implementation Considerations

Some functions may behave differently depending on the SAP ERP version used for integration with SAP Digital
Manufacturing for execution.

Related Information

Field Mapping for Integration to SAP ERP or SAP S/4HANA [page 202]
Allowed Characters for Key Fields [page 223]

2.1.5.1.1 Material Integration

You can transfer material master data from SAP ERP or SAP S/4HANA to create or update the corresponding
material record in SAP Digital Manufacturing for execution.

Before production orders can be created in SAP Digital Manufacturing for execution, the material to
manufacture must first exist in SAP ERP or SAP S/4HANA. The material integration process ensures that
a material created in SAP ERP or SAP S/4HANA and transferred to SAP Digital Manufacturing for execution
can be created and released.

In some cases, specific material properties may be required to manufacture the material. This information is
stored as classification data in SAP ERP or SAP S/4HANA and associated to the material master record. This
classification data must be maintained in SAP ERP or SAP S/4HANA and associated with the material. Then
the material and associated class data can be transferred to SAP Digital Manufacturing for execution as part of
the material transfer.

Transferring the material from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution ensures
consistent data so that inventory and WIP numbers are accurate between SAP ERP or SAP S/4HANA and SAP
Digital Manufacturing for execution during production.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 117
Integration information and constraints include the following:

• The material master is used by all components in the SAP ERP or SAP S/4HANA Logistics system.
• To facilitate integration, the data contained in the material master is required for the following functions in
SAP ERP or SAP S/4HANA:
• In Inventory Management, for goods movement postings and physical inventory
• In Production Planning and Control, for material requirements planning and scheduling

• The SAP ERP or SAP S/4HANA base unit of measure for material is used by SAP Digital Manufacturing for
execution material, inventory ID, bill of materials (BOM), and production order records and then reported
back to SAP ERP or SAP S/4HANA in confirmations.
• The SAP ERP or SAP S/4HANA discontinuation concept is not supported.
• The language of the material description value matches the SAP ERP or SAP S/4HANA plant language. If
the description in the SAP ERP or SAP S/4HANA plant language is not available, SAP Digital Manufacturing
for execution uses the value in the first available language.

Related Information

Manage Materials
Allowed Characters for Key Fields [page 223]

2.1.5.1.1.1 Transferring a Material Master

Learn how to create a material master in SAP ERP or SAP S/4HANA and transfer it to SAP Digital
Manufacturing for execution.

Prerequisites

• You've set up the Data Replication Framework (DRF) to send MATMAS03 IDocs from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution. Moreover, you've created and activated a replication
model with the outbound implementation for the material (194_1). For more information, see Data
Replication Framework [page 36].

 Note

For more information on the automatic distribution of changed master data, see 2515556 .

 Note

MATMAS05 is supported by SAP Digital Manufacturing for execution. For more information on the
supported material master versions, see 0003050090 .

SAP Digital Manufacturing Integration Guide

118 PUBLIC SAP Digital Manufacturing for execution Integration
Context

During production, material master data from SAP ERP or SAP S/4HANA is required for SAP Digital
Manufacturing for execution. Therefore, you need to transfer material master data from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution to create or update the corresponding material record in
SAP Digital Manufacturing for execution. Here you learn how to create a material master record in SAP ERP or
SAP S/4HANA and how to transfer it to SAP Digital Manufacturing for execution.

Procedure

1. Create a material master record in SAP ERP or SAP S/4HANA (see Creating a Material Master Record).

 Note

It's recommended to use at least one letter or one special character in the material number in SAP
ERP or SAP S/4HANA. By doing so, you make sure that SAP ERP or SAP S/4HANA doesn't fill up
the material number up to the full length with leading zeros, which can lead to challenges in certain
scenarios.

 Note

When you transfer master data to SAP Digital Manufacturing for execution, key fields can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 223].

2. Send the material master record to SAP Digital Manufacturing for execution.
We recommend using the Execute Data Replication transaction (transaction code – DRFOUT).

 Note

You can send a material using the Send Material (BD10) transaction.

3. To verify whether the MATMAS03 iDoc was transferred to SAP Digital Manufacturing for execution, you've
got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your MATMAS03 iDoc. For more information, see Integration Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your MATMAS03
iDoc. For more information, see Monitoring Message Processing.

Related Information

Integration Message Dashboard

Manage Materials
Mapping a Material [page 202]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 119
2.1.5.1.1.2 Transferring a Batch-Managed Material with Batch
Characteristics

You can transfer a batch-managed material master record together with batch characteristics assigned to
it from SAP ERP or SAP S/4HANA to create or update the corresponding material record in SAP Digital
Manufacturing for execution.

Prerequisites

• You've set up the Data Replication Framework (DRF) to send MATMAS03 IDocs from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution. Moreover, you've created and activated a replication
model with the outbound implementation for the material (194_1). For more information, see Data
Replication Framework [page 36].

 Note

For more information on the automatic distribution of changed master data, see 2515556 .

 Note

MATMAS05 is supported by SAP Digital Manufacturing for execution. For more information on the
supported material master versions, see 0003050090 .

• You've configured the Batch Management.

• You've assigned batch characteristics to the material.

Context

In production, you can’t guarantee that material features are exactly alike. For example, you cannot guarantee
that a certain color will always have the same shade. You can’t avoid minor differences between production
lots. To manage these differences, you must uniquely identify the individual production lots of the same
material and manage them separately in inventory.

A batch is a quantity of the material produced during a given production run. A batch represents a
homogeneous unit with unique specifications. A batch is a subset of the total quantity of a material held in
stock. The subset is managed from all other subsets of the same material.

Materials that require precise identification, for example, pharmaceutical products are identified and managed
in stock according to both, the material number and the batch number.

SAP Digital Manufacturing Integration Guide

120 PUBLIC SAP Digital Manufacturing for execution Integration
Procedure

1. Create a batch-managed material record in SAP ERP or SAP S/4HANA. For more information, see
Creating a Batch Master Record.

 Note

It's recommended to use at least one letter or one special character in the material number in SAP
ERP or SAP S/4HANA. By doing so, you make sure that SAP ERP or SAP S/4HANA doesn't fill up
the material number up to the full length with leading zeros, which can lead to challenges in certain
scenarios.

 Note

When you transfer master data to SAP Digital Manufacturing for execution, key fields can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 223].

2. Transfer the material master record to SAP Digital Manufacturing for execution.
We recommend using the Execute Data Replication transaction (transaction code – DRFOUT).

 Note

You can send a material using the Send Material (BD10) transaction.

3. To verify whether the MATMAS03 iDoc was transferred toSAP Digital Manufacturing for execution, you've
got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your MATMAS03 iDoc. For more information, see Integration Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your MATMAS03
iDoc. For more information, see Monitoring Message Processing.

Related Information

Integration Message Dashboard

Manage Materials
Mapping a Material [page 202]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 121
2.1.5.1.1.3 Transferring a Long Material Number

You can use a long material number record from SAP ERP or SAP S/4HANA to create or update the
corresponding material record in SAP Digital Manufacturing for execution.

Prerequisites

SAP ERP and SAP S/4HANA

• You've set up the Data Replication Framework (DRF) to send MATMAS03 IDocs from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution. Moreover, you've created and activated a replication
model with the outbound implementation for the material (194_1). For more information, see Data
Replication Framework [page 36].

 Note

For more information on the automatic distribution of changed master data, see 2515556 .

 Note

MATMAS05 is supported by SAP Digital Manufacturing for execution. For more information on the
supported material master versions, see 0003050090 .

SAP ERP

• You've activated the following business functions:

• DIMP_SDUD: Discrete Industries — Mill Products
• MGV_LAMA: Long Material Number
• You've run the ENLM (Enable Long Material Number) report.
• You've implemented SAP Notes 1795373 and 1871674 or applied the corresponding support
packages.

Context

The standard SAP ERP material number field uses the domain MATNR, which has an input, output, and
database length of 18 characters.

The long material number (MATNR_EXTERNAL) is the normal 18-character material number plus 22 additional
characters, allowing you to use 40-character material numbers.

SAP Digital Manufacturing Integration Guide

122 PUBLIC SAP Digital Manufacturing for execution Integration
For more information about sending long material number IDocs to SAP Digital Manufacturing for execution,
see Transfer of Long Material Number on the SAP Help Portal at http://help.sap.com.

Procedure

1. Create a material master record in SAP ERP with a name that contains more than 18 characters. For more
information, see Creating a Material Master Record.

 Note

When you transfer master data to SAP Digital Manufacturing for execution, key fields can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 223].

2. Send the material master record to SAP Digital Manufacturing for execution.
We recommend that you use the Execute Data Replication transaction (transaction code – DRFOUT).

 Note

You can send a material using the Send Material (BD10) transaction.

3. To verify whether the MATMAS03 iDoc was transferred to SAP Digital Manufacturing for execution, you've
got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your MATMAS03 iDoc. For more information, see Integration Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your MATMAS03
iDoc. For more information, see Monitoring Message Processing.

Related Information

Integration Message Dashboard

Manage Materials
Mapping a Material [page 202]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 123
2.1.5.1.1.4 Transferring a Backflushed Material

You can transfer backflushed materials from SAP ERP or SAP S/4HANA to create or update corresponding
material records in SAP Digital Manufacturing for execution.

Prerequisites

• You've set up the Data Replication Framework (DRF) to send MATMAS03 IDocs from SAP ERP or SAP S/
4HANA to . Moreover, you've created and activated a replication model with the outbound implementation
for the material (194_1). For more information, see Data Replication Framework [page 36].

 Note

For more information on the automatic distribution of changed master data, see 2515556 .

 Note

MATMAS05 is supported by SAP Digital Manufacturing for execution. For more information on the
supported material master versions, see 0003050090 .

Context

Normally, a goods issue is posted for every material that is withdrawn during order processing. When you use
backflushing, the goods issue posting is carried out later when the operation or phase is confirmed for the
material component. The backflush indicator that activates backflushing is set in SAP ERP or SAP S/4HANA
and transferred to SAP Digital Manufacturing for execution.

Procedure

1. Create a backflushed material record in SAP ERP or SAP S/4HANA. For more information, see Creating a
Material Master Record.

 Note

It's recommended to use at least one letter or one special character in the material number in SAP
ERP or SAP S/4HANA. By doing so, you make sure that SAP ERP or SAP S/4HANA doesn't fill up
the material number up to the full length with leading zeros, which can lead to challenges in certain
scenarios.

 Note

When you transfer master data to SAP Digital Manufacturing for execution, key fields can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 223].

SAP Digital Manufacturing Integration Guide

124 PUBLIC SAP Digital Manufacturing for execution Integration
2. Transfer the material master record to SAP Digital Manufacturing for execution.
We recommend that you use the Execute Data Replication transaction (transaction code – DRFOUT).

 Note

You can transfer materials using the Send Material (BD10) transaction.

3. To verify whether the MATMAS03 iDoc was transferred to SAP Digital Manufacturing for execution, you've
got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your MATMAS03 iDoc. For more information, see Integration Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your MATMAS03
iDoc. For more information, see Monitoring Message Processing.

Related Information

Integration Message Dashboard

Manage Materials
Mapping a Material [page 202]

2.1.5.1.2 Bill of Material Integration

You can transfer BOM master data from SAP ERP or SAP S/4HANA to create or update the corresponding
BOM record in SAP Digital Manufacturing for execution.

Purpose

A bill of material (BOM) in SAP ERP or SAP S/4HANA contains a list of all components belonging to an
assembly. This structured list of components can be transferred to SAP Digital Manufacturing for execution
to ensure that all the components are tracked during the manufacturing process. To avoid mistakes such as
duplicate entries of BOM data, use the BOM transfer functionality between SAP ERP or SAP S/4HANA and SAP
Digital Manufacturing for execution.

Each BOM is transferred as a single level BOM, so subassembly BOMs need to be transferred separately.
The structure of the BOM in SAP ERP or SAP S/4HANA may not match the structure of the BOM that
manufacturing would prefer. Review the structure of the BOM in SAP ERP or SAP S/4HANA to see if you need
to make any adjustments to the BOM structure.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 125
2.1.5.1.2.1 Configuring a Bill of Material (BOM)
You can transfer BOM master data from SAP ERP to create or update the corresponding BOM Master type
record in SAP Digital Manufacturing for execution.

For more information about data transferred using IDocs and the fields in SAP ERP that map to fields in
SAP Digital Manufacturing for execution, see the Field Mapping for the Integration with SAP ERP or S/4HANA
On-Premise section of this guide.

Prerequisites

SAP ERP

• You have set up ALE communication to create and transmit BOMMAT IDocs.
• You have transferred materials to SAP Digital Manufacturing for execution (see Material Transfer on the
SAP Help Portal at http://help.sap.com).

Procedural Steps

• 1. Create a bill of material master record in SAP ERP (see Steps in Creating a Simple Material BOM on the
SAP Help Portal at http://help.sap.com).

 Note

You need to assign components to phases, not to operations, in the integrated ERP system.

2. Send the BOM master record to SAP Digital Manufacturing for execution.
We recommend that you use the Material BOM Distribution transaction (transaction code – BD30).

 Note

The Bill of Material (BOM) can also be transferred to SAP Digital Manufacturing for execution with
the BOMMAT IDoc.

3. Verify the results in SAP Digital Manufacturing for execution. The corresponding BOM record is created
or updated in SAP Digital Manufacturing for execution (see Manage Bills of Materials).

2.1.5.1.2.2 Configuring a Bill of Material with Assembly

Operations
You can transfer BOM master data with assigned assembly operations from SAP ERP to create or update the
corresponding BOM Master type record in SAP Digital Manufacturing for execution.

The production processes for a product are described without reference to an order in routings. A routing
is a description of which operations (process steps) have to be carried out, and in which order, to

SAP Digital Manufacturing Integration Guide

126 PUBLIC SAP Digital Manufacturing for execution Integration
produce a material (product). The production processes describe the production resources or tools, material
components, and test equipment required.

When describing the production resources/tools used to produce a material, the work scheduler is supported
by the assignment of BOM items to operations.

This assignment means that the BOM items or materials are not reserved until the start point of the operation.
If you do not assign items to specific operations, the system automatically assigns all material components in
a BOM to the first operation when the order is opened. This means that they are all made available at the start
point of the first operation.

Prerequisites

SAP ERP

• You have created materials and routings in SAP ERP.

• You have transferred materials to SAP Digital Manufacturing for execution (see Material Transfer on the
SAP Help Portal at http://help.sap.com).
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .

Procedural Steps

• 1. Create a bill of material with allocated components in SAP ERP.

2. Send a BOM master record to SAP Digital Manufacturing for execution within a production order.
3. Verify the results in SAP Digital Manufacturing for execution. The corresponding BOM record is created
or updated in SAP Digital Manufacturing for execution (see Manage Bills of Materials).

2.1.5.1.2.3 Configuring a Shop Order-Specific Bill of Material

You can transfer BOM master data within a production order for make-to-order production.

In this case, SAP Digital Manufacturing for execution creates an order-specific BOM for use with this
production order.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 127
Procedural Steps

1. Create a finished material and transfer it to SAP Digital Manufacturing for execution.
2. Define a routing record in SAP ERP. You do not need to transfer it to SAP Digital Manufacturing for
execution.
3. Define a BOM record in SAP ERP. You do not need to transfer it to SAP Digital Manufacturing for execution.
4. Transfer work center records that were used when creating the routing from SAP ERP to SAP Digital
Manufacturing for execution.
5. Create and release a production order containing BOM and routing master data in SAP ERP.
6. In the Manage BOMs app, verify the results in SAP Digital Manufacturing for execution.

 Note

The Valid From value for the BOM is not transferred within a production order. It is available in the
BOMMAT IDoc only.

7. (optional) You can use the Integration Message Dashboard to verify that IDocs were received in SAP Digital
Manufacturing for execution. For more information, see Integration Message Dashboard.

For more information about make-to-order processing, see Make-to-Order Processing in ERP on the SAP Help
Portal at http://help.sap.com.

Related Information

Manage Bills of Materials

2.1.5.1.3 Production Version

As an optional step, you can replicate the production versions from SAP S/4HANA to SAP Digital
Manufacturing using SOAP.

Prerequisites

• You've transferred the material master to SAP Digital Manufacturing.

• You've created a production version in your SAP S/4HANA system.
• You've downloaded the WSDL file of service consumer ManufacturingProdnVersInfo_Out via t-code
SE80. Go to the repository browser, then PP_SOA_SERVICES Subpackages Enterprise Services
Service Consumers CLASCO_PRINT_MFG_PRODN_VERS . You can also download the WDSL file here:
Production Version . Choose Download API Specification and choose WSDL. You'll need to log in to get
the file.
• In the downloaded WSDL file, you've filled the address of the soap:address location using the SAP
Digital Manufacturing URL. To get the URL, go to the SAAS tenant of SAP Business Technology Platform

SAP Digital Manufacturing Integration Guide

128 PUBLIC SAP Digital Manufacturing for execution Integration
 Instances and Services , find the needed instance and choose the Keys button under the Credentials
column. Choose the URL for manufacturing-execution-integration. It should look like this:

 Sample Code

</wsdl:binding>
<wsdl:service name="CO_PPINT_MFG_PRODN_VERS_service">
<wsdl:port name="CO_PPINT_MFG_PRODN_VERS_port_soap11"
binding="tns:CO_PPINT_MFG_PRODN_VERS">
<soap:address location="https:// [URL for manufacturing-execution-
integration]/ws?X-Identity-Zone-Subdomain= [subdomain from the SAAS
tenant] "/>
</wsdl:port>
</wsdl:service>

Overview

You can create a production version in your integrated ERP to establish a relationship between your material
and one specific BOM and one specific routing/recipe out of all the BOMs and routings/recipes that exist
for this material. You can download this production version to SAP Digital Manufacturing using the procedure
described in this topic.

The production version download is optional and only needed if you want to be able to see the relationship
between master BOM and recipe/routing. This information can be seen in respective tabs of the Manage
Materials app and the Manage Routings/Recipes app accordingly. Otherwise, the production version isn't
relevant for the integration with SAP Digital Manufacturing because the BOM and routing/recipe are
transferred within the order.

Here the steps that you need to perform:

1. Upload the WSDL File in SOA Management [page 130]

2. Publish the WSDL File to the Service Registry [page 130]
3. Define a Profile [page 131]
4. Define a Provider System [page 132]
5. Define Logon Data to access SAP Digital Manufacturing [page 133]
6. Configure a Local Integration Scenario [page 134]
7. Accomplish Pending Tasks [page 135]
8. Configure the Web Service [page 135]
9. Create a Logical System [page 136]
10. Create an RFC Destination [page 136]
11. Set Up the Data Replication Framework [page 136]
12. Define a Replication Model [page 137]
13. Test your Scenario From the Integrated ERP system [page 137]
14. Check the Integration Scenario in SAP Digital Manufacturing [page 137]
15. Next Steps [page 137]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 129
Procedure

Upload the WSDL File in SOA Management

1. Open SOA Management using transaction SOAMANAGER).
2. In SOA Management, navigate to Tools WSDL Upload .
3. Choose Create and select Via File for the WSDL Base on the Upload WSDL screen.
4. Choose a name and description, for example DM_PROD_VERS.
5. Under WSDL Location, choose your WSDL file.
6. Choose OK.
Your WSDL with name DM_PROD_VERS has been created.
7. Choose  (display) to check the details of your your WSDL file:

Field Content Namespace

Service Binding CO_PPINT_MFG_PRODN_VERS http://sap.com/xi/PP/Global2

PortType Interface ManufacturingProdnVersInfo_Ou http://sap.com/xi/PP/Global2

t

Message Request ManufacturingProdnVersInfo http://sap.com/xi/PP/Global2

Interface Operation ManufacturingProdnVersInfo_Ou http://sap.com/xi/PP/Global2

t

WSDL Service CO_PPINT_MFG_PRODN_VERS_servi http://sap.com/xi/PP/Global2

ce

Endpoint URL https://..../ws?X-Identity-Zone-Sub­ http://sap.com/xi/PP/Global2

domain={...}

Publish the WSDL File to the Service Registry

1. Navigate to SOA Management Service Registry Publication of external WSDL .

2. On the Import WSDL tab, under Load WSDL from, select Uploaded and, under Name, search for the
production version WSDL for SAP Digital Manufacturing Integration, for example DM_PROD_VERS.
3. Choose Next.
4. On the Service Details tab, enter the Port Type Name and the Namespace. Make sure that the port type
name and namespace are identical to the service definition in t-code SPROXY. To find the t-code SPROXY,
go to the repository browser and search for PP_SOA_SERVICES Subpackages Enterprise Services
Service Consumers CLASCO_PRINT_MFG_PRODN_VERS . The information is in the Service Consumer
section.

 Example

• Port Type Name: ManufacturingProdnVersInfo_Out

• Namespace: http://sap.com/xi/PP/Global2
• Internal Name: DM_PROD_VERS

5. Choose Next.
6. On the Classifications tab, there are no entries needed.
7. Choose Next.

SAP Digital Manufacturing Integration Guide

130 PUBLIC SAP Digital Manufacturing for execution Integration
8. In the Service State tab, select Configured.
9. Choose Next.
10. On the Bindings tab, select the binding that will be published, for example CO_PPINT_MFG_PRODN_VERS.

 Example

Here's what you should find in the details of your binding:

Field Content

Access URL https://.../ws?X-Identity-Zone-

Subdomain={…}

Binding Name CO_PPINT_MFG_PRODN_VERS

Binding Namespace http://sap.com/xi/PP/Global2

Binding Description

Binding URL https:...srt/wsdl/ext_DM_PROD_VERS?sap-

client={…}

11. Choose Next.

12. On the Physical System tab, if the physical system is already defined, choose the existing one. Otherwise,
select New and enter the system name and enter any name for the host name. Select Third Party for the
system type.
13. Choose Next.
14. On the Summary tab, check the Service Details.

 Example

Field Content

WSDL URL https:...srt/wsdl/ext_DM_PROD_VERS?sap-

client={…}

WSDL URL ManufacturingProdnVersInfo_Out

Namespace http://sap.com/xi/PP/Global2

Internal Name DM_PROD_VERS

Description

Documentation URL

State Configured

15. Choose Finish.

Define a Profile

If the profile is already defined, you can skip this step.

1. Navigate to SOA Management Technical Administration Profiles .

2. Under Profiles, choose Create Profile.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 131
3. On the General tab, enter the profile name, description, and select Old Profile Mode.

 Example

Field Content

Name DM_NAME

Profile Description DM_NAME

Old Profile Mode Select this field.

4. Choose Next.
5. On the Security tab, under Authentication select User ID/Password for the authentication method. For
Transport Security, select Secured Communication.
6. Under Identifiable Business Context, choose No IBC Determination for the IBC Determination Type.
7. Choose Next.
8. On the Transport Settings tab, there are no settings required.
9. Choose Finish and confirm the activation of the profile.
The new profile is created and active.

Define a Provider System

If the provider system is already defined, you can skip this step.

1. Navigate to SOA Management Technical Administration Provider Systems .

2. On the General tab, choose Create to create a provider system.
3. Enter the provider system name and the profile name. Use the profile name that you created before.

 Example

Field Content

Name DM_NAME

Description DM_NAME

Profile Name Use the name of the profile that you've defined before,
for example DM_NAME.

Profile Version 1

 Note

The provider system name will be used in the Data Replication Framework as the business system in a
later step.

4. Choose Next.
5. On the Services Search Settings tab, make the following settings:

SAP Digital Manufacturing Integration Guide

132 PUBLIC SAP Digital Manufacturing for execution Integration
 Field Content

Use Services Registry Select the box

Services Registry SR_LOCAL

SLD Identifier Select the SLD Identifier from the table that corresponds
to your System ID, for example DM_NAME.

Logical System

Use WSIL Don't select this option

User for WSDL Access Enter the User for WSDL Access from the service registry
(using the credentials for the SAP S/4HANA user)

Password for WSDL Enter the password

Tolerant Search Select this box for the search granularity.

6. Choose Next.
7. On the Applications tab, choose Retrieve Business Applications.
Your business application is displayed in the table.
8. Choose Finish and confirm the activation of the provider system.
Your provider system is displayed in the provider system list.
9. Choose the Connection Test icon ( ) from the Actions column.
Check the results of the connection test.

Define Logon Data to access SAP Digital Manufacturing

If the logon data is already defined, you can skip this step.

1. Navigate to SOA Management Service Administration Logon Data Management .

2. On the Maintenance tab, choose Create.
3. Enter a name and description for the logon data, for example DM_LOGON.
4. Choose Next.
5. On the Credentials tab, enter the following elements:

Field Content

Authentication Methode User/Password or X.509

User Name Client ID of SAP Digital Manufacturing. To be found in the

service key.

Password Client secret of SAP Digital Manufacturing. To be found in

the service key.

X.509 SSL Client Certificate

Signature PSE

Encryption Certificate

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 133
  Note

To get the URL and basic authentication information for SAP Digital Manufacturing for execution go to
the SAAS tenant of the SAP Business Technology Platform, select the needed service instance, and
open the credentials by choosing the Keys button:
• manufacturing-execution-integration is the URL for SAP Digital Manufacturing
• clientid is the username
• clientsecret is the password

The manufacturing-execution-integration is the URL for SAP Digital Manufacturing. Use

the following format: https:// [URL for manufacturing-execution-integration]/ws?X-
Identity-Zone-Subdomain= [subdomain from the SAAS tenant]

6. Choose Finish and confirm the activation of the logon data.

Your logon data is displayed in the logon data list and has status Active. You can choose your logon data, for
example DM_LOGON, to check the details.

Configure the Local Integration Scenario

In this step, you can create a new scenario or add a new service group and binding assignment to an existing
scenario.

1. Navigate to SOA Management Service Administration Local Integration Scenario Configuration .

2. Choose Create.
3. On the General tab, enter the name of the business scenario and the description, for example
DM_PROD_VERS.
4. Choose Next.
5. On the Service Definitions tab, don't make any changes.
6. Choose Next.
7. On the Service Groups tab, choose Add to open the Add consumer value help.
8. Add the consumer uploaded from the external file. In the Search criteria, enter the following search criteria:

Field Content

Object Name contains *PRODN*

Maximum Number of Results 100

9. Choose Search.
10. In the Search Results section, select the correct consumer, for example PPINT_SOA_MFG_PRODN_VERS
and choose OK.
11. Choose Assign IBC Reference to assign a provider IBC reference.
12. In the Search criteria, enter the following search criteria:

Field Content

System contains System name, for example *DM*.

Type is Client

Leave the other criteria empty.

SAP Digital Manufacturing Integration Guide

134 PUBLIC SAP Digital Manufacturing for execution Integration
13. Choose Search.
14. In the Search Results, select the provider IBC reference and choose Assign to Service Group.
15. Choose Next.
16. On the Logon Data Assignment tab, provide your logon data:

 Example

Service Group Provider System Logon Data

PPINT_SOA_MFG_PRODN_VERS CLIENT / DM_NAME / DM_NAME DM_LOGON

17. Choose Finish and confirm the activation of the integration scenario.
18. Your local integration scenario, for example DM_PROD_VERS, is displayed in the Scenarios list as being
active.

Accomplish Pending Tasks

1. Navigate to SOA Management Service Administration Pending Tasks .

2. On the Pending Tasks, choose Switch to Expert Mode.
3. To find your tasks, filter by business scenario, for example DM_PROD_VERS, and set Type to Local
Configuration Requests.
4. Choose Rebuild List to filter the tasks.
5. Choose Process List in the Pending Tasks window to create a central logical post for the service group.

Configure the Web Service

This series of steps is about checking the configuration.

1. Navigate to SOA Management Service Administration Web Service Configuration .

2. In the Web Service Configuration window, choose the Design Time Object Search tab and enter your search
criteria:

 Example

Object Type is Consumer Proxy

Object Name contains *PRODN*

3. You should get the consumer proxy after the search, for example CO_PPINT_MFG_PRODN_VERS.
4. Choose the consumer proxy to see the destination.
The Configurations tab opens. Make sure that the state is Active for the provider system you defined.
5. In the Define Logical Ports section, select the business appl. ID (provider IBC reference) that you want to
configure.
6. Choose the  (edit) icon for details.
7. On the Transport Settings tab, choose Complete URL for the URL Access Path.
8. In the *URL field, enter the SAP Digital Manufacturing for execution URL.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 135
  Note

To get the URL and basic authentication information for SAP Digital Manufacturing for execution go to
the SAAS tenant of SAP Business Technology Platform, select the needed service instance, and open
the credentials by choosing the Keys button.

The manufacturing-execution-integration is the URL for SAP Digital Manufacturing. Use

the following format: https:// [URL for manufacturing-execution-integration]/ws?X-
Identity-Zone-Subdomain= [subdomain from the SAAS tenant]

9. For the Logon Language setting, choose Language of User Context.

10. For the Transport Binding section, choose the following values:

Field Content

Make Local Call No Call in Local System

*Transport Binding Type SOAP 1.1

Maximum Wait for WS Consumer 0

Optimized XML Transfer None

Compress HTTP Message Inactive

Compress Response True

11. Check if all pending tasks have been completed.

Create a Logical System

Create a new logical system using transaction BD54.

1. Use transaction BD54 to create a new logical system, for example DM_NAME.

Create an RFC Destination

1. In transaction SM59, create an RFC Destination of type G that points to SAP Cloud Integration that you
use exclusively for the production version, for example DM_NAME. For more information, see Build HTTP
Connection [page 31].
2. Choose Connection Test.
You can ignore an Error 500.

Setting Up the Data Replication Framework

Set up the Data Replication Framework for production version replication via t-code DRFIMG.

1. Open transaction DRFIMG.

2. Choose Define Technical Settings for Business Systems.
3. Choose Define Business Systems.
4. Under General, enter the following parameters:

SAP Digital Manufacturing Integration Guide

136 PUBLIC SAP Digital Manufacturing for execution Integration
 Name Name of the provider system defined in SOAMANAGER, for
example DM_NAME

Description DM_NAME

Profile Name Name of the profile defined in SOAMANAGER, for example

DM_NAME

Profile Version 1

Define a Replication Model

Assign the business system to a combination of a replication model and the outbound implementation
FIN0002_PV. You can reuse a previously created replication model for SAP Digital Manufacturing scenarios
or you can create a new one.

1. In the SAP Reference IMG, navigate to Cross Application Components Processes and Tools
for Enterprise Applications Master Data Governance Central Governance General Settings Data
Replication Define Custom Settings for Data Replication Define Replication Models .
2. Under Define Replication Model, create a replication model, for example DM_NAME by choosing New Entries.
3. Select your replication model, for example DM_NAME, and double-click Assign Outbound Implementation.
4. Select FIN0002_PV from the value help and save.
5. Choose Assign Target Systems for Repl. Model /Outb.Impl.
6. Assign your business system, for example DM_NAME, and save.
7. Choose Assign Outbound Parameter.
8. Assign the Outbound Parameter Value 10 to the Outbound Parameter PACK_SIZE_BULK and save.
9. Choose Define Replication Model.
10. In the Replication Model list, select your replication model, for example DM_NAME.
11. Choose Activate.
Your replication model is activated.

Test your Scenario From the Integrated ERP system

You can test your integration scenario with transaction DRFOUT.

1. Open transaction DRFOUT.

2. Under Replication Model, enter the name of your replication model, for example DM_NAME.
3. Under Outbound Implementation, enter FIN0002_PV.
4. Under Replication Mode, choose Manual Replication Filter Criteria.
5. Set your filter criteria for Material and Plant, and save.
6. Choose Execute to perform the test.

Check the Integration Scenario in SAP Digital Manufacturing

In SAP Digital Manufacturing, you can check in the Integration Message Dashboard whether or not your
Production Version Download has been successful.

If the transfer was successful, you can also see the production version in the Manage Materials app or the
Manage Routings/Recipes app by searching with your material.

Next Steps
Download the routing master data, which already contains the master BOM, to SAP Digital Manufacturing.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 137
For more information on configuring a service group in SOAMANAGER, see Configuring a Service Group .

2.1.5.1.4 Work Center Integration

You can transfer work center master data that is created or updated in SAP ERP or SAP S/4HANA to SAP
Digital Manufacturing for execution.

A work center is an area at a site at which inventory is manufactured or processed. Work centers are used to
divide the portions of a routing along functional work lines.

A work center in SAP ERP or SAP S/4HANA can represent either a work center or a resource in SAP Digital
Manufacturing for execution, depending on how the work center is configured. Configuring the work center
in SAP ERP or SAP S/4HANA allows for capacity planning to take place. To keep the number of resources
and work centers in SAP Digital Manufacturing for execution consistent with the capacity that is defined as
available in SAP ERP or SAP S/4HANA, you can transfer the defined production work centers.

Integration information and conditions include:

• Operations are carried out at a work center in SAP ERP or SAP S/4HANA.
• The data stored in the work center is used in SAP ERP or SAP S/4HANA for the following:
• Routings
Work centers are assigned to operations in task lists. If default values are changed in a work center, the
changes are effective in the task list in case a reference indicator has been set for the default value.
• Work center hierarchies
Work centers can be arranged in hierarchies. Hierarchies are used in capacity planning to cumulate
available capacities and capacity requirements in a hierarchy work center.

Related Information

Manage Work Centers

2.1.5.1.4.1 Transferring a Work Center

You can transfer work center master data that is created or updated in SAP S/4HANA to SAP Digital
Manufacturing for execution.

Shifts and shift assignments are transferred with work center capacities from SAP S/4HANA to SAP Digital
Manufacturing for execution.

SAP Digital Manufacturing Integration Guide

138 PUBLIC SAP Digital Manufacturing for execution Integration
Prerequisites

SAP S/4HANA
• You have defined individual capacities using work center capacity assignments (see Creating Individual
Capacities [page 140]).

 Note

The name of a work center (for example, ProdWC) is transferred to SAP Digital Manufacturing for
execution and used for the work center that is created there. Moreover, there's one resource created
that has the same name as the work center. The names of the capacities of this work center are not
used, though. Instead, SAP Digital Manufacturing for execution creates a resource for each capacity
and derives its name from the work center name following the naming pattern WCname_NUMBER (for
example, ProdWC_1).

 Example

Target Object in SAP Naming in SAP

Source Object in SAP S/ Naming in SAP S/ Digital Manufacturing Digital Manufacturing
4HANA 4HANA for execution for execution

Work Center ProdWC Work Center ProdWC

Resource (Default) ProdWC

Capacity Technical Name: Resource Technical Name:

Station_a ProdWC_1

Description: STATION_A Description: STATION_A

Capacity Technical Name: Resource Technical Name:

Station_b ProdWC_2

Description: STATION_B Description: STATION_B

Capacity Technical Name: Resource Technical Name:

Station_c ProdWC_3

Description: STATION_C Description: STATION_C

• You have set up ALE communication to create and transfer LOIWCS IDocs.
• You have defined the Data Replication Framework to replicate LOIWCS03 IDocs.
• Ensure that a user used for the master data transfer has the SAP_BR_PRODN_ENG_DISC role.
• Use the Master Data Transfer transaction (transaction code POIM) or Execute Data Replication transaction
(transaction code DRFOUT) to transfer the master data.
• You can transfer work centers along with standard value keys (see SAP Note 2996757 ).

 Note

You can download the multi-language descriptions of the standard value keys
(CO_MES_SVK_WITH_LANGUAGE). For more information, see 3134473 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 139
Procedural Steps

1. Log on to the SAP S/4HANA system.

2. Open the Master Data Transfer (POIM) transaction.
3. Specify Optimization System (logical system / target system).
4. Select a work center / plant for transfer.
5. Choose Execute.
6. Verify the results in SAP Digital Manufacturing for execution. You can view the transferred work centers in
the Manage Work Centers app.
Work center capacity updates in SAP S/4HANA result in the corresponding changes in SAP Digital
Manufacturing for execution.
You can view the capacity category in the Manage Work Centers app. ERP Work Center is set to Yes for work
centers transferred from SAP S/4HANA.
You can view the transferred shifts assigned to work center capacities in the Manage Resources app.

Related Information

Manage Work Centers

Manage Resources

2.1.5.1.4.2 Creating Individual Capacities

You can create individual capacities using work center capacity assignments in SAP S/4HANA.

Procedure

1. Log on to the SAP S/4HANA system.

2. Open the Create Work Center (CR01) transaction.
3. Enter a plant, a work center, and a work center category.
4. Choose Next Screen.
5. Enter a work center description, press Enter .
6. On the Basic Data tab, select or enter Person Responsible, Usage, and Standard Value Key.
7. On the Capacities tab, select or enter Capacity Category.
8. Scroll down and choose the Capacity button.
9. Select Capacity Responsible, enter Capacity Utilization and No. Ind. Capacities, select Capacity Base Unit.
10. In the upper menu, choose GoTo and select Individual Capacities.
11. Choose the Back arrow button to the left of the SAP icon.
12. Choose Intervals and Shifts.

SAP Digital Manufacturing Integration Guide

140 PUBLIC SAP Digital Manufacturing for execution Integration
13. In the Default Values section, you can add the default Start, End, and Length of the break.
14. In the upper right corner, choose Insert Interval.
15. Select the Valid From date and press Enter .
16. Select the Valid To date and press Enter .
17. You can edit Start Time, End Time, and Length of the break for each day.
18. Choose Save.

Results

You can verify this transaction in the Integration Message Dashboard app in SAP Digital Manufacturing.

Related Information

Transferring a Work Center [page 138]

2.1.5.1.5 Transfer of QM Defect Code Groups and Codes

You can transfer Quality Management (QM) defect code groups and codes from SAP ERP or SAP S/4HANA to
SAP Digital Manufacturing for execution using the Manage Nonconformance Groups app.

Prerequisites

You have set up integration with SAP ERP or SAP S/4HANA (see Technical Integration with SAP S/4HANA or
SAP ERP [page 14])

Procedural Steps

1. In the Manage Nonconformance Groups app, choose Sync QM Groups.

2. Search for production-relevant QM defect code groups that exist in the connected SAP ERP or SAP S/
4HANA system.
You can check which QM code groups have been previously transferred by selecting Yes in the Previously
Synched dropdown.

 Note

The selection is restricted to catalog type 9 (defect types) in SAP ERP or SAP S/4HANA. Only
released code groups are displayed and can be transferred.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 141
3. Select one or more QM code groups and choose Sync. The selected QM code groups are transferred to
SAP Digital Manufacturing for execution.

QM defect groups and codes that you transfer from SAP ERP or SAP S/4HANA are marked with ERP Group
and ERP Code indicators set to Yes in the Manage Nonconformance Groups and Manage Nonconformance
Codes apps. A nonconformance code that originates from SAP ERP or SAP S/4HANA is represented by a
concatenated name (QM defect code and code group).

When you log a nonconformance code originated from SAP S/4HANA, it is automatically transferred to SAP
S/4HANA and a generic defect record is created.

Related Information

Manage Nonconformance Groups

Manage Nonconformance Codes

2.1.5.1.6 Routing Integration

You can transfer routings from SAP ERP or SAP S/4HANA to create or update corresponding routing and
operation activities in SAP Digital Manufacturing for execution.

In SAP ERP or SAP S/4HANA, the routing defines the key aspects of inventory-related information. The
information includes the consumption points of components during the manufacturing process as well as the
final confirmation step when the manufactured material is posted to the finished goods inventory.

If an SAP ERP routing uses sub-operations, then ERP routing operations are mapped to SAP Digital
Manufacturing routing operation groups and SAP ERP sub-operations are mapped to SAP Digital
Manufacturing operation activities.

• The routing defines the operations (process steps) and the sequence of operations required to produce
a material (product). Routings are used as a template for production orders and planned orders (repetitive
manufacturing) as well as a basis for product costing.

• The data stored in the routing serves as a basis for production planning activities in SAP ERP or SAP
S/4HANA such as the following:

• In Materials Management to plan the usage of materials and external operations

• In Production Planning and Control to plan the usage of work centers
• In Quality Management to plan quality inspections for production activities

When you transfer routings to SAP Digital Manufacturing, the system creates two objects:

• Operation activity
The description of the operation activity uses the short text defined for the operation in SAP ERP or SAP
S/4HANA.
• Routing
• SAP Digital Manufacturing for execution defaults the first routing to version A and increments an
additional integer value for subsequent updates. For example: A-01, A-02.

SAP Digital Manufacturing Integration Guide

142 PUBLIC SAP Digital Manufacturing for execution Integration
 A new routing version is created when you add operations or change one of the following in SAP ERP or
SAP S/4HANA:
• Operation number
• Operation control key
• Operation short text

 Note

Operation activity master records can be created based on the SAP ME Operation and Version fields on the
Operation record in the routing configuration.

Related Information

Manage Routings/Recipes

2.1.5.1.6.1 Transferring a Standard Routing

You can transfer routing master records from SAP ERP or SAP S/4HANA to create or update corresponding
routing and operation records in SAP Digital Manufacturing for execution.

Prerequisites

SAP ERP or SAP S/4HANA

• You have created work centers with plant and production-relevant data in SAP ERP or SAP S/4HANA. You
have transferred the work centers to SAP Digital Manufacturing for execution.

 Note

Creating and setting up a work center is a required step for transferring routings.

• You have created a BOM and a routing for the produced material.
• You have transferred materials to SAP Digital Manufacturing for execution.
• You have set up ALE communication to create and transmit LOIROU IDocs.
• You have defined the Data Replication Framework (DRF) replication model to replicate LOIROU IDocs. For
information about the SAP ERP versions supporting DRF, see SAP Note 1793291

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 143
Procedural Steps

1. Create a routing master record in SAP ERP or SAP S/4HANA.

2. Transfer the routing master record to SAP Digital Manufacturing for execution using the Execute Data
Replication transaction (transaction code – DRFOUT).

 Note

Make sure that you have created and activated a replication model with the outbound implementation
for the routing (223_1).

3. Verify the result in SAP Digital Manufacturing for execution in the Manage Routings/Recipes app.

Related Information

Manage Routings/Recipes

2.1.5.1.7 Recipe Integration

You can transfer recipe master records from SAP ERP or SAP S/4HANA systems to SAP Digital Manufacturing
for execution.

Prerequisites

SAP ERP or SAP S/4HANA

• You have created work centers with plant and production-relevant data in the SAP ERP or SAP S/4HANA
system. For more information, see Creating, Changing and Displaying Work Centers on the SAP Help Portal.
You have transferred the work centers to SAP Digital Manufacturing for execution.
• You have created a BOM and a recipe for the produced material.
• You have transferred materials to SAP Digital Manufacturing for execution.
• You have set up ALE communication to create and transfer an LOIROU04 IDoc.
• You have created and activated a replication model with an outbound implementation for recipes (223_1).
For more information, see Data Replication Framework [page 36].

Procedure

• Create a recipe master record in SAP ERP or SAP S/4HANA.

• Transfer the recipe master record to SAP Digital Manufacturing for execution.
We recommend using the Execute Data Replication transaction (transaction code – DRFOUT).

SAP Digital Manufacturing Integration Guide

144 PUBLIC SAP Digital Manufacturing for execution Integration
• Verify the results in the Manage Routings/Recipes and the Integration Message Dashboard apps in SAP
Digital Manufacturing for execution.

Related Information

Integration Message Dashboard

Manage Routings/Recipes

2.1.5.1.8 Tool Integration

You can transfer PRTs from SAP ERP or SAP S/4HANA to create the corresponding tool record in SAP Digital
Manufacturing for execution.

Unlike machines and fixed assets, production resources and tools (PRTs) are movable (not stationary)
operating resources that are required to perform an activity and can be used repeatedly. There are several
categories of PRTs in SAP ERP or SAP S/4HANA system. The category determines the characteristics and
business functions that a PRT can have.

The PRTs can be assigned to operations / activities. You can use the assignment to track PRT usage during the
production.

Before the tools can be scheduled and logged in SAP Digital Manufacturing for execution, the corresponding
PRTs must first exist in SAP ERP or SAP S/4HANA and they need to be assigned to operations.

Integration Overview

The following table describes the supported PRT types and how tools are created for each type.

PRT Type Tool Integration

Equipment PRT The system automatically creates cor­ Equipment PRTs are transferred
responding equipment tools in the from ERP to SAP Digital
Manage Tools app when equipment Manufacturing for execution through
PRTs are downloaded from SAP ERP. the EQUIPMENT_CREATE02 IDoc. For
more details, see Transferring a Tool
[page 146].

Material PRT Unlike the equipment PRT, the system Material PRTs are transferred from ERP
does not create tools when material to SAP Digital Manufacturing for execu­
PRTs are downloaded from ERP. You tion together with the respective mate­
need to manually create respective rial master data.
tools in the Manage Tools app.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 145
2.1.5.1.8.1 Transferring a Tool

This section describes how to transfer equipment PRTs from SAP ERP to SAP Digital Manufacturing for
execution to create corresponding tools in SAP Digital Manufacturing for execution.

Prerequisites

SAP ERP

• You have set up ALE communication to create and transmit an EQUIPMENT_CREATE02 IDoc.
• You have created and activated a replication model with outbound implementation for the equipment
(183_1). For more information, see Data Replication Framework [page 36].

SAP Digital Manufacturing

The referenced material (if there are any) of the equipment PRT has already been transferred from SAP ERP to
SAP Digital Manufacturing.

Procedure

1. Create an equipment PRT in SAP ERP.

2. Send the equipment PRT to SAP Digital Manufacturing for execution.
We recommend using the Execute Data Replication transaction (transaction code – DRFOUT).
3. Verify results in the Manage Tools app or the Integration Message Dashboard in SAP Digital Manufacturing
for execution. For more information, see Manage Tools or Integration Message Dashboard.

2.1.5.2 Integration of Transaction Data

To integrate transaction data, transaction data is transferred from an SAP ERP or SAP S/4HANA system to the
SAP Digital Manufacturing for execution system and then back to SAP ERP

You can integrate the following transaction data with SAP ERP:

Transaction Data Integration

SAP ERP SAP Digital Manufacturing for execution

Production order Production order with routing

Production order with BOM Production order with BOM and routing

SAP Digital Manufacturing Integration Guide

146 PUBLIC SAP Digital Manufacturing for execution Integration
SAP ERP SAP Digital Manufacturing for execution

Production order with a storage location assignment Production order with storage location assignment

 Note
There is no UI for storage location on the order or man­
age-storage location used goods receipt

Production order with routing Production order with routing

Routing with document info record (only for order specific Order specific routing with work instruction
routing)

Production order with serial numbers Production order with serial numbers and planned SFCs

Production order with document info record Production order with work instruction

 Note
The work instruction will be created with the order and
attached at the order level. It will be displayed in the
work center POD plugin work instruction for the specific
order.

Production order with batch number Production order with batch number

A receipt for finished goods

Production order with schedule information Production shop order with schedule information that is
used in the Dispatching & Monitoring app

Production order with operation-level schedule information Production shop order with schedule information

Production order with work center assignment on routing Production shop order with work center assignment on rout­
step and operation ing step and operation

Confirmation Completion of SFC

Consumption Component assembling

Scrap Scrap

You can integrate the following transaction data:

• Production order
• Production order confirmation
• Production order yield confirmation
• Component scrap confirmation for production order

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 147
2.1.5.2.1 Production Order Integration

You can transfer production order data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for
execution.

This function supports long material numbers.

Order integration between SAP ERP or SAP S/4HANA and SAP Digital Manufacturing for execution provides
the control point from production planning to the order. The transfer of the order and integration of the order
confirmations are critical to maintaining order level data synchronization between the two systems.

The production order, typically converted from a planned order output of an MRP run in SAP ERP or SAP S/
4HANA and used to launch discrete production, is transferred to the SAP Digital Manufacturing for execution
system for release as a production order.

The order in SAP Digital Manufacturing for execution communicates to SAP ERP or SAP S/4HANA the
confirmation of yield and scrap as production is done on the shop floor. If components have been assembled,
they're included in the confirmation so that they can be issued to the order in SAP ERP or SAP S/4HANA.

 Note

To distinguish between a discrete industry order and a process industry order, when this differentiation is
required for the internal execution logic, SAP Digital Manufacturing relies on the Auto complete and confirm
flag that is set on material level in the integrated ERP system. If this flag is active, the downloaded order is
considered to be a discrete industry order and handled accordingly. If this flag isn't active, the downloaded
order is treated as a process industry order and handled accordingly.

 Note

In the integrated ERP system, implement BADI CO_MES_INT_REDISTRIBUTION to make sure that the
release notification (RMES) isn’t replicated back to SAP Digital Manufacturing after the release of the order
in SAP Digital Manufacturing. For more information, see 2165261 .

When you release an order in the Manage Orders app in SAP Digital Manufacturing, a release notification
(RMES) is sent to the integrated ERP system. If you don’t use the BADI CO_MES_INT_REDISTRIBUTION on
the ERP side, the ERP system will then communicate an order change to SAP Digital Manufacturing, which
can cause issues.

For more information about the implementation of the release notification (RMES) in your ERP system, see
Production Order (Version 2) and Activate and Maintain Services.

Related Information

Manage Orders
Order Statuses
How Order Statuses Change in a Business Scenario

SAP Digital Manufacturing Integration Guide

148 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.1.1 Transferring a Production Order

This section describes how to transfer production order data from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution to create or update the corresponding production order record in SAP Digital
Manufacturing for execution.

Prerequisites

SAP ERP or SAP S/4HANA

• You have transferred the material master records for the produced material and all the components.
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings/Recipes)
• You have created and sent work centers to SAP Digital Manufacturing for execution.
• You have set up ALE communication to create and transmit LOIPRO IDocs.
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing

• (Optional) You have imported BOM and routing master data from SAP ERP.
BOM and routing masters that are sent from SAP ERP to SAP Digital Manufacturing for execution prior
to the production order download allow additional manual configurations to happen inside of SAP Digital
Manufacturing for execution. This prerequisite is optional because you can create the BOM and routing
master in SAP Digital Manufacturing for execution directly from the production order download.
• You have enabled the artifact ProductionOrder LOIPRO05 process request V2 in SAP Cloud
Integration to use LOIPRO05 V2. For more information, see 3115603 .

Procedural Steps

1. Create or update a production order manually (transaction CO01 and CO02) or automatically by converting
a planned order (see Creating a Production Order on the SAP Help Portal at http://help.sap.com).
2. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 149
3. Verify the results in SAP Digital Manufacturing for execution.

The system creates or updates the production order based on the data received from Tools with Engineering
status can’t be used in Production/POD.

 Note

Before releasing an order to the shop floor in the Manage Orders app in SAP Digital Manufacturing, you can
update it from your integrated ERP system. The updating options you have vary depending on the order
type and the integrated ERP system. For more information, see Updating Orders Before the Release [page
185].

When the order is released in SAP Digital Manufacturing for execution, shop floor operators can see the
operation start and end time in the POD worklist.

Related Information

Manage Orders
Increasing the Build Quantity for Overproduction

2.1.5.2.1.2 Configuring a Production Order with a BOM

and Routing (Make-to-Stock or Make-to-Order
Manufacturing)
This section describes how to transfer a production order with BOM and routing from SAP ERP to create or
update the corresponding BOM with defined assembly operations that are assigned to the production order in
SAP Digital Manufacturing for execution.

Make-to-stock manufacturing is a manufacturing process in which you manufacture products for stock based
on demand forecasts.

Make-to-order manufacturing is a manufacturing process in which manufacturing starts only after an order
from a customer is received. Forms of make-to-order manufacturing vary. For example, an assembly process
can start when there's actual demand or manufacturing starts with development planning.

If no sales order is attached to the production order, the order is used for make-to-stock manufacturing. The
system reuses the existing standard BOM and routing if they match the BOM and routing in the production
order. Otherwise, the system creates a new standard BOM and routing or a new version of the existing BOM
and routing.

• You can transfer co-products and by-products defined for the BOM in SAP ERP to SAP Digital
Manufacturing for execution with a production order.
• You can transfer alternate components defined for the BOM in SAP ERP to SAP Digital Manufacturing
for execution with a production order. Among the components in an alternate group, the component
with the highest priority becomes the primary component and the other components become alternate
components.
• You can download the complete phantom hierarchy including the phantom components and the phantom
members from SAP ERP to SAP Digital Manufacturing for execution.

SAP Digital Manufacturing Integration Guide

150 PUBLIC SAP Digital Manufacturing for execution Integration
Prerequisites

SAP ERP

• This function works only with SAP ERP 6.05 or later with the activated business function
LOG_PP_MES_INT_02 (configuration type C and D).
• You've transferred the material master records for the produced material and all the components.
• You've created a BOM and a routing for the produced material (see Manage Bills of Materials and Manage
Routings/Recipes).
• You've created and transferred work centers to SAP Digital Manufacturing for execution.
• You've set up ALE communication to create and transfer LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You've defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs (in
Customizing for Production, choose Integration with a Manufacturing Execution System Basic Settings
for MES Integration . For information about the SAP ERP versions supporting DRF, see SAP Note
1793291 .
• You've defined unique ISO codes for every unit of measure.

Procedural Steps

1. Create or update a production order containing the BOM and routing master data in SAP ERP.
2. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

 Note

SAP ERP 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B) distributes
production orders automatically upon release based on the customized settings.

If you're using SAP ERP 6.00 – 6.04 (configuration type A), you transfer the production order using the
transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments of
the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 aren't supplied when distributing using the POIT
transaction.

3. Verify the results in SAP Digital Manufacturing for execution.

The system creates or updates the production order, BOM, and routing records in SAP Digital Manufacturing
for execution based on the data received from SAP ERP.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 151
2.1.5.2.1.3 Configuring a Production Order with Serial
Numbers

This section describes how to transfer serial numbers assigned to a production order from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing to create corresponding SFCs assigned to the production order in SAP
Digital Manufacturing.

• In SAP ERP or SAP S/4HANA, serial numbers are unique at the material level.
• In SAP Digital Manufacturing, an SFC, which stands for shop floor control unit, is a unique identifier that
represents an item to be produced on the shop floor.
• In an SAP ERP or SAP S/4HANA production order, you can define serial numbers for the product to be
produced.
• These serial numbers within the production order are distributed automatically to SAP Digital
Manufacturing.
• When a production order with serial numbers is imported from SAP ERP or SAP S/4HANA, the
corresponding production order and SFCs are created using the numbering pattern of <Material
Number>-<Serial Number>. These SFCs are used when you release the production order in SAP Digital
Manufacturing.
• The number of the transferred serial numbers equals the Quantity value of the production order (in
Customizing for Production, choose Integration with a Manufacturing Execution System Integrate
Production Order with a Manufacturing Execution System Check Serial Numbers in MES Production
Orders ).

Prerequisites

SAP ERP or SAP S/4HANA

• You have maintained a serial number profile for the header material so that a production order can
contain serial numbers (in Customizing for Logistics, choose Materials Management Material Master
Material Change Work Scheduling ).
• You have transferred the material master records for the produced material and all the components (see
Material Transfer on the SAP Help Portal at http://help.sap.com).
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings/Recipes).
• You have set up ALE communication to create and transmit LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP or SAP S/4HANA versions supporting
DRF, see SAP Note 1793291 .
• This function works with SAP ERP or SAP S/4HANA 6.05 and higher with the activated business function
LOG_PP_MES_INT_02. For information about the SAP ERP or SAP S/4HANA versions supporting DRF, see
SAP Note 1793291 .

SAP Digital Manufacturing Integration Guide

152 PUBLIC SAP Digital Manufacturing for execution Integration
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing

• (Optional) You have imported BOM and routing master data from SAP ERP or SAP S/4HANA.

 Posting Instructions

BOM and routing masters that are sent from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing
prior to the production order download allow additional manual configurations to happen inside of
SAP Digital Manufacturing. This prerequisite is optional because you can create the BOM and routing
master in SAP Digital Manufacturing directly from the production order download.

Procedural Steps

1. Create or update a production order containing serial numbers manually (transaction CO01 and CO02) or
automatically by converting a planned order.
2. SAP ERP or SAP S/4HANA 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02
distributes production orders automatically upon release based on the Data Replication Framework
(DRF) filter settings (see Data Replication Framework [page 36]). Changes to the order are distributed
immediately after the initial distribution.

 Note

SAP ERP or SAP S/4HANA 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B)
distributes production orders automatically upon release based on customized settings.

If you use SAP ERP or SAP S/4HANA 6.00 – 6.04 (configuration type A), you transfer the production order
using the transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments
of the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 are not supplied when distributing using the
POIT transaction.

3. Verify the results in SAP Digital Manufacturing.

SAP Digital Manufacturing creates or updates the production order with SFCs based on the data received from
SAP ERP or SAP S/4HANA.

For more information, see Transfer of Production Order with Serial Numbers on the SAP Help Portal at http://
help.sap.com.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 153
2.1.5.2.1.4 Configuring a Production Order with a Batch
Number

This section describes how to transfer production order data with a batch number from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution to create or update the corresponding production order
record in SAP Digital Manufacturing for execution.

Certain material features cannot always be guaranteed to be exactly alike in production. For example, you
cannot guarantee that a certain color will always have the same shade. Minor differences between production
lots cannot be avoided. You need to be able to uniquely identify the individual production lots of the same
material and manage them separately in inventory.

Materials that require such precise identification, for example pharmaceutical products, are identified and
managed in stock according to both, the material number and batch number.

A batch is a quantity of the material produced during a given production run. A batch represents a
homogeneous unit with unique specifications. A batch is a subset of the total quantity of a material held in
stock. The subset is managed from all other subsets of the same material.

Prerequisites

SAP ERP or SAP S/4HANA

• You have transferred the batch managed material master records for the produced material and all the
components (see Material Transfer on the SAP Help Portal at http://help.sap.com).
For more information about creating batch managed material master record, see the Configuring Batch
Managed Material section of this guide.
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings/Recipes).
• You have created and sent work centers to SAP Digital Manufacturing for execution.
• You have set up ALE communication to create and transmit LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .
• This function works with SAP ERP 6.05 and higher with activated business function LOG_PP_MES_INT_02.
For information about the SAP ERP versions supporting DRF, see SAP Note 1793291 .
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing for execution

• (Optional) You have imported BOM and routing master data from SAP ERP or SAP S/4HANA.

SAP Digital Manufacturing Integration Guide

154 PUBLIC SAP Digital Manufacturing for execution Integration
  Posting Instructions

BOM and routing masters that are sent from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing
for execution prior to the production order download allow additional manual configurations to happen
inside of SAP Digital Manufacturing for execution. This prerequisite is optional because you can create
the BOM and routing master in SAP Digital Manufacturing for execution directly from the production
order download.

Procedural Steps

1. Create a batch-managed material record in SAP ERP or SAP S/4HANA (see Transferring a Batch-Managed
Material with Batch Characteristics [page 120]).
2. Create or update a production order with a defined batch number manually (transaction CO01 and CO02.
3. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

 Note

SAP ERP 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B) distributes
production orders automatically upon release based on customized settings.

If you use SAP ERP 6.00 – 6.04 (configuration type A), you transfer the production order using the
transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments
of the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 are not supplied when distributing using the
POIT transaction.

4. Verify the results in SAP Digital Manufacturing for execution.

SAP Digital Manufacturing for execution creates or updates the production order with SFCs based on the data
received from SAP ERP or SAP S/4HANA.

Related Information

Manage Materials

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 155
2.1.5.2.1.5 Configuring a Production Order with Document
Info Records

This section describes how to transfer document info records attached to a production order in SAP ERP to
create a production order and work instructions attached to the order operations in SAP Digital Manufacturing.

You can use this function with SAP ERP 6.0 EHP 6 or higher.

Documents from document management that you have assigned to the order header or to the operations
directly or that you have defined as a production resource/tool at operation level are communicated to SAP
Digital Manufacturing with the IDoc. Before distributing the order, the system checks whether the assigned
documents were released. A URL that is part of the respective IDoc segments that provides an Internet
Communication Framework (ICF) service of the ERP system can be used to access the originals linked to the
documents. In this way, documents that are in the vault in document management can also be retrieved.

Data is transmitted over a secure connection (https port). To enable data transmission, you must activate
the service for structuring and reading a URL for this purpose. To do that, choose transaction SICF, browse
for DEFAULT_HOST in the Virtual Host field and choose Execute. Expand default_host sap co_mes_int
co_mes_document . Select the service and choose Activate in the Service/Host menu.

 Note

If you want to allow several users to access an original document with the URL, ensure that the original is
located in the SAP vault or in a network directory and not stored locally.

For more information, see Production Order on the SAP Help Portal at http://help.sap.com.

Prerequisites

SAP ERP

• You have transferred the material master records for the produced material and all the components (see
Material Transfer on the SAP Help Portal at http://help.sap.com).
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings/Recipes).
• You have created and sent work centers to SAP Digital Manufacturing.
• You have set up ALE communication to create and transmit LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .
• You have defined unique ISO codes for every unit of measure.
• You have created and released a document info record of the type PRT or Non-PRT (transaction CV01N) in
SAP ERP.

SAP Digital Manufacturing Integration Guide

156 PUBLIC SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing

• (Optional) You have imported BOM and routing master data from SAP ERP.

 Posting Instructions

BOM and routing masters that are sent from SAP ERP to SAP Digital Manufacturing prior to the
production order download allow additional manual configurations to take place inside of SAP Digital
Manufacturing. This prerequisite is optional because you can create the BOM and routing master in
SAP Digital Manufacturing directly from the production order download.

Procedural Steps

1. Create or update a production order manually (transaction CO01 and CO02) or automatically by converting
a planned order.
2. To attach one or more document info records to a production order header, enter the document type.
3. Release and save the production order after attaching the document info records.
4. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

 Note

SAP ERP 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B) distributes
production orders automatically upon release based on customizing settings.

If you use SAP ERP 6.00 – 6.04 (configuration type A), you transfer the production order using the
transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments
of the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 are not supplied when distributing using the
POIT transaction.

5. When the production order is sent to SAP Digital Manufacturing, the following records are created in SAP
Digital Manufacturing:
• Production order with operation activities and attachment points for the work instructions
• Routing
• Operation activities
• Work instructions
6. Verify the results in SAP Digital Manufacturing.

For more information, see Work Instruction on the SAP Help Portal at http://help.sap.com.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 157
2.1.5.2.1.6 Configuring a Production Order with Scheduling
Information
This section describes how to transfer a production order with scheduling information from SAP ERP to create
or update the corresponding production order with quantity splits associated with resources at a specific
routing step in SAP Digital Manufacturing for execution.

The production order is used by production planning in SAP ERP to define the material to be processed, the
location, the time, and the work required. You can also plan the resources to be used in the Production Process
Designer in SAP Digital Manufacturing for execution.

You can control and monitor short-term planning on your shop floor. Typical users are production supervisors,
foremen, or shift managers.

The release of the production order in SAP Digital Manufacturing for execution triggers production on the shop
floor (see Order Schedule Information).

Prerequisites

SAP ERP

• You have transferred the material master records for the produced material and all the components (see
Material Transfer on the SAP Help Portal at http://help.sap.com).
For more information about creating a batch-managed material master record, see the Configuring Batch
Managed Material section of this guide.
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings/Recipes).
• You have transferred the work centers with individual capacities.
• You have set up ALE communication to create and transmit LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing for execution

• You have imported a work center and resources from SAP ERP.
• (Optional) You have imported BOM and routing master data from SAP ERP.

 Posting Instructions

BOM and routing masters that are sent from SAP ERP to SAP Digital Manufacturing for execution
prior to the production order download allow additional manual configurations to take place inside

SAP Digital Manufacturing Integration Guide

158 PUBLIC SAP Digital Manufacturing for execution Integration
 of SAP Digital Manufacturing for execution. This prerequisite is optional because you can create the
BOM and routing master in SAP Digital Manufacturing for execution directly from the production order
download.

Procedural Steps

1. Create or update a production order manually (transaction CO01 and CO02) or automatically by converting
a planned order.
2. Allocate the production order quantity to specific resources for an operation to schedule production. This
generates a unique split ID for each resource assigned to an operation.
3. Send the production order with scheduling information from SAP ERP to SAP Digital Manufacturing for
execution.
4. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

 Note

SAP ERP 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B) distributes
production orders automatically upon release based on customized settings.

If you use SAP ERP 6.00 – 6.04 (configuration type A), you transfer the production order using the
transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments
of the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 are not supplied when distributing using the
POIT transaction.

5. Verify the results in SAP Digital Manufacturing for execution.

SAP Digital Manufacturing for execution creates or updates the production order containing scheduling
information based on the data received from SAP ERP.

2.1.5.2.1.7 Transfer of Production Order with Operation-Level

Scheduling

This section describes how to transfer a production order with operation-level scheduling information from
SAP ERP to create or update the corresponding production order that contains the operation start and end
time in SAP Digital Manufacturing for execution.

The production order is used by production planning in SAP ERP to define the material to be processed, the
location, the time, and the work required. Release of the production order in SAP Digital Manufacturing for
execution triggers production on the shop floor.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 159
Prerequisites

SAP ERP

• You have transferred the material master records for the produced material and all the components (see
Material Transfer on the SAP Help Portal at http://help.sap.com).
• You have created a BOM and a routing for the produced material (see Manage Bills of Materials and
Manage Routings (Deprecated)).
• You have transferred the work centers with individual capacities to SAP Digital Manufacturing for
execution.
• You have created a production order either manually or by converting a planned order automatically.
• You have set up ALE communication to create and transmit LOIPRO IDocs. For more information, see Data
Replication Framework [page 36].
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing for execution

• (Optional) You have imported the BOM and routing master data from SAP ERP.

 Posting Instructions

BOM and routing masters that are sent from SAP ERP to SAP Digital Manufacturing for execution
prior to the production order download allow additional manual configurations to take place inside
of SAP Digital Manufacturing for execution. This prerequisite is optional because you can create the
BOM and routing master in SAP Digital Manufacturing for execution directly from the production order
download.

Procedural Steps

1. Create a production order with scheduling information either manually or by converting a planned order
automatically or update the production order in SAP ERP.

 Note

Scheduling can be defined by using Material Requirement Planning (MRP) and detailed scheduling in
SAP Advanced Planning and Optimization (APO).

2. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter

SAP Digital Manufacturing Integration Guide

160 PUBLIC SAP Digital Manufacturing for execution Integration
 settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.

 Note

SAP ERP 6.05 with the activated BF LOG_PP_MES_INT_01 (configuration type B) distributes
production orders automatically upon release based on customized settings.

If you use SAP ERP 6.00 – 6.04 (configuration type A), you transfer the production order using the
transaction POIT after creating or changing the order.

 Note

The POIT transaction supports only the IDoc base types LOIPRO01. Additional fields and segments
of the IDoc types LOIPRO02, LOIPRO03, and LOIPRO04 are not supplied when distributing using the
POIT transaction.

3. Verify the results in SAP Digital Manufacturing for execution.

The system creates or updates the corresponding production order containing scheduling information in SAP
Digital Manufacturing for execution.

When the order is released in SAP Digital Manufacturing for execution, shop floor operators can see the
operation start and end time in the POD worklist.

2.1.5.2.1.8 Transferring a Production Order with PRT

Assignment

This section describes how to transfer production order data with PRT assignment from SAP ERP or SAP
S/4HANA to SAP Digital Manufacturing for execution to create or update the corresponding production order
record in SAP Digital Manufacturing for execution.

 Note

You can only transfer production order with equipment or material PRT assignment.

Prerequisites

SAP ERP or SAP S/4HANA

• You have completed all the prerequisites of Transferring a Production Order [page 149].
• The equipment PRT has already been transferred from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution. For detailed procedures, see Transferring a Tool [page 146].
• The material PRT has been transferred from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for
execution together with the material master data.
• The PRTs have already been assigned to routing operations.

SAP Digital Manufacturing

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 161
• The collaboration link COLLABORATION_PRT_ASSIGNMENT_GET is mapped to the directive
ERP_PRT_ASSIGNMENT_GET in the Manage Collaboration Links app.

Procedure

1. Create or update a production order manually (transaction CO01 and CO02) or automatically by converting
a planned order (see Creating a Production Order on the SAP Help Portal at http://help.sap.com).
2. SAP ERP 6.05 and later with the activated business function (BF) LOG_PP_MES_INT_02 distributes
production orders automatically upon release based on the Data Replication Framework (DRF) filter
settings. Changes to the order are distributed immediately after the initial distribution.
3. Verify the results in the Manage Orders app or the Integration Message Dashboard in SAP Digital
Manufacturing for execution. For more information, see Manage Orders or Integration Message Dashboard.

2.1.5.2.2 Production Order Status Confirmation

You can transfer the results of the production from SAP Digital Manufacturing for execution back to the
production order in SAP ERP or SAP S/4HANA for reporting steps to keep the status of the systems aligned.

A status confirmation documents the processing status of orders, operations, sub-operations and individual
capacities. It is an instrument for controlling orders.

With a confirmation you specify the following:

• The quantity in an operation that was produced as yield, scrap and the quantity to be reworked
• How much work was actually done
• Which work center was used for the operation
• Who performed the operation

Exact confirmation shortly after completion of an operation is essential for realistic production planning and
control.

2.1.5.2.2.1 Production Yield Confirmation on Operation

Complete

This section describes how to transfer a production yield confirmation message to SAP ERP.

The message is triggered when the SFC belonging to the production order completes an operation marked as
the SAP ERP reporting step.

 Note

An SFC can be re-processed at an operation that the SFC has already completed.

This function supports long material numbers (see Transferring a Long Material Number [page 122]).

SAP Digital Manufacturing Integration Guide

162 PUBLIC SAP Digital Manufacturing for execution Integration
For more information about reporting consumed components, see the Transfer of Goods Movement within
Yield/Scrap Confirmation section of this guide.

 Note

The Final Confirmation Type field was removed from the Production Yield Confirmation message to support
the overproduction scenario in the Manage Orders app. For more information, see Increasing the Build
Quantity for Overproduction. As this field was removed, the integrated ERP system sets the corresponding
operation to PCNF (partially confirmed), even if the yield quantity reaches the target quantity. Status CNF
(confirmed) is only set after the production order was manually or automatically completed in SAP Digital
Manufacturing.

If you have your own custom XSLT solution in place that communicates the final confirmation of each
operation automatically to the integrated ERP system, be aware that this custom XSLT solution is not
compatible with the overproduction scenario.

Prerequisites

SAP ERP

• You have verified that the control keys of the operations do not allow Auto Goods Receipt and that
they allow confirmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note
1502536 .
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations.
• You have verified that the operation sequence is not checked (see Logistics Production Shop Floor
Control Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).

SAP Digital Manufacturing

• You have imported the production order data from SAP ERP.
• You have released the production order to the shop floor.
• You have verified that routings contain at least one ERP reporting step.
We recommend that you mark the last routing operation as an ERP reporting step to ensure that all
consumed components are reported to SAP ERP.
• You have verified that collaboration links and directives are configured.

Procedural Steps

1. Complete an SFC that belongs to the production shop order at the ERP reporting step.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 163
2. The system triggers a collaboration event and sends the Production Order Yield Confirmation
message to update the processing status of the production order and operations in SAP ERP.

 Note

In SAP ERP, you can see the status of the production order on the Display Production Order
Confirmation: Details screen (transaction CO14).

If the production shop order contains scheduling information that has been transferred, then the
confirmation message also contains quantity split IDs and the capacity category.

2.1.5.2.2.2 Scrap Confirmation for a Production Order

This section describes how to transfer scrap data for the production order to SAP ERP when an SFC is
scrapped during production in SAP Digital Manufacturing for execution for execution.

When an SFC is scrapped, the system reports consumption of the components for this SFC with a goods issue
of the movement type 261.

If components were reserved for this shop order in SAP ERP, the consumption of these components is not
reported to SAP ERP.

This function supports long material numbers (see Transferring a Long Material Number [page 122]).

For more information about reporting consumed components, see the Transferring a Goods Movement within
Yield/Scrap Confirmation section of this guide.

Prerequisites

SAP ERP

• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that the operation sequence is not checked (see Logistics Production Shop Floor
Control Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).

SAP Digital Manufacturing for execution

• You have imported the production order data from SAP ERP.
• You have released the production order to the shop floor.
• You have verified that routings contain at least one ERP reporting step.
We recommend that you mark the last routing operation as an ERP reporting step to ensure that all
consumed components are reported to SAP ERP.
• You have verified that collaboration links and directives are configured.

SAP Digital Manufacturing Integration Guide

164 PUBLIC SAP Digital Manufacturing for execution Integration
Procedural Steps

1. Scrap an SFC belonging to the production order in SAP Digital Manufacturing for execution using Log NC.
2. The system triggers a collaboration event and sends the Production Order Scrap Confirmation message
with the following information to SAP ERP to report the quantity of scrapped finished goods and
component quantities consumed:
• Plant: SAP Digital Manufacturing for execution
• Production Order: Production order number.
• Operation: Operation activity name.
• Quantity: Quantity that has been scrapped.
• Base Unit of Measure: Units of measure of the produced material.
• Capacity Category: Capacity Category of the resource that was used to complete SFC.
• Split: Yield of a split that was processed by a capacity when an operation is split.
• Components: Assembled components (see Transferring a Goods Movement within Yield/Scrap
Confirmation section of this guide for more details).

 Note

The system does not send a serial number for a scrapped SFC to SAP ERP.

 Note

If an SFC is scrapped on the non-reporting step, SAP Digital Manufacturing for execution tries to
find a reporting step in the routing by checking future steps and uses the reporting step it finds.

In SAP ERP, you can see the status of the production order on the Display Production Order Confirmation:
Details screen (transaction CO14).

If the production order contains transferred scheduling information, then the confirmation message also
contains quantity split IDs and the capacity category.

2.1.5.2.2.3 Transferring a Goods Movement within Yield/

Scrap Confirmation

This section describes how to transfer goods movement (Goods Issue/Goods Receipt) to SAP ERP within
production yield confirmations, scrap confirmations for production orders, and container close messages.

 Note

An SFC can be re-processed at an operation that this SFC has already completed.

This function supports long material numbers.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 165
Prerequisites

SAP ERP

• You have verified that the control keys of the operations do not allow Auto Goods Receipt but allow
confirmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note 1502536 ).
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations.
• You have verified that the operation sequence is not checked (see Logistics Production Shop Floor
Control Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).

SAP Digital Manufacturing for execution

• You have imported the production order with BOM and routing data from SAP ERP.
• You have released the production order to the shop floor.
• You have received floor stock from SAP ERP.
• You have verified that routings contain at least one ERP reporting step.
We recommend that you mark the last routing operation as an ERP reporting step to ensure that all
consumed components are reported to SAP ERP.
• You have verified that collaboration links and directives are configured.

Procedure

1. Assemble a discrete component (by choosing Add in the Assembly Point or As-Built Configuration plugin,
or when a component is assembled using the Auto Assemble Component hook point activity) or a time-
based component.
2. Complete an SFC belonging to the production shop order at the ERP reporting step, scrap it, or pack it in
the container and close it.
3. The system triggers a collaboration event and sends a confirmation message that contains a goods
movement section with the goods movement type 261 (goods issue for an order) for the assembled
component to SAP ERP.

Goods movement is not triggered for co-products and by-products.

Goods movement is not triggered for floor stock pegged to a shop order.

Goods movement is triggered for non-BOM components.

Note: Goods movement section is included in the following messages:

• Production Order Yield Confirmation

• Production Order Scrap Confirmation

SAP Digital Manufacturing Integration Guide

166 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.2.4 Transferring a Goods Movement (Goods Issue)
Independent of Yield Confirmation

This section describes how to transfer a goods movement to SAP ERP on assembly of discrete components of
a top assembly in SAP Digital Manufacturing for execution.

 Note

This function does not support time-based and backflushed components.

Prerequisites

SAP ERP

• You have verified that the component materials are not marked as backflushed (the Backflush checkbox on
the MRP 2 tab of the MM01/MM02 transaction).

SAP Digital Manufacturing for execution

• In Collaboration Link Maintenance, you have verified that the ERP_COMPONENT_ADD directive is assigned to
the COLLABORATION_SFC_COMPONENT_ADD link.
• You have imported the production order data from SAP ERP.
• You have received floor stock from SAP ERP.
• You have released the production order to the shop floor.

Procedural Steps

1. Choose Add in the Assembly Point (Assemble Components) or As-Built Configuration plugin to indicate that
you have assembled a discrete component.
2. SAP Digital Manufacturing for execution triggers a collaboration action
(COLLABORATION_SFC_COMPONENT_ADD).
3. The system sends the Production Order Component Add message with the goods movement type
261 (goods issue for an order) for the assembled component to SAP ERP.

 Note

This component is not included in production yield confirmation.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 167
2.1.5.2.2.5 Production Order Complete

This section describes how to transfer a production order complete message to SAP S/4HANA or SAP ERP.

The message is triggered when the following occurs in SAP Digital Manufacturing for execution:

• All SFCs belonging to a production shop order are completed at the operation marked as the last ERP
reporting step (the Is Last Reporting Step checkbox in Routing Step Properties) and the status of the order
changes to Completed.
• The production order is completed manually in the Manage Orders app. For more information, see
Completing Orders.

Prerequisites

SAP ERP

• You have verified that the control keys of the operations do not allow Auto Goods Receipt but allow
confirmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note 1502536 ).
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations.
• You have verified that the operation sequence is not checked (see Logistics Production Shop Floor
Control Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).

SAP Digital Manufacturing for execution

• You have imported the production order data from SAP S/4HANA or SAP ERP.
• You have released the production order to the shop floor.
• You have verified that routings contain at least one ERP reporting step.
We recommend that you mark the last routing operation as the ERP reporting step to ensure that all
consumed components are reported to SAP S/4HANA or SAP ERP.
• You have verified that collaboration links and directives are configured. For more information, see Manage
Collaboration Links and Manage Collaboration Directives.

Procedural Steps

1. Change the status of the production shop order to Completed.

 Note

This can be done manually or by completing all SFCs belonging to the order at the operation marked as
the last ERP reporting step. For more information, see Completing Orders.

SAP Digital Manufacturing Integration Guide

168 PUBLIC SAP Digital Manufacturing for execution Integration
2. SAP Digital Manufacturing for execution triggers a collaboration event.
3. The system sends the Order Complete message to update the processing status of the production order in
SAP S/4HANA or SAP ERP. For integration, you need to use the COLLABORATION_ORDER_COMPLETE_DI
link and the ERP_ORDER_COMPLETE directive in the Manage Collaboration Links and Manage Collaboration
Directives apps.
In SAP ERP, you can see the status of the production order on the Display Production Order Confirmation:
Details screen (transaction CO14).

Related Information

Completing Orders
How Order Statuses Change in a Business Scenario

2.1.5.2.2.6 Report Serial and Batch Numbers for Semi-

Finished Components

This section describes how to transfer a serial and batch number for semi-finished components to SAP
ERP within production yield confirmation, planned order confirmation, scrap confirmation for production and
planned orders, and container close messages.

Prerequisites

SAP ERP

• You have configured Batch Management.

• You have maintained a serial number profile for the header material so that a production order can
contain serial numbers (in Customizing for Logistics, choose Materials Management Material Master
Material Change Work Scheduling ).
• You have verified that the control keys of the operations do not allow Auto Goods Receipt but allow
confirmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note 1502536 ).
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations.
• You have verified that the operation sequence is not checked (see Logistics Production Shop Floor
Control Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).
• You have set up ALE communication to create and transmit LOIPRO IDocs.
• You have also defined the Data Replication Framework (DRF) replication model to replicate LOIPRO IDocs
(in Customizing for Production, choose Integration with a Manufacturing Execution System Basic
Settings for MES Integration ). For information about the SAP ERP versions supporting DRF, see SAP
Note 1793291 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 169
• You have defined unique ISO codes for every unit of measure.

SAP Digital Manufacturing for execution

• You have imported the material master records for the produced material and all the components.
• For materials to be assembled, you have specified which data will be collected on assembly:
o SFC or INV_SFC
• You have imported the production order with BOM and routing data from SAP ERP.
• You have released the production shop order to the shop floor.
• You have received floor stock from SAP ERP.
• You have verified that routings contain at least one ERP reporting step.
• We recommend that you mark the last routing operation as the ERP reporting step to ensure that all
consumed components are reported to SAP ERP.
• You have verified that collaboration links and directives are configured in ERP.

Procedural Steps

1. Create a semi-finished material record in SAP ERP. It has to be either batch-managed or with an assigned
serial number profile.
2. Create a finished material record with the BOM containing semi-finished material.
3. Create and release a production order in SAP ERP for semi-finished material. Release this order in SAP
Digital Manufacturing for execution and complete SFCs until they get the status of Done.
4. Create and release a production order for your top assembly material (finished material).
5. Assemble a semi-finished component using either discrete (by choosing Add in the Assembly Point or
As-Built Configuration plugin) or time-based assembling.

 Note

Reporting of serial numbers is not supported for time-based components.

 Note

The SFC has to be collected for the component during assembly.

6. Complete an SFC belonging to the production shop order at the ERP reporting step, scrap it or pack to the
container and close it.
7. SAP Digital Manufacturing for execution triggers a collaboration event.
8. The system sends a confirmation message that contains a goods movement section with the goods
movement type 261 (goods issue for an order) for the assembled component to SAP ERP.
Note: The goods movement section is included in the following types of messages:
• Production Order Yield Confirmation
• Production Order Scrap Confirmation

SAP Digital Manufacturing Integration Guide

170 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.2.7 Activity Confirmation

You can transfer activity confirmation messages for production orders from SAP Digital Manufacturing for
execution to SAP ERP or SAP S/4HANA.

Prerequisites

SAP ERP or SAP S/4HANA

• You've created a work center and a standard value key.

• You've transferred the work center to SAP Digital Manufacturing for execution.

SAP Digital Manufacturing for execution

• The production order data is transferred from SAP ERP or SAP S/4HANA. For more information, see
Transferring a Production Order [page 149].
• The production order is released to the shop floor using the Manage Orders app.
• The routing contains at least one ERP reporting step.
• You've implemented the following collaboration link and directive in the Manage Collaboration Links and
Manage Collaboration Directives apps:

Collaboration Link Collaboration Directive

COLLABORATION_ACTIVITY_CONFIRMATION_DI ACTIVITY_CONFIRMATION

Procedure

1. In the Order POD (Default), post an activity confirmation for the production order. For more information,
see Order POD.
2. The system triggers a collaboration event and sends the Production Order Activity Confirmation message
to trigger the posting of an activity confirmation in SAP ERP or SAP S/4HANA.
3. To verify whether the Production Order Activity Confirmation message was transferred to the integrated
ERP system, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your Production Order Activity Confirmation message. For more information, see Integration
Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID that you can find in the
Integration Message Dashboard. For more information, see Monitoring Message Processing.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 171
2.1.5.2.2.8 Quantity Confirmation

You can transfer quantity confirmation messages from SAP Digital Manufacturing for execution to SAP ERP
and SAP S/4HANA.

Prerequisites

SAP ERP and SAP S/4HANA

• You have verified that the control keys of the operations do not allow Auto Goods Receipt and that they
allow confirmations (see Control Key on the SAP Help Portal).
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations. For more information, see
1502536 .
• You've made the following settings under Logistics Production Shop Floor Control Operations
Confirmation Define Confirmation Parameters (transaction OPK4) :
• The operation sequence is not checked
• No message if no insp. results exist
• Dates in Future unchecked.
Depending on your business scenario, you can choose other settings as well, which might impact your
integration scenario.

SAP Digital Manufacturing for execution

• The production order data is transferred from SAP ERP or SAP S/4HANA.
• The production order is released to the shop floor.
• The routing contains at least one ERP reporting step.
• The collaboration link COLLABORATION_QUANTITY_CONFIRMATION_DI is mapped to the directive
PRODORD_QUANTITY_CONFIRMATION in the Manage Collaboration Links app.

Procedure

1. In the Order POD (Default), post quantities in the Quantity Confirmation tab.

 Note

There's a check performed in the background whether the current resource is relevant for OEE and
scheduling (Scheduling and OEE Relevant flag is set in the Manage Work Centers app). If the resource
isn't OEE and scheduling relevant, the confirmation is rejected.

You can see the default resource against which yield/scrap is reported in the Operation Details tab.

2. The system triggers a collaboration event and sends the Production Order Quantity Confirmation
message to trigger the posting of a quantity confirmation in SAP ERP or SAP S/4HANA.

SAP Digital Manufacturing Integration Guide

172 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.3 Process Order Integration

You can transfer process orders from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution.

Prerequisites

SAP ERP or SAP S/4HANA

• You have created work centers with plant and production-relevant data in the Logistics module (see
Creating, Changing and Displaying Work Centers on the SAP Help Portal. You have transferred work centers
to SAP Digital Manufacturing for execution.
• You have created a BOM and a routing / recipe for the produced material (see Manage Bills of Materials
and Manage Routings/Recipes ).

 Note

BOM components must be assigned to phases.

• You have transferred materials to SAP Digital Manufacturing for execution.

• You have set up ALE communication to create and transmit an LOIPRO05 IDoc. For more information, see
Data Replication Framework [page 36].
• You've implemented BADI CO_MES_INT_REDISTRIBUTION in the integrated ERP system. This BADI
makes sure that the integrated ERP system doesn't communciate an order change to SAP Digital
Manufacturing after receiving the release notification (RMES). For more information, see 2165261 .

Procedure

1. Create or update a process order manually (transaction COR1 and COR2) or automatically by converting a
planned order.

 Note

To distinguish between a discrete industry order and a process industry order, when this differentiation
is required for the internal execution logic, SAP Digital Manufacturing relies on the Auto complete
and confirm flag that is set on material level in the integrated ERP system. If this flag is active, the
downloaded order is considered to be a discrete industry order and handled accordingly. If this flag
isn't active, the downloaded order is treated as a process industry order and handled accordingly.

 Note

For overproduction scenarios in the process industry, it's recommended to configure the overdelivery
limits only as soft limits (warning) in your integrated ERP system. If you configure the overdelivery
limits as hard limits, you might encounter issues when trying to cancel orders in SAP Digital
Manufacturing. For more information on how to deal with cancellations issues due to the overdelivery
configuration in the integrated ERP system, see 3267541 .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 173
2. Release the process order to transfer it via the Data Replication Framework (DRF) to SAP Digital
Manufacturing for execution using IDoc LOIPRO05 according to the filter criteria you set in the DRF. For
more information, see Data Replication Framework [page 36].

 Note

If you enable transfer of process orders using DRF, check the SAP notes: 2888888 , 2931412 , and
3017004 .

3. Verify the results in Manage Orders and Integration Message Dashboard apps in SAP Digital Manufacturing
for execution.

The system creates or updates the process order based on the data received from SAP ERP or SAP S/4HANA.

When the order is released in SAP Digital Manufacturing for execution, shop floor operators can see the
operation start and end time in the POD worklist.

Related Information

Manage Orders
Order Statuses
How Order Statuses Change in a Business Scenario

2.1.5.2.3.1 Transferring a Process Order with Inspection Lot

(type 03)

You can transfer the inspection lot (inspection type 03) and inspection characteristics assigned to a process
order from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution.

• In SAP ERP or SAP S/4HANA, an inspection lot documents a request for an inspection. Inspection
characteristics are assigned to the inspection lot.
• In SAP ERP, the type 03 inspection lot refers to in-process inspection that takes place in production. With
in-process inspections, an inspection lot is created for a process order. Characteristics are assigned to
individual operations in the master recipe.
• When a process order with inspection lot / inspection characteristics are transferred from SAP ERP or
SAP S/4HANA, the corresponding orders are created and inspection characteristics can be viewed at SFC
operation level in the Order POD (Default).

Prerequisites

SAP ERP and SAP S/4HANA

• You have completed all the prerequisites of Configuring a Process Order [page 173].
• Inspection characteristics have been assigned to individual operations in the master recipe.

SAP Digital Manufacturing Integration Guide

174 PUBLIC SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing

• You have set up ALE communication to create and transmit an LOIPRO05 IDoc. For more information, see
Data Replication Framework [page 36].

Procedure

1. Create a process order with inspection lot / inspection characteristics assigned to it (transaction COR1 and
COR2).
2. Release the process order. The system transfers the order data to SAP Digital Manufacturing using IDoc
LOIPRO05 according to the filter criteria you set in the DRF. For more information, see Data Replication
Framework [page 36].

 Note

If you enable transfer of process orders via DRF, make sure you checked these notes: SAP Note
2888888 , SAP Note 2931412 and SAP Note 3017004 .

3. Verify the results in the Manage Orders app and the Integration Message Dashboard in SAP Digital
Manufacturing for execution. For more information, see Manage Orders or Integration Message Dashboard.

The system creates the process order based on the data received from SAP ERP or SAP S/4HANA.

When the order is released in SAP Digital Manufacturing for execution, shop floor operators can see the
inspection characteristics at operation level in the Order POD (Default).

Related Information

Process Order Integration [page 173]

2.1.5.2.4 Process Order Status Confirmation

You can transfer the results of the production from SAP Digital Manufacturing for execution back to the process
order in SAP ERP or SAP S/4HANA for reporting steps to keep the status of the systems aligned.

A status confirmation documents the processing status of orders, operations and inventory movements. It is
an instrument for controlling orders.

With a confirmation you specify the following:

• The quantity in an operation that was produced as yield or scrap.

• The progress of the order.
• Who performed the operation.
• Production activities that are completed at the phase level of an order.
• The SFC that was processed.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 175
  Note

The information about which SFC was processed is transferred to SAP Cloud Integration within the
outbound confirmation message of process orders after you've performed one of the following actions:
• Process Order Goods Issue
• Process Order Goods Issue Cancellation
• Process Order Goods Receipt
• Process Order Goods Receipt Cancellation
• Process Order Quantity Confirmation
• Process Order Activity Confirmation
• Process Order Activity Confirmation Cancellation

You need to perform the mapping of OData fields to BAPI fields between SAP Cloud Integration and
your ERP system according to your needs.

Exact confirmation shortly after completion of an operation is essential for realistic production planning and
control.

Related Information

Goods Receipt [page 176]

Goods Issue [page 177]
Quantity Confirmation [page 178]
Activity Confirmation [page 179]

2.1.5.2.4.1 Goods Receipt

You can transfer goods receipts for process orders to SAP ERP or SAP S/4HANA within goods receipt
confirmations.

Prerequisites

SAP ERP or SAP S/4HANA

• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations.
• You have verified that the operation sequence is not checked (see Production Shop Floor Control
Operations Confirmation Define Confirmation Parameters (transaction OPK4) ).

SAP Digital Manufacturing

• The process order data is transferred from SAP ERP or SAP S/4HANA.

SAP Digital Manufacturing Integration Guide

176 PUBLIC SAP Digital Manufacturing for execution Integration
• The process order is released to the shop floor.
• The recipe contains at least one ERP reporting step.
• The collaboration link COLLABORATION_GOODS_RECEIPT_CONFIRMATION is mapped to the directive
GOODS_RECEIPT_CONFIRMATION in the Manage Collaboration Links app.

Procedure

For the detailed procedure, navigate to the following topic in the Application Help for Execution: Creating Goods
Receipts.

2.1.5.2.4.2 Goods Issue

You can transfer goods issue messages for process orders from SAP Digital Manufacturing for execution to
SAP ERP or SAP S/4HANA.

Prerequisites

SAP ERP or SAP S/4HANA

• You've created a process order for which stock is available.

SAP Digital Manufacturing for execution

• The process order data is transferred from SAP ERP or SAP S/4HANA. For more information, see Process
Order Integration [page 173].
• The process order is released to the shop floor.
• The recipe contains at least one ERP reporting step.
• Inventory is downloaded from the external SAP ERP system.
• Work centers are assigned to relevant users using the Manage User Assignments app. Users can post
consumption only on assigned work centers.
• You've implemented the following collaboration links and directives in the Manage Collaboration Links and
Manage Collaboration Directives apps:

Collaboration Link Collaboration Directive

COLLABORATION_GOODS_ISSUE_CONFIRMATION GOODS_ISSUE_CONFIRMATION

Procedure

1. In the Order POD (Default), post a goods issue for the process order. For more information, see Consuming
Materials.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 177
2. The system triggers a collaboration event and sends the Process Order Goods Issue message to trigger the
posting of a goods issue in SAP ERP or SAP S/4HANA.
3. To verify whether the Process Order Goods Issue message was transferred to the integrated ERP system,
you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your Process Order Goods Issue message. For more information, see Integration Message
Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID that you can find in the
Integration Message Dashboard. For more information, see Monitoring Message Processing.

2.1.5.2.4.3 Quantity Confirmation

You can transfer quantity confirmation messages from SAP Digital Manufacturing for execution to SAP ERP
and SAP S/4HANA.

Prerequisites

SAP ERP and SAP S/4HANA

• You have verified that the control keys of the operations do not allow Auto Goods Receipt and that they
allow confirmations (see Control Key on the SAP Help Portal)
• You have verified that all work centers have the same activity types arranged in the same sequence.
• You have verified that operations are not marked as milestone operations. For more information, see
1502536 .
• You've made the following settings under Logistics Production Shop Floor Control Operations
Confirmation Define Confirmation Parameters (transaction OPK4) :
• The operation sequence is not checked
• No message if no insp. results exist
• Dates in Future unchecked.
Depending on your business scenario, you can choose other settings as well, which might impact your
integration scenario.

SAP Digital Manufacturing for execution

• The process order data is transferred from SAP ERP.

• The process order is released to the shop floor.
• The recipe contains at least one ERP reporting step.
• The collaboration link COLLABORATION_QUANTITY_CONFIRMATION is mapped to the directive
QUANTITY_CONFIRMATION in the Manage Collaboration Links app.

SAP Digital Manufacturing Integration Guide

178 PUBLIC SAP Digital Manufacturing for execution Integration
Procedure

1. In the Order POD (Default), post quantities in the Quantity Confirmation tab.

 Note

There's a check performed in the background whether the current resource is relevant for OEE and
scheduling (Scheduling and OEE Relevant flag is set in the Manage Work Centers app). If the resource
isn't OEE and scheduling relevant, the confirmation is rejected.

You can see the default resource against which yield/scrap is reported in the Phase Details tab.

2. The system triggers a collaboration event and sends the Process Order Quantity Confirmation
message to trigger the posting of a quantity confirmation in SAP ERP or SAP S/4HANA.

2.1.5.2.4.4 Activity Confirmation

You can transfer activity confirmation messages for process orders from SAP Digital Manufacturing for
execution to SAP ERP or SAP S/4HANA.

Prerequisites

SAP ERP or SAP S/4HANA

• You've created a work center and a standard value key.

• You've transferred the work center to SAP Digital Manufacturing for execution.

SAP Digital Manufacturing for execution

• The process order data is transferred from SAP ERP or SAP S/4HANA. For more information, see Process
Order Integration [page 173].
• The process order is released to the shop floor.
• The recipe contains at least one ERP reporting step.
• You've implemented the following collaboration links and directives in the Manage Collaboration Links and
Manage Collaboration Directives apps:

Collaboration Link Collaboration Directive

COLLABORATION_ACTIVITY_CONFIRMATION ACTIVITY_CONFIRMATION

Procedure

1. In the Order POD (Default), post an activity confirmation for the process order. For more information, see
Order POD.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 179
2. The system triggers a collaboration event and sends the Process Order Activity Confirmation message to
trigger the posting of an activity confirmation in SAP ERP or SAP S/4HANA.
3. To verify whether the Process Order Activity Confirmation message was transferred to the integrated ERP
system, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your Process Order Activity Confirmation message. For more information, see Integration
Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID that you can find in the
Integration Message Dashboard. For more information, see Monitoring Message Processing.

2.1.5.2.5 Planned Order Integration

You can transfer planned orders from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing and send back
yield and scrap confirmations.

Overview

You use planned orders for repetitive manufacturing where production is based on the quantity and not
order-based as with production orders. Planned orders are the right choice if you want to manufacture a
defined quantity within a specific time frame. With repetitive manufacturing, you generally use simple routings
that don't change over time, so called rate routings. The following features are supported:

• Yield confirmation is sent to the integrated ERP system after an SFC has been completed at the last
operation.
• Scrap confirmation is sent to the integrated ERP system after an SFC has been scrapped.
• Goods issue posting to the integrated ERP system after operation / phase confirmation (backflush).

Restrictions

The following restrictions apply to planned orders:

• The order schedule isn't downloaded from the ERP side.

• Batch management for material isn't supported.
• Direct goods issue of components to the ERP system isn't supported.
• Order update from the integrated ERP system isn't supported.

SAP Digital Manufacturing Integration Guide

180 PUBLIC SAP Digital Manufacturing for execution Integration
Integration

The inbound and outbound integration of planned orders is based on the implementation steps described in
the technical integration section. For more information, see Technical Integration with SAP S/4HANA or SAP
ERP [page 14].

If you've already implemented the infrastructure described in the technical integration section, you can find the
planned order specific information in the following topics:

• Transferring a Planned Order [page 181]

• Scrap Confirmation for Planned Orders [page 183]
• Yield Confirmation for Planned Orders [page 184]

2.1.5.2.5.1 Transferring a Planned Order

You can transfer planned orders from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing.

Overview

You create planned orders in SAP ERP / SAP S/4HANA and transfer them to SAP Digital Manufacturing
to control your production. For the transfer of planned orders, you rely on the technical infrastructure that
you've set up between your integrated ERP system and SAP Digital Manufacturing. For more information, see
Technical Integration with SAP S/4HANA or SAP ERP [page 14]. In the section below, you'll learned what needs
to be done specifically to transfer planned orders to SAP Digital Manufacturing.

Prerequisites

SAP ERP / SAP S/4HANA

• You've transferred the material master records for the produced material and all the components.

 Note

You need to assign a REM profile (for example 0001) to the material on view MRP4. If needed, you can
create a REM profile using transaction OSP2 (SPRO).

• You've created a BOM and a routing for the produced material (see Manage Bills of Materials and Manage
Routings/Recipes).
• You've created and sent work centers to SAP Digital Manufacturing.
• You've set up Application Link Enabling (ALE) and the Data Replication Framework (DRF) for the LOIPLO02
IDoc. For more information, see Data Replication Framework [page 36].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 181
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Configure Inbound Processor iFlow [page 69]
and Configure Initial Parameters iFlow [page 71].

 Note

You can replicate planned orders with an opening date in the future periodically to the integrated ERP
system. For more information, see 1555198 .

SAP Digital Manufacturing

• (Optional) You've imported BOM and routing master data from SAP ERP or SAP S/4HANA.
• You've enabled the artifact PlannedOrder LOIPLO02 process request in SAP Cloud Integration to use
LOIPLO02 IDoc.

Procedure

1. In SAP ERP or SAP S/4HANA, create a planned order manually (transaction MD11).

 Note

Enter a storage location in the planned order in the integrated ERP system or in the Putaway Storage
Location field in the Manage Materials app in SAP Digital Manufacturing.

 Note

A planned order creation can also be triggered via an MRP run. The planned order is then transferred
automatically to SAP Digital Manufacturing.

2. Schedule the planned order to trigger the planned order download.

3. To verify whether the message of type Order Download IDoc was transferred to SAP Digital
Manufacturing for execution, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your LOIPLO02 IDoc (message type: Order Download). For more information, see Integration
Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID of your planned order that
you can find in the Integration Message Dashboard. For more information, see Monitoring Message
Processing.

Related Information

Manage Orders

SAP Digital Manufacturing Integration Guide

182 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.5.2 Scrap Confirmation for Planned Orders

Learn how to transfer scrap confirmations for planned orders from SAP Digital Manufacturing to SAP ERP or
SAP S/4HANA SAP Digital Manufacturing.

Overview

After downloading a planned order from your integrated ERP system, you release it in the Manage Orders app
and start the production using the Work Center POD. When you then scrap an SFC in the Work Center POD, this
information is communicated to your integrated ERP system, if you've put in place the configuration described
below.

Prerequisites

SAP ERP / SAP S/4HANA

• You've verified that all work centers have the same activity types arranged in the same sequence.

SAP Digital Manufacturing

• You've downloaded the planned order from SAP ERP or SAP S/4HANA. For more information, see
Transferring a Planned Order [page 181].
• You've released the planned order to the shop floor using the Manage Orders app.
• You've verified that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity flag in the Manage Routings/Recipes app is set to Yes.
• You've configured the following collaboration link and directive in the Manage Collaboration Directives and
the Manage Collaboration Links app:

Collaboration Link Collaboration Directive

COLLABORATION_PLANNED_ORDER_SCRAP_CONFIR­ ERP_PLANNED_ORDER_SCRAP_CONFIRMATION
MATION

Procedure

1. In SAP Digital Manufacturing, in the Work Center POD, scrap an SFC belonging to the planned order using
Log NC.
The Planned Order Scrap Confirmation message is sent to the integrated ERP system.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 183
  Note

If an SFC is scrapped on the nonreporting step, SAP Digital Manufacturing tries to find a reporting step
in the routing by checking future steps and uses the reporting step it finds.

2. To verify whether the Planned Order Scrap Confirmation message was transferred to the integrated ERP
system, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the
status of your Planned Order Scrap Confirmation message. For more information, see Integration
Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID of your planned order that
you can find in the Integration Message Dashboard. For more information, see Monitoring Message
Processing.

2.1.5.2.5.3 Yield Confirmation for Planned Orders

Learn how to transfer a yield confirmations for planned orders from SAP Digital Manufacturing to SAP ERP or
SAP S/4HANA.

Overview

After downloading a planned order from your integrated ERP system, you release it in the Manage Orders app
and start the production using the Work Center POD. When you then complete an SFC in the Work Center
POD, this information is communicated to your integrated ERP system, if you've put in place the configuration
described below.

Prerequisites

SAP ERP / SAP S/4HANA

• You've verified that all work centers have the same activity types arranged in the same sequence.
• You've verified that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity flag in the Manage Routings/Recipes app is set to Yes.

SAP Digital Manufacturing for execution

• You've downloaded the planned order from SAP ERP or SAP S/4HANA. For more information, see
Transferring a Planned Order [page 181].

SAP Digital Manufacturing Integration Guide

184 PUBLIC SAP Digital Manufacturing for execution Integration
• You've released the planned order to the shop floor using the Manage Orders app.
• You've verified that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity flag in the Manage Routings app is set to Yes.
• You've configured the following collaboration link and directive in the Manage Collaboration Directives and
the Manage Collaboration Links app:

Collaboration Link Collaboration Directive

COLLABORATION_PLANNED_ORDER_YIELD_CONFIR­ ERP_PLANNED_ORDER_YIELD_CONFIRMATION
MATION

Procedural Steps

1. Complete the SFC at all operations.

2. After the completion of the last operation, the system triggers a collaboration event and sends the
Planned Order Yield Confirmation message to SAP ERP or SAP S/4HANA.
3. To verify whether the Planned Order Yield Confirmation message was transferred to the integrated ERP
system, you've got two options:
1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check
the status of your Planned Order Yield Confirmation message. For more information, see Integration
Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of your integration
message. You can search for the relevant artifacts using the correlation ID of your planned order that
you can find in the Integration Message Dashboard. For more information, see Monitoring Message
Processing.

2.1.5.2.6 Updating Orders Before the Release

Learn about the options you've got for updating a production or process order from your integrated ERP
system before the order is released to the shop floor in SAP Digital Manufacturing.

Use

Before releasing an order to the shop floor in the Manage Orders app, you can update it from your integrated
ERP system. The updating options you have vary depending on the order type and the integrated ERP system.

Overview

Here you'll find an overview of the supported update scenarios. "X" means that the corresponding update is
supported.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 185
 SAP ERP SAP S/4HANA
Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

Finished Goods X X X X X X
Batch Number
(Order Header)

Goods Receipt X X X X X X
Storage Loca­
tion (Order
Header)

Customer X X N/A N/A N/A N/A

Name (Order
Header)

Sales Order X X X N/A N/A N/A

(Order Header)

Custom Field X X N/A X X N/A

(Order Header)

Work Instruc­ X X N/A N/A N/A N/A

tion

Dates Changes X X X X X X
(Order Header)

Operation X X X X X X
Schedule

Quantity De­ X X X X X X
crease

Quantity In­ X X X X X X
crease

Technical Com­ X X X X X X
pletion (TECO)

Order Header X X X X X X
Long Text

Order Header X X X X X X
Schedule
Dates/Plan
Dates

SAP Digital Manufacturing Integration Guide

186 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP ERP SAP S/4HANA
Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

BOM Compo­ X X X X X X
nent Storage
Location  Note  Note  Note  Note  Note  Note
The BOM The BOM The BOM The BOM The BOM The BOM
component component component component component component
storage lo­ storage lo­ storage lo­ storage lo­ storage lo­ storage lo­
cation cation cation cation cation cation
change is change is change is change is change is change is
supported supported supported supported supported supported
by EWM by EWM by EWM by EWM by EWM by EWM
2021 or 2021 or 2021 or 2021 or 2021 or 2021 or
higher. higher. higher. higher. higher. higher.

BOM Compo­ X X X X X X
nent Batch
Number

Underdelivery X X X N/A N/A N/A

Tolerance

Overdelivery X X X N/A N/A N/A

Tolerance

Addition / Re­ X X X X X X
moval of Com­
ponent

Component X X X X X X
Assignment
Change to Op­
eration Activ­
ity / Phase

Addition / Re­ X X X X X X
moval of Oper­
ation / Phase

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 187
 SAP ERP SAP S/4HANA
Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

Work Center X X X X X X
Change in Op­
eration /  Note  Note  Note  Note  Note  Note
Phase
For integra­ For integra­ For integra­ For integra­ For integra­ For integra­
tion with tion with tion with tion with tion with tion with
EWM, the EWM, the EWM, the EWM, the EWM, the EWM, the
new target new target new target new target new target new target
work cen­ work cen­ work cen­ work cen­ work cen­ work cen­
ter must be ter must be ter must be ter must be ter must be ter must be
mapped to mapped to mapped to mapped to mapped to mapped to
a produc­ a produc­ a produc­ a produc­ a produc­ a produc­
tion supply tion supply tion supply tion supply tion supply tion supply
area (PSA). area (PSA). area (PSA). area (PSA). area (PSA). area (PSA).

Change of X X X X X X
Component
Quantities

Order-Specific X X X X X X
Bill of Mate­
rial*

Order-Specific X X X X X X
Routing*

Inspection Lot X X X X
Change

*Objects are up-versioned if one of the following changes takes place:

• Changes to work centers on operations / phases

• Addition or removal of component
• Addition or removal of operations / phases
• Change of component quantities
• Changes to component assignment

2.1.5.2.7 Enrichment of Order-Specific Objects

Enrichment is the process of copying some of the fields from master objects to order-specific objects during
order integration.

The following fields are copied for BOM components:

• Assembly Qty As Required

• Minimum Tolerance

SAP Digital Manufacturing Integration Guide

188 PUBLIC SAP Digital Manufacturing for execution Integration
• Maximum Tolerance
• Assembly Data Type

For formula enrichment during order transfer, for every component of an order-specifc BOM, data type is
copied from the corresponding master component. When data type is copied to the master component, the
formula is enriched. The following objects are copied:

• Assembly Data Type

• Assembly Qty As Required

The following fields are copied for routings and recipes:

• Work instructions (on operation activity/phase and header level)

• Data collections (on operation activity/phase and header level)

The following fields are copied only for routings:

• Relaxed flow

The following fields are copied only for recipes

• Weighing relevant flag (on operation activity level)

2.1.5.2.8 Enrichment with Sub-Operations for Discrete

Manufacturing

You can add sub-operations to a routing in SAP ERP, SAP S/4HANA, or SAP S/4HANA Cloud, and then
transfer this routing to SAP Digital Manufacturing.

Overview

In a discrete industry scenario, you can add sub-operations to a routing in SAP ERP, SAP S/4HANA, or SAP
S/4HANA Cloud. These sub-operations are then transferred within the routing to SAP Digital Manufacturing.
To make this transfer work, you need to use the latest SAP S/4HANA Integration with SAP Digital Manufacturing
package in SAP Cloud Integration.

Reporting of SAP Digital Manufacturing activities back to the integrated ERP system is done at the last
operation activity within the respective operation group.

Order confirmations are posted against the ERP parent Operation.

Mapping

In SAP Digital Manufacturing, ERP routings containing sub-operations are mapped as follows:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 189
ERP System SAP Digital Manufacturing

Operation Operation Group

Sub-operation Operation Activity

BOM components assigned to an Operation First Operation Activity of the Operation Group

2.1.5.2.9 Batch Characteristics Update

You can update batch characteristic values in SAP Digital Manufacturing for execution and synchronize the
data to SAP ERP or SAP S/4HANA.

 Note

This function is supported only for process orders.

Prerequisites

SAP ERP or SAP S/4HANA

• Batch-managed materials are created in SAP ERP or SAP S/4HANA and are transferred to SAP Digital
Manufacturing for execution.
• Batch characteristics are assigned to the batch-managed material in SAP ERP or SAP S/4HANA.

Procedure

• Update batch characteristic values for the process order you want to work on.
• The system updates the batch characteristics data for respective material in SAP ERP or SAP S/4HANA.

Related Information

Updating Batch Characteristics

SAP Digital Manufacturing Integration Guide

190 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.10 Batch Creation

You can transfer batch numbers created in SAP Digital Manufacturing for execution to SAP ERP or SAP S/
4HANA.

The batch creation message is triggered when batch number is created in SAP Digital Manufacturing for
execution.

Prerequisites

SAP ERP or SAP S/4HANA

Batch-managed materials are created in SAP ERP or SAP S/4HANA and are transferred to SAP Digital
Manufacturing for execution.
SAP Digital Manufacturing

The collaboration link COLLABORATION_BATCH_CREATION is mapped to the directive BATCH_CREATION in

the Manage Collaboration Links app.

Procedure

• Create a batch number for the process order you want to work on.
• The system triggers a collaboration event and sends the Batch Creation message to update the batch data
for respective material in SAP ERP or SAP S/4HANA.

Related Information

Creating Batch Numbers

2.1.5.2.11 Inspection Characteristics Integration (Process

Order and Order-Based Production Order)

You can transfer inspection characteristics of an order from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution.

Prerequisites

SAP ERP or SAP S/4HANA

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 191
• An order exists for the material.
• QM is active for the material to be inspected. That means that in the inspection setup in the material
master, the following applies:
• An inspection type is active for inspection lot origin 03 (inspection during production)
• The other indicators for the inspection type are set appropriately to meet your requirements for
inspection lot processing.
• Inspection characteristics were created and assigned to one or more operations (production order) / one
or more phases (process order) used in the order.

 Note

In an integrated ERP system, you can create an additional value range, called first range, so that the
inspection results recorded in SAP Digital Manufacturing are checked against two value ranges: the
standard range and the first range.

• For quantitative characteristics, make sure the ISO codes have values and are mapped to respective
inspection characteristics. Otherwise, the characteristics will not be transferred to SAP Digital
Manufacturing. To check the ISO codes in integrated ERP systems, use the transaction code SE16N.

SAP Digital Manufacturing

• The Order POD is already configured with the Quality Inspection Characteristic List and the Quality
Inspection Results plugins.
• You have deployed the following artifacts in SAP S/4HANA Integration with SAP Digital Manufacturing
Cloud package in SAP Cloud Integration:
• API_INSPECTIONCATALOG_SRV
• API_INSPECTIONLOT_SRV
• API_CHARCATTRIBUTECATALOG_SRV

Procedure

An inspection during production is triggered by the release of a production order.

1. Release the order in SAP ERP or SAP S/4HANA.

2. Check and release the respective order in the Manage Orders app.
3. In the Order POD, select a specific order and you can verify the inspection characteristics of a specific
operation / phase on the Quality Inspection Characteristic List tab.

Related Information

Inspection Results Recording (Process Order and Order-Based Production Order) [page 193]

SAP Digital Manufacturing Integration Guide

192 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.12 Inspection Results Recording (Process Order and
Order-Based Production Order)

You can record inspection results and sychronize the data from SAP Digital Manufacturing for execution to SAP
ERP or SAP S/4HANA.

Prerequisites

SAP ERP or SAP S/4HANA

Inspection characteristics have been transferred from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing. For more information, see Inspection Characteristics Integration (Process Order and Order-
Based Production Order) [page 191].
SAP Digital Manufacturing

• The collaboration link COLLABORATION_INSPECTION_LOT is mapped to the directive INSPECTION_LOT

in the Manage Collaboration Links app.
• The Order POD is already configured with the Quality Inspection Results and the Quality Inspection Results
plugins.
• You have deployed the following artifacts in SAP S/4HANA Integration with SAP Digital Manufacturing
package in SAP Cloud Integration:
• API_INSPECTIONCATALOG_SRV
• API_INSPECTIONLOT_SRV
• API_CHARCATTRIBUTECATALOG_SRV

Procedure

1. In Manage Orders app, release the order for which the inspection is to be carried out.
2. In the Order POD, record the inspection results. Make sure you entered values for all mandatory inspection
characteristics.
3. Select one inspection characteristic and navigate to the details screen. There you can record the
inspection results. Make sure you entered values for all mandatory inspection characteristics.
4. Choose Save to save your entries.
5. On the characteristics overview screen, choose Submit Results to synchronize the results back to SAP ERP
or SAP S/4HANA.

Related Information

Inspection Characteristics Integration (Process Order and Order-Based Production Order) [page 191]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 193
2.1.5.2.13 Work Instruction (DMS Document) Integration

This function lets you transfer the document info records from SAP ERP to create work instructions in SAP
Digital Manufacturing for execution.

In particular, you can do the following:

• Transfer document info records attached to the production order

• Transfer document info records attached to routing operations

For more information about transferring document info records that are attached to the production order, see
Configuring a Production Order with Document Info Records [page 156].

2.1.5.2.14 Transfer of Floor Stock Data

You can transfer floor stock data for certain goods movement types from an SAP ERP or SAP S/4HANA system
to SAP Digital Manufacturing for execution.

Use

 Note

To use this functionality, you need to verify or update your integration configuration. For more information,
see Updating Integration Configuration to Use Floor Stock Data [page 199].

 Note

In SAP S/4HANA or SAP ERP, go to SPRO Production Integration with Manufacturing Execution
System Specify Production Storage Locations for an MES , and maintain your storage location with:

Business system set as the business system for SAP Digital Manufacturing for execution

Type set as Inventory management only by incoming transfer postings

The storage location configured as such only supports incoming goods movement 311. So if you still want
to post goods movement 261, make sure that not all storage locations are configured this way.

Inbound integration

Inbound integration messages include:

• Floor Stock Receipt (goods movement type 311)

• Floor Stock Receipt with Reservation (goods movement type 261)

Inbound integration messages can create inventory IDs and can change the location of inventory.

Outbound integration

Outbound integration messages include:

SAP Digital Manufacturing Integration Guide

194 PUBLIC SAP Digital Manufacturing for execution Integration
• Floor Stock Return (goods movement type 312)
• Floor Stock Return for specific orders (goods movement type 262)
• Goods Issue for Scrapping (goods movement type 551)

Outbound integration messages can change the location of goods, consume goods, and scrap goods in SAP
ERP or SAP S/4HANA.

The following scenarios are supported:

Floor Stock Receipt (replenishment, goods movement type 311)

In your SAP ERP or SAP S/4HANA system, you can use the transaction MIGO to trigger goods movement from
the central storage location to the production storage location.

The process for floor stock receipt without reservation (goods movement type 311 ) in SAP Digital
Manufacturing for execution assumes that the received goods are moved from a warehouse location to a
production location, so that they can be used during the production process. These quantities are recorded
and sent to SAP ERP or SAP S/4HANA as part of the production confirmation for consumption against the
production order.

• When you post a transfer of unrestricted-use stock from a central (issuing) storage location to a floor
stock (production) storage location in SAP ERP or SAP S/4HANA using the goods movement type
311 (transaction MIGO), the stock data is transferred from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution by the INVCON03 IDoc.
• SAP ERP or SAP S/4HANA triggers the IDoc INVCON03 to integrate the floor stock to the production
storage location (from Material Master or Production Order) in SAP Digital Manufacturing for execution
with Batch Number and Inventory ID created and Reserved Order Number attached to the new inventory.
The inventory is ready for consumption without reservation in SAP Digital Manufacturing for execution.
• A floor stock receipt is created for the specified components.

When yield /scrap collaboration is triggered, SAP Digital Manufacturing sends a confirmation to SAP ERP or
SAP S/4HANA to report consumed components.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 195
Production Order-Specific Consumption (goods movement type 261)

The process of floor stock receipt with reservation (goods movement type 261) in SAP Digital Manufacturing
assumes that the goods are issued from a warehouse location (central storage location) to an order
consumption.

In your SAP ERP or SAP S/4HANA system, you can use the transaction MIGO to trigger a goods issue to
order/reservation from the central storage location.

Goods consumption happens when a material leaves the storage location. This consumption creates an
inventory ID in SAP Digital Manufacturing for execution. This inventory ID is consumed during assembly
but this information is not reported to SAP ERP or SAP S/4HANA, because the consumption has already
happened.

• When you post a goods issue from a central storage location to a production order in SAP ERP or SAP
S/4HANA with the goods movement type 261 (transaction MIGO), the stock data is transferred through
the INVCON03 IDoc for order pegging in SAP Digital Manufacturing for execution.
• SAP ERP or SAP S/4HANA performs the goods issue to the respective production order.
• SAP ERP or SAP S/4HANA triggers the IDoc INVCON03 to integrate the floor stock to the production
storage location (from Material Master or Production Order) in SAP Digital Manufacturing with Batch
Number and Inventory ID created and Reserved Order Number attached to the new inventory.
• The inventory is ready for consumption only for the reserved order in SAP Digital Manufacturing for
execution.

Integration

• SAP ERP or SAP S/4HANA is the system of record for inventory management; SAP Digital Manufacturing
for execution is the system of record for floor stock management.
• A transfer posting in SAP ERP or SAP S/4HANA is used in the same way as a floor stock receipt in SAP
Digital Manufacturing for execution.
• For inventory ID records created in SAP Digital Manufacturing for execution through the integration, the
database field ERP_INVENTORY is equal to true.
• Floor storage location exists in both SAP ERP or SAP S/4HANA (LGORT) and SAP Digital Manufacturing for
execution (Storage Location); the Receiving Storage Location (UMLGO) exists only in SAP ERP.
• This function supports long material numbers (see Transfer of Long Material Number in the SAP Help
Portal).

Prerequisites

SAP ERP or SAP S/4HANA

• You have created production storage locations for floor stock materials.
• You have set up ALE communication to create and transmit INVCON03 IDocs.
• If you use SAP ERP 6.05 (with activated business functions LOG_PP_MES_INT_01 and
LOG_PP_MES_INT_02) or later, you have maintained integration of goods movements (see SAP Note
1555198 ).

SAP Digital Manufacturing Integration Guide

196 PUBLIC SAP Digital Manufacturing for execution Integration
• You have set up a filter for the goods movement type 261 and 311 (see Customizing for ALE
Communicaton on the SAP Help Porta).
• You have created a BOM for the finished good material of the order.

SAP Digital Manufacturing

• You have created and configured data type for floor stock integration.
• For materials to be received into floor stock and assembled, you have specified the following in the Manage
Materials app:
• Data to Collect on Assembly: INV or INV_SFC
• You have created a storage location matching SAP ERP or SAP S/4HANA Putaway Storage Location (see
Mapping a Production Order [page 211]).
• For the production order-specific consumption scenario, you have created or imported shop order data so
that components can be pegged (see Production Order Integration [page 148]).
• You have defined a numbering pattern for the number type floor stock receipt (see Configuring a
Production Order with Serial Numbers [page 152]).
• For the outbound integration with Inventory Management (IM), you have mapped the following
collaboration links to respective directives depending on your requirements in the Manage Collaboration
Links app.
• The link COLLABORATION_ERP_INV_CLEAR_RESERVATION is mapped to the directive
ERP_INVENTORY_CLEAR_RESERVATION.
• The link COLLABORATION_ERP_SCRAP_CONFIRMATION is mapped to the directive
ERP_SCRAP_CONFIRMATION.
• The link COLLABORATION_ERP_YIELD_CONFIRMATION is mapped to the directive
ERP_YIELD_CONFIRMATION.
• The link COLLABORATION_SFC_COMPONENT_ADD is mapped to the directive ERP_COMPONENT_ADD.
• If you have enabled EWM integration, configure the following collaboration links.
• The link EWM_COLLABORATION_COMPONENT_ADD is mapped to the directive EWM_COMPONENT_ADD.
• The link EWM_COLLABORATION_CONTAINER_CLOSE is mapped to the directive
EWM_CONTAINER_CLOSE_CONFIRMATION.
• The link EWM_COLLABORATION_SFC_DISPOSITION is mapped to the directive
EWM_SFC_DISPOSITION.
• The link EWM_COLLABORATION_YIELD_CONFIRMATION is mapped to the directive
EWM_GOODS_ISSUE_POST.

2.1.5.2.14.1 Configuring Floor Stocks

This section describes how to transfer floor stocks from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution to create corresponding floor stock records in the Manage Floor Stocks app.

 Note

You can transfer floor stocks through goods movement types 311 and 261.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 197
Prerequisites

SAP ERP or SAP S/4HANA

• You have created floor stock materials you want to transfer.

• You have created central storage locations and production storage locations for the floor stock materials.
• You have set up ALE communication to create and transmit INVCON03 IDocs.
• You have defined the DRF Replication Model to replicate INVCON03 IDocs. For more information, see Data
Replication Framework [page 36].

SAP Digital Manufacturing

• The floor stock materials are already downloaded from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing.
• You have created a production storage location matching ERP Putaway Storage Location (see Mapping a
Production Order [page 211]).
• The collaboration link COLLABORATION_BATCH_CHARACTERISTICS is mapped to the directive
BATCH_CHARACTERISTICS in the Manage Collaboration Links app.

Procedure

There are various methods to trigger the transfer of floor stocks. The following is one of the options.

1. Execute the transaction code MIGO to call up the Transfer Posting screen.
2. To transfer floor stocks for general usage, select Transfer Posting with goods movement type 311. If
you want to transfer floor stocks reserved for a specific order, select Goods Issue and Order with goods
movement type 261.
3. Check and post the goods movement.
4. Verify the results in the Manage Floor Stocks app or the Integration Message Dashboard in SAP Digital
Manufacturing.

Related Information

Integration Message Dashboard

Manage Floor Stocks

SAP Digital Manufacturing Integration Guide

198 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.2.14.2 Updating Integration Configuration to Use Floor
Stock Data

If you want to use floor stock integration functionality in SAP Digital Manufacturing, you need to update some
settings in your configuration integration, as shown here.

The SaaS tenant of your system must generate a new service instance and key for Digital Manufacturing
Cloud Services.

These are required for authentication in SAP Cloud Integration. You need to manually transfer this new service
instance and key as described here.

Prerequisites

• You have set up the SAP Cloud Connector.

• You have carried out the necessary steps in Integration with SAP S/4HANA or SAP ERP [page 9].

Steps

1. Go to the SaaS tenant of your system and generate a new service instance and key for digital-
manufacturing-services-**. Note down the clientid and clientsecret under the uaa tag.
2. Configure SAP Cloud Integration to connect with SAP Digital Manufacturing for execution.
1. Go to your SAP Cloud Integration tenant. In the side menu bar, choose Operations View and then
choose Security Material in Manage Security group.
2. Add User Credentials with the Name: CF_AUTH, the User: clientid, and the Password:
clientsecret.
3. Assign the collaboration directive ERP_INV_CLEAR_RESERVATION to the collaboration link
COLLABORATION_ERP_INV_CLEAR_RESERVATION for the inventory Return and Scrap activity.

Result

You can now use the floor stock functionality as described in this chapter.

Related Information

Setting Up the Cloud Connector [page 22]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 199
2.1.5.2.14.3 Transfer of Floor Stock Return and Scrap Data
You can transfer floor stock return and scrap data from SAP Digital Manufacturing for execution to SAP ERP or
SAP S/4HANA.

Use

This function lets you transfer floor stock return and scrap data from SAP Digital Manufacturing to SAP ERP or
SAP S/4HANA.

 Note

To use this functionality, you need to verify or update your integration configuration. For more information,
see Updating Integration Configuration to Use Floor Stock Data [page 199].

1. In SAP Digital Manufacturing, you can trigger the floor stock return to a central storage location and scrap
using a reason code.
2. The collaboration COLLABORATION_ERP_INV_CLEAR_RESERVATION (ERP_INV_CLEAR_RESERVATION)
is triggered iSAP Digital Manufacturing. This initiates the data synchronization to the ERP system.
3. In the ERP system, the floor stock is increased in the central storage location according to the return
request. The inventory in the production storage location is decreased according to the return and scrap
request.

The following scenarios are supported:

Production Order-Independent Floor Stock (311) Return (312) and Scrap (551)

The process below describes the flow of floor stock return and scrap in SAP Digital Manufacturing which will be
synchronized to ERP for production order-independent floor stock.

SAP Digital Manufacturing Integration Guide

200 PUBLIC SAP Digital Manufacturing for execution Integration
• The components are returned to the central storage location.
SAP ERP or SAP S/4HANA posts a goods movement of the type 312, the reversal of a one-step transfer
posting.
• The components are scrapped.
SAP ERP or SAP S/4HANA posts a scrapping movement of the type 551.

Production Order-Specific Floor Stock (261) Return (262) and Scrap (551)

The illustration shows the flow of floor stock return and scrap in SAP Digital Manufacturing, which is
synchronized to ERP for production order-independent floor stock.

• The Production order componentes are returned to central storage location.

SAP ERP or SAP S/4HANA reverses a goods issue of the production order components with movement
type 262.
• The components are scrapped.
SAP ERP or SAP S/4HANA scraps the Production shop order components.
• SAP ERP or SAP S/4HANA reverses a goods issue of the production order components with movement
type 262, then posts a scrapping movement (type 551).

Integration

• SAP ERP or SAP S/4HANA is the system of record for inventory management; SAP Digital Manufacturing
is the system of record for floor stock management.
• SAP Cloud Integration is used as the connector between the SAP Digital Manufacturing Manage Floor
Stock app and the SAP ERP or SAP S/4HANA floor stock control process for returning inventory and scrap.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 201
Prerequisites

SAP Digital Manufacturing

• You have received floor stock data from SAP ERP or SAP S/4HANA.
• You have verified the pre-defined reason codes.

SAP ERP or SAP S/4HANA

You have created a cost center for reporting material scrap quantities.

Activities

When you decrease the value of the Qty on Hand field for an inventory ID, enter a reason code and choose Save
in the Manage Floor Stock app in SAP Digital Manufacturing, SAP Cloud Integration sends a message to SAP
ERP or SAP S/4HANA to post the corresponding goods movements.

If the reason code has the prefix RTN-, the component quantity is returned to SAP ERP or SAP S/4HANA
Central Stores. If the reason code has the prefix SCR-, the component quantity is scrapped.

2.1.5.3 Field Mapping for Integration to SAP ERP or SAP

S/4HANA

This section describes what fields in an SAP ERP or SAP S/4HANA system are mapped to what fields in SAP
Digital Manufacturing.

2.1.5.3.1 Mapping a Material

You can transfer material data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc MATMAS03.

This table contains field names in SAP ERP and SAP S/4HANA and their corresponding field names in SAP
Digital Manufacturing for execution:

SAP Digital Manufacturing for

SAP ERP / SAP S/4HANA execution Comment

Plant (WERKS) Plant

Material Number (MATNR LONG) Material

SAP Digital Manufacturing Integration Guide

202 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP / SAP S/4HANA execution Comment

Material Description (MAKTX) Description In SAP ERP and SAP S/4HANA, you
can define the Material Description in
several languages.

 Note
You can only map material descrip­
tions in languages supported by
SAP Digital Manufacturing. Refer
to note 2722461 for an over­
view of supported languages. If you
require a language that isn't sup­
ported, you can use mediated inte­
gration to transform your mes­
sage content.

Current Version This field is not mapped from SAP ERP

or SAP S/4HANA. If this field is not
transferred from the CPI, then it has the
default value ERP001.

Status This field is not mapped from SAP

ERP or SAP S/4HANA. This is set as
RELEASABLE (201).

Unit of Measure (MEINS) Unit of Measure

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 203
 SAP Digital Manufacturing for
SAP ERP / SAP S/4HANA execution Comment

Material Type Material Type • Configurable: KMAT

• Finished: FERT
• General: MAT
• Nonstock: NLAG
• Nonvaluated: UNBW
• Operating Supplies: HIBE
• Packaging: VERP
• Returnable Packaging: LEIH
• Semifinished Product: HALB
• Service: DIEN
• Services: SERV
• Software Nonvaluated: SWNV
• Spare Parts: ERSA
• Trading Goods: HAWA
• Raw: ROH
• Custom: CSTM
• Pipeline: PIPE
• PRT: FHMI

Procurement Type (BESKZ) Procurement Type • Manufactured: M

• Purchased: P
• Manufactured / Purchased: B
• In-house Production: E

Batch Management Requirement Increment Batch Number If equal to X, set to Per Order, otherwise
Indicator (XCHPF) set to None.

Backflush(RGEKZ) Backflushing in ERP This field is not visible in SAP

Digital Manufacturing for execution.
If selected, the backflush indicator
(RGEKZ) value is True. If not selected,
the backflush indicator (RGEKZ) value
is False.

SAP Digital Manufacturing Integration Guide

204 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP / SAP S/4HANA execution Comment

Storage Location (LGPRO) ERP Production Storage Location or The length of ERP Production Storage
ERP Putaway Storage Location Location value must be less than or
equal to 4.

If the BESKZ value equals E, the LGPRO

value is stored in the ERP Putaway
Storage Location field. If the BESKZ
value isn’t equal to E, the LGPRO value
is stored in the ERP Production Storage
Location field.

Autocomplete and Confirm This field is not mapped from SAP ERP
or SAP S/4HANA. If this field is not
transferred from the CPI, then it has
the default value based on the value
of the Manufacturing Terminology set­
ting in the Manage Plants app. The
Autocomplete and Confirm flag is set to
Yes for discrete industry plants and to
No for process industry plants.

Mapping the European Article Number (EAN) and Units of Measure (UOMs) for ECC and SAP S/4HANA
SAP Digital Manufacturing for
SAP ERP / SAP S/4HANA execution Comment

E1MEANM unitsOfMeasureEans

EAN11 Ean.ean

EANTP Ean.category

HPEAN Ean.isMain

MEINH Ean.internalUom

BRGEW Ean.grossWeight

NTGEW Ean.netWeight

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 205
2.1.5.3.2 Mapping a Bill of Material (BOM)

Data is transferred from SAP ERP to SAP Digital Manufacturing for execution using the BOMMAT05 IDoc.

This table contains field names in SAP ERP and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

Plant (WERKS) Plant

Material Number (MATNR or BOM Material Number (MATNR) + "-"

MATNR_EXTERNAL), BOM Usage + BOM Usage(STLAN) + "-" +
(STLAN), Alternative BOM (STLAL) Alternative BOM (STLAL)

Bill of material ZTEXT or MATNR Description

MATNR_LONG or MATNR EXTERNAL

Status SAP ERP BOM status is mapped to SAP

ME BOM status as follows:

• 02 Inactive - New
• else Active - Releasable

Effectively Control R No logic in SAP Digital Manufacturing

for execution yet.

Current Version Selected

Bill of material (STLNR) ERP BOM

BOM Component (IDNRK) Component Saves the component as Primary.

No BOM alternates component sup­

port in SAP Digital Manufacturing for
execution yet.

BOM Item Number (POSNR) Sequence

BOM Component Type N

Test Part Deselected

Normalized Quantity for component Quantity

that is Component Quantity / Base
Quantity (MENGE_C / BMENG_C)

Installation Point for Subitem (EBORT) Ref Des

Ref Des Sequence 10

SAP Digital Manufacturing Integration Guide

206 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP execution Comment

Assembly Qty As Required The default value is calculated based

on the Manufacturing Terminology set­
ting of the Manage Plants app. The
Assembly Qty As Required flag is set to
No for discrete industry plants and to
Yes for process industry plants.

2.1.5.3.3 Mapping Alternate BOM Components

BOM components that belong to the same alternate group in SAP S/4HANA and ERP are mapped as alternate
components for each other in SAP Digital Manufacturing.

Master BOM Component

ERP / SAP S/4HANA

DME Field Default Value SAP S/4HANA Field

alternativeItemGroup ALPGR

ERP Alternate Item Group

alternates.enabled TRUE

Alternates Enabled

alternates.priority ALPRF

Alternates Priority

alternates.material IDNRK

Alternate Component

Order BOM

ERP / SAP S/4HANA

DME Field Default Value SAP S/4HANA Cloud Field

alternativeItemGroup ALPGR

ERP Alternate Item Group

alternates.enabled TRUE

Alternates Enabled

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 207
DME Field Default Value SAP S/4HANA Cloud Field

alternates.priority ALPRF

Alternates Priority

alternates.material MATNR

Alternate Component

2.1.5.3.4 Mapping a Routing with Operation Activities

Data is transferred from SAP ERP to SAP Digital Manufacturing for execution using the LOIROU04 IDoc.

LOIROU04 supports long material numbers (LMN) and mapping of work instructions. This table contains field
names in SAP ERP and their corresponding field names in SAP Digital Manufacturing for execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

Plant (WERKS) Plant

Key for Task List Group (PLNNR); Routing PLNNR + “-” + PLNAL
Group Counter (PLNAL) or /E1AFREF/
/E1AFREF/MES_ROUTINGID if the
MES_ROUTINGID
routing was created in SAP ME and
then sent to SAP ERP.

Version ERP001 for a new record and incre­

ments as necessary for updated re­
cords.

Routing Type U for a production routing type

V for a master recipe routing type

Short Description (KTEXT) Description

Status Releasable

Effectivity Control R No logic in SAP Digital Manufacturing

for execution yet.

Current Version Selected

Key for Task List Group (PLNNR); Entry Routing

Group Counter (PLNAL)

Entry Routing Type U

SAP Digital Manufacturing Integration Guide

208 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP execution Comment

Entry Routing Step ID 10

Key for Task List Group (PLNNR); Operation Activity PLNNR + “-” + PLNAL + “-”
Group Counter (PLNAL); Sequence + PLNFL + “-” + VORNR or
(PLNFL); Operation (VORNR) or ME_OPERATION_ID or UVORN
ME_OPERATION_ID or UVORN

Operation (VORNR) Reporting Step Operation step number in ERP. If sub-

operations are used, then the reporting
step is populated in a step mapped
from the last sub-operation within an
operation.

Rework Deselected

Sequence (FLAGAT) Data field: ERP_SEQUENCE 0. Only a zero sequence routing is sup­
ported.

Key for Task List Group (PLNNR), Operation Activity Operation activity master name
Group Counter (PLNAL), Sequence
(PLNFL), Operation (VORNR) or
 Note
ME_OPERATION_ID or UVORN Operation activity master records
can be created from the integration
as specified here. They can also
be created manually in the Manage
Operation Activities app.

Operation Activity Version ERP001 or ME_REVISION

Operation Short Text (LTXA1) Operation Activity Description

Maximum Loop Count Set to 0 in xslt in the CPI

Operation Activity Master Type N (Normal)

Work Center ID (ARBID) Work Center Based on the Work Center ID, SAP
Digital Manufacturing finds the work
center.

 Note
Replicate the work center before
the routing.

Relaxed Flow Relaxed Flow is set to Yes for recipes

and to No for routings.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 209
 SAP Digital Manufacturing for
SAP ERP execution Comment

Key for Task List Group (PLNNR), Operation Group PLNNR + “-” + PLNAL + “-”
Group Counter (PLNAL), Sequence + PLNFL + “-” + VORNR or
(PLNFL), Operation (VORNR) or ME_OPERATION_ID
ME_OPERATION_ID

Fields relevant for SAP ERP EhP05 and above

SAP Digital Manufacturing for
SAP ERP execution Comment

Operation Short Text (LTXA1) Description Routing step description

Operation Short Text (LTXA1) Description Operation activity description

Document number (DOKNR) Work Instruction DOKNR + ‘-’ + DOKAR + ‘-’

+DOKTL + ‘-’ + ORIGINAL
Document Type (DOKAR)

Document Part (DOKTL)

Application number (ORIGINAL)

Document Version (DOKVR) Version

2.1.5.3.5 Field Mapping for a Standard Value Key (SVK)

The fields created in SAP S/4HANA On-Premise and ERP correspond to certain fields of SAP Digital
Manufacturing for execution.

Work Center Download (LOIWCS) : Standard Value Key Mapping for an SV Group
SAP Digital Manufacturing for execution Field SAP S/4HANA On-Premise

.plant WERKS

.standardValKey VGWTS

StandardValue

.standardVal /CO_MES_STANDARD_VALUE_KEY_PULL/PARAME

.sequence 10 based sequence

Work Center Download (LOIWCS) : Standard Value Key Mapping for a StandardValueText
SAP Digital Manufacturing for execution Field SAP S/4HANA On-Premise

.locale EN

SAP Digital Manufacturing Integration Guide

210 PUBLIC SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing for execution Field SAP S/4HANA On-Premise

.description /CO_MES_STANDARD_VALUE_KEY_PULL/
PAR_DESCRIPTION

Routing Download (LOIROU) for a StandardValueTarget

SAP Digital Manufacturing for execution Field SAP S/4HANA On-Premise

.stepId 10 based sequence

.targetValue.value VGW01..VGW06

.targetValue.unitOfMeasure.uom VGE01..VGE06

2.1.5.3.6 Mapping a Production Order

You transfer production order data from SAP ERP to SAP Digital Manufacturing for execution using the IDoc
LOIPRO05 (used with SAP ERP EhP 05 and above).

This table contains field names in SAP ERP and the corresponding field names in SAP Digital Manufacturing for
execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

Plant (WERKS) Plant

Order Number (AUFNR) Production Order

Status (STAT) Status Last STAT segment in E1JSTKL; de­

faults to Releasable unless STAT equals:

I0045 - Technically completed (TECO)

If so, the status is set to Closed.

Priority 500

Material Number (MATNR or Planned Material

MATNR_EXTERNAL or MATNR_LONG)

Base Quantity (BMENGE) Build Qty

Base Quantity (BMENGE) Ordered Qty

Planned Start Date (GSTRP), Planned Planned Start GSTRP + GSUZP

Start Time (GSUZP)
If GSUZP left blank, defaults to 00:00:01

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 211
 SAP Digital Manufacturing for
SAP ERP execution Comment

Planned Finish Date (GLTRP), Planned Planned End GLTRP + GLUZP

Finish Time (GLUZP)
If GLUZP left blank, defaults to 00:00:01

Scheduled Start Date (GSTRS), Scheduled Start GSTRS + GSUZS

Scheduled Start Time (GSUZS)
If GSUZS left blank, defaults to 00:00:01

Scheduled Finish Date (GLTRS), Scheduled End GLTRS + GLUZS

Scheduled Finish Time (GLUZS)
If GLUZS left blank, defaults to 23:59:59

Sold-To Party Number (KUNAG) Customer

Sold-To Party Name (NAME1) Customer name

Base Unit of Measure (BMEINS) Custom data field: ERP_UOM This unit is converted in the IDoc in the
ISO unit of measure defined in SAP ERP
Customizing.

Database table column: Set to True by default (not present in

SHOP_ORDER.ERP_ORDER the GUI)

Storage Location (LGORT) ERP Putaway Storage Location

Batch (CHARG) Batch Number

Order Number (AUFNR) Planned BOM Same as shop order number

Bill of Material (STLNR) ERP_BOM

BOM Description Material Number (MATNR or

MATNR_EXTERNAL or MATNR_LONG)

SAP Digital Manufacturing Integration Guide

212 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP execution Comment

If there is an alternate group for BOM BOM Component Qty

components, then the component with
Priority 1 must be passed as a
BOM component in SAP ME, regard­
less of Usage Prob. The quantity of
this component must be calculated as
NOMNG divided by the order quantity
(BMENGE). All other components of
this alternate group must be passed as
alternate components of the BOM com­
ponent in SAP ME, regardless of Usage
Prob.

In all other cases, the quantity is calcu­

lated as component quantity (BDMNG)
divided by order quantity (BMENGE).

BOM Component Material Number BOM Component Only ERP components that populate
(MATNR or MATNR_EXTERNAL or the MATNR field are supported.
MATNR_LONG)

Key for Task List Group (PLNNR), BOM Component Assembly Operation Key for Task List Group (PLNNR) +
Group Counter (PLNAL), Sequence “-” + Group Counter (PLNAL) + “-” +
(PLNFL), Operation (VORNR) or Sequence (PLNFL) + “-” + Operation
ME_OPERATION_ID (VORNR) or ME_OPERATION_ID

BOM Component Assembly Operation Version of the assembly operation; de­

Version faults to # (not present in the GUI) or
ME_REVISION

BOM Component Assembly Qty As If this value is not by provided by

Required the CPI, then it is read from the
master BOM value. Otherwise, the de­
fault value is calculated based on the
Manufacturing Terminology setting of
the Manage Plants app. The Assembly
Qty As Required flag is set to No for
discrete industry plants and to Yes for
process industry plants.

BACKFLUSH Backflush Enabled If the BACKFLUSH = X, then Backflush

Enabled = Yes. Otherwise, No.

Routing Effectivity Control R

No logic in SAP Digital Manufacturing

for execution yet.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 213
 SAP Digital Manufacturing for
SAP ERP execution Comment

Material Number (MATNR or Routing Description

MATNR_EXTERNAL or MATNR_LONG)

Operation (VORNR) Reporting Step

Key for Task List Group (PLNNR), Operation

Group Counter (PLNAL), Sequence
(PLNFL), Operation (VORNR) or
ME_OPERATION_ID

Operation Version ERP001 or ME_REVISION

Operation Short Text (LTXA1) Operation Description

Maximum Loop Count 0

Operation Type N (Normal)

Sequence (RSPOS) Data field: SEQUENCE Sequence is calculated as RSPOS*10

Data field: IS_LAST_REPORTING_STEP If selected, this is the last ERP routing

step.

Material Number-BOM Explosion SFC (Sfc)

Number (MATNR- E1AFKOL/E1AFPOL/

E1AFSER/SERNR)

BOM Explosion Number (E1AFKOL/ Serial Number (SerialNumber)

E1AFPOL/

E1AFSER/SERNR)

Operation Short Text (LTXA1) Description Description of Routing Step

Operation Short Text (LTXA1) Description Operation description

Order Schedule List

KAPNAME Resource

Capacity ID (/E1AFKOL/E1AFFLL/ erpInternalID of resource SAP ME database field

E1AFVOL/E1KBEDL/KAPID)

Split Number (SPLIT) Split ID

Operation Quantity (MGVRG) Planned Quantity

SAP Digital Manufacturing Integration Guide

214 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP execution Comment

Start / Date (FSTAD) Start Time

Start / Time (FSTAU)

Finish / Date (FENDD) End Time

Finish / Time (FEDNU)

Earliest Setup Start / Date (FSAVD) Earliest Setup Start Time

Earliest Setup Start / Time (FSAVZ)

Latest Setup Start / Date (FSAVD) Latest Setup Start Time

Latest Setup Start / Time (FSAVZ)

Earliest Processing Start / Date Earliest Processing Start Time

(FSSBD)

Earliest Processing Start / Time

(FSSBZ)

Latest Processing Start / Date (FSSBD) Latest Processing Start Time

Latest Processing Start / Time (FSSBZ)

Earliest Teardown Start / Date (FSSAD) Earliest Teardown Start Time

Earliest Teardown Start / Time (FSSAZ)

Latest Teardown Start / Date (FSSAD) Latest Teardown Start Time

Latest Teardown Start / Time (FSSAZ)

Earliest Teardown Finish / Date Earliest Teardown End Time

(SSEVD)

Earliest Teardown Finish / Time

(SSEVZ)

Latest Teardown Finish / Date (SSEVD) Latest Teardown End Time

Latest Teardown Finish / Time (SSEVZ)

Earliest Waiting Finish / Date (FSSLD) Earliest Waiting End Time

Earliest Waiting Finish / Time (FSSLZ)

Latest Waiting Finish / Date (FSSLD) Latest Waiting End Time

Latest Waiting Finish / Time (FSSLZ)

Plan Setup Time (RUSET) Plan Setup Time

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 215
 SAP Digital Manufacturing for
SAP ERP execution Comment

Plan Processing Time (BEARZ) Plan Processing Time

Plan Teardown Time (ABRUE) Plan Teardown Time

Setup Time UoM (RSTZE) Setup Time UoM

Processing Time UoM (BEAZE) Processing Time UoM

Teardown Time UoM (ARZUE) Teardown Time UoM

Work Instructions

Document Number (DOKNR) Work Instruction DOKNR + ‘-’ + DOKAR + ‘-’

+DOKTL + ‘-’ + ORIGINAL
Document Type (DOKAR)

Document Part (DOKTL)

Application Number (ORIGINAL)

Document Version (DOKVR) Version

Original of document (FILENAME) ERP Filename

ME Integration: URL for Accessing ERP URL

Objects (URL)

Short Description of the Original Description

(DESCRIPTION) or

Document Description (DKTXT)

Work Instruction Attachments

Apply this to current version (#) of this Deselected

work instruction

Order Number (AUFNR) Order

2.1.5.3.7 Mapping a Production Yield Confirmation

(yieldConfirmationRequest or CorrelatedYieldConfirmationRequest) Data is transferred from

SAP Digital Manufacturing for execution to SAP ERP using the BAPI_PRODORDCONF_CREATE_TT or

SAP Digital Manufacturing Integration Guide

216 PUBLIC SAP Digital Manufacturing for execution Integration
CO_MES_PRODORDCONF_CREATE_TT (for SAP ERP 6.0 with EHP 5 or higher that uses Activated MES
Integration) BAPI.

This table contains field names in SAP ERP and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for Execu­

SAP ERP tion Comment

SFC Number (SFC_BO)

Plant (PLANT) Plant (PLANT)

Movement Type (MOVE_TYPE) 101 for parent material receipt, 261 for
component confirmation

Order Number (ORDERID) Order The order is determined from SFC_BO

Yield to Be Confirmed (YIELD) Quantity SFC quantity / quantity completed

(normally 1, except for a non-serialized
SFC)

Activity Number (OPERATION) Custom data field: REPORTING_STEP SAP ERP operation number related to
the process sequence number (routing
reporting step)

Batch Number (BATCH) Batch Number

FIN_CONF 1

CLEAR_RES X

CONF_QUAN_UNIT_ISO unitOfMeasure

Capacity Category (CAPA_CATEGORY) erpCapacityCategory

Split Number (SPLIT) Split ID (splitId)

IV_PROPOSE_BACKFLUSH X when components parameter in

Collaboration Directive is set to
onlyNonBackflushed

IV_2ND_TIME_CONFIRMATION X for repeated operation confirmation

(only for
CO_MES_PRODORDCONF_CREATE_TT)

GOODSMOVEMENTS segment

PLANT Plant

MOVE_TYPE The type of goods movement; 261 for

Goods Issue; 101 for Goods Receipt

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 217
 SAP Digital Manufacturing for Execu­
SAP ERP tion Comment

MATERIAL or MATERIAL_EXTERNAL or Material

MATERIAL_LONG

STGE_LOC storageLocation Floor Stock Storage Location available

for the selected inventory ID. If not
available, the value is defined in the
ERP Production Storage Location field in
Material Maintenance.

BATCH batchNumber

ENTRY_QNT Quantity

ENTRY_UOM_ISO unitOfMeasure

ORDERID orderNumber

Movement Indicator (MVT_IND) F for the movement type 101

IT_GOODSMVT_SERIALNUMBER segment (relevant for SAP ECC EhP05 and above)

Serial Number (SERIALNO) Serial Number (SERIALNO) Serial number (or SFC) of the main as­
sembly is sent from the last reporting
step (the movement type 101).

2.1.5.3.8 Mapping a Production Scrap Confirmation

Data is transferred from SAP Digital Manufacturing for execution to SAP ERP using the
BAPI_PRODORDCONF_CREATE_TT or CO_MES_PRODORDCONF_CREATE_TT BAPI.

This table contains field names in SAP ERP and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

SFC Number (SFC_BO)

Plant (PLANT) Plant

Movement Type (MOVE_TYPE) 261.

Order Number (ORDERID) Order The order is determined from SFC_BO

SAP Digital Manufacturing Integration Guide

218 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP ERP execution Comment

Yield to Be Confirmed (SCRAP) Quantity SFC quantity / quantity completed

(normally 1, except for non-serialized
SFC)

Activity Number (OPERATION) Custom data field: REPORTING_STEP SAP ERP operation number related to
the process sequence number (routing
reporting step)

Operation

Batch Number (BATCH) Batch Number

FIN_CONF 1

CLEAR_RES X

CONF_QUAN_UNIT_ISO unitOfMeasure

Capacity Category (CAPA_CATEGORY) erpCapacityCategory

Split Number (SPLIT) Split ID (splitId)

Component section

MOVE_TYPE The type of goods movement; 261 for

Goods Issue

MATERIAL or MATERIAL_EXTERNAL or item

MATERIAL_LONG

PLANT Plant

STGE_LOC Storage Location

BATCH batchNumber

ENTRY_QNT Quantity

CO_MES_PRODORDCONF_CREATE_TT BAPI name is changed from

BAPI_PRODORDCONF_CREATE_TT to
CO_MES_PRODORDCONF_CREATE_TT

CONF_ID messageID

ACTIVITY reportingStep

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 219
2.1.5.3.9 Mapping an Independent Components
Consumption

Data is transferred from SAP Digital Manufacturing for execution to SAP ERP using the
MB_MES_GOODSMVT_CREATE BAPI.

This table contains field names in SAP ERP and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

DETERMINE_RESERVATIONS Always set to X

GM_CODE Always set to 03

PSTNG_DATE Date Time (dateTime)

DOC_DATE Date Time (dateTime)

Storage Location (STGE_LOC) Storage location Floor Stock Storage Location available
for the selected Inventory ID. If not
available, the value is defined in ERP
Production Storage Location field in
Material Maintenance.

Batch Number (BATCH) Batch Number (batchNumber)

Consumption Quantity (ENTRY_QNT) Consumption Quantity

Order Number (ORDERID) Shop Order for pegged inventory

(shopOrder)

MOVE_TYPE 261

ACTIVITY Reporting Step Reporting step of a routing step where

component was assembled

GOODSMVT_SERIALNUMBER segment

SERIALNO ERP_SERIAL_NUMBER field collected

during assembly

SAP Digital Manufacturing Integration Guide

220 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.3.10 Mapping a Production Order Complete

Data is transferred from SAP Digital Manufacturing for execution to SAP ERP by calling the
BAPI_PORDORDCONF_CREATE_TT BAPI.

This table contains field names in SAP ERP and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP ERP execution Comment

Plant (PLANT) Plant

Order Id (ORDERID) Order Number

Operation (OPERATION) Operation

Yield (YIELD) 0

FIN_CONF X

CLEAR_RES X

2.1.5.3.11 Mapping a Release Order to MES

Data is transferred from SAP Digital Manufacturing for execution to SAP MES.

This table contains field names in SAP MES and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP MES execution Comment

Plant (plant) Plant

Order Id BO (shopOrderRef) Order Number BO

Quantity to release Quantity to Release

(quantityToRelease)

Work Center BO (workCenterRef) Work Center BO Optional

Add to new lot (addToNewLot) Add to new lot Optional

Allow RMA release Allow RMA release Optional

(allowRmaRelease)

Labor Charge Code BO Labor Charge Code BO Optional

(laborChargeCodeRef)

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 221
 SAP Digital Manufacturing for
SAP MES execution Comment

New SFC List segment Zero or more repetitions

SFC (id) SFC

2.1.5.3.12 Mapping an Updated Order Schedule to MES

Data is transferred from SAP Digital Manufacturing for execution to SAP MES.

This table contains field names in SAP MES and their corresponding field names in SAP Digital Manufacturing
for execution:

SAP Digital Manufacturing for

SAP MES execution Comment

Plant (plant) Plant

Shop Order Schedule segment 1 or more repetitions

Plant (plant) Plant

Router step BO (routerStepRef) Routing step BO

Sequence (sequence) Sequence

Resource BO (resourceRef) Resource BO Optional

Split ID (splitId) Split ID Optional

Planned Quantity Planned Quantity

(plannedQuantity)

Confirmed Quantity Confirmed Quantity Optional

(confirmedQuantity)

Planned start date (startDate) Planned start date

Planned end date (endDate) Planned end date Optional

Resource ERP ID Resource ERP ID Optional

(resourceErpInternalId)

Shop Order Number BO Order Number BO

(shopOrderRef)

SAP Digital Manufacturing Integration Guide

222 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.5.4 Units of Measure in SAP Digital Manufacturing for
execution

Materials are downloaded to SAP Digital Manufacturing for execution with their base units of measure (UOM)
as well their alternate units. Other business objects, such as orders, have their own units of measure. Internal
units are converted into commercial units.

SAP Digital Manufacturing for execution supports the following unit of measure features:

• Standard units of measure

• Internal units defined as primary ISO codes are converted into commercial units
• The names of commercial units are displayed on the screen in the local language. For example, the
abbreviation for "bottle" in English is BT while in German it is FL. The commercial unit abbreviation is
language-dependent.
• Custom units of measure

 Note

Since release 2108, you can create, view, and delete custom units of measure. In case custom units
of measure are used, make sure to set up custom units of measure before attempting to download
business objects such as a material. You can add your custom units of measure to an already existing
dimension group. To do this, you need to enter the code for the necessary dimension group. For more
information, see Unit of Measure .

2.1.5.5 Allowed Characters for Key Fields

When you transfer master data such as materials or work centers to SAP Digital Manufacturing for execution,
key fields can contain only allowed characters.

If key fields contain characters that aren't allowed, the data transfer fails. The following table provides an
overview of the allowed characters.

Allowed Characters Description

Alphanumeric characters Any combination of letters and numbers

Spaces Allowed before, between, and after characters.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 223
Allowed Characters Description

Special characters You can use the following special characters:

• Asterisk *
• At sign @
• Caret ^
• Closed parenthesis )
• Equals sign =
• Exclamation mark !
• Hyphen -
• Open parenthesis (
• Period .
• Plus sign +
• Tilde ~
• Underscore _

2.1.5.6 Mapping Plants (Plant Conversion)

You can enable the plant conversion feature if you need to integrate more than one plant with the system.

If you need to integrate more than one ERP system with SAP Digital Manufacturing, you can use this feature to
convert ERP plants to corresponding plants in SAP Digital Manufacturing.

 Note

Plant mapping (plant conversion) isn't compatible with direct communication scenarios involving SAP S/
4HANA. For more information, see Enable Direct Communication To SAP S/4HANA [page 107].

 Note

You can use plant conversion for production orders (LOIPRO05) and process orders (LOIPRO05).

 Note

If you want to use plant conversion in the context of an integration with EWM, see Mapping Plants (Plant
Conversion) [page 340]

Follow the steps to configure plant mapping values in SAP Cloud Integration.

• Log on to SAP Cloud Integration and choose  (Build and develop integration content) in the side bar
menu.
• Search for the SAP S/4HANA Integration with SAP Digital Manufacturing package.
• Choose the package and choose the Artifacts tab.
• Choose the Plant Value Mapping artifact.
• Choose Edit.

SAP Digital Manufacturing Integration Guide

224 PUBLIC SAP Digital Manufacturing for execution Integration
• In the ERP column, enter the plant name defined in the ERP system. In the corresponding column for SAP
Digital Manufacturing, enter the plant name you want to define in SAP Digital Manufacturing.

 Note

You can map your 3-tier landscape for your SAP ERP or SAP S/4HANA system to a 2-tier SAP Digital
Manufacturing landscape without changing your plant identifiers using the plant conversion functionality.
The setup looks like this:

For more information, see Bridging a 3-Tier SAP ERP Landscape to a 2-Tier SAP Digital Manufacturing
Cloud Landscape .

Related Information

How to Get SAP Cloud Integration Management URL [page 20]

2.1.6 Customizing the Integration Scenario

You can customize your integration scenario by using predefined XSLT code and standard integration flows, or
by implementing your own XSLT transformation rules and integration flows.

Overview

You can adapt your integration with SAP ERP or SAP S/4HANA to your needs by using the predefined
customizing options available through predefined XSLT code in the Manage Integration Workflows app together

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 225
with the standard integration flows from the SAP S/4HANA Integration with SAP Digital Manufacturing package
in SAP Cloud Integration. This is the recommended approach.

If you want to implement your own integration flows in SAP Cloud Integration, you need to create custom
integration workflows in the Manage Integration Workflows app that make sure that the field mapping between
ODATA and BAPI messages takes place between SAP Digital Manufacturing and SAP Cloud Integration.

For more information see:

• Predefined Customizing Options Using XSLT [page 226]

• User-Defined Customizing Options [page 227]

2.1.6.1 Predefined Customizing Options Using XSLT

You can customize integration workflows using XSLT in the Manage Integration Workflows app in SAP Digital
Manufacturing to benefit from certain fields or attributes that aren't covered by the standard workflows.

Use

In SAP Digital Manufacturing, you can add additional fields to various apps to include certain pre-defined or
customer-specific attributes and data. These attributes and data are transferred within iDoc messages from
SAP ERP or SAP S/4HANA to SAP Digital Manufacturing transiting through SAP Cloud Integration. Although
the main part of the workflow (iFlow) configuration takes part in SAP Cloud Integration, some configurations
can be done using XSLT code in the Manage Integration Workflows app in SAP Digital Manufacturing. In this
app, you can change the XSLT code that transforms the incoming iDoc messages into messages that SAP
Digital Manufacturing uses internally. By changing the XSLT code, you can make sure that, for example, the
value of a certain attribute that normally doesn't make it into SAP Digital Manufacturing is available there.

Predefined Customizing Options

You can choose among many predefined customizing options that are already contained in the standard
XSLT code but are commented out. In the Manage Integration Workflows app, you can choose a workflow, for
example LOIPRO05_PRODORDER, copy the whole XSLT script from the Standard XSLT field into the Custom
XSLT field. Then you uncomment the section that you want to activate.

For detailed information on the existing custom XSLT options and on how to activate them using the Manage
Integration Workflows app, see Manage Integration Workflows.

 Note

If you need data from different systems, the best approach is usually to consolidate this data in a single
system before sending it to SAP Digital Manufacturing. This is even more important if the data needs to be
consolidated, including ID mappings, for example.

SAP Digital Manufacturing Integration Guide

226 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

If you're already working with your own custom XSLT and need to find the exact positon where an XSLT
snippet needs to be inserted to activate a new functionality, you can refer to the position of that XSLT
snippet in the Standard XSLT.

 Note

You can check your integration scenario using the Check Integration Configuration functionality provided by
the Integration Message Dashboard app.

After choosing Check Integration Configuration, you select an integration message to start an automated
test of the integration configuration that covers the full integration scenario from SAP Digital
Manufacturing to the connected ERP system and back. The following tests are performed:

• Destination check
• SAP Cloud Integration parameter check
• SAP Cloud Integration artifact check
• Inbound connectivity check

In case of an error, a message will point you to the solution.

Related Information

Manage Integration Workflows

2.1.6.2 User-Defined Customizing Options

You can adapt your integration scenario to your needs by using custom integration flows in SAP Cloud
Integration and custom integration workflows in the Manage Integration Workflows app.

Overview

Instead of using the standard integration flows provided by SAP Digital Manufacturing through the SAP S/
4HANA Integration with SAP Digital Manufacturing package, you can create custom integration flows in SAP
Cloud Integration. To know more about how to create custom integration flows, see SAP Cloud Integration.

When working with custom integration flows in SAP Cloud Integration, you need to create custom integration
workflows in the Manage Integration Workflows app that take over data from an SAP Cloud Integration
integration flow or pass data to the integration flow.

 Note

It's recommended to use the standard integration flows provided by the SAP S/4HANA Integration with
SAP Digital Manufacturing package in connection with the standard / custom XSLT options available in the

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 227
 Manage Integration Workflows app. For more information, see Predefined Customizing Options Using XSLT
[page 226].

Inbound and Outbound Integration

Once you've created and deployed your custom integration flow in SAP Cloud Integration, you need perform
some configurations in SAP Digital Manufacturing to enable the communication between SAP ERP or SAP
S/4HANA and SAP Digital Manufacturing. These configurations are described in the following topics:

• SAP Cloud Integration to SAP Digital Manufacturing [page 228]

• SAP Digital Manufacturing to SAP Cloud Integration [page 230]

Related Information

Predefined Customizing Options Using XSLT [page 226]

2.1.6.2.1 SAP Cloud Integration to SAP Digital

Manufacturing

You can connect your custom SAP Cloud Integration integration flow to SAP Digital Manufacturing using the
Manage Integration Workflows app.

Prerequisites

• The technical integration has been implemented. For more information, see Technical Integration with SAP
S/4HANA or SAP ERP [page 14].
• You've got the root name of the iDoc that is sent from your integrated ERP system to SAP Cloud
Integration.
• You've created and deployed your custom integration flow in SAP Cloud Integration. This integration flow
fetches the incoming data and sends it to SAP Digital Manufacturing.
• You've got the Service Workflow name of your SAP Cloud Integration integration flow.
• You've created some XSLT code that you can use in the Manage Integration Workflows app in SAP Digital
Manufacturing to transform the incoming data.

SAP Digital Manufacturing Integration Guide

228 PUBLIC SAP Digital Manufacturing for execution Integration
Context

You can connect your custom SAP Cloud Integration integration flow to SAP Digital Manufacturing using the
Manage Integration Workflows app to adapt your communication scenario to your needs.

 Tip

If you're an integration developer and want to learn more about how to design integration flows, you
can refer to the Integration Flow Design Guidelines. You'll find there lots of information on the underlying
concepts as well as practical examples that will help you deepen your knowledge. For more information, see
Integration Flow Design Guidelines.

If you're particularly interested in optimizing workflow performance, you can jump right to this topic:
Optimize Performance.

 Note

For more information about the xslt fields available in the Manage Integration Workflows app, see Manage
Integration Workflows.

Procedure

1. In SAP Digital Manufacturing, go to the Manage Integration Workflows app.

2. On the Custom Workflow tab, choose Create.
3. Under Root Name, enter the root name of your iDoc.
4. Optional: Enter an Identifier to mark the outgoing message.

The identifier of your message will be found under Application Message ID in SAP Cloud Integration.

5. Under Service Configuration Pre-Service Stage Configuration XSLT enter your XSLT code.

6. Under Service Stage Configuration Service Workflow , enter the name of your service workflow.
7. Choose Save.

Results

You've added your custom integration workflow to the Manage Integration Workflows app.

To verify whether the integration workflow works as planned, you've got two options:

1. In SAP Digital Manufacturing for execution, go to the Integration Message Dashboard and check the status
of the corresponding outgoing message. For more information, see Integration Message Dashboard.
2. In SAP Cloud Integration, go to Monitor Message Processing and check the status of the message
corresponding to your custom integration workflow. For more information, see Monitoring Message
Processing.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 229
2.1.6.2.2 SAP Digital Manufacturing to SAP Cloud
Integration

You can adapt your outbound integration scenario by modifying the standard integration workflows available in
the Manage Integration Workflows app.

For integration scenarios involving outbound custom integration flows in SAP Cloud Integration, you can adapt
the standard integration workflows available in the Manage Integration Workflows app, so that they call the
custom integration flows that you've implemented in SAP Cloud Integration during execution.

You can add references to your SAP Cloud Integration custom integration workflows in the following fields of
the standard integration flows available in the Manage Integration Workflows app:

Field Description

Workflow URL The referenced artifact takes over control.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

Pre-Service Stage Configuration / Custom Pre-XSLT With this field, you can enhance the outgoing message be­
Workflow fore the message transformation using a custom artifact in
SAP Cloud Integration. This artifact then takes precedence
over the standard pre-XSLT transaction.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

Pre-Service Stage Configuration / Custom Post-XSLT With this field, you can enhance the outgoing message after
Workflow the message transformation using a custom artifact in SAP
Cloud Integration. This artifact then takes precedence over
the standard post-XSLT transaction.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

Service Stage Configuration / Custom Service Workflow With this field, you can define a SAP Cloud Integration arti­
fact that sends the transformed message to the destination
system to perform the intended action. This artifact then
takes precedence over the standard service transaction.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

SAP Digital Manufacturing Integration Guide

230 PUBLIC SAP Digital Manufacturing for execution Integration
Field Description

Post-Service Stage Configuration / Custom Post-Service With this field, you can enhance the message received as a
Workflow
result of the service transaction using a custom artifact in
SAP Cloud Integration. This artifact then takes precedence
over the standard post-service transaction.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

Custom Error Handler Workflow With this field, you can define which custom artifact in SAP
Cloud Integration should perform actions after the service
transaction has failed. This artifact takes precedence over
the standard fail handler transaction.

You need to enter the address of the ProcessDirect

adaptor that triggers your custom artifact in SAP Cloud
Integration.

2.1.7 Upgrade Information

This section describes the manual activities that are required with the upgrade of SAP Digital Manufacturing
for execution.

Update SAP Cloud Integration Package

To use certain new features of the new release, you need to update the respective SAP Cloud Integration
package. You can only update the package to the latest version.

 Tip

You can find the change log of the SAP S/4HANA Integration with SAP Digital Manufacturing package here:
3315636 .

1. Log on to your SAP Cloud Integration tenant. To find the URL for the SAP Cloud Integration, see How to Get
SAP Cloud Integration Management URL [page 20].
2. Choose the Click to work with content packages icon in the side bar menu.
3. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
4. Choose Update package.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 231
When the update is completed, you can see the supported new features in the Change log of the Documents
tab.

Deploy iFlows

To enable the new features of each release, you need to deploy the respective artifacts in SAP Cloud
Integration.

1. Log on to your SAP Cloud Integration tenant. To find the URL for the SAP Cloud Integration, see How to Get
SAP Cloud Integration Management URL [page 20].
2. Choose the Click to work with content packages icon in the side bar menu.
3. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
4. In the Artifacts tab, find the artifacts of new features you want to enable, and choose the Action icon.
5. Choose Deploy.

SAP Digital Manufacturing Integration Guide

232 PUBLIC SAP Digital Manufacturing for execution Integration
2.1.8 Restrictions and Limitations

This page lists the current restrictions and limitations of SAP ERP or SAP S/4HANA integration.

• Goods Issue
The goods issue from central storage location can't be triggered from SAP Digital Manufacturing. It is
triggered from SAP ERP or SAP S/4HANA.
• Goods Movement
The goods movement from production storage location and between production storage locations can't
be triggered from integrated SAP ERP or SAP S/4HANA system. It is triggered from SAP Digital
Manufacturing only.
• Material-Level Batch Management
Material level is the only supported batch level. The batch number is unique in all plants in connection with
the material. Plant level and client level batch management are not available.

 Note

You must choose the material level as the batch level in SAP ERP or SAP S/4HANA systems.
Otherwise, you might encounter inventory transfer issues from ERP systems to SAP Digital
Manufacturing.

• Long Material Number and Batch

Long material number is not supported in all batch scenarios including inventory download with batch
number, batch creation, batch characteristic update and goods receipt with batch number.
• Integration Scenarios of Process Industry
For more information about the integration scenarios that are not available for the process industry, see
the Limitations section in 2968056 .
• Backflush Enabled Material
If backflush is enabled for a material in ERP, when you transfer relative production or process orders
from SAP S/4HANA, the backflush indicator is not downloaded with the order. This may cause some data
inconsistencies between SAP Digital Manufacturing and SAP S/4HANA in transcations such as goods
issue or goods receipt.
• Allowed Values at Material Level for Batch (class type 023)
Allowed values defined at material level for class type 023 in SAP S/4HANA are not downloaded to SAP
Digital Manufacturing. This may result in errors in synchronizing batch characteristic updates back to SAP
S/4HANA.
• Order Change from ERP System before Release
Before releasing an order to the shop floor in the Manage Orders app, you can update it from your
integrated ERP system. The updating options you have vary depending on the order type and the
integrated ERP system. For more information, see Updating Orders Before the Release [page 185].
• Inbound Message Payload
For inbound integration messages, the maximum supported request payload size is 500 kilobytes.
• Standard Value Download
If you want to use To Be Confirmed values instead of the standard values, you must use LOIPRO05 V2 to
download the order data.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 233
2.2 Integration with SAP S/4HANA Cloud

You can enable the communication between SAP S/4HANA Cloud and SAP Digital Manufacturing.

 Note

Since SAP Digital Manufacturing is a software service on SAP Business Technology Platform, Cloud
Foundry environment, integration with SAP S/4HANA Cloud doesn't require SAP Cloud Integration or
cloud connector which are both used for integration between cloud application and on-premise systems.

Use the Communication Management apps to enable data exchange between SAP Digital Manufacturing and
SAP S/4HANA Cloud.

After you have completed the onboarding procedures as mentioned in Onboarding and User Management,
you can continue with the configurations that are required to build up connectivity between SAP Digital
Manufacturing and integrated SAP S/4HANA Cloud. For detailed steps, see Technical Integration with SAP
S/4HANA Cloud [page 238].

For more details about supported data exchange between the systems, see Business Integration with SAP
S/4HANA Cloud [page 265].

Related Information

Minimum Version Requirements and Supported Scenarios [page 234]

Restrictions and Limitations [page 313]

2.2.1 Minimum Version Requirements and Supported

Scenarios

Here are the minimum release requirements, supported scenarios, and limitations for integrating SAP Digital
Manufacturing with SAP S/4HANA Cloud.

Minimum Release Requirements

SAP Digital Manufacturing is compatible with SAP S/4HANA Cloud releases 2002 or higher.

SAP Digital Manufacturing Integration Guide

234 PUBLIC SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Objects Integrated with SAP Digital Manufacturing

Object Communication Scenario

Material SAP_COM_0009

Material classification SAP_COM_0163, SAP_COM_0309

BOM SAP_COM_0105

Goods movement SAP_COM_0108, SAP_COM_0263

Batch number SAP_COM_0337

Recipe and production version SAP_COM_0519

Process order SAP_COM_0522

Production order SAP_COM_0522

Quality inspection SAP_COM_0318

Inspection lot SAP_COM_0110

Material stock SAP_COM_0164

QM defect code groups and codes SAP_COM_0153

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 235
2.2.2 Overview Integration with SAP S/4HANA Cloud for
Discrete Industries

The following diagram provides an overview of the integration of SAP Digital Manufacturing for execution and
SAP S/4HANA Cloud for discrete industries. Select highlighted areas for more detailed information.

• Integration of Master Data [page 265]

• Transfer of Work Centers from SAP S/4HANA Cloud [page 267]
• Transfer of QM Defect Code Groups and Codes from SAP S/4HANA Cloud [page 268]
• Transferring Production Order with PRT Assignment [page 272]
• Inspection Characteristics Integration (Production Order) [page 280]
• Transfer of Floor Stock Data [page 273]
• Inspection Results Recording (Production Order) [page 281]
• Transfer of Floor Stock Return Data [page 277]
• Staging Request Upon Order Release
• Material Consumption (Order POD)
• Goods Receipt (Work Center POD)
• Goods Receipt (Order POD)
• Integration with SAP Business Network Asset Collaboration [page 313]
• Integration with EWM [page 317]
• Component Removal

SAP Digital Manufacturing Integration Guide

236 PUBLIC SAP Digital Manufacturing for execution Integration
2.2.3 Overview Integration with SAP S/4HANA Cloud for
Process Industries

The following diagram provides an overview of the integration of SAP Digital Manufacturing for execution and
SAP S/4HANA Cloud for process industries. Select highlighted areas for more detailed information.

• Integration of Master Data [page 265]

• Transfer of Work Centers from SAP S/4HANA Cloud [page 267]
• Transfer of QM Defect Code Groups and Codes from SAP S/4HANA Cloud [page 268]
• Inspection Characteristics Integration (Production Order) [page 280]
• Transfer of Floor Stock Data [page 273]
• Inspection Results Recording (Production Order) [page 281]
• Transfer of Floor Stock Return Data [page 277]
• Staging Request Upon Order Release
• Material Consumption (Order POD)
• Goods Receipt (Order POD)
• Integration of Master Data [page 265]
• Integration of Transaction Data [page 271]
• Integration with EWM [page 317]
• Batch Characteristics Update [page 279]
• Batch Creation [page 280]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 237
2.2.4 Technical Integration with SAP S/4HANA Cloud
You can transfer data between SAP S/4HANA Cloud and SAP Digital Manufacturing for execution using various
communication arrangements.

This page demonstrates the steps that are required to enable data transfer between these two systems.

• #unique_215/unique_215_Connect_42_subsection-im1 [page 238]

• #unique_215/unique_215_Connect_42_subsection-im2 [page 239]
• #unique_215/unique_215_Connect_42_subsection-im3 [page 239]
• #unique_215/unique_215_Connect_42_subsection-im4 [page 239]
• #unique_215/unique_215_Connect_42_subsection-im5 [page 239]

Create Destinations
Create destinations in your SAP Digital Manufacturing for execution subaccount in SAP BTP cockpit.

Use the following destinations for inbound integration:

• S4H_ODATA_INTEGRATION
• S4H_INTEGRATION_OAUTH

Use the following destinations for outbound integration:

• S4H_ODATA_INTEGRATION

For more information, see Creating Destinations [page 262].

SAP Digital Manufacturing Integration Guide

238 PUBLIC SAP Digital Manufacturing for execution Integration
Create a Communication User
Create a communication user in SAP S/4HANA Cloud for inbound calls. For more information, see Creating a
Communication User [page 241].

Create a Communication System

Create a communication system in SAP S/4HANA Cloud.

To create a communication system, you need to provide the following:

• The application route link of the integration microservice for the host name (use the value of the
"manufacturing-execution-integration" property in the service key of the service instance). For
more information, see Creating a Service Instance and a Service Key [page 243].
• A user ID and password for the outbound communication user (taken from the Saas-tenant, in the service
key of the service instance). For more information, see Creating a Service Instance and a Service Key [page
243].

For more information, see Creating a Communication System [page 242].

Create a Communication Arrangement

Select one of the following communication scenarios in SAP S/4HANA Cloud to create a communication
arrangement:

Communication Scenario ID Communication Scenario Name

SAP_COM_0009 Product Integration

SAP_COM_0105 Product Lifecycle Management - Master Data Integration

SAP_COM_0163 Classification Systems OData Integration

SAP_COM_0309 Product Classification Integration

SAP_COM_0519 Production Planning Master Data Integration

SAP_COM_0522 Manufacturing Execution - Order and Confirmation

Integration

For more information, see Creating Communication Arrangements [page 245].

Confirm Integration
Confirm the transfer of a specific business object (for example, a product or master recipe) from an application
in SAP S/4HANA Cloud (for example, the Replicate by Object Selection app or the Replicate by Model Selection
app) to SAP Digital Manufacturing for execution.

After setting up this integration, you need to configure the collaboration links and directives. For more
information, see Manage Collaboration Links.

 Note

Do not enter any personal data in any text fields or in any files uploaded to SAP Digital Manufacturing for
execution.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 239
  Note

You can check your integration scenario using the Check Integration Configuration functionality provided by
the Integration Message Dashboard app.

After choosing Check Integration Configuration, you select an integration message to start an automated
test of the integration configuration that covers the full integration scenario from SAP Digital
Manufacturing to the connected ERP system and back. The following tests are performed:

• Destination check
• SAP Cloud Integration parameter check
• SAP Cloud Integration artifact check
• Inbound connectivity check

In case of an error, a message will point you to the solution.

Related Information

Integration of Master Data [page 265]

Integration of Transaction Data [page 271]
Manage Collaboration Links

2.2.4.1 Before You Start

This page shows you the prerequisite steps that must be completed before configuring the integration with
SAP S/4HANA Cloud.

Before you start, you must have performed the following steps:

• Complete the onboarding process

 Note

This includes the configuration of the S4H_INTEGRATION_OAUTH destination. The destination data
is used by SAP Digital Manufacturing to provide authentication and authorization for internal system
communication. You also require it to integrate with SAP ERP, SAP S/4HANA, and SAP S/4HANA
Cloud.

 Tip

As an option, you can include SAP Cloud Integration as a middleware to enhance your integration
between SAP S/4HANA Cloud and SAP Digital Manufacturing with an indirect component.

SAP Digital Manufacturing Integration Guide

240 PUBLIC SAP Digital Manufacturing for execution Integration
Next Steps

• Creating a Service Instance and a Service Key [page 243]

• Creating a Communication User [page 241]
• Creating a Communication System [page 242]
• Creating Communication Arrangements [page 245]

2.2.4.2 Creating a Communication User

To integrate SAP Digital Manufacturing with SAP S/4HANA Cloud, you need to create a communication user.

Prerequisites

You've got the ADMINISTRATOR role in SAP S/4HANA Cloud.

Context

To integrate SAP Digital Manufacturing with SAP S/4HANA Cloud, you need to create a communication user
with a password in SAP S/4HANA Cloud. Once it has been assigned to a communication system representing
SAP S/4HANA Cloud, the communcation user enables SAP Digital Manufacturing to access SAP S/4HANA
Cloud.

Procedure

1. In SAP S/4HANA Cloud, go to Communication Management.

2. Choose Maintain Communication Users.
3. Choose New.
4. Enter the user name, for example DM_COM_USER and a description.
5. Enter a password.
6. Choose Create.

Results

You've created a communication user that will be assigned to a communcation system later.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 241
2.2.4.3 Creating a Communication System

To integrate SAP S/4HANA Cloud and SAP Digital Manufacturing, you need to create a communication system.

Prerequisites

• You've got the Administrator role for SAP S/4HANA Cloud.

• You've created a communication user and a password. For more information, see Creating a
Communication User [page 241].
• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've got the ID of your system.
• You've got the ID of your logical system.
• You've got the ID of your business partner.

Context

To establish a connection between SAP S/4HANA Cloud and SAP Digital Manufacturing, you need to
create a communication system in SAP S/4HANA Cloud, which represents SAP S/4HANA Cloud. In this
communication system, you register the partner systems with their respective credentials. For inbound calls
to SAP S/4HANA Cloud, you add the communication user and its password. For outbound calls to SAP Digital
Manufacturing, you use the client ID and client secret of the service key that you've created in your SAP Digital
Manufacturing subaccount in SAP BTP cockpit.

Procedure

1. In SAP S/4HANA Cloud, go to the Communication Management.

2. Choose Communication Systems.
3. To create a new communication system, choose New
4. On the New Communication System screen, make the following entries:

Field Value

System ID Enter an ID of your choice, for example SAP_DM_TENANT

System Name Enter a name of your choice, for example SAP Digital
Manufacturing

5. Choose Create.
6. In the General tab, make the following entries in the Technical Data section:

SAP Digital Manufacturing Integration Guide

242 PUBLIC SAP Digital Manufacturing for execution Integration
 Field Description

Host Name Enter the tenant address taken from the service key
that you've created in your SAP Digital Manufacturing
subaccount. You can find it in the service key creden­
tials under the property manufacturing-execution-
integration.

 Example
{…}-integration-
ms.cfapps.sap.hana.ondemand.com

Logical System ID Enter an ID of your choice, for example

SAP_DM_TENANT.
Port Use the default value, for example, 443.

Business System Enter an ID of your choice, for example

SAP_DM_TENANT.

7. On the User for Inbound Communication tab, choose Add to specify the user name.
8. Select User Name and Password as the Authentication Method.
9. Choose OK.
10. Use the credentials that were used to create the communication user.
11. On the User for Outbound Communication tab, for the Authentication Method, select User Name and
Password.
12. For the user name and password, use the clientid and client secret from the service key.
13. On the Business Partners tab, select the business partner.
14. Choose Create.
15. Choose Save.

2.2.4.3.1 Creating a Service Instance and a Service Key

Create a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP BTP cockpit
to integrate with SAP S/4HANA Cloud.

Prerequisites

• You've completed the Onboarding Process.

• You've got the Administrator role for SAP BTP cockpit.
• You've got access to the SAP Digital Manufacturing subaccount in SAP BTP cockpit.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 243
Context

To enable communication from SAP S/4HANA Cloud to SAP Digital Manufacturing, you need to create a
service instance and a service key supporting OAUTH 2.0 client credential authentication (client ID / client
secret) in your SAP Digital Manufacturing subaccount in SAP BTP cockpit.

Procedure

1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.

2. Go to Services Instances and Subscriptions and choose Create.

The New Instance or Subscription popup opens.

3. Enter the following fields to create a service instance:

Field Value

Service SAP Digital Manufacturing Cloud Services

Plan execution

Runtime Environment Cloud Foundry

Space Name of your space

4. Choose Next and leave the Parameters popup empty.

5. Choose Next and Create.
6. Under Instances, choose the instance that you've created.
7. On the Service Key tab, choose Create.

The New Service Keys popup opens.

8. Enter the following fields to create a service key supporting client ID / client secret:

Field Value

Service Key Name Service Key

 Note
You can choose a random name.

9. Choose Create.

 Note

You can access the service key content by choosing  and then View.

SAP Digital Manufacturing Integration Guide

244 PUBLIC SAP Digital Manufacturing for execution Integration
Results

You've created a service instance and a service key supporting OAuth 2.0 client credential authentication.

2.2.4.4 Creating Communication Arrangements

A communication arrangement specifies the metadata for a specific communication scenario, such as material
replication. The metadata for the communication arrangement is contained in a service key. You can define one
or more destinations for a communication arrangement.

You need to create a communication arrangement to allow inbound communication to the SAP S/4HANA
Cloud tenant and outbound communication to the SAP Digital Manufacturing for execution tenant. The
communication arrangement defines the user and the system for specific communication scenarios.

For general information on communication arrangements and how to create them, see How to Create a
Communication Arrangement in the user assistance for SAP Business Technology Platform on the SAP Help
Portal.

2.2.4.4.1 Product Integration (SAP_COM_0009)

This communication arrangement is for downloading materials from SAP S/4HANA Cloud to SAP Digital
Manufacturing for execution.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, seeCreating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create the communication arrangement for product integration, follow these steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0009 (Product Integration).

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 245
  Note

For an overview of the APIs provided by the communication scenario SAP_COM_0009, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. In Outbound Communication, select the user that is associated with your Communication System.

 Note

When you choose this user, the system defaults the Authentication Method assigned to this user.

9. In the Outbound Services section, activate the Product Master - Replicate from SAP S/4HANA Cloud to
Client service.
10. In the Path for the Product Master - Replicate from SAP S/4HANA Cloud to Client service, enter /ws?
X-Identity-Zone-Subdomain=<subdomain>.

 Note

To find the <subdomain> value, go to the subaccount that you’ve used to deploy SAP Digital
Manufacturing on the SAP BTP cockpit. The <subdomain> value is displayed in the Overview under
the General tab.

11. In the Job Execution Details section, specify the frequency for job execution by entering the relevant value
in the Run Every field. If the job is scheduled, the Job Status becomes Active. You can also specify the
number of objects that can be replicated in one job execution.
12. Under Additional Properties, in the Replication Model field, enter any name for the replication model that
you want to create for the selected outbound interfaces. If you've enabled Job Execution, choose the
replication mode C.
13. Choose an Output Mode. If Job Execution is enabled, you have to choose output mode P.
14. Choose Save.

 Note

For complete material replication, you need to configure three communication arrangements:

• SAP_COM_0009 for product integration

• SAP_COM_0163 for classification systems OData/SOAP integration
• SAP_COM_0309 for product classification integration

SAP Digital Manufacturing Integration Guide

246 PUBLIC SAP Digital Manufacturing for execution Integration
Related Information

Classification Systems OData/SOAP Integration (SAP_COM_0163) [page 249]

Product Classification Integration (SAP_COM_0309) [page 252]

2.2.4.4.2 Product Lifecycle Management - Master Data

Integration (SAP_COM_0105)

This communication arrangement is for downloading BOM data from SAP S/4HANA Cloud to SAP Digital
Manufacturing for execution.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, follow these steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0105 (Product Lifecycle Management - Master Data
Integration).

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0105, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the
input help. The communication user that was created earlier is automatically added to the Inbound
Communication section.
The inbound services added to the communication scenario in the back-end system are reflected in the
communication arrangement under Inbound Services.
8. To activate the communication arrangement, choose Save.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 247
2.2.4.4.3 Material Document Integration (SAP_COM_0108)

This communication arrangement is for transferring goods movements from SAP Digital Manufacturing for
execution to SAP S/4HANA Cloud.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create the communication arrangement for material document integration, follow these steps:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0108 (Material Document Integration).

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0108, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that you created earlier from the input
help.

 Note

The communication user that you created earlier is automatically added to the Inbound
Communication section.

8. In Outbound Communication section, select the user that is associated with your Communication System.

 Note

When you choose this user, the system defaults the Authentication Method assigned to this user.

9. In the Outbound Services section, make sure that the Service Status is Active.
10. In the Path for the Material Document – Receive Confirmation, enter /ws?X-Identity-Zone-
Subdomain=<subdomain>.

SAP Digital Manufacturing Integration Guide

248 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

To find the <subdomain> value, go to the subaccount that you’ve used to deploy SAP Digital
Manufacturing on the SAP BTP cockpit. The <subdomain> value is displayed in the Overview under
the General tab.

11. To activate the communication arrangement, choose Save.

 Note

To enable the integration, you also need to go to SAP Digital Manufacturing and
map the collaboration link COLLABORATION_ERP_INV_CLEAR_RESERVATION to the directive
ERP_INVENTORY_CLEAR_RESERVATION in the app.

2.2.4.4.4 Classification Systems OData/SOAP Integration

(SAP_COM_0163)

This communication arrangement is for downloading material classifications from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0163 (Classification Systems OData/SOAP Integration)

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0163, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 249
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. The inbound services added to the communication scenario in the back-end system are reflected in the
communication arrangement under Inbound Services.
9. Under Outbound Services Characteristic Data for Classification - Replicate (Asynchronous,
Outbound) , unselect the Service Status to deactivate the outbound services.
10. To activate the communication arrangement, choose Save.

2.2.4.4.5 Material Document Outbound Notification

Integration (SAP_COM_0263)

You can use this communication arrangement to transfer goods movements from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].
• You've assigned a business partner to your communication system.

Procedure

To create the communication arrangement, complete the following steps:

1. Log on to the SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0263 (Material Document Outbound Notification
Integration).

SAP Digital Manufacturing Integration Guide

250 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

For an overview of the APIs provided by the communication scenario SAP_COM_0263, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that you created earlier from the input
help.

 Note

The communication user that you created earlier is automatically added to the Outbound
Communication section.

8. In the Outbound Services section, make sure that the Service Status is Active.
9. In the Path for the Material Document – Receive Notification service, enter /ws?X-Identity-Zone-
Subdomain=<subdomain>.

 Note

To find the <subdomain> value, go to the subaccount that you’ve used to deploy SAP Digital
Manufacturing on the SAP BTP cockpit. The <subdomain> value is displayed in the Overview under
the General tab.

10. Choose Save.

11. Open the Output Parameter Determination app.

 Note

For more information on defining output settings for specific business objects, see Output Parameter
Determination.

12. In the Select Business Rules section, select Goods Movement for Show Rules For and select Output Type for
Determination Step.
13. In the Maintain Business Rules section, choose Edit.
14. In Table Contents, choose  (Insert New Row).
15. Under Output Type, choose Direct Value Input from the dropdown menu.
16. Under Output Type, enter MMIM_MATDOC_GDSMVMT_ESOA (Goods Movement ESOA) and select the
corresponding row.
17. Choose OK.
18. Make the following settings for the MMIM_MATDOC_GDSMVMT_ESOA (Goods Movement ESOA) row by
using Direct Value Input from the respective columns dropdown menu:
• Print Active = X(Yes)
• Plant = The plant for integration
• Movement Type = 311
19. Select your row and choose Activate to apply your settings.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 251
Related Information

Material Document Integration (SAP_COM_0108) [page 248]

2.2.4.4.6 Product Classification Integration

(SAP_COM_0309)

This communication arrangement is for downloading material classifications from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0309 (Product Classification Integration) from the pick list.

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0309, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. The inbound services added to the communication scenario in the back-end system are reflected in the
communication arrangement under Inbound Services.

SAP Digital Manufacturing Integration Guide

252 PUBLIC SAP Digital Manufacturing for execution Integration
9. To activate the communication arrangement, choose Save.

2.2.4.4.7 Batch Management OData Integration

(SAP_COM_0337)

This communication arrangement is for integrating batch management in SAP S/4HANA Cloud with SAP
Digital Manufacturing for execution.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create the communication arrangement for batch management integration, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0337 (Batch Management OData Integration).

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0337, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. In Inbound Communication select a user. The system defaults the Authentication Method assigned to this
user.
9. To activate the communication arrangement, choose Save.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 253
  Note

To enable the integration, you also need to go to SAP Digital Manufacturing and ensure that the
collaboration link COLLABORATION_BATCH_CREATION is mapped to the directive BATCH_CREATION in
the Manage Collaboration Links app.

Related Information

Creating Batch Numbers

2.2.4.4.8 Production Planning Master Data Integration

(SAP_COM_0519)

This communication arrangement is for downloading a master recipe with a production version from SAP
S/4HANA Cloud to SAP Digital Manufacturing for execution.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0519 (Production Planning Master Data Integration).

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0519, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.

SAP Digital Manufacturing Integration Guide

254 PUBLIC SAP Digital Manufacturing for execution Integration
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. In the Outbound Communication section, the user associated with the Communication System is displayed
by default in the value help for the User Name field. By choosing the user, the Authentication Method is
defaulted with same authentication method associated with this user.
9. In the Outbound Services section, ensure that the Service Status checkbox is selected for all SOAP services.
The following services must be Active:
• Master Recipe – Replicate
• Production Routing – Replicate
• Production Version - Replicate
• Work Center – Replicate
10. In the Path for every SOAP service, enter the API endpoint:

Service SOAP Version 2 API Endpoint

Master Recipe /dmc/ws/masterRecipeV2?X-Identity-Zone-

Subdomain=<subdomain>

Production Routing /dmc/ws/productionRoutingV2?X-Identity-

Zone-Subdomain=<subdomain>

Production Version /dmc/ws/productionVersionV2?X-Identity-

Zone-Subdomain=<subdomain>

Work Center /dmc/ws/workCenterV2?X-Identity-Zone-

Subdomain=<subdomain>

 Note

To find the <subdomain> value, go to the subaccount that you’ve used to deploy SAP Digital
Manufacturing on the SAP BTP cockpit. The <subdomain> value is displayed in the Overview under
the General tab.

11. In the Job Execution Details section, you can specify how frequently the job is executed by entering the
relevant value in the Run Every field. Once the job is scheduled, the Job Status becomes Active. You can
also specify the size of the objects that can be replicated in one job.
12. In the Additional Properties section, in the Replication Model field, enter any name for the replication model
that you want to create. If you've enabled job execution, choose a Replication Mode.
13. Choose an Output Mode. If the job execution is enabled, you must choose output mode P.
14. In the input help of the System Filter field, select active or inactive mode, depending on your requirements.
15. To activate the communication arrangement, choose Save.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 255
Related Information

Production Planning Master Data Integration (SAP_COM_0519) [page 254]

2.2.4.4.9 Manufacturing Execution - Order and

Confirmation Integration (SAP_COM_0522)

This communication arrangement is for downloading production or process orders from SAP S/4HANA Cloud
to SAP Digital Manufacturing for execution.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0522 (Manufacturing Execution - Order and Confirmation
Integration).

 Note

For an overview of the APIs provided by the communication scenario SAP_COM_0522, go to the SAP
Business Accelerator Hub .

5. The Arrangement Name field is filled automatically.

6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

SAP Digital Manufacturing Integration Guide

256 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

The included inbound services are listed in the Inbound Services section.

SAP S/4HANA Cloud In­

Interaction SAP S/4HANA Cloud Format terface

Process Order Confirmation Inbound OData V2 API_PROC_ORDER_CONFIR

MATION_2_SRV

Production Order Confirma- Inbound OData V2 API_PROD_ORDER_CONFIR

tion MATION_2_SRV

Production Order (Version Inbound OData V2 API_PRODUCTION_ORDER_

2) 2_SRV

Process Order (Version 2) Inbound OData V2 API_PROCESS_ORDER_2_S

RV

8. In the Outbound Communication section, the user associated with the Communication System is displayed
by default in the value help for the User Name field. By choosing the user, the Authentication Method is
defaulted with same authentication method associated with this user.

SAP S/4HANA Cloud

Interaction SAP S/4HANA Cloud Format Interface

Manufacturing Order - Send Outbound SOAP CO_PPINT_MFGORD_EXE_R

EQ_OUT_V2

9. In the Outbound Services section, ensure that the Service Status checkbox is selected for Manufacturing
Order -Send, Version 2.

 Note

In SAP S/4HANA Cloud, the delivered order types are set by default to shop floor distribution when you
create a communication scenario. By activating the integration, all orders are automatically distributed
to your shop floor system unless you define filter criteria. Without a filter, you can no longer confirm
orders in the SAP S/4HANA Cloud system. You confirm orders in your shop floor system and the
confirmations are transferred to the SAP S/4HANA Cloud system.

10. In the Path for Manufacturing Order - Send, Version 2, enter /dmc/ws/manufacturingOrderV2?X-
Identity-Zone-Subdomain=<subdomain>.

 Note

To find the <subdomain> value, go to the subaccount that you’ve used to deploy SAP Digital
Manufacturing on the SAP BTP cockpit. The <subdomain> value is displayed in the Overview under
the General tab.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 257
11. In the Additional Properties section, enter the following data:

First Column (Property Name) Second Column (Property Value) Note

Material <your materials> Select the materials for which orders

are distributed to your shop floor sys­
tem.

Order Type <your order types> Select the order type of the orders
that are distributed to your shop floor
system.

Plant <your plant> Select your plant.

 Note

The system evaluates the filter criteria using the following logic:
• If you apply several filter criteria to the same attribute (for example, material), the system applies
the filter if any filter criterion is true.
• If you apply several filter criteria to different attributes (for example, material and order type), the
system applies the filter if all filter criteria are true.
• The system ignores empty fields.

12. To activate the communication arrangement, choose Save.

 Note

To enable the integration, you also need to go to SAP Digital Manufacturing

and ensure that the collaboration link COLLABORATION_QUANTITY_CONFIRMATION
is mapped to the directive QUANTITY_CONFIRMATION and the collaboration
link COLLABORATION_GOODS_RECEIPT_CONFIRMATION is mapped to the directive
GOODS_RECEIPT_CONFIRMATION in the Manage Collaboration Links app.

2.2.4.4.10 Inspection Master Data Integration

(SAP_COM_0110)
This communication arrangement is for retrieving inspection information from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].

SAP Digital Manufacturing Integration Guide

258 PUBLIC SAP Digital Manufacturing for execution Integration
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a new communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0110 (Inspection Master Data Integration) from the pick list.
5. The Arrangement Name field is filled automatically with the name of the selected integration scenario.
Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.
8. In Inbound Communication, select a user. The system defaults the Authentication Method assigned to this
user.
9. The inbound services added to the communication scenario in the backend system will be reflected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose .

2.2.4.4.11 Quality Inspection Process Integration

(SAP_COM_0318)

This communication arrangement is for uploading inspection recording results from SAP Digital Manufacturing
for execution to SAP S/4HANA Cloud.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 259
1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.
2. Open the Communication Arrangements app.
3. To create a new communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0318 (Quality Inspection Process Integration) from the pick
list.
5. The Arrangement Name field is filled automatically with the name of the selected integration scenario.
Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. In Inbound Communication, select a user. The system defaults the Authentication Method assigned to this
user.
9. The inbound services added to the communication scenario in the backend system will be reflected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose Save.

2.2.4.4.12 Defect Processing Integration (SAP_COM_0153)

This communication arrangement is for transferring Quality Management (QM) defect code groups and codes
from SAP S/4HANA Cloud to SAP Digital Manufacturing.

Prerequisites

• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create the communication arrangement for defect processing integration, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a new communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0153 (Defect Processing Integration).

SAP Digital Manufacturing Integration Guide

260 PUBLIC SAP Digital Manufacturing for execution Integration
5. The Arrangement Name field will be filled automatically with the name of the selected integration scenario.
Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

 Note

The communication user that was created earlier is automatically added to the Inbound
Communication section.

8. In Inbound Communication, select a user. The system defaults the Authentication Method assigned to this
user.
9. To activate the communication arrangement, choose Save.

2.2.4.4.13 Material Stock Integration (SAP_COM_0164)

This communication arrangement is for retrieving inventory stock information from SAP S/4HANA Cloud to
SAP Digital Manufacturing.

Prerequisites

• You've created a service instance and a service key in your SAP Digital Manufacturing subaccount in SAP
BTP cockpit. For more information, see Creating a Service Instance and a Service Key [page 243].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 241].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 242].

Procedure

To create this communication arrangement, complete the following steps:

1. Log on to SAP Fiori launchpad in the SAP S/4HANA Cloud system.

2. Open the Communication Arrangements app.
3. To create a new communication arrangement, choose New.
4. Select the communication scenario SAP_COM_0164 (Material Stock Integration) from the pick list.
5. The Arrangement Name field is filled automatically with the name of the selected integration scenario.
Adapt the Arrangement Name if required.
6. Choose Create.
7. In the Common Data section, select the Communication System that was created earlier from the input
help.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 261
8. In Inbound Communication, select a user. The system defaults the Authentication Method assigned to this
user.
9. The inbound services added to the communication scenario in the backend system will be reflected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose Save.

2.2.4.5 Creating Destinations

You need to create destinations in SAP Business Technology Platform to integrate SAP Digital Manufacturing
for execution with SAP S/4HANA Cloud.

The following destination is used for inbound integration:

• S4H_INTEGRATION_OAUTH, which is part of the onboarding process. For more information, see Create
Destination S4H_INTEGRATION_OAUTH.

The following destination is used for outbound integration:

• S4H_ODATA_INTEGRATION. For more information, see Destination S4H_ODATA_INTEGRATION [page

262].

2.2.4.5.1 Destination S4H_ODATA_INTEGRATION

Configure the S4H_ODATA_INTEGRATION destination for outbound integration from SAP Digital Manufacturing
for execution to SAP S/4HANA Cloud.

• You've got the Administrator role for SAP BTP cockpit.

• You've got access to your SAP Digital Manufacturing subaccount in SAP BTP cockpit.
• You've got the Administrator role for SAP S/4HANA Cloud.
• You've got the user name and password of the communication user representing SAP S/4HANA Cloud. For
more information, see Creating a Communication User [page 241].

Context

The destination data is used by SAP Digital Manufacturing to integrate with SAP S/4HANA Cloud.

Procedure

1. In your SAP Digital Manufacturing subaccount in SAP BTP cockpit, go to Destinations.

2. Choose New Destination to create the S4H_ODATA_INTEGRATION destination.
3. Enter the name, S4H_ODATA_INTEGRATION, and description of the destination.

SAP Digital Manufacturing Integration Guide

262 PUBLIC SAP Digital Manufacturing for execution Integration
4. Select HTTP as Type of Destination.
5. Under URL, enter the API-URL of your SAP S/4HANA Cloud system and add /sap/opu/odata/sap to it.

 Note

You can find the API-URL in one of the following inbound communcation scenarios that you've created
in a previous step:
• SAP_COM_0163
• SAP_COM_0309
• SAP_COM_0009

 Example

Depending on your system, the url should look like this: https://{system_name}-
api.s4hana.ondemand.com/sap/opu/odata/sap

6. Select Internet as Proxy Type.

7. Select BasicAuthentication as Authentication. The destination data will be used by SAP Digital
Manufacturing for execution to provide authentication and authorization for SAP S/4HANA Cloud OData
integration.
8. Enter the user and password using the credentials of the communication user in SAP S/4HANA Cloud.
9. Under Additional Properties check that Use default JDK Truststore is selected.
SAP Digital Manufacturing for executionacturing Cloud for execution uses the destination data to provide
authentication and authorization for SAP S/4HANA Cloud integration.
10. Choose Save.
11. Choose Check Connection to check whether the connection has been established. You can ignore the 403
response.

2.2.4.6 Managing Supported Plants

You can connect the SAP S/4HANA Cloud system to plants for integration with SAP Digital Manufacturing for
execution. The global SAP Digital Manufacturing for execution system is used across all plants.

Prerequisites

• If you integrate SAP Digital Manufacturing for execution with multiple SAP S/4HANA Cloud systems, these
systems need to have different system IDs. Systems are identified at the client level.
• Each plant needs to have a unique plant name across the tenant.
• You have to create and set up plants for integration in the Manage Plants and Manage Business Settings
apps.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 263
Related Information

Manage Plants
Manage Business Settings

2.2.4.7 Defining Operations in SAP S/4HANA Cloud for

SAP Digital Manufacturing for execution

In SAP S/4HANA Cloud, you can define operations to use data in SAP Digital Manufacturing for execution.

In SAP S/4HANA Cloud, you define on operation level if an operation in a master recipe or routing is relevant
for the transfer to SAP Digital Manufacturing for execution. The tables below show the mapping rules for recipe
steps and dependent objects to use in SAP Digital Manufacturing for execution, such as operation activities,
BOM components, and the standard value key in SAP S/4HANA Cloud. These rules are valid for both the
process order and master recipe.

 Note

Operation transfer is controlled by exclusion flags. If you set the relevant exclusion flag, the operation will
not be downloaded to SAP Digital Manufacturing for execution. If the flag is not set, the operation will be
downloaded together with all dependent objects.

Mapping Rules for an Operation in SAP S/4HANA Cloud

If an operation is flagged operationIsNotMESRelevant = true, the system doesn't transfer this operation or any phase
belonging to this operation to SAP Digital Manufacturing.

If an operation is flagged operationIsNotMESRelevant = false, the system transfers this operation and all phases
belonging to this operation that are flagged operationIsNotMESRelevant = false to SAP Digital Manufacturing.

If an operation is flagged operationIsNotMESRelevant = false, but none of its phases are flagged
operationIsNotMESRelevant = false, the system does not transfer this operation or any phase belonging to it, to
SAP Digital Manufacturing.

Note that BOM components that are attached to a notMESRelevant step are not mapped.

Mapping for an Operation Flag in SAP S/4HANA Cloud

Path of operationIsNotMESRelevant flag in ProcessOrder: /n0:ManufacturingOrderExecuteRequest/

ManufacturingOrder/ManufacturingOrderActivityNetworkElement/n1:OperationControlProfile/
n1:OperationIsNotMESRelevant

Path of operationIsNotMESRelevant flag

in MasterRecipe: /n0:ManufacturingMasterRecipeInfomation/BillOfOperations/
BillOfOperationsActivityNetworkElement/BillOfOperationsActivityNetworkElementTimeSlice/
OperationControlProfile/n1:OperationIsNotMESRelevant

SAP Digital Manufacturing Integration Guide

264 PUBLIC SAP Digital Manufacturing for execution Integration
2.2.5 Business Integration with SAP S/4HANA Cloud

The following scenarios are supported in the integration with SAP S/4HANA Cloud.

• Integration of Master Data

You can transfer master data such as materials, BOMs, routings and work centers from SAP S/4HANA
Cloud to SAP Digital Manufacturing.
• Integration of Transaction Data
You can enable bidirectional transfer of transaction data such as orders, inventory, batch and quality
inspection information.

Related Information

Integration of Master Data [page 265]

Integration of Transaction Data [page 271]

2.2.5.1 Integration of Master Data

You can transfer master data from an SAP S/4HANA Cloud system to an SAP Digital Manufacturing for
execution system.

Master Data Integration

Master data represents the business data your company requires about business partners, individuals,
organizations, or products. Master data tends to remain unchanged over longer periods of time and supports
transactional processes. You can use Master Data Maintenance to maintain master data. For more information
about Master Data Maintenance in SAP S/4HANA Cloud, see Master Data Maintenance on the SAP Help Portal
at http://help.sap.com.

You can integrate the following master data withSAP S/4HANA Cloud :

Master Data Integration from SAP S/4HANA Cloud to SAP Digital Manufacturing
SAP S/4HANA Cloud SAP Digital Manufacturing Cloudfor execution

Material Material

If Classification (Class and Characteristics) data is main­

tained for a material in SAP S/4HANA Cloud, that data is
also downloaded.

Only Class Type 023 (Batch) is downloaded.

Work Center (PP-PI Resource) Work Center

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 265
SAP S/4HANA Cloud SAP Digital Manufacturing Cloudfor execution

Master Recipe Master Recipe

Prerequisites

• You have defined and set up plants for integration using the Manage Plants and Manage Business Settings
apps.

Sequence Considerations

• 1. Transfer the work centers.

2. Transfer the materials.
3. Transfer the component materials.
4. Transfer the master recipe.
5. Transfer the process order.
• Materials must be transferred before master recipe and process order.
• Finished items must be transferred before routings.

Implementation Considerations

Some functions may behave differently depending on the SAP S/4HANA Cloud version used for integration
with SAP Digital Manufacturing for execution.

Related Information

Integration of Transaction Data [page 271]

SAP Digital Manufacturing Integration Guide

266 PUBLIC SAP Digital Manufacturing for execution Integration
2.2.5.1.1 Transfer of Work Centers from SAP S/4HANA
Cloud

You can transfer work centers created or updated in SAP S/4HANA Cloud to SAP Digital Manufacturing for
execution.

Prerequisites

• You have maintained the SAP_COM_0519 communication arrangement in the SAP S/4HANA Cloud SOAP
interface for the work center: CO_PPINT_WORK_CENTER_SPRX.
• Ensure that the user that transfers work centers has read authorization to the work center and resource
objects in SAP S/4HANA Cloud.

Procedural Steps

1. Log on to the SAP S/4HANA Cloud system.

2. Open the Replicate by Object Selection app.
3. Select Workcenter from the Business Object Type dropdown.
4. Enter your work center in the Work Ctr field.
5. Enter your plant in the Plant field.
6. Select a target system in the Target System Selection table.
7. Choose Replicate.
8. Check logs for the replication status.

You can view the transferred work centers in the Manage Work Centers app. Work center capacity updates in
SAP S/4HANA Cloud will result in the corresponding changes in SAP Digital Manufacturing for execution and in
addition, you can see the capacity category in the Manage Work Centers app. Note that ERP Work Center is set
to Yes for the work centers transferred from SAP S/4HANA Cloud.

Related Information

Manage Work Centers

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 267
2.2.5.1.2 Transfer of QM Defect Code Groups and Codes
from SAP S/4HANA Cloud

You can transfer Quality Management (QM) defect code groups and codes from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution using the Manage Nonconformance Groups app.

Prerequisites

• You have set up integration with SAP S/4HANA Cloud (see Technical Integration with SAP S/4HANA Cloud
[page 238])
• You have set up the communication arrangement for the Defect Processing Integration (SAP_COM_0153)
communication scenario in SAP S/4HANA Cloud .

Procedural Steps

1. In the Manage Nonconformance Groups app, choose Sync QM Groups.

2. Search for the production-relevant QM defect code groups that exist in the connected SAP S/4HANA
Cloud system. The selection is restricted to catalog type 9 (Defect types) in SAP S/4HANA Cloud. Only
released code groups are displayed and can be transferred.
You can check which QM code groups have been previously transferred by selecting Yes in the Previously
Synched dropdown. If you need to transfer new QM code groups, select Yes in the Previously Synched
dropdown.
3. Select one or more QM code groups and choose Sync.

The selected QM code groups are transferred to SAP Digital Manufacturing for execution. QM defect groups
and codes transferred from SAP S/4HANA Cloud are marked with ERP Group and ERP Code indicators
set to Yes in the Manage Nonconformance Groups and Manage Nonconformance Codes apps. Note that a
nonconformance code originated from SAP S/4HANA Cloud is represented by the concatenated name (QM
defect code and code group).

When you log a nonconformance code originated from SAP S/4HANA Cloud, it is automatically transferred to
SAP S/4HANA Cloud and a generic defect record is created.

Related Information

Defect Processing Integration (SAP_COM_0153) [page 260]

Destination S4H_ODATA_INTEGRATION [page 262]
Manage Nonconformance Groups
Manage Nonconformance Codes

SAP Digital Manufacturing Integration Guide

268 PUBLIC SAP Digital Manufacturing for execution Integration
2.2.5.1.3 Current Version Dependencies
You can change the current version of different master data objects, such as BOMs, routings, and materials.

Note that when you change the current version of a BOM, routing, or a material, the dependencies between
these objects will also change.

2.2.5.1.4 Updating a Master Recipe

You can update master recipes in SAP S/4HANA Cloud.

When master recipe data is updated in SAP S/4HANA Cloud, the data is updated according to the following
rules:

1. All the master recipe fields that have been mapped are updated.
2. All the enrichments done in SAP Digital Manufacturing for execution (for example, work instructions and
data collection attachments) are kept.
3. When a resource is changed on a phase in SAP S/4HANA Cloud, then this resource is updated to a phase
in
SAP Digital Manufacturing for execution, but work instructions and data collection attachments are
deleted from the phase.
4. When a phase is deleted in SAP S/4HANA Cloud, then the phase, along with its work instructions and data
collections, is deleted in
SAP Digital Manufacturing for execution
.

2.2.5.1.5 Updating and Upversioning a Material

You can update and upversion master materials in SAP S/4HANA Cloud, as well as SAP ERP and SAP S/
4HANA.

Changes to the following fields trigger material upversioning:

• Base UOM
• Material UOM
• Material Type
• Production Version

Changes in all other fields will result in a material update only.

2.2.5.1.6 Updating and Upversioning a BOM

You can update and upversion master BOMs in SAP S/4HANA Cloud, as well as SAP ERP and SAP S/4HANA.

A master BOM is downloaded from SAP S/4HANA Cloud to SAP Digital Manufacturing for execution using
an OData call while downloading a master recipe or master routing. A master BOM is downloaded only when

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 269
at least one component is assigned to the routing or recipe step. The master BOM is downloaded from SAP S/
4HANA Cloud using OData protocol using the connection details maintained in the S4H_ODATA_INTEGRATION
destination.

Changes to the following fields trigger BOM upversioning:

• Description
• Add Component
• Remove Component
• Change Quantities
• Header Base Quantity
• Component Type
• Component UOM
• Component Scrap %

Changes in all other fields will result in a BOM update only.

2.2.5.1.7 Updating and Upversioning a Routing

You can update and upversion master routings in SAP S/4HANA Cloud and SAP S/4HANA.

Changes to the following routing header fields trigger routing upversioning:

• Description
• Adding Operation Activities
• Removing Operation Activities
• Status

Changes to the following routing operation activity fields trigger routing upversioning:

• Description
• Work Center
• Control Key
• Long Text
• Standard Value Keys and Values
• Normal Operation Activity

Changes in all other fields will result in a routing update only.

SAP Digital Manufacturing Integration Guide

270 PUBLIC SAP Digital Manufacturing for execution Integration
2.2.5.2 Integration of Transaction Data

You can transfer transaction data between an SAP S/4HANA Cloud system and an SAP Digital Manufacturing
for execution system.

Transaction Data Integration

Transaction data is data that’s created during an event or operation. It is assigned to certain master data, for
example the produced quantity of a particular product included in an individual order, and it changes with each
transaction.

You can integrate the following transaction data withSAP S/4HANA Cloud :

Transaction Data for outbound integration from SAP Digital Manufacturing for execution to SAP S/4HANA Cloud
SAP Digital Manufacturing for execution SAP S/4HANA Cloud

Quantity Confirmation Quantity Confirmation

Material Consumption (Goods Issue) Material Consumption (Goods Issue)

Goods Receipt Goods Receipt

Activity Confirmation Activity Confirmation

Transaction Data for inbound integration from SAP S/4HANA Cloud to SAP Digital Manufacturing
SAP S/4HANA Cloud SAP Digital Manufacturing for Execution

Process Order / Production Order Order

Prerequisites

• Master data integration has been set up (see Integration of Master Data [page 265]).

Sequence Considerations

1. Transfer the master data.

2. Transfer the process order data.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 271
Implementation Considerations

Some functions may behave differently depending on the SAP S/4HANA Cloud version used for integration
with SAP Digital Manufacturing for execution.

Related Information

Integration of Master Data [page 265]

2.2.5.2.1 Transferring Production Order with PRT

Assignment

You can transfer production order data with PRT assignment from SAP S/4HANA Cloud to SAP Digital
Manufacturing for execution to create or update the corresponding production order record.

 Note

You can only transfer production order with material PRT assignment.

Prerequisites

SAP S/4HANA Cloud

• You have created communication arrangement to transfer production order from SAP S/4HANA Cloud
to SAP Digital Manufacturing for execution. For details, see Manufacturing Execution - Order and
Confirmation Integration (SAP_COM_0522) [page 256].
• The material PRT has been transferred from SAP S/4HANA Cloud to SAP Digital Manufacturing for
execution together with the material master data.
• The material PRT has already been assigned to routing operations.

SAP Digital Manufacturing

• The collaboration link COLLABORATION_PRT_ASSIGNMENT_GET is mapped to the directive

ERP_PRT_ASSIGNMENT_GET in the Manage Collaboration Links app.

Procedure

1. Create or update a production order manually in SAP S/4HANA Cloud.

2. Choose the Release Order button to transfer the order to SAP Digital Manufacturing for execution.

SAP Digital Manufacturing Integration Guide

272 PUBLIC SAP Digital Manufacturing for execution Integration
3. Choose Save.
4. Verify the results in the Manage Orders app or the Integration Message Dashboard in SAP Digital
Manufacturing for execution. For more information, see Manage Orders or Integration Message Dashboard.

 Note

Before releasing an order to the shop floor in the Manage Orders app in SAP Digital Manufacturing, you can
update it from your integrated ERP system. The updating options you have vary depending on the order
type and the integrated ERP system. For more information, see Updating Orders Before the Release [page
185].

2.2.5.2.2 Transfer of Floor Stock Data

You can transfer floor stock data for certain goods movement types from an SAP S/4HANA Cloud system to
SAP Digital Manufacturing for execution.

Use

You can select the inventory management mode you want to enable for your plant in the Manage Business
Settings app. Depending on the mode you enabled, the supported goods movement types varies.

 Note

Unlike with the integration to SAP ERP or SAP S/4HANA, no IDocs or SAP Cloud Integration are used for
the integration to SAP S/4HANA Cloud. The SAP Digital Manufacturing for execution system is directly
integrated with SAP S/4HANA Cloud.

 Note

In SAP S/4HANA Cloud, the filter Print Active need be set as =X(Yes) for output type
MMIM_MATDOC_GDSMVMT_ESOA in Output Parameter Determination. The Print via Output Control need
be checked for posting the goods movement to SAP Digital Manufacturing for execution system.

Consolidated Inventory Management Mode

If you have enabled Consolidated inventory management mode, all standard goods movement types in SAP
S/4HANA Cloud are supported in SAP Digital Manufacturing for execution.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 273
Individual Inventory Management Mode

If you have enabled Individual inventory management mode, the following goods movement types are
supported.

Inbound integration

Inbound integration messages include floor stock receipt (goods movement type 311).

Outbound integration

Outbound integration messages include:

• Floor Stock Consumption (goods movement type 261)

• Floor Stock Return (goods movement type 312)

The following scenarios are supported:

Floor Stock Receipt (replenishment, goods movement type 311)

In your SAP S/4HANA Cloud system, you can use the Post Goods Movement app to trigger goods movement
from the central storage location to the production storage location.

The process for floor stock receipt without reservation (goods movement type 311) in SAP Digital
Manufacturing for execution assumes that the received goods are moved from a central warehouse location to
a production location, so that they can be used during the production process.

SAP Digital Manufacturing Integration Guide

274 PUBLIC SAP Digital Manufacturing for execution Integration
• When you post a transfer of unrestricted-use stock from a central (issuing) storage location to a floor stock
(production) storage location in SAP S/4HANA Cloud using the goods movement type 311, the stock data
is transferred from SAP S/4HANA Cloud to SAP Digital Manufacturing for execution via the soap call of
communication scenario SAP_COM_0263.
• SAP S/4HANA Cloudtriggers the outbound message MMIM_MATDOC_GDSMVMT_ESOA to integrate the
floor stock to the production storage location in SAP Digital Manufacturing for execution with Batch
Number and Inventory ID created to the new inventory.
The inventory is ready for consumption without reservation in SAP Digital Manufacturing for execution.
• A floor stock receipt is created for the specified components.

When COLLABORATION_GOODS_ISSUE_CONFIRMATION is triggered, SAP Digital Manufacturing for execution

sends a confirmation to SAP S/4HANA Cloud to report consumed components.

Integration

• SAP S/4HANA Cloud is the system of record for inventory management; SAP Digital Manufacturing for
execution is the system of record for floor stock management.
• A transfer posting in SAP ERP or SAP S/4HANA is used in the same way as a floor stock receipt in SAP
Digital Manufacturing for execution.
• For inventory ID records created in SAP Digital Manufacturing for execution through the integration, the
field ERP Inventory is checked.

Prerequisites

SAP S/4HANA Cloud

• You have created production storage locations for floor stock materials.
• You have set up communication arrangement for SAP_COM_0108 and SAP_COM_0263.
• You have set up a filter for Print Active and the goods movement type 311 in Output Parameter
Determination.
• You have created a BOM for the finished good material of the order.

SAP Digital Manufacturing

• You have created a storage location matching SAP S/4HANA Cloud Storage Location.
• For the production order-specific consumption scenario, you have created or imported shop order data so
that components can be pegged.
• You have defined a numbering pattern for the number type floor stock receipt.
• For outbound integration, make sure the following collaboration links are mapped to respective directives
in the Manage Collaboration Links app.
• The link COLLABORATION_GOODS_ISSUE_CONFIRMATION is mapped to the directive
GOODS_ISSUE_CONFIRMATION.
• The link COLLABORATION_GOODS_RECEIPT_CONFIRMATION is mapped to the directive
GOODS_RECEIPT_CONFIRMATION.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 275
 • The link COLLABORATION_QUANTITY_CONFIRMATION is mapped to the directive
QUANTITY_CONFIRMATION.
• The link COLLABORATION_BATCH_CHARACTERISTICS is mapped to the directive
BATCH_CHARACTERISTICS.

2.2.5.2.2.1 Updating Integration Configuration to Use Floor

Stock Data

If you want to use the floor stock integration functionality in SAP Digital Manufacturing, you need to update
some settings in your integration configuration, as described in this topic.

Prerequisites

You have made the following configurations to connect SAP Digital Manufacturing for execution to SAP S/
4HANA Cloud:

• Creating a Service Instance and a Service Key [page 243]

• Creating a Communication User [page 241]
• Creating a Communication System [page 242]
• Creating Communication Arrangements [page 245]
• Creating Destinations [page 262]
• Managing Supported Plants [page 263]
• Defining Operations in SAP S/4HANA Cloud for SAP Digital Manufacturing for execution [page 264]

Procedure

1. Go to the SaaS tenant of your system and generate a new service instance and key for Digital
Manufacturing Cloud Services. Note down the clientid and clientsecret under the uaa tag.
2. Update the destination configuration for S4H_INTEGRATION_OAUTH.

• Go to SAP BTP cockpit, and in the side menu bar, choose Connectivity Destinations .
• Update the credentials for S4H_INTEGRATION_OAUTH with the clientid and clientsecret noted
in above step.
3. Assign the collaboration directive ERP_INV_CLEAR_RESERVATION to the collaboration link
COLLABORATION_ERP_INV_CLEAR_RESERVATION for the inventory return activity.

Results

You can now use the floor stock functionality as described in this chapter.

SAP Digital Manufacturing Integration Guide

276 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

If you have already enabled the transfer of floor stock data and you want to integrate inbound inventory
with batch characteristic values, you need to create a new service broker (while keeping the old service
broker you've created before) and complete the above procedures again.

2.2.5.2.2.2 Transfer of Floor Stock Return Data

You can transfer floor stock return data from SAP Digital Manufacturing for execution to SAP S/4HANA Cloud.

Use

This function lets you transfer floor stock return data from SAP Digital Manufacturing for execution to SAP
S/4HANA Cloud.

1. In SAP Digital Manufacturing for execution, you can trigger the floor stock return to a central storage
location.
2. The SAP Digital Manufacturing collaboration COLLABORATION_ERP_INV_CLEAR_RESERVATION
(ERP_INV_CLEAR_RESERVATION) is triggered in SAP Digital Manufacturing for execution. This initiates
the data synchronization to the SAP S/4HANA Cloud system.
3. In the SAP S/4HANA Cloud system, the floor stock is increased in the central storage location according
to the return request. The inventory in the production storage location is decreased according to the return
request.

The following scenario is supported:

Process Order-Independent Floor Stock (311) Return (312)

The diagram shows the flow of a floor stock return that's synchronized from SAP Digital Manufacturing for
execution to SAP S/4HANA Cloud for process order-independent floor stock.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 277
The components are returned to the central storage location.SAP S/4HANA Cloud posts a goods movement of
the type 312, the reversal of a one-step transfer posting.

Integration

SAP S/4HANA Cloud is the system of record for inventory management; SAP Digital Manufacturing for
execution is the system of record for floor stock management.

Prerequisites

SAP Digital Manufacturing

You have received floor stock data from SAP S/4HANA Cloud.

Activities

When you decrease the value of the Qty on Hand field for an inventory ID, enter a reason code and choose Save
in the Manage Floor Stock app in SAP Digital Manufacturing for execution. A message is sent to SAP S/4HANA
Cloud to post the corresponding goods movements.

SAP Digital Manufacturing Integration Guide

278 PUBLIC SAP Digital Manufacturing for execution Integration
Related Information

Manage Floor Stocks

2.2.5.2.3 Batch Characteristics Update

You can update batch characteristic values and sychronize the data from SAP Digital Manufacturing to SAP
S/4HANA Cloud.

 Note

At the moment, this function is supported only for process orders.

Prerequisites

SAP S/4HANA Cloud

• Batch-managed materials are created in SAP S/4HANA Cloud and are transferred to SAP Digital
Manufacturing.
• Batch characteristics are assigned to the batch-managed material in SAP S/4HANA Cloud.

Procedure

• Update batch characteristic values for the process order you want to work on.
• The system updates the batch characteristics data for respective material in SAP S/4HANA Cloud.

Related Information

Updating Batch Characteristics

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 279
2.2.5.2.4 Batch Creation

You can transfer batch number created in SAP Digital Manufacturing to SAP S/4HANA Cloud.

Prerequisites

SAP S/4HANA Cloud

• Batch-managed materials are created in SAP S/4HANA Cloud and are transferred to SAP Digital
Manufacturing.

SAP Digital Manufacturing

• The collaboration link COLLABORATION_BATCH_CREATION is mapped to the directive BATCH_CREATION

in the Manage Collaboration Links app.

Procedure

• Create a batch number for the process order you want to work on.
• The system triggers a collaboration event and sends the COLLABORATION_BATCH_CREATION message to
update the batch data for respective material in SAP ERP.

Related Information

Creating Batch Numbers

2.2.5.2.5 Inspection Characteristics Integration

(Production Order)

You can transfer an inspection lot (type 03) from SAP S/4HANA Cloud to SAP Digital Manufacturing for
execution.

Prerequisites

SAP S/4HANA Cloud

SAP Digital Manufacturing Integration Guide

280 PUBLIC SAP Digital Manufacturing for execution Integration
• You have maintained the SAP_COM_0522 communication arrangement in the SAP S/4HANA Cloud SOAP
interface for the production order: CO_PPINT_MFGORD_EXE_REQ_OUT_V2. For more information, see
Manufacturing Execution - Order and Confirmation Integration (SAP_COM_0522) [page 256].
• The inspection lot (type 03) has been created and assigned inspection characteristics.
• The inspection lot has been assigned to the production order.

Procedure

Release the production order in SAP S/4HANA Cloud, and the inspection characteristics are downloaded to
SAP Digital Manufacturing for execution.

Related Information

Inspection Results Recording (Production Order) [page 281]

2.2.5.2.6 Inspection Results Recording (Production Order)

You can record inspection results and sychronize the data from SAP Digital Manufacturing for execution to SAP
S/4HANA Cloud.

Prerequisites

SAP S/4HANA Cloud

• The inspection lot (type 03) has been created and assigned inspection characteristics.
• The inspection lot has been assigned to the production order.
• The base sample quantity must be set to 1.
• You have maintained the SAP_COM_0318 communication arrangement in the SAP S/4HANA Cloud. For
more information, see Quality Inspection Process Integration (SAP_COM_0318) [page 259].

SAP Digital Manufacturing

• The collaboration link COLLABORATION_INSPECTION_LOT is mapped to the directive INSPECTION_LOT in

the Manage Collaboration Links app.

Procedure

1. In the Work Center POD, record inspection results for the order you want to work on.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 281
2. Complete an operation activity of the order. The system triggers a collaboration event and sends the
COLLABORATION_INSPECTION_LOT message to update the inspection characteristics data for respective
order in SAP S/4HANA Cloud.

Related Information

Inspection Characteristics Integration (Production Order) [page 280]

2.2.5.2.7 Updating Orders Before the Release

Learn about the options you've got for updating a production or process order from your integrated ERP
system before the order is released to the shop floor in SAP Digital Manufacturing.

Use

Before releasing an order to the shop floor in the Manage Orders app, you can update it from your integrated
ERP system. The updating options you have vary depending on the order type and the integrated ERP system.

Overview

Here you'll find an overview of the supported update scenarios. "X" means that the corresponding update is
supported.

SAP ERP SAP S/4HANA

Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

Finished Goods X X X X X X
Batch Number
(Order Header)

Goods Receipt X X X X X X
Storage Loca­
tion (Order
Header)

Customer X X N/A N/A N/A N/A

Name (Order
Header)

SAP Digital Manufacturing Integration Guide

282 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP ERP SAP S/4HANA
Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

Sales Order X X X N/A N/A N/A

(Order Header)

Custom Field X X N/A X X N/A

(Order Header)

Work Instruc­ X X N/A N/A N/A N/A

tion

Dates Changes X X X X X X
(Order Header)

Operation X X X X X X
Schedule

Quantity De­ X X X X X X
crease

Quantity In­ X X X X X X
crease

Technical Com­ X X X X X X
pletion (TECO)

Order Header X X X X X X
Long Text

Order Header X X X X X X
Schedule
Dates/Plan
Dates

BOM Compo­ X X X X X X
nent Storage
Location  Note  Note  Note  Note  Note  Note
The BOM The BOM The BOM The BOM The BOM The BOM
component component component component component component
storage lo­ storage lo­ storage lo­ storage lo­ storage lo­ storage lo­
cation cation cation cation cation cation
change is change is change is change is change is change is
supported supported supported supported supported supported
by EWM by EWM by EWM by EWM by EWM by EWM
2021 or 2021 or 2021 or 2021 or 2021 or 2021 or
higher. higher. higher. higher. higher. higher.

BOM Compo­ X X X X X X
nent Batch
Number

Underdelivery X X X N/A N/A N/A

Tolerance

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 283
 SAP ERP SAP S/4HANA
Production Or­ SAP S/4HANA Cloud SAP S/4HANA
der SAP ERP SAP S/4HANA Cloud
Production Or­ Production Or­
Order Update der der Process Order Process Order Process Order

Overdelivery X X X N/A N/A N/A

Tolerance

Addition / Re­ X X X X X X
moval of Com­
ponent

Component X X X X X X
Assignment
Change to Op­
eration Activ­
ity / Phase

Addition / Re­ X X X X X X
moval of Oper­
ation / Phase

Work Center X X X X X X
Change in Op­
eration /  Note  Note  Note  Note  Note  Note
Phase
For integra­ For integra­ For integra­ For integra­ For integra­ For integra­
tion with tion with tion with tion with tion with tion with
EWM, the EWM, the EWM, the EWM, the EWM, the EWM, the
new target new target new target new target new target new target
work cen­ work cen­ work cen­ work cen­ work cen­ work cen­
ter must be ter must be ter must be ter must be ter must be ter must be
mapped to mapped to mapped to mapped to mapped to mapped to
a produc­ a produc­ a produc­ a produc­ a produc­ a produc­
tion supply tion supply tion supply tion supply tion supply tion supply
area (PSA). area (PSA). area (PSA). area (PSA). area (PSA). area (PSA).

Change of X X X X X X
Component
Quantities

Order-Specific X X X X X X
Bill of Mate­
rial*

Order-Specific X X X X X X
Routing*

Inspection Lot X X X X
Change

*Objects are up-versioned if one of the following changes takes place:

• Changes to work centers on operations / phases

• Addition or removal of component
• Addition or removal of operations / phases

SAP Digital Manufacturing Integration Guide

284 PUBLIC SAP Digital Manufacturing for execution Integration
• Change of component quantities
• Changes to component assignment

2.2.5.3 Field Mapping for the Integration to SAP S/4HANA

Cloud

The fields created in SAP S/4HANA Cloud correspond to certain fields of SAP Digital Manufacturing for
execution.

 Note

For the connection to an SAP S/4HANA Cloud system, certain communication arrangements need to be
active. For more information, see Integration with SAP S/4HANA or SAP ERP [page 9].

Material and Data Collection Group Mapping (based on SAP_COM_0309 and SAP_COM_0163 Scenarios for DC Groups, and
SAP_COM_0009 Scenario for Materials)
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

productInternalID material N/A

baseMeasureUnitCode unitOfMeasure N/A

Every description with a supported descriptions Only supported language codes will be
languageCode displayed.

N/A version A

N/A currentVersion TRUE

N/A lotSize one

N/A status releasable

N/A quantityRestriction ANY_NUMBER

productTypecode/value materialType N/A

supplyPlanning/ procurementType If E→ Manufactured.

procurementTypeCode
If F→ Purchased.

In other cases →
Manufactured_purchased.

supplyPlanning/ mrpController N/A

productRequirementsPlanningRes
ponsibleCode

plant/plantId plant N/A

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 285
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A incrementBatchNumber If product/

batchManagementRequiredIndicat
or = true or product/plant/
batchManagementRequiredIndicat
or = true → ORDER.

In other cases → NONE.

plant/workScheduling/ productionStorageLocation or If procurementType = Manufactured

productionInventoryManagedLoca putawayStorageLocation → putawayStorageLocation
tionInternalID
In other cases →
productionStorageLocation

N/A DataCollectionGroup If Material procurementType

= Manufactured or
Manufactured_purchased

N/A DataCollectionGroup/status releasable

N/A
N/A DataCollectionGroup/plant

N/A DataCollectionGroup/version A

N/A DataCollectionGroup/ true

currentVersion

N/A
API_CLFN_PRODUCT_SRV/ DataCollectionGroup/dcGroup
A_ClfnClassForKeyDate/Class

API_CLFN_PRODUCT_SRV/ DataCollectionGroup/ dcGroup

A_ClfnClassForKeyDate/ description
ClassTypeName

Not developed yet. DataCollectionGroup.attachedPo material

ints[0].material

API_CLFN_CHARACTERISTIC_SRV/ DataCollectionGroup.dcParamete N/A

A_ClfnCharacteristicForKeyDate rs[].parameterName
/Characteristic

API_CLFN_CHARACTERISTIC_SRV/ DataCollectionGroup.dcParamete parameterName

A_ClfnCharacteristicForKeyDate rs[].description
If En localization not null.
/CharcDescription

API_CLFN_CHARACTERISTIC_SRV/ DataCollectionGroup.dcParamete TEXT

A_ClfnCharacteristicForKeyDate rs[].dcParameterType
/CharcDataType

SAP Digital Manufacturing Integration Guide

286 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A DataCollectionGroup.dcParamete N/A

rs[].sequence

product/class material/inventoryDataType If product/classType = 023

and material/procurement_type
= Purchased or
Manufactured_purchased.

material/plant DataType/plant N/A

N/A DataType/category N/A

product/class/Class (product DataType/dataType (datatype name) N/A

class name)

product/class/characteristics DataType/dataFields N/A

characteristic DataField N/A

characteristic/EntryIsRequired DataField/Required N/A

material/plant DataField/Plant N/A

characteristic/characteristic DataField/fieldName N/A

(name)

characteristic/CharcDataType DataField/type N/A

characteristic/CharcStatus DataField/status N/A

characteristic/ DataField/description If language code is set to EN.

CharcDescription

characteristic/ DataField/fieldLabel If language code is set to EN.

CharcDescription

characteristic/CharcDataType DataField/type If NUM→ FieldType/NUMBER.

If CHAR → FieldType/TEXT.

If DATE → FieldType/DATE.

If Default →
FieldType.TEXT_AREA.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 287
Process Order SOAP Message (based on SAP_COM_0522 Scenario ID)
SAP S/4HANA Cloud Field SAP Digital Manufacturing for execution Field

ManufacturingOrder • Shop Order

• BOM (with the type Order)
• Recipe (with the type Order)
• Phase (with the type Operation Activity)
• Data Collection Groups

Master Recipe SOAP Message (based on SAP_COM_0519 Scenario ID)

SAP S/4HANA Cloud Field SAP Digital Manufacturing for execution Field

BillOfOperations • Recipe (with the type Production)

• Phase (Operation Activity)
• Data Collection Groups

Order Recipe Mapping

SAP Digital Manufacturing
SAP S/4HANA Cloud Field for execution Field Conditions

N/A /version A

/n0:ManufacturingOrderExecuteRequest/ /plant N/A

ManufacturingOrder/ProductionPlant

N/A /status RELEASABLE

N/A /currentVersion True

/n0:ManufacturingOrderExecuteRequest/ /description N/A

ManufacturingOrder/Material

/n0:ManufacturingOrderExecuteRequest/ /recipe N/A

ManufacturingOrder/ManufacturingOrder

N/A /recipeType If
ManufacturingOrderC
ategory = 40, then
SHOPORDER_SPECIFIC_
RECIPE. Otherwise,
SHOPORDER_SPECIFIC.

N/A /relaxedFlow If
ManufacturingOrderC
ategory = 40, then
True.

N/A /routingSteps/stepId 10 based counter

SAP Digital Manufacturing Integration Guide

288 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing
SAP S/4HANA Cloud Field for execution Field Conditions

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ description
ManufacturingOrderActivityNetworkElement/
n1:MfgOrderOperationText

N/A /routingSteps/isEntry True for the first step.

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ reportingStep
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/
ManufacturingOrder/ProductionPlant workCenter/plant

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/
ManufacturingOrder/ workCenter/workCenter
ManufacturingOrderActivityNetworkElement/
n1:WorkCenter

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ProductionPlant routingOperation/
operation/plant

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ManufacturingOrder-/ routingOperation/
n0:ManufacturingOrderExecuteRequest/ operation/operation
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderSequence-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation

N/A /routingSteps/ Default A

routingOperation/
operation/version

N/A /routingSteps/ NORMAL N

routingOperation/
stepType

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 289
 SAP Digital Manufacturing
SAP S/4HANA Cloud Field for execution Field Conditions

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ManufacturingOrder-/ routingStepComponentLi
n0:ManufacturingOrderExecuteRequest/ st/
ManufacturingOrder/Material-/ bomComponent/bom/bom
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/BillOfMaterialVariant

N/A /routingSteps/ Default A

routingStepComponentLi
st/bomComponent/bom/
version

N/A /routingSteps/ Default SHOPORDERBOM

routingStepComponentLi
st/bomComponent/bom/
bomType

/n0:ManufacturingOrderExecuteRequest/ /routingSteps/ N/A

ManufacturingOrder/ routingStepComponentLi
ManufacturingOrderActivityNetworkElement/ st/bomComponent/
n1:ManufacturingOrderComponent/Material material/material

N/A /routingSteps/ Default A

routingStepComponentLi
st/bomComponent/
material/version

N/A /routingSteps/ 10 based counter. Se­

routingStepComponentLi quence in the order
st/bomComponent/ BOM.
sequence

N/A /routingSteps/ 10 based counter

routingStepComponentLi
st/sequence

N/A /routingSteps/ The ID of the next step.

nextStepList/nextStep/
stepId

SAP Digital Manufacturing Integration Guide

290 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing
SAP S/4HANA Cloud Field for execution Field Conditions

/n0:ManufacturingOrderExecuteRequest/ / N/A
ManufacturingOrder/ManufacturingOrder-/ routingOperationGroups
n0:ManufacturingOrderExecuteRequest/ /routingOperationGroup
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderSequence-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation

/n0:ManufacturingOrderExecuteRequest/ / N/A
ManufacturingOrder/ routingOperationGroups
ManufacturingOrderActivityNetworkElement/ /description
n1:MfgOrderOperationText

Shop Order Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ /shopOrder N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder

N/A /status If OrderIsDelivered or

OrderIsTechnicallyCompleted or
OrderIsDeleted, then CLOSED
(504). Otherwise RELEASABLE
(501).

N/A /shopOrderType/orderType PRODUCTION

N/A /erpOrder Default True

/ /erpUnitOfMeasure N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrdPlndTotQtyInBaseUnit

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 291
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /routing/plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ /routing/routing N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder

N/A /routing/routingType If ManufacturingOrderCategory

= 40, then
SHOPORDER_SPECIFIC_RECIPE. Oth­
erwise, SHOPORDER_SPECIFIC.

N/A /routing/version Default A

/ /material/material N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material

N/A /material/version Default A

/ /material/plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ /bom/plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ /bom/bom N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant

SAP Digital Manufacturing Integration Guide

292 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /bom/bomType Default SHOPORDERBOM

N/A /bom/version Default A

N/A /priority 500

/ /plannedStartDate N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedStartDate + /
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderScheduledStartTime

/ /plannedCompletionDate N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedEndDate + /
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderScheduledEndTime

/ /buildQuantity N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedTotalQty

/ /orderedQuantity N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedTotalQty

Order BOM Mapping for the BOM Header

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /version Default A

N/A /currentVersion Default True

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 293
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /bom AUFNR-MATNR-STLAN-STLAL
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant

/ /description N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material

N/A /bomType Default SHOPORDERBOM

N/A /status Default RELEASABLE

/ /erpBom N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterial

Order BOM Mapping for the BOM Component

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /sequence 10 based counter

/ /quantity N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/RequiredQuantityInBaseUnit

/ material/plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

SAP Digital Manufacturing Integration Guide

294 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ material/material N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/Material

N/A material/version Default A

/ bom/plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ bom/bom N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant

N/A bom/bomType Default SHOPORDERBOM

N/A bom/version Default A

/ .customValues.BATCH_NUMBER N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/Batch

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 295
Order Mapping for the Data Collection Group
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

N/A /version Default A

N/A /currentVersion Default True

/ /dcGroup N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation
@SVK

/ /description N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/
@StandardWorkFormulaParamGroup
ID

SAP Digital Manufacturing Integration Guide

296 PUBLIC SAP Digital Manufacturing for execution Integration
Order Data Collection Group Mapping for the Data Collection Parameter
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /parameterName N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation
-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
@WorkCenterFormulaParamID

/ /description N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
StandardWorkFormulaParamName

N/A /sequence 10 based sequence

N/A /dcParameterType NUMBER

/ /unitOfMeasure N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
WorkCenterStandardWorkQty/
@unitCode

Order Data Collection Group Mapping for the Data Collection Group Attachment Point
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /sequence 10

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 297
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /routingStep Routing step reference

Order Mapping for the Operation Activity Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /plant N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant

/ /operation N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderSequence-
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation

N/A /version Default A

N/A /currentVersion Default True

N/A /type Default NORMAL_OPERATION

/ /description N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:MfgOrderOperationText

N/A /status Default RELEASABLE

N/A /resourceType Default DEFAULT

SAP Digital Manufacturing Integration Guide

298 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /workCenter N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/n1:WorkCenter

Master Recipe Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /version Deault A

/ /plant N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

N/A /status Default RELEASABLE

N/A /currentVersion Default True

/ /description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup

/ /recipe N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant

N/A /recipeType PRODUCTION_RECIPE

N/A /relaxedFlow If ManufacturingOrderCategory =

40, then True.

N/A /routingSteps/stepId 10 based counter

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 299
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /routingSteps/description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription

N/A /routingSteps/isEntry True for the first step.

/ /routingSteps/reportingStep N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation

/ /routingSteps/workCenter/plant N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

/ /routingSteps/workCenter/ N/A
n0:ManufacturingMasterRecipeIn workCenter
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/WorkCenter

/ /routingSteps/ N/A
n0:ManufacturingMasterRecipeIn routingOperation/operation/
fomationMessage/ plant
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

SAP Digital Manufacturing Integration Guide

300 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /routingSteps/ N/A
n0:ManufacturingMasterRecipeIn routingOperation/operation/
fomationMessage/ operation
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation

N/A /routingSteps/ Default A

routingOperation/operation/
version

N/A /routingSteps/ NORMAL N

routingOperation/stepType

/ /routingOperationGroups/ N/A
n0:ManufacturingMasterRecipeIn routingOperationGroup
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 301
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /routingOperationGroups/ N/A
n0:ManufacturingMasterRecipeIn description
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription

Master Recipe Operation Activity Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /plant N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

/ /operation N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation

N/A /version Default A

N/A /currentVersion Default True

N/A /type Default NORMAL_OPERATION

SAP Digital Manufacturing Integration Guide

302 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription

N/A /status Default RELEASABLE

N/A /resourceType Default DEFAULT

/ /workCenter N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/WorkCenter

Master Recipe Data Collection Group Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Conditions

/ /plant N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

N/A /version Default A

N/A /currentVersion Default True

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 303
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Conditions

/ /dcGroup N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation

/ /description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
@StandardWorkFormulaParamGroup
ID

SAP Digital Manufacturing Integration Guide

304 PUBLIC SAP Digital Manufacturing for execution Integration
Master Recipe Data Collection Parameter Mapping
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /parameterName N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
@WorkCenterFormulaParamID

/ /description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName

N/A /sequence 10 based sequence

N/A /dcParameterType NUMBER

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 305
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /unitOfMeasure N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
WorkCenterStandardWorkQty/
@unitCode

Master Recipe Data Collection Group Attachment Point Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /sequence 10

N/A /routingStep Routing step reference

Master Recipe Standard Value Key Mapping for a Standard Value Group
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /plant N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant

/ /standardValKey N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
@StandardWorkFormulaParamGroup
ID

SAP Digital Manufacturing Integration Guide

306 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /standardVal N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
@WorkCenterFormulaParamID

10 based sequence /sequence N/A

Master Recipe Standard Value Key Mapping for a Standard Value Text
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /locale N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName/
@languageCode

/ /description N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 307
Master Recipe Standard Value Key Mapping for a Standard Value Target
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A /id N/A

10 based sequence /stepId N/A

/ /targetValue N/A
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
WorkCenterStandardWorkQty

Master Recipe BOM Header oData Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A version A

N/A currentVersion TRUE

BillOfMaterial erpBom N/A

Material description N/A

N/A bomType USERBOM

Plant plant N/A

BillOfMaterial- bom N/A

BillOfMaterialVariant

Master Recipe BOM Component oData Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

BillOfMaterialItemQuantity quantity N/A

BillOfMaterialItemUnit unitOfMeasure N/A

BOMItemInternalChangeCount changeNumber N/A

BillOfMaterialItemNodeNumber sequence N/A

BillOfMaterialItemNodeNumber erpSequence N/A

SAP Digital Manufacturing Integration Guide

308 PUBLIC SAP Digital Manufacturing for execution Integration
 SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

N/A assemblyQtyAsRequired TRUE

N/A bomComponentType • CO_PRODUCT if

MaterialCoProduct
• BY_PRODUCT if
BillOfMaterialItemQuantity
is less than 0
• Or else NORMAL

BillOfMaterialComponent, Plant material Material entity found by search fields

Control Key Mapping

SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Conditions

/ /controlKey N/A
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:OperationControlProfile/
@n1:OperationControlKey

N/A /gi N/A

Statuses Mapping
SAP Digital Manufacturing for
SAP S/4HANA Cloud Field execution Field Meaning

DLV I0012 Delivered

TECO I0045 Technically completed

DLFL I0076 Deletion Flag

2.2.5.3.1 Mapping a Material

You can transfer material data from SAP S/4HANA Cloud to SAP Digital Manufacturing for execution.

Mapping the European Article Number (EAN) and Units of Measure (UOMs)
SAP Digital Manufacturing for
SAP S/4HANA Cloud execution Comment

GlobalTradeItemNumber unitsOfMeasureEans

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 309
 SAP Digital Manufacturing for
SAP S/4HANA Cloud execution Comment

tradeNumber.productStandardID Ean.ean

tradeNumber.getProductStandard Ean.category
VariantID())

tradeNumber.isProductStandardM Ean.isMain
ainIndicator()

tradeNumber.getMeasureUnitCode Ean.internalUom

Uom.grossWeight Ean.grossWeight

Ean.netWeight Ean.netWeight

2.2.5.3.2 Mapping of Tolerance-Related Fields of the Order

Header Material

The following table contains the mapping of tolerance-related fields of the order header material.

XML order field of node

ManufacturingOrder.Man
ufacturingOrderItem.
Database field GoodsReceiptTolerances DMC field Type

SHOP_ORDER. UnderdelivTolrtdLmtRat ShopOrder.toleranceUnd BigDecimal

TOLERANCE_UNDER ioInPct er

SHOP_ORDER. OverdelivTolrtdLmtRati ShopOrder.toleranceOve BigDecimal

TOLERANCE_OVER oInPct r

SHOP_ORDER. UnlimitedOverdeliveryI ShopOrder.overDelivery Boolean

OVER_DELIVERY_IS_ALLOW sAllowed IsAllowed
ED

2.2.5.3.3 Mapping Alternate BOM Components

BOM components that belong to the same alternate group in SAP S/4HANA Cloud are mapped as alternate
components for each other in SAP Digital Manufacturing for execution.

Master BOM Component

SAP Digital Manufacturing Integration Guide

310 PUBLIC SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud

DME Field Default Value SAP S/4HANA Cloud Field

alternativeItemGroup AlternativeItemGroup

ERP Alternate Item Group

alternates.enabled TRUE

Alternates Enabled

alternates.priority AlternativeItemPriority

Alternates Priority

alternates.material BillOfMaterialComponent

Alternate Component

Order BOM

SAP S/4HANA Cloud

DME Field Default Value SAP S/4HANA Cloud Field

alternativeItemGroup AlternativeItemGroup

ERP Alternate Item Group

alternates.enabled TRUE

Alternates Enabled

alternates.priority AlternativeItemPriority

Alternates Priority

alternates.material Material

Alternate Component

2.2.5.3.4 Mapping for a Standard Value Key (SVK)

The fields created in SAP S/4HANA Cloud correspond to certain fields of SAP Digital Manufacturing for
execution.

Standard Value Key Mapping for an SV Group

SAP Digital Manufacturing for execution Field SAP S/4HANA Cloud

.plant /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/BillOfOperationsHeader/
n1:BillOfOperationsPlant

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 311
SAP Digital Manufacturing for execution Field SAP S/4HANA Cloud

.standardValKey /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/
BillOfOperationsActivityNetworkElement/
BillOfOperationsActivityNetworkElementTimeSli
ce/StandardWorkFormulaParamGroup/
@StandardWorkFormulaParamGroupID

StandardValue

.standardVal /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/
BillOfOperationsActivityNetworkElement/
BillOfOperationsActivityNetworkElementTimeSli
ce/StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
@WorkCenterFormulaParamID

.sequence 10 based sequence

Standard Value Key Mapping for a StandardValueText

SAP Digital Manufacturing for execution Field SAP S/4HANA Cloud

.locale /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/
BillOfOperationsActivityNetworkElement/
BillOfOperationsActivityNetworkElementTimeSli
ce/StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName/@languageCode

.description /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/
BillOfOperationsActivityNetworkElement/
BillOfOperationsActivityNetworkElementTimeSli
ce/StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName

Standard Value Key Mapping for a StandardValueTarget

SAP Digital Manufacturing for execution Field SAP S/4HANA Cloud

.id

.stepId 10 based sequence

SAP Digital Manufacturing Integration Guide

312 PUBLIC SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing for execution Field SAP S/4HANA Cloud

.targetValue /
n0:ManufacturingMasterRecipeInfomationMessage
/BillOfOperations/
BillOfOperationsActivityNetworkElement/
BillOfOperationsActivityNetworkElementTimeSli
ce/StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
WorkCenterStandardWorkQty

2.2.6 Restrictions and Limitations

This page lists the current restrictions and limitations of SAP S/4HANA Cloud integration.

• Goods Issue
The goods issue from Central Storage Location can't be triggered from SAP Digital Manufacturing. It is
triggered from SAP S/4HANA Cloud.
• Goods Movement
The goods movement from Production Storage Location and between Production Storage Locations can't
be triggered from integrated SAP S/4HANA Cloud system. It is triggered from SAP Digital Manufacturing
only.
• Material-Level Batch Management
Material level is the only supported batch level. The batch number is unique in all plants in connection with
the material. Plant level and client level batch management are not available.

 Note

You must choose the material level as the batch level in SAP S/4HANA Cloud. Otherwise, you might
encounter inbound inventory transfer issues from SAP S/4HANA Cloud to SAP Digital Manufacturing.

• Long Material Number and Batch

Long material number is not supported in all batch scenarios including inventory download with batch
number, batch creation, batch characteristic update and goods receipt with batch number.

2.3 Integration with SAP Business Network Asset

Collaboration

You can connect SAP Digital Manufacturing for execution to SAP Business Network Asset Collaboration.

The aim of SAP Business Network Asset Collaboration is to maintain a global registry of equipment that
uses common definitions. These common definitions are then shared between business partners, such
as manufacturers or original equipment manufacturers (OEMs), operators, or service providers to deliver
collaborative business models.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 313
At the core of the network is the SAP Business Technology Platform with IoT application services. SAP and
partners within the network, collaborate on solutions for connected asset lifecycle management, track and
trace, and IoT for the process industry.

Integration with SAP Business Network Asset Collaboration

SAP Business Network Asset Collaboration SAP Digital Manufacturing for execution

Item of Equipment SFC

Prerequisites

• You've subscribed to both SAP Digital Manufacturing for execution andSAP Business Network Asset
Collaboration .
• You've subscribed and received client credentials. For information about generating the required service
key, see Accessing APIs of SAP Intelligent Asset Management Solutions on the SAP Help Portal.

Procedure

1. Configure the SAP Business Technology Platform for SAP Digital Manufacturing for execution.
1. To create destinations for SAP Business Network Asset Collaboration under the customer SaaS
tenant, go to the SAP BTP cockpit (of Digital Manufacturing Cloud for execution) Connectivity
Destinations .
2. Set the destination name to AIN_DESTINATION_OAUTH.
3. Under Type, select HTTP.
4. Under URL, set the URL provided by SAP Business Network Asset Collaboration DevOps, for example:
https://ain<>-<>.hana.ondemand.com/ain.
5. Under Proxy Type, select Internet.
6. Under Authentication, set OAuth2ClientCredentials.
7. Under Client ID, set clientid provided by SAP Business Network Asset Collaboration DevOps (see
Client ID information in Accessing APIs of SAP Intelligent Asset Management Solutions on the SAP
Help Portal).
8. Under Client Secret, set clientsecret provided by SAP Business Network Asset Collaboration
DevOps (see Client Secret information in Accessing APIs of SAP Intelligent Asset Management
Solutions on the SAP Help Portal).
9. Under Token Service URL, set tokenurl provided by SAP Business Network Asset Collaboration
DevOps (see Token URL information in Accessing APIs of SAP Intelligent Asset Management Solutions
on the SAP Help Portal).
10. Check the availability of the destination connection.

 Example

Connection to AIN_DESTINATION_OAUTH established. Response returned: 401 :

Unauthorized.

SAP Digital Manufacturing Integration Guide

314 PUBLIC SAP Digital Manufacturing for execution Integration
2. Verify that the description name of the business partner in the SAP S/4HANA system corresponds to the
name of the company profile maintained in SAP Business Network Asset Collaboration.

 Note

There are two roles involved in the integration between SAP Business Network Asset Collaboration and
SAP Digital Manufacturing for execution: Manufacturer and Operator.

Manufacturer: This role is assigned to the credential/service key customer configured in the
destination of the SAP BTP cockpit. It can't be configured when setting up the integration between
SAP Business Network Asset Collaboration and SAP Digital Manufacturing for execution. For more
information, see Creating a Service Key in SAP BTP cockpit on the SAP Help Portal.

Operator: This role indicates the buyer or operator of the equipment produced in SAP Digital
Manufacturing for execution. Operators can be maintained in the company profile in SAP Business
Network Asset Collaboration. For more information, see Managing Company Profile in the product
assistance for SAP Business Network Asset Collaboration on the SAP Help Portal.

The SAP S/4HANA business partner corresponds to the operator in SAP Business Network Asset
Collaboration. The description name of the SAP S/4HANA business partner must be identical to the
operator maintained in the company profile in SAP Business Network Asset Collaboration, as SAP
Business Network Asset Collaboration uses the company profile name as a key, not the customer
number in SAP S/4HANA.

1. In SAP Business Network Asset Collaboration, call up the Company Profile app.
2. Note down the name of the operator maintained in the Company Profile. This is a prerequisite for the
integration setup. For example, if the description of the company profile is ABC Corporation, the same
name needs to be maintained for the business partner in the SAP S/4HANA system.
3. Create or edit the business partner in SAP S/4HANA as required. For more information, see SAP
Business Partner in the product assistance for SAP S/4HANA on the SAP Help Portal.
3. Configure SAP Business Network Asset Collaboration.
1. Create and publish the model in SAP Business Network Asset Collaboration based on your business
requirements. For more information on creating and publishing models, see Creating a Model in the
product assistance for SAP Predictive Maintenance and Service, cloud edition on the SAP Help Portal.
2. In SAP Business Network Asset Collaboration, call up the Models app and select the model to create
the external ID.
3. Choose the external ID and select the system name and object type. Then enter the external ID as
required, for example: DMCAINFG126.
4. Configure SAP Digital Manufacturing for execution.
1. Go to the Models app in SAP Business Network Asset Collaboration, select the model, and note down
the external ID you created in Step 3.
2. Enter the external ID of the model in SAP Business Network Asset Collaboration in the field AIN Model
External ID of the material in the Manage Materials app. For more information, see Manage Materials.
3. Go to the Manage Collaboration Links app.
4. Add or maintain the connection between collaboration link and collaboration directive.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 315
 Collaboration Link Collaboration Directive Description

AIN_COLLABORATION_SFC_DONE AIN_CREATE_EQUIPMENT_POST Create an outbound transaction

to create an equipment in
SAP Business Network Asset
Collaboration when an SFC is com­
pleted.

 Note

The equipment is created in SAP Business Network Asset Collaboration when an SFC is completed in SAP
Digital Manufacturing.

Related Information

Product Assistance for SAP Business Network Asset Collaboration

2.3.1 Verification and Troubleshooting for SAP Business

Network Asset Collaboration

Verify if your integration setup was successful and obtain information on how to solve issues.

To verify whether you've set up the integration successfully, check the listed items in the respective systems.

SAP ERP

• Material master records for the produced material and all components have been transferred to SAP
Digital Manufacturing for execution.
• The production order and the respective customer number have been transferred to SAP Digital
Manufacturing for execution.

SAP Business Network Asset Collaboration

• The equipment model has been published.

• The equipment model has been assigned as an external ID. For more information, see Creating a Model in
the product assistance of SAP Business Network Asset Collaboration.

SAP Digital Manufacturing for execution

• The material master has been transferred from SAP ERP to SAP Digital Manufacturing for execution.
• The external ID of the SAP Business Network Asset Collaboration model has been maintained in the
material master.
• You've configured the collaboration link AIN_COLLABORATION_SFC_DONE and the collaboration directive
AIN_CREATE_EQUIPMENT_POST.
• The order has been released.
• An SFC belonging to the production order is completed at the last routing step.

SAP Digital Manufacturing Integration Guide

316 PUBLIC SAP Digital Manufacturing for execution Integration
2.4 Integration with EWM

You can integrate SAP Digital Manufacturing with EWM to achieve planned and efficient processing of all
logistics processes in your warehouse.

Why EWM

Different from the Inventory Management (MM-IM) application, EWM provides the option of mapping your
entire warehouse complex in detail in the system, down to storage bin level. Not only does this give you an
overview of the total quantity of a product in the warehouse, but you can also always see exactly where a
specific product is, at any time, in your warehouse complex.

Use

You can use advanced production integration to stage products that are needed by production and to post the
consumption of products so the goods issue process can be completed. When production is done, you can
pack finished goods in a container and trigger the transfer of goods receipt back to SAP ERP.

To learn more about how to set up the configurations to connect SAP Digital Manufacturing and EWM, see
Connecting to EWM in SAP S/4HANA 1909 to 2020 [page 319] or Connecting to EWM in SAP S/4HANA
2021 [page 323]. For the detailed integration processes and transfer of data and goods movements, see EWM
Integration Scenarios.

Supported EWM

The integration capabilities mentioned in this documentation only applies to the EWM embedded in SAP S/
4HANA 1909 FPS01 and higher versions, as well as decentralized EWM based on SAP S/4HANA 1909 FPS01
and higher.

Related Information

Minimum Version Requirements and Supported Scenarios [page 318]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 317
2.4.1 Minimum Version Requirements and Supported
Scenarios

Here are the minimum release requirements, supported scenarios, and limitations for integrating SAP Digital
Manufacturing with EWM.

Minimum Release Requirement

SAP Digital Manufacturing is compatible with EWM embedded in SAP S/4HANA 1909 FPS01 and higher
version, as well as decentralized EWM based on SAP S/4HANA 1909 FPS01 and higher.

Scenarios Supported

For more information about the supported scenarios, see EWM Integration Scenarios.

SAP Digital Manufacturing Integration Guide

318 PUBLIC SAP Digital Manufacturing for execution Integration
2.4.2 Connecting to EWM in SAP S/4HANA 1909 to 2020

The page demonstrates the configurations that are required to enable integration with EWM versions from
EWM in SAP S/4HANA 1909 to EWM in SAP S/4HANA 2020.

• #unique_265/unique_265_Connect_42_subsection-im1 [page 319]

• #unique_265/unique_265_Connect_42_subsection-im2 [page 319]
• #unique_265/unique_265_Connect_42_subsection-im3 [page 320]
• #unique_265/unique_265_Connect_42_subsection-im4 [page 320]
• #unique_265/unique_265_Connect_42_subsection-im5 [page 321]

Configuration in SAP S/4HANA

Follow the configuration steps in Technical Integration with SAP S/4HANA or SAP ERP [page 14] to enable
communication from EWM to SAP Digital Manufacturing.

Configuration in EWM

Please refer to SAP Note 2944311 for detailed configurations that needs to be completed in order to enable
the integration.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 319
Configuration in SAP Cloud Connector
Configure access control to specify the backend systems and resources that can be accessed by your cloud
applications.

1. Log on to SAP Cloud Connector.

2. From your subaccount menu, choose Cloud To On-Premise and select the tab Access Control.
3. Select the virtual host of the EWM system, and add below resources to it.

 Note

The virtual host representing the EWM system also needs to be added as property in the RFC
destination in SAP Cloud Integration.

Configuration in SAP Cloud Integration

Create destinations to specify EWM system for outbound message fromSAP Digital Manufacturing to EWM.

1. Log on to SAP BTP Cockpit and choose Connectivity Destinations .

2. Choose New Destination to create destinations for SAP Cloud Integration with the SAP Cloud Connector.
3. Enter the destination name, and select RFC as Type.
4. Enter the username and password to access EWM.
5. In Additional Properties, add the following properties:

Property Description Value

jco.client.ashost The Virtual Host of the EWM system  Example

defined in the SAP Cloud Connector.
<virtual host>

jco.client.client The client number of EWM.  Example

1000

SAP Digital Manufacturing Integration Guide

320 PUBLIC SAP Digital Manufacturing for execution Integration
 Property Description Value

jco.client.lang The language of EWM.  Example

EN

jco.client.sysnr The system number of EWM.  Example

22

jco.destination.pool_capacity The connection number.  Example

5

Configuration in SAP Digital Manufacturing

1. Set up logical systems and system destinations. Go to the Manage Business Settings app and configure the
following settings.

Field Description Example

Integration Mode Indicates which ERP system SAP S/4 HANA

Digital Manufacturing is integrated
with.

ERP Destination Enter here the destination of your Refer to below screenshot.
ERP system. Make sure the destina­
tion is the same as the one that
is configured for your SAP Cloud
Integration tenant. To see the ERP
destination configured for SAP Cloud
Integration tenant, go to SAP BTP

cockpit, and choose Connectivity

Destinations in the side menu bar.

EWM Destination Enter here the destination name for Refer to below screenshot.
your EWM system. Make sure the
destination is the same as the one
that is configured for your SAP Cloud
Integration tenant. To see the EWM
destination configured for SAP Cloud
Integration tenant, go to SAP BTP

cockpit, and choose Connectivity

Destinations in the side menu bar.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 321
 Field Description Example

ERP Logical System The logical system of ERP de­

fined in EWM system. To see
your logical system, in EWM, go
to Customizing for Extended
Warehouse Management under SCM
Basis Integration Basic Settings
for Setting Up the System Landscape
Name Logical Systems

2. Maintain EWM-managed storage locations. Go to the Manage Storage Locations app, create storage
locations with the same names as the storage locations in the EWM system, and enable EWM-Managed
Storage Location.
3. Go to the Manage Collaboration Links app and assign the following directives to respective collaboration
links to enable outbound integration from SAP Digital Manufacturing toEWM.

Collaboration Link Collaboration Directive Description

EWM_COLLABORATION_SHOPORDER_R EWM_SINGLE_ORDER_STAGING_REQU This collaboration link is triggered

ELEASE EST by order release to send single-order
staging request to EWM.

EWM_COLLABORATION_AUTO_STAGIN EWM_SINGLE_ORDER_STAGING_REQU This collaboration link is used to send

G EST SFC-level staging request to EWM.

EWM_COLLABORATION_COMPONENT_A EWM_COMPONENT_ADD This collaboration link is triggered by

DD Assemble Components plugin to send
component consumption to EWM.

SAP Digital Manufacturing Integration Guide

322 PUBLIC SAP Digital Manufacturing for execution Integration
 Collaboration Link Collaboration Directive Description

EWM_COLLABORATION_YIELD_CONFI EWM_GOODS_ISSUE_POST When

RMATION EWM_COLLABORATION_COMPONENT_A
DD is not configured, this collabora­
tion link is triggered by SFC complete
to send component consumption to
EWM.

EWM_COLLABORATION_SFC_DISPOSI EWM_SFC_DISPOSITION When

TION EWM_COLLABORATION_COMPONENT_A
DD is not configured, this collabora­
tion link is triggered by SFC scrap to
send component consumption to
EWM.

COLLABORATION_SFC_COMP_REMOVE EWM_COMPONENT_REMOVE_OP This collaboration link is triggered by

_EWM_OP component removal for production
order in Work Center POD.

EWM_COLLABORATION_CONTAINER_C EWM_CONTAINER_CLOSE_CONFIRMAT This collaboration link is triggered by

LOSE ION closing container to send goods re­
ceipt message to EWM.

COLLABORATION_ERP_SCRAP_CONFI ERP_SCRAP_CONFIRMATION This collaboration link is triggered by

RMATION SFC scrap to report scrapped compo­
nent quantity to SAP ERP.

COLLABORATION_ERP_YIELD_CONFI ERP_YIELD_CONFIRMATION This collaboration link is triggered by

RMATION SFC Complete to report quantity of
finished goods to SAP ERP.

Related Information

Connecting to EWM in SAP S/4HANA 2021 [page 323]

Integration Scenario with EWM in SAP S/4HANA 1909 to 2020

2.4.3 Connecting to EWM in SAP S/4HANA 2021

This guide is intended for those who want to use MES-driven staging functionalities in SAP Digital
Manufacturing. It will guide you through the configuration procedures that are required to enable integration
with EWM in SAP S/4HANA 2021.

 Note

Compared to the staging functionality that's supported with EWM in SAP S/4HANA 1909 to 2020, MES-
driven staging allows you to request materials more flexibly. For more information, see Staging Request.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 323
• #unique_266/unique_266_Connect_42_subsection-im1 [page 324]
• #unique_266/unique_266_Connect_42_subsection-im2 [page 324]
• #unique_266/unique_266_Connect_42_subsection-im3 [page 333]
• #unique_266/unique_266_Connect_42_subsection-im4 [page 335]
• #unique_266/unique_266_Connect_42_subsection-im5 [page 338]

Configuration in SAP S/4HANA

Follow the configuration steps in Technical Integration with SAP S/4HANA or SAP ERP [page 14] to enable
communication from EWM to SAP Digital Manufacturing.

Configuration in EWM

Make the following configurations in EWM system. These mainly include using SOA Manager to complete the
configuration for consumer proxies for EWM, as well as some stock notification configurations.

 Note

For additional information on the configuration process, see also 3137363

1. Check the 4 EWM web services: 1 service provider and 3 service consumers.
1. Log on to EWM and execute the transaction code SPROXY.

SAP Digital Manufacturing Integration Guide

324 PUBLIC SAP Digital Manufacturing for execution Integration
 2. On the Enterprise Services Browser screen, choose Namespaces http://sap.com/xi/EWM/
Global Object Types Service Providers Objects , and you can find an object named
WarehouseStagingRequest_In.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 325
 SAP Digital Manufacturing Integration Guide
326 PUBLIC SAP Digital Manufacturing for execution Integration
 3. On the Enterprise Services Browser screen, choose Namespaces http://
sap.com/xi/EWM/Global Object Types Service Consumers Objects , and you can
find 3 object named WarehouseRequestStatus_Out, WarehouseStagingMethod_Out and
WarehouseStockChangeNotification_Out respectively.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 327
2. Create and configure logical ports for consumer proxies of the 3 consumer services.
1. Doubleclick one of the consumer service object checked in above Step 1 to see its detailed information.
For example, you can doubleclick WarehouseRequestStatus_Out.
2. In the top navigation menu, choose Goto Start SOA Manager .

SAP Digital Manufacturing Integration Guide

328 PUBLIC SAP Digital Manufacturing for execution Integration
 3. On the Web Service Configuration screen of SOA Manager, choose Create Manual Configuration
to define logical ports for the consumer proxy /SCWM/CO_BIF_STG_WHR_STATUS.

4. On the manual configuration screen, enter a name in Logical Port Name.

5. In Consumer Security, enter the user name and password that are used to log on to your SAP Cloud
Integration client.

6. In HTTPSettings, enter the URL in URL Access Path. The URL should be: <SAP Cloud Integration
runtime URL>/cxf/soap/GenericMessageProcessor_00.
For more information about getting SAP Cloud Integration runtime URL, seeHow to Get SAP Cloud
Integration Runtime URL [page 21].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 329
 7. Continue to complete the remaining steps. You can keep the default settings. Choose Finish.
8. Set the logical port to default by choosing Set Log.Port Default.

 Note

If you don't set the logical port to default, no messages are created.

9. Repeat step a-g to define logical ports for the other two consumer services
WarehouseStagingMethod_Out and WarehouseStockChangeNotification_Out.
3. Create service binding for the provider service WarehouseStagingRequest_In.
1. Doubleclick the provider service object WarehouseStagingRequest_In.
2. In the top navigation menu, choose Goto Start SOA Manager .
3. On the Web Service Configuration screen of SOA Manager, choose Create Service.

SAP Digital Manufacturing Integration Guide

330 PUBLIC SAP Digital Manufacturing for execution Integration
 4. In Service and Binding Name, enter Service Name and New Binding Name.
5. In Provider Security step, select User ID/Password in the Authentication Settings section.
6. Continue to complete the remaining steps. You can keep the default settings. Choose Finish.
7. In the Service/Binding list, choose Display Binding for the binding you just created.

8. In the Transport Settings tab, note down the value in Calculated Access URL.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 331
4. Make EWM stock synchronization configurations.
1. Execute the transaction code SPRO and choose SAP IMG Reference.
2. Choose SCM Extended Warehouse Management Extended Warehouse Management Interfaces
MES Integration Define Synchronization of Stock Data for MES .

3. Leave ME System empty. Select Synchronized in the Synchronize Stock Data column.

SAP Digital Manufacturing Integration Guide

332 PUBLIC SAP Digital Manufacturing for execution Integration
5. Check that the SCWM service is activated.
1. In the SAP Easy Access Menu, choose Tools Administration Administration Network HTTP
Service Hierarchy Maintenance (transaction code SICF) . The systems open the Define Services
screen.
2. In the Hierarchy Type field, select Service and choose Execute.
3. In the Virtual Hosts/Services column under default host, follow the path sap/bc/srt/xip/SCWM.
4. If the SCWM service is grayed out, it isn't activated. In this case, right-click SCWM and choose Activate.

 Note

To make the staging method download work, you need to define the staging method in EWM first. For more
information, see Sending Staging Method to MES.

Configuration in SAP Cloud Connector

Add 2 virtual host mappings to support RFC and SOAP outbound requests from cloud connector to EWM.

To add the mappings for RFC and SOAP requests, follow below steps:

1. In the cloud connector administration console, choose <Subaccount> Cloud To On-Premise ACCESS
CONTROL .

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 333
2. In the Mapping Virtual To Internal System section, choose Add.
3. In the Add System Mapping pop-up, fill in the required fields step by step. You can refer to below table for
field values.

Field Name Value

Back-end Type ABAP System

Protocol RFC

Connection Type Without load balancing

Application Server Example: idcixxx.wdf.sap.corp To find the application server and in­
stance number of your ERP system:
Instance Number Example: 43000
1. Log on to your target ERP sys­
tem, and execute transaction
code SMICM.
2. From the top menu, choose

Goto Services .
3. You can see the application
server in the Host Name column,
and the instance number in the
Service Name/Port column.

Virtual Application Server Example: xxxclnt910 It is recommended to use a virtual

(cloud-side) name that is different
from internal application server name.

Virtual Instance Number Example: 43000 The default value is the instance num­
ber you entered previously. Leave it
unchanged.

4. For RFC protocol, add the same accessible resources as those mentioned in the cloud connector
configuration in Connecting to EWM in SAP S/4HANA 1909 to 2020 [page 319].
5. Samewise, add another mapping and this time, specify HTTPS as the Protocol. Refer to below table to fill
the required fields.

Field Name Value

Back-end Type ABAP System

Protocol HTTPS

Internal Host Example: idcixxx.wdf.sap.corp To find the internal host and internal
port of your ERP system:
1. Login to your target ERP system,
and execute transaction code
SMICM.
2. From the top menu, choose

Goto Services .
3. You can see the internal host
in the Host Name column, and

SAP Digital Manufacturing Integration Guide

334 PUBLIC SAP Digital Manufacturing for execution Integration
 Field Name Value

Internal Port Example: 43000 the internal port in the Service

Name/Port column.

Virtual Host Example: xxxclnt910 It is recommended to use a virtual

(cloud-side) name that is different
from internal host name.

It's recommended to use the same

name for the EWM destination in SAP
Digital Manufacturing as for the virtual
host.

Virtual Port Example: 43000 The default value is the internal port
you entered previously. Leave it un­
changed.

Principal Type X.509 Certificate (Strict Usage)

Host In Request Header Use Internal Host

6. For HTTPS protocol, add URL Path / and allow access to Path And All Sub-Paths.

Configuration in SAP Cloud Integration

 Note

For the outbound integration to EWM to work, make sure that the EWM Destination configured in
the Manage Business Settings app, the destination configured in SAP Cloud Integration, and the
jco.client.ashost configured in Additional Properties below are all the same.

Add RFC destination of EWM in SAP Cloud Integration.

1. Log on to SAP Digital Manufacturing (SAP Cloud Integration tenant) in the SAP BTP Cockpit, and choose
Connectivity Destinations in the side menu bar.
2. Choose New Destination and enter the following fields to create the destination.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 335
 Name Type Proxy Type User Password Location ID

Enter a destina­ RFC OnPremise Enter the user­ Enter the pass­ If you have main­
tion name that is name to access word to access tained a location
the same as the EWM EWM ID in the Cloud
EWM destination
Connector, enter
configured in the
the location ID
Manage Business
Settings app in here.
SAP Digital Manu­
facturing Cloud.

 Note
To avoid er­
rors in the
SAP Digital
Manufacturin
g outgoing
message, the
destination
name must
not contain
special char­
acters.

3. Add the following Additional Properties:

Property Description Value

jco.client.ashost The Virtual Host of the EWM system  Example

as defined in the Cloud Connector.
<virtual host>

 Note
The virtual host defined here
must be the same as the EWM
destination configured in the
Manage Business Settings app.

jco.client.client The client number of EWM.  Example

100

jco.client.lang The language of EWM.  Example

EN

SAP Digital Manufacturing Integration Guide

336 PUBLIC SAP Digital Manufacturing for execution Integration
 Property Description Value

jco.client.sysnr The system number of EWM.  Example

22

jco.destination.pool_capacity The connection number.  Example

5

Configuration for SAP Cloud Integration iFlow

1. Log on to SAP Cloud Integration and choose the SAP S/4HANA Integration with SAP Digital Manufacturing
package.
2. In the Artifacts tab, search for the EWM OrderStaging process request iFlow.
3. Choose Actions Configure to set the following parameters.
• EWM_PORT
Enter the port that is configured in cloud connector virtual host as mentioned in the above
Configuration in Cloud Connector section.
• EWM_URL
Enter the value after the string warehoustagingrequest_ of the Calculated Access URL noted down
in the service/binding created for EWM provider service in the above Configuration in EWM section.

 Caution

The service name must be the same for all systems (development, quality, and production).

• Location ID
Enter the location ID defined in RFC destination in SAP Cloud Integration.
• Credential Name
Enter the security material name defined in SAP Cloud Integration. The credentials refer to a technical
user defined in EWM / SAP S/4HANA.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 337
  Caution

The user credentials must be the same for all systems (development, quality, production).

Configuration in SAP Digital Manufacturing

1. Set up logical systems and system destinations. Go to the Manage Business Settings app and configure the
following settings.

Field Description Example

Integration Mode Indicates which ERP system SAP S/4 HANA

Digital Manufacturing is integrated
with.

ERP Destination Enter here the destination of your Refer to below screenshot.
ERP system. Make sure the destina­
tion is the same as the one that
is configured for your SAP Cloud
Integration tenant. To see the ERP
destination configured for SAP Cloud
Integration tenant, go to SAP BTP

cockpit, and choose Connectivity

Destinations in the side menu bar.

EWM Destination Enter here the name of the virtual

host of the Cloud Connector, which
you can find under Cloud Connectors
in your SAP Cloud Integration subac­
count in SAP BTP cockpit.

ERP Logical System The logical system of ERP de­

fined in EWM system. To see
your logical system, in EWM, go
to Customizing for Extended
Warehouse Management under SCM
Basis Integration Basic Settings
for Setting Up the System Landscape
Name Logical Systems

SAP Digital Manufacturing Integration Guide

338 PUBLIC SAP Digital Manufacturing for execution Integration
2. Maintain EWM-managed storage locations. Go to the Manage Storage Locations app, create storage
locations with the same names as the storage locations in the EWM system, and enable EWM-Managed
Storage Location.
3. Go to the Manage Collaboration Links app and assign the following directives to respective collaboration
links to enable outbound integration from SAP Digital Manufacturing to EWM.

Collaboration Link Collaboration Directive Description

EWM_COLLABORATION_STAGING EWM_STAGING This collaboration link is used for

MES-driven staging that's supported
in EWM in SAP S/4HANA2021 or
higher versions. It is triggered when
you request components in the
Manage Staging or Manage Staging
2.0 app to send single-order and
cross-order staging requests to EWM.

EWM_COLLABORATION_SHOPORDER_R EWM_SINGLE_ORDER_STAGING_REQU This collaboration link is triggered

ELEASE EST by order release to send single-order
staging request to EWM.

EWM_COLLABORATION_AUTO_STAGIN EWM_SINGLE_ORDER_STAGING_REQU This collaboration link is used to send

G EST SFC-level staging request to EWM.

EWM_COLLABORATION_COMPONENT_A EWM_COMPONENT_ADD This collaboration link is triggered by

DD Assemble Components plugin to send
component consumption to EWM.

EWM_COLLABORATION_YIELD_CONFI EWM_GOODS_ISSUE_POST When

RMATION EWM_COLLABORATION_COMPONENT_A
DD is not configured, this collabora­
tion link is triggered by SFC complete
to send component consumption to
EWM.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 339
 Collaboration Link Collaboration Directive Description

EWM_COLLABORATION_SFC_DISPOSI EWM_SFC_DISPOSITION When

TION EWM_COLLABORATION_COMPONENT_A
DD is not configured, this collabora­
tion link is triggered by SFC scrap to
send component consumption to
EWM.

COLLABORATION_SFC_COMP_REMOVE EWM_COMPONENT_REMOVE_OP This collaboration link is triggered by

_EWM_OP component removal for production
order in Work Center POD.

EWM_COLLABORATION_CONTAINER_C EWM_CONTAINER_CLOSE_CONFIRMAT This collaboration link is triggered by

LOSE ION closing container to send goods re­
ceipt message to EWM.

COLLABORATION_ERP_SCRAP_CONFI ERP_SCRAP_CONFIRMATION This collaboration link is triggered by

RMATION SFC scrap to report scrapped compo­
nent quantity to SAP ERP.

COLLABORATION_ERP_YIELD_CONFI ERP_YIELD_CONFIRMATION This collaboration link is triggered by

RMATION SFC Complete to report quantity of
finished goods to SAP ERP.

EWM_COLLABORATION_FG_GOODS_RE EWM_GOODS_RECEIPT This collaboration link is triggered by

CEIPT Goods Receipt plugin to report goods
receipt of finished goods to EWM.

EWM_COLLABORATION_CO_GOODS_RE EWM_GOODS_RECEIPT This collaboration link is triggered by

CEIPT Goods Receipt plugin to report goods
receipt of co-products to EWM.

EWM_COLLABORATION_BY_GOODS_RE EWM_GOODS_RECEIPT This collaboration link is triggered by

CEIPT Goods Receipt plugin to report goods
receipt of by-products to EWM.

Related Information

Connecting to EWM in SAP S/4HANA 1909 to 2020 [page 319]

Integration Scenario with EWM in SAP S/4HANA 2021

2.4.4 Mapping Plants (Plant Conversion)

If you are managing the same plant in multiple EWM systems, you can use plant conversion to map the EWM
plant to different plants in SAP Digital Manufacturing.

 Note

Plant conversion is supported in integration with EWM in SAP S/4HANA 2021 version or higher.

SAP Digital Manufacturing Integration Guide

340 PUBLIC SAP Digital Manufacturing for execution Integration
  Note

Plant mapping (plant conversion) isn't compatible with the direct communciation scenarios involving SAP
S/4HANA. For more information, see Enable Direct Communication To SAP S/4HANA [page 107].

Procedure

Follow below steps to enable plant converion in EWM integration:

1. Log on to SAP Cloud Integration and search for the SAP S/4HANA Integration with SAP Digital
Manufacturing package.
2. Enter the package and choose the Artifacts tab.
3. In Plant Value Mapping artifact, choose Actions Configure .
4. Select the EWM row item and add value mapping configuration.
5. For each EWM plant in one EWM system, add 2 mapping items. For example, if you have maintained the
same plant A in 2 EWM systems, you need to configure the mappings as follows:

EWM, PLANT DMC, PLANT

<EWM programID A>:<EWM Plant A> <DMC Plant A1>

 Note
For EWM embeded in SAP ERP, the EWM Program ID
equals ERP logical system maintained in the Manage
Business Settings app.

To see your logical system, in EWM customizaing, go

to SCM Extended Warehouse Management SCM

Basis Integration Basic Settings for Creating the

System Landscape Name Logical Systems .

<EWM Destination A>:<EWM PlantA> <DMC Plant A1>

 Note
Use the EWM destination maintained in the Manage
Business Settings app. In this app, you can freely de­
fine the EWM destination.

<EWM programID B>:<EWM Plant A> <DMC Plant B1>

<EWM Destination B>:<EWM PlantA> <DMC Plant B1>

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 341
Related Information

Manage Business Settings

2.4.5 Technical Restrictions and Limitations

This page lists the current technical restrictions and limitations of EWM integration.

• Multiple clients in One System

SAP Cloud Integration does not support multiple clients for one system. Therefore, you can only connect
one SAP S/4HANA SOAP service.

Related Information

Business Restrictions and Limitations

2.5 Troubleshooting Overview

If you run into problems during or after setting up a specific integration scenario, you can find general
troubleshooting information in this guide. The information will be updated as applicable.

Troubleshooting for the Integration with SAP S/4HANA [page 343]

Trouble with User Role Management or Role Templates

Due to changes in the usage of business services of SAP Business Technology Platform, certain role collections
need to be adjusted, otherwise you won't be able to access some of the apps on the launchpad. For some
Production Connectivity Model and Network apps, you need to adjust your role collections by adding some new

SAP Digital Manufacturing Integration Guide

342 PUBLIC SAP Digital Manufacturing for execution Integration
roles from different applications. For more information, see Role Templates (Persona-Based) as well as the SAP
Note 2924331 .

Trouble Using Integrated Floor Stock

If you want to use floor stock integration in SAP Digital Manufacturing, and be able to transfer floor stock data
from and to an SAP ERP, SAP S/4HANA or SAP S/4HANA Cloud system, you need to update certain settings
in your configuration integration. In case of issues, please check that all necessary configuration settings are
done.

• If you use SAP ERP or SAP S/4HANA, see Updating Integration Configuration to Use Floor Stock Data
[page 199]
• If you use SAP S/4HANA Cloud, see Updating Integration Configuration to Use Floor Stock Data [page
276]

For more detailled troubleshooting information and guidance for a specific integration scenario, please refer to
the Implementation Starter Kit for your scenario: Implementation Starter Kits for SAP Digital Manufacturing.

 Note

The content of Implementation Starter Kits is available only to registered or licensed customers and
partners.

Related Information

Verification and Troubleshooting for SAP Business Network Asset Collaboration [page 316]
How to Contact Us
Integration Message Dashboard

2.5.1 Troubleshooting for the Integration with SAP S/4HANA

This section helps you to track, analyse, and resolve issues which can occur regarding the integration between
SAP ERP or SAP S/4HANA and SAP Digital Manufacturing via SAP Cloud Integration using IDOCs.

It provides the following troubleshooting steps per business scenario:

Related Information

Master Data Upload from SAP ERP to SAP Digital Manufacturing Fails [page 344]
Production Order Transfer to ERP Fails [page 344]
Production Order Status is not Updated in SAP S/4HANA or SAP ERP [page 345]
No Equipment Registered in SAP Business Network Asset Collaboration After SFC is Completed [page 345]

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 343
2.5.1.1 Master Data Upload from SAP ERP to SAP Digital
Manufacturing Fails

Find out what to do when master data can't be replicated to SAP Digital Manufacturing.

Symptom

Master data has been created in SAP ERP and you are trying to replicate this master data to SAP Digital
Manufacturing, but the data is not available in SAP Digital Manufacturing.

 Note

You can transfer work centers along with standard value keys (see 2996757 ). To know how to download
the multi-language descriptions of the standard value keys, see 3134473 .

Troubleshooting Steps

1. Check if the correct IDoc has been created and sent successfully.
2. Check if the IDoc has been created, but not sent.
3. Check, if no IDoc has been created.
You can find a detailed description of the necessay steps in IDoc Troubleshooting Steps [page 346].
4. If the IDoc has been been created and sent, but is not yet visible in SAP Digital Manufacturing, check the
message processing in SAP Cloud Integration. To do so, follow the steps outlined in SAP Cloud Integration
Troubleshooting Steps [page 345] message status in SAP Digital Manufacturing.
5. You may also check for incoming messages in the Integration Message Dashboard in SAP Digital
Manufacturing. For more information, see Integration Message Dashboard.

2.5.1.2 Production Order Transfer to ERP Fails

Find out what to do when the production order doesn't reach SAP Digital Manufacturing.

Symptom

You have released a production order through the transaction codes CO01 or CO02 in SAP S/4HANA or SAP
ERP, yet the production order is not reaching SAP Digital Manufacturing.

Troubleshooting Steps

1. Check if the correct IDoc has been created and sent successfully.
2. Check if the IDoc has been created, but not sent.
3. Check, if no IDoc has been created.
You can find a detailed description of the necessay steps in IDoc Troubleshooting Steps [page 346].
4. If the IDoc has been been created and sent, but is not yet visible in SAP Digital Manufacturing, check the
message processing in SAP Cloud Integration. To do so, follow the steps outlined in SAP Cloud Integration
Troubleshooting Steps [page 345].
5. You may also check for incoming messages in SAP Digital Manufacturing. To do so, follow the general
guidance on how to use the Integration Message Dashboard app.

SAP Digital Manufacturing Integration Guide

344 PUBLIC SAP Digital Manufacturing for execution Integration
Related Information

Integration Message Dashboard

2.5.1.3 Production Order Status is not Updated in SAP S/

4HANA or SAP ERP

Find out what to do when status updates for production orders don't reach connected systems.

Symptom

You are executing a production order on the shop floor. Status updates for goods issues, goods receipts, and
the order status aren't reaching SAP S/4HANA or SAP ERP.

Troubleshooting Steps

1. Check the message status in the Integration Message Dashboard in SAP Digital Manufacturing. For more
information, see Integration Message Dashboard.
2. If the message has been delivered successfully to SAP Cloud Integration, check the message processing
on the platform. To do so, follow the steps described in SAP Cloud Integration Troubleshooting Steps [page
345].

2.5.1.4 No Equipment Registered in SAP Business Network

Asset Collaboration After SFC is Completed

You have completed an SFC for an order. SAP Digital Manufacturing for execution is integrated with SAP
Business Network Asset Collaboration.

Symptom

No equipment is registered in SAP Business Network Asset Collaboration after the SFC is completed.

Troubleshooting Steps

Check the message status in the Integration Message Dashboard. For more information, see Integration
Message Dashboard.

2.5.1.5 SAP Cloud Integration Troubleshooting Steps

Learn how to troubleshoot for specific IDoc-related issues.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 345
How to open tickets for issues regarding SAP Cloud Integration usage?

If you encounter issues regarding how to use SAP Cloud Integration such as obtaining P-User accounts and
restarting SAP Cloud Integration, etc., you can open a customer support ticket and assign it to LOD-HCI-PI
component.

How to troubleshoot issues with message processing in SAP Cloud

Integration?

For detailed troubleshooting steps, please see SAP Note 3006794 .

2.5.1.6 IDoc Troubleshooting Steps

Learn how to troubleshoot for specific IDoc-related issues:

Check if the correct IDoc has been created and sent:

Has the IDoc been created successfully?

1. Access your SAP ERP or SAP S/4HANA system.

2. Use transaction WE02 to find errors in IDoc processing and check for IDocs with status Failed.

SAP Digital Manufacturing Integration Guide

346 PUBLIC SAP Digital Manufacturing for execution Integration
3. Choose F8 . The system lists all IDocs that were sent in the respective period. IDocs that have successfully
been posted outbound have the Status 03 and a green light.
4. If you can't find the required IDoc in this list, it has not been created successfully in SAP ERP or SAP
S/4HANA. If you can see the IDoc in this list, but it doesn't have Status 03 and a green light, proceed to
analyze as outlined below.

Has the created IDoc been sent successfully?

1. Double-click the IDoc you need to analyze. You can find the production order details under Data records.

2. Check the status of the IDoc and the respective error code under Status Records.

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 347
  Example

Error Code 02 – Error passing data to port.

3. Click on the record for detailed information.

SAP Digital Manufacturing Integration Guide

348 PUBLIC SAP Digital Manufacturing for execution Integration
 According to the diagnosis information, the IDoc has been sent to SAP Cloud Integration with the specified
MPL ID. Example:
SAP Cloud Integration: https://v0614-tmn.avt.eu1.hana.ondemand.com:443/itspaces/shell/
monitoring/M
ID: AFu2Yym6kLgUUCKWvyKTTXeW54Xh
4. To solve the issue, go to the SAP Cloud Integration to check the message processing.
For more information, see SAP Cloud Integration Troubleshooting Steps [page 345].

SAP Digital Manufacturing Integration Guide

SAP Digital Manufacturing for execution Integration PUBLIC 349
2.6 Extensibility Information

This chapter gives an overview of the extensibility options you've got for SAP Digital Manufacturing.

Introduction

With extensibility, you can customize and enhance existing products and functionalities based on industry-
specific or customer-specific requirements. This section provides you with an overview of the available
extensibility options for SAP Digital Manufacturing and how to make use of these options.

 Note

In addition to the documentation available here, you can also refer to the documentation for SAP Cloud
Integration for data services on the SAP Help Portal (especially the chapters Data Flows, Transform
Operations, Scripts and Functions).

Extending SAP Digital Manufacturing Using the SAP BTP Kyma Environment

One of the environments in which you can deploy your own developments is the Kyma environment for SAP
Business Technology Platform. The Kyma environment includes a serverless engine that lets you build, run,
and manage serverless applications and services to extend SAP Digital Manufacturing. You can enable the
Kyma environment in the Overview section of your subaccount in the SAP BTP cockpit. To know more about
the additional capabilities offered by the Kyma environment for SAP Business Technology Platform, see Kyma
Environment.

SAP Samples

You can find samples for plugins, business processes, as well as other useful content to show how you can
extend your solution to meet your needs in the Develop section on the SAP Help Portal.

API

You can find the APIs that SAP Digital Manufacturing offers as well as the related documentation in the
SAP Business Accelerator Hub . For the procedure to create a service key that is needed to acces SAP
Digital Manufacturing via API, see Create a Service Instance and Service Key in SAP Digital Manufacturing
Subaccount [page 66].

For scenario-related API information, see APIs for SAP Digital Manufacturing.

Custom Integration Flows

You can add the custom integration workflows that you've deployed in SAP Cloud Integration to the Manage
Integration Workflows app. For more information, see User-Defined Customizing Options [page 227].

Related Information

Predefined Customizing Options Using XSLT [page 226]

SAP Digital Manufacturing Integration Guide

350 PUBLIC SAP Digital Manufacturing for execution Integration
3 Shop Floor Integration

SAP Digital Manufacturing connects to the shop floor through Production Connector / SAP Plant Connectivity
to retrieve machine data for analytics and run production processes.

Integration Overview

• https://go.sap.corp/UA [https://go.sap.corp/UA]

3.1 Integration Scenarios

The following integration scenarios are supported:

• Digital Twin Configuration

You use the Production Connectivity Model to configure and manage the equipment and service providers
to establish connectivity to the shop floor. The model helps you configure the digital twins of the machines
on the shop floor. For more information, see: Digital Twin Configuration [page 352].
• Machine Data Integration
You can create service providers that help you connect Production Connectivity Model to tags from
external data sources and also services from various external and internal sources. For more information,
see: Machine Data Integration [page 354].

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 351
• Production Process Configuration
You can use the Production Process Designer to model production processes and translate the production
process designs into configurations by deploying them to Production Connector / SAP Plant Connectivity.
For more information, see:Production Process Configuration [page 356].
• Production Process Execution
Production Connector / SAP Plant Connectivity executes the production processes as configured and
transmits data between the machines and SAP Digital Manufacturing. For more information, see:
Production Process Execution [page 357].

3.1.1 Digital Twin Configuration

Using the Production Connectivity Model, you can configure and manage equipment and service providers to
establish connectivity to the shop floor. The model helps you configure the digital twins of the equipment on
the shop floor.

You can configure equipment and its constant properties such as dimensions or other manufacturer
specifications, as well as the sensor data points.

You can create the digital twin of an equipment using the following apps and wizard:

• Equipment app
• Templates app
• Onboarding Equipment into Production Connectivity Model wizard

Equipment

Using the Equipment app, you can create, view, update, and delete equipment. For more information on using
the Equipment app, see Managing Equipment.

An equipment is a physical instance of a model. An operator maintains additional information specific to an

item of an equipment such as the following:

• Installation information:
An operator maintains installation information related to an equipment such as the serial number, tag
number, installation date, and build date.
• Installation location:
An operator maintains geographical coordinates of the item of an equipment to locate the location of an
item of an equipment.
• Documents:
An operator maintains some best practices information while using the item of an equipment using
unstructured documents.

An equipment can be in any of the following states:

• Unpublished
• In Revision
• Published

SAP Digital Manufacturing Integration Guide

352 PUBLIC Shop Floor Integration
Templates

A template is a format to maintain metadata, that is, attributes and attribute groups, related to a model,
equipment, location, system, or spare part. A template inherits metadata from its parent objects, for example,
parent subclass templates or other parent templates, and can have additional attribute groups and attributes.

A model template inherits the structure from a parent model template, a parent subclass template, other
related parent subclasses, and the parent class.

A template is identified by a unique name and consists of attribute groups and attributes. An attribute group is
a logical grouping of related attributes of the equipment, model and location, and an attribute is a qualifier to
define the equipment.

Example - Classification structure and the relationship to model and equipment

1. The class level is the top-node of the classification.

A class doesn't have a parent object, but can have multiple subclasses as child objects.
2. Subclasses are the child objects of a class. It's possible to model multiple subclasses under the top-level
subclass. Each child subclass inherits attributes or attribute groups from its parent objects, that is, class
and subclasses.
In the example:
• • Subclass 1 (Power transformer) inherits from Class (Transformer)
• Subclass 2 (Dry-type transformer) inherits from Subclass 1 (Power transformer) and Class
(Transformer)
3. Model Templates – created by manufacturers – are the child objects of a subclass. It's possible to
have multiple model templates under the top-level model template. Each child model template inherits
attributes or attribute groups from its parent objects, that is, class, subclasses, and model templates.
When creating a model, you create it with reference to a model template.
In the example:
• Model Template 1 (SDT) inherits from Subclass 2 (Dry-type transformer), Subclass 1 (Power
transformer), and Class (Transformer)

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 353
 • Model Template 2 (SDT-100x) inherits from Model Template 1 (SDT), Subclass 2 (Dry-type
transformer), Subclass 1 (Power transformer), and Class (Transformer)
• The Model is be created with reference to Model Template 2 (SDT-100x), and therefore the model has
all attributes or attribute groups coming from the model template as well as the ones inherited.
4. Equipment Templates – created by operators – are used to provide equipment-specific attributes
or attribute groups. You can use equipment templates as the sole reference for an equipment or in
combination with the templates coming via a model.

 Note

Similar to the model template it possible to have multiple equipment templates under the top-level
equipment template. Each child equipment template inherits attribute or attribute groups from it'ss
parent object, that is, equipment templates.

In the example:
• The Equipment was created with reference to the Model, and therefore this equipment has all
attributes /attribute groups associated with the model, that is, inherited from Model Template 2
(SDT-100x), Model Template 1 (SDT), Subclass 2 (Dry-type transformer), Subclass 1 (Power
transformer), and Class (Transformer)
• Since the Equipment was also created with reference to the Equipment Template, this equipment
would additionally have all attributes or attribute groups associated with the equipment template.

For more information on templates, see Managing Templates.

Onboarding Equipment into Production Connectivity Model Wizard

You can use the Onboarding Equipment into Production Connectivity Model wizard to onboard an equipment
into the Production Connectivity Model. For detailed steps on how to use the wizard, see Onboarding
Equipment into Production Connectivity Model.

3.1.2 Machine Data Integration

A machine can contain one or more shop floor systems. A shop floor system in the Production Connectivity
Model is a server that provides an endpoint that you can use to access data and functions of the machine.

Using shop floor systems, you can connect the Production Connectivity Model to tags provided by external
data sources as well as to services provided by external and internal sources. With the help of shop floor
systems, you can model objects, services, and tag information in the Production Connectivity Model. When you
configure a shop floor system, you define the shop floor system type (internal or external) and the usage of
the shop floor system in Production Connector / SAP Plant Connectivity, for example, usage as a data source.
The corresponding elements are then deployed to Production Connector / SAP Plant Connectivity using the
activation flow provided by the Deploy Shop Floor Elements app.

The following table shows which objects configured in the Production Connectivity Model, correspond to which
configuration elements inProduction Connector / SAP Plant Connectivity.

SAP Digital Manufacturing Integration Guide

354 PUBLIC Shop Floor Integration
Mapping of Entities
Production Connector /
Object in Production Con­ SAP Plant Connectivity
nectivity Model Shop Floor System Type Usage Type Configuration Elements

Shop Floor System External OPC UA data source OPC UA source system
and corresponding agent in­
stance

Shop Floor System External OPC DA data source OPC DA source system
and corresponding agent in­
stance

Shop Floor System External IP21 data source IP21 source system and cor­
responding agent instance

Shop Floor System External AF data source Asset Framework source sys­
tem and corresponding agent
instance

Shop Floor System External OPC UA server (in this case, OPC UA source system
you select methods and not (without agent instance)
tags)

Shop Floor System External Web server Shop Floor System is only
created in the Production
Connector / SAP Plant
Connectivity database; dis­
play in the Control Center of
the Production Connector /
PCo Management Console
isn’t possible

Shop Floor System Internal OPC UA server OPC UA server created

and running in Production
Connector / SAP Plant
Connectivity and corre­
sponding agent instance

Tag Internal - Tag

Service External - Service, only metadata, dis­

play in the Production Con­
nector / PCo Management
Console isn't possible

Service Internal Direct destination call Service, method definition,

method notification with ref­
erence to a destination sys­
tem

Client proxy - Universal Web Server Destination system of the

type Universal Web Service
(RESTful)

Client proxy - OPC UA server Destination system of the

type OPC UA destination sys­
tem

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 355
Managing Shop Floor System

You can use shop floor system to model the following:

• Data sources
You can connect an external data source, such as an OPC UA server, and define all the properties of the
data source. The data source provides tags.
• External servers (type: OPC UA server)
You can connect an external OPC UA server that provides methods.
• Internal servers (type: OPC UA server)
You can define an OPC UA server that is created automatically in Production Connector / SAP Plant
Connectivity. You can define the methods in the configuration of the shop floor system.
• Internal servers (type: Web server)
You can define a Production Connector / SAP Plant Connectivity web server that is created automatically
in Production Connector / SAP Plant Connectivity. You can define the Web services in the configuration of
the service.
• Execution in SAP Digital Manufacturing
You can connect a manufacturing execution service provided by SAP Digital Manufacturing to the
Production Connectivity Model. The manufacturing services allow you, for example, to start or complete an
SFC.

Related Information

Deploy Shop Floor Elements

3.1.3 Production Process Configuration

Using the Production Process Designer, you can model production processes (automation sequences) that
automate the production on the shop floor using services provided by service providers connected to
Production Connector / SAP Plant Connectivity systems. After a design is completed, you deploy and activate
the production process design to transfer the configurations to the runtime environment, including these
Production Connector / SAP Plant Connectivity systems.

SAP Digital Manufacturing Integration Guide

356 PUBLIC Shop Floor Integration
3.1.3.1 Mapping Between Process Models and Production
Connector / SAP Plant Connectivity Configurations

The production processes (automation sequences) created in a production process design correspond to
certain configuration elements in an Production Connector / SAP Plant Connectivity system.

Production Process

Production Process Production Connector / SAP Plant Connectivity

Production Process Multiple call destination system

Input parameters Input variables

Output parameters Output variables

Variables Temporary variables

Service Destination system

Parameters Parameters of a destination system

Subscriptions Subscriptions

3.1.4 Production Process Execution

As a manufacturing automation software, Production Connector / SAP Plant Connectivity enables machine-to-
machine communication and connects equipment with SAP Digital Manufacturing

After a shop floor design is deployed to Production Connector / SAP Plant Connectivity, it is responsible to do
the following:

• Execute automation that's configured by shop floor designs

• Call services in SAP Digital Manufacturing when tag values change
• Write values that are passed from SAP Digital Manufacturing into tags on equipment
• Read tag values from equipment and pass them on to SAP Digital Manufacturing

3.2 Integrate with Production Connector / SAP Plant

Connectivity

Production Connector / SAP Plant Connectivity is the connectivity layer between SAP Digital Manufacturing
and the shop floor.

The supported versions of Production Connector / SAP Plant Connectivity are available in 3253702 .

To connect the Production Connector / SAP Plant Connectivity to SAP Digital Manufacturing via the Cloud
Connector, refer to the procedure describe here: 3271973 .

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 357
If you've already created a connection from Production Connector / SAP Plant Connectivity to Cloud using
SAML, please have a look at the bottom of this page.

The table below shows you how you can assign Production Connector / SAP Plant Connectivity roles based on
the SAP Digital Manufacturing roles of each user. Note, however, that this mapping is not mandatory though.

SAP
Digital
CertificateAdministrator

Manufact
uring Role
\
Productio
PCoConfigurator

ServiceExecutor
n
Administrator

FileProcessor

BackupCreator
Connecto

DataReader

DataStorer
r / SAP

Operator
Plant
Connectiv
ity Role

Producti Yes Yes Yes Yes

on_Engin
eer

Automati Yes Yes Yes Yes Yes Yes

on_Engin
eer

Producti Yes Yes Yes

on_Super
visor

Producti Yes Yes Yes

on_Opera
tor

Manufact Yes
uring_Ad
min

Global_R Yes
egional_
Manager

Plant_Ma Yes
nager

Enable Communication from Production Connector / SAP

Plant Connectivity to Cloud

Context

This procedure is about enabling communication from Production Connector / SAP Plant Connectivity to
SAP Digital Manufacturing. For an overview of the available connectivity use cases, navigate to the Use
Cases section under: Set Up Connectivity to Shop Floor with Production Connectivity Model and Production
Connector / SAP Plant Connectivity On-Premise.

SAP Digital Manufacturing Integration Guide

358 PUBLIC Shop Floor Integration
There are two authentication methods: SAML OAuth certification and x.509 certificate authentication.

To use x.509 authentication for Production Connector or Plant Connectivity (15.5. SP01 or higher), you need to
create a destination in your subaccount that you use for your production process in SAP BTP cockpit. For more
information, see Create a Destination for SAP Digital Manufacturing.

 Note

Production Connector supports x.509 authentification by default. If you migrate from SAP Plant
Connectivity (version 15.5. (SP04) to Production Connector with a destination still using a valid SAML
OAuth certificate, you can continue to use SAML authentication. Once your SAML certificate expires, you
need to replace it manually. For more information, see Certificates.

If you want to use x.509 authorization for destination configurations that still use SAML OAuth, you
need to redeploy the production process / subscription to migrate the destinations from SAML to x.509
authorization.

If you get an error message referring to the import of the certificate, please check 3194709 .

The procedure below is about creating and downloading a SAML OAuth certificate. SAML OAuth authentication
is available for SAP Plant Connectivity versions 15.5 (SP00) or lower. If you want to use x.509 authenticaton,
this procedure is not relevant to you.

 Note

For SAP Plant Connectivity versions 15.5 (SP00) or lower, the SAML OAuth authentication is available.
As of SAP Plant Connectivity 15.5 SP01, the SAP Plant Connectivity to Digital Manufacturing Cloud
authentication process uses the x.509 certificate authentication. You don't need to add trust configuration
in the tenant subaccount anymore. For details, see Certificates and Background: SAML 2.0 Bearer
Assertion Flow.

If you upgrade from an SAP Plant Connectivity version 15.5 (SP00) or lower to an SAP Plant Connectivity
version 15.5 (SP01) or higher, new destinations use x.509 authentication by default. You can continue to
use SAML authentication, though, for destinations created in a previous version of SAP Plant Connectivity.
Note that, once your SAML certificate expires, you need to replace it manually. For more information, see
Certificates.

If you want to use x.509 authorization for destination configurations that still use SAML OAuth, you
need to redeploy the production process / subscription to migrate the destinations from SAML to x.509
authorization.

Procedure

1. For SAML OAuth authentification, on the SAP Digital Manufacturing launchpad, go to the Configure
Production Connectivity app and open the Production Connectors / Plant Connectivity tab to create and
download a SAML OAuth certificate.
a. Choose your SAP Plant Connectivity system.
b. In the Certificates section, under PCo to Cloud Certificate (SAML OAuth), choose Create Certificate.
c. Choose Generate Certificate.
d. Choose Download Certificate to download the SAML metadata.

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 359
2. In the SAP BTP cockpit subaccount where you've subscribed to SAP Digital Manufacturing, you do the
following:
a. Create a service instance as described in the Operations Guide: Prepare for API Integration.
b. Configure trust to the Production Connector / SAP Plant Connectivity system by, in this case,
importing the SAML metadata.

Production Connector / SAP Plant Connectivity works as an identity provider in this case. For more
information, see Establish Trust and Federation with UAA Using Any SAML Identity Provider.

You don't need to register the subaccount in Production Connector / SAP Plant Connectivity as an
application provider; Production Connector / SAP Plant Connectivity authenticates the subaccount
using the certificate.
c. In SAP BTP cockpit, create a new role collection and assign the role Automation_Technical_User
from the service instance, with an application identifier starting with dmc-services-
<randomString>, to the role collection.

For more information, see Configure Authorization by Creating Role Collections

d. Assign the role collection to a technical user: pco_integration_user. For more information, see
Assign Users to Role Collections.

You can use a dummy email address for this purpose.

3.2.1 Minimum Version Requirements and Supported

Scenarios

Here are the minimum release requirements, supported scenarios, and limitations for integrating machinery
and equipment on the shop floor using Production Connector / SAP Plant Connectivity.

Minimum Release Requirements

Information on the Production Connector / SAP Plant Connectivity versions that are supported by the current
release of SAP Digital Manufacturing is available here: 3253702 .

 Recommendation

To use the latest features and developments, install the highest available patch level of the pertaining SAP
Plant Connectivity release.

3.2.2 Assignment of Production Connector / SAP Plant

Connectivity Role to IAS User Groups

Production Connector / SAP Plant Connectivity roles can be manually assigned to users in Production
Connector / SAP Plant Connectivity or assigned to user groups in SAP Digital Manufacturing. Assigning

SAP Digital Manufacturing Integration Guide

360 PUBLIC Shop Floor Integration
Production Connector / SAP Plant Connectivity roles to user groups helps minimize the downtime in
Production Connector / SAP Plant Connectivity as the assignment is managed from the Cloud.

Access to Production Connector / SAP Plant Connectivity functions for SAP Digital Manufacturing users is
managed by assigning the relevant Production Connector / SAP Plant Connectivity roles to user groups.

Prerequisites

Before the assignment, ensure the following:

1. User groups with users are created in your Identity Authentication tenant.
2. Role collections in SAP Digital Manufacturing are assigned to the relevant user groups in SAP Business
Technology Platform.
3. You have to set the Principal Type to None in the mapping of the Virtual to Internal System of the Cloud
Connector to allow authorization checks that consider user groups.

For more information, see Manage Users and Authorization.

Production Connector / SAP Plant Connectivity roles correspond to certain user rights that are required in
SAP Digital Manufacturing. User groups with users are created in your Identity Authentication to perform
Production Connector / SAP Plant Connectivity functions. You assign the user rights to user groups in
the Production Connector / Plant Connectivity section of the Configure Production Connectivity app. For
information on how to assign user rights to user groups, see User Groups.

When a new plant connectivity is configured in SAP Digital Manufacturing, by default a technical user group
SAP_Technical_UG is available that can be used to manage service calls from production processes running
in cloud. The access to read indicator values is provided by default. Access for other services such as applying
set points, writing indicator values, printing through file transfer to network location managed in Production
Connector / SAP Plant Connectivity, triggering of Production Connector / SAP Plant Connectivity processes
configured through cloud and so on can be provided by editing the permissions of the technical group.

For an existing Plant Connectivity, the option to create the default technical user group is available in the Plant
Connectivity section of the Configure Production Connectivity app.

See the table below to know the user right that corresponds to a specific role in Production Connector / SAP
Plant Connectivity:

User Right in SAP Digital Production Connector / SAP Plant Role Description in Production
Manufacturing Connectivity Role Connector / SAP Plant Connectivity

Manage Production Connectivity Model PCoConfigurator Configuration of Production

configuration Connector / Plant Connectivity

Read access to Indicator measure­ DataReader Reading and Browsing of Data Tags
ments

Operate shop floor systems (start/stop Operator Starting and Stopping of Service Pro­
agents) viders

Write access to set Indicator value FileProcessor Reading and Writing of Files

Invoke production process or ServiceExecutor Execution of Services

Production Connector / SAP Plant
Connectivity services

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 361
User Right in SAP Digital Production Connector / SAP Plant Role Description in Production
Manufacturing Connectivity Role Connector / SAP Plant Connectivity

Administration of certificates CertificateAdministrator Administration of Certificates

Printing/File storage DataStorer Writing of Data Tags

3.3 Integration with SAP MII

This document guides the user to set up the integration between SAP Manufacturing Integration and
Intelligence (MII). The integration enables the user to import transactions from MII and design production
processes with these transactions as services.

Prerequisites

You have added the SAP Digital Manufacturing subaccount in your cloud connector.

Set up cloud connector

1. Log on to the cloud connector administration console.

2. Choose <YourSubaccount> Cloud To On-Premise .
3. Map your MII system to a virtual system configured in the cloud connector:
1. On the ACCESS CONTROL tab, in the Mapping Virtual To Internal System section, choose  (Add).

2. Specify the backend type as SAP Application Server Java.

3. Specify the protocol as either HTTP or HTTPS, as appropriate.
4. Specify the internal host and internal port.
5. Specify the virtual host and virtual port.
6. Select the principal type as None.

SAP Digital Manufacturing Integration Guide

362 PUBLIC Shop Floor Integration
 7. Select Use Internal Host for Host in Request Header.
8. Optionally, enter a description for this system.
4. Configure access control to the resources on your MII system:
1. Select the newly created system.
2. In the Resources Of <System> section, choose  (Add).
3. Add the resource.

Create destination for MII system

1. Log on to your subaccount for SAP Digital Manufacturing.

2. Choose Connectivity Destinations .
3. Choose New Destination.
4. Enter the following information:

Field Description

Name Enter an identifiable and unique name.

Description [Optional] Enter a description for the destination.

Type Select HTTP.

URL Enter http://<virtualhost>:<virtualport> or https://<vir­

tualhost>:<virtualport>, according to your configuration in
the cloud connector.

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 363
 Field Description

Proxy Type Select OnPremise.

Authentication Select BasicAuthentication.

User Enter the user name and password for an MII

user that has the SAP_XMII_Administrator or
SAP_XMII_Developer role. To create custom role with
specific actions, see Actions for Permissions.

 Note
XMII_Read_Only is a must action for the customized
role. You should be assigned to the transactions that
you want to import into the service registry.

 Caution

There is security risk to use HTTP/Basic authentication in destination configuration.

5. Save the destination.

6. Check if the connection is OK.

 Note

Ignore 404 (Not Found) error, if any. However, you will still need to check other errors such as 401
(Unauthorized).

Create a web server for MII and manage destinations

For details, see Manage Web Servers.

Import transactions into service registry

For details, see Import MII Transactions.

3.4 Troubleshooting for Configure Production Connectivity

This section provides description of typical problems that you may encounter while configuring Cloud
Connector and Production Connector / SAP Plant Connectivity, and establishing connectivity between SAP
Digital Manufacturing and Production Connector / SAP Plant Connectivity.

SAP Digital Manufacturing Integration Guide

364 PUBLIC Shop Floor Integration
3.4.1 Connectivity Issues
You might face the following issues while establishing connectivity between SAP Digital Manufacturing and
Production Connector / SAP Plant Connectivity through Cloud Connector.

Connection cannot be established; please contact your system administrator

Follow these steps to verify the configurations on Cloud Connector and Production Connecter / SAP Cloud
Connectivity to debug the connectivity issue between SAP Digital Manufacturing and Production Connector /
SAP Plant Connectivity.

1. Go to Cloud Connector and open your subaccount. Verify if the status shows Connected and Location ID
value is the same as configured in the SAP Digital Manufacturing Cloud Connector object in the Configure
Production Connectivity application (Note: If multiple cloud connectors are connected, different Location
IDs are must be configured.)
2. Choose Cloud to On-Premise to verify the mapping in Mapping Virtual to Internal System. Verify the Virtual
Host and Virtual Port values shown here are same as configured in the SAP Digital Manufacturing Cloud
Connector object.
3. Go to Principal Propagation tab and check if the IDP configurations have been synchronized. In case
there is an update of the SAML IDP configuration for a subaccount on cloud side, then you must trigger
synchronize action again by refreshing the trust configuration (using the Refresh option).
4. In the Cloud Connector, choose Configuration and go to the On Premise tab. Verify that the System and CA
Certificates are added and are valid. Now go to the Production Connector / SAP Plant Connectivity server.
1. On the server, for a signed certificate, verify if the CA certificate chain (all certificates in the certificate
path, including the root certificate and, if any, all intermediate certificates) have been placed in the
Issuer Store location in the file system and ensure that the certificate is valid:
• SAP Plant Connectivity
C:\ProgramData\SAP\PCo\CertificateStores\CloudServicesHost\Issuer\certs
• Production Connector
C:\ProgramData\SAP\ProdCon\CertificateStores\CloudServicesHost\Issuer\cert
s
2. For a self-signed certificate, verify if the public key of the certificate has been placed in the Trusted
Store location in the file system:
• SAP Plant Connectivity
C:\ProgramData\SAP\PCo\CertificateStores\CloudServicesHost\Trusted\certs
• Production Connector
C:\ProgramData\SAP\ProdCon\CertificateStores\CloudServicesHost\Trusted\cer
ts
3. In Cloud Connector, check if Principal Propagation is set to name (this is the default setting).
5. Restart the cloud server to apply any configuration change.
6. For SAP Plant Connectivity, go to PCO Management Console Tools Cloud Integration Global
Settings Main Service and verify that the server status is Running.
For Production Connector, go to Control Center of the Production Connector Cloud Integration Basic
Settings and verify that the server status is Running.
7. In the Certificate field, check if the certificate that you have created for the cloud server is selected and is
valid (has not expired):

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 365
 • SAP Plant Connectivity
PCO Management Console Tools Cloud Integration Global Settings Main Service
• Production Connector
Control Center of the Production Connector Cloud Integration Internal Communication with Main
Service

3.4.2 Internal Server Error

An internal server error occurred in Production Connector / SAP Plant

Connectivity. Please contact the system administrator.

Please check Production Connector / SAP Plant Connectivity CloudServicesHost log. The log files
(PCoCloudServerLog_yyyy.MM.dd.csv) can be found under:

• SAP Plant Connectivity

C:\Program Files (x86)\SAP\Plant Connectivity\Logs
• Production Connector
C:\Program Files (x86)\SAP\Production Connector\Logs

See the error logs for the time duration.

3.4.3 User Authentication Issues

Find out how to resolve authentication issues.

Production Connector / SAP Plant Connectivity is not able to authenticate a

user

This error occurs due to a missing user entry in the Cloud Integration section of Production Connector /
SAP Plant Connectivity. You need to add all users who require access to Production Connector / SAP
Plant Connectivity cloud services through SAP Digital Manufacturing in Production Connector / SAP Plant
Connectivity under:

• SAP Plant Connectivity

PCO Management Console Tools Cloud Integration User Configuration
• Production Connector
Control Center of the Production Connector Cloud Integration User Configuration

The user ID in Production Connector / SAP Plant Connectivity must match the Subject Name Identifier
attribute selected in the Identity Authentication Service of the user. For example, if the attribute value is E-Mail,

SAP Digital Manufacturing Integration Guide

366 PUBLIC Shop Floor Integration
you need to provide the email ID of the SAP Digital Manufacturing user in the User ID field of Production
Connector / SAP Plant Connectivity.

SAP Digital Manufacturing Integration Guide

Shop Floor Integration PUBLIC 367
4 Resource Orchestration Integration

Learn to connect ERP systems and applications to SAP Digital Manufacturing for resource orchestration to
enable seamless data transfer and synchronization.

SAP Digital Manufacturing for resource orchestration is a cloud-based scheduling service that enables you to
control operations and monitor events on the shop floor. Integrating other systems and applications with SAP
Digital Manufacturing for resource orchestration can help manufacturers to :

• Streamline their production processes and improve overall efficiency

• Achieve end-to-end visibility into their production processes
• Make data-driven decisions and optimize resource usage

To learn about the features and its functionalities, see About Resource Orchestration.

Related Information

Overview Characteristics-Based Sequencing [page 368]

Integration with SAP Manufacturing Execution [page 372]
Data Engineering Configuration [page 389]

4.1 Overview Characteristics-Based Sequencing

Schedule operations based on characteristics in SAP Digital Manufacturing for resource orchestration for
production orders from SAP S/4HANA system.

Scheduling operations based on characteristics sequencing is an effective way to optimize manufacturing

processes. In this approach, the sequencing of operations in resource orchestration is determined by the
characteristics of the product being manufactured. Characteristics represent distinct features or attributes of a
material, such as color, size, shape, and so on. By assigning characteristics to a material, you can:

• Optimize the production process and reduce the time and effort required.
• Reduce the risk of errors, defects, or other quality control issues.
• Adjust the production process quickly and easily to accommodate changes.
• Improve resource allocation in the most efficient and effective way.

SAP Digital Manufacturing Integration Guide

368 PUBLIC Resource Orchestration Integration
4.1.1 Integration with SAP S/4HANA

Characteristic-based sequencing is a feature that allows users to sequence production orders based on
characteristic values.

You can extend your integration scenario involving SAP Digital Manufacturing for resource orchestration and
SAP S/4HANA using the options provided in this chapter. However, characteristic-based sequencing feature is
not supported for orders coming from SAP ERP.

To benefit from the options described here, you need to set up the integration between SAP Digital
Manufacturing, which includes SAP Digital Manufacturing for resource orchestration, and SAP S/4HANA. More
information, see Integration with SAP S/4HANA or SAP ERP [page 9].

To implement characteristics-based sequencing, you've to do the following:

1. Maintain Custom Data [page 369]

2. Modify Data Values for Production Orders [page 370]

4.1.1.1 Maintain Custom Data

Use the Manage Custom Data app to define custom data to be used as characteristic values in production
orders.

Prerequisites

To schedule characteristics-based operations in SAP Digital Manufacturing for resource orchestration using
the Dispatching and Monitoring app you must perform the prerequisites mentioned here:

• You've established integration with SAP S/4HANA system.

• You've created a configurable material for a semi-finished or a finished material that contains the
characteristics and their values in SAP S/4HANA system and before sending it to SAP Digital
Manufacturing:
• You've created characteristics. Use the REO_ prefix for each characteristic's name.

 Example

REO_RED

• You've assigned class type 300 as the material class.

• You've assigned your characteristics to your classification. Use the REO_ prefix for its name.
• You've created a configurable material. Use the REO_ prefix for its name. Otherwise, you can’t schedule
the order in the Dispatching and Monitoring app.

 Example

REO_CONFIG_MAT_COLOR

• You've assigned your classification to the material.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 369
 • You've defined the configuration profile for the configurable material and linked it.

Context

Perform the steps to map and manage REO_ specific data in the shop order category. This allows you to sort
the materials associated with production orders (prefixed with REO_) easily in resource orchestration.

Procedure

1. Launch the SAP Digital Manufacturing application.

2. Go to the Manage Custom Data app.
3. Select the Shop Order custom field definition.
4. Choose Add to create a custom field that represents a characteristic of a configurable material.

 Example

Identify the characteristics of the configurable material and define them as custom data:
• Data Field: Represents characteristics of the material.

 Example

REO_COLOR

• Field Label: UI label displayed for the data field

4.1.1.2 Modify Data Values for Production Orders

Perform the transformation of the incoming XSLT message by adding custom data values.

Prerequisites

To schedule characteristics-based operations in SAP Digital Manufacturing for resource orchestration using
the Dispatching and Monitoring app you must perform the prerequisites mentioned here:

• You've established integration with SAP S/4HANA system.

• You've created a configurable material for a semi-finished or a finished material that contains the
characteristics and their values in SAP S/4HANA system and before sending it to SAP Digital
Manufacturing:
• You've created characteristics. Use the REO_ prefix for each characteristic's name.

SAP Digital Manufacturing Integration Guide

370 PUBLIC Resource Orchestration Integration
  Example

REO_RED

• You've assigned class type 300 as the material class.

• You've assigned your characteristics to your classification. Use the REO_ prefix for its name.
• You've created a configurable material. Use the REO_ prefix for its name. Otherwise, you can't schedule
the order in the Dispatching and Monitoring app.

 Example

REO_CONFIG_MAT_COLOR

• You've assigned your classification to the material.

• You've defined the configuration profile for the configurable material and linked it.

Context

Perform the steps to customize existing integration workflows in the Manage Integration Workflows app. To
enable this function, you need to modify the XSLT of the workflow type Production Order Download
(LOIPRO05 V2).

 Note

For more information on how to enable LOIPRO05 version 2, see 3115603 .

Procedure

1. In the Manage Integration Workflows app, enter LOIPRO05 in the search field.
2. In the workflow Production Order Download (LOIPRO05 V2), go to the Standard XSLT field and copy
the whole section into the Custom XSLT field.
3. In the Custom XSLT field, make the required modifications:

Search for the code snippet in the Custom XSLT.

<CustomFieldList>
<CustomField>
<Attribute>ABC</Attribute>
<Value>value_1</Value>
</CustomField>
<CustomField>
<Attribute>XYZ</Attribute>
<Value>value_2</Value>
</CustomField>
</CustomFieldList>

Replace the code snippet with the code here.

<CustomFieldList>

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 371
 <xsl:for-each select="E1VCCHR">
<CustomField>
<Attribute>
<xsl:value-of select="ATNAM"/>
</Attribute>
<Value>
<xsl:value-of select="ATWRT"/>
</Value>
</CustomField>
</xsl:for-each>
</CustomFieldList>

 Note

If you're already working with your own custom XSLT and need to find the exact positon where an XSLT
snippet needs to be inserted to activate a new functionality, you can refer to the position of that XSLT
snippet in the Standard XSLT.

The E1VCCHR message segment in the LOIPRO05 V2 IDoc document contains information such as the
characteristic values, dependencies, and restrictions for a configurable material. Check for data that
starts with REO_ and its attribute. This helps you validate if all characteristics specific to SAP Digital
Manufacturing for resource orchestration that were defined earlier, while creating the production order, are
displayed.
4. To verify the data do as follows:
1. Launch the SAP Digital Manufacturing application.
2. Navigate to the Integration Message Dashboard Payload Request Payload to check if the
characteristics are downloaded into custom data of the order.

 Tip

Check the attributes of <CustomFieldList>.

3. Go to the Manage Orders app.

4. Search for the relevant production order that's transferred from SAP S/4HANA system.
5. Choose the production order and select the Custom Data tab.
Check for data that starts with REO_ and its attribute. This helps you validate if all REO specific
characteristics defined earlier, while creating the production order, are displayed.
For more information, see Maintain Custom Data [page 369].
5. Go to the Dispatching and Monitoring app to sort and schedule operations based on sequencing of
characteristics.

Use the multi-sorting and filtering options in the worklist table to schedule characteristics-based
dispatching operations. For more information, see Worklist Area.

4.2 Integration with SAP Manufacturing Execution

In addition to using Resource Orchestration with SAP Digital Manufacturing for execution, you can also
integrate it with SAP Manufacturing Execution.

This integration lets production supervisors create schedules using Resource Orchestration in SAP Digital
Manufacturing for execution and then transfer the scheduling data to SAP Manufacturing Execution

SAP Digital Manufacturing Integration Guide

372 PUBLIC Resource Orchestration Integration
The integration of SAP Manufacturing Execution with Resource Orchestration supports the following business
scenarios:

• Scheduling of orders that you create in the SAP Manufacturing Execution system using Resource
Orchestration where the supervisor dispatches operations to resources. The scheduled dates and
resources from Resource Orchestration are then transferred to the SAP Manufacturing Execution system.
• Orders that you release in Resource Orchestration trigger the creation of an SFC in the SAP Manufacturing
Execution system. All further execution is carried out in the SAP Manufacturing Execution system.

Related Information

Minimum Version Requirements and Supported Scenarios [page 373]

4.2.1 Minimum Version Requirements and Supported

Scenarios

Here are the minimum release requirements, supported scenarios, and limitations for integrating SAP Digital
Manufacturing with SAP Manufacturing Execution.

Minimum Release Requirements

You can integrate Resource Orchestration in SAP Digital Manufacturing with SAP Manufacturing Execution
15.1SP05 or higher.

 Recommendation

To use the latest features and developments, integrate with the highest available patch level of SAP
Manufacturing Execution.

Supported Scenarios

• Scheduling shop orders in Resource Orchestration and SAP Digital Manufacturing through the Operator
POD in SAP Manufacturing Execution
• Shop orders created in SAP ERP and replicated to SAP Manufacturing Execution
• Shop orders created in a standalone SAP Manufacturing Execution system
• Re-scheduling shop orders in Resource Orchestration

• Automatically replicating shop orders and schedules generated in SAP Manufacturing Execution to
Resource Orchestration

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 373
• Enhancing the SO Step Report in SAP Manufacturing Execution to display schedules that include
scheduled dates and resource information
• Releasing orders from Resource Orchestration to SAP Manufacturing Execution

Manual and automatic scheduling modes are supported for all scenarios.

Unsupported Scenarios

• Operation split in Resource Orchestration and its use in SAP Manufacturing Execution
• Visualization of production progress in Resource Orchestration

4.2.2 Integrating SAP Manufacturing Execution On-Premise

to Resource Orchestration (Inbound)

You can connect SAP Manufacturing Execution On-Premise to Resource Orchestration.

Context

After you get the email from SAP confirming that provisioning is complete, create a ticket to request data
needed for data replication. After receiving the data, define plants in your system and install and configure
SDI (see Setting Up the Connection to SAP Digital Manufacturing [page 374]). After you have configured SDI,
create a second ticket with SAP to request data replication.

Note that steps for configuring SDI often change and vary depending on the database source, such as Oracle
or SAP S/4HANA. For more information, see Set Up Data Provisioning Monitoring and HANA Smart Data
Integration.

For the initial setup, create a remote source using SDI_USER.

4.2.2.1 Setting Up the Connection to SAP Digital

Manufacturing

You can set up the connection to SAP Digital Manufacturing using SAP HANA Smart Data Integration (SDI).

 Note

SDI works for SAP Digital Manufacturing hosted on AWS and MS Azure. However, for SAP Digital
Manufacturing hosted on MS Azure, we recommend you use Data Engineering for SAP Digital
Manufacturing. To set up the connection using Data Engineering see the Setup Guide.

SAP HANA Smart Data Integration (SDI) replicates business data from on-premise systems to the HANA
database in SAP Digital Manufacturing. SDI uses the HANA DP Agent 2.0 for this purpose. It’s a client

SAP Digital Manufacturing Integration Guide

374 PUBLIC Resource Orchestration Integration
component that is available with your cloud license and has to be installed on the on-premise network to
set up the connection.

1. Install and configure SDI (HANA DP Agent 2.0). For more information, see Install the Data Provisioning
Agent.
2. Depending on the source database, configure the appropriate adapter. Based on the adapter you choose,
provide permissions to data source tables.

 Note

One data provisioning agent can connect to multiple source systems that use different databases.

The agent offers various adapters. You must choose the correct adapter that corresponds to the
database of your data source system. For example, if you use an SAP HANA database with SAP
Manufacturing Execution, you must use an SAP HANA adapter. For more information, see the user
assistance for SAP HANA Smart Data Integration and SAP HANA Smart Data Quality on the SAP Help
Portal.

3. When you've configured the data provisioning agent, Create a Customer Incident [page 375]. The SAP
DevOps team reaches out to you to initiate data replication.
4. Any data table changes at the source system are tracked automatically by the data provisioning agent.
Once the data provisioning agent gets the table changes, it sends these changes to the SAP HANA
database.

 Note

• The data provisioning agent uses different mechanisms depending on the source database. For
example: SAP HANA database uses triggers. Microsoft SQL uses logs.

5. Enter the system details, such as the logical system ID, of the on-premise system that you intend to use
as the data source in the Manage Business Settings app. For more information, see Manage Business
Settings.

Result: After these steps in the workflow are completed, the data tables are available in SAP Digital
Manufacturing and are continuously updated.

Related Information:

• Downloading and Configuring the HANA DP Agent 2.0

• Configure the Data Provisioning Agent
• SAP HANA Smart Data Integration Data Provisioning Agent Sizing Guide

4.2.2.1.1 Create a Customer Incident

Once you configure the DP Agent, the process of data replication can be initiated. To start this process, create
an incident.

You must create an incident on the Support Portal .

 Note

S-User account is required.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 375
The required support component details are as follows:

• Onboarding and Operations Issue: MFG-DM-OPS

• Short Text: DMC Data Replication: Request for technical information <CUSTOMER_NAME>
• Priority: Medium
• Detailed Text:
• DB type (HANA, Oracle, MSSQL and so on)
• Host
• Port Number
• Database Name
• Schema
• Period for Data Replication (For example - 3 months, 6 months and so on)
• System ID for each system (or Netweaver ID if SID does not exist)
• Client (Client needed if it is ERP)

Please share a username and password in secure storage. This user must have SELECT, TRIGGER and CREATE
ANY permissions, with the GRANT option, on the source system SCHEMA.

 Note

After installation and configuration of the agent, update dpagentconfig.ini in the root folder as follows,
and then restart the agent:

• parameter framework.async.fetchSize: set to 50

• parameter framework.maxDataSize: set to 5MB
• parameter framework.fetchSize: set to 1000

4.2.2.1.2 Data Replication

SAP replicates a fixed set of data tables from the source systems based on certain start data.

After replication, the data tables are available in the SAP HANA database, that is used by SAP Digital
Manufacturing.

Any data table changes at the source system is being tracked automatically by the DP agent. Once the DP
agent gets the changes, it sends the delta to the SAP HANA database.

 Note

The DP agent has different mechanisms based on the source database. For example: HANA database uses
triggers. Microsoft SQL uses logs.

For DMC Data Engineering, any data table changes at the source system is being tracked automatically by
the Data Engineering agent. Once the Data Engineering agent gets the changes, it sends the delta to the SAP
DMC database, based on the schedule maintained. For more information, refer the Manage Data Models topic
in DMC Data Engineering.

SAP Digital Manufacturing Integration Guide

376 PUBLIC Resource Orchestration Integration
Related Information

SAP ME Tables [page 377]

4.2.2.1.2.1 SAP ME Tables

SAP ME

Table Name Short Description

WORK_INSTRUCTION_LOG Work instruction log

WORK_CENTER Work center

USR User

SHOP_ORDER Shop order

AR_SHOP_ORDER Shop order archive

SFC_DATA SFC data

SFC_BOM SFC bill of material

SFC_ASSY SFC assembly

SFC SFC

AR_SFC SFC archive

RMA_NUMBER RMA number

RMA_DATA RMA data

RESRCE Resource

OPERATION Operation

NC_DATA Non conformance data

AR_NC_DATA Non conformance data archive

NC_CODE Nonconformance code

LABOR_CHARGE_CODE Labor charge code

ITEM_GROUP_MEMBER Item group member

ITEM_GROUP Item group

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 377
Table Name Short Description

ITEM Item

INCIDENT_NUMBER Incident number

ACTIVITY_LOG Activity log

AR_ACTIVITY_LOG Activity log archive

PARAMETRIC Parametric

PARAMETRIC_MEASURE Parametric measure

NC_GROUP Nonconformance group

NC_GROUP_MEMBER Nonconformance group member

ITEM_T Item text

RESOURCE_SPEED_LOSS Resource speed loss

PRODUCTION_LOG Production log

RESOURCE_REASON_CODE Resource reason code

RESOURCE_REASON_CODE_T Resource reason code text

RESOURCE_SHIFT Resource shift

RESOURCE_STATUS_LOG Resource status log

SHOP_ORDER_STANDARD_RATE Shop order standard rate

SITE Site

TIME_ELEMENT Time element

TIME_ELEMENT_T Time element text

TIME_ELEMENT_TYPE Time element type

TIME_ELEMENT_TYPE_T Time element type text

USER_SHIFT User Shift

USER_SHIFT_DEFINITION User shift definition

USER_SHIFT_DEFINITION_BREAKS User shift definition breaks

USER_SHIFT_T User shift text

DATA_FIELDS Data field

SAP Digital Manufacturing Integration Guide

378 PUBLIC Resource Orchestration Integration
 Table Name Short Description

RESOURCE_TYPE Resource type

AR_ NC_CUSTOM_DATA Archived nonconformance custom data

NC_CUSTOM_DATA Nonconformance custom data

NC_DATA_REF_DES Nonconformance data reference description

SHOP_ORDER_SFC Shop order SFC

STATUS_MEANING Status meaning

WORK_CENTER_MEMBER Work center member

ROUTER_OPERATION Router operation

SFC_ROUTER SFC router

SFC_STEP SFC step

BOM_COMPONENT B0M component

COMP_TIME_LOG Component time log

COMP_TIME_REF_DES Component time reference description

INVENTORY Inventory

PROCESS_LOT Process lot

PROCESS_LOT_MEMBER Process lot member

RESOURCE_TIME_LOG Resource time log

RESOURCE_TIME_MEMBER Resource time member

ROUTER Router

ROUTER_STEP Router step

SFC_ROUTING SFC routing

SHOP_ORDER_TYPE Shop order type

DC_GROUP Data collection group

DC_PARAMETER Data collection parameter

SFC_IN_WORK SFC InWork

SHOP_ORDER_SCHEDULE Shop order schedule

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 379
Table Name Short Description

RESOURCE_TYPE_RESOURCE Resource type resource

BOM B0M

INVENTORY_ASSY_DATA Inventory assembly data

STATUS Status

NC_CODE_T Nonconformance code text

WORK_CENTER_T Work center text

4.2.3 Integrating Resource Orchestration to SAP

Manufacturing Execution On-Premise (Outbound)

You can connect Resource Orchestration to SAP Manufacturing Execution On-Premise.

Context

Here you learn how you can connect Resource Orchestration to SAP Manufacturing Execution On-Premise.

Procedure

1. Install and configure Cloud Connector.

For information on installing and configuring the Cloud Connector, see Setting Up the Cloud Connector
[page 22].
2. Configure SAP Cloud Integration to connect with SAP Digital Manufacturing for execution.

1. Go to Operations View Manage Security .

2. Add User Credentials with the Name: CF_AUTH, the User: <the clientid of uaa>, and the
Password: <the clientsecret of uaa>.

 Note

To get the clientid and clientsecret, go to SAP BTP Cockpit (of SAP Digital Manufacturing
for execution) Services Service Instance Service Key , the clientid and clientsecret
are under the uaa tag.

3. Add User Credentials with the Name: PD_DEPLOYER_USER and the User: <the SAP Cloud
Integration user>, Password: <the password of SAP Cloud Integration user>.

SAP Digital Manufacturing Integration Guide

380 PUBLIC Resource Orchestration Integration
 4. To search for the Digital Manufacturing Execution Integration package in the content hub, go to
Discover .
5. Choose the Digital Manufacturing Execution Integration package (Integration iflow package of SAP
Digital Manufacturing for execution).
6. Choose Copy to copy the Digital Manufacturing Execution Integration package to the customer
tenant.
7. To set the following parameters in Initial Parameters go to Design Digital Manufacturing
Execution Integration package Artifacts Initial Parameters Action Configure .

Parameter Name Description Value

PID DME_GENERIC_PROCESSING_00

TENANT_CREDENTIALS The user credential created in SAP PD_DEPLOYER_USER

Cloud Integration Security Material.

TENANT_URL SAP Cloud Integration Tenant Man­ Refer to the email the customer re­
agement URL used for access from ceived after confirming successful
the Eclipse plugin. Used during con­ SAP Cloud Integration tenant provi­
tent deployment (iflow). sioning. Add the Management URL
(accessed from the Eclipse plugin)
included in the CPI successful provi­
sioning email.

 Example
https://xxxx-
tmn.avt.eu1.hana.onde­
mand.com

COMMON_DME_SB_URL Service Broker URL for JWT token Go to SAP BTP Cockpit (of SAP
fetching. Digital Manufacturing for execution)

Services Service Instances

Service Key . The URL can be

found by choosing the tag url, un­
der the tag uaa.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 381
 Parameter Name Description Value

COMMON_DME_INT_URL The application routers URL of back- Go to SAP BTP Cockpit (of SAP
end integration -ms application. Digital Manufacturing for execution)

Subaccounts , enter the cus­

tomer tenant and select the data
center from the third node of the API
Endpoint.

 Example
https://api.cf.eu10.hana.onde­
mand.com

The data center is eu10.

Use the data center value to re­

place <data center> of the fol­
lowing URL: https://dm-prod-prod-
dme-integration-ms.cfapps.<data
center>.hana.ondemand.com

COMMON_DMC_REO_M_E_OP_SECUR The list to map the plant and  Example

ITY_MATERIAL_LIST technical user credential for inte­
SAP=ME_CREDENTIAL1;
gration. Format: <plant1>=<user
1000=ME_CREDENTIAL2
credential1>;<plant2>=<user
credential2>

SAP Digital Manufacturing Integration Guide

382 PUBLIC Resource Orchestration Integration
 Parameter Name Description Value

COMMON_DMC_REO_M_E_OP_URL_L The list to map the plant  Example

IST and the URL of wsdl. For­
SAP=http://vhreo:50000/
mat: <plant1>=<url1 of
manufacturing-papiservices/
wsdl with virtual host ShopOrderServiceWSSer­
and port>;<plant2>=<url2 of vice;1000=http://
wsdl with virtual host and vhreo2:51038/manufacturing-
port> papiservices/ShopOrderServi­
ceWSService

 Note
Use http for the virtual ad­
dress.

To retrieve the WSDL URL

from SAP ME system, go to

SAP NetWeaver Administrator

Configuration Connectivity

Single Service Administration .

Search for ShopOrderServiceWS.
Choose WSDLs tag to get the URL of
WSDL. Use the virtual host and port
number from Cloud Connector.

8. Save and deploy Initial Parameters.

9. If multiple Cloud Connectors are configured for the same SAP Cloud Integration tenant, then you
should configure the location ID from the Cloud Connector for the following artifacts:
• REO Update ShopOrder Schedule process request
• REO Release ShopOrder Schedule process request
10. Choose Actions Update for the selected artifact and enter the following fields:
• Type
• ENDPOINT_ID
• LOCATION_ID
11. After you have entered the fields, save and deploy these artifacts.
12. Deploy the rest of the artifacts.
• General Message Processor
• REO - Release ShopOrder Schedule - Service
• REO - Update ShopOrder Schedule - Service
• REO - Update ShopOrder Schedule Splitter
13. Go to Overview Manage Integration Content to verify that all the artifacts are started.

3. Configure SAP Business Technology Platform of SAP Digital Manufacturing for execution.

1. To create destinations for integration, under the corresponding tenant go to SAP BTP Cockpit SAP
Digital Manufacturing for execution Connectivity Destinations .

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 383
 2. Create the destination CPI_DESTINATION_IFLMAP.
3. Under Type of Destination, for CPI_DESTINATION_IFLMAP select HTTP.
4. Enter the CPI Runtime URL in URL.
5. Select Internet as Proxy Type.
6. Select BasicAuthentication as Authentication.
7. Enter the User and Password.
8. Create the destination CPI_DESTINATION_TMN for the front-end process.
9. Under Type of Destination for CPI_DESTINATION_TMN, select HTTP.
10. Under URL, enter the URL for CPI Management URL.
11. Under Proxy Type, select Internet.
12. Under Authentication, select BasicAuthentication.
13. Enter the User and Password.
14. The destination data is used by SAP Digital Manufacturing for execution to find the specific SAP Cloud
Integration for integration.
4. Configure SAP Digital Manufacturing for execution
1. In the SAP Digital Manufacturing Fiori Launchpad, choose Execution .
2. Choose Manage Plants.
3. Add or maintain the SAP S/4HANA plant that needs to be supported with SAP Digital Manufacturing
for execution in the Main section of the Manage Plants app.

Properties Description Value

Plant Name The plant name of SAP Digital  Example

Manufacturing for execution.
1000

Description The description of the plant of SAP  Example

Digital Manufacturing for execution.
1000 Plant

Time Zone The time zone of SAP Digital  Example

Manufacturing for execution.
Europe/Berlin

SAP Digital Manufacturing Integration Guide

384 PUBLIC Resource Orchestration Integration
 Properties Description Value

Local If set to Yes, this plant will be  Example

used for integration between SAP
No
Digital Manufacturing for execution
and SAP S/4HANA.

If set to No, this plant will be

used for integration between Re­
source Orchestration in SAP Digital
Manufacturing for execution and
SAP Manufacturing Execution. Or­
der creation and release are not al­
lowed in SAP Digital Manufacturing
for execution.

4. Maintain the SAP S/4HANA plant that needs to be integrated with SAP Digital Manufacturing for
execution in the Integration category of the Manage Business Settings app.

Properties Description Value

Integration Mode The integration mode type that is  Example

supported.
S/4HANA
S/4HANA: Indicates that this plant is
integrated with SAP S/4HANA.

S/4HANA Cloud: Indicates that this

plant is integrated with SAP S/
4HANA Cloud.

Execution Time Zone The time zone in SAP Digital  Example

Manufacturing for execution
America/New York

ERP Time Zone The time zone of SAP S/4HANA  Example

Europe/Berlin

Language The language used in SAP Digital  Example

Manufacturing for execution
English-E

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 385
 Properties Description Value

ERP Destination If S/4HANA is set for Integration  Example

Mode, this field is visible.
ECCCLNT500
Enter the destination name that is
configured in SAP Cloud Integration.

Connectivity Destination

4.2.4 Configuring Master Data for Resource Orchestration in

SAP ME System

This section explains the steps to configure master data relevant to Resource Orchestration in SAP
Manufacturing Execution (SAP ME) system.

1. Logon to the SAP ME system.

2. In the upper-right corner of the Activity Manager screen, choose the site (plant) link to change to a different
site. The Site Selection screen opens. Sites that you are assigned to are displayed.
3. Choose the relevant site/plant.
4. Maintain Resource Types
1. Choose Resource Type Maintenance under Maintenance Product Configuration .
2. Enter a resource type or choose an existing resource type from the list. Enter a brief description
(optional).
3. Choose Save. The resource type is created.

 Note

You can also assign a resource type to a resource. Choose a resource from the list of Available
Resources and move the resource to the Assigned Resources list.

For more information on maintaining resource types in SAP ME, see Resource Type Maintenance.
5. Maintain Resources
1. Choose Resource Maintenance under Maintenance Product Configuration .
2. Enter a name for the resource or choose a resource from the list.
3. Choose the status as Enabled. This indicates that the resource is available.
4. Go to the Resource Type tab to associate a resource with a resource type. Choose the resource type
created in step 4 from the Available Resources Types list and move it to the Assigned Resource Types
list.

 Note

You can associate resources with resource types in either Resource Maintenance or in Resource
Type Maintenance.

5. Choose Save. The resource is created and associated with the resource type.
For more information on maintaining resource in SAP ME, see Resource Maintenance .

SAP Digital Manufacturing Integration Guide

386 PUBLIC Resource Orchestration Integration
 6. Maintain Material Groups
In this step, you assign materials of the same characteristics to a material group.
1. Choose Material Group Maintenance under Maintenance Product Configuration .
2. Enter a material group or choose a material group from the list. Enter a brief description (optional).
3. Choose Save. The material group is created.
For more information on maintaining material groups in SAP ME, see Material Group Maintenance.
7. Maintain Materials
In this step, you assign the material to a material group.
1. Choose Material Maintenance under Maintenance Product Configuration .
2. Enter a material or choose a material from the list.
3. Enter the version.
Select Current Version checkbox so that the version you have added is the considered as the current
version.
4. To assign the material group to the material, go to the Material Group tab. Choose the material group
created in step 6 from the Available Material Groups list and move it to the Assigned Material Groups
list.
5. Choose Save. The material is created and is assigned to a material group.
For more information on maintaining material in SAP ME, see Material Maintenance.
8. Maintain Custom Data
In this step, you create fields that appear Custom Data tab (in Work Center Maintenance) to provide
additional information when defining master data.
1. Choose Custom Data Maintenance under Maintenance Product Configuration .
2. Choose the category as Work Center.
3. Choose Insert New to create a new record. This record displays the sequence, data field and field label.
The sequence displays the order of the custom data.
4. Enter REO_MATERIAL_GROUP for both Data Field and Field Labels fields.
5. Choose Save. The custom data has been created.
For more information on maintaining custom data in SAP ME, see Custom Data Maintenance.
9. Maintain Work Center Records
In this step, you create and change work center records by assigning either resources or work centers to
them. A specific resource can belong to only one work center.
1. Choose Work Center Maintenance under Maintenance Product Configuration .
2. Enter a name for the work center or choose a work center from list.
3. Enter or choose the Standard Value Key. This field is the standard value key associated with a work
center.
4. Select the SFC Can Be Released to This Work Center checkbox to release SFCs to this work center.
5. Choose Insert New to insert a new work center or resource record. The sequence displays the order of
the work center or resources in the work center.
6. Choose the type as resource in the Work Center or Resource field.
7. Choose the resource created in step 5.
8. Go to the Custom Data tab.
9. In the REO_MATERIAL_GROUP data field, add the material group that you have created in step 6.
10. Save the record.
For more information on maintaining work center records in SAP ME, see Work Center Maintenance.
10. Define operations
In this step, you define operation and its attributes.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 387
 1. Choose Operation Maintenance under Maintenance Product Configuration .
2. Enter a name for an operation name or choose an operation from the list.
3. Choose the resource type that you have created in step 4.
4. Enter the ERP Control Key as PP01.
5. Choose the work center that you have created in step 9. Choose the same work center for the ERP
work center as well.
6. Choose Save. The operation is created for resource type and work centers.
You can create multiple operations for different resource types and work centers.
For more information on maintaining operations in SAP ME, see Operation Maintenance.
11. Maintaining Orders
In this step, you define shop orders of different types.
1. Choose Shop Order Maintenance under Maintenance Production Product .
2. Enter a shop order number or choose an existing shop order number.
3. In the Planned Material field, enter the material created in step 7.
4. Enter or choose a planned routing and enter the version of the routing.
5. Enter the Planned Start and Planned Completion dates for the order.
6. In the Build Qty field, enter the build quantity of the material for this shop order.
7. Enter the priority for this shop order, and each SFC released by this shop order. The larger the number,
the higher the priority.
8. Choose Save. The shop order is created.
9. Choose the Shop Order Schedule Report to view the schedule report with the operation details.
For more information on maintaining shop orders in SAP ME, see Shop Order Maintenance.

4.2.5 Maintain Custom Data

Use the Manage Custom Data app to define custom data to be used as characteristic values in production
orders.

Prerequisites

To schedule characteristics-based operations in SAP Digital Manufacturing for resource orchestration using
the Dispatching and Monitoring app you must perform the prerequisites mentioned here:

• You've established integration with SAP S/4HANA system.

• You've created a configurable material for a semi-finished or a finished material that contains the
characteristics and their values in SAP S/4HANA system and before sending it to SAP Digital
Manufacturing:
• You've created characteristics. Use the REO_ prefix for each characteristic's name.

 Example

REO_RED

• You've assigned class type 300 as the material class.

SAP Digital Manufacturing Integration Guide

388 PUBLIC Resource Orchestration Integration
 • You've assigned your characteristics to your classification. Use the REO_ prefix for its name.
• You've created a configurable material. Use the REO_ prefix for its name. Otherwise, you can’t schedule
the order in the Dispatching and Monitoring app.

 Example

REO_CONFIG_MAT_COLOR

• You've assigned your classification to the material.

• You've defined the configuration profile for the configurable material and linked it.

Context

Perform the steps to map and manage REO_ specific data in the shop order category. This allows you to sort
the materials associated with production orders (prefixed with REO_) easily in resource orchestration.

Procedure

1. Launch the SAP Digital Manufacturing application.

2. Go to the Manage Custom Data app.
3. Select the Shop Order custom field definition.
4. Choose Add to create a custom field that represents a characteristic of a configurable material.

 Example

Identify the characteristics of the configurable material and define them as custom data:
• Data Field: Represents characteristics of the material.

 Example

REO_COLOR

• Field Label: UI label displayed for the data field

4.3 Data Engineering Configuration

You can configure the following:

• Data agents, connections, and data replicas for Data Engineering. For more information, see
• Manage Data Agents [page 391]
• Manage Connections [page 391]
• Manage Data Replicas [page 392]

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 389
 • Setup Information.

4.3.1 Data Engineering - An Overview

The concept of Data Engineering (DE) revolves around replicating on-premise data in Cloud. This data is
then available for analysis using the SAP Digital Manufacturing for insights component, covering various
manufacturing use cases, such as consumption of analytical reports at a global scale.

 Note

Presently, this feature is available only in Azure deployments.

Replication of on-premise data in Cloud can be achieved using three apps:

• Manage Data Agents: The data agent queries the source table to get data. You can source data from your
on-premise systems, such as SAP ME, SAP MII, SAP ECC, and SAP S/4HANA. Using this Fiori app, you can
create a new data agent, delete or check the status of existing data agents, download scripts, and copy the
connection string. For more information on why you should download scripts and copy connection strings,
see this topic in the Setup Guide.
• Manage Connections: After setting up a data agent, you need a connection or a bridge, to connect
your source database to a target or destination database. This Fiori app helps you create a connection.
Additionally, you can delete and check the status of existing connections. Click any connection to edit
or change the connection details, and save them as different views. Before saving, you can test your
connection to verify the status (whether Connected or Disconnected). You can also suspend and resume
connections.
• Manage Data Replicas: With the data agent and connection up and running, you must replicate this data on
to a destination table. You can choose how to replica or replicate the source data in the destination table,
using this Fiori app. You can create a new data replica. You can copy or delete an existing data replica. You
can suspend and resume data replicas. The Pipeline Status displays as Completed or In progress. Hover
on each status. A link is displayed. Click the link to get a snapshot of the pipeline status. Clicking Details
provides information on the total and failed runs. Delta Load Triggered, Upload to Cloud, and Insert to
Database show the different stages of the pipeline run. Using Replication Schedule, you can set a schedule
for data replication. The schedule can be set in minutes, hours, or days. These replications happen in
deltas, based on the schedule provided. You can save and activate existing data replicas, by clicking on
them. You can also save and activate newly-created data replicas. On activation, the system displays a
confirmation message, stating that the data replica is activated. Once the data is copied, the Initial Load
Status displays as: N of N rows are copied. Here, N represents the number of rows. You can edit the
activated data replica to include additional filters or accommodate any changes that you make.

Related Information

Manage Data Agents [page 391]

Manage Connections [page 391]
Manage Data Replicas [page 392]
Vision and Business Scenarios

SAP Digital Manufacturing Integration Guide

390 PUBLIC Resource Orchestration Integration
4.3.1.1 Manage Data Agents
You can create, delete, check the status, download the script, and copy the connection string of data agents.

Using SAP Digital Manufacturing, you can connect an on-premise system to a Cloud system.

To achieve this goal, data from on-premise systems needs to be first replicated or copied to Cloud.

You can source data from your on-premise systems like SAP ME, SAP MII, SAP ECC, and SAP S/4HANA.

The data agent queries the source table to get data. This data is then replicated on to a destination table. You
can choose how to model or replicate the source data in the destination table, using the Manage Data Models
app.

When you create a new data agent, the system associates the newly created data agent with a connection
string.

This connection string serves as an input in the shell script to run and complete the installation of the agent.

You can save different variants and check the status of data agents.

You can delete a data agent only if no open connections exist.

Once you have created a data agent, you can directly create a new connection, instead of exiting the Manage
Data Agents app and navigating to the Manage Connections app. Choose Create Connection to directly create a
connection from the Manage Data Agents app.

For more information on configuring and managing data agents, see Setup Information under the Setup Guide
for Data Engineering.

4.3.1.2 Manage Connections

You can create, edit, delete, and check the status of connections.

After the setup of the data agent, you need to create a connection to the source system. You can create these
connections to your databases or files using Fiori apps, such as Manage Connections.

After you create a connection and choose Save to store the connection in Cloud, a copy of this is sent to the
data agent as well.

You can edit and change connection details and save these changes as Views.

Using the Suspend and Resume buttons, you can suspend or resume one or more connections, that are in the
Connected and Disconnected state. Once a connection is suspended, all activated data models associated with
this connection, are also suspended. A warning is issued for this. Likewise, on resumption of a connection, the
connection as well as associated (suspended) data models resume.

 Note

If you want to suspend more than one connection, and if any one of these connections is already in
Suspended state, then it will remain as it is. The same is true with resumption of connections as well.

Once you have created a connection, you can directly create a new data model, instead of exiting the Manage
Connections app and navigating to the Manage Data Models app. Choose Create Data Model to directly create a
data model from the Manage Connections app.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 391
Click any connection with any status (Connected or Disconnected) to edit fields such as Description, Data
Agents, System Type, and so on.

You can verify that the target database is reachable and can be connected, using the Test Connection button.

The following system types are supported:

• SAP ME WIP
• SAP ME ODS
• SAP MII OEE
• SAP ECC
• SAP S/4HANA

The following database types are supported:

• HANA
• Oracle
• SQL Server

 Note

A connection can be deleted only if there are no active data models for it or associated with it.

For more information on configuring and managing connections, see Setup Information under the Setup
Guide for Data Engineering.

4.3.1.3 Manage Data Replicas

You can create, copy, and delete data replicas.

To replicate data, you need to create a data replica. This data replica is a mapping of the source table to the
target table, and contains the data to be replicated or copied.

 Note

The data agent and connection must be up and running to configure the Manage Data Replicas app.

You can select a data source, while acquiring data.

The Create button is a dropdown, with two options: New Data Replica and Bulk Data Replicas. Using the New
Data Replica option, you can create a new data replica. Using the Bulk Data Replicas option, you can create
multiple data replicas, at once. The need to individually create multiple data replicas is therefore eliminated.

You can suspend or resume data replicas, using the Suspend and Resume buttons.

 Note

You cannot suspend certain data replicas, such as those with status New, Deletion Started, Deletion Failed,
and, replicas where the initial load is running. The Suspend feature works only for activated replicas. Once
suspended, you cannot activate or delete a data replica. You can edit and save a suspended data replica. If
you choose Resume, then all the data replicas that are in suspended state are resumed. All operations of
the replica are allowed, once you perform the Resume operation.

SAP Digital Manufacturing Integration Guide

392 PUBLIC Resource Orchestration Integration
You can filter data from the source and set a frequency for the ongoing load.

Using Replication Schedule, you can set a schedule for data replication. The schedule can be set in minutes,
hours, or days. These replications happen in deltas, based on the schedule provided.

On the preview page, you can see the status of initial load and delta load, and the run logs. The Pipeline Status
reflects the latest information on the status and start and end times, related to a data replica. Click any status
to get a snapshot of the pipeline. Choose Details to navigate to the Run Logs Details page. It gives information
on the total and failed runs. Delta Load Triggered, Upload to Cloud, and Insert to Database show the different
stages of the pipeline run.

In case of failed delta loads, an Error Log is generated. Click Error Log to view details.

If you do not want to wait for the normal delta load to bring data, you can always trigger an 'on-demand' delta
load, using the Trigger Now button.

You can terminate an ongoing run (for example:- if the run is taking abnormally long to complete) using the
Terminate Current Run button. This button not only terminates the existing run, but also immediately starts a
new run (That is: A new run is scheduled immediately, but reflects soon after, for example - after a minute).

For more information on configuring and managing data replicas, see Setup Information, under the Setup
Guide for Data Engineering.

SAP Digital Manufacturing Integration Guide

Resource Orchestration Integration PUBLIC 393
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.

SAP Digital Manufacturing Integration Guide

394 PUBLIC Important Disclaimers and Legal Information
SAP Digital Manufacturing Integration Guide
Important Disclaimers and Legal Information PUBLIC 395
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