Integration Guide | PUBLIC
Document Version: 2408–2024-08-24
SAP Digital Manufacturing Integration Guide
© 2024 SAP SE or an SAP aliate 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.............................9
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 ................................15
Business Integration with SAP S/4HANA or SAP ERP............................... 128
Customizing the Integration Scenario...........................................312
Upgrade Information...................................................... 318
2.2 Integration with SAP S/4HANA Cloud.............................................319
Minimum Version Requirements and Supported Scenarios...........................320
Overview Integration with SAP S/4HANA Cloud for Discrete Industries...................321
Overview Integration with SAP S/4HANA Cloud for Process Industries...................322
Technical Integration with SAP S/4HANA Cloud ...................................323
Business Integration with SAP S/4HANA Cloud................................... 350
2.3 Integration with EWM........................................................409
Minimum Version Requirements and Supported Scenarios........................... 410
Connecting to EWM in SAP S/4HANA 1909 to 2020 （Deprecated）.................... 410
Connecting to EWM in SAP S/4HANA 2021.......................................416
Mapping Plants (Plant Conversion)............................................436
2.4 Troubleshooting Overview.....................................................438
Troubleshooting for the Integration with SAP S/4HANA ............................. 439
2.5 Extensibility Information......................................................446
3 Shop Floor Integration......................................................447
3.1 Integration Scenarios........................................................ 447
Digital Twin Conguration...................................................448
Machine Data Integration...................................................448
Production Process Conguration.............................................450
Production Process Execution................................................450
3.2 Integrate with the Production Connector for SAP Digital Manufacturing.....................450
Enable Communication from the Production Connector to the Cloud....................452
Minimum Version Requirements and Supported Scenarios........................... 453
Assignment of Production Connector Role to IAS User Groups.........................453
3.3 Integration with SAP MII......................................................454
2
PUBLIC
SAP Digital Manufacturing Integration Guide
Content
3.4 Troubleshooting - Congure Production Connectivity App...............................458
Connectivity Issues.......................................................458
Internal Server Error...................................................... 459
User Authorization Issues...................................................459
4 Resource Orchestration Integration............................................460
4.1 Overview Characteristics-Based Sequencing........................................460
Integration with SAP S/4HANA...............................................461
4.2 Integration with SAP Manufacturing Execution...................................... 464
Minimum Version Requirements and Supported Scenarios...........................465
Integrating SAP Manufacturing Execution On-Premise to Resource Orchestration (Inbound)
.....................................................................466
Integrating Resource Orchestration to SAP Manufacturing Execution On-Premise (Outbound)
..................................................................... 472
Conguring Master Data for Resource Orchestration in SAP ME System..................478
Maintain Custom Data.....................................................480
4.3 Integration with SAP SuccessFactors Employee Central................................482
Before You Start......................................................... 483
Create a Master Data Integration Instance.......................................484
Create Distribution Models for Cost Center and Workforce Person......................486
Create a Destination for Cost Center and Workforce Person...........................488
Create a Destination for Availability............................................490
Congure SAP Digital Manufacturing for resource orchestration to Retrieve Data............494
Congure SAP Digital Manufacturing for resource orchestration to Use Master Data......... 495
4.4 Data Engineering Conguration.................................................495
Manage Data Agents......................................................496
Manage Connections......................................................497
Manage Data Replicas.....................................................498
5 SAP Digital Manufacturing for edge computing Integration..........................500
5.1 Enable Production Connector to Invoke Edge Services.................................500
5.2 SAP MQTT Broker...........................................................501
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 oor 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
SAP Digital Manufacturing can be integrated with the following business systems:
• SAP ERP
4
PUBLIC
SAP Digital Manufacturing Integration Guide
Introduction
• SAP S/4HANA
• SAP S/4HANA Cloud
• SAP Manufacturing Integration and Intelligence
• Production Connector for SAP Digital Manufacturing
• SAP Overall Equipment Eectiveness Management
• 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 447]
• Resource Orchestration Integration [page 460]
As an extensive capability of SAP Digital Manufacturing, SAP Digital Manufacturing for edge computing
also provides multiple integration scenarios. For more information, see SAP Digital Manufacturing for edge
computing Integration [page 500].
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
specic 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 nd 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 9]
• Minimum Version Requirements and Supported Scenarios for Integration with SAP S/4HANA Cloud [page
320]
• Minimum Version Requirements and Supported Scenarios for Integration with the Production Connector
[page 453]
SAP Digital Manufacturing Integration Guide
Introduction
PUBLIC 5
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.
Overview
The following diagram gives you an overview of the possible integration scenarios between SAP Digital
Manufacturing for execution and its partner systems. It doesn't provide information on the relationships the
dierent partner systems might have with each other.
• Integration with SAP S/4HANA or SAP ERP [page 9]
• Integration with SAP S/4HANA Cloud [page 319]
• Integration with EWM [page 409]
• Integrate with the Production Connector for SAP Digital Manufacturing [page 450]
• Resource Orchestration Integration [page 460]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 7
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]
• Overview Integration with SAP S/4HANA / SAP ERP for Process Industries [page 13]
• Overview Integration with SAP S/4HANA Cloud for Discrete Industries [page 321]
• Overview Integration with SAP S/4HANA Cloud for Process Industries [page 322]
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
Integrated Sys-
tems
Integration with
SAP ERP
Integration with
SAP S/4HANA
Integration with
SAP S/4HANA
Cloud
Integration
with SAP
Manufacturing
Execution
1
Integration with
SAP Extended
Warehouse
Management
2
SAP ERP * *
SAP S/4HANA * *
SAP S/4HANA
Cloud
* *
SAP
Manufacturing
Execution
*
SAP Extended
Warehouse Man-
agement
* * * *
Cloud Connector * * * *
SAP Cloud
Integration
* * * *
•
1
Integration with SAP Manufacturing Execution is limited to Resource Orchestration.
•
2
Integration 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 319]
8
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Integration with SAP Manufacturing Execution [page 464]
Integration with EWM [page 409]
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.
After you've completed the onboarding procedures as described in Onboarding and User Management, you
can continue with the congurations 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 congurations are set up. For more information, see
Technical Integration with SAP S/4HANA or SAP ERP [page 15] and Business Integration with SAP S/4HANA
or SAP ERP [page 128].
Related Information
Minimum Version Requirements and Supported Scenarios [page 9]
2.1.1Minimum 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 versions requested. For more information on the
supported message types and versions, see 3050090
.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 9
Supported Scenarios
Scenario SAP ERP SAP S/4HANA
Production order
Yes Yes
Process order
Yes Yes
Planned order Yes Yes
Material
Yes Yes
Characteristic Yes Yes
Class Yes Yes
Classication Assignment 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
Return inventory
Yes Yes
Scrap inventory
Yes Yes
Use Resource Orchestration for
scheduling
Yes
Yes
Middleware Requirements
• SAP Cloud Integration and Cloud Connector are required as middleware
• SAP Cloud Integration in the Neo environment is supported
10
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Supported IDocs
IDoc SAP ERP SAP S/4HANA
MATMAS03
Yes Yes
MATMAS04
Yes Yes
MATMAS05
Yes Yes
CHRMAS05
Yes Yes
CLSMAS04
Yes Yes
CLFMAS02
Yes Yes
BOMMAT04
Yes No
BOMMAT05
No Yes
LOIROU04
Yes Yes
LOIPRO05 (production and process
orders)
Yes
Yes
LOIPLO02 (planned order) Yes Yes
INVCON02
Yes No
INVCON03
Yes Yes
LOIWCS03
Yes Yes
EQUIPMENT_CREATE02
Yes Yes
PP_SHIFT01
Yes Yes
Note
To nd out more about any limitations or restrictions that could apply to your scenario, see 3379404 .
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 11
2.1.2Overview 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 162]
• Bill of Material Integration [page 149]
• Routing Integration [page 165]
• Production Version [page 152]
• Transferring QM Defect Code Groups and Codes from SAP S/4HANA [page 164]
• Tool Integration [page 168]
• Production Order Integration [page 171]
• Transfer of Floor Stock Data [page 224]
• Material Integration [page 130]
• Production Order Status Conrmation [page 186]
• Inspection Results Recording (Process Order and Production Order) [page 223]
• Congure Inspection Points
• Transfer of Floor Stock Return and Scrap Data [page 231]
• Integration with EWM [page 409]
• Staging Request Upon Order Release
• Material Consumption (Order POD)
• EWM Goods Receipt (Work Center POD)
12
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• EWM Goods Receipt (Order POD)
• Component Removal
• Transferring a Planned Order [page 205]
• Planned Order Integration [page 204]
• Activity Conrmation [page 195]
• Quantity Conrmation [page 196]
• Classication Integration [page 138]
• Conguring a Production Order with a BOM and Routing (Make-to-Stock or Make-to-Order Manufacturing)
[page 174]
• Conguring a Production Order with Serial Numbers [page 176]
• Conguring a Production Order with a Batch Number [page 178]
• Conguring a Production Order with Document Info Records [page 180]
• Conguring a Production Order with Scheduling Information [page 182]
• Transfer of Production Order with Operation-Level Scheduling [page 183]
• Transferring a Production Order with PRT Assignment [page 185]
• Production Order Complete [page 192]
2.1.3Overview 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 13
• Material Integration [page 130]
• Work Center Integration [page 162]
• Bill of Material Integration [page 149]
• Recipe Integration [page 168]
• Production Version [page 152]
• Transferring QM Defect Code Groups and Codes from SAP S/4HANA [page 164]
• Tool Integration [page 168]
• Process Order Integration [page 197]
• Transferring a Process Order with Inspection Lot (type 03) [page 198]
• Transfer of Floor Stock Data [page 224]
• Process Order Status Conrmation [page 200]
• Activity Conrmation [page 203]
• Batch Characteristics Update [page 221]
• Congure Inspection Points
• Transfer of Floor Stock Return and Scrap Data [page 231]
• Staging Request Upon Order Release
• Material Consumption (Order POD)
• Inspection Results Recording (Process Order and Production Order) [page 223]
• Integration with EWM [page 409]
• EWM Goods Receipt (Work Center POD)
• EWM Goods Receipt Cancellation
• Cancelling Goods Issues
14
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• Classication Integration [page 138]
• Quantity Conrmation [page 202]
2.1.4Technical Integration with SAP S/4HANA or SAP ERP
Here are the administrative congurations 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 rewall, an asymmetrical communication
design connects SAP Digital Manufacturing for execution to SAP S/4HANA or SAP ERP.
• Build HTTP Connection [page 30]
• Data Replication Framework [page 36]
• Connect SAP Cloud Integration to SAP Digital Manufacturing [page 66]
• Connect SAP Digital Manufacturing to SAP Cloud Integration [page 87]
• Setting Up the Cloud Connector [page 22]
• Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 106]
• Congure SAP Digital Manufacturing for Outbound Integration [page 108]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 15
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 conrmation
and production scrap conrmation.
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 109].
Note
For more information on the supported message types and needed integration artifacts, see
0003050090
.
Note
Plant names need to be unique across the dierent ERP systems at the client level.
Note
You can check your integration scenario using the Check Integration Conguration functionality provided by
the Integration Message Dashboard app.
After choosing Check Integration Conguration, you select an integration message to start an automated
test of the integration conguration 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 ows, you
can refer to the Integration Flow Design Guidelines. You'll nd 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 workow performance, you can jump right to this topic:
Optimize Performance.
16
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 30]
4. Data Replication Framework [page 36]
5. Prepare Credentials for Initial Parameter Deployment [page 52]
6. Connect SAP Cloud Integration to SAP Digital Manufacturing [page 66]
7. Connect SAP Digital Manufacturing to SAP Cloud Integration [page 87]
8. Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 106]
9. Congure SAP Digital Manufacturing for Outbound Integration [page 108]
10. Enable Direct Communication To SAP S/4HANA [page 109]
Related Information
Asynchronous Communication with SAP Cloud Integration [page 112]
Troubleshooting Overview [page 438]
2.1.4.1 Before You Start
This page shows you the prerequisite steps that must be completed before conguring integration with SAP
S/4HANA or SAP ERP.
Before you start, you must have performed the following steps:
• If you integrate SAP Digital Manufacturing with multiple SAP S/4HANA or SAP ERP, these systems need to
have unique system IDs. Systems are identied at the client level.
• Complete the onboarding process
Note
This includes the conguration 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.
Tip
The change log of the SAP S/4HANA Integration with SAP Digital Manufacturing package is available
here: 3315636 .
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 17
Tip
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 .
• 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 109].
• Upload SSL certicates [page 18]
• Create a Technical User for SAP S/4HANA [page 20]
• Know how to get the SAP Cloud Integration Management URL [page 21]
• Know how to get the SAP Cloud Integration Runtime URL [page 22]
• 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 notication (RMES). For more information, see 2165261
.
Next Steps
• Setting Up the Cloud Connector [page 22]
• Build HTTP Connection [page 30]
• Set Up Data Replication Framework (DRF) [page 36]
• Connect SAP Cloud Integration to SAP Digital Manufacturing [page 66]
• Connect SAP Digital Manufacturing to SAP Cloud Integration [page 87]
• Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP ERP
[page 106]
• Congure SAP Digital Manufacturing for Outbound Integration [page 108]
• Enable Direct Communication To SAP S/4HANA [page 109]
2.1.4.1.1 Upload SSL Certicates
This page shows you how to upload SSL certicates to build the trust between the systems.
The certicate uploading processes mentioned below apply to SAP Cloud Integration in both Neo and Cloud
Foundry environments.
18
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Upload SSL Certicate of SAP Cloud Integration to SAP ERP or SAP S/
4HANA
Download SAP Cloud Integration Certicate
1. Go to the SAP Cloud Integration management URL, which you can nd 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
21].
2. Choose in the address bar to download the SSL certicate of SAP Cloud Integration. Save the certicate
in le format base-64 encoded X.509 (.cer).
Upload Certicate 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 certicate you saved in previous steps to SSL client SSL Client (Standard) node.
Upload SSL Certicate of SAP Digital Manufacturing to SAP Cloud
Integration
Download SAP Digital Manufacturing Certicate
If your SAP Cloud Integration tenant is already using DigiCert Global Root G2, you don't need to follow
the steps belows because SAP Digital Manufacturing also utilizes DigiCert Global Root G2 certication.
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 certicate. Save the certicate in le format base-64
encoded X.509 (.cer).
Upload Certicate to SAP Cloud Integration
For more information, see Importing a Certicate.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 19
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.
7. In the Proles tab, assign SAP_ALL or SAP_NEW to your user.
8. Choose Save.
Results
You have created a technical user for SAP S/4HANA.
20
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 nd the SAP Cloud Integration management URL in the url eld.
Example
https://<Cloud Integration tenant>.it-
<...>.cfapps.<datacenter>sap.hana.ondemand.com
Note
This instance is created during the integration process. For more information, see Create a Service
Instance and Key with client credential authorization [page 62].
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 22]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 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, nd the instance for the Process Integration Runtime service, which has integration-
ow 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 97].
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>imap application.
3. In the Application URLs section, you will see the runtime URL named https://<Cloud Integration tenant>-
imap.avtsbhf.eu1.hana.ondemand.com.
Related Information
How to Get SAP Cloud Integration Management URL [page 21]
2.1.4.2 Setting Up the Cloud Connector
Congure 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
22
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution 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 464]: SAP Digital Manufacturing (resource orchestration) → SAP Cloud
Integration → Cloud Connector → SAP Manufacturing Execution
• Scenario 3 - PPD/Insights/MM2PCo [page 450]: SAP Digital Manufacturing (Production Process
Designer / insights / Production Connectivity Model) → Cloud Connector → Production Connector
2.1.4.2.1 Install Cloud Connector
Find out how to install the Cloud Connector.
Context
The installation les 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 rst time.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 23
2.1.4.2.2 Congure Subaccounts in Cloud Connector
For each SAP Business Technology Platform subaccount that you want to connect with an on-premises
system, congure 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 predened role Cloud Connector Admin or
Administrator, or assign the user to a custom role that includes the scope.
• You have congured 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 congure the rst subaccount and proxy. To do this, on the
initial conguration page look for the proxy settings in
Connector Conguration .
Context
You always have two separate subaccounts: one for SAP Digital Manufacturing and one for SAP Cloud
Integration.
For the following scenarios, congure the Neo or Cloud Foundry subaccount for SAP Cloud Integration in the
Cloud Connector:
• Execution2S4
• REO2ME
For the following scenario, congure 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].
24
PUBLIC
SAP Digital Manufacturing Integration Guide
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 specied 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 nd 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,
dene 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
Congure trust to SAP Digital Manufacturing by dening an allowlist of cloud applications that can use the
Cloud Connector.
Initial Conguration
Cloud Foundry: Add Organization Members Using the Cockpit
Neo: Add Members to Your Subaccount
2.1.4.2.3 Congure 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 conguration, you need to dene 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 dierent 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 specic
on-premise system.
• To communicate with SAP S/4HANA using RFC, follow the instructions at Congure Access Control
(RFC).
Applicable scenario: Execution2S4
• To communicate with SAP S/4HANA, SAP Manufacturing Execution, or the Production Connector
using HTTPS, follow the instructions at Congure Access Control (HTTP).
Applicable scenarios: REO2ME, PPD/Insights/MM2PCo
For the back-end type and principal type system, see the following table:
26
PUBLIC
SAP Digital Manufacturing Integration Guide
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
Java
None
Production Connector Other SAP System None
Note
The virtual host and virtual port can be freely dened. 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 nd detailed instructions at Congure Accessible Resources. In addition, for the required
congurations 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 Prex.
PPD/Insights/MM2PCo URL Path Enter /cloudservices
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 27
Scenario Field Description
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 congure 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 nd
the accessible resource conguration. 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 certicate into the Cloud Connector.
Context
The certicate must be issued for the fully qualied domain name (FQDN) of the machine on which you've
installed the Cloud Connector. The Cloud Connector uses the so-called system certicate for all HTTPS
requests to back-end systems that request or require a client certicate.
28
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Related Information
Install a System Certicate for Mutual Authentication
2.1.4.2.5 Congure User Authentication Against On-
Premise Systems
To secure the communication with an on-premise system, apply dierent 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
106].
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 472].
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 certicate.
Note
Principal propagation is possible but not required from
15.4 SP2 onwards.
The certicate must be issued for the fully qualied domain
name (FQDN) of the machine on which you've installed the
Cloud Connector.
If you use a self-signed certicate, place the public key in the
Trusted store location in the le system of the Production
Connector server:
C:\ProgramData\SAP\ProdCon\CertificateSt
ores\CloudServicesHost\Trusted\certs
You can obtain the public key by choosing
Connector
Conguration ON PREMISE Download certicate in DER
format
.
For more information, see Congure a CA Certicate for
Principal Propagation.
Related Information
Authenticating Users Against On-Premise Systems
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 22].
• Depending on your environment and your preferred authentication method, you've got one of the following
users:
30
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Environment User Password Comment
Cloud Foundry P-User* authorized in SAP
Cloud Integration
P-User password Basic authentication
Cloud Foundry SAP Cloud Integration Cli-
ent ID
SAP Cloud Integration Cli-
ent Secret
Recommended authentica-
tion because no need to
change the password peri-
odically. Same security level
as with basic authentication
Neo
P-User* authorized in SAP
Cloud Integration
P-User password 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to your prole. Under
Personal Info Personal Data , you nd your P-user ID under User ID.
Caution
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 nd your users.
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
• 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 Conguration of RFC Connections
screen.
2. Choose
Edit Create
3. Enter the following general data:
• Destination: Name of the HTTP connection, for example DME_INT
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 31
• Connection Type: G (HTTP Connection to External Server)
4. In the Technical Settings tab, enter data for the elds as follows:
Field Example Description
Target Host <Cloud Integration tenant>-i-
map.abcdef.eu1.hana.ondemand.com
(Neo) or <Cloud
Integration tenant>-abcd000-
rt.cfapps.sap.hana.ondemand.com
(Cloud Foundry)
SAP Cloud Integration runtime URL
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
22].
Note
Do not paste https:// as it is auto-
matically added.
Port 443
Path Prex /cxf/GenericMessageProcessor_00 The service implemented on SAP
Cloud Integration to receive the mes-
sage/IDOC from SAP S/4HANA or
SAP ERP.
Proxy Host Example
proxy.wdf.sap.corp
The proxy host for the external sys-
tem connection.
Proxy Service Example
8080
The proxy service for the external sys-
tem connection.
5. In the Logon & Security tab, activate SSL and complete the following settings for basic or OAuth 2.0
authentication:
Authentication Type
Credentials Certicate
Basic Authentication User and password DFAULT SSL Client (Standard)
Note
SSL needs to be set to Active.
32 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Authentication Type Credentials Certicate
OAuth 2.0 Authentication Client ID and client secret
Note
Enter client ID and client secret
under Basic Authentication as
user and password.
DFAULT SSL Client (Standard)
Note
SSL needs to be set to Active.
6. Choose Connection Test to test the connection between SAP S/4HANA or SAP ERP and SAP Cloud
Integration.
Note
If the General Message Processor 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com
using your email address. Go to Manage my Account
Accounts to nd your users.
Caution
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 Manage my Account Accounts to nd your users.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 33
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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 eld, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predened role) and Developer (predened 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.
34
PUBLIC
SAP Digital Manufacturing Integration Guide
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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com
using your email address. Go to Manage my Account
Accounts to nd your users.
Caution
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 Manage my Account Accounts to nd your users.
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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 Communication with SAP Cloud Integration [page 112].
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 (predened)
PI_Administrator (predened)
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 dene
lter 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).
36
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
General Overview of the Procedure
To use the Data Replication Framework (DRF), you must rst set up ALE communication (Application Link
Enabling), which is the technical basis for data exchange between your systems. You need to dene 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
Note
If you set up the DRF, which is recommended, you don't need to create any distribution model. If you
prefer working only with ALE, then you need the distribution model to control the distribution of IDoc
messages.
After setting up the ALE communication, you can make the necessary congurations for the Data Replication
Framework (DRF) that enables you to send messages in specic 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 congure the following elements in SAP ERP or
SAP S/4HANA:
• Assign business object types to your business system
• Replication model that denes which business objects (for example, production order or work center) are
sent to which 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 specic plant, specic
order type, or specic material.)
Overview Setup Steps
To set up the Data Replication Framework (DRF), perform the tasks described in the following topics:
1. Before You Start [page 38]
2. Create Logical Systems [page 38]
3. Assign a Logical System to a Client [page 39]
4. Dening Outbound Communication in SAP S/4HANA or SAP ERP [page 41]
5. Dene Outbound Messages for Partner Systems [page 42]
6. Dene a Distribution Model [page 44]
7. Assign Business Objects to Your Business System [page 46]
8. Dene Replication Models and Outbound Implementations [page 48]
9. Dene Filter Criteria [page 50]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 37
2.1.4.4.1 Before You Start
Here you nd 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 30].
• The following business functions 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
2.1.4.4.2 Set Up Application Link Enabling (ALE)
2.1.4.4.2.1Create 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 rst represents your SAP S/4HANA or SAP ERP system, the second your SAP Digital
Manufacturing for execution system.
Procedure
Dene the logical systems.
1. Use transaction BD54 and dene the logical system in the cross-client for SAP S/4HANA or SAP ERP.
38
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
Creating a logical system is a cross-client activity, that is, all changes also aect all other clients in the
system. You need the authorization S_TABU_CLI in order to do it.
2. Use transaction BD54 and dene the logical system for SAP Digital Manufacturing for execution.
Add the logical system representing SAP Digital Manufacturing for execution to your ERP system (client) to
ensure 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.
Example
Plant
Order Type
Determ. Method Logical
System Logical System
<Plant number>, for
example, 1010
<Order type>, for ex-
ample, *
Customizing
Creates Logical
System
Logical System rep-
resenting SAP Digital
Manufacturing for
execution, for example
DMETest
6. Choose Save.
Results
You have created two logical systems representing your source and target system.
2.1.4.4.2.2Assign 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 dened a logical system for the SAP S/4HANA or SAP ERP system using transaction BD54. For
more information, see Create Logical Systems [page 38].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 39
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.
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
system
SAP Menu Tools Administration Administration Client Administration
Client Maintenance
3. On the Display View "Clients": Overview screen, choose Edit.
4. Conrm 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 eld, 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 conrm 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.
40
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.4.2.3Dening Outbound Communication in SAP S/
4HANA or SAP ERP
As administrator, you dene 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.
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 dene 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 30].
3. Choose Application/x-sap.idoc and SOAP Protocol.
4. Choose Save.
Results
You have dened a port for outbound communication.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 41
2.1.4.4.2.4Dene Outbound Messages for Partner Systems
As administrator, you dene 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 Proles and assign the logical system
representing SAP Digital Manufacturing for execution to the SAP Digital Manufacturing for execution system.
Moreover, you dene 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.
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 Proles: Outbound Parameters screen, select Pass IDoc Immediately and Cancel Processing
After Syntax Error, and enter data in the following elds:
Field Value
Message Type BOMMAT
Receiver port HCI_DME
Pack. Size 1
Basic type BOMMAT05
Note
HCI_DME ist just a placeholder for the receiver port, which refers to the port for outbound
communication dened in a previous step: Dening Outbound Communication in SAP S/4HANA or
42
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP [page 41]. You can dene the receiver port's name as you please, but make sure that all
message types dened 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
CHRMAS HCI_DME CHRMAS05
CLSMAS HCI_DME CLSMAS04
CLFMAS HCI_DME CLFMAS02
EQUIPMENT_CREATE HCI_DME EQUIPMENT_CREATE02
Note
For more information, see Tool In-
tegration [page 168].
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 43
2.1.4.4.2.5Dene a Distribution Model
As administrator, you need to dene a distribution model in SAP S/4HANA or SAP ERP to control the data
transfer between your system and SAP Digital Manufacturing for execution. If you're implementing the data
replication framework, you don't need to perform this step.
Prerequisites
You have the Administrator role for SAP S/4HANA or SAP ERP.
Context
If you're not implementing the data replication framework (DRF), you need to dene a distribution model
in SAP S/4HANA or SAP ERP to control the data transfer from SAP S/4HANA or SAP ERP to SAP Digital
Manufacturing for execution. The distribution model denes which message types can be sent to SAP Digital
Manufacturing for execution.
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 elds:
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
44 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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
CHRMAS Characteristic
CLSMAS Class
CLFMAS Classication assignment
Note
To add message type EQUIPMENT_CREATE, in step 4, select the model view you created and choose
Add BAPI instead of Add Message Type. Enter the values described in step 4 for Model View, Sender /
Client and Receiver / Server. Select Equipment in Object / Interface and Create in Method.
7. Choose Save.
Results
You have dened a distribution model.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 45
2.1.4.4.3 Set Up Data Replication Framework
2.1.4.4.3.1Assign 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 Dene Custom Settings for Data Replication Dene Technical
Settings
Dene Technical Settings for Business Systems .
2. On the Change View "Dene 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
elds to create a business system:
Field Value
Business System DMESystem
Logical System DMETest (For more information, see Create Logical Sys-
tems [page 38])
46 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Value
RFC Destination DME_INT (For more information, see Build HTTP Con-
nection [page 30])
4. Choose Save.
5. Choose the business system DMESystem you created and double-click Dene 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 DRF_0043 Characteristic
BO Type DRF_0044 Class
BO Type DRF_0011 Class Assignment
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
SAP Digital Manufacturing for execution Integration
PUBLIC 47
2.1.4.4.3.2Dene Replication Models and Outbound
Implementations
As administrator, you dene 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 dene 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 Dene Custom Settings for Data
Replication Dene Replication Models .
3. Choose New Entries and complete the following elds:
Field Example
Replication Model DMEModel
Description DMEModel
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:
48
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Value Description
Outbound Implementation 97_1 Production Order via 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 CLF_CHRMAS Characteristic via IDoc
Outbound Implementation CLF_CLSMAS Class via IDoc
Outbound Implementation CLF_CLFMAS Classication Assignment via IDoc
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 Dene Replication Model in Dialog Structure on the side menu, choose the replication model
and then choose Activate.
Results
You've dened and activated a replication model with its outbound implementations.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 49
2.1.4.4.3.3Dene Filter Criteria
As administrator, you dene lter 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 dene lter criteria for business objects (for
example, production order or material) that belong to a replication model. With these lter 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 specic plant, specic order
type, or specic material.
Note
In this procedure, the values in the value help depend on the Customizing settings. For dierent
parameters, dene 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
system
SAP Menu Cross Application Components Processes and Tools for Enterprise
Applications Master Data Governance Data Replication Dene Filter Criteria
Replication
3. On the Dene 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:
50
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
1st Column 2nd Column 3rd Column Note
Plant is <Plant number>, for ex-
ample, 1010
Choose to create a sec-
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
SAP Digital Manufacturing for execution Integration
PUBLIC 51
Results
You have successfully created the lter criteria for the various objects.
2.1.4.5 Prepare Credentials for Initial Parameter
Deployment
For the deployment of the Initial Parameters integration ow, you can choose between basic
authentication with P-User, OAUTH 2.0 authentication with authorization code, or OAUTH 2.0 client credential
authorization depending on your environment (cloud foundry or neo).
Use
To make sure that all integration ows 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
the following options depending on your environment:
• Basic authentication with your P-user and password (Neo and Cloud Foundry)
• OAUTH 2.0 authorization code authentication based on a service key with grant type authorization code
(Neo) (Recommended)
• OAUTH 2.0 client credential authorization (Cloud Foundry) (Recommended)
In a later step, this security material is needed to congure 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 53]
• OAuth 2.0 Client Credential Authentication for Initial Parameter Deployment (Cloud Foundry) [page 62]
• OAuth 2.0 Authentication with Authorization Code for Initial Parameter Deployment (Neo) [page 57]
52
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 54] or Granting Your
P-User Access to SAP Cloud Integration in Cloud Foundry Environment [page 56].
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 Manage my Account Accounts to nd 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 conguring the Initial Parameters
integration ow 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 elds:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 53
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.
2.1.4.5.1.1Granting 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com using your email address. Go to Manage my Account
Accounts to nd your users.
54
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Caution
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 Manage my Account Accounts to nd your users.
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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 eld, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predened role) and Developer (predened 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
SAP Digital Manufacturing for execution Integration
PUBLIC 55
2.1.4.5.1.2Granting 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com
using your email address. Go to Manage my Account
Accounts to nd your users.
Caution
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 Manage my Account Accounts to nd your users.
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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.
56
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 Communication with SAP Cloud Integration [page 112].
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 (predened)
PI_Administrator (predened)
Results
Your P-user has now access to SAP Cloud Integration.
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 ows 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 congure the Initial Parameters iFlow in SAP
Cloud Integration, so that all integration ows can access all integration parameters.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 57
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 58]
2. Create a Security Material with OAuth 2.0 Authorization Code in SAP Cloud Integration [page 60]
2.1.4.5.2.1Create 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).
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 elds to create client:
58
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 conguring the au-
thorizations.
Authorization Grant
Authorization Code
Condential Do not check this eld.
Skip Consent Screen Do not check this eld.
Redirect URI Application URL of SAP Integration
Cloud
Note
To nd it, go to
Applications Subscriptions
and choose the Application ending with tmn. Add /
itspaces/odata/api/v1/OAuthTokenFromCode
to this URI. You can also nd 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
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 elds:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 59
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.2Create 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
58].
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
the client. The security material, called here PD_DEPLOYER_CLIENT, is needed later to congure the Initial
Parameters integration ow 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.
60
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 elds:
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 nd 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 nd 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 58].
Client Secret
This eld 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.
Results
You've created and authorized a security material with OAuth 2.0 authorization code.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 61
2.1.4.5.3 OAuth 2.0 Client Credential Authentication for
Initial Parameter Deployment (Cloud Foundry)
Use OAuth 2.0 client credential authorization for the deployment of initial parameters in SAP Cloud Integration.
Use
To make sure that all integration ows 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
OAuth2 Client Credentials. 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 congure the Initial Parameters iFlow in SAP
Cloud Integration, so that all integration ows 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 client credential authorization [page 62]
2. Create a Security Material with OAuth 2.0 Client Credential Authentication in SAP Cloud Integration [page
64]
2.1.4.5.3.1Create a Service Instance and Key with client
credential authorization
To enable authentication without user and password in Cloud Foundry environment, you need to create a
service instance and a service key with client credential authorization.
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).
62
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 client credential authorization.
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 elds to create a service instance:
Field
Service Process Integration Runtime
Plan api
Runtime Environment Cloud Foundry
Space Name of your space
Instance Name Instance Name
Note
You can choose a random name.
4. Choose Next and enter the following elds:
Field
Congure instance paramters Form
Roles AuthGroup_TenantPartnerDirectoryCongurator
Grant-types Client Credential
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 elds:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 63
Field
Service Key Name Service Key
Note
You can choose a random name.
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 client credential authorization.
2.1.4.5.3.2Create a Security Material with OAuth 2.0
Client Credential Authentication in SAP Cloud
Integration
Create a security material with OAuth 2.0 client credential authorization 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 client credential authorization in
your SAP Cloud Integration subaccount in SAP BTP cockpit (Cloud Foundry environment). For more
information, see Create a Service Instance and Key with client credential authorization [page 62].
Context
You've created a service key with OAuth 2.0 client credential authorization 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 congure the Initial Parameters integration ow in SAP Cloud Integration. The PD_DEPLOYER_CLIENT
64
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 Client Credentials.
The Create OAuth2 Client Credentials popup opens.
3. Enter the following els:
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.
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.
Client Authentication
Send as Request Header
Scope Leave empty
Content Type application/json
Resource Leave empty
Audience Leave empty
4. Choose Deploy.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 65
Results
You've created and activated a security material with OAuth 2.0 client credential authorization.
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 predened
integration ows (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 congured in SAP Cloud 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 .
You can nd the change log of the SAP S/4HANA Integration with SAP Digital Manufacturing package here:
3315636
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 52].
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 67].
2. OAUTH 2.0 client certicate authorization (x.509). For more information, see Connection with Client
Certicate Authorization (X.509) [page 76].
66
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 authentication for the communication from SAP Cloud Integration to
SAP Digital Manufacturing, you benet 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 congure the relevant
integration ow package in SAP Cloud Integration.
Note
If you're already using client credential authorization, you can switch over from client credential
authorization to OAuth 2.0 client certicate 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 68]
2. Create an OAuth 2.0 Client Credential Security Material [page 69]
3. Congure Inbound Processor iFlow [page 71]
4. Congure Initial Parameters iFlow [page 73]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 67
2.1.4.6.1.1Create 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.
The New Instance or Subscription popup opens.
3. Enter the following elds 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 elds to create a service key supporting client ID / client secret:
68
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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.
2.1.4.6.1.2Create an OAuth 2.0 Client Credential Security
Material
Create a security material named CF_AUTH in SAP Cloud Integration that you need for the conguration of the
integration ow.
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 68].
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 congure the INBOUND_PROCESSOR integration ow in SAP Cloud
Integration.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 69
Procedure
1. Log on to SAP Cloud Integration and go to the Monitor section.
2. Choose the Security Material app.
3. Choose Create, and select User Credentials.
The Create User Credentials popup opens.
4. Complete the following data:
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
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
68].
Password
<clientsecret of service key>
To be found in SAP Digital Manufacturing subaccount.
Note
Here's how to nd 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 nd 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.
70
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.6.1.3Congure Inbound Processor iFlow
You congure 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 workow 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 318].
• 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 69].
Context
In this step, you congure the INBOUND PROCESSSOR integration ow 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 eld. Moreover, you leave the
DMC_PRIVATE_KEY_ALIAS eld 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 conguration 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 certicate 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 workow.
Procedure
1. In SAP Cloud Integration, go to the Discover section.
2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. Choose Copy to make a copy of the integration package.
4. Go to the Design section and choose your package.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 71
5. In the Artifacts tab, search for the INBOUND PROCESSOR integration workow and choose , then
Congure.
The Congure "INBOUND PROCESSOR" popup opens.
6. On the Receiver tab, keep the default parameters.
7. On the More tab, 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 68].
DMC_CREDENTIAL CF_AUTH
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 69].
DMC_PRIVATE_KEY_ALIAS
Leave this eld 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 68].
ENDPOINT_ID 00
8. Choose Save.
9. To deploy the INBOUND PROCESSOR integration workow, choose , then Deploy.
Results
You've congured and deployed the INBOUND PROCESSOR iow.
72
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.6.1.4Congure Initial Parameters iFlow
You congure 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 52].
• You've congured the INBOUND PROCESSOR integration workow. For more information, see Congure
Inbound Processor iFlow [page 71].
Context
With this procedure, you congure the Initial Parameters integration ow in SAP Cloud Integration.
To enable SAP Cloud Integration to write parameters to SAP Cloud Integration, so that all integration ows
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 ow. The rst 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 workow and choose , then Congure.
The Congure "Initial Parameters" popup opens.
4. Enter the following parameters:
Parameter Name Description Value
COMMON_DME_IDENTITY_ZONE_SUBD
OMAIN
The subdomain that allows SAP Cloud
Integration to access web services of
SAP Digital Manufacturing.
Go to the subaccount in the SAP
BTP cockpit that you use to sub-
scribe to SAP Digital Manufacturing
for execution. You can nd the subdo-
main in the General section.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 73
Parameter Name Description Value
COMMON_DME_INT_URL
The URL of the back-end integration-
ms application.
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
display the service key for SAP
Digital Manufacturing Services. You
can nd the URL under the
tag manufacturing-execution-
integration.
Note
Remember to add the prex
https:// to the URL.
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 nd
the URL under the tag uaa and then
url.
ENABLE_PLANT_CONVERSION
Dene if you want to enable plant
conversion function to connect mul-
tiple ERP plants to SAP Digital
Manufacturing.
Enter TRUE to enable this function.
For more information, see Mapping
Plants (Plant Conversion) [page 309].
PID
- DME_Generic_Processing_00
TENANT_CREDENTIALS
The SAP Cloud Integration user
credential created in the Security
Material app.
PD_DEPLOYER_USER or
PD_DEPLOYER_CLIENT
For more information, see Prepare
Credentials for Initial Parameter De-
ployment [page 52].
74 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Parameter Name Description Value
TENANT_URL
SAP Cloud Integration management
URL used for iFlow deployment.
Use the SAP Cloud Integration man-
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 21].
ENABLE_INBOUND_OAUTH
Set ENABLE_INBOUND_OAUTH to
TRUE to use the INBOUND
PROCESSOR iow, which is recom-
mended. If set to TRUE, the rst 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.
TRUE
5. Choose Save.
6. To deploy the Initial Parameters integration workow, choose , then Deploy.
7. Under Monitor Message Processing, check whether the Initial Parameters message has status
Completed.
Note
In SAP Cloud Integration, you've got the following monitoring options:
• Under Manage Integration Content, you can check whether your integration ow has status
Started.
• Under Monitor Message Processing, you can check whether the integration message has status
Completed.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 75
Note
If you're using OAuth 2.0 Authentication with Authorization Code for initial parameter deployment
(PD_DEPLOYER_CLIENT) and if the initial parameter message has status Failed, authorize your
security material again under Manage Security Material and deploy the Initial Parameters
integration ow again.
Results
You've congured and deployed the Initial Parameters iFlow.
2.1.4.6.2 Connection with Client Certicate Authorization
(X.509)
Connect SAP Cloud Integration to SAP Digital Manufacturing using OAUTH 2.0 client certicate 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 certicate.
General Overview of the Procedure
To enable OAUTH 2.0 client certicate 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 certicate that will enable secure communication between the systems. You
upload the x.509 certicate 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 congure the INBOUND_PROCESSOR integration ow and the Initial Parameters in SAP
Cloud Integration.
Overview Setup Steps
To set up OAUTH 2.0 client certicate authentication (X.509) from SAP Digital Manufacturing to SAP Cloud
Integration, perform the tasks described in the following topics:
76
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
1. Before You Start [page 77]
2. Create an X.509 Service Key in SAP Digital Manufacturing [page 77]
3. Create an X.509 Certicate [page 78]
4. Create a Key Pair and Upload the X.509 Certicate File to SAP Cloud Integration [page 79]
5. Create a Security Material with User Credentials in SAP Cloud Integration [page 80]
6. Congure Inbound Processor iFlow [page 82]
7. Congure Initial Parameters iFlow [page 84]
2.1.4.6.2.1Before You Start
This page shows you the prerequisites that are required to connect SAP Cloud Integration to SAP Digital
Manufacturing using an x.509 certicate.
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 certicate les of type .pfx, such as openSSL.
2.1.4.6.2.2Create 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 certicate, you need to create a service key that
supports X.509 credentials in your SAP Digital Manufacturing subaccount.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 77
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 eld.
Note
You can also specify the validity period:
Sample Code
{
"xsuaa": {
"credential-type": "x509",
"x509": {
"validity": 12,
"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 certicate of the current service
key expires.
6. Choose Create.
You've created a service key supporting X.509 credentials.
2.1.4.6.2.3Create an X.509 Certicate
Create an X.509 certicate that's needed for X.509 certicate-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 certicate authorization for your SAP Cloud
Integration instance. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing
[page 77].
• You've software to create certicate les of type .pfx, such as openSSL.
78
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Context
To enable communication between SAP Digital Manufacturing and SAP Cloud Integration using X.509
credentials, you need to create an X.509 certicate 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 eld, which is under the "uaa" tag, and copy the content of the key eld into
a new le of type .pem, for example key.pem, and save it.
5. In the JSON box, go to the certicate eld, which is under the "uaa" tag, and copy the content of the
certicate eld into a new le of type .pem, for example certificate.pem, and save it.
6. Replace the \n characters of the les with line breaks.
For example, you could use this code: awk '{gsub(/\\n/,"\n")}1' key.txt | tee key_new.pem.
7. Create a certicate le 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 le, use this command: openssl pkcs12 -export -out
service.pfx -inkey key.pem -in certificate.pem.
2.1.4.6.2.4Create a Key Pair and Upload the X.509
Certicate File to SAP Cloud Integration
Create a key pair in SAP Cloud Integration and upload the X.509 certicate le 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 certicate with a password. For more information, see Create an X.509 Certicate
[page 78].
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 certicate, you need to create a key pair in SAP
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 79
Cloud Integration and upload the X.509 certicate into the system. Then you need to download the certicate
to your computer to use it later in the integration process.
Procedure
1. In SAP Cloud Integration, go to the Monitor section 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 le, for example service.pfx, by using the Browse function.
6. Enter the password that you've dened for the .pfx le.
7. Choose Add.
8. In the Actions column of the newly created key pair, choose (More) and then Download Certicate.
A certicate 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.5Create 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 certicate
in your SAP Digital Manufacturing. For more information, see Create an X.509 Service Key in SAP Digital
Manufacturing [page 77].
Context
You've created a service key that supports client credentials with x.509 certicate 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.
80
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 data:
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 77].
Password
Leave this eld empty
Repeat Password Leave this eld empty
4. Choose Deploy.
Results
You've created and activated a security material that supports OAuth 2.0 client certicate authorization
(x.509).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 81
2.1.4.6.2.6Congure Inbound Processor iFlow
You congure the INBOUND PROCESSOR iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAUTH 2.0 client certicate authorization (x.509).
Prerequisites
• You've got the Administrator role for SAP Cloud Integration.
• The INBOUND PROCESSOR integration workow 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 318].
• You've created a security material with user credentials supporting OAUTH 2.0 client certicate
authorization. For more information, see Create a Security Material with User Credentials in SAP Cloud
Integration [page 80].
• 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 Certicate File to SAP Cloud Integration [page 79].
Context
In this step, you congure the INBOUND_PROCESSSOR integration ow 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 eld. To use the
OAUTH 2.0 client certicate authentication (x.509), you copy the alias name of the certicate from the Manage
Keystore app in SAP Cloud Integration into the DMC_PRIVATE_KEY_ALIAS eld.
Note
If you're already using client credential authoriziation, you can switch over from client credential
authorization to OAUTH 2.0 client certicate 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. Choose Copy to make a copy of the integration package.
4. Go to the Design section and choose your package.
5. In the Artifacts tab, search for the INBOUND PROCESSOR integration workow and choose , then
Congure.
The Congure "INBOUND PROCESSOR" popup opens.
82
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
6. On the Receiver tab, keep the default parameters.
7. On the More tab, enter the following parameters:
Parameter Value
Type All Parameters
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 77].
DMC_CREDENTIAL CF_AUTH
Enter the name of the security material that you've cre-
ated in SAP Cloud Integration. For more information, see
Create a Security Material with User Credentials in SAP
Cloud Integration [page 80].
DMC_PRIVATE_KEY_ALIAS
DMC_KEY_PAIR
Enter the alias of your certicate from the Manage
Keystore app in SAP Cloud Integration. For more informa-
tion, see Create a Key Pair and Upload the X.509 Certi-
cate File to SAP Cloud Integration [page 79].
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 77].
ENDPOINT_ID
00
8. Choose Save.
9. To deploy the INBOUND PROCESSOR integration workow, choose , then Deploy.
Results
You've congured and deployed the INBOUND PROCESSOR iow.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 83
Related Information
Create a Security Material with User Credentials in SAP Cloud Integration [page 80]
2.1.4.6.2.7Congure Initial Parameters iFlow
You congure the Initial Parameters iFlow in SAP Cloud Integration to connect SAP Cloud Integration to
SAP Digital Manufacturing using OAuth 2.0 client certicate authorization (x.509).
Prerequisites
• You've got the Administrator role for SAP Cloud Integration.
• You've congured the INBOUND PROCESSOR integration workow. For more information, see Congure
Inbound Processor iFlow [page 82].
• You've created a service key supporting OAUTH 2.0 client certicate authorization in SAP Digital
Manufacturing. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing [page
77].
Context
With this procedure, you congure the Initial Parameters integration ow in SAP Cloud Integration.
To enable SAP Cloud Integration to write parameters to SAP Cloud Integration, so that all integration ows
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 ow. The rst 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 workow and choose , then Congure.
The Congure "Initial Parameters" popup opens.
4. Enter the following parameters:
84
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Parameter Name Description Value
COMMON_DME_IDENTITY_ZONE_SUBD
OMAIN
The subdomain that allows SAP Cloud
Integration to access web services of
SAP Digital Manufacturing.
Go to SAP BTP Cockpit (of SAP
Digital Manufacturing for execution)
integration workow, choose , choose
the Execution SaaS tenant, and
you can nd the Subdomain in the
Subaccount Details section.
COMMON_DME_INT_URL integration workow, the URL of the
back-end integration-ms application.
Go to SAP BTP Cockpit (of SAP
Digital Manufacturing for execution)
Subaccounts Services Service
Instances
Service Key . You
can nd the URL under the
tag manufacturing-execution-
integration.
Note
Remember to add the prex
https:// for the URL.
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
nd the URL by choosing the tag url
under the tag uaa.
ENABLE_PLANT_CONVERSION
Dene if you want to enable plant
conversion function to connect mul-
tiple ERP plants to SAP Digital
Manufacturing.
Enter TRUE to enable this function.
For more information, see Mapping
Plants (Plant Conversion) [page 309].
PID
- DME_Generic_Processing_00
TENANT_CREDENTIALS
The user credential created in the
Security Material app.
PD_DEPLOYER_USER or
PD_DEPLOYER_CLIENT
For more information, see Prepare
Credentials for Initial Parameter De-
ployment [page 52].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 85
Parameter Name Description Value
TENANT_URL
SAP Cloud Integration management
URL used for iFlow deployment.
Use the SAP Cloud Integration man-
agement URL in the email you re-
ceived after successful SAP Cloud
Integration tenant provisioning. If
you'ven't access to this mail, see How
to Get SAP Cloud Integration Manage-
ment URL [page 21].
ENABLE_INBOUND_OAUTH
Set ENABLE_INBOUND_OAUTH
to TRUE to use the
INBOUND_PROCESSOR iFlow, which is
recommended. If set to TRUE, the
rst three parameters at the top of the
table disappear.
Note
The default setting is FALSE.
TRUE
5. Choose Save.
6. To deploy the Initial Parameters , then Deploy.
7. Under Monitor Message Processing, check whether the Initial Parameters message has status
Completed.
Tip
In SAP Cloud Integration, you've got the following monitoring options:
• Under Manage Integration Content, you can check whether your integration ow has status
Started.
• Under Monitor Message Processing, you can check whether the integration message has status
Completed.
Tip
If you're using OAuth 2.0 Authentication with Authorization Code for initial parameter deployment
(PD_DEPLOYER_CLIENT) and if the initial parameter message has status Failed, authorize your
security material again under Manage Security Material and deploy the Initial Parameters
integration ow again.
Results
You've congured and deployed the Initial Parameters iFlow.
86
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.7 Connect SAP Digital Manufacturing to SAP Cloud
Integration
To enable communication from SAP Digital Manufacturing to SAP Cloud Integration, you congure destinations
and choose an authentication method.
Use
To enable communication from SAP Digital Manufacturing to SAP Cloud Integration, you need to congure
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 87]
• Connection with Client Credential Authentication in Neo Environment [page 92]
• Connection with Client Credential Authentication in Cloud Foundry Environment [page 94]
• Connection with X.509 certicate-based Authorization in Cloud Foundry Environment [page 98]
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 89] or Granting Your P-User Access to SAP
Cloud Integration in Cloud Foundry Environment [page 91].
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 Manage my Account Accounts to nd your users.
• You've got the SAP Cloud Integration runtime URL. For more information, see How to Get SAP Cloud
Integration Runtime URL [page 22].
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 87
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 21].
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 congure
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 specic methods for the Neo and SAP
Cloud Integration environment. For more information, see Connection with Client Credential Authentication
in Neo Environment [page 92] or Connection with Client Credential Authentication in Cloud Foundry
Environment [page 94].
Note
The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workows 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. Log on to SAP BTP cockpit of SAP Digital Manufacturing and choose
Connectivity Destinations in
the side menu bar.
2. Choose Create Destination and enter the following elds to create two SAP Cloud Integration destinations.
88
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field
CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN
Name CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN
Type HTTP HTTP
URL Enter the SAP Cloud Integration run-
time URL. The part to enter here ends
with .com. For example, https://
<Cloud Integration
tenant><...>ondemand.com.
For more information, see above in the
prerequisites section.
Enter the SAP Cloud
Integration management URL.
The part to enter here ends
with .com. For example, https://
<Cloud Integration
tenant><...>ondemand.com.
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.1Granting 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com
using your email address. Go to Manage my Account
Accounts to nd your users.
Caution
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 Manage my Account Accounts to nd your users.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 89
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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 eld, enter your P-User ID.
5. Assign the following roles to the member: Administrator (predened role) and Developer (predened 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.
90
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.7.1.2Granting 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 nd 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 prole, under
Accounts, you nd your P-user ID.
• Log on to your account at www.sap.com
using your email address. Go to Manage my Account
Accounts to nd your users.
Caution
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 Manage my Account Accounts to nd your users.
If you get errors related to your credentials or the authorization, you can refer to 3085908 .
Context
To enable basic authentication, you need to grant your P-user access to SAP Cloud Integration rst.
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 91
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 Communication with SAP Cloud Integration [page 112].
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 (predened)
PI_Administrator (predened)
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 22].
Example
For SAP Cloud Integration in Neo environment, the URL is https://<Cloud Integration
tenant>-iflmap.avtsbhf.eu1.hana.ondemand.com.
92
PUBLIC
SAP Digital Manufacturing Integration Guide
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 21].
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 Workows 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
dene 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_<client ID of ifmap> and oauth_client_<client ID
of tmn> by choosing Show Assignments, for example oauth_client_123456-a123-a123-a123-
a12345678.
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 93
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 Create Destination and enter the following elds 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-
time URL.
For example: https://<Cloud
Integration tenant>-
iflmap.avtsbhf.eu1.hana.o
ndemand.com.
Enter the SAP Cloud Integration man-
agement URL.
For example: https://<Cloud
Integration tenant>-
tmn.avt.eu1.hana.ondemand
.com
Proxy Type
Internet Internet
Authentication OAuth2ClientCredentials OAuth2ClientCredentials
Client ID Enter the <client ID of imap> that's
noted down in Step 2.
Enter the <client ID of tmn> that's
noted down in Step 2.
Client Secret Enter the secret you used to register
clients in Step 2.
Enter the secret you used to register
clients in Step 2.
Token Service URL Type Select Dedicated. Select Dedicated.
Token Service URL Enter the token endpoint that's noted
down in Step 1.
Enter the token endpoint that's noted
down in Step 1.
Token Service User Enter the same value as the one en-
tered in the Client ID eld.
Enter the same value as the one en-
tered in the Client ID eld.
Token Service Password Enter the secret you used to register
clients in Step 2.
Enter the secret you used to register
clients in Step 2.
9. Choose Save.
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 22].
94
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 21].
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 rst instance is used for the IFLMAP destination and requires the integration-
ow 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 97].
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 Workows 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 Services
Instances and Subscriptions to nd 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 Create Destination and enter the following elds to create two SAP Cloud Integration destinations.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 95
Field
CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN
Name CPI_DESTINATION_IFLMAP CPI_DESTINATION_TMN
Type HTTP HTTP
URL Enter the SAP Cloud Integration run-
time URL.
For example: https://<Cloud
Integration tenant>.it-
accd002-
rt.cfapps.sap.hana.ondemand.c
om
Enter the SAP Cloud Integration man-
agement URL.
For example: https://<Cloud
Integration tenant>.it-
accd002.cfapps.sap.hana.ondem
and.com
Proxy Type
Internet Internet
Authentication OAuth2ClientCredentials OAuth2ClientCredentials
Client ID Enter the <clientid of
Service key> of instance 1, which
has the integration-ow service plan.
Enter the <clientid of
Service key> of instance 2, which
has the api service plan.
Client Secret Enter the <clientsecret of
Service key> of instance 1, which
has the integration-ow service plan.
Enter the <clientsecret of
Service key> of instance 2, which
has the api service plan.
Token Service URL Type Select Dedicated. Select Dedicated.
Token Service URL Enter the <tokenURL of
Service Key>/oauth/token,
taken from the service key of instance
1, which has the integration-ow serv-
ice plan.
Enter the <tokenURL of
Service Key>/oauth/token,
taken from the service key of instance
2, which has the api service plan.
Related Information
Creating Service Instance and Service Key for Inbound Authentication
96
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.7.3.1Create 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 rst one, where integration-ow 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-ow
Runtime Environment Cloud Foundry
Space Name of your subaccount's space
Instance Name Name
5. Choose Next.
6. Under Congure instance parameters, enter the following parameters:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 97
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
• MessagePayloadsRead
If you want to use the CPI Async Mode, there a some additional roles required. For more information, see
Asynchronous Communication with SAP Cloud Integration [page 112].
2.1.4.7.4 Connection with X.509 certicate-based
Authorization in Cloud Foundry Environment
Connect SAP Digital Manufacturing to SAP Cloud Integration using X.509 certicate-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 certicate.
98
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
General Overview of the Procedure
To enable X.509 certicate-based communication from SAP Digital Manufacturing to SAP Cloud Integration,
you need to create a service key in SAP Digital Manufacturing and create a certicate that will enable secure
communication between the systems. You upload the x.509 certicate 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 certicate-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 99]
2. Create an X.509 Service Key in SAP Digital Manufacturing [page 100]
3. Create an X.509 Certicate [page 101]
4. Create a Key Pair and Upload the X.509 Certicate File to SAP Cloud Integration [page 102]
5. Create Instances with an X.509 Service Key in your SAP Cloud Integration subaccount [page 103]
6. Create Destinations in SAP Digital Manufacturing [page 104]
2.1.4.7.4.1Before You Start
This page shows you the prerequisites that are required to connect SAP Digital Manufacturing to SAP Cloud
Integration using an x.509 certicate.
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 certicate les of type .pfx, such as openSSL.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 99
2.1.4.7.4.2Create 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 certicate, 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 eld.
Note
You can also specify the validity period, for example:
Sample Code
{
"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 certicate of the current service
key expires.
100
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
6. Choose Create.
You've created a service key supporting X.509 credentials.
2.1.4.7.4.3Create an X.509 Certicate
Create an X.509 certicate that's needed for X.509 certicate-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 certicate authorization for your SAP Cloud
Integration instance. For more information, see Create an X.509 Service Key in SAP Digital Manufacturing
[page 100].
• You've software to create certicate les 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 certicate 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 eld, which is under the "uaa" tag, and copy the content of the key eld into
a new le of type .pem, for example key.pem, and save it.
5. In the JSON box, go to the certicate eld, which is under the "uaa" tag, and copy the content of the
certicate eld into a new le of type .pem, for example certificate.pem, and save it.
6. Replace the \n characters of the les with line breaks.
For example, you could use this code: awk '{gsub(/\\n/,"\n")}1' key.txt | tee key_new.pem.
7. Create a certicate le of type .pfx, for example service.pfx, combining key.pem and
certificate.pem, and assign a password to it.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 101
If you're using OpenSSL to create the .pfx le, use this command: openssl pkcs12 -export -out
service.pfx -inkey key.pem -in certificate.pem.
2.1.4.7.4.4Create a Key Pair and Upload the X.509 Certicate
File to SAP Cloud Integration
Create a key pair in SAP Cloud Integration and upload the X.509 certicate le 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 certicate with a password. For more information, see Create an X.509 Certicate
[page 101].
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 certicate, you need to create a key pair in SAP
Cloud Integration and upload the X.509 certicate into the system. Then you need to download the certicate
to your computer to use it later in the integration process.
Procedure
1. In SAP Cloud Integration, go to the Monitor section 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 le, for example service.pfx, by using the Browse function.
6. Enter the password that you've dened for the .pfx le.
7. Choose Add.
8. In the Actions column of the newly created key pair, choose (More) and then Download Certicate.
A certicate of type .cer has been created, for example dmc_service.cer, and downloaded to your
computer. You need it for the next step.
102
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.7.4.5Create 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 certicate le of type .cer that you've downloaded from SAP Cloud Integration. For more
information, see Create a Key Pair and Upload the X.509 Certicate File to SAP Cloud Integration [page
102].
Context
To set up the X.509 certicate-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 rst one, where integration-ow 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-ow
Runtime Environment Cloud Foundry
Space Name of your subaccount's space
Instance Name Name
5. Choose Next.
6. Under Congure instance parameters, enter the following parameters:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 103
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 Certicate.
13. Under External Certicate, paste the content of the certicate le 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.6Create 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 certicate of type .pfx. For more information, see Create an X.509 Certicate [page 101].
Context
To set up the X.509 certicate-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.
Note
The CPI_DESTINATION_TMN destination is a prerequisite for the Manage Integration Workows app as
well as for the Fetch CPI Logs functionality available in the Integration Message Dashboard app. For more
information, see Integration Message Dashboard.
104
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Procedure
1. In SAP BTP cockpit, go to your SAP Digital Manufacturing subaccount.
2. Under Destinations, choose Certicates and upload the .pfx le, for example service.pfx to the system.
3. Choose Create 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 Conguration enter the following values:
Field
CPI_DESTINATION_IFLMA
P CPI_DESTINATION_TMN
Name CPI_DESTINATION_IFLMA
P
CPI_DESTINATION_TMN
Type HTTP HTTP
Description Description Description
URL SAP Cloud Integration run-
time URL to be found in
the SAP Cloud Integration
subaccount under Instances
in the Credentials column.
Choose the Key that be-
longs to your instance with
integration-ow plan. Under
url, you nd the runtime
URL.
SAP Cloud Integration man-
agement URL to be found
in the SAP Cloud Integration
subaccount under Instances
in the Credentials column.
Choose the Key that be-
longs to your instance with
API plan. Under url, you nd
the management 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
your certicate le, for ex-
ample service.pfx.
To be found under clientid in
your certicate le, for ex-
ample service.pfx.
Token Service Key Store
Location
Choose your certicate le,
for example service.pfx.
Choose your certicate le,
for example service.pfx.
Token Service Key Store
Password
Enter the password that
you dened for your cer-
ticate le, for example
service.pfx.
Enter the password that
you dened for your cer-
ticate le, for example
service.pfx.
Token Service URL Type
Dedicated Dedicated
Token Service URL To be found under tokenurl
in the certicate.
To be found under tokenurl
in the certicate.
Token Service User
Token Service Password
5. Choose Save.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 105
2.1.4.8 Set Up Connection Between SAP Cloud Integration,
Cloud Connector, and SAP S/4HANA or SAP ERP
Congure 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 20].
• 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 congure
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
Congure the Cloud Connector
1. Initial conguration
After installing and starting the Cloud Connector, log on to the administration UI and perform the required
conguration to make your Cloud Connector operational. For more information, see Initial Conguration.
2. Add and connect your SAP Cloud Integration subaccount to the Cloud Connector. For detailed procedures,
see Congure Subaccounts in Cloud Connector [page 24].
3. Add system mapping to SAP S/4HANA or SAP ERP and congure access control. For more information,
see Congure 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.
106
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2. Choose Create Destination, and enter the following elds to create the destination:
Name Type Proxy Type User Password
Authorization
Type Location ID
Enter a desti-
nation name.
Note
You use
this desti-
nation
name later
in the
Manage
Business
Settings
app in SAP
Digital
Manufactu
ring.
RFC
OnPremise Enter the name
of your techni-
cal user to ac-
cess SAP S/
4HANA / SAP
ERP.
Enter the pass-
word to access
SAP S/
4HANA / SAP
ERP.
CONFIGURED_
USER
If you've main-
tained a loca-
tion ID in the
Cloud Connec-
tor, enter the
location ID
here.
3. Add the following Additional Properties:
Property Description Value
jco.client.ashost The Virtual Host of SAP S/4HANA /
SAP ERP dened in the Cloud Con-
nector
Example
<virtual host>
jco.client.client The client number of SAP S/4HANA /
SAP ERP
Example
100
jco.client.lang The language of SAP S/4HANA / SAP
ERP
Example
EN
jco.client.sysnr The system number of SAP S/
4HANA / SAP ERP
Example
22
jco.destination.pool_capacity The connection number Example
5
4. Check the availability of the destination connection.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 107
2.1.4.9 Congure SAP Digital Manufacturing for Outbound
Integration
You need to make congurations 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. Dene 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 dened in SAP S/4HANA that you want to
integrate with SAP Digital Manufacturing.
3. Complete the elds on the Create Plant screen.
4. Choose the Manage Business Settings app and complete the elds. Use the destination name that
you've dened in your SAP Cloud Integration subaccount in SAP BTP cockpit. (For more information,
see Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP S/4HANA or SAP
ERP [page 106].)
For more information about the elds, see Manage Plants and Manage Business Settings.
2. Dene 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.
108
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.10Enable 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 dierent 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.
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 .
• Released by MES (RMES)
You can communicate the release of an order in SAP Digital Manufacturing to your integrated SAP S/
4HANA system. For this scenario, you need to use the following collaboration directives / links in the
Manage Collaboration Links app:
• COLLABORATION_ORDER_RELEASE_PI and ERP_SET_ORDER_STATUS_TO_RMES for process orders
• COLLABORATION_ORDER_RELEASE_DI and ERP_SET_ORDER_STATUS_TO_RMES for production
orders
You need to activate the API_PRODUCTION_ORDER_2_SRV or API_PROCESS_ORDER_2_SRV API in SAP
S/4HANA.
You need to activate the Direct Access SAP S/4 HANA switch of your collaboration directive in the Manage
Collaboration Directives app.
• Order Discard
When you discard an order in the Manage Orders app, the order status is updated to DISC in your SAP
S/4HANA. For this scenario, you need to use the following collaboration directives / links in the Manage
Collaboration Links app:
• COLLABORATION_ORDER_DISCARD_PI and ERP_SET_ORDER_STATUS_TO_DISC for process orders
• COLLABORATION_ORDER_DISCARD_DI and ERP_SET_ORDER_STATUS_TO_DISC for production
orders
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 109
You need to activate the Direct Access SAP S/4 HANA switch of your collaboration directive in the Manage
Collaboration Directives app.
• Defect Recording
When you log nonconformances with the Direct Access SAP S/4Work Center POD, the defect recording can
be transferred to SAP S/4HANA. For this scenario, you need to use the following collaboration directives /
links in the Manage Collaboration Links app:
• COLLABORATION_DEFECT_RECORD and ERP_DEFECT_RECORD (ODATA V2) require SAP 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. For this scenario, you need to use the
collaboration directive ERP_CONSOLID_INV_READ_OP for ERP together with collaboration link
COLLABORATION_CONSOLID_INV_READ_ERP_OP in the Manage Collaboration Links app.
You need to activate the Direct Access SAP S/4 HANA switch of your collaboration directive in the Manage
Collaboration Directives app.
If your integration scenario involves plant mapping (plant conversion), refer to 3419986
.
• 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 and collaboration link COLLABORATION_FETCH_DEFECT_CODE with
the Direct Access SAP S/4HANA ag set to O (=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 ag 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 using the
Defect Code and Code Group API (/API_DEFECTCODE_SRV/A_DefectCodeGroup). For more information,
see Defect Code and Code Group - Read
.
• 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 ag 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.
110
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Procedure
1. Dene the destination name.
Go to the Manage Business Settings app to nd the specic 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 dierent 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. In SAP BTP cockpit, log on to your SAP Digital Manufacturing subaccount 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>
Related Information
How to Enable OData Services in SAP S/4HANA
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 111
2.1.4.11Asynchronous Communication with SAP Cloud
Integration
Learn how to enable asynchronous communication with SAP Cloud Integration (Cloud Foundry environment)
using the CPI Async mode. Using this mode, you benet 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 15].
• 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:
• DataStoresAndQueuesRead
• DataStoresAndQueuesDelete
• DataStorePayloadsRead
For more information, see Granting Your P-User Access to SAP Cloud Integration in Cloud Foundry
Environment [page 56] and Working with Role Collections.
• 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
You need to update your service instance afterwards. For more information, see Updating a Service
Instance and Create Instances in SAP Cloud Integration Subaccount [page 97].
• You've deployed the following integration artifacts from your SAP S/4HANA Integration with SAP Digital
Manufacturing 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 for parallel processing or into the request JMS queue for sequential processing
depending on the message type.
• Async Request Consumer Parallel Adaptor
This iFlow consumes SAP Digital Manufacturing request messages that come from the JMS queue that
handles the messages that can be processed in parallel. The adaptor transfers the messages to the
Async Request Consumer.
• Async Request Consumer Sequential Adaptor
This iFlow consumes SAP Digital Manufacturing request messages that come from the JMS queue that
handles the messages that need to be processed sequentially. The adaptor transfers the messages to
the Async Request Consumer.
• Async Request Consumer
This iFlow gets the request message from the JMS request queue through the Async Request
Consumer Sequential Adaptor or the Async Request Consumer Parallel Adaptor and
112
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 Adaptor
This iFlow processes the response messages coming from the JMS queue and transfers them to the
Async Request Consumer. It doesn't distinguish between messages that are processed in parallel
and messages that are processed sequentially.
• Async Response Consumer
This iFlow consumes the response message from the response JMS queue through the Async
Response Consumer Adaptor and sends the response to SAP Digital Manufacturing.
If your business case requires a modication of the default settings, see Overview Advanced CPI Async
Settings [page 115].
For information on the supported message types, see 3050090 .
For information on the supported collaboration links and directives, see Manage Collaboration Links.
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[].
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 conrms the reception of the integration message back to SAP Digital Manufacturing. In the Integration
Message Dashboard of SAP Digital Manufacturing, the status of the integration message changes from In
Process to Delivered.
In SAP Cloud Integration, the Request Producer iFlow determines whether the message requires parallel
or sequential processing and sends the messages to the JMS request queue for parallel processing
(SAP_DM_INT_REQ_P_00) or to the JMS request queue for sequential processing (SAP_DM_INT_REQ_S_00).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 113
The message is stored in the queue until it's called by the Request Consumer iFlow (asynchronous processing)
through the parallel adaptor or the sequential adaptor. 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 response to the JMS response queue
(SAP_DM_INT_RESP_00). The Response Consumer iFlow retrieves the message from the Response JMS
Queue through the response consumer adaptor and sends the response to SAP Digital Manufacturing. Then,
the message status in the Integration Message Dashboard changes to Completed or Failed.
When transferring data from SAP Digital Manufacturing to the integrated ERP system, SAP Cloud Integration
(CPI) distinguishes between messages that need to be processed sequentially and messages that can be
processed in parallel. This distinction is necessary to meet the needs of the business process.
Example
Quantity conrmations require sequential processing. The order in which the messages are processed is
important because all quantity conrmations must be processed by the ERP system before the order can
be closed.
Example
The synchronisation of inspection results can be handled in parallel. Here, the order in which the messages
are processed in SAP Cloud Integration (CPI) and sent to the integrated ERP system doesn't matter.
This distinction between messages that are processed sequentially or in parallel isn't made for the
communication from the integrated ERP system to SAP Digital Manufacturing.
After modifying your integration setup as described in the prerequisites, you need to activate the CPI Async
mode for each message individually, 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.
For information on the integration messages that support the CPI Async mode and the corresponding
collaboration links and directives, see 3050090
and Manage Collaboration Links.
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
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.
114
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 124].
Related Information
Overview Advanced CPI Async Settings [page 115]
Increasing the CPI Async Performance [page 121]
Increasing the Number of JMS Queues [page 122]
2.1.4.11.1Advanced CPI Async Settings
2.1.4.11.1.1Overview Advanced CPI Async Settings
Learn more about how to congure the integration artifacts needed for an asynchronous connection to SAP
Cloud Integration (Cloud Foundry).
If the standard settings of the following integration artifacts don't suit your business needs, you'll nd some
information here on the key parameters that can be modied.
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 Congure option for the artifact:
• Retention Threshold for Alerting (in d)
Enter the time period (in days) by which the messages have to be fetched. The default value is 1.
• Expiration Period (in d)
Enter the time period (in days) by which the messages have to be fetched. Specify a time period for
expiration period that is no less than the number of days entered for the Retention Threshold for Alerting (in
d). The recommendation is to use at least twice the retention threshold. The default is set to 30.
• NonSequenceRequestQueueCount
Enter the number of queues for parallel processing. The default value is 1. For more information, see JMS
Resource and Size Limits
.
If you increase the number of JMS queues for parallel processing, you also need to increase this counter.
Note
If the NonSequenceRequestQueueCount value is smaller than the number of queues, the additional
queues won't receive messages. If the NonSequenceRequestQueueCount value is larger than the
number of queues, you will get an error: 400 Queue Not Found.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 115
• SequenceRequestQueueCount
Enter the number of queues for sequential processing of messages. The default value is 1.
For more information, see JMS Resource and Size Limits .
If you increase the number of JMS request queues for sequential processing, you also need to increase this
counter.
Note
If the SequenceRequestQueueCount value is smaller than the number of queues, the additional queues
won't receive messages. If the SequenceRequestQueueCount value is larger than the number of
queues, you will get an error: 400 Queue Not Found.
To know more about these settings, see Congure the JMS Receiver Adapter.
JMS Request Queue for Parallel Processing
In SAP Cloud Integration, you nd the JMS Request Queue (SAP_DM_INT_REQ_P_00) in your SAP S/4HANA
Integration with SAP Digital Manufacturing package as part of the Async Request Consumer Parallel Adaptor.
You can modify the following settings:
• Queue Name
The default queue is SAP_DM_INT_REQ_P_00. If you create additional queues, use the same name but
increase the counter at the end continuously: _01, _02, etc. The name for the second queue for parallel
processing is SAP_DM_INT_REQ_P_01.
• Number of Concurrent Processes
The number of concurrent processes for each worker node. The recommended value depends on the
number of worker nodes, the number of queues on the tenant, and the incoming load. Make sure to enter a
value that is as small as possible (1-5) because JMS resources are limited. The default value is 1.
• Retry Interval
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
• Exponential Backo
This setting makes sure that the retry interval is doubled after each unsuccessful retry. Therefore, the
receiver back end isn't called every minute if it's unavailable for a longer time period.
• Maximum Retry Interval
This value denes the maximum time between two retries if exponential backo is used. It's recommended
to keep the 16 minutes or even increase it if this is compatible with your scenario.
• Dead-Letter Queue
Don't deselect this setting. For more information, see Congure the JMS Sender Adapter and Dead Letter
Handling in JMS Adapter
.
Example
To illustrate the retry mechanism, the following values have been dened:
• Retry Interval is 3
• Exponential Backo is selected
• Maximum Retry Interval is 16 min
• RetryCount is 6 (You make this setting in the conguration section of the Async Request Consumer
artifact.)
116
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Given these settings, retry will happen after 3 min, 6 min, 12 min, 16 min, 16 min, and 16 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 Congure the JMS Sender Adapter.
JMS Request Queue for Sequential Processing
In SAP Cloud Integration, you nd the JMS Request Queue (SAP_DM_INT_REQ_S_00) in your SAP S/4HANA
Integration with SAP Digital Manufacturing package as part of the Async Request Consumer Sequential Adaptor.
You can modify the following settings:
• Queue Name
The default queue is SAP_DM_INT_REQ_S_00. If you create additional queues, use the same name but
increase the counter at the end continuously: _01, _02, etc. The name for the second queue for parallel
processing is SAP_DM_INT_REQ_S_01.
• Number of Concurrent Processes
The number of concurrent processes for each worker node. The recommended value depends on the
number of worker nodes, the number of queues on the tenant, and the incoming load. Make sure to enter a
value that is as small as possible (1-5) because JMS resources are limited. The default value is 1.
• Retry Interval
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
To know more about these settings, see Congure the JMS Sender Adapter.
Async Request Consumer Parallel Adaptor
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 Congure option for the artifact:
• Number of Concurrent Processes
The number of concurrent processes for each worker node. The recommended value depends on the
number of worker nodes, the number of queues on the tenant, and the incoming load. Make sure to enter a
value that is as small as possible (1-5) because JMS resources are limited.
Note
The default number of concurrent processes is 1. You should only increase this number if your scenario
requires parallel processing. However, keep in mind that when processing large messages, having a
high number of concurrent processes can cause out of memory problems.
• Retry Interval (in min)
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
• Maximum Retry Interval (in min)
Enter a value for the maximum amount of time to wait before retrying message delivery. The minimum
value is 10 minutes. The default value is set to 16 minutes because retry count default value is 5 (Retry after
1 min, 2, min, 4 min, 8 min, 16 min).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 117
Async Request Consumer Sequential Adaptor
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 Congure option for the artifact:
• Retry Interval (in min)
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
• Maximum Retry Interval (in min)
Enter a value for the maximum amount of time to wait before retrying message delivery. The minimum
value is 10 minutes. The default value is set to 16 minutes, because retry count default value is 5 (Retry
after 1 min, 2, min, 4 min, 8 min, 16 min).
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 Congure option for the artifact:
• RetryCount
Enter a value for the maximum times to retry message delivery. The default value is 5.
Note
Until the retry has been successful, the message remains in status Delivered in the Integration Message
Dashboard.
To know more about these settings, see Congure 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 Congure option for the artifact:
• Retention Threshold for Alerting (in d)
Enter the time period (in days) by which the messages have to be fetched. The default value is 1.
• Expiration Period (in d)
Enter the time period (in days) by which the messages have to be fetched. Specify a time period for
Expiration Periodwhich is no less than the number of days entered for the Retention Threshold for Alerting.
The recommendation is to use at least twice the retention threshold. The default is set to 30.
• ResponseQueueCount
Enter the count of response queue. The default is set to 1.
If you increase the number of JMS response queues, you also need to increase this counter.
Note
If the ResponseQueueCount value is smaller than the number of queues, the additional queues won't
receive messages. If the ResponseQueueCount value is larger than the number of queues, you will get
an error: 400 Queue Not Found.
118
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
To know more about these settings, see Congure the JMS Receiver Adapter.
JMS Response Queue
In SAP Cloud Integration, you nd the JMS Response Queue (SAP_DM_INT_RESP_00) in your SAP S/4HANA
Integration with SAP Digital Manufacturing package as part of the Async Response Consumer Adaptor. You can
modify the following settings:
• Number of Concurrent Processes
The number of concurrent processes for each worker node. The recommended value depends on the
number of worker nodes, the number of queues on the tenant, and the incoming load. Make sure to enter a
value that is as small as possible (1-5) because JMS resources are limited.
Note
The default number of concurrent processes is 1. You should only increase this number if your scenario
requires parallel processing. However, keep in mind that when processing large messages, having a
high number of concurrent processes can cause out of memory problems.
• Retry Interval
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
• Exponential Backo
This setting makes sure that the retry interval is doubled after each unsuccessful retry. Therefore, the
receiver back end isn't called every minute if it's unavailable for a longer time period.
• Maximum Retry Interval
This value denes the maximum time between two retries if exponential backo is used. It's recommended
to keep the 60 minutes or even increase it if this is compatible with your scenario.
• Dead-Letter Queue
Don't deselect this setting. For more information, see Congure the JMS Sender Adapter and Dead Letter
Handling in JMS Adapter
.
Example
To illustrate the retry mechanism, the following values have been dened:
• Retry Interval is 3
• Exponential Backo is selected
• Maximum Retry Interval is 15
• RetryCount is 6 (You make this setting in the conguration section of the Async Response 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 Response 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 Congure the JMS Sender Adapter.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 119
Async Response Consumer Adaptor
You can nd the settings below in SAP Cloud Integration in your SAP S/4HANA Integration with SAP Digital
Manufacturing package by choosing the Congure option for the artifact:
• Number of Concurrent Processes
The number of concurrent processes for each worker node. The recommended value depends on the
number of worker nodes, the number of queues on the tenant, and the incoming load. Make sure to enter a
value that is as small as possible (1-5) because JMS resources are limited.
Note
The default number of concurrent processes is 2. You should only increase this number if your scenario
requires parallel processing. However, keep in mind that when processing large messages, having a
high number of concurrent processes can cause out of memory problems.
• Retry Interval
Enter a value for the amount of time to wait before retrying message delivery. The default value is 1 minute.
Async Response Consumer
You can nd the settings below in SAP Cloud Integration in your SAP S/4HANA Integration with SAP Digital
Manufacturing package by choosing the Congure option for the artifact:
• RetryCount
Enter a value for the maximum times to retry message delivery. The default value is 10.
To know more about these settings, see Congure the JMS Receiver Adapter.
Related Information
Congure Asynchronous Messaging with Retry Using JMS Adaptor
120
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.4.11.1.2Increasing the CPI Async Performance
Learn how to increase the number of messages that can be processed in the CPI Async scenario in SAP Cloud
Integration (Cloud Foundry).
Overview
If the CPI Async default setup provided by the SAP S/4HANA Integration with SAP Digital Manufacturing
package doesn't meet your business requirements in terms of message processing performance, you have
several options to increase the message throughput in SAP Cloud Integration and you can take action on the
following artifacts:
• Async Request Consumer Parallel Adaptor, which consumes messages coming from the JMS request
queue that processes message that can be handled in parallel (Parallel Queue).
• Async Request Consumer Sequential Adaptor, which consumes messages coming from the JMS request
queue that processes messages that need to be handled sequentially (Sequential Queue).
• Async Response Consumer Adaptor, which consumes messages coming from the JMS response queue.
More specically, you can act on three levels:
• You can increase the number of concurrent processes in the Async Request Consumer Parallel Adaptor and
the Async Response Consumer Adaptor. For more information, see Overview Advanced CPI Async Settings
[page 115].
• You can increase the number of adaptors without increasing the number of JMS queues. For this, simply
copy one of the adaptors and add a number to its name.
Example
You copy the Async Request Consumer Sequential Adaptor and give it a unique name, for example
Async Request Consumer Sequential Adaptor 1. No further changes are needed. The new adaptor is still
connected to the same JMS queue as the intial adaptor.
• You can increase the number of JMS queues by copying an adaptor and creating a new JMS queue for it.
For more information, see Increasing the Number of JMS Queues [page 122].
The appropriate level of action (adaptor settings, copying the adaptor, copying the adaptor and creating an
additional JMS queue) depends on your specic situation that you need to analyze. For more information, see
Monitoring CPI Async [page 124].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 121
2.1.4.11.1.2.1Increasing the Number of JMS Queues
Learn how to increase the number of JMS queues in your CPI Async scenario in SAP Cloud Integration (Cloud
Foundry) to increase the throughput of integration messages.
Prerequisites
• You've deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in SAP Cloud
Integration (Cloud Foundry).
• You've implemented the prerequisites described here: Asynchronous Communication with SAP Cloud
Integration [page 112].
Context
You can increase the throughput of integration messages in your CPI Async scenario by increasing the number
of the following queue types:
• JMS Request Queue for Parallel Processing (Parallel Queue)
• JMS Request Queue for Sequential Processing (Sequential Queue)
• JMS Response Queue
To create a queue, you must copy the corresponding adaptor rst and change the name of the referenced
queue. Then, the system automatically creates a new queue with the name you've dened.
Caution
Follow this naming convention for the new queues: SAP_DM_INT_REQ_P_01, SAP_DM_INT_REQ_P_02,...
As a next step, you need to increase the queue count in the producer iFlow to make sure that the producer can
send messages to the new JMS queue. Depending on the type of integration message, there's an adaptor/JMS
queue for sequential processing and an adaptor/JMS queue for parallel processing.
122
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
If the queue counter value is smaller than the number of queues, the additional queues won't receive
messages. If the queue counter value is larger than the number of queues, you will get an error: 400 Queue
Not Found.
For more information, see Asynchronous Communication with SAP Cloud Integration [page 112] and JMS
Resource and Size Limits .
The procedure below describes how to add a JMS Request Queue for Parallel Processing, but applies to all three
JMS queue types.
Procedure
1. In SAP Cloud Integration, go to the Design section and open your SAP S/4HANA Integration with SAP
Digital Manufacturing package.
2. Choose the Artifacts tab and select the artifact Async Request Consumer Parallel Adaptor and choose
Actions.
3. Choose Copy.
4. Give the artifact a unique name.
5. As Package, keep SAP S/4HANA Integration with SAP Digital Manufacturing.
6. Choose Copy.
7. In the Design section, choose the artifact that you've just created.
The overview diagram opens.
8. Choose Edit.
9. Choose JMS in the diagram to access the settings.
10. Under Connection, change the Queue Name from SAP_DM_INT_REQ_P_00 to SAP_DM_INT_REQ_P_01.
Increase the counter at the end of the name by one for each additional JMS queue that you want to create.
Stick to this pattern: SAP_DM_INT_REQ_P_01. The third JMS queue would be: SAP_DM_INT_REQ_P_02. If
you don't follow this naming pattern, the request producer won't nd the adaptor and the JMS queue.
11. Choose Save.
The system automatically creates a new queue SAP_DM_INT_REQ_P_01 that is connected to the Async
Request Consumer Parallel Adaptor 1.
12. Choose Save and Deploy.
13. Choose the Async Request Producer.
The overview diagram opens.
14. Choose Edit.
15. Choose Externalized Parameters.
16. Increase the NonSequenceRequestQueueCount by one.
Given that you've got now two JMS queues: SAP_DM_INT_REQ_P_00 and SAP_DM_INT_REQ_P_01, the
counter needs to be 2.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 123
If you're creating an adaptor/JMS queue for sequential processing, you need to increase the
SequenceRequestQueueCount.
17. Choose Save and Deploy.
Results
You've created an additional JMS queue for parallel processing.
2.1.4.11.2Monitoring 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 or Failed.
Messages with status Delivered don't support automatic and manual retry.
The CPI Correlation ID of your message that you can nd 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.
124
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution 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 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 nd the internal messages that are related to your integration message. You can nd the
CPI Correlation ID of your integration message in the Integration Message Dashboard.
Tip
In SAP Cloud Integration, you can nd the CPI Correlation ID within each message under Monitor Message
Processing and use it in the Integration Message Dashboard of SAP Digital Manufacturing to search for the
integration message.
If a message isn't transferred successfully from the JMS Queue to the Request Consumer iFlow through the
Request Consumer Adaptor, the message is retried as congured in the sender channel of the JMS queue. You
can nd detailed information about errors and the retries in the message processing log. For more information,
see Overview Advanced CPI Async Settings [page 115].
JMS Queues
Under Manage Stores Message Queues , you'll nd the following JMS queue messages that are used for
the asynchronous processing of messages:
• SAP_DM_INT_REQ_P_00, which represents the request JMS queue for parallel processing
• SAP_DM_INT_REQ_S_00, which represents the request JMS queue for sequential processing
• SAP_DM_INT_RESP_00, which represents the response JMS queue, which doesn't distinguish between
messages for parallel or sequential processing
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 Congure the JMS Sender Adapter and Dead Letter Handling in
JMS Adapter .
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 125
2.1.4.12Monitor Your Integration Scenario
Learn about how you can monitor your integration scenario.
Introduction
It's important to monitor certain integration points on a regular basis to ensure that the application is healthy
and that your integration scenario is operational from end to end. For this monitoring, you've got several
options, which are presented here.
Monitoring in SAP Digital Manufacturing
In SAP Digital Manufacturing, you can monitor your integration scenario using the Integration Message
Dashboard. This dashboard shows you information on inbound and outbound messages and lets you retry
failed messages. You can also use it to check your integration scenario for conguration errors and view the
SAP Cloud Integration logs for failed outbound messages. For more information, see Integration Message
Dashboard.
Monitoring in SAP Cloud Integration
In SAP Cloud Integration, you can check the status of your integration messages under Monitor Message
Processing. For more information, see Monitor Message Processing.
Monitoring Using SAP Cloud ALM
Using the Integration & Exception Monitoring feature of SAP Cloud ALM, which isn't part of SAP Digital
Manufacturing, you can monitor your end-to-end integration scenario centrally and access detailed
information about the status of your integration messages in dierent systems of your integration scenario.
When it comes to user authorization, be aware that the data made available to SAP Cloud ALM is a subset
of the data available in the Integration Message Dashboard. For more information, see Integration & Exception
Monitoring - Setup & Conguration .
The Integration & Exception Monitoring feature of SAP Cloud ALM uses the following integration statuses to
monitor integration messages in SAP Digital Manufacturing:
126
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Integration Status Description
In Process
The message is currently under processing in SAP Digital
Manufacturing.
For inbound messages, it means that SAP Digital
Manufacturing has received a message from an external sys-
tem and is processing it.
For outbound messages, it means a message is being pre-
pared in SAP Digital Manufacturing to be sent to an external
system.
Failed
An error occurred when the message was processed in SAP
Digital Manufacturing.
For inbound scenarios, it indicates that the correspond-
ing business object will not be available in SAP Digital
Manufacturing.
For outbound scenarios, it indicates that the message was
not delivered and the corresponding action notication isn't
sent to the external system.
Note
If the error is external, such as "Order locked in ERP",
the integration status is Completed, instead of
Failed, because the business object was delivered suc-
cessfully to the external system.
Completed
The message has been processed successfully.
For inbound scenarios, it indicates that the corresponding
business object, for example, a material, is now available in
SAP Digital Manufacturing.
For outbound scenarios, it indicates that the message has
been delivered and the corresponding action notication,
such as yield conrmation, has been sent to an external
system.
Note
If the error is external, such as "Order locked in ERP",
the integration status is Completed, instead of
Failed, because the business object was delivered suc-
cessfully to the external system.
Note
The integration status Not Started isn't displayed in SAP Cloud ALM, but only available in the Integration
Message Dashboard of SAP Digital Manufacturing. It indicates that a business process has been started
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 127
but that the message hasn't been received by the integration layer of SAP Digital Manufacturing. Once the
integration layer receives the message, the integration status is set to In Process.
If a message is stuck in status Not Started, the message isn't displayed in SAP Cloud ALM.
The times of the status changes are determined as follows in SAP Cloud ALM:
• The integration process starts when the integration status of a message in SAP Digital Manufacturing is set
to In Process for the rst time.
• The integration process ends when the integration status is changed from In Process to Completed, or
when it's set to Failed for the last time (after retry).
This method of determining event times is slightly dierent from how the times are determined in the
Integration Message Dashboard. As a result, the timestamp of a message in SAP Cloud ALM might not match
the timestamp of the same message in the Integration Message Dashboard of SAP Digital Manufacturing.
2.1.5Business 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 identier that represent dierent 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 identier in multiple SAP ERP or SAP S/4HANA systems, you can use plant
conversion to map each plant identier 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 dierent
plant in the real world, but they have the same identier. With plant conversion, you can perform the
following mapping to make sure that integration messages are transferred correctly:
Plant
Identier in SAP ERP / SAP S/
4HANA
Identier in SAP Digital
Manufacturing
Plant A in ERP 1 1000 1000-A
Plant B in ERP 2 1000 1000-B
128 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Related Information
Integration of Master Data [page 129]
Integration of Transaction Data [page 170]
Mapping Plants (Plant Conversion) [page 309]
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
Classication Classication
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 129
Sequence Considerations
You must transfer materials before BOMs.
Implementation Considerations
Some functions may behave dierently 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 233]
Allowed Characters for Key Fields [page 308]
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 orders can be created in SAP Digital Manufacturing, the material to manufacture must rst 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 can be created and released.
In some cases, specic material properties are required to manufacture the material. This information is
stored as classication data in SAP ERP or SAP S/4HANA and associated to the material master record. This
classication data must be maintained in SAP ERP or SAP S/4HANA and associated with the material. For
reasons of performance and stability, the classication data contained in the material master isn't used for
integration purposes. Instead, the classication data is transferred to SAP Digital Manufacturing separately
from the material master.
Transferring the material and its classication data from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing 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.
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 ease 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
material, inventory ID, bill of materials (BOM), and order records and then reported back to SAP ERP or
SAP S/4HANA in conrmations.
130
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• 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 isn't available, SAP Digital Manufacturing
uses the value in the rst available language.
Related Information
Manage Materials
Allowed Characters for Key Fields [page 308]
2.1.5.1.1.1Transferring 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 .
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 131
Note
Classication data (characteristic, class, classication assignment) is transferred separately from the
material master. For more information, see Classication Integration [page 138].
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 ll 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 elds can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 308].
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 233]
132
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.1.1.2Transferring 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 congured 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 dierences between production
lots. To manage these dierences, 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 specications. 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 identication, for example, pharmaceutical products are identied and managed
in stock according to both, the material number and the batch number.
Procedure
1. Create a batch-managed material record in SAP ERP or SAP S/4HANA. For more information, see
Creating a Batch Master Record.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 133
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 ll 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 elds can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 308].
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 233]
2.1.5.1.1.3Transferring 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
134
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 eld 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.
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 elds can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 308].
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).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 135
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 233]
2.1.5.1.1.4Transferring a Backushed Material
You can transfer backushed 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
backushing, the goods issue posting is carried out later when the operation or phase is conrmed for the
136
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
material component. The backush indicator that activates backushing is set in SAP ERP or SAP S/4HANA
and transferred to SAP Digital Manufacturing for execution.
Procedure
1. Create a backushed 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 ll 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 elds can contain only
allowed characters. For more information, see Allowed Characters for Key Fields [page 308].
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 233]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 137
2.1.5.1.2 Classication Integration
You can transfer classication data (characteristic, class, classication assignment) from your integrated SAP
ERP or SAP S/4HANA system to SAP Digital Manufacturing.
Use
In some cases, specic material properties may be required to manufacture a material. This information is
stored as classication data in SAP ERP or SAP S/4HANA and associated to the material master record. To be
more precise, a characteristic is assigned to a class, and the class is assigned to a classication assignment,
which binds the characteristic to the material master.
To transfer classication data to SAP Digital Manufacturing, you rst need to transfer the corresponding
material master and then the classication data in the following order:
1. Characteristic
2. Class
3. Classication assignment
For performance and stability reasons, the classication data download isn't triggered by the material master,
but the classication data is transferred separately from your ERP system to SAP Digital Manufacturing using
IDocs.
Overview
The integration procedure for classication data varies depending on the system you want to integrate with:
• Integration with SAP ERP [page 138]
• Integration with SAP S/4HANA [page 143]
2.1.5.1.2.1Integration with SAP ERP
You can transfer classication data (characteristic, class, classication assignment) from your integrated SAP
ERP to SAP Digital Manufacturing.
Use
You can transfer classication data, such as characteristics, classes, and classication assignments, from your
integrated SAP ERP to SAP Digital Manufacturing to use this data in your production processes.
138
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Overview
To transfer classication data to SAP Digital Manufacturing, perform the tasks described in the following
topics:
1. Transferring a Characteristic [page 139]
2. Transferring a Class [page 140]
3. Transferring a Classication Assignment [page 142]
2.1.5.1.2.1.1Transferring a Characteristic
Learn how to transfer a characteristic from SAP ERP to SAP Digital Manufacturing.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE communication to send the CHRMAS05 IDoc (characteristics) from SAP ERP to SAP
Digital Manufacturing. For more information, see Set Up Application Link Enabling (ALE) [page 38].
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
SAP Cloud Integration Artifact
SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP ERP system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 139
Context
After transferring the material master from SAP ERP to SAP Digital Manufacturing, you need to transfer the
characteristics separately from the material master to be able to use them for your shop oor processes.
Moreover, when you update a characteristic in your integrated SAP ERP system, you need to perform the
following procedure to communicate this change to SAP Digital Manufacturing.
Note
Alternatively, you can congure the change pointers in SAP ERP, so that the data is replicated
automatically to SAP Digital Manufacturing.
Procedure
1. Use transaction BD91 to distribute the characteristic.
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the
Characteristics Download integration message. For more information, see Integration Message Dashboard.
If the Characteristics Download wasn't successful even after retry, you can go to SAP Cloud Integration
and check the message status under Monitor Message Processing. For more information, see Monitoring
Message Processing.
2.1.5.1.2.1.2Transferring a Class
Learn how to transfer a class from SAP ERP to SAP Digital Manufacturing.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE communication to send the CLSMAS04 IDoc (class) from SAP ERP to SAP Digital
Manufacturing. For more information, see Set Up Application Link Enabling (ALE) [page 38].
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
140
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Cloud Integration Artifact SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP ERP system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
• You've transferred the characteristics to SAP Digital Manufacturing. For more information, see Transferring
a Characteristic [page 139].
Context
After transferring the material master and the characteristic from SAP ERP to SAP Digital Manufacturing, you
need to transfer the class separately from the material master to be able to use them for your shop oor
processes.
Moreover, when you update a class in your integrated SAP ERP system, you need to perform the following
procedure to communicate this change to SAP Digital Manufacturing.
Note
Alternatively, you can congure the change pointers in SAP ERP, so that the data is replicated
automatically to SAP Digital Manufacturing.
Procedure
1. Use transaction BD92 to distribute the class.
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the Class
Download integration message. For more information, see Integration Message Dashboard.
If the Class Download wasn't successful even after retry, you can go to SAP Cloud Integration and check
the message status under Monitor Message Processing. For more information, see Monitoring Message
Processing.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 141
2.1.5.1.2.1.3Transferring a Classication Assignment
Learn how to transfer a classication assignment from SAP ERP to SAP Digital Manufacturing for execution.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE communication to send the CLFMAS02 IDoc (classication assignment) from SAP ERP to
SAP Digital Manufacturing. For more information, see Set Up Application Link Enabling (ALE) [page 38].
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
SAP Cloud Integration Artifact
SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP ERP system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
• You've transferred the characteristic to SAP Digital Manufacturing. For more information, see Transferring
a Characteristic [page 139].
• You've transferred the class to SAP Digital Manufacturing. For more information, see Transferring a Class
[page 140].
Context
After transferring the material master, its characteristic, and class, from SAP ERP to SAP Digital
Manufacturing, you need to transfer the classication assignment separately from the material master to
be able to use them for your shop oor processes.
142
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Moreover, when you update a classication assignment in your integrated SAP ERP system, you need to
perform the following procedure to communicate this change to SAP Digital Manufacturing.
Note
By choosing Refresh in the Manage Materials app of SAP Digital Manufacturing, you can trigger a download
of the classication assignments as well.
Note
Alternatively, you can congure the change pointers in SAP ERP, so that the data is replicated
automatically to SAP Digital Manufacturing.
Procedure
1. Use transaction BD93 to distribute the classication assignment.
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the
Classication Assignment Download integration message. For more information, see Integration Message
Dashboard.
If the Classication Assignment Download wasn't successful even after retry, you can go to SAP Cloud
Integration and check the message status under Monitor Message Processing. For more information, see
Monitoring Message Processing.
2.1.5.1.2.2Integration with SAP S/4HANA
You can transfer classication data (characteristic, class, classication assignment) from your integrated SAP
S/4HANA system to SAP Digital Manufacturing using the data replication framework (DRF) and the business
transaction events (BTE).
Context
You can transfer classication data, such as characteristics, classes, and classication assignments, from your
integrated SAP S/4HANA system to SAP Digital Manufacturing using specic iDocs that are replicated through
the data replication framework (DRF).
For ad-hoc replication, you can use transaction DRFOUT. After transferring the material master, you replicate
the objects in the following order:
1. Characteristic
2. Class
3. Classication Assignment
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 143
It's recommended to set up the business transaction events (BTE) framework on top of the data replication
framework (DRF) to enable the automatic replication of characteristic, class, and classication assignment.
The topics referenced below provide you with more information.
Note
You can nd the minimum version requirements for the classication integration here: 3050090
.
Overview
To transfer classication data to SAP Digital Manufacturing, perform the tasks described in the following
topics:
1. Transferring a Characteristic [page 144]
2. Transferring a Class [page 146]
3. Transferring a Classication Assignment [page 147]
2.1.5.1.2.2.1Transferring a Characteristic
Learn how to transfer a characteristic from SAP S/4HANA to SAP Digital Manufacturing.
Prerequisites
• Your system meets the minimum version requirements for the classication integration. For more
information, see 3050090
.
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE and DRF communication to send the CHRMAS05 IDoc (characteristics) from SAP S/
4HANA to SAP Digital Manufacturing. For more information, see Set Up Application Link Enabling (ALE)
[page 38].
• Recommended: You've set up business transaction events (BTE) to enable automatic download of
characteristics, classes, and classication assignments. With transaction FIBF, you've implemented
application EDOC (eDocuments) and application CA-CL (Classication). For more information, see Dening
Business Transaction Event (BTE) for Electronic Documents.
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
144
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Cloud Integration Artifact SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP S/4HANA system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
Context
After transferring the material master from SAP S/4HANA to SAP Digital Manufacturing, you need to transfer
the characteristic separately from the material master to be able to use it for your shop oor processes.
By using the data replication framework (DRF) and the business transaction events (BTE) together, you can
automate the replication, so that created or updated characteristics are transferred automatically to SAP
Digital Manufacturing. For adhoc replication, you can follow the procedure below.
Procedure
1. Use transaction DRFOUT to distribute the characteristic.
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the
Characteristics Download integration message. For more information, see Integration Message Dashboard.
If the Characteristics Download wasn't successful even after retry, you can go to SAP Cloud Integration
and check the message status under Monitor Message Processing. For more information, see Monitoring
Message Processing.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 145
2.1.5.1.2.2.2Transferring a Class
Learn how to transfer a class from SAP S/4HANA to SAP Digital Manufacturing.
Prerequisites
• Your system meets the minimum version requirements for the classication integration. For more
information, see 3050090
.
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE and DRF communication to send the CLSMAS04 IDoc (class) from SAP S/4HANA to SAP
Digital Manufacturing. For more information, see Set Up Application Link Enabling (ALE) [page 38].
• Recommended: You've set up business transaction events (BTE) to enable automatic download of
characteristics, classes, and classication assignments. With transaction FIBF, you've implemented
application EDOC (eDocuments) and application CA-CL (Classication). For more information, see Dening
Business Transaction Event (BTE) for Electronic Documents.
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
SAP Cloud Integration Artifact
SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP S/4HANA system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
• You've transferred the characteristic to SAP Digital Manufacturing. For more information, see Transferring
a Characteristic [page 144].
146
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Context
After transferring the material master and the characteristic from SAP S/4HANA to SAP Digital Manufacturing,
you need to transfer the class separately from the material master to be able to use it for your shop oor
processes. By using the data replication framework (DRF) and the business transaction events (BTE) together,
you can automate the replication, so that created or updated classes is transferred automatically to SAP Digital
Manufacturing. For adhoc replication, you can follow the procedure below.
Procedure
1. Use transaction DRFOUT to distribute the class.The integration of class and characteristic deletion isn't
supported by
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the Class
Download integration message. For more information, see Integration Message Dashboard.
If the Class Download wasn't successful even after retry, you can go to SAP Cloud Integration and check
the message status under Monitor Message Processing. For more information, see Monitoring Message
Processing.
2.1.5.1.2.2.3Transferring a Classication Assignment
Learn how to transfer a classication assignment from SAP S/4HANA to SAP Digital Manufacturing.
Prerequisites
• Your system meets the minimum version requirements for the classication integration. For more
information, see 3050090 .
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've set up ALE and DRF communication to send the CLFMAS02 IDoc (classication assignments) from
SAP S/4HANA to SAP Digital Manufacturing. For more information, see Set Up Application Link Enabling
(ALE) [page 38].
• Recommended: You've set up business transaction events (BTE) to enable automatic download of
characteristics, classes, and classication assignments. With transaction FIBF, you've implemented
application EDOC (eDocuments) and application CA-CL (Classication). For more information, see Dening
Business Transaction Event (BTE) for Electronic Documents.
• You've manually deployed the latest SAP S/4HANA Integration with SAP Digital Manufacturing package in
SAP Cloud Integration.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 147
Note
The mapping between the SAP Cloud Integration artifacts and the integration workows available in
the Manage Integration Workows app is as follows:
SAP Cloud Integration Artifact
SAP Digital Manufacturing Integration Workow
Characteristic CHRMAS05 process request Characteristic Download
Class CLSMAS04 process request Class Download
ClassificationAssignment CLFMAS02 process
request
Classication Assignment Download
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
• You’ve created a material master, and assigned a characteristic, class, and classication assignment to the
material master in your SAP S/4HANA system.
• You've transferred the material master to SAP Digital Manufacturing. For more information, see
Transferring a Material Master [page 131].
• You've transferred the characteristic to SAP Digital Manufacturing. For more information, see Transferring
a Characteristic [page 144].
• You've transferred the class to SAP Digital Manufacturing. For more information, see Transferring a
Characteristic [page 144].
Context
After transferring the material master, the characteristic, and the class, from SAP S/4HANA to SAP Digital
Manufacturing, you need to transfer the classication assignment separately from the material master to be
able to use it for your shop oor processes. By using the data replication framework (DRF) and the business
transaction events (BTE) together, you can automate the replication, so that created or updated classication
assignments are transferred automatically to SAP Digital Manufacturing. For adhoc replication, you can follow
the procedure below.
Note
By choosing Refresh in the Manage Materials app of SAP Digital Manufacturing, you trigger a download of
the classication assigments.
Procedure
1. Use transaction DRFOUT to distribute the classication assignment.
2. In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of the
Classication Assignment Download integration message. For more information, see Integration Message
Dashboard.
148
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
If the Classication Assignment Download wasn't successful even after retry, you can go to SAP Cloud
Integration and check the message status under Monitor Message Processing. For more information, see
Monitoring Message Processing.
2.1.5.1.3 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.
2.1.5.1.3.1Conguring 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.
Prerequisites
SAP ERP
• You've set up ALE / DRF communication to create and transmit BOMMAT IDocs. For more information, see
Data Replication Framework [page 36].
• You've transferred materials to SAP Digital Manufacturing for execution. For more information, see
Transferring a Material Master [page 131].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 149
Procedural Steps
•
1. Create a bill of material master record in SAP ERP. For more information, see Steps in Creating a
Simple Material BOM.
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).
Related Information
Mapping a Bill of Material (BOM) [page 237]
2.1.5.1.3.2Conguring 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
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 specic operations, the system automatically assigns all material components in
a BOM to the rst operation when the order is opened. This means that they are all made available at the start
point of the rst operation.
150
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 dened 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.3.3Conguring an Order-Specic 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-specic BOM for use with this
production order.
Procedural Steps
1. Create a nished material and transfer it to SAP Digital Manufacturing for execution.
2. Dene a routing record in SAP ERP. You do not need to transfer it to SAP Digital Manufacturing for
execution.
3. Dene 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 151
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.4 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 le 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 le here:
Production Version . Choose Download API Specication and choose WSDL. You'll need to log in to get
the le.
• In the downloaded WSDL le, you've lled 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
Instances and Services , nd 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>
152
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Overview
You can create a production version in your integrated ERP to establish a relationship between your material
and one specic BOM and one specic 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 153]
2. Publish the WSDL File to the Service Registry [page 154]
3. Dene a Prole [page 155]
4. Dene a Provider System [page 156]
5. Dene Logon Data to access SAP Digital Manufacturing [page 157]
6. Congure a Local Integration Scenario [page 158]
7. Accomplish Pending Tasks [page 159]
8. Congure the Web Service [page 159]
9. Create a Logical System [page 160]
10. Create an RFC Destination [page 160]
11. Set Up the Data Replication Framework [page 160]
12. Dene a Replication Model [page 161]
13. Test your Scenario From the Integrated ERP system [page 161]
14. Check the Integration Scenario in SAP Digital Manufacturing [page 161]
15. Next Steps [page 161]
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 le.
6. Choose OK.
Your WSDL with name DM_PROD_VERS has been created.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 153
7. Choose (display) to check the details of your your WSDL le:
Field Content Namespace
Service Binding CO_PPINT_MFG_PRODN_VERS http://sap.com/xi/PP/Global2
PortType Interface ManufacturingProdnVersInfo_Ou
t
http://sap.com/xi/PP/Global2
Message Request ManufacturingProdnVersInfo http://sap.com/xi/PP/Global2
Interface Operation ManufacturingProdnVersInfo_Ou
t
http://sap.com/xi/PP/Global2
WSDL Service CO_PPINT_MFG_PRODN_VERS_servi
ce
http://sap.com/xi/PP/Global2
Endpoint URL https://..../ws?X-Identity-Zone-Sub-
domain={...}
http://sap.com/xi/PP/Global2
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 denition in t-code SPROXY. To nd 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 Classications tab, there are no entries needed.
7. Choose Next.
8. In the Service State tab, select Congured.
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 nd in the details of your binding:
Field
Content
Access URL https://.../ws?X-Identity-Zone-
Subdomain={…}
154 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Content
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 dened, 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 Congured
15. Choose Finish.
Dene a Prole
If the prole is already dened, you can skip this step.
1. Navigate to SOA Management Technical Administration Proles .
2. Under Proles, choose Create Prole.
3. On the General tab, enter the prole name, description, and select Old Prole Mode.
Example
Field
Content
Name DM_NAME
Prole Description DM_NAME
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 155
Field Content
Old Prole Mode Select this eld.
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 Identiable 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 conrm the activation of the prole.
The new prole is created and active.
Dene a Provider System
If the provider system is already dened, 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 prole name. Use the prole name that you created before.
Example
Field
Content
Name DM_NAME
Description DM_NAME
Prole Name Use the name of the prole that you've dened before,
for example DM_NAME.
Prole 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:
Field
Content
Use Services Registry Select the box
Services Registry SR_LOCAL
SLD Identier Select the SLD Identier from the table that corresponds
to your System ID, for example DM_NAME.
Logical System
156 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Content
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 conrm 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.
Dene Logon Data to access SAP Digital Manufacturing
If the logon data is already dened, 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 Certicate
Signature PSE
Encryption Certicate
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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 157
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 conrm 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.
Congure 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 Conguration .
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 Denitions 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 le. 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.
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:
158
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Example
Service Group Provider System Logon Data
PPINT_SOA_MFG_PRODN_VERS CLIENT / DM_NAME / DM_NAME DM_LOGON
17. Choose Finish and conrm 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 nd your tasks, lter by business scenario, for example DM_PROD_VERS, and set Type to Local
Conguration Requests.
4. Choose Rebuild List to lter the tasks.
5. Choose Process List in the Pending Tasks window to create a central logical post for the service group.
Congure the Web Service
This series of steps is about checking the conguration.
1. Navigate to
SOA Management Service Administration Web Service Conguration .
2. In the Web Service Conguration 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 Congurations tab opens. Make sure that the state is Active for the provider system you dened.
5. In the Dene Logical Ports section, select the business appl. ID (provider IBC reference) that you want to
congure.
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 eld, enter the SAP Digital Manufacturing for execution URL.
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]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 159
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 30].
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 Dene Technical Settings for Business Systems.
3. Choose Dene Business Systems.
4. Under General, enter the following parameters:
Name
Name of the provider system dened in SOAMANAGER, for
example DM_NAME
Description DM_NAME
Prole Name Name of the prole dened in SOAMANAGER, for example
DM_NAME
Prole Version 1
160 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Dene 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 Dene Custom Settings for Data Replication Dene Replication Models .
2. Under Dene 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 Dene 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 lter 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.
For more information on conguring a service group in SOAMANAGER, see Conguring a Service Group
.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 161
2.1.5.1.5 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 congured. Conguring 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 dened as
available in SAP ERP or SAP S/4HANA, you can transfer the dened 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 eective 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.5.1Transferring 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.
Prerequisites
SAP S/4HANA
• You have dened individual capacities using work center capacity assignments (see Manage Work Center
Capacity) and Work Center Capacity Mapping [page 164].
• You have set up ALE communication to create and transfer LOIWCS IDocs.
162
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You have dened the Data Replication Framework to replicate LOIWCS03 IDocs.
• 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
and SAP Note
3379404 ).
Note
You can download the multi-language descriptions of the standard value keys
(CO_MES_SVK_WITH_LANGUAGE). For more information, see 3134473 .
Procedural Steps
1. In SAP S/4HANA, open the Master Data Transfer (POIM) transaction.
2. Specify Optimization System (logical system / target system).
3. Select a work center for transfer.
4. Choose Execute.
5. Verify the results in the Integration Message Dashboard of SAP Digital Manufacturing for execution. There
you should nd two messages: Work Center Download and Standard Value Key Download. These messages
show that the work center has been downloaded and that SAP Digital Manufacturing for execution has
successfully retrieved the standard value key from the integrated ERP system.
Caution
If the standard value keys aren't retrieved from the integrated ERP system because the automatic call
made after the work center download fails, any subsequent order downloads fails too.
You can check dierent aspects in the following apps:
• 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 in the Manage Shifts app. The shift name usually has the following
format: the work center name, capacity category, SAP S/4HANA shift version, and internal SAP Digital
Manufacturing version separated by an underscore (for example, WCTEST1_008_01_V02).
• You can control if a default resource is created in SAP Digital Manufacturing for execution when a
work center is transferred from SAP S/4HANA using the Create Default Resources during Work Center
Transfer setting in the Plant category of the Manage Business Settings app.
Related Information
Manage Work Centers
Manage Resources
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 163
Manage Business Settings
2.1.5.1.5.1.1Work Center Capacity Mapping
Learn about the mapping of work center capacities between SAP S/4HANA or SAP ERP and SAP Digital
Manufacturing for execution.
Source Object in SAP S/
4HANA Naming in SAP S/4HANA
Target Object in SAP
Digital Manufacturing for
execution
Naming in SAP
Digital Manufacturing for
execution
Work Center ProdWC Work Center ProdWC
Resource (Default) ProdWC
Note
You control the creation
of the default resource
by using the Create
Default Resources during
Work Center Transfer
setting in the Manage
Business Settings app.
Capacity Category
Description: Capacity_A
Individual Capacity
Description: Station_A
Resource
Description: ProdWC_1
2.1.5.1.6 Transferring QM Defect Code Groups and Codes
from SAP S/4HANA
You can transfer Quality Management (QM) defect code groups and codes from SAP S/4HANA to SAP Digital
Manufacturing for execution using the Manage Nonconformance Groups app.
Prerequisites
• You've set up the integration with SAP S/4HANA (see Technical Integration with SAP S/4HANA or SAP
ERP [page 15]).
• You've checked that BAPI BAPI_CODEGROUP_CODE_GETLIST is available in your SAP S/4HANA system.
Note
There are SAP S/4HANA systems where this BADI is no longer used. If that's the case, you need to
implement the direct communication scenario instead of the indirect scenario that involves SAP Cloud
164
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Integration as middleware. For more information, see Enable Direct Communication To SAP S/4HANA
[page 109].
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 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 S/4HANA. Only released code
groups are displayed and can be transferred.
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 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 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.7 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 denes the key aspects of inventory-related information. The
information includes the consumption points of components during the manufacturing process as well as the
nal conrmation step when the manufactured material is posted to the nished 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 165
• The routing denes 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 dened for the operation in SAP ERP or SAP
S/4HANA.
• Routing
• SAP Digital Manufacturing for execution defaults the rst routing to version A and increments an
additional integer value for subsequent updates. For example: A-01, A-02.
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 elds on the
Operation record in the routing conguration.
Related Information
Manage Routings/Recipes
166
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.1.7.1Transferring 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 dened the Data Replication Framework (DRF) replication model to replicate LOIROU IDocs. For
information about the SAP ERP versions supporting DRF, see SAP Note 1793291
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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 167
2.1.5.1.8 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 theExecute Data Replicationtransaction (transaction code –DRFOUT).
• 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.9 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 xed 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.
168
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 rst 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-
responding equipment tools in the
Manage Tools app when equipment
PRTs are downloaded from SAP ERP.
Equipment PRTs are transferred
from ERP to SAP Digital
Manufacturing for execution through
the EQUIPMENT_CREATE02 IDoc. For
more details, see Transferring a Tool
[page 169].
Material PRT
Unlike the equipment PRT, the system
does not create tools when material
PRTs are downloaded from ERP. You
need to manually create respective
tools in the Manage Tools app.
Material PRTs are transferred from ERP
to SAP Digital Manufacturing for execu-
tion together with the respective mate-
rial master data.
2.1.5.1.9.1Transferring 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 169
Procedure
1. Create an equipment PRT in SAP ERP.
2. Send the equipment PRT to SAP Digital Manufacturing for execution.
We recommend using theExecute Data Replicationtransaction (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 your integrated ERP system.
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
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 specic
routing)
Order specic routing with work instruction
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 specic
order.
Production order with batch number Production order with batch number
A receipt for nished goods
170 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP SAP Digital Manufacturing for execution
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
step and operation
Production shop order with work center assignment on rout-
ing step and operation
Conrmation Completion of SFC
Consumption Component assembling
Scrap Scrap
You can integrate the following transaction data:
• Production order
• Production order conrmation
• Production order yield conrmation
• Component scrap conrmation for production order
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
conrmations 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
conrmation of yield and scrap as production is done on the shop oor. If components have been assembled,
they're included in the conrmation 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 dierentiation is
required for the internal execution logic, SAP Digital Manufacturing relies on the Auto complete and conrm
ag that is set on material level in the integrated ERP system. If this ag is active, the downloaded order is
considered to be a discrete industry order and handled accordingly. If this ag isn't active, the downloaded
order is treated as a process industry order and handled accordingly.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 171
Note
In the integrated ERP system, implement BADI CO_MES_INT_REDISTRIBUTION to make sure that the
release notication (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 notication
(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 notication (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
2.1.5.2.1.1Transferring 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.
• You have created and sent work centers to SAP Digital Manufacturing.
Note
Make sure that the standard value key download, which starts automatically after the work center
download, has been successful. Otherwise the order download won't work. In the Integration Message
Dashboard, you can check the status of the Standard Value Key Download integration message to see if
the standard value key download was successful.
• You have set up ALE communication to create and transmit LOIPRO IDocs.
172
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You have also dened 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 dened 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 prior to the production
order download allow additional manual congurations 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.
• You have enabled the artifact ProductionOrder LOIPRO05 process request V2 in SAP Cloud
Integration to use LOIPRO05 V2. For more information, see 3115603
Note
Creating and updating production orders using ProductionOrder LOIPRO05 process request
V2 is handled asynchronously in SAP Digital Manufacturing.
Tip
You can transfer a production order to SAP Digital Manufacturing for execution without BOM
components. To do this, you need to use the Production Order Download (LOIPRO05 V2) integration
ow. In the Manage Business Settings app, you need to switch on the Enable Order BOM Without
Components function.
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) lter
settings (see Data Replication Framework [page 36]). Changes to the order are distributed immediately
after the initial distribution.
3. Verify the results in SAP Digital Manufacturing.
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
If the header text contains an invalid character that could cause the order detail API to fail formatting, the
order download blocks it and you can't download the order successfully. In this case, remove the invalid
character and download the order again.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 173
Note
You can update an order from your integrated ERP system before and after the release in SAP Digital
Manufacturing. The updating options you have vary depending on the order category and the integrated
ERP system. For more information, see Updating Orders Before the Release [page 209] and Updating
Orders After the Release [page 214].
When the order is released in SAP Digital Manufacturing, shop oor 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.2Conguring 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 dened 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.
If the production order downloaded from your onpremise system contains BOM and routing data, SAP Digital
Manufacturing for execution creates the order-specic BOM and routing based on the downloaded order data.
If there's no BOM and routing in the production order, the order creation in SAP Digital Manufacturing for
execution fails.
• You can transfer co-products and by-products dened for the BOM in SAP ERP to SAP Digital
Manufacturing for execution with a production order.
• You can transfer alternate components dened 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.
174
PUBLIC
SAP Digital Manufacturing Integration Guide
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 (conguration 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 dened 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 dened 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) lter
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 (conguration type B) distributes
production orders automatically upon release based on the customized settings.
If you're using SAP ERP 6.00 – 6.04 (conguration 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 elds 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 175
2.1.5.2.1.3Conguring 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 oor control unit, is a unique identier that
represents an item to be produced on the shop oor.
• In an SAP ERP or SAP S/4HANA production order, you can dene 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 prole 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 dened 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
.
176
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You have dened 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 congurations 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) lter 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 (conguration 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 (conguration 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 elds 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 177
2.1.5.2.1.4Conguring 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 dierences 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 identication, for example pharmaceutical products, are identied 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 specications. 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 Conguring 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 dened 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 dened 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.
178
PUBLIC
SAP Digital Manufacturing Integration Guide
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 congurations 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 133]).
2. Create or update a production order with a dened 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) lter
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 (conguration type B) distributes
production orders automatically upon release based on customized settings.
If you use SAP ERP 6.00 – 6.04 (conguration 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 elds 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 179
2.1.5.2.1.5Conguring 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 dened 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 eld 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 dened 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 dened 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.
180
PUBLIC
SAP Digital Manufacturing Integration Guide
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 congurations 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) lter
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 (conguration type B) distributes
production orders automatically upon release based on customizing settings.
If you use SAP ERP 6.00 – 6.04 (conguration 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 elds 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 181
2.1.5.2.1.6Conguring 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 specic
routing step in SAP Digital Manufacturing for execution.
The production order is used by production planning in SAP ERP to dene 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 oor. 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
oor (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 Conguring 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 dened 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 dened 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 congurations to take place inside
182
PUBLIC
SAP Digital Manufacturing Integration Guide
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 specic 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) lter
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 (conguration type B) distributes
production orders automatically upon release based on customized settings.
If you use SAP ERP 6.00 – 6.04 (conguration 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 elds 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.7Transfer 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 dene 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 oor.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 183
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
Routings in the Manage Routings/Recipes App).
• 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 dened 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 dened 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 congurations 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 dened 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) lter
184
PUBLIC
SAP Digital Manufacturing Integration Guide
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 (conguration type B) distributes
production orders automatically upon release based on customized settings.
If you use SAP ERP 6.00 – 6.04 (conguration 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 elds 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 oor operators can see the
operation start and end time in the POD worklist.
2.1.5.2.1.8Transferring 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 172].
• 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 169].
• 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 185
• 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) lter
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 Conrmation
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 conrmation documents the processing status of orders, operations, sub-operations and individual
capacities. It is an instrument for controlling orders.
With a conrmation 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 conrmation shortly after completion of an operation is essential for realistic production planning and
control.
2.1.5.2.2.1Production Yield Conrmation on Operation
Complete
This section describes how to transfer a production yield conrmation 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 134]).
186
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
For more information about reporting consumed components, see the Transfer of Goods Movement within
Yield/Scrap Conrmation section of this guide.
Note
The Final Conrmation Type eld was removed from the Production Yield Conrmation message to support
the overproduction scenario in the Manage Orders app. For more information, see Increasing the Build
Quantity for Overproduction. As this eld was removed, the integrated ERP system sets the corresponding
operation to PCNF (partially conrmed), even if the yield quantity reaches the target quantity. Status CNF
(conrmed) 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 nal conrmation 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 veried that the control keys of the operations do not allow Auto Goods Receipt and that
they allow conrmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note
1502536 .
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that operations are not marked as milestone operations.
• You have veried that the operation sequence is not checked (see Logistics Production Shop Floor
Control
Operations Conrmation Dene Conrmation 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 oor.
• You have veried 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 veried that collaboration links and directives are congured. For more information, see
Collaboration Link / Directive Mappings for Outbound Communication Scenarios.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 187
Procedural Steps
1. Complete an SFC that belongs to the production shop order at the ERP reporting step.
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
Conrmation: Details screen (transaction CO14).
If the production shop order contains scheduling information that has been transferred, then the
conrmation message also contains quantity split IDs and the capacity category.
2.1.5.2.2.2Scrap Conrmation 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.
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 production 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 134]).
For more information about reporting consumed components, see Transferring a Goods Movement within
Yield/Scrap Conrmation [page 190].
Prerequisites
SAP ERP
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that the operation sequence is not checked (see
Logistics Production Shop Floor
Control
Operations Conrmation Dene Conrmation Parameters (transaction OPK4) ).
SAP Digital Manufacturing for execution
• You've imported the production order data from SAP ERP.
• You've released the production order to the shop oor.
188
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You've veried 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've veried that collaboration links and directives are congured. For more information, see Manage
Collaboration Links and Manage Collaboration Directives.
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 Conrmation message
with the following information to SAP ERP to report the quantity of scrapped nished goods and
component quantities consumed:
Data
Explanation
Plant Name of your plant
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 com-
plete the SFC
Split Yield of a split that was processed by a capacity when an
operation is split
Components Assembled components (For more information, see Trans-
ferring a Goods Movement within Yield/Scrap Conrma-
tion [page 190])
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 nd a re-
porting step in the routing by checking future steps
and uses the reporting step it nds.
In SAP ERP, you can see the status of the production order on the Display Production Order Conrmation:
Details screen (transaction CO14).
If the production order contains transferred scheduling information, then the conrmation message also
contains quantity split IDs and the capacity category.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 189
2.1.5.2.2.3Transferring a Goods Movement within Yield/
Scrap Conrmation
This section describes how to transfer goods movement (Goods Issue/Goods Receipt) to SAP ERP within
production yield conrmations and scrap conrmations for production orders.
Note
An SFC can be re-processed at an operation that this SFC has already completed.
This function supports long material numbers.
Prerequisites
SAP ERP
• You have veried that the control keys of the operations do not allow Auto Goods Receipt but allow
conrmations (see 1502536 ).
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that operations are not marked as milestone operations.
• You have veried that the operation sequence is not checked (see
Logistics Production Shop Floor
Control Operations Conrmation Dene Conrmation 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 oor.
• You have received oor stock from SAP ERP.
• You have veried 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 veried that collaboration links and directives are congured. For more information, see
Collaboration Link / Directive Mappings for Outbound Communication Scenarios.
Procedure
1. Assemble a discrete component (by choosing Add in the Assembly Point or As-Built Conguration plugin,
or when a component is assembled using the Auto Assemble Component hook point activity) or a time-
based component.
190
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2. Complete an SFC belonging to the production order at the ERP reporting step and scrap it.
3. The system triggers a collaboration event and sends a conrmation 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
Goods movement is triggered for non-BOM components. But it's not triggered for:
• Co-products and by-products
• Floor stock pegged to an order
Note
The goods movement section is included in the following messages:
• Production Order Yield Confirmation
• Production Order Scrap Confirmation
2.1.5.2.2.4Transferring a Goods Movement (Goods Issue)
Independent of Yield Conrmation
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.
Prerequisites
SAP ERP
• You have veried that the component materials are not marked as backushed (the Backush checkbox on
the MRP 2 tab of the MM01/MM02 transaction).
SAP Digital Manufacturing for execution
• In Collaboration Link Maintenance, you have veried 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 oor stock from SAP ERP.
• You have released the production order to the shop oor.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 191
Procedural Steps
1. Choose Add in the Assembly Point (Assemble Components) or As-Built Conguration 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.
2.1.5.2.2.5Production Order Complete
You can transfer a production order complete message to SAP ERP or SAP S/4HANA.
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 / SAP S/4HANA
• You've veried that the control keys of the operations do not allow Auto Goods Receipt but allow
conrmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note 1502536
).
• You've veried that all work centers have the same activity types arranged in the same sequence.
• You've veried that operations are not marked as milestone operations.
• You've veried that the operation sequence is not checked (see Logistics Production Shop Floor
Control
Operations Conrmation Dene Conrmation Parameters (transaction OPK4) ).
SAP Digital Manufacturing for execution
• You have imported the production order data from SAP ERP or SAP S/4HANA.
• You have released the production order to the shop oor.
• You have veried 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 or SAP S/4HANA.
192
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You've set up the COLLABORATION_ORDER_COMPLETE_DI link and the ERP_ORDER_COMPLETE_V2
directive in the Manage Collaboration Links and Manage Collaboration Directives apps. For more
information, see Collaboration Link / Directive Mappings for Outbound Communication Scenarios.
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.
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 ERP or SAP S/4HANA.
In SAP ERP or SAP S/4HANA, you can see the status of the production order on the Display Production
Order Conrmation: Details screen (transaction CO14).
Related Information
Completing Orders
How Order Statuses Change in a Business Scenario
SAP Note 3489424
2.1.5.2.2.6Report Serial and Batch Numbers for Semi-
Finished Components
This section describes how to transfer a serial and batch number for semi-nished components to SAP
ERP within production yield conrmation, planned order conrmation, scrap conrmation for production and
planned orders, and container close messages.
Prerequisites
SAP ERP
• You have congured Batch Management.
• You have maintained a serial number prole 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 ).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 193
• You have veried that the control keys of the operations do not allow Auto Goods Receipt but allow
conrmations (see Control Key on the SAP Help Portal at http://help.sap.com and SAP Note 1502536 ).
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that operations are not marked as milestone operations.
• You have veried that the operation sequence is not checked (see
Logistics Production Shop Floor
Control Operations Conrmation Dene Conrmation Parameters (transaction OPK4) ).
• You have set up ALE communication to create and transmit LOIPRO IDocs.
• You have also dened 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 dened unique ISO codes for every unit of measure.
SAP Digital Manufacturing for execution
• You've imported the material master records for the produced material and all the components.
• For materials to be assembled, you've specied which data will be collected on assembly:
o SFC or INV_SFC
• You've imported the production order with BOM and routing data from SAP ERP.
• You've released the production shop order to the shop oor.
• You've received oor stock from SAP ERP.
• You've veried 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've set up the collaboration links and directives in the Manage Collaboration Links and Manage
Colloabration Directives apps. For more information, see Collaboration Link / Directive Mappings for
Outbound Communication Scenarios.
Procedural Steps
1. Create a semi-nished material record in SAP ERP. It has to be either batch-managed or with an assigned
serial number prole.
2. Create a nished material record with the BOM containing semi-nished material.
3. Create and release a production order in SAP ERP for semi-nished 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 (nished material).
5. Assemble a semi-nished component using either discrete (by choosing Add in the Assembly Point or
As-Built Conguration plugin) or time-based assembling.
Note
Reporting of serial numbers is not supported for time-based components.
194
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 conrmation 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
2.1.5.2.2.7Activity Conrmation
You can transfer activity conrmation 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 172].
• The production order is released to the shop oor 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 conrmation for the production order. For more information,
see Order POD.
2. The system triggers a collaboration event and sends the Production Order Activity Conrmation message
to trigger the posting of an activity conrmation in SAP ERP or SAP S/4HANA.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 195
3. To verify whether the Production Order Activity Conrmation 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 Conrmation 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 nd in the
Integration Message Dashboard. For more information, see Monitoring Message Processing.
2.1.5.2.2.8Quantity Conrmation
You can transfer quantity conrmation messages from SAP Digital Manufacturing for execution to SAP ERP
and SAP S/4HANA.
Prerequisites
SAP ERP and SAP S/4HANA
• You have veried that the control keys of the operations do not allow Auto Goods Receipt and that they
allow conrmations (see Control Key on the SAP Help Portal).
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried 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
Conrmation Dene Conrmation 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 oor.
• 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 Conrmation tab.
196
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
There's a check performed in the background whether the current resource is relevant for OEE and
scheduling (Scheduling and OEE Relevant ag is set in the Manage Work Centers app). If the resource
isn't OEE and scheduling relevant, the conrmation 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 conrmation in SAP ERP or SAP S/4HANA.
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 recipe for the produced material.
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 notication (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 dierentiation
is required for the internal execution logic, SAP Digital Manufacturing relies on the Auto complete
and conrm ag that is set on material level in the integrated ERP system. If this ag is active, the
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 197
downloaded order is considered to be a discrete industry order and handled accordingly. If this ag
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 congure the overdelivery
limits only as soft limits (warning) in your integrated ERP system. If you congure 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
conguration in the integrated ERP system, see 3267541 .
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 lter 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.
After releasing the order in SAP Digital Manufacturing for execution, the Manage Orders app allows shop oor
operators to view the scheduled start and end time. It is important to note that the execution of process orders
should be exclusively carried out through the Order POD app.
Related Information
Manage Orders
Order Statuses
How Order Statuses Change in a Business Scenario
2.1.5.2.3.1Transferring 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.
198
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• 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).
Tip
You can transfer a process order to SAP Digital Manufacturing for execution without BOM components.
To do this, you need to use the Process Order Download (LOIPRO05 V2) integration ow. In the Manage
Business Settings app, you need to switch on the Enable Order BOM Without Components function.
Prerequisites
SAP ERP and SAP S/4HANA
• You have completed all the prerequisites of Conguring a Process Order [page 197].
• Inspection characteristics have been assigned to individual operations in the master recipe.
SAP Digital Manufacturing
• You have set up ALE / DRF 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 lter 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 oor operators can see the
inspection characteristics at operation level in the Order POD (Default).
Related Information
Process Order Integration [page 197]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 199
2.1.5.2.4 Process Order Status Conrmation
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 conrmation documents the processing status of orders, operations and inventory movements. It is
an instrument for controlling orders.
With a conrmation 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.
Note
The information about which SFC was processed is transferred to SAP Cloud Integration within the
outbound conrmation 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 Conrmation
• Process Order Quantity Conrmation Cancellation
• Process Order Activity Conrmation
• Process Order Activity Conrmation Cancellation
You need to perform the mapping of OData elds to BAPI elds between SAP Cloud Integration and
your ERP system according to your needs.
Exact conrmation shortly after completion of an operation is essential for realistic production planning and
control.
Related Information
Goods Receipt [page 201]
Goods Issue [page 201]
Quantity Conrmation [page 202]
Activity Conrmation [page 203]
200
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.2.4.1Goods Receipt
You can transfer goods receipts for process orders to SAP ERP or SAP S/4HANA within goods receipt
conrmations.
Prerequisites
SAP ERP or SAP S/4HANA
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that operations are not marked as milestone operations.
• You have veried that the operation sequence is not checked (see Production Shop Floor Control
Operations Conrmation Dene Conrmation Parameters (transaction OPK4) ).
SAP Digital Manufacturing
• The process order data is transferred from SAP ERP or SAP S/4HANA.
• The process order is released to the shop oor.
• 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.2Goods 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 197].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 201
• The process order is released to the shop oor.
• 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.
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 nd in the
Integration Message Dashboard. For more information, see Monitoring Message Processing.
2.1.5.2.4.3Quantity Conrmation
You can transfer quantity conrmation messages from SAP Digital Manufacturing for execution to SAP ERP
and SAP S/4HANA.
Prerequisites
SAP ERP and SAP S/4HANA
• You have veried that the control keys of the operations do not allow Auto Goods Receipt and that they
allow conrmations (see Control Key on the SAP Help Portal)
• You have veried that all work centers have the same activity types arranged in the same sequence.
• You have veried that operations are not marked as milestone operations. For more information, see
1502536
.
202
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• You've made the following settings under Logistics Production Shop Floor Control Operations
Conrmation Dene Conrmation 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 oor.
• 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.
Procedure
1. In the Order POD (Default), post quantities in the Quantity Conrmation tab.
Note
There's a check performed in the background whether the current resource is relevant for OEE and
scheduling (Scheduling and OEE Relevant ag is set in the Manage Work Centers app). If the resource
isn't OEE and scheduling relevant, the conrmation 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 conrmation in SAP ERP or SAP S/4HANA.
2.1.5.2.4.4Activity Conrmation
You can transfer activity conrmation 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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 203
• The process order data is transferred from SAP ERP or SAP S/4HANA. For more information, see Process
Order Integration [page 197].
• The process order is released to the shop oor.
• 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 conrmation for the process order. For more information, see
Order POD.
2. The system triggers a collaboration event and sends the Process Order Activity Conrmation message to
trigger the posting of an activity conrmation in SAP ERP or SAP S/4HANA.
3. To verify whether the Process Order Activity Conrmation 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 Conrmation 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 nd 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 conrmations.
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
dened quantity within a specic time frame. With repetitive manufacturing, you generally use simple routings
that don't change over time. The following features are supported:
• Yield conrmation is sent to the integrated ERP system after an SFC has been completed at the last
operation.
• Scrap conrmation is sent to the integrated ERP system after an SFC has been scrapped.
204
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• Goods issue posting to the integrated ERP system after operation / phase conrmation (backush).
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 15].
If you've already implemented the infrastructure described in the technical integration section, you can nd the
planned order specic information in the following topics:
• Transferring a Planned Order [page 205]
• Scrap Conrmation for Planned Orders [page 207]
• Yield Conrmation for Planned Orders [page 208]
2.1.5.2.5.1Transferring 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 15]. In the section below, you'll learned what needs
to be done specically 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 prole (for example 0001) to the material on view MRP4. If needed, you can
create a REM prole 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).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 205
• 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].
• You've implemented the INBOUND PROCESSOR iFlow in SAP Cloud Integration and activated it through
the Initial Parameters iFlow. For more information, see Congure Inbound Processor iFlow [page 71]
and Congure Initial Parameters iFlow [page 73].
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 eld 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 nd in the Integration Message Dashboard. For more information, see Monitoring Message
Processing.
206
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Related Information
Manage Orders
2.1.5.2.5.2Scrap Conrmation for Planned Orders
Learn how to transfer scrap conrmations 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 conguration described
below.
Prerequisites
SAP ERP / SAP S/4HANA
• You've veried 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 205].
• You've released the planned order to the shop oor using the Manage Orders app.
• You've veried that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity ag in the Manage Routings/Recipes app is set to Yes.
• You've congured 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-
MATION
ERP_PLANNED_ORDER_SCRAP_CONFIRMATION
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 207
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 Conrmation message is sent to the integrated ERP system.
Note
If an SFC is scrapped on the nonreporting step, SAP Digital Manufacturing tries to nd a reporting step
in the routing by checking future steps and uses the reporting step it nds.
2. To verify whether the Planned Order Scrap Conrmation 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 Conrmation 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 nd in the Integration Message Dashboard. For more information, see Monitoring Message
Processing.
2.1.5.2.5.3Yield Conrmation for Planned Orders
Learn how to transfer a yield conrmations 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 conguration
described below.
Prerequisites
SAP ERP / SAP S/4HANA
• You've veried that all work centers have the same activity types arranged in the same sequence.
• You've veried that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity ag in the Manage Routings/Recipes app is set to Yes.
208
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 205].
• You've released the planned order to the shop oor using the Manage Orders app.
• You've veried that routings contain at least one ERP reporting step, which means that the Last Reporting
Activity ag in the Manage Routings app is set to Yes.
• You've congured 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-
MATION
ERP_PLANNED_ORDER_YIELD_CONFIRMATION
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 Conrmation 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 Conrmation 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 nd 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 has been released to the shop oor and SFCs have been created in SAP Digital
Manufacturing.
Use
Before releasing an order to the shop oor 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 209
Overview
Here you'll nd an overview of the supported update scenarios. "X" means that the corresponding update is
supported.
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Finished Goods
Batch Number
(Order Header)
X X X X X X
Goods Receipt
Storage Loca-
tion (Order
Header)
X
X X X X X
Customer
Name (Order
Header)
X X N/A N/A N/A N/A
Sales Order
(Order Header)
X X X N/A N/A N/A
Custom Field
(Order Header)
X X N/A X X N/A
Work Instruc-
tion (Order
Header)
X X N/A N/A N/A N/A
Dates Changes
(Order Header)
X X X X X X
Inspection Lot
Change (Order
Header)
X X X X X X
Operation
Schedule (Or-
der Schedule)
X X X X X X
Production
Version (Order
Header)
X X N/A X X N/A
Scheduling
Type (Order
Header)
N/A N/A N/A N/A N/A N/A
Quantity De-
crease (Order
Header)
X X X X X X
Quantity In-
crease (Order
Header)
X X X X X X
210 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Serial Number
(Order Header)
X X X N/A N/A N/A
Technical Com-
pletion (TECO)
(Order Header)
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
Order Header
Long Text (Or-
der Header)
X X X X X X
Order Header
Schedule
Dates/Plan
Dates (Order
Header)
X
X X X X X
BOM Compo-
nent Storage
Location (BOM
Component)
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
BOM Compo-
nent Batch
Number (BOM
Component)
X
X X X X X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 211
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Underdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Overdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Warehouse
Number (Order
Header)
X X X X X X
Addition / Re-
moval of Com-
ponent (BOM
Component)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Component
Assignment
Change to Op-
eration Activ-
ity / Phase
(BOM Compo-
nent)
X
X X X X X
Addition / Re-
moval of Oper-
ation / Phase
(Operation)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Work Center
Change in Op-
eration /
Phase (Opera-
tion)
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
Control Key
(Operation)
X X X X X X
212 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Change of
Component
Quantities
(BOM Compo-
nent)
X
X X X X X
Operation/
Phase Number
(Operation)
X X X
Operation/
Phase Text
(Operation)
X X X X X X
Order-Specic
Bill of Mate-
rial*
X X X X X X
Order-Specic
Routing*
X X X X X X
Priority (Order
Header)
X X N/A X X N/A
Warehouse
Number (BOM
Component)
X X X X X X
ERP Bom ID X X X X
ERP Bom Us-
age
X X X X
ERP Alterna-
tive Bom ID
X X X X
ERP Routing
Group
X X
ERP Group
Counter
X X
ERP Recipe
Group
X X
ERP Recipe X X
*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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 213
• Changes to component units of measure, line numbers, or storage locations
2.1.5.2.7 Updating Orders After the Release
Learn about the options you've got for updating a production or process order from your integrated ERP
system after the order has been released to the shop oor and SFCs have been created in SAP Digital
Manufacturing.
Prerequisites
• For integration scenarios with SAP ERP or SAP S/4HANA, see Updating Orders After the Release (Custom
XSLT).
Note
For integration scenarios with SAP S/4HANA Cloud, there are no actions required.
• The order isn't in status Completed, Discarded, or Closed in SAP Digital Manufacturing.
Use
After releasing an order to the shop oor in the Manage Orders app, you can update it from your integrated ERP
system. The updating options you've got depend on the order type and the integrated ERP system you're using.
Overview
Here you'll nd an overview of the supported update scenarios. "X" means that the corresponding update is
supported.
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Finished Goods
Batch Number
(Order Header)
X X X X X X
214 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Goods Receipt
Storage Loca-
tion (Order
Header)
X
X X X X X
Customer
Name (Order
Header)
X X N/A N/A N/A N/A
Sales Order
(Order Header)
X X X N/A N/A N/A
Custom Field
(Order Header)
X X N/A X X N/A
Work Instruc-
tion (Order
Header)
X X N/A N/A N/A N/A
Dates Changes
(Order Header)
X X X X X X
Inspection Lot
Change (Order
Header)
N/A N/A N/A N/A N/A N/A
Operation
Schedule (Or-
der Schedule)
X X X X X X
Production
Version (Order
Header)
X X N/A X X N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 215
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Quantity De-
crease (Order
Header)
X
Note
Production
orders from
SAP ERP or
communi-
cated
through
processed
in the Work
Center POD
are sup-
ported.Pro-
duction Or-
der Down-
load (LOI-
PRO05 V2)
X
Note
Production
orders from
SAP ERP or
SAP S/
4HANA
communi-
cated
through
Production
Order
Download
(LOIPRO05
V2) proc-
essed in
the Work
Center POD
are sup-
ported.
X
N/A N/A N/AX
Quantity In-
crease (Order
Header)
X X X X X X
Serial Number
(Order Header)
X X X N/A N/A N/A
Technical Com-
pletion (TECO)
(Order Header)
N/A N/A N/A N/A N/A N/A
Order Header
Long Text (Or-
der Header)
X X X X X X
Order Header
Schedule
Dates/Plan
Dates (Order
Header)
X
X X X X X
216 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
BOM Compo-
nent Storage
Location (BOM
Component)
X
Note
Production
Order
Down-
loadThe
BOM com-
ponent
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
BOM Compo-
nent Batch
Number (BOM
Component)
X
X X X X X
Underdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Overdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Warehouse
Number (Order
Header)
X X X X X X
Addition / Re-
moval of Com-
ponent (BOM
Component)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Component
Assignment
Change to Op-
eration Activ-
ity / Phase
(BOM Compo-
nent)
X
X X X X X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 217
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Addition / Re-
moval of Oper-
ation / Phase
(Operation)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Work Center
Change in Op-
eration /
Phase (Opera-
tion)
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
Control Key
(Operation)
X X X X X X
Work Instruc-
tion (Opera-
tion)
X X N/A N/A N/A N/A
Change of
Component
Quantities
(BOM Compo-
nent)
X
X X X X X
Operation/
Phase Number
(Operation)
X X X
Operation/
Phase Text
(Operation)
X X X X X X
Order-Specic
Bill of Mate-
rial*
X X X X X X
Order-Specic
Routing*
X X X X X X
Priority (Order
Header)
X X N/A X X N/A
218 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Warehouse
Number (BOM
Component)
X X X X X X
ERP Bom ID X X X X
ERP Bom Us-
age
X X X X
ERP Alterna-
tive Bom ID
X X X X
ERP Routing
Group
X X
ERP Group
Counter
X X
ERP Recipe
Group
X X
ERP Recipe X X
*Objects are up-versioned if one of the following changes takes place:
• Changes to work centers on operations / phases
• 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 units of measure, line numbers, or storage locations
2.1.5.2.8 Enrichment of Order-Specic Objects
Enrichment is the process of copying some of the elds from master objects to order-specic objects during
order integration.
The following elds are copied for BOM components:
• Assembly Qty As Required
• Minimum Tolerance
• 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:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 219
• Assembly Data Type
• Assembly Qty As Required
The following elds 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 elds are copied only for routings:
• Relaxed ow
• Quantity validation
The following elds are copied only for recipes
• Weighing relevant ag (on operation activity level)
2.1.5.2.9 Enrichment with Sub-Operations for Discrete
Manufacturing
You can add sub-operations to an order-specic routing in SAP ERP, SAP S/4HANA, or SAP S/4HANA Cloud,
and then transfer this routing to SAP Digital Manufacturing. You can also add sub-operations to a master
routing in SAP ERP or SAP S/4HANA and then transfer this routing to SAP Digital Manufacturing.
Overview
In a discrete industry scenario, you can add sub-operations to an order-specic routing in SAP ERP, SAP
S/4HANA, or SAP S/4HANA Cloud.
Caution
Transferring a master routing with sub-operations to SAP Digital Manufacturing is supported only in SAP
ERP and SAP S/4HANA.
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 conrmations are posted against the ERP parent Operation.
Mapping
In SAP Digital Manufacturing, ERP routings containing sub-operations are mapped as follows:
220
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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
SAP Digital Manufacturing operation activity IDs for the case of suboperations consist of the ERP operation ID
(the rst four digits) and the ERP sub-operation ID (the last four digits).
2.1.5.2.10Batch 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.
For an overview of prerequisites and the steps required to update batch characteristics, see Updating Batch
Characteristics.
2.1.5.2.11Batch 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. For an overview of prerequisites and the steps required to create batch numbers, see Creating Batch
Numbers.
2.1.5.2.12Inspection Characteristics Integration (Process
Order and 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
• 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)
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 221
• 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 rst range, so that the
inspection results recorded in SAP Digital Manufacturing are checked against two value ranges: the
standard range and the rst range.
Note
You can use after acceptance or rejection characteristics that are dened in an integrated ERP system.
The acceptance or rejection characteristic is a conditional characteristic that depends on the valuation
results of the previous mandatory characteristic in the same operation.
Acceptance or rejection characteristics are supported for production orders from SAP ERP or SAP
S/4HANA in the Order POD and the Work Center POD.
• 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 transaction code CUNI.
SAP Digital Manufacturing
• The Order POD, for process industry, or the Work Center POD, for discrete industry, are already congured
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 an 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. Check whether the inspection characteristics are available:
• In the Order POD, select a specic order and you can verify the inspection characteristics of a specic
operation / phase on the Quality Inspection Characteristic List tab.
• In the Work Center POD, select a specic SFC and you can verify the inspection characteristics of a
specic operation on the Quality Inspection Characteristic List tab.
222
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Related Information
Inspection Results Recording (Process Order and Production Order) [page 223]
2.1.5.2.13Inspection Results Recording (Process Order and
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
Production Order) [page 221].
SAP Digital Manufacturing
Note
For more information on the supported message types and needed integration artifacts, see 3050090 .
• The Order POD or the Work Center POD is already congured with the Quality Inspection Results and the
Quality Inspection Characteristic List 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
For the procedure applying to process and production orders in the Order POD, see Recording Quality
Inspection Results.
For the procedure applying to production orders in the Work Center POD, see Recording Quality Inspection
Results.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 223
Related Information
Inspection Characteristics Integration (Process Order and Production Order) [page 221]
2.1.5.2.14Work 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
Conguring a Production Order with Document Info Records [page 180].
2.1.5.2.15Transfer of Floor Stock Data
You can transfer oor stock data for certain goods movement types from an SAP ERP or SAP S/4HANA system
to SAP Digital Manufacturing.
Use
Note
To use this functionality, you need to verify or update your integration conguration. For more information,
see Updating Integration Conguration to Use Floor Stock Data [page 230].
Note
To ensure data consistency, you need to make some additonal conguration for your storage locations in
ERP system. 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
• Type set as Inventory management only by incoming transfer postings
The storage location congured 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 congured this way.
The above settings apply to individual inventory management mode. If you're using the consolidated
inventory management mode, you only need to set the business system as the business system for SAP
Digital Manufacturing.
224
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Consolidated Inventory Management Mode
If you've enabled Consolidated inventory management mode, all standard goods movement types in SAP
S/4HANA are supported in SAP Digital Manufacturing . However, for integration with SAP ERP, only goods
movement types that are relevant to Unstricted-Use Stock (01) are supported.
Note
For consolidated inventory management mode, you need to enable the API_MATERIAL_STOCK_SRV
technical service in SAP S/4HANA.
Individual Inventory Management Mode
If you've 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)
• 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:
• Floor Stock Return (goods movement type 312)
• Floor Stock Return for specic 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)
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 225
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 oor stock receipt without reservation (goods movement type 311 ) in SAP Digital
Manufacturing 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 conrmation for consumption against the production
order.
• When you post a transfer of unrestricted-use stock from a central (issuing) storage location to a oor
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 by the INVCON03 IDoc.
• SAP ERP or SAP S/4HANA triggers the IDoc INVCON03 to integrate the oor stock to the production
storage location in SAP Digital Manufacturing with Inventory ID created to the new inventory.
If the material is batch-managed, the Batch Number is also created and displayed in the new inventory.
If you have serialized material want to download the serial number along with the stock transfer, as well as
view the Serial Number in the new inventory, refer to the Prerequisites session below for more information.
The inventory is ready for consumption without reservation in SAP Digital Manufacturing.
• A oor stock receipt is created for the specied components.
When yield /scrap collaboration is triggered, SAP Digital Manufacturing sends a conrmation to SAP ERP or
SAP S/4HANA to report consumed components.
Production Order-Specic Consumption (goods movement type 261)
The process of oor 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.
226
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Goods consumption happens when a material leaves the storage location. This consumption creates an
inventory ID in SAP Digital Manufacturing . This inventory ID is consumed during assembly but this information
isn't 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 .
• 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 oor stock to the production
storage location (from Material Master or Production Order) in SAP Digital Manufacturing with Inventory ID
created and Reserved Order Number attached to the new inventory.
If the material is batch-managed, the Batch Number is also created and displayed in the new inventory.
If you have serialized material want to download the serial number along with the stock transfer, as well as
view the Serial Number in the new inventory, refer to the Prerequisites session below for more information.
• The inventory is ready for consumption only for the reserved order in SAP Digital Manufacturing .
Integration
• SAP ERP or SAP S/4HANA is the system of record for inventory management; SAP Digital Manufacturing
is the system of record for oor stock management.
• A transfer posting in SAP ERP or SAP S/4HANA is used in the same way as a oor stock receipt in SAP
Digital Manufacturing .
• For inventory ID records created in SAP Digital Manufacturing through the integration, the database eld
ERP_INVENTORY is equal to true.
• Floor storage location exists in both SAP ERP or SAP S/4HANA (LGORT) and SAP Digital Manufacturing
(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've created production storage locations for oor stock materials.
• You've set up ALE communication to create and transmit INVCON03 IDocs. For more information, see Data
Replication Framework [page 36].
• 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've maintained integration of goods movements (see SAP Note
1555198 ).
• You've set up a lter for the goods movement type 261 and 311 (see Customizing for ALE Communication
on the SAP Help Porta).
• You've created a BOM for the nished good material of the order.
• If you want to transfer stocks for serialized materials, ensure you've added a new segment specically
for serial numbers under the segment E1ICIT in the extended IDoc for INVCON03. The IDoc INVCON03
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 227
doesn't support serial numbers by default, so you need to add this extension and also make other
corresponding customizations to include serial numbers in the goods movements. For more information,
see SAP Note 3452935 .
SAP Digital Manufacturing
• You've created and congured data type for oor stock integration.
• For materials to be received into oor stock and assembled, you've specied the following in the Manage
Materials app:
• Data to Collect on Assembly: INV or INV_SFC
• You've created a storage location matching SAP ERP or SAP S/4HANA Putaway Storage Location (see
Mapping a Production Order [page 245]).
• For the production order-specic consumption scenario, you've created or imported shop order data so
that components can be pegged (see Production Order Integration [page 171]).
• You've dened a numbering pattern for the number type oor stock receipt (see Conguring a Production
Order with Serial Numbers [page 176]).
• For the outbound integration with Inventory Management (IM), you've 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_V2. For more information, see 3420816 .
• The link COLLABORATION_SFC_COMPONENT_ADD is mapped to the directive ERP_COMPONENT_ADD.
• If you've enabled EWM integration, congure 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.15.1Conguring Floor Stocks
This section describes how to transfer oor stocks from SAP ERP or SAP S/4HANA to SAP Digital
Manufacturing for execution to create corresponding oor stock records in the Manage Floor Stocks app.
Note
You can transfer oor stocks through goods movement types 311 and 261.
228
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Prerequisites
SAP ERP or SAP S/4HANA
• You have created oor stock materials you want to transfer.
• You have created central storage locations and production storage locations for the oor stock materials.
• You have set up ALE communication to create and transmit INVCON03 IDocs.
• You have dened the DRF Replication Model to replicate INVCON03 IDocs. For more information, see Data
Replication Framework [page 36].
SAP Digital Manufacturing
• The oor 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 245]).
• 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 oor stocks. The following is one of the options.
1. Execute the transaction code MIGO to call up the Transfer Posting screen.
2. To transfer oor stocks for general usage, select Transfer Posting with goods movement type 311. If
you want to transfer oor stocks reserved for a specic 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
SAP Digital Manufacturing for execution Integration
PUBLIC 229
2.1.5.2.15.2Updating Integration Conguration to Use Floor
Stock Data
If you want to use oor stock integration functionality in SAP Digital Manufacturing, you need to update some
settings in your conguration 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. Congure 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_INVENTORY_CLEAR_RESERVATION to the collaboration link
COLLABORATION_ERP_INV_CLEAR_RESERVATION for the inventory Return and Scrap activity.
Result
You can now use the oor stock functionality as described in this chapter.
Related Information
Setting Up the Cloud Connector [page 22]
230
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.2.15.3Transfer of Floor Stock Return and Scrap Data
You can transfer oor stock return and scrap data from SAP Digital Manufacturing for execution to SAP ERP or
SAP S/4HANA.
Use
This function lets you transfer oor 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 conguration. For more information,
see Updating Integration Conguration to Use Floor Stock Data [page 230].
1. In SAP Digital Manufacturing, you can trigger the oor 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 oor 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 ow of oor stock return and scrap in SAP Digital Manufacturing which will be
synchronized to ERP for production order-independent oor stock.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 231
• 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-Specic Floor Stock (261) Return (262) and Scrap (551)
The illustration shows the ow of oor stock return and scrap in SAP Digital Manufacturing, which is
synchronized to ERP for production order-independent oor 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 oor 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 oor stock control process for returning inventory and scrap.
232
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Prerequisites
SAP Digital Manufacturing
• You have received oor stock data from SAP ERP or SAP S/4HANA.
• You have veried the pre-dened 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 eld 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 prex RTN-, the component quantity is returned to SAP ERP or SAP S/4HANA
Central Stores. If the reason code has the prex 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 elds in an SAP ERP or SAP S/4HANA system are mapped to what elds in SAP
Digital Manufacturing.
2.1.5.3.1 Inbound Communication
2.1.5.3.1.1Mapping 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 eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Plant (WERKS) plant
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 233
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Material (MATNR_LONG) material
If MATNR_LONG is present, it's selected.
Note
The lot size isn't downloaded
from the integrated SAP ERP or
SAP S/4HANA system. By default,
it's set to -1.000 in SAP Digital
Manufacturing for execution. If a
serial number prole is present, the
lot size is set to 1.
Material (MATNR)
material If MATNR_LONG isn't present, MATNR is
selected.
Procurement Type (BESKZ) procurementType
If BESKZ is 'E', procurementType is 'M'.
If BESKZ is 'F', procurementType is 'P'.
Otherwise, procurementType is 'B'.
Material Type (MTART) materialType
If MTART is in the ERP payload, it's se-
lected.
Material Description (MAKTX) description
If there's a seg-
ment ../E1MAKTM[SPRAS=//
SupportedPlant/Language]/MAKTX
that indicates specic languages, this
string is selected.
Otherwise, the string contained in ../
E1MAKTM/MAKTX is selected.
Note
You can only map material descrip-
tions in languages supported by
SAP Digital Manufacturing. Refer to
2722461
for an overview of sup-
ported languages. If you require a
language that isn't supported, you
can use mediated integration to
transform your message content.
multiLanguageDescriptionDTOList
Complex element that isn't available in
the ERP payload.
The system loops over each E1MAKTM
segment.
234 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Material Description (MAKTX) multiLanguageDescriptionDTO The languageCode attribute of
the multiLanguageDescriptionDTO
eld is set to the SPRAS value of the
corresponding E1MAKTM element.
Base unit of measure (MEINS) unitOfMeasure
Gross weight (BRGEW) grossWeight
Net weight (NTGEW) netWeight
Unit of weight (GEWEI) unitOfWeight
International article number (EAN/
UPC) (EAN11)
ean
Category of international article number
(EAN) (NUMTP)
eanCategory
Batch management requirement
indicator (XCHPF)
incrementBatchNumber If XCHPF is 'X',
incrementBatchNumber is
set to 'ORDER'. Otherwise,
incrementBatchNumber is set to
'NONE'.
MRP controller (DISPO) mrpController
Issue storage location (LGPRO) putawayStorageLocation
If BESKZ is equal to 'E', the eld
putawayStorageLocation is created.
Note
The maximum eld length allowed
in SAP Digital Manufacturing for
execution less than or equal to 4.
Issue storage location (LGPRO)
productionStorageLocation
If BESKZ equals 'F', the eld
productionStorageLocation is cre-
ated.
Note
The maximum eld length allowed
in SAP Digital Manufacturing for
execution less than or equal to 4.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 235
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Issue storage location (LGPRO)
putawayStorageLocation
productionStorageLocation
If BESKZ is neither 'E' nor 'F', the
elds putawayStorageLocation and
productionStorageLocation are
created. Both elds get the value of
LGPRO.
Note
The maximum eld length allowed
in SAP Digital Manufacturing for
execution less than or equal to 4.
Indicator: backush (RGEKZ)
erpBackushing If RGEKZ is '1', erpBackflushing is
set to 'true'. Otherwise, it's set to
'false'.
alternateUomDTOList
Complex element that isn't available in
ERP payload.
The system loops over each E1MARMM
segment.
alternateUomDTO
Complex element that isn't available in
ERP payload.
Numerator for conversion to base units
of measure (UMREZ)
quantity
The quantity eld gets a unitCode
attribute, to which the value of the base
unit of measure (MEINS) is assigned.
Denominator for conversion to base
units of measure (UMREN)
correspondingQuantity
The correspondingQuantity eld
gets a unitCode attribute, to which the
value of the alternative unit of meas-
ure for stockkeeping unit (MEINH) is as-
signed.
Gross weight (BRGEW)
grossWeight
Unit of weight (GEWEI) unitOfWeight
eanList
Complex element that isn't available in
the ERP payload.
The system loops over each E1MEANM
segment.
236 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
International article number (EAN/
UPC) (EAN11)
eanDTO
The eanDTO eld gets a category
attribute, to which the value of the
category of international article num-
ber (EAN) (EANTP) is assigned. It also
gets a mainEanIndicator attribute,
to which the value of the main EAN indi-
cator (HPEAN) is assigned.
Serial number prole (SERNP)
serialNumbProle
Total shelf life (MHDHB) maxShelfLife
Period indicator for shelf life expiration
date (IPRKZ)
maxShelfLifeUnitCode
Related Information
Specifying the Custom Value of Autocomplete and Conrm for a Material
Specifying Data Values for Material Downloading
2.1.5.3.1.2Mapping a Bill of Material (BOM)
Data is transferred from SAP S/4HANA to SAP Digital Manufacturing for execution using the BOMMAT05 IDoc.
This table contains eld names in SAP S/4HANA and their corresponding eld names in SAP Digital
Manufacturing for execution:
SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Plant (WERKS) plant
Material Number (MATNR_EXTERNAL),
BOM usage (STLAN), and Alternative
BOM (STLAL)
bom
If MATNR_EXTERNAL is present, it's se-
lected.
Its value is concatenated with
STLAN (BOM usage) and STLAL
(Alternative BOM): Material-
BOMUsage-AltBOM.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 237
SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Material Number (MATNR_LONG), BOM
usage (STLAN), and Alternative BOM
(STLAL)
bom
If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Its value is concatenated with
STLAN (BOM usage) and STLAL
(Alternative BOM): Material-
BOMUsage-AltBOM.
Material Number (MATNR), BOM usage
(STLAN), and Alternative BOM (STLAL)
bom
If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
Its value is concatenated with
STLAN (BOM usage) and STLAL
(Alternative BOM): Material-
BOMUsage-AltBOM.
BOM description (ZTEXT)
description
If ZTEXT isn't empty, it's selected.
Material Number (MATNR_EXTERNAL) description
If ZTEXT is empty and if there's a mate-
rial number MATNR_EXTERNAL, the ma-
terial number is selected.
Material Number (MATNR_LONG description
If ZTEXT is empty and if there's no
material number MATNR_EXTERNAL,
but there's a material number
(MATNR_LONG), the MATNR_LONG is se-
lected.
Material Number (MATNR)
description
If ZTEXT is empty and if there are no no
material numbers MATNR_EXTERNAL or
MATNR_LONG, the MATNR is selected.
Function (MSGFN) action
If MSGFN is 009, action is set to
Create.
If MSGFN is 005, action is set to
Change.
Bill of Material (STLNR)
erpBom
Bill of material status (STLST)
status
currentVersion
If STLST equals '02', status is set to
'205' and currentVersion is set to
'false'.
Otherwise, status is set to '201' and
currentVersion is set to 'true'.
238 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
bomType
The eld isn't present in the ERP pay-
load. The value set to 'U'.
eectivityControl
The eld isn't present in the ERP pay-
load. The value set to 'R'.
Base quantity (BMENG_C) baseQuantity
Unit of measure for base quantity
(BMEIN)
baseUom
bomComponentDTOList
Complex element that isn't available in
the ERP payload.
The system loops over each E1STPOM
segment and checks if either IDNRK or
IDNRK_LONG contain a value. If this is
the case, the bomComponentDTO sec-
tion is created.
bomComponentDTO
Complex element that isn't available in
the ERP payload.
component
Complex element that isn't available in
the ERP payload.
Long material number for eld IDNRK
(IDNRK_EXTERNAL)
material If IDNRK_EXTERNAL is present, it's se-
lected.
BOM component (IDNRK_LONG) material If IDNRK_EXTERNAL isn't present but
IDNRK_LONG is, IDNRK_LONG is se-
lected.
BOM component (IDNRK) material If neither IDNRK_EXTERNAL nor
IDNRK_LONG is present, IDNRK is se-
lected.
BOM item number (POSNR) sequence
bomComponentType The eld isn't present in the ERP pay-
load. The value set to 'N'.
enabled The eld isn't present in the ERP pay-
load. The value set to 'true'.
Component quantity (MENGE_C) and
Base quantity (BMENG_C)
quantity The quantity is calculated as the divi-
sion of MENGE_C by BMENGE_C.
Component quantity (MENGE_C) totalQtyBaseUom
The system removes leading and trail-
ing white-space from a string and repla-
ces sequences of white-space charac-
ters by a single space.
The system removes all hypens ('-')
from MENGE_C).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 239
SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
useItemDefaults
The eld isn't present in the ERP pay-
load. The value set to 'false'.
preAssembled
The eld isn't present in the ERP pay-
load. The value set to 'false'.
testPart
The eld isn't present in the ERP pay-
load. The value set to 'false'.
Issue location for production order
(LGORT)
storageLocation
Base unit of measure (MEINS) unitOfMeasure
Alternative item: group (ALPGR) alternativeItemGroup
Alternative item: ranking order (ALPRF) alternativeItemPriority
Usage probability in % (alternative item)
(EWAHR)
usageProbability
bomRefDesDTOList
Complex element that isn't available in
the ERP payload.
This eld is created if EBORT is present
in the E1STPUM segment.
bomRefDesDTO
Complex element that isn't available in
the ERP payload.
Installation point for subitem (EBORT) refDes The system transfroms all letters of
EBORT from lowercase to uppercase.
sequence
The eld isn't present in the ERP pay-
load. The value set to '10'.
Subitem quantity (UPMNG_C) and Base
quantity (BMENG_C)
quantity
The quantity is calculated as the divi-
sion of UPMNG_C (from E1STPUM seg-
ment) by BMENG_C (from E1STKOM
segement).
BOM item node number (STLKN)
erpRefDesSequence
BOM sub-item text (UPTXT) description
BOM item number (POSNR) erpSequence
Related Information
Specifying Data Values for BOM Downloading
Specifying Data Values for Order-Specic BOM Components
Specifying Custom Data Fields for BOM Components
240
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Setting Backushing for BOM Components
Setting Custom Data for Master BOMs
Setting Custom Data for Order BOMs
2.1.5.3.1.3Mapping 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
ERP Alternate Item Group
ALPGR
alternates.enabled
Alternates Enabled
TRUE
alternates.priority
Alternates Priority
ALPRF
alternates.material
Alternate Component
IDNRK
Order BOM
ERP / SAP S/4HANA
DME Field Default Value SAP S/4HANA Cloud Field
alternativeItemGroup
ERP Alternate Item Group
ALPGR
alternates.enabled
Alternates Enabled
TRUE
alternates.priority
Alternates Priority
ALPRF
alternates.material
Alternate Component
MATNR
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 241
2.1.5.3.1.4Mapping Installation Points of BOM Components
There may be a collection of sub-items on the SAP ERP side. For each sub-item, a separate BOM component
with a corresponding quantity and installation point elds is created in SAP Digital Manufacturing. Installation
point integration is supported only for production orders that are transferred from SAP S/4HANA.
Master BOM Component
DME Field
Default Value SAP S/4HANA Field
bomRefDesDTO.erpRefDesSequence UPOSZ
Subitem Number
bomRefDesDTO.refDes
Installation Point
EBORT
Installation Point
bomRefDesDTO.quantity
Assembly Quantity
UPMNG
Sub-Item Quantity
bomRefDesDTO.description
Installation Point Description
UPTXT
Sub-Item Text
Order BOM
DME Field
Default Value SAP S/4HANA Cloud Field
ZBOMSubItem.ZBOMSubItemNumberV
alue
UPOSZ
ZBOMSubItem.ZBOMSubItemInstall
ationPoint
Installation Point
EBORT
ZBOMSubItem.ZBillOfMaterialSub
ItemQuantity
Assembly Quantity
UPMNG
ZBOMSubItem.ZBillOfMaterialSub
ItemText
Installation Point Description
UPTXT
242 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.3.1.5Mapping 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 eld
names in SAP ERP and their corresponding eld names in SAP Digital Manufacturing for execution:
SAP ERP
SAP Digital Manufacturing for
execution Comment
Plant (WERKS) Plant
Key for Task List Group (PLNNR);
Group Counter (PLNAL) or /E1AFREF/
MES_ROUTINGID
Routing
PLNNR + “-” + PLNAL
/E1AFREF/MES_ROUTINGID if the
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
Eectivity Control R No logic in SAP Digital Manufacturing
for execution yet.
Current Version Selected
Key for Task List Group (PLNNR);
Group Counter (PLNAL)
Entry Routing
Entry Routing Type
U
Entry Routing Step ID
10
Key for Task List Group (PLNNR);
Group Counter (PLNAL); Sequence
(PLNFL); Operation (VORNR) or
ME_OPERATION_ID or UVORN
Operation Activity
PLNNR + “-” + PLNAL + “-”
+ PLNFL + “-” + VORNR or
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 243
SAP ERP
SAP Digital Manufacturing for
execution Comment
Rework Deselected
Sequence (FLAGAT) Data eld: ERP_SEQUENCE 0. Only a zero sequence routing is sup-
ported.
Key for Task List Group (PLNNR),
Group Counter (PLNAL), Sequence
(PLNFL), Operation (VORNR) or
ME_OPERATION_ID or UVORN
Operation Activity Operation activity master name
Note
Operation activity master records
can be created from the integration
as specied 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 nds 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.
Key for Task List Group (PLNNR),
Group Counter (PLNAL), Sequence
(PLNFL), Operation (VORNR) or
ME_OPERATION_ID
Operation Group
PLNNR + “-” + PLNAL + “-”
+ PLNFL + “-” + VORNR or
ME_OPERATION_ID
Operation Short Text (LTXA1) Description Routing step description
Operation Short Text (LTXA1) Description Operation activity description
244 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP
SAP Digital Manufacturing for
execution Comment
Document number (DOKNR)
Document Type (DOKAR)
Document Part (DOKTL)
Application number (ORIGINAL)
Work Instruction
DOKNR + ‘-’ + DOKAR + ‘-’
+DOKTL + ‘-’ + ORIGINAL
Document Version (DOKVR) Version
2.1.5.3.1.6Mapping a Production Order
You transfer production production order data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing
for execution using the IDoc LOIPRO05 Production Order V2.
This table contains eld names in SAP ERP or SAP S/4HANA and the corresponding eld names in SAP Digital
Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
ManufacturingOrder
Complex element that isn't available in
the ERP payload.
Order number (AUFNR) ManufacturingOrder
Order category (AUTYP) ManufacturingOrderCategory
Order type (AUART) ManufacturingOrderType
Plant (WERKS) ProductionPlant
Material number (MATNR_EXTERNAL) material If MATNR_EXTERNAL is present, it's se-
lected.
Material number (MATNR_LONG) material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material number (MATNR) material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
BOM category (STLTY) BillOfMaterialCategory
Bill of material (STLNR) BillOfMaterial
Alternative BOM (STLAL) BillOfMaterialVariant
BOM usage (STLAN) BillOfMaterialVariantUsage
Task list type (PLNTY) BillOfOperationsType
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 245
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Key for task list group (PLNNR) BillOfOperationsGroup
Group counter (PLNAL) BillOfOperationsVariant
Total order quantity (GAMNG) MfgOrderPlannedTotalQty
The MfgOrderPlannedTotalQty eld
gets a pp:unitCode attribute, to which
the value of the common unit of meas-
ure for all order items (GMEIN) is as-
signed.
Base quantity (BMENGE)
MfgOrdPlndTotQtyInBaseUnit
The MfgOrdPlndTotQtyInBaseUnit
eld gets a pp:unitCode attribute, to
which the value of the base unit of
measure (BMEINS) is assigned.
Minimum lot size (PLSVN)
BOOMinLotSizeQuantity
The BOOMinLotSizeQuantity eld
gets a pp:unitCode attribute, to which
the value of the task list unit of measure
(PLNME) is assigned.
Maximum lot size (PLSVB)
BOOMaxLotSizeQuantity
The BOOMaxLotSizeQuantity eld
gets a pp:unitCode attribute, to which
the value of the task list unit of measure
(PLNME) is assigned.
Basic start date (GSTRP)
MfgOrderPlannedStartDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Basic start (time) (GSUZP) MfgOrderPlannedStartTime
If GSUZP isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Basic nish date (GLTRP)
MfgOrderPlannedEndDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Basic nish (time) (GLUZP) MfgOrderPlannedEndTime
If GLUZP isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Scheduled start (GSTRS)
MfgOrderScheduledStartDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Scheduled start (time) (GSUZS) MfgOrderScheduledStartTime
If GSUZS isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
246 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Scheduled nish (GLTRS) MfgOrderScheduledEndDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Scheduled nish time (GLUZS) MfgOrderScheduledEndTime
If GLUZS isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Inspection lot number (PRUEFLOS)
InspectionLot If PRUEFLOS isn't empty and isn't zero,
it's selected. Leading zeros are added to
PRUEFLOS until 12 places are reached.
Scheduling type (TERKZ) ZSchedulingType
Priority of vacancy assignment (APRIO) Priority
Language (TDSPRAS) LongText
If the E1AFLTH segment is present, the
LongText element is created.
The LongText eld gets a
pp:MIMECode attribute, which has
the value 'application/json', and a
pp:TextCategory attribute, to which
the value of the SAPscript format
of text (TDTEXTTYPE) from the rst
E1AFLTH segment found is assigned.
The LongText eld gets the value of
TDSPRAS, which is converted as follows:
• 'E' becomes 'EN'
• '1' becomes 'ZH'
• 'D' becomes 'DE'
• 'H' becomes 'HU'
• '3' becomes 'KO'
• 'F' becomes 'FR'
• 'S' becomes 'ES'
• 'M' becomes 'ZF'
• 'J' becomes 'JA'
Additionally, the system loops over
each E1AFLTP segment that is a child
of the rst E1AFLTH segment. It cre-
ates a json object that contains the
tag column (TDFORMAT) and text
line (TDLINE) values and has this
structure: [{"TDFORMAT": "tag column
","TDLINE":"text line", ...}].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 247
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ManufacturingOrderSystemStatus
Complex element that isn't available in
the ERP payload.
Object status (STAT) pp:OrderHasGeneratedOperations
If the object status (STAT) in E1JSTKL
is equal to 'I0328', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsClosed
If the object status (STAT) in E1JSTKL
is equal to 'I0046', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsConrmed
If the object status (STAT) in E1JSTKL
is equal to 'I0009', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsCreated
If the object status (STAT) in E1JSTKL
is equal to 'I0001', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsDeleted
If the object status (STAT) in E1JSTKL
is equal to 'I0013', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsDelivered
If the object status (STAT) in E1JSTKL
is equal to 'I0012', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsLocked
If the object status (STAT) in E1JSTKL
is equal to 'I0043', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsMarkedForDeletion
If the object status (STAT) in E1JSTKL
is equal to 'I0076', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsPartiallyConrmed
If the object status (STAT) in E1JSTKL
is equal to 'I0010', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsPartiallyDelivered
If the object status (STAT) in E1JSTKL
is equal to 'I0074', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsPartiallyReleased
If the object status (STAT) in E1JSTKL
is equal to 'I0042', the eld is created
and the value is set to 'true'.
248 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Object status (STAT) pp:OrderIsPreCosted
If the object status (STAT) in E1JSTKL
is equal to 'I0016', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsPrinted
If the object status (STAT) in E1JSTKL
is equal to 'I0007', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsReleased
If the object status (STAT) in E1JSTKL
is equal to 'I0002', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsScheduled
If the object status (STAT) in E1JSTKL
is equal to 'I0117', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsTechnicallyCompleted
If the object status (STAT) in E1JSTKL
is equal to 'I0045', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsToBeHandledInBatches
If the object status (STAT) in E1JSTKL
is equal to 'I0369', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:SettlementRuleIsCreated
If the object status (STAT) in E1JSTKL
is equal to 'I0028', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:SettlementRuleIsCrtedManually
If the object status (STAT) in E1JSTKL
is equal to 'I0102', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:MaterialAvailyIsNotChecked
If the object status (STAT) in E1JSTKL
is equal to 'I0420', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderChangeIsRestricted
If the object status (STAT) in E1JSTKL
is equal to 'I0667', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderHasNoMaterialComponents
If the object status (STAT) in E1JSTKL
is equal to 'I0239', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderHasPostedGoodsMovements
If the object status (STAT) in E1JSTKL
is equal to 'I0321', the eld is created
and the value is set to 'true'.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 249
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Object status (STAT) pp:OrderIsDistributedToMES
If the object status (STAT) in E1JSTKL
is equal to 'I0048', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsHandedOverToProduction
If the object status (STAT) in E1JSTKL
is equal to 'I0666', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:OrderIsShopFloorOrder
If the object status (STAT) in E1JSTKL
is equal to 'I0665', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:MaterialIsCommitted
If the object status (STAT) in E1JSTKL
is equal to 'I0340', the eld is created
and the value is set to 'true'.
ManufacturingOrderItem
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFPOL
segment.
Order item number (POSNR)
ManufacturingOrderItem
Material number (MATNR_EXTERNAL) Material If MATNR_EXTERNAL is present, it's se-
lected.
Material number (MATNR_LONG) Material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material number (MATNR) Material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
Order item planned total quantity
(PSMNG)
MfgOrderItemPlannedTotalQty
The
MfgOrderItemPlannedTotalQty
eld gets a pp:unitCode attrib-
ute, to which the value of the
unit of measure for in-house
production (AMEIN) is assigned.
Batch number (CHARG)
Batch
Production version (VERID) ProductionVersion
Storage location (LGORT) StorageLocation
Warehouse number / warehouse
complex (LGNUM)
Warehouse
250 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
MfgOrderSerialNumbers
Complex element that isn't available in
the ERP payload.
It's created if a segment 'E1AFSER' is
present.
MfgOrderSerialNumber
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFSER
segment.
Serial number (SERNR)
SerialNumber
Unique item identier (UII) UniqueItemIdentier
GoodsReceiptTolerances
Complex element that isn't available in
the ERP payload.
Underdelivery tolerance (UNTTO) pp:UnderdelivTolrtdLmtRatioInPct
Unlimited overdelivery allowed (UEBTK) pp:UnlimitedOverdeliveryIsAllowed
If UEBTK is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Overdelivery tolerance (UEBTO) pp:OverdelivTolrtdLmtRatioInPct
ManufacturingOrderActivityNetworkEle
ment
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFVOL
element and choses it only if the last
E1JSTVL child element contains an ob-
ject status (STAT) child element that
isn't equal to 'I0013'.
The system creates this eld and the
elds below only if this condition is met.
pp:MfgOrderNodeType
This element isn't available in the ERP
payload. Its value is set to 'Operation'.
Operation/activity number (VORNR) pp:MfgOrderNodeID
The value of VORNR is concatenated
with 'OP'. Example: 'OP1234'
pp:OrderInternalBillOfOperations
Element that isn't available in the ERP
payload and that is empty.
Operation/activity number (VORNR) pp:OrderIntBillOfOperationsItem
Operation/activity number (VORNR) pp:ManufacturingOrderOperation
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 251
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Minimum send-ahead quantity (MINWE) pp:ZMinimumSendAheadQuantity
The
pp:ZMinimumSendAheadQuantity
eld gets a pp:unitCode attribute,
to which the value of the unit of
measure for activity (MEINH) is
assigned.
Unit for the minimum overlap time
(ZMINU)
pp:ZMinimumOverlapTime
The pp:ZMinimumOverlapTime eld
gets a pp:unitCode attribute, to which
the value of the unit for the
minimum overlap time (ZEIMU) is
assigned.
Optional overlapping (UEKAN)
pp:ZOptionalOverlapping
If UEKAN is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Required Overlapping (UEMUS) pp:ZRequiredOverlapping
If UEMUS is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Flow manufacturing (FLIES) pp:ZFlowManufacturing
If FLIES is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Sequence (PLNFL) pp:ManufacturingOrderSequence
Work center (ARBPL) pp:WorkCenter
Work Center ID (ARBID) pp:WorkCenterInternalID
Operation total quantity (MGVRG) pp:OpPlannedTotalQuantity
The pp:OpPlannedTotalQuantity
eld gets a pp:unitCode attribute,
to which the value of the unit of
measure for activity (MEINH) is
assigned.
Base quantity (BMSCH)
pp:OperationReferenceQuantity
The
pp:OperationReferenceQuantity
eld gets a pp:unitCode attribute,
to which the value of the unit of
measure for activity (MEINH) is
assigned.
Operation short text (LTXA1)
pp:MfgOrderOperationText
Operation short text (LTXA1) pp:MfgOrderSequenceText
Factory calendar (KALID) pp:FactoryCalendar
Earliest scheduled start: execution
(date) (FSAVD)
pp:OpErlstSchedldExecStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
252 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Earliest scheduled start: execution
(time) (FSAVZ)
pp:OpErlstSchedldExecStrtTme
If FSAVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest scheduled nish: execution
(date) (FSEDD)
pp:OpErlstSchedldExecEndDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest scheduled nish: execution
(time) (FSEDZ)
pp:OpErlstSchedldExecEndTme
If FSEDZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: execution (date)
(SSAVD)
pp:OpLtstSchedldExecStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled start: execution (time)
(SSAVZ)
pp:OpLtstSchedldExecStrtTme
If SSAVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled nish: execution (date)
(SSEDD)
pp:OpLtstSchedldExecEndDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled nish: execution (time)
(SSEDZ)
pp:OpLtstSchedldExecEndTme
If SSEDZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest nish of operation (date)
(FSEVD)
pp:EarliestFinishOfOperationDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest nish of operation (time)
(FSEVZ)
pp:EarliestFinishOfOperationTime
If FSEVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest scheduled start: processing
(date) (FSSBD)
pp:OpErlstSchedldProcgStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest Scheduled Start: processing
(time) (FSSBZ)
pp:OpErlstSchedldProcgStrtTme
If FSSBZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: processing
(date) (SSSBD)
pp:OpLtstSchedldProcgStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 253
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Latest scheduled start: processing
(time) (SSSBZ)
pp:OpLtstSchedldProcgStrtTme
If SSSBZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Processing time (BEARZ)
pp:OpPlannedProcessingDurn
The OpPlannedProcessingDurn eld
gets a unitCode attribute, to which
the value of the unit of measure
for processing time (BEAZE) is as-
signed.
Earliest scheduled start: teardown
(date) (FSSAD)
pp:OpErlstSchedldTrdwnStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest scheduled start: teardown
(time) (FSSAZ)
pp:OpErlstSchedldTrdwnStrtTme
If FSSAZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: teardown (date)
(SSSAD)
pp:OpLtstSchedldTrdwnStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled start: teardown (time)
(SSSAZ)
pp:OpLtstSchedldTrdwnStrtTme
If SSSAZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled wait end date (SSELD)
pp:LatestScheduledWaitEndDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled wait end time (SSELZ) pp:LatestScheduledWaitEndTime
If SSELZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Setup time (RUEST)
pp:OpPlannedSetupDurn
The OpPlannedSetupDurn eld gets a
unitCode attribute, to which the value
of the unit of measure for setup
time (RSTZE) is assigned.
Teardown (ABRUE)
pp:OpPlannedTeardownDurn
The OpPlannedTeardownDurn eld
gets a unitCode attribute, to which the
value of the unit of measure for
teardown (ARUZE) is assigned.
254 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Teardown (ABRUE) pp:ScheduledWaitDuration
The ScheduledWaitDuration eld
gets a unitCode attribute, to which the
value of the unit of measure for
teardown (ARUZE) is assigned.
Teardown and wait occur in parallel
(ABLIPKZ)
pp:TeardownAndWaitIsParallel
If ABLIPKZ is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
pp:MfgOrderConrmationGroup
Element that isn't available in the ERP
payload and that is empty.
pp:OperationControlProle
Complex element that isn't available in
the ERP payload.
It gets a pp:OperationControlKey
attribute, to which the value of the
control key (STEUS) is assigned.
pp:CompletionConrmation
Complex element that isn't available in
the ERP payload.
It gets a
pp:CompletionConfirmationCode
attribute, to which the value of the
confirmation (RUEK) is assigned.
Conrmation (RUEK)
ConrmationIsMilestoneConf
If RUEK is '1', the eld is set to 'true',
otherwise it's set to 'false'.
Conrmation (RUEK) ConrmationIsRequired
If RUEK is '2', the eld is set to 'true',
otherwise it's set to 'false'.
Conrmation (RUEK) ConrmationIsNotPossible
If RUEK is '3', the eld is set to 'true',
otherwise it's set to 'false'.
Conrmation (RUEK) ConrmationIsOptional
If RUEK contains an empty string, a
space, or a '0', or if it isn't present, the
eld is set to 'true', otherwise it's set
to 'false'.
Indicator: scheduling (TERM)
pp:OperationIsScheduled
If TERM is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Indicator: determine capacity
requirements (KAPA)
pp:CapacityRequirementsAreDtmnd
If KAPA is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Indicator: post goods receipt
automatically (AUTWE)
pp:GRIsPostedAutomatically
If AUTWE is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 255
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Not relevant for external manufacturing
execution system (NOT_MES_REL)
pp:OperationIsNotMESRelevant
If NOT_MES_REL is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
pp:StandardWorkFormulaParamGroup
Complex element that isn't available in
the ERP payload.
It gets a
StandardWorkFormulaParamGroupI
D attribute, to which the value of the
standard value key (VGWTS) is as-
signed.
The subelements of this element are
created depending on conditions.
WorkCenterFormulaParam1
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE01 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR01_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
Standard value (VGW01) WorkCenterStandardWorkQty
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measurement of standard value
(VGE01) is assigned.
Activity type (LAR01)
CostCtrActivityType
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY1)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM1) is as-
signed.
256 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
WorkCenterFormulaParam2
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE02 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR02_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
Standard value (VGW02) WorkCenterStandardWorkQty
The eld gets a pp:unitCode attribute,
to which the value of the unit of
measurement of standard value
(VGE02) is assigned.
Activity type (LAR02)
CostCtrActivityType
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY2)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM2) is as-
signed.
WorkCenterFormulaParam3
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE03 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR03_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
Standard value (VGW03) WorkCenterStandardWorkQty
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measurement of standard value
(VGE03) is assigned.
Activity type (LAR03)
CostCtrActivityType
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 257
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY3)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM3) is as-
signed.
WorkCenterFormulaParam4
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE04 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR04_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
Standard value (VGW04) WorkCenterStandardWorkQty
The eld gets a unitCode attribute,
to which the value of the unit of
measurement of standard value
(VGE04) is assigned.
Activity type (LAR04)
CostCtrActivityType
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY4)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM4) is as-
signed.
WorkCenterFormulaParam5
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE05 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR05_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
258 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Standard value (VGW05) WorkCenterStandardWorkQty
The eld gets a unitCode pp:attribute,
to which the value of the unit of
measurement of standard value
(VGE05) is assigned.
Activity type (LAR05)
CostCtrActivityType
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY5)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM5) is as-
signed.
WorkCenterFormulaParam6
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE06 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Keyword for parameter ID
(PAR06_LTXT)
StandardWorkFormulaParamName
The eld gets a languageCode attrib-
ute that is empty.
Standard value (VGW06) WorkCenterStandardWorkQty
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measurement of standard value
(VGE06) is assigned.
Activity type (LAR06)
CostCtrActivityType
Total activity to be conrmed
(TO_BE_CONF_ACTIVITY6)
ToBeConrmedTotalWorkQty The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
total activity to be confirmed
value (TO_BE_CONF_ACT_UOM6) is as-
signed.
pp:ManufacturingOrderComponent
Complex element that isn't available in
the ERP payload.
The system loops over each E1RESBL
segment.
Requirement type (BDART)
RequirementType
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 259
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Requirement quantity (BDMNG) RequiredQuantityInBaseUnit
The eld gets a pp:unitCode attrib-
ute, to which the value of the base
unit of measurement (MEINS) is as-
signed.
Requirements date for the component
(BDTER)
MatlCompRequirementDate
If BDTER isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Batch number (CHARG)
Batch
Material number (MATNR_EXTERNAL) material If MATNR_EXTERNAL is present, it's se-
lected.
Material number (MATNR_LONG) material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material number (MATNR) material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
Number of reservation/dependent
requirements (RSNUM)
Reservation
Item number of reservation / dependent
requirements (RSPOS)
ReservationItem
Movement type (inventory
management) (BWART)
GoodsMovementType
BOM item number (POSNR) BillOfMaterialItemNumber
Item category (bill of material) (POSTP) BillOfMaterialItemCategory
Order item number (AFPOS) ManufacturingOrderItem
Bill of material (STLNR) BillOfMaterial
BOM item node number (STLKN) BillOfMaterialItemNodeNumber
Production supply area (PRVBE) SupplyArea
Storage location (LGORT) StorageLocation
Warehouse number / warehouse
complex (LGNUM)
Warehouse
Indicator: backush (BACKFLUSH) MatlCompIsMarkedForBackush
If BACKFLUSH is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Indicator: co-product (KZKUP) MaterialIsCoProduct
If KZKUP is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Debit/credit indicator (SHKZG) DebitCreditCode
Special stock indicator (SOBKZ) InventorySpecialStockType
260 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Alternative item indicator (ALPOS) MaterialCompIsAlternativeItem
If ALPOS is 'X', the eld is set to 'true'.
Otherwise, it's set to 'false'.
Alternative item: group (ALPGR) AlternativeItemGroup
Alternative item: ranking order (ALPRF) AlternativeItemPriority
Alternative item: strategy (ALPST) AlternativeItemStrategy
Usage probability in % (alternative item)
(EWAHR)
UsageProbabilityPercent
ZBOMSubItem
Complex element that isn't available in
the ERP payload.
The system loops over each E1STPUL
segment.
Subitem number (UPOSZ)
ZBOMSubItemNumberValue
Installation point for subitem (EBORT) ZBOMSubItemInstallationPoint
BOM sub-item text (UPTXT) ZBillOfMaterialSubItemText
Sub-item quantity (UPMNG) ZBillOfMaterialSubItemQuantity
pp:ManufacturingOrderInspCharc
Complex element that isn't available in
the ERP payload.
The system loops over each E1QAMVL
segment.
Insp. lot charac. no. (INSPCHAR)
InspectionCharacteristic
Short text for the inspection
characteristic (CHAR_DESCR)
InspectionSpecicationText
Characteristic type (CHAR_TYPE) InspSpecCharacteristicType
Required conrmation for inspection
characteristic (OBLIGATORY)
InspSpecCharcCategory
Single results (SINGLE_RES) InspSpecRecordingType
Inspection scope (SCOPE) InspCharacteristicSampleSize
The eld gets a pp:unitCode at-
tribute, to which the value of the
base unit of measure for the
inspection lot (SMPL_UNIT) is as-
signed.
Inspection scope (SCOPE_IND)
InspectionScope
Documentation required for inspection
results (DOCU_REQU)
InspResultIsDocumentationRqd
If DOCU_REQU is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Number of decimal places
(DEC_PLACES)
InspSpecDecimalPlaces
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 261
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Target value (TARGET_VAL) InspSpecTargetValue
The eld gets a unitCode attribute,
to which the value of the unit
of measurement (internal code)
(MEAS_UNIT) is assigned.
Lower tolerance limit (LW_TOL_LMT)
InspSpecLowerLimit
The eld gets a unitCode attribute,
to which the value of the unit
of measurement (internal code)
(MEAS_UNIT) is assigned.
Upper tolerance limit (UP_TOL_LMT)
InspSpecUpperLimit
The eld gets a unitCode attribute,
to which the value of the unit
of measurement (internal code)
(MEAS_UNIT) is assigned.
Plausibility limit (lower) (LW_PLS_LMT)
InspSpecLowerPlausibilityLimit
The eld gets a unitCode attribute,
to which the value of the unit
of measurement (internal code)
(MEAS_UNIT) is assigned.
Plausibility limit (upper) (UP_PLS_LMT)
InspSpecUpperPlausibilityLimit
The eld gets a unitCode attribute,
to which the value of the unit
of measurement (internal code)
(MEAS_UNIT) is assigned.
Catalog type (CAT_TYPE1)
CharacteristicAttributeCatalog
Selected set (SEL_SET1) SelectedCodeSet
Plant for selected set (PSEL_SET1) SelectedCodeSetPlant
Info eld 1 from the characteristic
(INFOFIELD1)
InspSpecInformationField1
Info eld 2 from the characteristic
(INFOFIELD2)
InspSpecInformationField2
Info eld 3 from the characteristic
(INFOFIELD3)
InspSpecInformationField3
Defects recording automatically called
up (FEHLREC)
InspSpecIsDefectsRecgAutomatic
If FEHLREC is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Serial number to be recorded in QM
subsystem (SERIALREQU)
InspLotIsSerialNumberRequired
If SERIALREQU is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Valuation type for sample for QM
subsystems (VALN_TYPE)
InspCharcSampleValuationType
262 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
pp:LongText
The eld isn't present in the ERP pay-
load and gets the following attributes:
• pp:languageCode, which is
empty
• pp:MIMECode, which is set to
'text/plain'
• pp:TextCategory, which is
empty
pp:ActivityNetworkElementSystemStatu
s
Complex element that isn't available in
the ERP payload.
The elements on the level below are
created only if the respective conditions
are met.
Object status (STAT)
pp:CreatedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0001', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:ReleasedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0002', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:PrintedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0007', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:ConrmedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0009', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:PrtlyConrmedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0010', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:DeletedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0013', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:TechlyCompletedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0045', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:ClosedStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0046', the eld is created
and the value is set to 'true'.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 263
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Object status (STAT) pp:ScheduledStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0117', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:PrtlyDeliveredStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0074', the eld is created
and the value is set to 'true'.
Object status (STAT) pp:DeliveredStatusIsActive
If the object status (STAT) in E1JSTVL
is equal to 'I0012', the eld is created
and the value is set to 'true'.
pp:ManufacturingOrderMESReference
Complex element that isn't available in
the ERP payload.
Operation (SAP ME)
(ME_OPERATION_ID)
pp:MESOperation
Version (SAP ME) (ME_REVISION) pp:MESObjectVersion
ManufacturingOrderActivityNetworkEle
ment
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFUVL
element and choses it only if the last
E1JSTUL child element contains an ob-
ject status (STAT) child element that
isn't equal to 'I0013'.
The system creates this eld and the
elds below only if this condition is met.
pp:MfgOrderNodeType
The element isn't available in the
ERP payload. Its value is set to
'Suboperation'.
Operation/Activity Number (VORNR)
and Suboperation (UVORN)
pp:MfgOrderNodeID The value of VORNR, and the value of
UVORN are concatenated and get the
prex 'SUBOP'. For example: SUBOP-
VORNR-UVORN.
pp:OrderInternalBillOfOperations
The element isn't available in the ERP
payload.
Suboperation (UVORN) pp:OrderIntBillOfOperationsItem
Suboperation (UVORN) pp:ManufacturingOrderOperation
Minimum send-ahead quantity (MINWE) pp:ZMinimumSendAheadQuantity
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measure for activity (MEINH) is
assigned.
264 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Minimum overlap time (ZMINU) pp:ZMinimumOverlapTime
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit
for the minimum overlap Time
(ZEIMU) is assigned.
Sequence (PLNFL)
pp:ManufacturingOrderSequence
Object ID of the resource (ARBID) pp:WorkCenterInternalID
Operation total quantity (MGVRG) pp:OpPlannedTotalQuantity
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measure for activity (MEINH) is
assigned.
Base quantity (BMSCH)
pp:OperationReferenceQuantity
The eld gets a pp:unitCode attrib-
ute, to which the value of the unit of
measure for activity (MEINH) is
assigned.
Operation short text (LTXA1)
pp:MfgOrderOperationText The system selects the LTXA1 value of
the current segment.
Operation short text (LTXA1) pp:MfgOrderSequenceText The system selects the LTXA1 value of
the parent node.
Factory calendar (KALID) pp:FactoryCalendar
Earliest scheduled start: execution
(date) (FSAVD)
pp:OpErlstSchedldExecStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest scheduled start: execution
(time) (FSAVZ)
pp:OpErlstSchedldExecStrtTme
If FSAVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest scheduled nish: execution
(date) (FSEDD)
pp:OpErlstSchedldExecEndDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest scheduled nish: execution
(time) (FSEDZ)
pp:OpErlstSchedldExecEndTme
If FSEDZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: execution (date)
(SSAVD)
pp:OpLtstSchedldExecStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled start: execution (time)
(SSAVZ)
pp:OpLtstSchedldExecStrtTme
If SSAVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 265
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Latest scheduled nish: execution (date)
(SSEDD)
pp:OpLtstSchedldExecEndDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled nish: execution (time)
(SSEDZ)
pp:OpLtstSchedldExecEndTme
If SSEDZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest nish of operation (date)
(FSEVD)
pp:EarliestFinishOfOperationDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest nish of operation (time)
(FSEVZ)
pp:EarliestFinishOfOperationTime
If FSEVZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Earliest scheduled start: processing
(date) (FSSBD)
pp:OpErlstSchedldProcgStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest Scheduled Start: processing
(time) (FSSBZ)
pp:OpErlstSchedldProcgStrtTme
If FSSBZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: processing
(date) (SSSBD)
pp:OpLtstSchedldProcgStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled start: processing
(time) (SSSBZ)
pp:OpLtstSchedldProcgStrtTme
If SSSBZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Processing time (BEARZ)
pp:OpPlannedProcessingDurn
The eld gets a unitCode attribute,
to which the value of the unit of
measure for processing time
(BEAZE) is assigned.
Earliest scheduled start: teardown
(date) (FSSAD)
pp:OpErlstSchedldTrdwnStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Earliest scheduled start: teardown
(time) (FSSAZ)
pp:OpErlstSchedldTrdwnStrtTme
If FSSAZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled start: teardown (date)
(SSSAD)
pp:OpLtstSchedldTrdwnStrtDte
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
266 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Latest scheduled start: teardown (time)
(SSSAZ)
pp:OpLtstSchedldTrdwnStrtTme
If SSSAZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Latest scheduled wait end date (SSELD)
pp:LatestScheduledWaitEndDate
The date from the iDoc is transformed
into this format: YYYY-MM-DD.
Latest scheduled wait end time (SSELZ) pp:LatestScheduledWaitEndTime
If SSELZ isn't empty and isn't equal
to '000000', the time from the
iDoc is transformed into this format:
hh:mm:ss.
Setup time (RUEST)
pp:OpPlannedSetupDurn
The eld gets a unitCode attribute,
to which the value of the unit of
measure for setup time (RSTZE)
is assigned.
Teardown (ABRUE)
pp:OpPlannedTeardownDurn
The eld gets a unitCode attribute,
to which the value of the unit of
measure for teardown (ARUZE) is
assigned.
Teardown (ABRUE)
pp:ScheduledWaitDuration
The eld gets a unitCode attribute,
to which the value of the unit of
measure for teardown (ARUZE) is
assigned.
pp:TeardownAndWaitIsParallel
The element isn't available in the ERP
payload and is empty.
pp:MfgOrderConrmationGroup
The element isn't available in the ERP
payload and is empty.
pp:OperationControlProle
The element isn't available in the ERP
payload and is empty.
The eld gets a
pp:OperationControlKey attribute,
to which the value of the control key
(STEUS) is assigned.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 267
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
StandardWorkFormulaParamGroup
Complex element that isn't available in
the ERP payload.
The eld gets a
StandardWorkFormulaParamGroupI
D attribute, to which the value of the
standard value key (VGWTS) is as-
signed.
WorkCenterFormulaParam1
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE01 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Standard value (VGW01)
WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE01) is assigned.
Activity type (LAR01)
CostCtrActivityType
WorkCenterFormulaParam2
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE02 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Standard value (VGW02)
WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE02) is assigned.
Activity type (LAR02)
CostCtrActivityType
268 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
WorkCenterFormulaParam3
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE03 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Standard value (VGW03)
WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE03) is assigned.
Activity type (LAR03)
CostCtrActivityType
WorkCenterFormulaParam4
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE04 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Standard value (VGW04)
WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE04) is assigned.
Activity type (LAR04)
CostCtrActivityType
WorkCenterFormulaParam5
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE05 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 269
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Standard value (VGW05) WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE05) is assigned.
Activity type (LAR05)
CostCtrActivityType
WorkCenterFormulaParam6
Complex element that isn't available in
the ERP payload.
This element and the elements on the
level below are created if unit of
measurement of standard value
VGE06 isn't empty.
This element gets a
WorkCenterFormulaParamID attrib-
ute that is empty.
Standard value (VGW06)
WorkCenterStandardWorkQty
This element gets a pp:unitCode at-
tribute, to which the value of the unit
of measurement of standard
value (VGE06) is assigned.
Activity type (LAR06)
CostCtrActivityType
pp:LongText
The eld isn't present in the ERP pay-
load and gets the following attributes:
• pp:languageCode, which is
empty
• pp:MIMECode, which is set to
'text/plain'
• pp:TextCategory, which is
empty
pp:ActivityNetworkElementSystemStatu
s
Complex element that isn't available in
the ERP payload.
Object status (STAT) pp:CreatedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0001'.
Object status (STAT) pp:ReleasedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0002'.
270 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Object status (STAT) pp:PrintedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0007'.
Object status (STAT) pp:ConrmedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0009'.
Object status (STAT) pp:PrtlyConrmedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0010'.
Object status (STAT) pp:DeletedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0013'.
Object status (STAT) pp:TechlyCompletedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0045'.
Object status (STAT) pp:ClosedStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0046'.
Object status (STAT) pp:ScheduledStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0117'.
Object status (STAT) pp:PrtlyDeliveredStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0074'.
Object status (STAT) pp:DeliveredStatusIsActive
The eld is created and set to 'true' if
STAT in segment E1JSTUL is equal to
'I0012'.
pp:ManufacturingOrderMESReference
Complex element that isn't available in
the ERP payload.
Operation (SAP ME)
(ME_OPERATION_ID)
pp:MESOperation
Version (SAP ME) (ME_REVISION) pp:MESObjectVersion
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 271
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ManufacturingOrderRelationship
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFVOL
element and choses it only if the
last E1JSTVL child element contains
an object status (STAT) child ele-
ment that isn't equal to 'I0013'. The
E1AFVOL segments are arranged in
ascending order based on the value
of the operation/activity number
(VORNR).
PredecessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is '1', the eld is set to
'StartEvent'. Otherwise, it's set to
'Operation'.
Order number (AUFN) or operation/
activity number (VORNR)
PredecessorMfgOrderNodeID
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is '1', the eld receives the value
of AUFN from the E1AFKOL segment
combined with the string 'SEVT'. For
example, 123456789012SEVT. Other-
wise, the eld receives the combination
of the string 'OP' and the value of VORNR
from the previous E1AFVOL. For exam-
ple, OP1234.
SuccessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is '1', the eld is set to
'Operation'. Otherwise, the eld is set
to 'Operation' as well.
Operation/activity number (VORNR)
SuccessorMfgOrderNodeID
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is '1' or isn't '1', the eld receives
the combination of the string 'OP' and
the value of VORNR from the current
segment. For example: OP1234.
272 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
NetworkActivityRelationType
The eld isn't present in the ERP pay-
load.
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is '1' or isn't '1', the eld is set
to 'SucRel'.
ManufacturingOrderRelationship
Complex element that isn't available in
the ERP payload.
If the position of the current E1AFVOL
segment in the list of E1AFVOL seg-
ments is 'last', this element and it's
subelements are created.
PredecessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
The eld is set to 'Operation'.
operation/activity number (VORNR)
PredecessorMfgOrderNodeID
The eld receives the combination of
the string 'OP' and the value of VORNR.
For example, OP1234.
SuccessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
The eld is set to 'EndEvent'.
Order number (AUFNR)
SuccessorMfgOrderNodeID The eld receives the combination of
the value of AUFNR from the E1AFKOL
segment and the string 'EEVT'. For ex-
ample: 123456789012EEVT.
NetworkActivityRelationType
The eld isn't present in the ERP pay-
load.
The eld is set to 'SucRel'.
ManufacturingOrderRelationship
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFUVL
element and choses it only if the last
E1JSTUL child element contains an ob-
ject status (STAT) child element that
isn't equal to 'I0013'. The E1AFUVL
segments are arranged in ascending
order based on the value of the
suboperation (UVORN).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 273
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
PredecessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
The eld is set to 'Operation'.
operation/activity number (VORNR)
PredecessorMfgOrderNodeID
The eld receives the combination of
the string 'OP' and the value of VORNR.
For example, OP1234.
SuccessorMfgOrderNodeType
The eld isn't present in the ERP pay-
load.
The eld is set to 'Suboperation'.
Suboperation (UVORN)
SuccessorMfgOrderNodeID The eld receives the combination of
the string 'SUBOP', the value of VORNR
and the value of UVORN. For example:
SUBOPVORN-UVORN.
NetworkActivityRelationType
The eld isn't present in the ERP pay-
load.
The eld is set to 'PChild'.
ManufacturingOrderVariantConguratio
n
Complex element that isn't available in
the ERP payload.
It's created if a segment 'E1VCCHR' is
present.
CharacteristicValuationOutb
Complex element that isn't available in
the ERP payload.
Characteristic name (ATNAM) Characteristic
Characteristic value (ATWRT) CharcValue
274 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP Customer
Complex element that isn't available in
the ERP payload.
It's created if the following two condi-
tions are met:
• There's a non-empty KUNAG el-
ement in a E1AFPOL segment
that has a number of order item
(POSNR) attribute that is equal to
'0001'.
• There's a non-empty NAME1 el-
ement in a E1AFPOL segment
that has a number of order item
(POSNR) attribute that is equal to
'0001'.
Sold-to party (KUNAG) Customer
Name 1 (NAME1) CustomerName
ErpCustomerOrder
Complex element that isn't available in
the ERP payload.
It's created if there's a KDAUF element
in a E1AFPOL segment that has a num-
ber of order item (POSNR) attribute that
is equal to '0001'.
Sales order number (KDAUF) CustomerOrder
Item number in sales order (KDPOS) CustomerOrderItem
Sales order number (KDAUF) SalesOrder This eld and the SalesOrderItem
eld are created if there's a KDAUF ele-
ment in a E1AFPOL segment that has a
number of order item (POSNR) attribute
that is equal to '0001'.
Item number in sales order (KDPOS) SalesOrderItem This eld and the SalesOrder eld are
created if there's a KDAUF element in
E1AFPOL segment that has a number
of order item (POSNR) attribute that is
equal to '0001'.
ChangeProduction Complex element that isn't available in
the ERP payload.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 275
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
SupportChangeAfterRelease This element isn't available in the ERP
payload. It's set to 'false'.
HoldProduction This element isn't available in the ERP
payload. It's set to 'BY_SFC'.
workInstructionIn
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFDHO
element.
trackViewing
This element isn't available in the ERP
payload. It's set to 'true'.
Document number (DOKNR), document
type (DOKAR), document part
(DOKTL), order number (AUFNR), and
application number (ORIGINAL)
workInstruction The system concatenates the order
number (AUFNR), document number
(DOKNR), document type (DOKAR),
document part (DOKTL), and order
number (AUFNR) values from the pa-
rent node and the application number
(ORIGINAL) value from the current
node. Example: AUFNRDOKNR-DOKAR-
DOKTL-ORIGINAL.
Document version (DOKVR) version
Original of document (FILENAME) erpFilename
ME integration: URL for accessing ERP
objects (URL)
url
Short description of the original
(DESCRIPTION) or document
description (DKTXT)
description If the DESCRIPTION string isn't empty,
it's selected. Otherwise, DKTXT is se-
lected.
attachmentList
Complex element that isn't available in
the ERP payload.
workInstructionAttachmentPointDTO
Complex element that isn't available in
the ERP payload.
The system loops over each E1AFVOL
segment. In each E1AFVOL segment, it
loops over each E1AFDOO segment.
shopOrderDTO
Complex element that isn't available in
the ERP payload.
Order number (AUFNR)
shopOrder
276 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
workInstructionIn Complex element that isn't available in
the ERP payload.
trackViewing This element isn't available in the ERP
payload. It's set to 'true'.
Document number (DOKNR), document
type (DOKAR), document part
(DOKTL), order number (AUFNR), and
application number (ORIGINAL)
workInstruction
The system concatenates the docu-
ment number (DOKNR), document type
(DOKAR), document part (DOKTL), and
order number (AUFNR) values from the
parent node and the application num-
ber (ORIGINAL) value from the current
node. Example: AUFNRDOKNR-DOKAR-
DOKTL-ORIGINAL.
Document version (DOKVR) version
Original of document (FILENAME)
erpFilename
ME integration: URL for accessing ERP
objects (URL)
url
Short description of the original
(DESCRIPTION) or Description of the
production resource/tool (DKTXT)
description
If the DESCRIPTION eld isn't empty,
its content is selected. Otherwise the
value of DKTXT is selected.
attachmentList Complex element that isn't available in
the ERP payload.
workInstructionAttachmentPointDTO Complex element that isn't available in
the ERP payload.
shopOrderDTO Complex element that isn't available in
the ERP payload.
Order number (AUFNR) shopOrder
bomComponentRef Complex element that isn't available in
the ERP payload.
This element and the elements below
are created if RSPOS is available. Oth-
erwise, a routingDTO element and its
subelements are created.
bomDTO Complex element that isn't available in
the ERP payload.
Order number (AUFNR) bom
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 277
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
bomType This element isn't available in the ERP
payload. It's set to 'U'.
materialDTO
Complex element that isn't available in
the ERP payload.
Material number (MATNR_EXTERNAL)
material
If MATNR_EXTERNAL is present, it's se-
lected.
Material number (MATNR_LONG)
material
If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material number (MATNR)
material
If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
version This element isn't available in the ERP
payload. It's set to '#'.
Item number of reservation / dependent
requirements (RSPOS)
sequence
The RSPOS number is multiplied by 10.
routingDTO Complex element that isn't available in
the ERP payload.
This element and its child elements are
created only if there's no RSPOS, which
means that the bomComponentRef ele-
ment above isn't created.
Order number (AUFNR) routing
version This element isn't available in the ERP
payload. It's set to 'A'.
routingType This element isn't available in the ERP
payload. It's set to 'U'.
routingStepRef Complex element that isn't available in
the ERP payload.
Key of a step in a routing (SAP ME)
(MES_STEPID), order number (VORNR),
or generated step ID
stepId If MES_STEPID is available, it's se-
lected. If MES_STEPID isn't available,
but VORNR is, VORNR is selected. Oth-
erwise, the number of the current iter-
ation is multiplied by 10 to generate a
step ID.
Version (SAP ME) (ME_REVISION) version If ME_REVISION is available, this eld is
created.
278 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
routingDTO Complex element that isn't available in
the ERP payload.
Order number (AUFNR) routing
version This element isn't available in the ERP
payload. It's set to 'A'.
routingType This element isn't available in the ERP
payload. It's set to 'U'.
Related Information
Enabling Auto-Release of Production and Process Orders
Specifying Data Values for Production Orders
Specifying Custom Values of Resource Types for Production Orders
Disabling the Work Instruction Viewing Log
Activating Assembly Quantity as Required
Dening the Min/Max Tolerance of the Assembly Quantity
Specifying Custom Values on Routing Step for an Order-Specic Routing
2.1.5.3.1.7Mapping Inventory Download
You can transfer material data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc INVCON03.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Movement type (BWART) goodsMovementType
Debit/credit indicator (SHKZG) debitCreditCode
Plant (WERKS) plant
Material number (MATNR_EXTERNAL) material If MATNR_EXTERNAL is present, it's se-
lected.
Material number (MATNR_LONG) material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 279
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Material number (MATNR) material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
Quantity (MENGE) quantityOnHand
Material document line item (ZEILE) erpMaterialDocumentLineItem
Material document year (MJAHR) erpMaterialDocumentYear
Material document number (MBLNR) erpMaterialDocumentNumber
Order number (AUFNR) reservedShopOrder Only if BWART equals 261.
Storage location (LGORT) receivingStorageLocation Only if LGORT is present as a string.
Issuing storage location (UMLGO) sourceStorageLocation Only if UMLGO is present as a string.
Batch (CHARG) batchNumber
Purchase order (EBELN) purchaseOrder
Serial number (SERNR) serialNumbers Only if ZE1ICIT6 is present.
Related Information
Enhancement of INVCON03 with Serial Numbers
2.1.5.3.1.8Mapping a Planned Order
You can transfer planned orders from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc LOIPLO02.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Planned Order (PLNUM) orderNumber
Planned Order Type (PAART) orderType
Planning Plant (PLWRK) productionPlant
Material Number (MATNR_EXTERNAL) material If MATNR_EXTERNAL is present, it's se-
lected.
280 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
Material Number (MATNR_LONG) material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material Number (MATNR) material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
billOfMaterialCategory
The eld isn't present in the ERP pay-
load.
Bill of Material Number (STLNR) billOfMaterial
Alternative BOM (STALT) alternativeBillOfMaterial
Alternative BOM (STALT) billOfMaterialVariant
BOM Usage (STLAN) billOfMaterialVariantUsage
Task List Type (PLNTY) billOfOperationsType
Key of the Task List Group (PLNNR) billOfOperationsGroup
Group Counter (PLNAL) billOfOperationsVariant
totalPlannedQuantityInBaseUnit
Complex element that isn't available in
the ERP payload.
Planned Total Order Quantity (GSMNG) value
Base Unit of Measure (MEINS) isoUnitCode
totalConrmedQuantityInBaseUnit
Complex element that isn't available in
the ERP payload.
Total Conrmed Qty Planned Order
(Repetitive Manufacturing) (CNFQTY)
value
Base Unit of Measure (MEINS) isoUnitCode
Scheduled Start (GSTRS) and Earliest
scheduled start: Execution (time)
(GSUZS)
scheduledStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Scheduled nish (GLTRS) and Earliest
scheduled nish: Execution (Time)
(GLUZS)
scheduledCompletionDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Planned Order Start Date (PSTTR) plannedStartDate The date from the iDoc is trans-
formed into this format: YYYY-MM-
DDTHH:MM:SS. Time value is created
in the transformation and set to
'00:00:00'.
Planned Order End Date (PEDTR)
plannedCompletionDate The date from the iDoc is trans-
formed into this format: YYYY-MM-
DDTHH:MM:SS. Time value is created
in the transformation and set to
'23:59:59'.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 281
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
priority There's no corresponding ERP eld.
The value is set to 500.
Storage Location (LGORT) erpPutawayStorageLocation
batchNumber
The eld isn't present in the ERP pay-
load.
Production Version (VERID) productionVersion
Sales Order Number (KDAUF) salesOrder
Item Number in Sales Order (KDPOS) salesOrderItem
orderSteps
Complex element that isn't available in
the ERP payload.
The system loops over each E1PLOPL
segments with FLGAT='0' to nd order
steps. E1PLOPL segments are arranged
in ascending order based on the value
of the VORNR element.
orderStep
Complex element that isn't available in
the ERP payload.
Operation/Activity Number (VORNR) stepId
erpStepType
The eld isn't present in the ERP pay-
load.
The value is set to Operation.
Operation Short Text (LTXA1)
operationText
Sequence (PLNFL) sequence
Work Center ID (ARBID) erpWorkCenterId
Earliest Scheduled Start: Execution
(Date) (FSAVD) and Earliest scheduled
start: Execution (Time) (FSAVZ)
earliestExecutionStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Earliest Scheduled Start: Processing
(Date) (FSSBD) and Earliest Scheduled
Start: Processing (Time) FSSBZ
earliestProcessingStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Earliest Scheduled Start: Teardown
(Date) (FSSAD) and Earliest Scheduled
Start: Teardown (Time) (FSSAZ)
earliestTeardownStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Earliest Scheduled Finish: Execution
(Date) (FSEDD) and Earliest Scheduled
Finish: Execution (Time) (FSEDZ)
earliestExecutionEndDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Latest Scheduled Start: Execution
(Date) (SSAVD) and Latest Scheduled
Start: Execution (Time) (SSAVZ)
latestExecutionStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
282 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
Latest Scheduled Start: Processing
(Date) (SSSBD) and Latest Scheduled
Start: Processing (Time) (SSSBZ)
latestProcessingStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Latest Scheduled Start: Teardown
(Date) (SSSAD) and Latest Scheduled
Start: Teardown (Time) (SSSAZ)
latestTeardownStartDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
Latest Scheduled Finish: Execution
(Date) (SSEDD) and Latest Scheduled
Finish: Execution (Time) (SSEDZ)
latestExecutionEndDate The date and time from the iDoc
are transformed into this format: YYYY-
MM-DDTHH:MM:SS.
orderComponents
Complex element that isn't available in
the ERP payload.
The system rst loops over each
E1RESBAS segment to collect the
RSNUM and RSPOS data. Then, it uses
these values to loop over each E1RESBL
segment that matches the RSNUM and
RSPOS data.
orderComponent
Complex element that isn't available in
the ERP payload.
Requirement Type (BDART) requirementType
Order Item Number (AFPOS) orderItem
Bill of Material (STLNR) billOfMaterial
Item Category (Bill of Material) (POSTP) billOfMaterialItemCategory
BOM Item Number (POSNR) billOfMaterialItemNumber
BOM Item Node Number (STLKN) billOfMaterialItemNodeNumber
Production Supply Area (PRVBE) supplyArea
requiredQuantityInBaseUnit
Complex element that isn't available in
the ERP payload.
Requirement Quantity (BDMNG) value
Base Unit of Measure (MEINS) isoUnitCode
requiredQuantityInBaseUnit There's no corresponding ERP eld.
Number of Reservation/Dependent
Requirements (RSNUM)
reservation
Item Number of Reservation /
Dependent Requirements (RSPOS)
reservationItem
Warehouse Number / Warehouse
Complex (LGNUM)
warehouseNumber
Alternative Item: Group (ALPGR) alternativeItemGroup
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 283
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
Alternative Item: Ranking Order
(ALPRF)
alternativeItemPriority
Alternative Item: Strategy (ALPST) alternativeItemStrategy
Material Number (MATNR_EXTERNAL) material If MATNR_EXTERNAL is present, it's se-
lected.
Material No. (MATNR_LONG) material If MATNR_EXTERNAL isn't present but
MATNR_LONG is, MATNR_LONG is se-
lected.
Material Number (MATNR) material If neither MATNR_EXTERNAL nor
MATNR_LONG is present, MATNR is se-
lected.
Batch Number (CHARG) batch
Movement Type (Inventory
Management) (BWART)
goodsMovementType
Alternative Item Indicator (ALPOS) materialCompIsAlternativeItem If ALPOS is equal to X,
materialCompIsAlternativeItem
is set to true. Otherwise,
materialCompIsAlternativeItem
is set to false.
Indicator: Backush (BACKFLUSH) materialCompIsMarkedForBackush If BACKFLUSH is equal to X,
materialCompIsMarkedForBackflu
sh is set to true. Otherwise,
materialCompIsMarkedForBackflu
sh is set to false.
Indicator: co-product (KZKUP) materialIsCoProduct If KZKUP is equal to X,
materialIsCoProduct is set to true.
Otherwise, materialIsCoProduct is
set to false.
Storage Location (LGORT) storageLocation
Debit/Credit Indicator (SHKZG) debitCreditCode
orderStepRelationships
Complex element that isn't available in
the ERP payload.
The system rst loops over each
E1PLOPL segment with FLGAT='0'.
E1PLOPL segments are arranged
in ascending order based on
the value of the VORNR element.
orderStepRelationship elements
are created only for segments after the
rst iteration.
orderStepRelationship
Complex element that isn't available in
the ERP payload.
284 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing for execu-
tion
SAP Digital Manufacturing for
execution Comment
Operation/Activity Number (VORNR) predecessorStepId It's the VORNR element of the preceed-
ing E1PLOPL segment that is selected.
predecessorStepType There's no corresponding ERP eld.
The value is set to Operation.
Operation/Activity Number (VORNR) successorStepId
successorStepType There's no corresponding ERP eld.
The value is set to Operation.
relationType There's no corresponding ERP eld.
The value is set to SucRel.
Related Information
Enabling Custom Resource Type For Planned Orders
Enabling Schedule Download For Planned Orders
2.1.5.3.1.9Mapping a Work Center
You can transfer work center data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc LOIWCS03.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID SNDPRN SenderBusinessSystemID
Plant (WERKS) plant
Work Center (ARBPL) workCenter
Short Description (KTEXT) description If there's a seg-
ment E1CRHDL/E1CRTXL[SPRAS=//
SupportedPlant/Language]/
KTEXT) in the iDoc that indicates
specic languages, this string is used.
If there's a segment E1CRHDL/
E1CRTXL[SPRAS='E']/KTEXT), the
corresponding string is used.
Otherwise, the string contained in
E1CRHDL/E1CRTXL/KTEXT is used.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 285
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
capacityCategoryIn
Complex element that isn't available in
ERP payload.
Capacity ID (KAPID) erpInternalId
Capacity category (KAPAR) category
Short Description (KTEXT) description
capacityIn
Complex element that isn't available in
ERP payload.
The system loops over each E1KAKOIL
segment.
Capacity ID (KAPID)
erpInternalId
Capacity category (KAPAR) category
Capacity name (NAME) name
Short Description (KTEXT) description
capacityShiftIn
Complex element that isn't available in
the ERP payload.
The system loops over each E1KAZYL
segment that has a VERSN value equal
to the maximum VERSN value among
all E1KAZYL elements in the parent
context: E1KAZYL[VERSN = max(../
E1KAZYL/VERSN)].
Valid-From Date DATUV
beginDate
Valid-to date (DATUB) endDate
Number of shifts in a day (ANZSH) shiftNumber
Available capacity version (VERSN) version
Length of the interval cycle (ANZTG) cycleLength
Ind.: Standard available capacity is valid
for this interval (KKOPF)
standardCapacity
capacityOverrideIn
Complex element that isn't available in
the ERP payload.
The system loops over each E1KAPAL
segment.
Shift number of an available capacity
(SCHNR)
shiftNumber
Current weekday number within the
available capacity cycle (TAGNR)
weekDayNumber
286 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Start time in seconds (internal) (BEGZT) beginTime
End time in seconds (internal) (ENDZT) endTime
Object ID of the resource (OBJID) erpInternalId
Production supply area (PRVBE) supplyArea
Standard Value Key (VGWTS) standardValueKey
standardValueIn
Complex element that isn't available in
the ERP payload.
The system loops over each E1CRHDL/
E1CRCOL segment where the FORML
value isn't empty. The segments are ar-
ranged in ascending order based on the
value of the LANUM element.
Activity type number within a set
(LANUM)
sequence
Formula key for costing (FORML) standardValue
2.1.5.3.1.10Field Mapping for a Standard Value Key (SVK)
The elds created in SAP S/4HANA On-Premise and ERP correspond to certain elds 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
.description /CO_MES_STANDARD_VALUE_KEY_PULL/
PAR_DESCRIPTION
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 287
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.1.11Mapping Characteristics Download
You can transfer characteristics from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc CHRMAS05.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Function (MSGFN) messageFunction
Characteristic Name (ATNAM) characteristicName
Characteristic Name (ATNAM) charcInternalID
Data Type of Characteristic (ATFOR) dataType
Number of Characters (ANZST) charcLength
Number of Decimal Places (ANZDZ) charcDecimals
Value with Plus or Minus Sign (ATVOR) charcWithSign
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Value with template (ATSCH) charcValueWithTemplate
Case Sensitive (ATKLE) caseSensitive
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Entry Required (ATERF) entryRequired
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Single Value (ATEIN) singleValue
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Unit of Measurement (MSEHI) uom
Exponent display (ATDIM) exponentDisplay
Indicator: Restrictable Characteristic
(ATGLA)
restrictableCharc
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
288 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Interval Values Allowed (ATINT) intervalsAllowed
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Indicator: Additional Values (ATSON) additionalValuesAllowed
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Display Allowed Values Dened in
Characteristic (ATWRD)
displayAllowedValues
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Name of Person Responsible for
Creating the Object (ANAME)
createdBy
Record Creation Date (ADATU) creationDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Name of Person Who Changed Object
(VNAME)
modiedBy
Last Changed On (VDATU) lastChangeDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Status of a Characteristic (ATMST)
charcStatus
Valid-From Date (DATUV) validFromDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Deletion Indicator (LKENZ)
deletionIndicator
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
No Entry Can be Made for Characteristic
(ATINP)
noEntryForCharc
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Characteristic Not to be Displayed
(ATVIE)
noDisplayForCharc
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Class number (CLASS) internalClassNumber
Indicator for Allowed Tolerances
(ATTOL)
indicatorForAllowedTolerance
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Counter for Sorting Object Allocations
(DEP_LINENO)
sortOrder
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 289
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Status of a Characteristic (ATMST) charcStatus
characteristicDescriptions
Complex element that isn't available in
the ERP payload.
The system loops over each E1CABTM
segment.
characteristicDescription
Complex element that isn't available in
the ERP payload.
2-Character SAP Language Code
(SPRAS_ISO)
language
Characteristic Description (ATBEZ) description
characteristicValues
Complex element that isn't available in
the ERP payload.
The system loops over each E1CAWNM
segment.
characteristicValue
Complex element that isn't available in
the ERP payload.
Characteristic Name (ATNAM) characteristic
Int Counter (ATZHL) position
Characteristic Value (ATWRT) characteristicValue
Internal Floating Point From (ATFLV) tpValueFrom
Internal Floating Point Value To (ATFLB) tpValueTo
Code for value dependency (ATCOD) codeForValue
Default Value (ATSTD) defaultValue
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Unit of Measurement (ATAWE) fromValueUom
Unit of Measurement (ATAW1) toValueUom
Language Key (SPRAS) locale
Valid-From Date (DATUV) validFrom
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Deletion Indicator (LKENZ)
deletionIndicator
Tolerance From (ATTLV) toleranceFrom
Tolerance To (ATTLB) toleranceTo
290 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Indicator: Tolerance Shown as a
Percentage (ATPRZ)
toleranceShownAsPercentage
Increment Within a Specied Interval
(ATINC)
incrementWithSpecicInterval
2.1.5.3.1.12Mapping Class Download
You can transfer class data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution using
the IDoc CLSMAS04.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Function (MSGFN) messageFunction
Class Type (KLART) classType
Class Number (CLASS) classInternalID
Class Number (CLASS) className
Class Status (STATU) status
Class Group (KLAGR) classGroup
Authorization Group for Finding Objects
(BGRSE)
classSearchAuthGrp
Classication Authorization Group
(BGRKL)
classClassfctnAuth
Class maintenance Authorization Group
(BGRKP)
classMaintAuthGrp
Document Number (DOKNR) docNumber
Document Type (DOKAR) documentType
Document Part (DOKTL) documentPart
Document Version (DOKVR) documentVersion
Name of Standards Organization
(NNORM)
classStandardOrgName
Standard Number (NORMN) classStandardNumber
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 291
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Issue Date (AUSGD) ClassStandardStartDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Version Number (VERSI)
classStandardVersionStartDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Version Number (VERSI)
classStandardVersion
Characteristics Table (LEIST) classStandardCharcTable
Local Class (LOCLA) classIsLocal
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Valid-From Date (VONDT) validityStartDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Valid-to date (BISDT)
validityEndDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Same Classication (PRAUS)
sameClassicationCheck
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
Name of Person Responsible for
Creating the Object (ANAME)
createdBy
Record Creation Date (ADATU) creationDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Name of Person Who Changed Object
(VNAME)
modiedBy
292 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Last Changed On (VDATU) lastChangeDate
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
classDescriptions
Complex element that isn't available in
the ERP payload.
The system loops over each E1SWORM
segment where KLPOS equals '01'.
classDescription
Complex element that isn't available in
the ERP payload.
2-Character SAP Language Code
(SPRAS_ISO)
language
Keywords (KSCHL) description
toClassCharacteristics
Complex element that isn't available in
the ERP payload.
The system loops over each E1KSMLM
segment..
classCharacteristic
Complex element that isn't available in
the ERP payload.
Characteristic Name (ATNAM) characteristic
Item Number (POSNR) position
Characteristic origin (HERKU) characteristicOrigin
Relevancy Indicator (RELEV) relevancyIndicator
Valid-From Date (DATUV) validFrom
If the date eld in the ERP pay-
load isn't empty and isn't equal to
'00000000' or '0000-00-00', the date
is converted into this format 'YYYY-MM-
DDT00:00:00'.
Deletion Indicator (LKENZ)
deletionIndicator
If the ERP value is 'X', the eld is set to
'true'. Otherwise, it's set to 'false'.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 293
2.1.5.3.1.13Mapping Classication Assignment Download
You can transfer classication assignment data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing
for execution using the IDoc CLFMAS02.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
Name of database table for object
(OBJECT_TABLE)
AssignmentType
Classication: Object Field (90 length,
technically needed) (OBJEK_LONG)
objectKey
If 'OBJEK_LONG' isn't empty, its value is
taken. Otherwise the value of 'OBJEK' is
selected.
Class Type (KLART) classType
classAssignment
Complex element that isn't available in
the ERP payload.
The system loops over each E1KSSKM
segment.
A_Class
Complex element that isn't available in
the ERP payload.
Class number (CLASS) classInternalID
Valid-From Date (DATUV) validFromDate
Classication status (STATU) status
validityStartDate
The eld isn't present in the ERP pay-
load.
validityEndDate
The eld isn't present in the ERP pay-
load.
keyDate
The eld isn't present in the ERP pay-
load.
charcLastChangedDateTime
The eld isn't present in the ERP pay-
load.
assignedCharValues
Complex element that isn't available in
the ERP payload.
The system loops over each E1AUSPM
segment.
294 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
assignedCharValue
Complex element that isn't available in
the ERP payload.
Characteristic Name (ATNAM) characteristicName
Characteristic Name (ATNAM) charcInternalID
Valid-From Date (DATUV) validFromDate
Characteristic Value (ATWRT) characteristicValue
Internal Floating Point From (ATFLV) internalFloatValueFrom
Unit of Measurement (ATAWE) uom
Characteristic Value (ATWRT) internalFloatValueTo
Characteristic Value (ATWRT_LONG) charcValue
2.1.5.3.1.14Mapping Equipment Download
You can send equipment data from SAP ERP or SAP S/4HANA to SAP Digital Manufacturing for execution
using the IDoc EQUIPMENT_CREATE02.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing for execution:
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
ERP ID (SNDPRN) SenderBusinessSystemID
equipment
Complex element that isn't available in
the ERP payload.
Maintenance Plant (MAINTPLANT) plant
Material Number (MATERIAL_LONG) materialNumber
Equipment Number
(EXTERNAL_NUMBER)
equipmentNumber
If the EXTERNAL_NUMBER value repre-
sents a number, the system removes
the leading zeros and trailing decimal
zeros. If EXTERNAL_NUMBER is a string,
all leading and trailing white space is
removed.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 295
SAP ERP / SAP S/4HANA
SAP Digital Manufacturing for
execution Comment
Equipment Number
(EXTERNAL_NUMBER)
toolNumber
If the EXTERNAL_NUMBER value repre-
sents a number, the system removes
the leading zeros and trailing decimal
zeros. If EXTERNAL_NUMBER is a string,
all leading and trailing white space is
removed.
Serial Number (SERIALNO)
serialNumber
If the SERIALNO value represents a
number, the system removes the lead-
ing zeros. If SERIALNO is a string, all
leading and trailing white space is re-
moved.
quantity
There's no corresponding ERP eld.
The value is set to 1.
Description of technical object
(DESCRIPT)
description
Asset location (MAINTLOC) location
Equipment category (EQUICATGRY) equipmentCategory
2.1.5.3.2 Outbound Communication
2.1.5.3.2.1Mapping a Production Yield Conrmation
Production yield conrmation is transferred from SAP Digital Manufacturing to SAP ERP or SAP S/4HANA
using CO_MES_PRODORDCONF_CREATE_TT.
This table contains eld names in SAP ERP and SAP S/4HANA and their corresponding eld names in SAP
Digital Manufacturing:
SAP Digital Manufacturing
SAP ERP / SAP S/4HANA Comment
IS_TIMETICKETS Complex element
messageId CONF_ID The system concatenates the cur-
rent date and time 'YYYDDHHMMSS'
with the value of the
SAP_MessageProcessingLogID and
returns only the last 40 characters from
the concatenated string.
orderId ORDERID
296 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
Sequence SEQUENCE If the value of Sequence is a number,
it's formated into a six digit number, for
example '12' becomes '000012'.
If the value of Sequence is a string,
white space is removed from the string.
OrderOperation OPERATION
OrderSuboperation SUB_OPER
CapacityCategoryCode CAPA_CATEGORY If the CapacityRequirementSplit
element isn't empty, the sys-
tem checks whether or not
CapacityCategoryCode is empty.
If CapacityCategoryCode isn't
empty, its value is selected. If
CapacityCategoryCode is empty, the
eld is set to '001'.
If CapacityRequirementSplit is
empty, the eld remains empty.
CapacityRequirementSplit SPLIT If CapacityRequirementSplit isn't
empty, it's value is selected.
FinalConrmationType FIN_CONF
OpenReservationsIsCleared CLEAR_RES If OpenReservationsIsCleared is
'true', the eld is set to 'X'. Otherwise,
the eld is set to ' '.
PostingDate POSTG_DATE The PostingDate is converted from
YYYY-MM-DDTHH:MM:SS to YYYY-MM-
DD.
VarianceReasonCode DEV_REASON
ConrmationText CONF_TEXT
Plant PLANT
WorkCenter WORK_CNTR
ConrmationUnitSAPCode CONF_QUAN_UNIT
ConrmationUnitISOCode CONF_QUAN_UNIT_ISO
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 297
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
ConrmationYieldQuantity /
ConrmationReworkQuantity
YIELD If the ConfirmationYieldQuantity
element isn't empty, the sys-
tem selects its value. Otherwise,
the ConfirmationReworkQuantity
value is selected.
ConrmationScrapQuantity SCRAP
OpWorkQuantityUnit1 CONF_ACTI_UNIT1
WorkQuantityUnit1ISOCode CONF_ACTI_UNIT1_ISO
OpConrmedWorkQuantity1 CONF_ACTIVITY1
NoFurtherOpWorkQuantity1IsExpd NO_REMN_ACTI1 If
NoFurtherOpWorkQuantity1IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
OpWorkQuantityUnit2 CONF_ACTI_UNIT2
WorkQuantityUnit2ISOCode CONF_ACTI_UNIT2_ISO
OpConrmedWorkQuantity2 CONF_ACTIVITY2
NoFurtherOpWorkQuantity2IsExpd NO_REMN_ACTI2 If
NoFurtherOpWorkQuantity2IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
OpWorkQuantityUnit3 CONF_ACTI_UNIT3
WorkQuantityUnit3ISOCode CONF_ACTI_UNIT3_ISO
OpConrmedWorkQuantity3 CONF_ACTIVITY3
NoFurtherOpWorkQuantity3IsExpd NO_REMN_ACTI3 If
NoFurtherOpWorkQuantity3IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
OpWorkQuantityUnit4 CONF_ACTI_UNIT4
WorkQuantityUnit4ISOCode CONF_ACTI_UNIT4_ISO
OpConrmedWorkQuantity4 CONF_ACTIVITY4
298 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
NoFurtherOpWorkQuantity4IsExpd NO_REMN_ACTI4 If
NoFurtherOpWorkQuantity4IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
OpWorkQuantityUnit5 CONF_ACTI_UNIT5
WorkQuantityUnit5ISOCode CONF_ACTI_UNIT5_ISO
OpConrmedWorkQuantity5 CONF_ACTIVITY5
NoFurtherOpWorkQuantity5IsExpd NO_REMN_ACTI5 If
NoFurtherOpWorkQuantity5IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
OpWorkQuantityUnit6 CONF_ACTI_UNIT6
WorkQuantityUnit6ISOCode CONF_ACTI_UNIT6_ISO
OpConrmedWorkQuantity6 CONF_ACTIVITY6
NoFurtherOpWorkQuantity6IsExpd NO_REMN_ACTI6 If
NoFurtherOpWorkQuantity6IsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
BusinessProcessEntryUnit CONF_BUS_PROC_UNIT1
BusProcessEntrUnitISOCode CONF_BUS_PROC_UNIT1_ISO
BusinessProcessConrmedQty CONF_BUS_PROC1
NoFurtherBusinessProcQtyIsExpd NO_REMN_BUS_PROC1 If
NoFurtherBusinessProcQtyIsExpd
is 'true', the eld is set to 'X'. Other-
wise, the eld is set to ' '.
ConrmedExecutionStartDate EXEC_START_DATE The
ConfirmedExecutionStartDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmedExecutionStartTime EXEC_START_TIME If the
ConfirmedExecutionStartTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 299
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
ConrmedSetupEndDate SETUP_FIN_DATE The ConfirmedSetupEndDate value
is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmedSetupEndTime SETUP_FIN_TIME If the ConfirmedSetupEndTime value
contains a 'T', the system extracts the
time in this format: HH:MM:SS. If 'T' is
not present, the input time is returned
as is.
ConrmedProcessingStartDate PROC_START_DATE The
ConfirmedProcessingStartDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmedProcessingStartTime PROC_START_TIME If the
ConfirmedProcessingStartTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
ConrmedProcessingEndDate PROC_FIN_DATE The ConfirmedProcessingEndDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmedProcessingEndTime PROC_FIN_TIME If the
ConfirmedProcessingEndTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
ConrmedTeardownStartDate TEARDOWN_START_DATE The ConfirmedTeardownStartDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmedTeardownStartTime TEARDOWN_START_TIME If the
ConfirmedTeardownStartTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
ConrmedExecutionEndDate EXEC_FIN_DATE The ConfirmedExecutionEndDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
300 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
ConrmedExecutionEndTime EXEC_FIN_TIME If the ConfirmedExecutionEndTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
Personnel PERS_NO
TimeRecording TIMEID_NO
EmployeeWageType WAGETYPE
EmployeeSuitability SUITABILITY
NumberOfEmployees NO_OF_EMPLOYEE
EmployeeWageGroup WAGEGROUP
BreakDurationUnit BREAK_UNIT
BreakDurationUnitISOCode BREAK_UNIT_ISO
ConrmedBreakDuration BREAK_TIME
EnteredByExternalUser EX_CREATED_BY
ConrmationExternalEntryDate EX_CREATED_DATE The
ConfirmationExternalEntryDate
value is converted from YYYY-MM-
DDTHH:MM:SS to YYYY-MM-DD.
ConrmationExternalEntryTime EX_CREATED_TIME If the
ConfirmationExternalEntryTime
value contains a 'T', the system extracts
the time in this format: HH:MM:SS. If
'T' is not present, the input time is re-
turned as is.
ExternalSystemConrmation EX_IDENT
ConrmationReworkQuantity IV_2ND_TIME_CONFIRMATION If ConfirmationReworkQuantity
isn't empty, the eld is set to 'X'.
ProposeBackush IV_PROPOSE_BACKFLUSH If ProposeBackflush is 'true', the
eld is set to 'X'. Otherwise, the eld is
set to ' '.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 301
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
IT_GOODSMOVEMENTS Complex element.
The system loops over each
ProdnOrdConfMatlDocItmType ele-
ment.
item Complex element
Material MATERIAL / MATERIAL_LONG If the material name's length is less
than or equal to 18 characters, the
eld MATERIAL is created. Otherwise,
the eldMATERIAL_LONG iscreated. In
both cases the value of Material isse-
lected.
Plant PLANT
StorageLocation STGE_LOC
Batch BATCH
GoodsMovementType MOVE_TYPE
InventorySpecialStockType SPEC_STOCK
QuantityInEntryUnit ENTRY_QNT
EntryUnitSAPCode ENTRY_UOM
orderId ORDERID
OrderItem ORDER_ITNO
Reservation RESERV_NO
ReservationItem RES_ITEM
GoodsMovementRefDocType MVT_IND
ProdnOrdConf2/ProdnOrdConf2Type/
OrderOperation
ACTIVITY
MaterialDocumentYear REF_DOC_YR
MaterialDocument REF_DOC
MaterialDocumentItem REF_DOC_IT
StorageType STGE_TYPE
StorageBin STGE_BIN
302 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP Digital Manufacturing SAP ERP / SAP S/4HANA Comment
IT_GOODSMVT_SERIALNUMBER Complex element.
The system loops over each
MatlDocItmSerialNumberType ele-
ment.
item Complex element
MatDocItm MATDOC_ITM
SerialNo SERIALNO
Uii UII
2.1.5.3.2.2Mapping a Production Scrap Conrmation
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 eld names in SAP ERP and their corresponding eld names in SAP Digital Manufacturing
for execution:
SAP ERP
SAP Digital Manufacturing for
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
Yield to Be Conrmed (SCRAP) Quantity SFC quantity / quantity completed
(normally 1, except for non-serialized
SFC)
Activity Number (OPERATION) Custom data eld: 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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 303
SAP ERP
SAP Digital Manufacturing for
execution Comment
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
MATERIAL_LONG
item
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
2.1.5.3.2.3Mapping 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 eld names in SAP ERP and their corresponding eld names in SAP Digital Manufacturing
for execution:
SAP ERP
SAP Digital Manufacturing for
execution Comment
DETERMINE_RESERVATIONS
Always set to X
GM_CODE
Always set to 03
304 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP ERP
SAP Digital Manufacturing for
execution Comment
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 dened in ERP
Production Storage Location eld 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 eld collected
during assembly
2.1.5.3.2.4Mapping a Production Order Complete
Data is transferred from SAP Digital Manufacturing for execution to SAP ERP by calling the
BAPI_PRODORDCONF_CREATE_TT.
This table contains eld names in SAP ERP and their corresponding eld names in SAP Digital Manufacturing
for execution:
SAP ERP
SAP Digital Manufacturing for
execution Comment
Plant (PLANT) Plant
Order Id (ORDERID) Order Number
Operation (OPERATION) Operation
Yield (YIELD)
0
FIN_CONF X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 305
SAP ERP
SAP Digital Manufacturing for
execution Comment
CLEAR_RES X
2.1.5.3.2.5Mapping a Release Order to MES
Data is transferred from SAP Digital Manufacturing for execution to SAP MES.
This table contains eld names in SAP MES and their corresponding eld names in SAP Digital Manufacturing
for execution:
SAP MES
SAP Digital Manufacturing for
execution Comment
Plant (plant) Plant
Order Id BO (shopOrderRef) Order Number BO
Quantity to release
(quantityToRelease)
Quantity to Release
Work Center BO (workCenterRef) Work Center BO Optional
Add to new lot (addToNewLot) Add to new lot Optional
Allow RMA release
(allowRmaRelease)
Allow RMA release Optional
Labor Charge Code BO
(laborChargeCodeRef)
Labor Charge Code BO Optional
New SFC List segment Zero or more repetitions
SFC (id) SFC
306 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.5.3.2.6Mapping an Updated Order Schedule to MES
Data is transferred from SAP Digital Manufacturing for execution to SAP MES.
This table contains eld names in SAP MES and their corresponding eld names in SAP Digital Manufacturing
for execution:
SAP MES
SAP Digital Manufacturing for
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
(plannedQuantity)
Planned Quantity
Conrmed Quantity
(confirmedQuantity)
Conrmed Quantity Optional
Planned start date (startDate) Planned start date
Planned end date (endDate) Planned end date Optional
Resource ERP ID
(resourceErpInternalId)
Resource ERP ID Optional
Shop Order Number BO
(shopOrderRef)
Order Number BO
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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 307
• Internal units dened 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
You can create, view, and delete custom units of measure (UOM) using the Unit of Measure API. If you're
using custom UOMs, make sure to set up custom UOMs before attempting to download business objects,
such as materials that use the custom UOM from external systems. You can add custom UOMs to already
existing dimension groups. To do this, you need to enter the code for the necessary dimension group. For
more information, see Unit of Measure API .
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 elds can contain only allowed characters.
Key elds, such as object names, support only Latin-based characters. If key elds 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 Latin-based letters and numbers
Spaces Allowed before, between, and after characters.
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 _
Special characters supported additionally for the names of
the following objects:
• Material
• Bill of materials (BOM)
• Forward slash /
• Hashtag #
• Dollar sign $
308 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Allowed Characters Description
Special characters supported for work instruction There are no restrictions because the work instruction name
isn't used for object handling in SAP Digital Manufacturing
for execution.
Special characters supported for work center, resource, and
resource type
•
Forward slash /
•
Period .
•
Hashtag #
•
Quotation mark "
•
At sign @
•
Backtick `
•
Space
•
Colon :
Caution
Do not use a forward slash / at the beginning or the end of a material or BOM name, or multiple forward
slashes consecutively, as such scenarios are not supported. Do not use double forward slashes in the
names of work centers, shifts, and resources.
2.1.5.6 Mapping Plants (Plant Conversion)
You can integrate several ERP plants with the same identier into one SAP Digital Manufacturing tenant using
the plant-mapping feature.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
or SAP ERP [page 15].
• You've created a unique destination for each ERP plant in your SAP Cloud Integration subaccount. For
more information, see Set Up Connection Between SAP Cloud Integration, Cloud Connector, and SAP
S/4HANA or SAP ERP [page 106].
• You've created a plant with a unique name in SAP Digital Manufacturing for each ERP plant using the
Manage Plants app. For more information, see Manage Plants.
• You've enabled the S/4HANA integration mode in the Manage Business Settings app for each plant. For
more information, see Manage Business Settings.
Note
In the Manage Business Settings app, the ERP Destination corresponds to the destination that you've
created in your SAP Cloud Integration subaccount and that points to the integrated ERP system.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 309
Context
If you need to integrate more than one SAP ERP or SAP S/4HANA system with SAP Digital Manufacturing,
you may encounter a situation where the same plant identier is used for multiple plants in dierent ERP
systems. For example, there's Plant 1000 in ERP 1 and Plant 1000 in ERP 2. To address this, you need to create
a mapping that ensures the inbound and outbound data goes to the correct system. This means you create two
plants in SAP Digital Manufacturing, such as plant 100A and plant 100B, which represent the two Plants 1000
in the integrated ERP systems. Then, you use the plant conversion feature in SAP Cloud Integration to create
two mappings for each plant in SAP Cloud Integration: One is for outbound communication and the other is
for inbound communication between SAP Digital Manufacturing and the integrated SAP ERP or SAP S/4HANA
system.
Note
If you want to use plant conversion in the context of an integration with EWM, see Mapping Plants (Plant
Conversion) [page 436]
Procedure
1. In SAP Cloud Integration, go to Build and Develop Integration Content () and select the SAP S/4HANA
Integration with SAP Digital Manufacturing package.
2. Under Artifacts, search for Initial Parameters.
3. Choose Actions () and then Congure.
4. Set ENABLE_PLANT_CONVERSION to TRUE.
5. Save your changes.
6. Choose Actions () and then Deploy.
7. Under Artifacts, search for Plant Value Mapping.
8. Choose Actions () and then Congure.
The Congure Plant Value Mapping window opens.
9. Under Value Mappings, choose Add.
10. Create the following two entries for each of the integrated ERP systems:
310
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
ERP, WERKS DMC, PLANT Description
<Logical System>:<ERP Plant
Identifier>
Note
Use the logical system that repre-
sents the integrated ERP system.
For more information, see Create
Logical Systems [page 38].
Example
QE5ABCD300:1000
<Plant Name in SAP Digital
Manufacturing>
Note
Use the plant name that you've
dened in the Manage Plants app.
For more information, see Cong-
ure SAP Digital Manufacturing for
Outbound Integration [page 108].
Example
100A
This mapping is used for the data
transfer from your ERP system to SAP
Digital Manufacturing.
Note
There's no need to enter your
space in this line.
<ERP Destination Field for
Plant>:<ERP Identifier>
Note
Use the destination you've cre-
ated for the integrated ERP
system in your SAP Cloud
Integration. For more information,
see Set Up Connection Between
SAP Cloud Integration, Cloud
Connector, and SAP S/4HANA or
SAP ERP [page 106].
Example
QE5abcd300rfc:1000
<Plant Name in SAP Digital
Manufacturing>
Note
Use the plant name that you've
dened in the Manage Plants app.
For more information, see Cong-
ure SAP Digital Manufacturing for
Outbound Integration [page 108].
Example
100A
This mapping is used for the
data transfer from SAP Digital
Manufacturing to your ERP system.
Note
There's no need to enter your
space in this line.
11. Choose Save and Deploy.
Results
Your ERP plants are mapped to their respective plants in SAP Digital Manufacturing for inbound and outbound
communication.
Tip
As a test, you can download a work center with standard value keys from your integrated ERP system to
SAP Digital Manufacturing because the data transfer is bidirectional. If your conguration is correct, you
nd two integration messages in the Integration Message Dashboard:
• LOIWCS03
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 311
• Standard Value Key Download
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 identiers 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 21]
2.1.6Customizing the Integration Scenario
You can customize your integration scenario by using predened XSLT code and standard integration ows, or
by implementing your own XSLT transformation rules and integration ows.
Overview
You can adapt your integration with SAP ERP or SAP S/4HANA to your needs by using the predened
customizing options available through predened XSLT code in the Manage Integration Workows app together
312
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
with the standard integration ows 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 ows in SAP Cloud Integration, you need to create custom
integration workows in the Manage Integration Workows app that make sure that the eld mapping between
ODATA and BAPI messages takes place between SAP Digital Manufacturing and SAP Cloud Integration.
For more information see:
• Predened Customizing Options Using XSLT [page 313]
• User-Dened Customizing Options [page 314]
2.1.6.1 Predened Customizing Options Using XSLT
You can customize integration workows using XSLT in the Manage Integration Workows app in SAP Digital
Manufacturing to benet from certain elds or attributes that aren't covered by the standard workows.
Use
In SAP Digital Manufacturing, you can add additional elds to various apps to include certain pre-dened or
customer-specic 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 workow (iFlow) conguration takes part in SAP Cloud Integration, some congurations
can be done using XSLT code in the Manage Integration Workows 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.
Predened Customizing Options
You can choose among many predened customizing options that are already contained in the standard
XSLT code but are commented out. In the Manage Integration Workows app, you can choose a workow, for
example LOIPRO05_PRODORDER, copy the whole XSLT script from the Standard XSLT eld into the Custom
XSLT eld. 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 Workows app, see Manage Integration Workows.
Note
If you need data from dierent 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
SAP Digital Manufacturing for execution Integration
PUBLIC 313
Note
If you're already working with your own custom XSLT and need to nd 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 Conguration functionality provided by
the Integration Message Dashboard app.
After choosing Check Integration Conguration, you select an integration message to start an automated
test of the integration conguration 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 Workows
2.1.6.2 User-Dened Customizing Options
You can adapt your integration scenario to your needs by using custom integration ows in SAP Cloud
Integration and custom integration workows in the Manage Integration Workows app.
Overview
Instead of using the standard integration ows provided by SAP Digital Manufacturing through the SAP S/
4HANA Integration with SAP Digital Manufacturing package, you can create custom integration ows in SAP
Cloud Integration. To know more about how to create custom integration ows, see SAP Cloud Integration.
When working with custom integration ows in SAP Cloud Integration, you need to create custom integration
workows in the Manage Integration Workows app that take over data from an SAP Cloud Integration
integration ow or pass data to the integration ow.
Note
It's recommended to use the standard integration ows provided by the SAP S/4HANA Integration with
SAP Digital Manufacturing package in connection with the standard / custom XSLT options available in the
314
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Manage Integration Workows app. For more information, see Predened Customizing Options Using XSLT
[page 313].
Inbound and Outbound Integration
Once you've created and deployed your custom integration ow in SAP Cloud Integration, you need to perform
some congurations in SAP Digital Manufacturing to enable the communication between SAP ERP or SAP
S/4HANA and SAP Digital Manufacturing. These congurations are described in the following topics:
• SAP Cloud Integration to SAP Digital Manufacturing [page 315]
• SAP Digital Manufacturing to SAP Cloud Integration [page 317]
Related Information
Predened Customizing Options Using XSLT [page 313]
2.1.6.2.1 SAP Cloud Integration to SAP Digital
Manufacturing
You can connect your custom SAP Cloud Integration integration ow to SAP Digital Manufacturing using the
Manage Integration Workows app.
Prerequisites
• The technical integration has been implemented. For more information, see Technical Integration with SAP
S/4HANA or SAP ERP [page 15].
• 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 ow in SAP Cloud Integration. This integration ow
fetches the incoming data and sends it to SAP Digital Manufacturing.
• You've got the Service Workow name of your SAP Cloud Integration integration ow.
• You've created some XSLT code that you can use in the Manage Integration Workows app in SAP Digital
Manufacturing to transform the incoming data.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 315
Context
You can connect your custom SAP Cloud Integration integration ow to SAP Digital Manufacturing using the
Manage Integration Workows 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 ows, you
can refer to the Integration Flow Design Guidelines. You'll nd 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 workow performance, you can jump right to this topic:
Optimize Performance.
Note
For more information about the xslt elds available in the Manage Integration Workows app, see Manage
Integration Workows.
Procedure
1. In SAP Digital Manufacturing, go to the Manage Integration Workows app.
2. On the Custom Workow tab, choose Create.
3. Under Root Name, enter the root name of your iDoc.
4. Optional: Enter an Identier to mark the outgoing message.
The identier of your message will be found under Application Message ID in SAP Cloud Integration.
5. Under
Service Conguration Pre-Service Stage Conguration XSLT enter your XSLT code.
6. Under
Service Stage Conguration Service Workow , enter the name of your service workow.
7. Choose Save.
Results
You've added your custom integration workow to the Manage Integration Workows app.
To verify whether the integration workow 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 workow. For more information, see Monitoring Message
Processing.
316
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.1.6.2.2 SAP Digital Manufacturing to SAP Cloud
Integration
You can adapt your outbound integration scenario by modifying the standard integration workows available in
the Manage Integration Workows app.
For integration scenarios involving outbound custom integration ows in SAP Cloud Integration, you can adapt
the standard integration workows available in the Manage Integration Workows app, so that they call the
custom integration ows that you've implemented in SAP Cloud Integration during execution.
You can add references to your SAP Cloud Integration custom integration workows in the following elds of
the standard integration ows available in the Manage Integration Workows app:
Field
Description
Workow 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 Conguration / Custom Pre-XSLT
Workow
With this eld, you can enhance the outgoing message be-
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 Conguration / Custom Post-XSLT
Workow
With this eld, you can enhance the outgoing message after
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 Conguration / Custom Service Workow
With this eld, you can dene 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
SAP Digital Manufacturing for execution Integration
PUBLIC 317
Field Description
Post-Service Stage Conguration / Custom Post-Service
Workow
With this eld, you can enhance the message received as a
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 Workow
With this eld, you can dene 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.7Upgrade Information
When an upgrade of SAP Digital Manufacturing for execution is released, you need to manually update the
SAP S/4HANA Integration with SAP Digital Manufacturing package in SAP Cloud Integration and deploy the
integration artifacts it contains.
Prerequisites
You've got the Administrator role in SAP Cloud Integration.
Context
To use the features of the new release, you need to update the SAP S/4HANA Integration with SAP Digital
Manufacturing package in SAP Cloud Integration. You can only update the package to the latest version. For the
change log, see 3315636 .
Tip
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
.
318
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Procedure
1. In SAP Cloud Integration, go to the Design section.
2. Choose the SAP S/4HANA Integration with SAP Digital Manufacturing package.
3. Choose Update package and then Update.
You've updated the package.
4. On the Artifacts tab, select an artifact.
5. Choose Actions () and then Deploy.
6. Deploy the remaining artifacts manually.
Results
You've updated your SAP S/4HANA Integration with SAP Digital Manufacturing package and deployed its
artifacts.
2.2 Integration with SAP S/4HANA Cloud
You can enable the communication between SAP S/4HANA Cloud (Public Edition) 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.
Note
This chapter describes the integration scenario with SAP S/4HANA Cloud (Public Edition).
After you have completed the onboarding procedures as mentioned in Onboarding and User Management,
you can continue with the congurations 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 323].
For more details about supported data exchange between the systems, see Business Integration with SAP
S/4HANA Cloud [page 350].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 319
Related Information
Minimum Version Requirements and Supported Scenarios [page 320]
2.2.1Minimum 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 S/4HANA Cloud Objects Integrated with SAP Digital Manufacturing
Object Communication Scenario
Material
SAP_COM_0009
Material classication
SAP_COM_0163, SAP_COM_0309
BOM
SAP_COM_0105
Goods movement
SAP_COM_0263
Batch number
SAP_COM_0337
Recipe, routing, and production version
SAP_COM_0519
Process and 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
Note
To nd out more about any limitations or restrictions that could apply to your scenario, see 3379404
.
320
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.2Overview 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.
• Transferring a Material Master [page 353]
• Transferring a Work Center [page 354]
• Transferring QM Defect Code Groups and Codes from SAP S/4HANA Cloud [page 358]
• Transferring Production Order with PRT Assignment [page 362]
• Inspection Characteristics Integration (Production Order) [page 369]
• Transfer of Floor Stock Data [page 363]
• Inspection Results Recording (Production Order) [page 370]
• Transfer of Floor Stock Return Data [page 367]
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 321
2.2.3Overview 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.
• Transferring a Material Master [page 353]
• Transferring a Work Center [page 354]
• Transferring QM Defect Code Groups and Codes from SAP S/4HANA Cloud [page 358]
• Inspection Characteristics Integration (Production Order) [page 369]
• Transfer of Floor Stock Data [page 363]
• Inspection Results Recording (Production Order) [page 370]
• Transfer of Floor Stock Return Data [page 367]
• Transferring a Master Recipe [page 355]
• Integration of Transaction Data [page 361]
• Batch Characteristics Update [page 369]
• Batch Creation [page 369]
322
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.4Technical 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_256/unique_256_Connect_42_subsection-im1 [page 323]
• #unique_256/unique_256_Connect_42_subsection-im2 [page 324]
• #unique_256/unique_256_Connect_42_subsection-im3 [page 324]
• #unique_256/unique_256_Connect_42_subsection-im4 [page 324]
• #unique_256/unique_256_Connect_42_subsection-im5 [page 324]
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 348].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 323
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 326].
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 328].
• 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
328].
For more information, see Creating a Communication System [page 327].
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
Classication Systems OData Integration
SAP_COM_0309
Product Classication Integration
SAP_COM_0519
Production Planning Master Data Integration
SAP_COM_0522
Manufacturing Execution - Order and Conrmation
Integration
For more information, see Creating Communication Arrangements [page 330].
Conrm Integration
Conrm the transfer of a specic 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 congure the collaboration links and directives. For more
information, see Manage Collaboration Links.
Note
Do not enter any personal data in any text elds or in any les uploaded to SAP Digital Manufacturing for
execution.
324
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
You can check your integration scenario using the Check Integration Conguration functionality provided by
the Integration Message Dashboard app.
After choosing Check Integration Conguration, you select an integration message to start an automated
test of the integration conguration 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 351]
Integration of Transaction Data [page 361]
Manage Collaboration Links
2.2.4.1 Before You Start
This page shows you the prerequisite steps that must be completed before conguring 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 conguration 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
SAP Digital Manufacturing for execution Integration
PUBLIC 325
Next Steps
• Creating a Service Instance and a Service Key [page 328]
• Creating a Communication User [page 326]
• Creating a Communication System [page 327]
• Creating Communication Arrangements [page 330]
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 SAP_BR_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.
326
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 SAP_BR_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 326].
• 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 328].
• 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
SAP Digital Manufacturing for execution Integration
PUBLIC 327
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 nd it in the service key creden-
tials under the property manufacturing-execution-
integration.
Example
https://dme-integration-ms.dm.<data
center>-quality.prod.shoot.live.k8s-
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.
328
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 elds 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 elds 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
SAP Digital Manufacturing for execution Integration
PUBLIC 329
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 species the metadata for a specic communication scenario, such as material
replication. The metadata for the communication arrangement is contained in a service key. You can dene 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 denes the user and the system for specic 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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.
330
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
4. Select the communication scenario SAP_COM_0009 (Product Integration).
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 lled 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 nd 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 eld. 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 eld, 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 congure three communication arrangements:
• SAP_COM_0009 for product integration
• SAP_COM_0163 for classication systems OData/SOAP integration
• SAP_COM_0309 for product classication integration
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 331
Related Information
Classication Systems OData/SOAP Integration (SAP_COM_0163) [page 334]
Product Classication Integration (SAP_COM_0309) [page 337]
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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 eld is lled 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.
332
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
The inbound services added to the communication scenario in the back-end system are reected in the
communication arrangement under Inbound Services.
8. To activate the communication arrangement, choose Save.
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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 eld is lled 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 333
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 Conrmation, enter /ws?X-Identity-Zone-
Subdomain=<subdomain>.
Note
To nd 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 Classication Systems OData/SOAP Integration
(SAP_COM_0163)
This communication arrangement is for downloading material classications from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.
Prerequisites
• You've got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
Procedure
To create this communication arrangement, complete the following steps:
334
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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 (Classication 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 eld is lled 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 reected in the
communication arrangement under Inbound Services.
9. Under
Outbound Services Characteristic Data for Classication - 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 Notication
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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
• You've assigned a business partner to your communication system.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 335
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 Notication
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 eld is lled 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 Notication service, enter /ws?X-Identity-Zone-
Subdomain=<subdomain>.
Note
To nd 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 dening output settings for specic 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.
336
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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.
Related Information
Material Document Integration (SAP_COM_0108) [page 333]
2.2.4.4.6 Product Classication Integration
(SAP_COM_0309)
This communication arrangement is for downloading material classications from SAP S/4HANA Cloud to SAP
Digital Manufacturing for execution.
Prerequisites
• You've got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 Classication 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
.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 337
5. The Arrangement Name eld is lled 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 reected in the
communication arrangement under Inbound Services.
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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 .
338
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
5. The Arrangement Name eld is lled 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.
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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 339
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 eld is lled 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 the Outbound Communication section, the user associated with the Communication System is displayed
by default in the value help for the User Name eld. 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>
340 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
To nd 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 eld. 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 eld, 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 eld, select active or inactive mode, depending on your requirements.
15. To activate the communication arrangement, choose Save.
2.2.4.4.9 Manufacturing Execution - Order and
Conrmation 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 Conrmation
Integration).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 341
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 eld is lled 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.
The included inbound services are listed in the Inbound Services section.
Interaction
SAP S/4HANA Cloud Format
SAP S/4HANA Cloud In-
terface
Process Order Conrmation Inbound
OData V2 API_PROC_ORDER_CONFIR
MATION_2_SRV
Production Order Conrma-
tion
Inbound
OData V2 API_PROD_ORDER_CONFIR
MATION_2_SRV
Production Order (Version
2)
Inbound
OData V2 API_PRODUCTION_ORDER_
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 eld. By choosing the user, the Authentication Method is
defaulted with same authentication method associated with this user.
Interaction SAP S/4HANA Cloud Format
SAP S/4HANA Cloud
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 oor distribution when you
create a communication scenario. By activating the integration, all orders are automatically distributed
to your shop oor system unless you dene lter criteria. Without a lter, you can no longer conrm
orders in the SAP S/4HANA Cloud system. You conrm orders in your shop oor system and the
conrmations are transferred to the SAP S/4HANA Cloud system.
342
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
10. In the Path for Manufacturing Order - Send, Version 2, enter /dmc/ws/manufacturingOrderV2?X-
Identity-Zone-Subdomain=<subdomain>.
Note
To nd 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 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 oor sys-
tem.
Order Type
<your order types>
Select the order type of the orders
that are distributed to your shop oor
system.
Plant
<your plant>
Select your plant.
Note
The system evaluates the lter criteria using the following logic:
• If you apply several lter criteria to the same attribute (for example, material), the system applies
the lter if any lter criterion is true.
• If you apply several lter criteria to dierent attributes (for example, material and order type), the
system applies the lter if all lter criteria are true.
• The system ignores empty elds.
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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 343
2.2.4.4.10Inspection 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 eld is lled 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 reected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose Save.
344
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.4.4.11Quality 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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_0318 (Quality Inspection Process Integration) from the pick
list.
5. The Arrangement Name eld is lled 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 reected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose Save.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 345
2.2.4.4.12Defect 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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).
5. The Arrangement Name eld will be lled 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.
346
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.4.4.13Material 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 got the SAP_BR_ADMINISTRATOR role in SAP S/4HANA Cloud.
• 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 328].
• You've created a communication user in SAP S/4HANA Cloud. For more information, see Creating a
Communication User [page 326].
• You've created a communication system in SAP S/4HANA Cloud. For more information, see Creating a
Communication System [page 327].
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 eld is lled 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 reected here in
the communication arrangement under Inbound Services.
10. To activate the communication arrangement, choose Save.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 347
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 a
Destination for System Communication and Integration.
The following destination is used for outbound integration:
• S4H_ODATA_INTEGRATION. For more information, see Destination S4H_ODATA_INTEGRATION [page
348].
2.2.4.5.1 Destination S4H_ODATA_INTEGRATION
Congure 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 326].
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 Create Destination to create the S4H_ODATA_INTEGRATION destination.
3. Enter the name, S4H_ODATA_INTEGRATION, and description of the destination.
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 nd the API-URL in one of the following inbound communcation scenarios that you've created
in a previous step:
• SAP_COM_0163
348
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• 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 name 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 dierent system IDs. Systems are identied 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.
Related Information
Manage Plants
Manage Business Settings
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 349
2.2.4.7 Dening Operations in SAP S/4HANA Cloud for
SAP Digital Manufacturing for execution
In SAP S/4HANA Cloud, you can dene operations to use data in SAP Digital Manufacturing for execution.
In SAP S/4HANA Cloud, you dene 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 ags. If you set the relevant exclusion ag, the operation will
not be downloaded to SAP Digital Manufacturing for execution. If the ag 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 agged operationIsNotMESRelevant = true, the system doesn't transfer this operation or any phase
belonging to this operation to SAP Digital Manufacturing.
If an operation is agged operationIsNotMESRelevant = false, the system transfers this operation and all phases
belonging to this operation that are agged operationIsNotMESRelevant = false to SAP Digital Manufacturing.
If an operation is agged operationIsNotMESRelevant = false, but none of its phases are agged
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 ag in ProcessOrder: /n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ManufacturingOrderActivityNetworkElement/n1:OperationControlProfile/
n1:OperationIsNotMESRelevant
Path of operationIsNotMESRelevant ag
in MasterRecipe: /n0:ManufacturingMasterRecipeInfomation/BillOfOperations/
BillOfOperationsActivityNetworkElement/BillOfOperationsActivityNetworkElementTimeSlice/
OperationControlProfile/n1:OperationIsNotMESRelevant
2.2.5Business 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.
350
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• 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 351]
Integration of Transaction Data [page 361]
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,
see Master Data Maintenance.
You can integrate the following master data with SAP S/4HANA Cloud:
Master Data Integration from SAP S/4HANA Cloud to SAP Digital Manufacturing
SAP S/4HANA Cloud
SAP Digital Manufacturing Cloud for execution
Material
If Classication (Class and Characteristics) data is main-
tained for a material in SAP S/4HANA Cloud, that data is
also downloaded.
Class Type 022 (batch management activated at plant level),
023 (batch management activated at client level) and 300
(material) are downloaded.
Material
Work Center (PP-PI Resource) Work Center
Master Recipe Master Recipe
Master Routing Master Routing
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 351
Prerequisites
• You have dened and set up plants for integration using the Manage Plants and Manage Business Settings
apps.
Sequence Considerations
•
1. Transfer the materials.
2. Transfer the component materials.
3. Transfer the work centers.
4. Transfer the master recipe / master routing.
Note
The master BOM is downloaded using an OData call while downloading your master recipe or
master routing. The master BOM is downloaded only when at least one component is assigned to
the routing or recipe step.
5. Transfer the process order / production order.
• Materials must be transferred before master recipe / master routing and process order / production order.
• Finished items must be transferred before routings.
Implementation Considerations
Some functions may behave dierently depending on the SAP S/4HANA Cloud version used for integration
with SAP Digital Manufacturing for execution.
Related Information
Integration of Transaction Data [page 361]
352
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.5.1.1 Transferring a Material Master
You can transfer a material master created or updated in SAP S/4HANA Cloud to SAP Digital Manufacturing.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
Cloud [page 323].
• You've set up the following communication arrangements in your SAP S/4HANA Cloud system:
• SAP_COM_0009 for product integration. For more information, see Product Integration
(SAP_COM_0009) [page 330].
• SAP_COM_0163 for classification systems OData/SOAP integration. For more
information, see Classication Systems OData/SOAP Integration (SAP_COM_0163) [page 334].
• SAP_COM_0309 for product classification integration. For more information, see
Product Classication Integration (SAP_COM_0309) [page 337].
Context
During production, material master data from SAP S/4HANA Cloud is required for SAP Digital Manufacturing.
Therefore, you need to transfer material master data from SAP S/4HANA Cloud to SAP Digital Manufacturing
to create or update the corresponding material record in SAP Digital Manufacturing. Here you learn how to
transfer a material master record created in SAP S/4HANA Cloud to SAP Digital Manufacturing.
Note
The following class types are supported for download from SAP S/4HANA Cloud:
• 001 (material class)
• 022 (classication)
• 023 (batch)
• 300 (variant)
Procedural Steps
1. In your SAP S/4HANA Cloud system, open the Replicate by Object Selection app.
2. Select Product from the Business Object Type dropdown.
3. Enter your material in the Business Objects to be Replicated table.
4. Select a target system under Target System Selection.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 353
Note
The target system is the business system you dened for the communication system. For more
information, see Creating a Communication System [page 327].
5. Choose Replicate.
6. To verify whether the material master has been transferred to SAP Digital Manufacturing, you've got the
following options:
• In SAP S/4HANA Cloud, check the replication status by choosing Display Log.
• In SAP S/4HANA Cloud, check the message status in the Message Dashboard.
• In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of your
Material Download integration message. For more information, see Integration Message Dashboard.
2.2.5.1.2 Transferring a Work Center
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 eld.
5. Enter your plant in the Plant eld.
6. Select a target system in the Target System Selection table.
Note
The target system is the business system you dened for the communication system. For more
information, see Creating a Communication System [page 327].
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
354
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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.
You can control if a default resource is created in SAP Digital Manufacturing for execution when a work center is
transferred from SAP S/4HANA Cloud using the Create Default Resources during Work Center Transfer setting
in the Plant and Product category of the Manage Business Settings app.
Related Information
Manage Work Centers
Manage Business Settings
2.2.5.1.3 Transferring a Master Recipe
You can transfer a master recipe created or updated in SAP S/4HANA Cloud to SAP Digital Manufacturing.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
Cloud [page 323].
• You've set up the following communication arrangement in your SAP S/4HANA Cloud system:
Production Planning Master Data Integration (SAP_COM_0519).
• You've transferred the material master. For more information, see Transferring a Material Master [page
353].
Context
During production, master recipe data from SAP S/4HANA Cloud is required for the shop oor processes
that are going on in SAP Digital Manufacturing. Therefore, you need to transfer master recipe data from SAP
S/4HANA Cloud to SAP Digital Manufacturing to create or update the corresponding recipe record in SAP
Digital Manufacturing. Here you learn how to transfer a master recipe from SAP S/4HANA Cloud to SAP Digital
Manufacturing.
Note
Once you've transferred the recipe, SAP Digital Manufacturing calls the BOM from your SAP S/4HANA
Cloud system if at least one component is assigned to the recipe step. For more information, see Updating
and Upversioning a BOM [page 360].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 355
Procedural Steps
1. In your SAP S/4HANA Cloud system, open Replicate by Object Selection app.
2. Select Master Recipe from the Business Object Type dropdown.
3. Enter the following elements in the Business Objects to be Replicated table:
• Material
• Plant
• Type
• Group
• Group Counter
4. Select a target system under Target System Selection.
Note
The target system is the business system you dened for the communication system. For more
information, see Creating a Communication System [page 327].
5. Choose Replicate.
6. To verify whether the master recipe has been transferred to SAP Digital Manufacturing, you've got the
following options:
• In SAP S/4HANA Cloud, check the replication status by choosing Display Log.
• In SAP S/4HANA Cloud, check the message status in the Message Dashboard.
• In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of
your Master Recipe Download integration message. For more information, see Integration Message
Dashboard.
7.
2.2.5.1.4 Transferring a Master Routing
You can transfer a master routing created or updated in SAP S/4HANA Cloud to SAP Digital Manufacturing.
Prerequisites
• You've set up the technical integration. For more information, see Technical Integration with SAP S/4HANA
Cloud [page 323].
• You've set up the following communication arrangement in your SAP S/4HANA Cloud system:
Production Planning Master Data Integration (SAP_COM_0519).
• You've transferred the material master. For more information, see Transferring a Material Master [page
353].
356
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Context
During production, master routing data from SAP S/4HANA Cloud is required for the shop oor processes
that are going on in SAP Digital Manufacturing. Therefore, you need to transfer master routing data from SAP
S/4HANA Cloud to SAP Digital Manufacturing to create or update the corresponding routing record in SAP
Digital Manufacturing. Here you learn how to transfer a master routing from SAP S/4HANA Cloud to SAP
Digital Manufacturing.
Note
Once you've transferred the master routing, SAP Digital Manufacturing calls the BOM from your SAP S/
4HANA Cloud system if at least one component is assigned to the routing step. For more information, see
Updating and Upversioning a BOM [page 360].
Procedural Steps
1. In your SAP S/4HANA Cloud system, open the Replicate by Object Selection app.
2. Select Production Bill of Operations from the Business Object Type dropdown.
3. Enter the following elements in the Business Objects to be Replicated table:
• Material
• Plant
• Type
• Group
• Group Counter
4. Select a target system under Target System Selection.
Note
The target system is the business system you dened for the communication system. For more
information, see Creating a Communication System [page 327].
5. Choose Replicate.
6. To verify whether the master routing has been transferred to SAP Digital Manufacturing, you've got the
following options:
• In SAP S/4HANA Cloud, check the replication status by choosing Display Log.
• In SAP S/4HANA Cloud, check the message status in the Message Dashboard.
• In SAP Digital Manufacturing, go to the Integration Message Dashboard and check the status of
your Master Routing Download integration message. For more information, see Integration Message
Dashboard.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 357
2.2.5.1.5 Transferring 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 323])
• 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 346]
Destination S4H_ODATA_INTEGRATION [page 348]
Manage Nonconformance Groups
Manage Nonconformance Codes
358
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2.2.5.1.6 Current Version Dependencies
You can change the current version of dierent 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.7 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 elds trigger material upversioning:
• Base UOM
• Material UOM
• Material Type
• Production Version
Changes in all other elds will result in a material update only.
2.2.5.1.8 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 elds 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.9 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 elds trigger routing upversioning:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 359
• Description
• Adding Operation Activities
• Removing Operation Activities
• Status
Changes to the following routing operation activity elds trigger routing upversioning:
• Description
• Work Center
• Control Key
• Long Text
• Standard Value Keys and Values
• Normal Operation Activity
Changes in all other elds will result in a routing update only.
2.2.5.1.10Updating 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
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 elds trigger BOM upversioning:
• Description
• Add Component
• Remove Component
• Change Quantities
• Header Base Quantity
• Component Type
• Component UOM
• Component Scrap %
Changes in all other elds will result in a BOM update only.
360
PUBLIC
SAP Digital Manufacturing Integration Guide
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 Conrmation Quantity Conrmation
Material Consumption (Goods Issue) Material Consumption (Goods Issue)
Goods Receipt Goods Receipt
Activity Conrmation Activity Conrmation
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 351]).
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 361
Implementation Considerations
Some functions may behave dierently depending on the SAP S/4HANA Cloud version used for integration
with SAP Digital Manufacturing for execution.
Related Information
Integration of Master Data [page 351]
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've 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
Conrmation Integration (SAP_COM_0522) [page 341].
• 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.
362
PUBLIC
SAP Digital Manufacturing Integration Guide
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
You can update an order from your integrated ERP system before and after the release in SAP Digital
Manufacturing. The updating options you have vary depending on the order category and the integrated
ERP system. For more information, see Updating Orders Before the Release [page 209] and Updating
Orders After the Release [page 214].
Note
The order-specic BOM and routing/recipe are created in SAP Digital Manufacturing using the data
available in the order that has been transferred from SAP S/4HANA Cloud to SAP Digital Manufacturing.
2.2.5.2.2 Transfer of Floor Stock Data
You can transfer oor 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 lter 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 363
Note
For consolidated inventory management mode, you need to enable the API_MATERIAL_STOCK_SRV
technical service in SAP S/4HANA Cloud.
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 oor 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 oor 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.
364
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• When you post a transfer of unrestricted-use stock from a central (issuing) storage location to a oor 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 Cloud triggers the outbound message MMIM_MATDOC_GDSMVMT_ESOA to integrate the
oor stock to the production storage location in SAP Digital Manufacturing for execution with Inventory ID
created to the new inventory.
If the material is batch-managed or serialized material, the Batch Number or Serial Number is also created
and displayed in the new inventory.
The inventory is ready for consumption without reservation in SAP Digital Manufacturing for execution.
• A oor stock receipt is created for the specied components.
When COLLABORATION_GOODS_ISSUE_CONFIRMATION is triggered, SAP Digital Manufacturing for execution
sends a conrmation 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 oor stock management.
• A transfer posting in SAP ERP or SAP S/4HANA is used in the same way as a oor stock receipt in SAP
Digital Manufacturing for execution.
• For inventory ID records created in SAP Digital Manufacturing for execution through the integration, the
eld ERP Inventory is checked.
Prerequisites
SAP S/4HANA Cloud
• You have created production storage locations for oor stock materials.
• You have set up communication arrangement for SAP_COM_0108 and SAP_COM_0263.
• You have set up a lter for Print Active and the goods movement type 311 in Output Parameter
Determination.
• You have created a BOM for the nished 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-specic consumption scenario, you have created or imported shop order data so
that components can be pegged.
• You have dened a numbering pattern for the number type oor 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 365
• 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.1Updating Integration Conguration to Use Floor
Stock Data
If you want to use the oor stock integration functionality in SAP Digital Manufacturing, you need to update
some settings in your integration conguration, as described in this topic.
Prerequisites
You have made the following congurations to connect SAP Digital Manufacturing for execution to SAP S/
4HANA Cloud:
• Creating a Service Instance and a Service Key [page 328]
• Creating a Communication User [page 326]
• Creating a Communication System [page 327]
• Creating Communication Arrangements [page 330]
• Creating Destinations [page 348]
• Managing Supported Plants [page 349]
• Dening Operations in SAP S/4HANA Cloud for SAP Digital Manufacturing for execution [page 350]
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 conguration 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_INVENTORY_CLEAR_RESERVATION to the collaboration link
COLLABORATION_ERP_INV_CLEAR_RESERVATION for the inventory return activity.
Results
You can now use the oor stock functionality as described in this chapter.
366
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
If you have already enabled the transfer of oor 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.2Transfer of Floor Stock Return Data
You can transfer oor stock return data from SAP Digital Manufacturing for execution to SAP S/4HANA Cloud.
Use
This function lets you transfer oor 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 oor stock return to a central storage
location.
2. The SAP Digital Manufacturing collaboration COLLABORATION_ERP_INV_CLEAR_RESERVATION
(ERP_INVENTORY_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 oor 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 ow of a oor stock return that's synchronized from SAP Digital Manufacturing for
execution to SAP S/4HANA Cloud for process order-independent oor stock.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 367
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 oor stock management.
Prerequisites
SAP Digital Manufacturing
You have received oor stock data from SAP S/4HANA Cloud.
Activities
When you decrease the value of the Qty on Hand eld 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.
368
PUBLIC
SAP Digital Manufacturing Integration Guide
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.
For an overview of prerequisites and the steps required to update batch characteristics, see Updating Batch
Characteristics.
2.2.5.2.4 Batch Creation
You can transfer batch number created in SAP Digital Manufacturing to SAP S/4HANA Cloud.
The batch creation message is triggered when batch number is created in SAP Digital Manufacturing for
execution. For an overview of prerequisites and the steps required to create batch numbers, see 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
• 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 Conrmation Integration (SAP_COM_0522) [page 341].
• The inspection lot (type 03) has been created and assigned inspection characteristics.
Note
You can use after acceptance or rejection characteristics that are dened in an integrated ERP system.
The acceptance or rejection characteristic is a conditional characteristic that depends on the valuation
results of the previous mandatory characteristic in the same operation.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 369
Acceptance or rejection characteristics are supported for production orders from SAP S/4HANA Cloud
in the Order POD and the Work Center POD.
• 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 370]
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 345].
Procedure
1. In the Work Center POD, record inspection results for the order you want to work on.
2. Complete an operation activity of the order. The system updates the inspection characteristics data for
your order in SAP S/4HANA Cloud.
370
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Related Information
Inspection Characteristics Integration (Production Order) [page 369]
2.2.5.2.7 Enrichment with Sub-Operations for Discrete
Manufacturing
You can add sub-operations to an order-specic routing in SAP ERP, SAP S/4HANA, or SAP S/4HANA Cloud,
and then transfer this routing to SAP Digital Manufacturing. You can also add sub-operations to a master
routing in SAP ERP or SAP S/4HANA and then transfer this routing to SAP Digital Manufacturing.
Overview
In a discrete industry scenario, you can add sub-operations to an order-specic routing in SAP ERP, SAP
S/4HANA, or SAP S/4HANA Cloud.
Caution
Transferring a master routing with sub-operations to SAP Digital Manufacturing is supported only in SAP
ERP and SAP S/4HANA.
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 conrmations are posted against the ERP parent Operation.
Mapping
In SAP Digital Manufacturing, ERP routings containing sub-operations are mapped as follows:
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
SAP Digital Manufacturing operation activity IDs for the case of suboperations consist of the ERP operation ID
(the rst four digits) and the ERP sub-operation ID (the last four digits).
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 371
2.2.5.2.8 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 has been released to the shop oor and SFCs have been created in SAP Digital
Manufacturing.
Use
Before releasing an order to the shop oor 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 nd an overview of the supported update scenarios. "X" means that the corresponding update is
supported.
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Finished Goods
Batch Number
(Order Header)
X X X X X X
Goods Receipt
Storage Loca-
tion (Order
Header)
X
X X X X X
Customer
Name (Order
Header)
X X N/A N/A N/A N/A
Sales Order
(Order Header)
X X X N/A N/A N/A
Custom Field
(Order Header)
X X N/A X X N/A
Work Instruc-
tion (Order
Header)
X X N/A N/A N/A N/A
Dates Changes
(Order Header)
X X X X X X
372 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Inspection Lot
Change (Order
Header)
X X X X X X
Operation
Schedule (Or-
der Schedule)
X X X X X X
Production
Version (Order
Header)
X X N/A X X N/A
Scheduling
Type (Order
Header)
N/A N/A N/A N/A N/A N/A
Quantity De-
crease (Order
Header)
X X X X X X
Quantity In-
crease (Order
Header)
X X X X X X
Serial Number
(Order Header)
X X X N/A N/A N/A
Technical Com-
pletion (TECO)
(Order Header)
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
X
Note
If you re-
voke the
technical
completion
in your ERP
system, the
order stays
in status
Closed in
SAP Digital
Manufactur
ing.
Order Header
Long Text (Or-
der Header)
X X X X X X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 373
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Order Header
Schedule
Dates/Plan
Dates (Order
Header)
X
X X X X X
BOM Compo-
nent Storage
Location (BOM
Component)
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
BOM Compo-
nent Batch
Number (BOM
Component)
X
X X X X X
Underdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Overdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Warehouse
Number (Order
Header)
X X X X X X
Addition / Re-
moval of Com-
ponent (BOM
Component)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Component
Assignment
Change to Op-
eration Activ-
ity / Phase
(BOM Compo-
nent)
X
X X X X X
374 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Addition / Re-
moval of Oper-
ation / Phase
(Operation)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Work Center
Change in Op-
eration /
Phase (Opera-
tion)
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
Control Key
(Operation)
X X X X X X
Change of
Component
Quantities
(BOM Compo-
nent)
X
X X X X X
Operation/
Phase Number
(Operation)
X X X
Operation/
Phase Text
(Operation)
X X X X X X
Order-Specic
Bill of Mate-
rial*
X X X X X X
Order-Specic
Routing*
X X X X X X
Priority (Order
Header)
X X N/A X X N/A
Warehouse
Number (BOM
Component)
X X X X X X
ERP Bom ID X X X X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 375
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
ERP Bom Us-
age
X X X X
ERP Alterna-
tive Bom ID
X X X X
ERP Routing
Group
X X
ERP Group
Counter
X X
ERP Recipe
Group
X X
ERP Recipe X X
*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
• Changes to component units of measure, line numbers, or storage locations
2.2.5.2.9 Updating Orders After the Release
Learn about the options you've got for updating a production or process order from your integrated ERP
system after the order has been released to the shop oor and SFCs have been created in SAP Digital
Manufacturing.
Prerequisites
• For integration scenarios with SAP ERP or SAP S/4HANA, see Updating Orders After the Release (Custom
XSLT).
Note
For integration scenarios with SAP S/4HANA Cloud, there are no actions required.
• The order isn't in status Completed, Discarded, or Closed in SAP Digital Manufacturing.
376
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Use
After releasing an order to the shop oor in the Manage Orders app, you can update it from your integrated ERP
system. The updating options you've got depend on the order type and the integrated ERP system you're using.
Overview
Here you'll nd an overview of the supported update scenarios. "X" means that the corresponding update is
supported.
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Finished Goods
Batch Number
(Order Header)
X X X X X X
Goods Receipt
Storage Loca-
tion (Order
Header)
X
X X X X X
Customer
Name (Order
Header)
X X N/A N/A N/A N/A
Sales Order
(Order Header)
X X X N/A N/A N/A
Custom Field
(Order Header)
X X N/A X X N/A
Work Instruc-
tion (Order
Header)
X X N/A N/A N/A N/A
Dates Changes
(Order Header)
X X X X X X
Inspection Lot
Change (Order
Header)
N/A N/A N/A N/A N/A N/A
Operation
Schedule (Or-
der Schedule)
X X X X X X
Production
Version (Order
Header)
X X N/A X X N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 377
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Quantity De-
crease (Order
Header)
X
Note
Production
orders from
SAP ERP or
communi-
cated
through
processed
in the Work
Center POD
are sup-
ported.Pro-
duction Or-
der Down-
load (LOI-
PRO05 V2)
X
Note
Production
orders from
SAP ERP or
SAP S/
4HANA
communi-
cated
through
Production
Order
Download
(LOIPRO05
V2) proc-
essed in
the Work
Center POD
are sup-
ported.
X
N/A N/A N/AX
Quantity In-
crease (Order
Header)
X X X X X X
Serial Number
(Order Header)
X X X N/A N/A N/A
Technical Com-
pletion (TECO)
(Order Header)
N/A N/A N/A N/A N/A N/A
Order Header
Long Text (Or-
der Header)
X X X X X X
Order Header
Schedule
Dates/Plan
Dates (Order
Header)
X
X X X X X
378 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
BOM Compo-
nent Storage
Location (BOM
Component)
X
Note
Production
Order
Down-
loadThe
BOM com-
ponent
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
X
Note
The BOM
component
storage lo-
cation
change is
supported
by EWM
2021 or
higher.
BOM Compo-
nent Batch
Number (BOM
Component)
X
X X X X X
Underdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Overdelivery
Tolerance (Or-
der Header)
X X X N/A N/A N/A
Warehouse
Number (Order
Header)
X X X X X X
Addition / Re-
moval of Com-
ponent (BOM
Component)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Component
Assignment
Change to Op-
eration Activ-
ity / Phase
(BOM Compo-
nent)
X
X X X X X
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 379
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Addition / Re-
moval of Oper-
ation / Phase
(Operation)
X
X
X (Addition)
N/A (Removal)
X X
X (Addition)
N/A (Removal)
Work Center
Change in Op-
eration /
Phase (Opera-
tion)
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
X
Note
For integra-
tion with
EWM, the
new target
work cen-
ter must be
mapped to
a produc-
tion supply
area (PSA).
Control Key
(Operation)
X X X X X X
Work Instruc-
tion (Opera-
tion)
X X N/A N/A N/A N/A
Change of
Component
Quantities
(BOM Compo-
nent)
X
X X X X X
Operation/
Phase Number
(Operation)
X X X
Operation/
Phase Text
(Operation)
X X X X X X
Order-Specic
Bill of Mate-
rial*
X X X X X X
Order-Specic
Routing*
X X X X X X
Priority (Order
Header)
X X N/A X X N/A
380 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Update
SAP ERP
Production Or-
der
SAP S/4HANA
Production Or-
der
SAP S/4HANA
Cloud
Production Or-
der
SAP ERP
Process Order
SAP S/4HANA
Process Order
SAP S/4HANA
Cloud
Process Order
Warehouse
Number (BOM
Component)
X X X X X X
ERP Bom ID X X X X
ERP Bom Us-
age
X X X X
ERP Alterna-
tive Bom ID
X X X X
ERP Routing
Group
X X
ERP Group
Counter
X X
ERP Recipe
Group
X X
ERP Recipe X X
*Objects are up-versioned if one of the following changes takes place:
• Changes to work centers on operations / phases
• 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 units of measure, line numbers, or storage locations
2.2.5.3 Field Mapping for the Integration to SAP S/4HANA
Cloud
The elds created in SAP S/4HANA Cloud correspond to certain elds 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].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 381
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 S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
productInternalID material
N/A
baseMeasureUnitCode unitOfMeasure
N/A
Every description with a supported
languageCode
descriptions
Only supported language codes will be
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/
procurementTypeCode
procurementType
If E→ Manufactured.
If F→ Purchased.
In other cases →
Manufactured_purchased.
supplyPlanning/
productRequirementsPlanningRes
ponsibleCode
mrpController
N/A
plant/plantId plant
N/A
N/A
incrementBatchNumber
If product/
batchManagementRequiredIndicat
or = true or product/plant/
batchManagementRequiredIndicat
or = true → ORDER.
In other cases → NONE.
plant/workScheduling/
productionInventoryManagedLoca
tionInternalID
productionStorageLocation or
putawayStorageLocation
If procurementType = Manufactured
→ putawayStorageLocation
In other cases →
productionStorageLocation
N/A
DataCollectionGroup
If Material procurementType
= Manufactured or
Manufactured_purchased
382 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
DataCollectionGroup/status releasable
N/A
DataCollectionGroup/plant
N/A
N/A
DataCollectionGroup/version A
N/A
DataCollectionGroup/
currentVersion
true
API_CLFN_PRODUCT_SRV/
A_ClfnClassForKeyDate/Class
DataCollectionGroup/dcGroup
N/A
API_CLFN_PRODUCT_SRV/
A_ClfnClassForKeyDate/
ClassTypeName
DataCollectionGroup/
description
dcGroup
Not developed yet.
DataCollectionGroup.attachedPo
ints[0].material
material
API_CLFN_CHARACTERISTIC_SRV/
A_ClfnCharacteristicForKeyDate
/Characteristic
DataCollectionGroup.dcParamete
rs[].parameterName
N/A
API_CLFN_CHARACTERISTIC_SRV/
A_ClfnCharacteristicForKeyDate
/CharcDescription
DataCollectionGroup.dcParamete
rs[].description
parameterName
If En localization not null.
API_CLFN_CHARACTERISTIC_SRV/
A_ClfnCharacteristicForKeyDate
/CharcDataType
DataCollectionGroup.dcParamete
rs[].dcParameterType
TEXT
N/A
DataCollectionGroup.dcParamete
rs[].sequence
N/A
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
class name)
DataType/dataType (datatype name) N/A
product/class/characteristics DataType/dataFields
N/A
characteristic DataField
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 383
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
characteristic/EntryIsRequired DataField/Required
N/A
material/plant DataField/Plant
N/A
characteristic/characteristic
(name)
DataField/fieldName
N/A
characteristic/CharcDataType DataField/type
N/A
characteristic/CharcStatus DataField/status
N/A
characteristic/
CharcDescription
DataField/description
If language code is set to EN.
characteristic/
CharcDescription
DataField/fieldLabel
If language code is set to EN.
characteristic/CharcDataType DataField/type
If NUM→ FieldType/NUMBER.
If CHAR → FieldType/TEXT.
If DATE → FieldType/DATE.
If Default →
FieldType.TEXT_AREA.
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 S/4HANA Cloud Field
SAP Digital Manufacturing
for execution Field Conditions
N/A
/version A
384 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing
for execution Field Conditions
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ProductionPlant
/plant
N/A
N/A
/status RELEASABLE
N/A
/currentVersion True
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/Material
/description
N/A
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ManufacturingOrder
/recipe
N/A
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
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:MfgOrderOperationText
/routingSteps/
description
N/A
N/A
/routingSteps/isEntry
True for the rst step.
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation
/routingSteps/
reportingStep
N/A
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ProductionPlant
/routingSteps/
workCenter/plant
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:WorkCenter
/routingSteps/
workCenter/workCenter
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 385
SAP S/4HANA Cloud Field
SAP Digital Manufacturing
for execution Field Conditions
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ProductionPlant
/routingSteps/
routingOperation/
operation/plant
N/A
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ManufacturingOrder-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderSequence-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation
/routingSteps/
routingOperation/
operation/operation
N/A
N/A
/routingSteps/
routingOperation/
operation/version
Default A
N/A
/routingSteps/
routingOperation/
stepType
NORMAL N
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ManufacturingOrder-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/Material-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/BillOfMaterialVariant
/routingSteps/
routingStepComponentLi
st/
bomComponent/bom/bom
N/A
N/A
/routingSteps/
routingStepComponentLi
st/bomComponent/bom/
version
Default A
N/A
/routingSteps/
routingStepComponentLi
st/bomComponent/bom/
bomType
Default SHOPORDERBOM
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderComponent/Material
/routingSteps/
routingStepComponentLi
st/bomComponent/
material/material
N/A
386 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing
for execution Field Conditions
N/A
/routingSteps/
routingStepComponentLi
st/bomComponent/
material/version
Default A
N/A
/routingSteps/
routingStepComponentLi
st/bomComponent/
sequence
10 based counter. Se-
quence in the order
BOM.
N/A
/routingSteps/
routingStepComponentLi
st/sequence
10 based counter
N/A
/routingSteps/
nextStepList/nextStep/
stepId
The ID of the next step.
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/ManufacturingOrder-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderSequence-/
n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:ManufacturingOrderOperation
/
routingOperationGroups
/routingOperationGroup
N/A
/n0:ManufacturingOrderExecuteRequest/
ManufacturingOrder/
ManufacturingOrderActivityNetworkElement/
n1:MfgOrderOperationText
/
routingOperationGroups
/description
N/A
Shop Order Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder
/shopOrder
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 387
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
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
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrdPlndTotQtyInBaseUnit
/erpUnitOfMeasure
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/routing/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder
/routing/routing
N/A
N/A
/routing/routingType
If ManufacturingOrderCategory
= 40, then
SHOPORDER_SPECIFIC_RECIPE. Oth-
erwise, SHOPORDER_SPECIFIC.
N/A
/routing/version
Default A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material
/material/material
N/A
N/A
/material/version
Default A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/material/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/bom/plant
N/A
388 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant
/bom/bom
N/A
N/A
/bom/bomType
Default SHOPORDERBOM
N/A
/bom/version
Default A
N/A
/priority 500
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedStartDate + /
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderScheduledStartTime
/plannedStartDate
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedEndDate + /
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderScheduledEndTime
/plannedCompletionDate
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedTotalQty
/buildQuantity
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
MfgOrderPlannedTotalQty
/orderedQuantity
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 389
Order BOM Mapping for the BOM Header
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/version
Default A
N/A
/currentVersion
Default True
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant
/bom AUFNR-MATNR-STLAN-STLAL
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material
/description
N/A
N/A
/bomType
Default SHOPORDERBOM
N/A
/status
Default RELEASABLE
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterial
/erpBom
N/A
Order BOM Mapping for the BOM Component
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/sequence
10 based counter
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/RequiredQuantityInBaseUnit
/quantity
N/A
390 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
material/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/Material
material/material
N/A
N/A
material/version
Default A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
bom/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
Material-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariantUsage-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
BillOfMaterialVariant
bom/bom
N/A
N/A
bom/bomType
Default SHOPORDERBOM
N/A
bom/version
Default A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderComponent
/Batch
.customValues.BATCH_NUMBER
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 391
Order Mapping for the Data Collection Group
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/plant
N/A
N/A
/version
Default A
N/A
/currentVersion
Default True
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation
@SVK
/dcGroup
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/
@StandardWorkFormulaParamGroup
ID
/description
N/A
392 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Order Data Collection Group Mapping for the Data Collection Parameter
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation
-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
@WorkCenterFormulaParamID
/parameterName
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
StandardWorkFormulaParamName
/description
N/A
N/A
/sequence
10 based sequence
N/A
/dcParameterType NUMBER
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:StandardWorkFormulaParamGro
up/WorkCenterFormulaParam1/
WorkCenterStandardWorkQty/
@unitCode
/unitOfMeasure
N/A
Order Data Collection Group Mapping for the Data Collection Group Attachment Point
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/sequence 10
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 393
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/routingStep
Routing step reference
Order Mapping for the Operation Activity Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ProductionPlant
/plant
N/A
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrder-/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderSequence-
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:ManufacturingOrderOperation
/operation
N/A
N/A
/version
Default A
N/A
/currentVersion
Default True
N/A
/type
Default NORMAL_OPERATION
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:MfgOrderOperationText
/description
N/A
N/A
/status
Default RELEASABLE
N/A
/resourceType
Default DEFAULT
394 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/n1:WorkCenter
/workCenter
N/A
Master Recipe Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/version
Deault A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/plant
N/A
N/A
/status
Default RELEASABLE
N/A
/currentVersion
Default True
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup
/description
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant
/recipe
N/A
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 395
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription
/routingSteps/description
N/A
N/A
/routingSteps/isEntry
True for the rst step.
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation
/routingSteps/reportingStep
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/routingSteps/workCenter/plant
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/WorkCenter
/routingSteps/workCenter/
workCenter
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/routingSteps/
routingOperation/operation/
plant
N/A
396 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation
/routingSteps/
routingOperation/operation/
operation
N/A
N/A
/routingSteps/
routingOperation/operation/
version
Default A
N/A
/routingSteps/
routingOperation/stepType
NORMAL N
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation
/routingOperationGroups/
routingOperationGroup
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 397
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription
/routingOperationGroups/
description
N/A
Master Recipe Operation Activity Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/plant
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation
/operation
N/A
N/A
/version
Default A
N/A
/currentVersion
Default True
N/A
/type
Default NORMAL_OPERATION
398 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
OperationDescription
/description
N/A
N/A
/status
Default RELEASABLE
N/A
/resourceType
Default DEFAULT
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/WorkCenter
/workCenter
N/A
Master Recipe Data Collection Group Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/plant
N/A
N/A
/version
Default A
N/A
/currentVersion
Default True
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 399
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsGroup-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsVariant-/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/Operation
/dcGroup
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
@StandardWorkFormulaParamGroup
ID
/description
N/A
400 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Master Recipe Data Collection Parameter Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
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
/parameterName
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName
/description
N/A
N/A
/sequence
10 based sequence
N/A
/dcParameterType NUMBER
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 401
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
WorkCenterStandardWorkQty/
@unitCode
/unitOfMeasure
N/A
Master Recipe Data Collection Group Attachment Point Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
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 S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsHeader/
n1:BillOfOperationsPlant
/plant
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
@StandardWorkFormulaParamGroup
ID
/standardValKey
N/A
402 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
@WorkCenterFormulaParamID
/standardVal
N/A
10 based sequence
/sequence
N/A
Master Recipe Standard Value Key Mapping for a Standard Value Text
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName/
@languageCode
/locale
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
StandardWorkFormulaParamName
/description
N/A
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 403
Master Recipe Standard Value Key Mapping for a Standard Value Target
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
N/A
/id
N/A
10 based sequence
/stepId
N/A
/
n0:ManufacturingMasterRecipeIn
fomationMessage/
BillOfOperations/
BillOfOperationsActivityNetwor
kElement/
BillOfOperationsActivityNetwor
kElementTimeSlice/
StandardWorkFormulaParamGroup/
WorkCenterFormulaParam1/
WorkCenterStandardWorkQty
/targetValue
N/A
Master Recipe BOM Header oData Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
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-
BillOfMaterialVariant
bom
N/A
Master Recipe BOM Component oData Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
BillOfMaterialItemQuantity quantity
N/A
BillOfMaterialItemUnit unitOfMeasure
N/A
BOMItemInternalChangeCount changeNumber
N/A
BillOfMaterialItemNodeNumber sequence
N/A
BillOfMaterialItemNodeNumber erpSequence
N/A
404 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
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 elds
Control Key Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
execution Field Conditions
/
n0:ManufacturingOrderExecuteRe
quest/ManufacturingOrder/
ManufacturingOrderActivityNetw
orkElement/
n1:OperationControlProfile/
@n1:OperationControlKey
/controlKey
N/A
N/A
/gi
N/A
Statuses Mapping
SAP S/4HANA Cloud Field
SAP Digital Manufacturing for
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 S/4HANA Cloud
SAP Digital Manufacturing for
execution Comment
GlobalTradeItemNumber unitsOfMeasureEans
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 405
SAP S/4HANA Cloud
SAP Digital Manufacturing for
execution Comment
tradeNumber.productStandardID Ean.ean
tradeNumber.getProductStandard
VariantID())
Ean.category
tradeNumber.isProductStandardM
ainIndicator()
Ean.isMain
tradeNumber.getMeasureUnitCode
Uom.grossWeight
Ean.netWeight
Ean.internalUom
Ean.grossWeight
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 elds of the order header material.
Database
eld
XML order eld of node
ManufacturingOrder.Man
ufacturingOrderItem.
GoodsReceiptTolerances
DMC eld Type
SHOP_ORDER.
TOLERANCE_UNDER
UnderdelivTolrtdLmtRat
ioInPct
ShopOrder.toleranceUnd
er
BigDecimal
SHOP_ORDER.
TOLERANCE_OVER
OverdelivTolrtdLmtRati
oInPct
ShopOrder.toleranceOve
r
BigDecimal
SHOP_ORDER.
OVER_DELIVERY_IS_ALLOW
ED
UnlimitedOverdeliveryI
sAllowed
ShopOrder.overDelivery
IsAllowed
Boolean
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
406
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
SAP S/4HANA Cloud
DME Field Default Value SAP S/4HANA Cloud Field
alternativeItemGroup
ERP Alternate Item Group
AlternativeItemGroup
alternates.enabled
Alternates Enabled
TRUE
alternates.priority
Alternates Priority
AlternativeItemPriority
alternates.material
Alternate Component
BillOfMaterialComponent
Order BOM
SAP S/4HANA Cloud
DME Field Default Value SAP S/4HANA Cloud Field
alternativeItemGroup
ERP Alternate Item Group
AlternativeItemGroup
alternates.enabled
Alternates Enabled
TRUE
alternates.priority
Alternates Priority
AlternativeItemPriority
alternates.material
Alternate Component
Material
2.2.5.3.4 Mapping for a Standard Value Key (SVK)
The elds created in SAP S/4HANA Cloud correspond to certain elds 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 407
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
408 PUBLIC
SAP Digital Manufacturing Integration Guide
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.3 Integration with EWM
You can integrate SAP Digital Manufacturing with EWM to achieve planned and ecient processing of all
logistics processes in your warehouse.
Why EWM
Dierent 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
specic 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 nished goods in a container and trigger the transfer of goods receipt back to SAP ERP.
To learn more about how to set up the congurations to connect SAP Digital Manufacturing and EWM, see
Connecting to EWM in SAP S/4HANA 1909 to 2020 （Deprecated） [page 410] or Connecting to EWM in SAP
S/4HANA 2021 [page 416]. 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 applies to the EWM embedded in SAP S/4HANA
2021 and higher versions, as well as decentralized EWM based on SAP S/4HANA 2021 and higher.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 409
The integration with EWM supports only SAP S/4HANA and SAP ERP. If you're using SAP S/4HANA, you have
the option to use either the embedded or the decentralized EWM. But, if you're using SAP ERP, you can only
use the decentralized EWM.
Related Information
Minimum Version Requirements and Supported Scenarios [page 410]
2.3.1Minimum 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 2021 and higher version, as
well as decentralized EWM based on SAP S/4HANA 2021 and higher.
Scenarios Supported
For more information about the supported scenarios, see EWM Integration Scenarios.
2.3.2Connecting to EWM in SAP S/4HANA 1909 to 2020
（Deprecated）
This topic shows you the congurations you need to enable integration with EWM versions ranging from EWM
in SAP S/4HANA 1909 to EWM in SAP S/4HANA 2020.
Note
The integration with EWM versions lower than EWM in SAP S/4HANA 2021 is deprecated. You're still able
to use the older version, but it's set to be decommissioned and won't be available for use after one year. If
you’re using the older versions, we suggest you switch to integration with EWM in SAP S/4HANA 2021 or
higher versions as soon as you can.
410
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• #unique_307/unique_307_Connect_42_subsection-im1 [page 411]
• #unique_307/unique_307_Connect_42_subsection-im2 [page 411]
• #unique_307/unique_307_Connect_42_subsection-im3 [page 411]
• #unique_307/unique_307_Connect_42_subsection-im4 [page 412]
• #unique_307/unique_307_Connect_42_subsection-im5 [page 413]
Conguration in SAP S/4HANA
Follow the conguration steps in Technical Integration with SAP S/4HANA or SAP ERP [page 15] to enable
communication from EWM to SAP Digital Manufacturing.
Conguration in EWM
Please refer to SAP Note 2944311 for detailed congurations that needs to be completed in order to enable
the integration.
Conguration in SAP Cloud Connector
Congure 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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 411
3. Select the virtual host of the EWM system, and add below resources to it.
• /SCWM/MFG_CONSUME_ITEMS_EXT
External interface for EWM goods issue posting.
• /SCWM/MFG_REVERSE_ITEMS_EXT
External interface for EWM goods issue cancellation.
• /SCWM/MFG_READ_STOCK_EXT
External interface for EWM stock synchronization.
• /SCWM/MFG_RECEIVE_HUS_EXT
External interface for EWM goods receipt posting.
• /SCWM/MFG_REVERSE_HUS_EXT
External interface for EWM goods receipt cancellation.
• /SCWM/MFG_STAGE_EXT
External interface for EWM staging.
• BAPI
BAPI related external interfaces.
• CO_MES_PRODORDCONF_CREATE_TT
External interface for production order goods issue posting.
• MB_MES_GOODSMVT_CREATE
External interface for production order component add.
Note
The virtual host representing the EWM system also needs to be added as property in the RFC
destination in SAP Cloud Integration.
Conguration 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.
412
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
5. In Additional Properties, add the following properties:
Property Description Value
jco.client.ashost The Virtual Host of the EWM system
dened in the SAP Cloud Connector.
Example
<virtual host>
jco.client.client The client number of EWM. Example
1000
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
Conguration in SAP Digital Manufacturing
1. Set up logical systems and system destinations. Go to the Manage Business Settings app and congure the
following settings.
Field
Description Example
Integration Mode Indicates which ERP system SAP
Digital Manufacturing is integrated
with.
S/4 HANA
ERP Destination Enter here the destination of your
ERP system. Make sure the destina-
tion is the same as the one that
is congured for your SAP Cloud
Integration tenant. To see the ERP
destination congured for SAP Cloud
Integration tenant, go to SAP BTP
cockpit, and choose Connectivity
Destinations in the side menu bar.
Refer to below screenshot.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 413
Field Description Example
EWM Destination Enter here the destination name for
your EWM system. Make sure the
destination is the same as the one
that is congured for your SAP Cloud
Integration tenant. To see the EWM
destination congured for SAP Cloud
Integration tenant, go to SAP BTP
cockpit, and choose Connectivity
Destinations in the side menu bar.
Refer to below screenshot.
ERP Logical System The logical system of ERP de-
ned 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.
414
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Collaboration Link Collaboration Directive Description
EWM_COLLABORATION_SHOPORDER_R
ELEASE
EWM_SINGLE_ORDER_STAGING_REQU
EST
This collaboration link is triggered
by order release to send single-order
staging request to EWM.
EWM_COLLABORATION_COMPONENT_A
DD
EWM_COMPONENT_ADD This collaboration link is triggered by
Assemble Components plugin to send
component consumption to EWM.
EWM_COLLABORATION_YIELD_CONFI
RMATION
EWM_GOODS_ISSUE_POST When
EWM_COLLABORATION_COMPONENT_A
DD is not congured, this collabora-
tion link is triggered by SFC complete
to send component consumption to
EWM.
EWM_COLLABORATION_SFC_DISPOSI
TION
EWM_SFC_DISPOSITION When
EWM_COLLABORATION_COMPONENT_A
DD is not congured, this collabora-
tion link is triggered by SFC scrap to
send component consumption to
EWM.
COLLABORATION_SFC_COMP_REMOVE
_EWM_OP
EWM_COMPONENT_REMOVE_OP This collaboration link is triggered by
component removal for production
order in Work Center POD.
EWM_COLLABORATION_CONTAINER_C
LOSE
EWM_CONTAINER_CLOSE_CONFIRMAT
ION
This collaboration link is triggered by
closing container to send goods re-
ceipt message to EWM.
COLLABORATION_ERP_SCRAP_CONFI
RMATION
ERP_SCRAP_CONFIRMATION This collaboration link is triggered by
SFC scrap to report scrapped compo-
nent quantity to SAP ERP.
COLLABORATION_ERP_YIELD_CONFI
RMATION
ERP_YIELD_CONFIRMATION_V2 This collaboration link is triggered by
SFC Complete to report quantity of
nished goods to SAP ERP. For more
information, see 3420816 .
EWM_COLLABORATION_FG_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of nished goods to EWM.
EWM_COLLABORATION_CO_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of co-products to EWM.
EWM_COLLABORATION_BY_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of by-products to EWM.
COLLABORATION_INV_READ_EWM EWM_INV_READ This collaboration link is only re-
quired when you use the EWM stock
sync public API (/inventories/
ewmSynchronization.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 415
Related Information
Connecting to EWM in SAP S/4HANA 2021 [page 416]
Integration Scenario with EWM in SAP S/4HANA 1909 to 2020 (Deprecated)
2.3.3Connecting to EWM in SAP S/4HANA 2021
This topic shows you the congurations you need to enable integration with EWM in SAP S/4HANA 2021 or
higher versions.
Note
Compared to older EWM versions, you can use MES-driven staging which allows you to request materials
more exibly with EWM in SAP S/4HANA 2021 or higher versions. For more information, see Staging
Request.
• #unique_308/unique_308_Connect_42_subsection-im1 [page 417]
• #unique_308/unique_308_Connect_42_subsection-im2 [page 417]
416
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
• #unique_308/unique_308_Connect_42_subsection-im3 [page 426]
• #unique_308/unique_308_Connect_42_subsection-im4 [page 430]
• #unique_308/unique_308_Connect_42_subsection-im5 [page 433]
Conguration in SAP S/4HANA
Follow the conguration steps in Technical Integration with SAP S/4HANA or SAP ERP [page 15] to enable
communication from EWM to SAP Digital Manufacturing.
Conguration in EWM
Make the following congurations in EWM system. These mainly include using SOA Manager to complete the
conguration for consumer proxies for EWM, as well as some stock notication congurations.
Note
For additional information on the conguration process, see also 3137363
Note
To use the EWM WIP processing feature, in addition to the congurations listed below, ensure you've
nished all the settings in How to Set Up WIP Management .
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.
2. On the Enterprise Services Browser screen, choose Namespaces http://sap.com/xi/EWM/
Global Object Types Service Providers Objects , and you can nd an object named
WarehouseStagingRequest_In.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 417
418 PUBLIC
SAP Digital Manufacturing Integration Guide
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
nd 3 object named WarehouseRequestStatus_Out, WarehouseStagingMethod_Out and
WarehouseStockChangeNotication_Out respectively.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 419
2. Create and congure 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 .
420
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
3. On the Web Service Conguration screen of SOA Manager, choose Create Manual Conguration
to dene logical ports for the consumer proxy /SCWM/CO_BIF_STG_WHR_STATUS.
4. On the manual conguration screen, enter a name in Logical Port Name.
5. In Consumer Security, enter the P-user name and password that you've granted access to in your
SAP Cloud Integration subaccount in your SAP BTP cockpit. For more information, see Granting Your
P-User Access to SAP Cloud Integration in Cloud Foundry Environment [page 56].
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, see How to Get SAP Cloud
Integration Runtime URL [page 22].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 421
7. In SOAP Protocol, select the options as displayed in below screenshot.
8. Continue to complete the remaining steps. You can keep the default settings. Choose Finish.
9. Set the logical port to default by choosing Set Log.Port Default.
422
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
If you don't set the logical port to default, no messages are created.
10. Repeat step a-g to dene logical ports for the other two consumer services
WarehouseStagingMethod_Out and WarehouseStockChangeNotication_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 Conguration screen of SOA Manager, choose Create Service.
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 423
4. Make EWM stock synchronization congurations.
1. Execute the transaction code SPRO and choose SAP IMG Reference.
2. Choose SCM Extended Warehouse Management Extended Warehouse Management Interfaces
MES Integration Dene Synchronization of Stock Data for MES .
424
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
3. Leave ME System empty. Select Synchronized in the Synchronize Stock Data column.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 425
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 Dene Services
screen.
2. In the Hierarchy Type eld, 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 dene the staging method in EWM rst. For more
information, see Sending Staging Method to MES.
Conguration 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:
If you have already integrated with SAP S/4HANA, you should already have the RFC connection in place. In this
case, you can skip the rst three steps and go directly to Step 4.
426
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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.
3. In the Add System Mapping pop-up, ll in the required elds step by step. You can refer to below table for
eld values.
Field Name
Value
Back-end Type ABAP System
Protocol RFC
Connection Type Without load balancing
Application Server Example: idcixxx.wdf.sap.corp To nd the application server and in-
stance number of your ERP system:
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.
Instance Number
Example: 43000
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 427
Field Name Value
Virtual Application Server Example: xxxclnt910 It is recommended to use a virtual
server (cloud-side) name that is dif-
ferent from internal application server
name.
To enable EWM integration, make sure
you use the same value for these
elds:
•
The Virtual Application Server for
RFC protocol in the Cloud Con-
nector
• The Virtual Host for HTTPS pro-
tocol in the Cloud Connector
• The Destination of the SAP Cloud
Integration subaccount in SAP
BTP Cockpit
• The EWM Destination in the
Manage Business Settings app in
SAP Digital Manufacturing
To avoid errors in SAP Digital
Manufacturing's outgoing messages,
ensure the value you specify for the
above elds don't contain special
characters such as underscores, peri-
ods and hyphens, etc.
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
conguration in Connecting to EWM in SAP S/4HANA 1909 to 2020 （Deprecated） [page 410].
5. Samewise, add another mapping and this time, specify HTTPS as the Protocol. Refer to below table to ll
the required elds.
Field Name
Value
Back-end Type ABAP System
Protocol HTTPS
Internal Host Example: idcixxx.wdf.sap.corp To nd 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 .
428 PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Name Value
Internal Port Example: 43000
3. You can see the internal host
in the Host Name column, and
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 dierent
from internal host name.
To enable EWM integration, make sure
you use the same value for these
elds:
•
The Virtual Application Server for
RFC protocol in the Cloud Con-
nector
• The Virtual Host for HTTPS pro-
tocol in the Cloud Connector
• The Destination of the SAP Cloud
Integration subaccount in SAP
BTP Cockpit
• The EWM Destination in the
Manage Business Settings app in
SAP Digital Manufacturing
To avoid errors in SAP Digital
Manufacturing's outgoing messages,
ensure the value you specify for the
above elds don't contain special
characters such as underscores, peri-
ods and hyphens, etc.
Virtual Port
Example: 43000 The default value is the internal port
you entered previously. Leave it un-
changed.
Principal Type X.509 Certicate (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.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 429
Conguration in SAP Cloud Integration
Note
To enable EWM integration, make sure you use the same value for these elds:
• The Virtual Application Server for RFC protocol in the Cloud Connector
• The Virtual Host for HTTPS protocol in the Cloud Connector
• The Destination of the SAP Cloud Integration subaccount in SAP BTP Cockpit
• The EWM Destination in the Manage Business Settings app in SAP Digital Manufacturing
To avoid errors in SAP Digital Manufacturing's outgoing messages, ensure the value you specify for the
above elds don't contain special characters such as underscores, periods and hyphens, etc.
Add RFC destination of EWM in SAP Cloud Integration.
1. Log on to your SAP Cloud Integration subaccount in the SAP BTP Cockpit, and choose Connectivity
Destinations in the side menu bar.
2. Choose Create Destination and enter the following elds to create the destination.
430
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Name Type Proxy Type User Password Location ID
To enable EWM
integration, make
sure you use the
same value for
these elds:
•
The Virtual
Application
Server for
RFC protocol
in the Cloud
Connector
• The Virtual
Host for
HTTPS pro-
tocol in the
Cloud Con-
nector
• The
Destination
of the SAP
Cloud
Integration
subaccount
in SAP BTP
Cockpit
• The EWM
Destination in
the Manage
Business
Settings app
in SAP Digital
Manufacturin
g
To avoid errors
in SAP Digital
Manufacturing's
outgoing mes-
sages, ensure the
value you spec-
ify for the above
elds don't con-
tain special char-
acters such as
underscores, peri-
ods and hyphens,
etc.
RFC
OnPremise Enter the user-
name to access
EWM
Enter the pass-
word to access
EWM
If you have main-
tained a location
ID in the Cloud
Connector, enter
the location ID
here.
3. Add the following Additional Properties:
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 431
Property Description Value
jco.client.ashost The Virtual Host of the EWM system
as dened in the Cloud Connector.
Note
The virtual host dened here
must be the same as the EWM
destination congured in the
Manage Business Settings app.
Example
<virtual host>
jco.client.client The client number of EWM. Example
100
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
Conguration 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 Congure to set the following parameters.
• EWM_PORT
Enter the port that is congured in cloud connector virtual host as mentioned in the above
Conguration 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 Conguration in EWM section.
432
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Caution
The service name must be the same for all systems (development, quality, and production).
• Location ID
Enter the location ID that you have maintained in the Cloud Connector.
• Credential Name
Enter the security material name dened in SAP Cloud Integration. The credentials refer to a technical
user dened in EWM / SAP S/4HANA. For more information about the technical user, seeCreate a
Technical User for SAP S/4HANA [page 20] .
Caution
The user credentials must be the same for all systems (development, quality, production).
Conguration in SAP Digital Manufacturing
1. Set up logical systems and system destinations. Go to the Manage Business Settings app and congure the
following settings.
Field
Description Example
Integration Mode Indicates which ERP system SAP
Digital Manufacturing is integrated
with.
S/4 HANA
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 433
Field Description Example
ERP Destination Enter here the destination of your
ERP system. Make sure the destina-
tion is the same as the one that
is congured for your SAP Cloud
Integration tenant. To see the ERP
destination congured for SAP Cloud
Integration tenant, go to SAP BTP
cockpit, and choose Connectivity
Destinations in the side menu bar.
Refer to below screenshot.
EWM Destination Enter the destination of your ERP sys-
tem. Make sure the destination is the
same as the one that is congured
for your SAP Cloud Integration tenant.
To see the ERP destination congured
for the SAP Cloud Integration tenant,
go to SAP BTP cockpit, and choose
Connectivity Destinations in
the side menu bar.
To enable EWM integration, make sure
you use the same value for these
elds:
•
The Virtual Application Server for
RFC protocol in the Cloud Con-
nector
• The Virtual Host for HTTPS pro-
tocol in the Cloud Connector
• The Destination of the SAP Cloud
Integration subaccount in SAP
BTP Cockpit
• The EWM Destination in the
Manage Business Settings app in
SAP Digital Manufacturing
To avoid errors in SAP Digital
Manufacturing's outgoing messages,
ensure the value you specify for the
above elds don't contain special
characters such as underscores, peri-
ods and hyphens, etc.
434
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Field Description Example
ERP Logical System The logical system of ERP de-
ned 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 to EWM.
Collaboration Link
Collaboration Directive Description
EWM_COLLABORATION_SHOPORDER_R
ELEASE
EWM_SINGLE_ORDER_STAGING_REQU
EST
This collaboration link is triggered
by order release to send single-order
staging request to EWM.
EWM_COLLABORATION_COMPONENT_A
DD
EWM_COMPONENT_ADD This collaboration link is triggered by
Assemble Components plugin to send
component consumption to EWM.
EWM_COLLABORATION_YIELD_CONFI
RMATION
EWM_GOODS_ISSUE_POST When
EWM_COLLABORATION_COMPONENT_A
DD is not congured, 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 435
Collaboration Link Collaboration Directive Description
EWM_COLLABORATION_SFC_DISPOSI
TION
EWM_SFC_DISPOSITION When
EWM_COLLABORATION_COMPONENT_A
DD is not congured, this collabora-
tion link is triggered by SFC scrap to
send component consumption to
EWM.
COLLABORATION_SFC_COMP_REMOVE
_EWM_OP
EWM_COMPONENT_REMOVE_OP This collaboration link is triggered by
component removal for production
order in Work Center POD.
EWM_COLLABORATION_CONTAINER_C
LOSE
EWM_CONTAINER_CLOSE_CONFIRMAT
ION
This collaboration link is triggered by
closing container to send goods re-
ceipt message to EWM.
COLLABORATION_ERP_SCRAP_CONFI
RMATION
ERP_SCRAP_CONFIRMATION This collaboration link is triggered by
SFC scrap to report scrapped compo-
nent quantity to SAP ERP.
COLLABORATION_ERP_YIELD_CONFI
RMATION
ERP_YIELD_CONFIRMATION_V2 This collaboration link is triggered by
SFC Complete to report quantity of
nished goods to SAP ERP. For more
information, see 3420816 .
EWM_COLLABORATION_FG_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of nished goods to EWM.
EWM_COLLABORATION_CO_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of co-products to EWM.
EWM_COLLABORATION_BY_GOODS_RE
CEIPT
EWM_GOODS_RECEIPT This collaboration link is triggered by
Goods Receipt plugin to report goods
receipt of by-products to EWM.
COLLABORATION_INV_READ_EWM EWM_INV_READ This collaboration link is only re-
quired when you use the EWM stock
sync public API (/inventories/
ewmSynchronization.
Related Information
Connecting to EWM in SAP S/4HANA 1909 to 2020 （Deprecated） [page 410]
Integration Scenario with EWM in SAP S/4HANA 2021
2.3.4Mapping Plants (Plant Conversion)
If you're managing the same plant in multiple EWM systems, you can use plant conversion to map the EWM
plant to dierent plants in SAP Digital Manufacturing.
436
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
Plant conversion is supported in integration with EWM in SAP S/4HANA 2021 version or higher.
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 Congure .
4. Select the EWM row item and add value-mapping conguration.
5. For each EWM plant in one EWM system, add two mapping items. For example, if you've maintained the
same plant A in two EWM systems, you need to congure the mappings as follows:
EWM, PLANT
DMC, PLANT
<EWM programID A>:<EWM Plant A>
Note
For EWM embedded 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 customizing, go
to
SCM Extended Warehouse Management SCM
Basis Integration Basic Settings for Creating the
System Landscape
Name Logical Systems .
<DMC Plant A1>
<EWM Destination A>:<EWM PlantA>
Note
Use the EWM destination maintained in the Manage
Business Settings app. In this app, you can freely de-
ne the EWM destination.
<DMC Plant A1>
<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 437
Related Information
Manage Business Settings
2.4 Troubleshooting Overview
If you run into problems during or after setting up a specic integration scenario, you can nd general
troubleshooting information in this guide. The information will be updated as applicable.
Troubleshooting for the Integration with SAP S/4HANA [page 439]
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
roles from dierent 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 oor stock integration in SAP Digital Manufacturing, and be able to transfer oor 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 conguration integration. In case of issues, please check that all necessary conguration settings are
done.
• If you use SAP ERP or SAP S/4HANA, see Updating Integration Conguration to Use Floor Stock Data
[page 230]
• If you use SAP S/4HANA Cloud, see Updating Integration Conguration to Use Floor Stock Data [page
366]
For more detailled troubleshooting information and guidance for a specic integration scenario, please refer to
the Implementation Starter Kit for your scenario: Implementation Starter Kits for Discrete Manufacturing for
SAP Digital Manufacturing.
438
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
Note
The content of Implementation Starter Kits is available only to registered or licensed customers and
partners.
Related Information
How to Contact Us
Integration Message Dashboard
2.4.1Troubleshooting 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 439]
Production Order Transfer to ERP Fails [page 440]
Production Order Status is not Updated in SAP S/4HANA or SAP ERP [page 440]
2.4.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
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 439
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 nd a detailed description of the necessay steps in IDoc Troubleshooting Steps [page 441].
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 441] 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.4.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 nd a detailed description of the necessay steps in IDoc Troubleshooting Steps [page 441].
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 441].
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.
Related Information
Integration Message Dashboard
2.4.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 oor. Status updates for goods issues, goods receipts, and
the order status aren't reaching SAP S/4HANA or SAP ERP.
440
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
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
441].
2.4.1.4 SAP Cloud Integration Troubleshooting Steps
Learn how to troubleshoot for specic IDoc-related issues.
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.4.1.5 IDoc Troubleshooting Steps
Learn how to troubleshoot for specic 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 nd errors in IDoc processing and check for IDocs with status Failed.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 441
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 nd 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 nd the production order details under Data records.
442
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
2. Check the status of the IDoc and the respective error code under Status Records.
Example
Error Code 02 – Error passing data to port.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 443
3. Click on the record for detailed information.
444
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
According to the diagnosis information, the IDoc has been sent to SAP Cloud Integration with the specied
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 441].
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
PUBLIC 445
2.5 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-
specic or customer-specic 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 oered by the Kyma environment for SAP Business Technology Platform, see Kyma
Environment.
SAP Samples
You can nd 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 nd the APIs that SAP Digital Manufacturing oers as well as the related documentation in the SAP
Business Accelerator Hub . For the procedure to create a service key that is needed to access SAP Digital
Manufacturing using an API, see Create a Service Instance and Service Key in SAP Digital Manufacturing
Subaccount [page 68].
For scenario-related API information, see APIs for SAP Digital Manufacturing.
Custom Integration Flows
You can add the custom integration workows that you've deployed in SAP Cloud Integration to the Manage
Integration Workows app. For more information, see User-Dened Customizing Options [page 314].
Related Information
Predened Customizing Options Using XSLT [page 313]
446
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for execution Integration
3 Shop Floor Integration
SAP Digital Manufacturing connects to the shop oor through the Production Connector to retrieve machine
data for analytics and run production processes.
Integration Overview
Note
You can use one Cloud Connector to connect multiple Production Connectors across tenants, such as
production and quality.
3.1 Integration Scenarios
Learn about the integration scenarios that are supported in the context of the Asset Model.
• Digital Twin Conguration
You use the Production Connectivity Model to congure and manage the assets and service providers to
establish connectivity to the shop oor. The model helps you congure the digital twins of the machines on
the shop oor. For more information, see Digital Twin Conguration [page 448].
• Machine Data Integration
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 447
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 448].
• Production Process Conguration
You can use the Production Process Designer to model production processes and translate the production
process designs into congurations by deploying them to the Production Connector. For more information,
see Production Process Conguration [page 450].
• Production Process Execution
The Production Connector executes the production processes as congured and transmits data between
the machines and SAP Digital Manufacturing. For more information, see Production Process Execution
[page 450].
Related Information
Asset Model
3.1.1Digital Twin Conguration
Using the Production Connectivity Model, you can congure and manage an asset and service providers to
establish connectivity to the shop oor. The model helps you congure the digital twins of your asset on the
shop oor.
You can congure an asset and its constant properties such as dimensions or other manufacturer
specications, as well as the sensor data points.
To create a digital twin of your asset, see Managing Assets.
To onboard an asset to the Production Connectivity Model, see Manage Asset Connectivity.
3.1.2Machine Data Integration
A machine can contain one or more shop oor systems. A shop oor 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 oor 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 oor
systems, you can model objects, services, and tag information in the Production Connectivity Model. When
you congure a shop oor system, you dene the shop oor system type (internal or external) and the usage
of the shop oor system in Production Connector, for example, usage as a data source. The corresponding
elements are then deployed to Production Connector using the activation ow provided by the Deploy Shop
Floor Elements app.
The following table shows which objects congured in the Production Connectivity Model, correspond to which
conguration elements in Production Connector.
448
PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
Mapping of Entities
Object in Production Con-
nectivity Model Shop Floor System Type Usage Type
Production Connector Con-
guration 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,
you select methods and not
tags)
OPC UA source system
(without agent instance)
Shop Floor System Internal OPC UA server OPC UA server created
and running in Production
Connector and correspond-
ing agent instance
Tag
Internal - Tag
Service External - Service, only metadata
Service Internal Direct destination call Service, method denition,
method notication 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
Managing Shop Floor System
You can use shop oor system to model the following:
• Data sources
You can connect an external data source, such as an OPC UA server, and dene 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 dene an OPC UA server that is created automatically in Production Connector. You can dene the
methods in the conguration of the shop oor system.
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 449
• Internal servers (type: Web server)
You can dene a Production Connector web server that is created automatically in Production Connector.
You can dene the Web services in the conguration 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.3Production Process Conguration
Using the Production Process Designer, you can model production processes (automation sequences) that
automate the production on the shop oor using services provided by service providers connected to the
Production Connector systems. After a design is completed, you deploy and activate the production process
design to transfer the congurations to the runtime environment, including these Production Connector
systems.
3.1.4Production Process Execution
As a manufacturing automation software, the Production Connector enables machine-to-machine
communication and connects equipment with SAP Digital Manufacturing
After a shop oor design is deployed to the Production Connector, it is responsible to do the following:
• Execute automation that's congured by shop oor 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 the Production Connector for SAP
Digital Manufacturing
The Production Connector for SAP Digital Manufacturing is the connectivity layer between SAP Digital
Manufacturing and the shop oor.
The supported versions of the Production Connector for SAP Digital Manufacturing are available in
3253702
.
450
PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
Note
To connect the Production Connector for SAP Digital Manufacturing to SAP Digital Manufacturing via the
Cloud Connector, refer to the procedure described here: Cloud Integration Guide.
Note
It's strongly recommended that you use the Production Connector for SAP Digital Manufacturing instead
of SAP Plant Connectivity as your connectivity layer. SAP has already ended the support for SAP Plant
Connectivity in the integration with SAP Digital Manufacturing. For more information, see 3255564 .
To know more about your migration options, see 3223128 and Preparing the Migration from SAP Plant
Connectivity.
If you've already created a connection from SAP Plant Connectivity to the cloud using SAML, have a look at
the bottom of this page.
The table below shows you how you can assign the Production Connector roles based on the SAP Digital
Manufacturing roles of each user. Note, however, that this mapping is not mandatory.
SAP
Digital
Manufact
uring Role
\
Productio
n
Connecto
r Role
Administrator This procedure
is about enabling
communication from the
Production Connector to the
CertificateAdministrator
PCoConfigurator
ServiceExecutor
DataReader
DataStorer
FileProcessor
Operator
BackupCreator
Producti
on_Engin
eer
Yes Yes Yes Yes
Automati
on_Engin
eer
Yes Yes Yes Yes Yes Yes
Producti
on_Super
visor
Yes Yes Yes
Producti
on_Opera
tor
Yes Yes Yes
Manufact
uring_Ad
min
Yes
Global_R
egional_
Manager
Yes
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 451
SAP
Digital
Manufact
uring Role
\
Productio
n
Connecto
r Role
Administrator This procedure
is about enabling
communication from the
Production Connector to the
CertificateAdministrator
PCoConfigurator
ServiceExecutor
DataReader
DataStorer
FileProcessor
Operator
BackupCreator
Plant_Ma
nager
Yes
Enable Communication from the Production Connector to the
Cloud
Context
This procedure is about enabling communication from the Production Connector 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 On-Premise.
SAP Digital Manufacturing supports two authentication methods for incoming Web service calls: SAML OAuth
certication and x.509 certicate authentication. The Production Connector uses x.509 authentication by
default; the SAML OAuth method is legacy and no longer recommended.
The following procedure is recommended: To use x.509 authentication for the Production Connector, 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
If you migrate from SAP Plant Connectivity (version 15.5.4) to the Production Connector with a destination
still using a valid SAML OAuth certicate, you can continue to use SAML authentication. However, once
your SAML certicate expires, you need to replace it manually. For more information, see Certicates.
If you want to migrate destination congurations that still use SAML OAuth to use x.509 authentication,
you need to redeploy the production process or subscription.
Older Windows operating systems may issue an error message if you generate or refresh the Production
Connector to Cloud Certicate (X.509 OAuth). Refer to the procedure described in SAP Note 3194709 in
this case.
452
PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
3.2.1Minimum Version Requirements and Supported
Scenarios
Here are the minimum release requirements, supported scenarios, and limitations for integrating machinery
and equipment on the shop oor using the Production Connector.
Minimum Release Requirements
Information on the Production Connector 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
Production Connector release.
3.2.2Assignment of Production Connector Role to IAS User
Groups
Production Connector roles can be manually assigned to users in the Production Connector or assigned to user
groups in SAP Digital Manufacturing. Assigning the Production Connector roles to user groups helps minimize
the downtime in the Production Connector as the assignment is managed from the cloud.
Access to Production Connector functions for SAP Digital Manufacturing users is managed by assigning the
relevant Production Connector 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.
Note
This is setting is automatically made if you used the assisted conguration of the Cloud Connector
integration in the Production Connector.
For more information, see Manage Users and Authorization.
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 453
Production Connector 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 functions.
You assign the user rights to user groups in the Production Connector section of the Congure Production
Connectivity app. For information on how to assign user rights to user groups, see User Groups.
When a new Production Connector is congured 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 le transfer to network location managed in the
Production Connector, triggering of Production Connector processes congured through the cloud and so on
can be provided by editing the permissions of the technical group.
See the table below to know the user right that corresponds to a specic role in the Production Connector:
Authorization in SAP Digital
Manufacturing
Production Connector Role
Role Description in the Production
Connector
Manage Production Connectivity Model
conguration
PCoCongurator Conguration of Production Connector
Read access to indicator measure-
ments
DataReader Reading and Browsing of Data Tags
Operate shop oor systems (start/stop
agents)
Operator Starting and Stopping of Service Pro-
viders
Write access to set indicator value FileProcessor Reading and Writing of Files
Invoke production process or
Production Connector services
ServiceExecutor Execution of Services
Administration of certicates CerticateAdministrator Administration of Certicates
Printing/le 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.
454
PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
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 congured 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.
7. Select Use Internal Host for Host in Request Header.
8. Optionally, enter a description for this system.
4. Congure 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.
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 455
Create destination for MII system
1. Log on to your subaccount for SAP Digital Manufacturing.
2. Choose Connectivity Destinations .
3. Choose Create Destination.
4. Enter the following information:
Field
Description
Name Enter an identiable 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 conguration in
the cloud connector.
Proxy Type Select OnPremise.
Authentication Select BasicAuthentication.
456 PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
Field Description
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
specic 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 conguration.
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.
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 457
3.4 Troubleshooting - Congure Production Connectivity
App
This section provides description of typical problems that you may encounter while conguring the Cloud
Connector and the Production Connector, and establishing connectivity between SAP Digital Manufacturing
and the Production Connector.
3.4.1Connectivity Issues
You might face the following issues while establishing connectivity between SAP Digital Manufacturing and the
Production Connector through the Cloud Connector.
Connection cannot be established; please contact your system administrator
Follow these steps to verify the congurations on Cloud Connector and on the Production Connector to debug
the connectivity issue between SAP Digital Manufacturing and the Production Connector.
1. Go to Cloud Connector and open your subaccount. Verify if the status shows Connected and Location ID
value is the same as congured in the SAP Digital Manufacturing Cloud Connector object in the Congure
Production Connectivity app. (Note: .)
Note
If multiple Cloud Connectors are connected, you must congure dierent Location IDs.
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 congured in the SAP Digital Manufacturing Cloud
Connector object.
3. Go to Principal Propagation tab and check if the IDP congurations have been synchronized. In case
there is an update of the SAML IDP conguration for a subaccount on cloud side, then you must trigger
synchronize action again by refreshing the trust conguration (using the Refresh option).
4. In the Cloud Connector, choose Conguration and go to the On Premise tab. Verify that the System and CA
Certicates are added and are valid. Now go to the Production Connector server.
1. For a signed certicate, verify if the CA certicate chain (all certicates in the certicate path, including
the root certicate and, if any, all intermediate certicates) have been placed in the Issuer Store
location in the le system of the server, where the Production Connector is installed. Ensure that the
certicate is valid:
C:\ProgramData\SAP\ProdCon\CertificateStores\CloudServicesHost\Issuer\certs
2. For a self-signed certicate, verify if the public key of the certicate has been placed in the Trusted
Store location in the le system of the Production Connector:
C:\ProgramData\SAP\ProdCon\CertificateStores\CloudServicesHost\Trusted\certs
3. In the Cloud Connector, check if Principal Propagation is set to name (this is the default setting).
5. Restart the main service of the Production Connector to apply any conguration change.
458
PUBLIC
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
6. For the Production Connector, go to Control Center Cloud Integration Port Settings and verify that
the server status is Running.
7. In the Certicate eld of the Production Connector, check if the server certicate that you have created for
the cloud server is selected and is valid (has not expired):
To check this, go to the Control Center of the Production Connector Cloud Integration Server
Security Settings
.
3.4.2Internal Server Error
An internal server error occurred in the Production Connector. Please
contact the system administrator.
Please check the Production Connector MainService log. The log les
(ProdConMainServerLog_yyyy.MM.dd.csv) can be found under:
C:\Program Files(x86)\SAP\ProductionConnector\Logs
See the error logs for the time duration.
3.4.3User Authorization Issues
If you receive an error message about an authorization error when connecting to the Production Connector,
check the following settings:
• Make sure that the user is assigned to a user group and that this user group has the required authorization
roles for the pertaining Production Connector installation. You can check the role assignment in the
Congure Production Connectivity app in SAP Digital Manufacturing.
As an alternative to assigning users to groups, you can add all users who require access to the Production
Connector cloud services through SAP Digital Manufacturing. You can do this in the Control Center of the
Production Connector under
Cloud Integration User Conguration .
The user ID in the Production Connector must match the Subject Name Identier attribute selected in
the Identity Authentication Service of the user. For example, if the attribute value is E-Mail, you need to
provide the email ID of the SAP Digital Manufacturing user in the User ID eld of the Production Connector.
• Check whether the parameters for validation of JSON Web Tokens (JWT) are correctly congured. You
can nd the corresponding settings in the Control Center of the Production Connector under Cloud
Integration
JWT Validation .
SAP Digital Manufacturing Integration Guide
Shop Floor Integration
PUBLIC 459
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 oor. Integrating other systems and applications with SAP
Digital Manufacturing for resource orchestration can help manufacturers to:
• Streamline their production processes and improve overall eciency
• 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.
To nd the limitations or restrictions that apply to your scenario, see 3379404 .
Related Information
Overview Characteristics-Based Sequencing [page 460]
Integration with SAP Manufacturing Execution [page 464]
Integration with SAP SuccessFactors Employee Central [page 482]
Data Engineering Conguration [page 495]
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 eective 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 eort 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 ecient and eective way.
460
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
4.1.1Integration 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 benet 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 461]
2. Modify Data Values for Production Orders [page 462]
4.1.1.1 Maintain Custom Data
Use the Manage Custom Data app to dene 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 congurable material for a semi-nished or a nished 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_ prex 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 classication. Use the REO_ prex for its name.
• You've created a congurable material. Use the REO_ prex 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 classication to the material.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 461
• You've dened the conguration prole for the congurable material and linked it.
Context
Perform the steps to map and manage REO_ specic data in the shop order category. This allows you to sort
the materials associated with production orders (prexed 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 eld denition.
4. Choose Add to create a custom eld that represents a characteristic of a congurable material.
Example
Identify the characteristics of the congurable material and dene them as custom data:
• Data Field: Represents characteristics of the material.
Example
REO_COLOR
• Field Label: UI label displayed for the data eld
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 congurable material for a semi-nished or a nished 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_ prex for each characteristic's name.
462
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Example
REO_RED
• You've assigned class type 300 as the material class.
• You've assigned your characteristics to your classication. Use the REO_ prex for its name.
• You've created a congurable material. Use the REO_ prex 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 classication to the material.
• You've dened the conguration prole for the congurable material and linked it.
Context
Perform the steps to customize existing integration workows in the Manage Integration Workows app. To
enable this function, you need to modify the XSLT of the workow 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 Workows app, enter LOIPRO05 in the search eld.
2. In the workow Production Order Download (LOIPRO05 V2), go to the Standard XSLT eld and copy
the whole section into the Custom XSLT eld.
3. In the Custom XSLT eld, make the required modications:
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 463
<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 nd 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 congurable material. Check for data that
starts with REO_ and its attribute. This helps you validate if all characteristics specic to SAP Digital
Manufacturing for resource orchestration that were dened 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 specic
characteristics dened earlier, while creating the production order, are displayed.
For more information, see Maintain Custom Data [page 461].
5. Go to the Dispatching and Monitoring app to sort and schedule operations based on sequencing of
characteristics.
Use the multi-sorting and ltering 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
464
PUBLIC
SAP Digital Manufacturing Integration Guide
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 465]
4.2.1Minimum 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 465
• 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.
4.2.2Integrating 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 conrming that provisioning is complete, create a ticket to request data
needed for data replication. After receiving the data, dene plants in your system and install and congure
SDI (see Setting Up the Connection to SAP Digital Manufacturing [page 466]). After you have congured SDI,
create a second ticket with SAP to request data replication.
Note that steps for conguring 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
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 congure SDI (HANA DP Agent 2.0). For more information, see Install the Data Provisioning
Agent.
2. Depending on the source database, congure the appropriate adapter. Based on the adapter you choose,
provide permissions to data source tables.
466
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Note
One data provisioning agent can connect to multiple source systems that use dierent databases.
The agent oers 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 congured the data provisioning agent, Create a Customer Incident [page 467]. 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 dierent 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 workow are completed, the data tables are available in SAP Digital
Manufacturing and are continuously updated.
Related Information:
• Downloading and Conguring the HANA DP Agent 2.0
• Congure 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 congure 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.
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
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 467
• 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 conguration 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 xed 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 dierent mechanisms based on the source database. For example: HANA database uses
triggers. Microsoft SQL uses logs.
For DM 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.
Related Information
SAP ME Tables [page 469]
468
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
4.2.2.1.2.1SAP 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
ITEM
Item
INCIDENT_NUMBER
Incident number
ACTIVITY_LOG
Activity log
AR_ACTIVITY_LOG
Activity log archive
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 469
Table Name Short Description
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 denition
USER_SHIFT_DEFINITION_BREAKS
User shift denition breaks
USER_SHIFT_T
User shift text
DATA_FIELDS
Data eld
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
470 PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Table Name Short 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
RESOURCE_TYPE_RESOURCE
Resource type resource
BOM
B0M
INVENTORY_ASSY_DATA
Inventory assembly data
STATUS
Status
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 471
Table Name Short Description
NC_CODE_T
Nonconformance code text
WORK_CENTER_T
Work center text
4.2.3Integrating 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 congure Cloud Connector.
For information on installing and conguring the Cloud Connector, see Setting Up the Cloud Connector
[page 22].
2. Congure 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>.
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 iow package of SAP
Digital Manufacturing for execution).
6. Choose Copy to copy the Digital Manufacturing Execution Integration package to the customer
tenant.
472
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
7. To set the following parameters in Initial Parameters go to Design Digital Manufacturing
Execution Integration package Artifacts Initial Parameters Action Congure .
Parameter Name Description Value
PID DME_GENERIC_PROCESSING_00
TENANT_CREDENTIALS
The user credential created in SAP
Cloud Integration Security Material.
PD_DEPLOYER_USER
TENANT_URL
SAP Cloud Integration Tenant Man-
agement URL used for access from
the Eclipse plugin. Used during con-
tent deployment (iow).
Refer to the email the customer re-
ceived after conrming successful
SAP Cloud Integration tenant provi-
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
fetching.
Go to SAP BTP Cockpit (of SAP
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 473
Parameter Name Description Value
COMMON_DME_INT_URL
The application routers URL of back-
end integration -ms application.
It's recommended to leave this eld
empty and to use the INBOUND
PROCESSOR integration ow. For
more information, see Congure In-
bound Processor iFlow [page 71].
If you don't want to follow this
recommended approach, go to
SAP BTP Cockpit (of SAP
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 replace
<data center> of the following
URL:
• https://dme-integration-
ms.dm.<data center>-qual-
ity.prod.shoot.live.k8s-hana.on-
demand.com
• https://dme-integration-
ms.dm.<data cen-
ter>-prod.prod.shoot.live.k8s-
hana.ondemand.com
COMMON_DMC_REO_M_E_OP_SECUR
ITY_MATERIAL_LIST
The list to map the plant and
technical user credential for inte-
gration. Format: <plant1>=<user
credential1>;<plant2>=<user
credential2>
Example
SAP=ME_CREDENTIAL1;
1000=ME_CREDENTIAL2
474 PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Parameter Name Description Value
COMMON_DMC_REO_M_E_OP_URL_L
IST
The list to map the plant
and the URL of wsdl. For-
mat: <plant1>=<url1 of
wsdl with virtual host
and port>;<plant2>=<url2 of
wsdl with virtual host and
port>
Example
SAP=http://vhreo:50000/
manufacturing-papiservices/
ShopOrderServiceWSSer-
vice;1000=http://
vhreo2:51038/manufacturing-
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
Conguration 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 congured for the same SAP Cloud Integration tenant, then you
should congure 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 elds:
• Type
• ENDPOINT_ID
• LOCATION_ID
11. After you have entered the elds, 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. Congure SAP Business Technology Platform of SAP Digital Manufacturing for execution.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 475
1. To create destinations for integration, under the corresponding tenant go to SAP BTP Cockpit SAP
Digital Manufacturing for execution Connectivity Destinations .
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 nd the specic SAP Cloud
Integration for integration.
4. Congure 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
Manufacturing for execution.
Example
1000
Description The description of the plant of SAP
Digital Manufacturing for execution.
Example
1000 Plant
Time Zone The time zone of SAP Digital
Manufacturing for execution.
Example
Europe/Berlin
476 PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Properties Description Value
Local If set to Yes, this plant will be
used for integration between SAP
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.
Example
No
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
supported.
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.
Example
S/4HANA
Execution Time Zone The time zone in SAP Digital
Manufacturing for execution
Example
America/New York
ERP Time Zone The time zone of SAP S/4HANA Example
Europe/Berlin
Language The language used in SAP Digital
Manufacturing for execution
Example
English-E
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 477
Properties Description Value
ERP Destination If S/4HANA is set for Integration
Mode, this eld is visible.
Enter the destination name that is
congured in SAP Cloud Integration.
Connectivity Destination
Example
ECCCLNT500
4.2.4Conguring Master Data for Resource Orchestration in
SAP ME System
This section explains the steps to congure 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 dierent
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 Conguration .
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 Conguration .
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 .
478
PUBLIC
SAP Digital Manufacturing Integration Guide
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 Conguration .
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 Conguration .
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 elds that appear Custom Data tab (in Work Center Maintenance) to provide
additional information when dening master data.
1. Choose Custom Data Maintenance under Maintenance Product Conguration .
2. Choose the category as Work Center.
3. Choose Insert New to create a new record. This record displays the sequence, data eld and eld label.
The sequence displays the order of the custom data.
4. Enter REO_MATERIAL_GROUP for both Data Field and Field Labels elds.
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 specic resource can belong to only one work center.
1. Choose Work Center Maintenance under Maintenance Product Conguration .
2. Enter a name for the work center or choose a work center from list.
3. Enter or choose the Standard Value Key. This eld 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 eld.
7. Choose the resource created in step 5.
8. Go to the Custom Data tab.
9. In the REO_MATERIAL_GROUP data eld, 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. Dene operations
In this step, you dene operation and its attributes.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 479
1. Choose Operation Maintenance under Maintenance Product Conguration .
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 dierent resource types and work centers.
For more information on maintaining operations in SAP ME, see Operation Maintenance.
11. Maintaining Orders
In this step, you dene shop orders of dierent 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 eld, 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 eld, 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.5Maintain Custom Data
Use the Manage Custom Data app to dene 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 congurable material for a semi-nished or a nished 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_ prex for each characteristic's name.
Example
REO_RED
• You've assigned class type 300 as the material class.
480
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
• You've assigned your characteristics to your classication. Use the REO_ prex for its name.
• You've created a congurable material. Use the REO_ prex 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 classication to the material.
• You've dened the conguration prole for the congurable material and linked it.
Context
Perform the steps to map and manage REO_ specic data in the shop order category. This allows you to sort
the materials associated with production orders (prexed 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 eld denition.
4. Choose Add to create a custom eld that represents a characteristic of a congurable material.
Example
Identify the characteristics of the congurable material and dene them as custom data:
• Data Field: Represents characteristics of the material.
Example
REO_COLOR
• Field Label: UI label displayed for the data eld
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 481
4.3 Integration with SAP SuccessFactors Employee Central
Optimize workforce management and resource allocation by integrating SAP SuccessFactors Employee
Central with SAP Digital Manufacturing for resource orchestration.
Introduction
SAP SuccessFactors Employee Central and SAP Digital Manufacturing for resource orchestration can optimize
workforce management and resource allocation by providing users with information about employees, their
availability and cost center. You use this information to make better decisions about production scheduling,
resource allocation, and other aspects of manufacturing operations.
For example, users can use workforce availability data to ensure that they've the right number of employees
working on the right tasks at the right time. This information can be used to optimize resource utilization and
improve overall productivity.
Master data processed by SAP Digital Manufacturing for resource orchestration include:
• Workforce Person: This data comprises of information about individual employees, including their
personal details, employment details, and other relevant attributes.
• Workforce Availability: This data includes information about when employees are available to work, such
as their shift schedule and vacation days.
• Cost Center: This data links employees to their respective cost centers, enabling accurate cost allocation
and budgeting. The cost center data is fetched from the SAP S/4HANA Cloud.
Integration Overview
482
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
• Before You Start [page 483]
• Create a Master Data Integration Instance [page 484]
• Create Distribution Models for Cost Center and Workforce Person [page 486]
• Create a Destination for Cost Center and Workforce Person [page 488]
• Create a Destination for Availability (Basic Authentication) [page 492]
• Congure SAP Digital Manufacturing for resource orchestration to Retrieve Data [page 494]
• Congure SAP Digital Manufacturing for resource orchestration to Use Master Data [page 495]
• Create Distribution Models for Cost Center and Workforce Person [page 486]
The integration process involves connecting SAP S/4HANA Cloud and SAP SuccessFactors Employee Central
to SAP Master Data Integration, which acts as a hub for the replication of cost center and workforce person
master data. In SAP Master Data Integration, distribution models control the distribution of cost center and
workforce person master data, which can be consumed by SAP Digital Manufacturing through a service
instance and a destination. Availability master data is retrieved directly from SAP SuccessFactors Employee
Central through the Availability API.
In SAP Digital Manufacturing for resource orchestration, the Scheduler Conguration app connects to the
workforce person and cost center destination and to the availability destination to retrieve the master data.
This data is then used in the Manage Workforce and Schedule Labor apps to optimize processes on the shop
oor.
Related Information
Before You Start [page 483]
Create a Master Data Integration Instance [page 484]
Create Distribution Models for Cost Center and Workforce Person [page 486]
Create a Destination for Cost Center and Workforce Person [page 488]
Create a Destination for Availability (Basic Authentication) [page 492]
Congure SAP Digital Manufacturing for resource orchestration to Retrieve Data [page 494]
Congure SAP Digital Manufacturing for resource orchestration to Use Master Data [page 495]
4.3.1Before You Start
This page shows you the prerequisite steps that you must complete before implementing the integration of
SAP Digital Manufacturing for resource orchestration and SAP SuccessFactors Employee Central.
Before you start, you must have performed the following steps:
• You've connected SAP S/4HANA Cloud to SAP Master Data Integration and enabled the cost center
integration. For more information, see Cost Center Replication: Setup Instructions and Integrating SAP
S/4HANA Cloud with SAP Master Data Integration.
• You've connected SAP Master Data Integration to SAP SuccessFactors Employee Central and enabled
the cost center integration. For more information, see Integrating Cost Center from SAP Master Data
Integration to Employee Central.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 483
• You've connected SAP SuccessFactors Employee Central to SAP Master Data Integration and enabled
the integration of workforce person. For more information, see Integrating SAP SuccessFactors Employee
Central with SAP Master Data Integration.
• You've enabled the workforce availability solution in SAP SuccessFactors Employee Central and have got
access to the Workforce Availability API provided by SAP SuccessFactors Employee Central. For more
information, see Enabling Workforce Availability and Workforce Availability API.
Note
In this integration scenario, the Workforce Availability API is consumed directly. There's no integration
ow between SAP Digital Manufacturing for resource orchestration and SAP SuccessFactors Employee
Central.
4.3.2Create a Master Data Integration Instance
Create a SAP Master Data Integration service instance in your SAP Master Data Integration subaccount to
transfer cost center and workforce person master data to SAP Digital Manufacturing.
Prerequisites
You've got the Administrator role for your SAP Master Data Integration subaccount.
Context
Once you've integrated SAP SuccessFactors Employee Central and SAP S/4HANA Cloud with SAP Master Data
Integration, your cost center and workforce person master data is available in SAP Master Data Integration.
To transfer the master data from SAP Master Data Integration to SAP Digital Manufacturing, you need to
create an SAP Master Data Integration service instance and a service key in your SAP Master Data Integration
subaccount. Then you assign a business system ID to this service instance. The business system ID links the
service instance to the business objects that you create in a later step to control the distribution of workforce
person and cost center data.
Procedure
1. In the SAP BTP cockpit, go to your SAP Master Data Integration subaccount.
2. Under Service Marketplace, search for Master Data Integration.
3. Choose the Master Data Integration tile.
The Master Data Integration view opens.
484
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
4. Choose Create to create an instance of Master Data Integration.
5. Enter the following elds to create a service instance:
Field
Service Master Data Integration
Plan sap-integration
Runtime Environment Cloud Foundry
Space Name of your space
Instance Name Choose an instance name, for example DM-SF-
Integration.
6. Choose Next and add the following parameters:
JSON
Description
"businessSystemId": "", Choose a unique identier for your business system, for
example "businessSystemId": "DM".
Note
The business system ID is the link between the busi-
ness object you create later and this instance. The
business system ID ensures that cost center and
workforce person data are available through the serv-
ice instance.
"enableTenantDeletion": false,
"application": "sfsf" sfsf represents SAP SuccessFactors Employee Central
7. Choose Create.
8. Under Instances, choose the instance that you've created.
9. On the Service Key tab, choose Create.
The New Service Keys popup opens.
10. Enter the following elds to create a service key supporting client ID / client secret:
Field
Value
Service Key Name Service Key
Note
You can choose a random name.
11. Choose Create.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 485
Note
You can access the service key content by choosing and then View.
Results
You've created a service instance and a service key.
4.3.3Create Distribution Models for Cost Center and
Workforce Person
Create two business objects to integrate cost center and workforce person master data with SAP Digital
Manufacturing.
Prerequisites
• You've got the Administrator role for your SAP Master Data Integration subaccount.
• You've got the DLAB_MDO_Admin role collection for SAP Master Data Integration.
• You've created a service instance and a service key for the integration of master data in your SAP Master
Data Integration subaccount. For more information, see Create a Master Data Integration Instance [page
484].
Context
To make the cost center and workforce person master data stored in SAP Master Data Integration available for
SAP Digital Manufacturing, you need to create two business objects. The rst one controls the distribution of
cost center data, and the second one controls the distribution of workforce person data. The business system
name you dened during the instance creation is used in the business objects, ensuring that the cost center
and workforce person data is available through the service instance.
Procedure
1. In the SAP BTP cockpit, go to your SAP Master Data Integration subaccount.
2. Under Service Marketplace, search for Master Data Integration (Orchestration).
3. Choose the Master Data Integration tile.
The Master Data Integration (Orchestration) view opens.
486
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
4. Choose Go to Application.
The Fiori Launchpad of SAP Master Data Integration opens.
5. Choose the Manage Distribution Model tile.
The Manage Distribution Model app opens.
6. Choose Create.
7. Under Header, enter a name for your distribution model, for example SF-HR-CC for the cost center data, or
SF-HR-WP for the workforce person data.
8. Under Description, choose Create to create a description for the distribution object.
9. Under Provider, choose Create.
10. Make the following settings:
Parameter
Value
Business System The business system ID dened in the service instance.
For example, DM.
Destination MDI
Local Conguration Required No
11. Under Consumer, choose Create.
12. Make the following settings:
Parameter
Value
Business System Enter the business system ID dened in the instance, for
example DM. For more information, see Create a Master
Data Integration Instance [page 484].
Destination Leave empty.
Local Conguration Required Yes
Application Category SAP S/4HANA Cloud (S/4)
13. Under Parameters, choose Business Object Type.
14. Make the following settings:
Parameter
Value
Business Object Type sap.odm.finance.costobject.CostCenter OR
sap.odm.workforce.WorkforcePerson
Business Object Type Version 3.0.0
API MDI_LOG_COST_CENTER
Package Size 1
Mode Pull
Recurrence Pattern Continuous Distribution
15. Optional: Under Object Selection, lter for dierent attributes, such as your company code or your cost
center ID.
16. Choose Save.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 487
17. Choose Activate.
18. Create the second distribution model. All the parameters are the same except for the Business Object
Type.
Results
You've created and activated two business objects for the distribution of cost center and workforce person
master data.
4.3.4Create a Destination for Cost Center and Workforce
Person
To make the cost center and workforce person master data available in SAP Digital Manufacturing, you need to
create a destination for cost center and workforce person data in your SAP Digital Manufacturing subaccount.
Prerequisites
• You've got the Administrator role for your SAP Digital Manufacturing subaccount.
• You've got the client ID and client secret of your SAP Master Data Integration instance as well as the token
service URL. For more information, see Create a Master Data Integration Instance [page 484].
Context
To retrieve the cost center data and workforce person data available in SAP Master Data Integration, you need
to create a destination in your SAP Digital Manufacturing subaccount. This destination needs to point to your
SAP Master Data Integration instance through which cost center data and workforce person master data are
replicated. To set up this destination, use the credentials found in the service key of your SAP Master Data
Integration instance.
Procedure
1. In the SAP BTP cockpit, log on to your SAP Digital Manufacturing subaccount and choose Connectivity
Destinations in the side menu bar.
2. Choose Create Destination and enter the following elds to create a destination pointing to your SAP
Master Data Integration instance. You can choose a random name for the destination.
488
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Field Value
Name Destination name, for example
SF_MDI_COSTCENTER_WORKFORCE_DESTINATION
Type HTTP
URL Enter the URL to be found under the uaa tag in the service
key of the corresponding service instance.
For example: https://<Master Data
Tenant>.cfapps.sap.hana.ondemand.com
Proxy Type
Internet
Authentication OAuth2ClientCredentials
Client ID Enter the client ID to be found in the service key of the
corresponding service instance.
Client Secret Enter the client secret to be found in the service key of the
corresponding service instance.
Token Service URL Type Select Dedicated.
Token Service URL Enter the <URL of Service Key>/oauth/token.
For example: https://<Authentication Ten-
ant>.sap.hana.ondemand.com/oauth/token
3. Under Additional Properties, create the following properties:
Property
Value
MDOConsumer true
MDOONEmds true
Use default JDK truststore Checked
4. Choose Save.
5. Choose Check Connection.
You can ignore the error "404: Not Found" that might be displayed.
Results
You've created a destination for the replication of cost center and workforce person master data.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 489
4.3.5Create a Destination for Availability
To transfer availability master data from SAP SuccessFactors Employee Central to SAP Digital Manufacturing
for resource orchestration, you need to create a destination for availability master data in your SAP Digital
Manufacturing subaccount.
Prerequisites
• You've got the Administrator role for your SAP Digital Manufacturing subaccount.
• You've got acces to the Workforce Availability API provided by SAP SuccessFactors Employee Central
and have enabled the workforce availability solution in SAP SuccessFactors Employee Central. For more
information, see Before You Start [page 483].
• You've registered your client in SAP SuccessFactors Employee Central. For more information, see
Registering Your OAuth2 Client Application.
Context
To retrieve the SAP SuccessFactors Employee Central availability data, you need to create a destination in your
SAP Digital Manufacturing subaccount. You use this destination to call the Workforce Availability API provided
by SAP SuccessFactors Employee Central directly.
Procedure
1. In the SAP BTP cockpit, log on to your SAP Digital Manufacturing subaccount and choose Connectivity
Destinations in the side menu bar.
2. Choose Create Destination and enter the following elds to create a destination pointing to the Workforce
Availability API provided by SAP SuccessFactors Employee Central. You can choose a random name for the
destination.
Field
Value
Name Destination name, for example
SFSF_WORKFORCE_AVAILABILITY
Type HTTP
490 PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Field Value
URL Enter the host of your SAP SuccessFactors Employee
Central Workforce Availability API. The path is added au-
tomatically in the background.
For example: https://
<hostname>.ondemand.com
Proxy Type
Internet
Authentication OAuth2SAMLBearerAssertion
Note
You can use basic authentication, but this authentica-
tion mode doesn't support productive environments.
For more information, see Create a Destination for
Availability (Basic Authentication) [page 492] and
SAP SuccessFactors API Reference Guide (OData V2)
- Basic Authenication (Deprecated).
Key Store Location
Leave empty
Key Store Password Leave empty
Audience www.successfactors.com
AuthnContextClassRef urn:oasis:names:tc:SAML:2.0:ac:classes:PreviousSession
Use mTLS for token retrieval Keep unselected
Client Key Use the client key that is created when registering your
client in your SAP SuccessFactors Employee Central. For
more information, see Registering Your OAuth2 Client Ap-
plication.
Token Service URL Type
Dedicated
Token Service URL <BASEURL>/OAUTH/TOKEN
Token Service User Leave empty
Token Service Password Leave empty
3. Under Additional Properties, create the following properties:
Field
Value
apiKey Use the client key that is created when registering your
client in your SAP SuccessFactors Employee Central. For
more information, see Registering Your OAuth2 Client Ap-
plication.
companyId
Your company code
nameIdFormat urn:oasis:names:tc:SAML:1.1:nameid-format:unspecied
SystemUser Your technical user name
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 491
Field Value
Use default JDK truststore Selected
4. Choose Save.
5. Choose Check Connection.
Results
You've created a destination connected to the Workforce Availability API provided by SAP SuccessFactors
Employee Central.
4.3.5.1 Create a Destination for Availability (Basic
Authentication)
To transfer availability master data from SAP SuccessFactors Employee Central to SAP Digital Manufacturing
for resource orchestration, you need to create a destination for availability master data in your SAP Digital
Manufacturing subaccount.
Prerequisites
• You've got the Administrator role for your SAP Digital Manufacturing subaccount.
• You've got acces to the Workforce Availability API provided by SAP SuccessFactors Employee Central
and have enabled the workforce availability solution in SAP SuccessFactors Employee Central. For more
information, see Before You Start [page 483].
Context
To retrieve the SAP SuccessFactors Employee Central availability data, you need to create a destination in your
SAP Digital Manufacturing subaccount. You use this destination to call the Workforce Availability API provided
by SAP SuccessFactors Employee Central directly. This topic describes how to set up basic authentication,
which doesn't support productive environments. It's recommended to use OAuth authentication as described
here: Create a Destination for Availability [page 490].
Procedure
1. In the SAP BTP cockpit, log on to your SAP Digital Manufacturing subaccount and choose
Connectivity
Destinations in the side menu bar.
492
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
2. Choose Create Destination and enter the following elds to create a destination pointing to the Workforce
Availability API provided by SAP SuccessFactors Employee Central. You can choose a random name for the
destination.
Field Value
Name Destination name, for example
SFSF_WORKFORCE_AVAILABILITY
Type HTTP
URL Enter the host of your SAP SuccessFactors Employee
Central Workforce Availability API. The path is added au-
tomatically in the background.
For example: https://
<hostname>.ondemand.com
Proxy Type
Internet
Authentication Basic Authentication
Note
For more information, see SAP SuccessFactors API
Reference Guide (OData V2) - Basic Authenication
(Deprecated).
User
Enter the technical user name and the company code.
Example
The required format: superuser@COMPANYCODE
Password Enter your password.
3. Choose Save.
4. Choose Check Connection.
Results
You've created a destination connected to the Workforce Availability API provided by SAP SuccessFactors
Employee Central.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 493
4.3.6Congure SAP Digital Manufacturing for resource
orchestration to Retrieve Data
To replicate workforce person, cost center, and availability master data to SAP Digital Manufacturing for
resource orchestration, you need to congure the Scheduler Conguration app.
Prerequisites
You've created two destinations in your SAP Digital Manufacturing subaccount. One points to your SAP Master
Data Integration instance and retrieves workforce person and cost center master data. The other destination
points to the availability endpoint of the SAP SuccessFactors Employee Central API. For more information, see
Create a Destination for Cost Center and Workforce Person [page 488] and Create a Destination for Availability
(Basic Authentication) [page 492].
Context
To make workforce person, cost center, and availability master data available in SAP Digital Manufacturing
for resource orchestration, you need to make some congurations in the Scheduler Conguration app. First,
connect the app to the destination that points to the SAP Master Data Integration service instance to access
workforce person and cost center master data. Then, connect the app to the destination that points to the
Workforce Availability API of SAP SuccessFactors Employee Central. Lastly, dene the version of data you want
to use and how often you want the data to be retrieved.
Procedure
1. In the Scheduler Conguration app, choose Edit.
2. Make the following congurations:
Field
Description
Workforce Destination The name of the corresponding destination, for example
SF_MDI_COSTCENTER_WORKFORCE_DESTINATION
Workforce Availability Destination The name of the corresponding destination, for example
SFSF_WORKFORCE_AVAILABILITY
Run Every The frequency at which the data is pulled
Work Center Entity Version 3.0.0
Cost Center Entity Version 3.0.0
3. Choose Save.
494
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
Results
The workforce person, cost center, and availability master data is available in SAP Digital Manufacturing for
resource orchestration.
Related Information
Schedule Replication of Workforce Data
4.3.7Congure SAP Digital Manufacturing for resource
orchestration to Use Master Data
Involves onboarding employees to relevant cost centers, and using the workforce information for shop oor
operations.
Context
After establishing the connection between SAP SuccessFactors Employee Central, SAP S/4HANA Cloud,
and SAP Digital Manufacturing for resource orchestration, you must congure SAP Digital Manufacturing for
resource orchestration to utilize the imported master data.
You need to perform the following steps in SAP Digital Manufacturing for resource orchestration:
Procedure
1. Go to the Manage Workforce app, to onboard employees, assigning them to relevant cost centers, and
ensuring their availability for labor planning. See: Onboarding Workforce.
2. Go to the Schedule Labor app, to eectively plan and assign labor to work orders, ensuring that the right
resources are available on the shop oor. See: Optimize Workforce Availability Using the Schedule Labor
App.
4.4 Data Engineering Conguration
The concept of Data Engineering (DE) revolves around replicating data from on-premise systems to the cloud.
This data is then available in SAP Digital Manufacturing for resource orchestration.
Replication of on-premise data to the cloud is achieved using three apps:
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 495
• 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 app, you can
create new data agents and delete or check the status of existing data agents, download scripts, and
copy connection strings. For more information on downloading scripts and copying connection strings, see
Manage Data Agents in the Setup Guide for Data Engineering.
• 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 app helps you create a connection. Additionally,
you can delete and check the status of existing connections. Choose any connection to edit or change the
connection details, and save them as dierent 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 replicate the data to
a destination table. You can choose how to replica or replicate the source data in the destination table
using this 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. Choose the link to get a snapshot of the pipeline status. Choosing
Details provides information on the total and failed runs. Delta Load Triggered, Upload to Cloud, and Insert
to Database show the dierent 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 conrmation 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 lters or
accommodate any changes that you make.
For additional setup information, see Setup Information.
Related Information
Manage Data Agents [page 496]
Manage Connections [page 497]
Manage Data Replicas [page 498]
Setup Information
4.4.1Manage 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 rst 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.
496
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
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 dierent 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 conguring and managing data agents, see Setup Information under the Setup Guide
for Data Engineering.
4.4.2Manage 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 les 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.
Click any connection with any status (Connected or Disconnected) to edit elds 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
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 497
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 conguring and managing connections, see Setup Information under the Setup
Guide for Data Engineering.
4.4.3Manage 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 congure 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.
You can lter 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
reects 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 dierent
stages of the pipeline run.
In case of failed delta loads, an Error Log is generated. Click Error Log to view details.
498
PUBLIC
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
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 reects soon after, for example - after a minute).
For more information on conguring and managing data replicas, see Setup Information, under the Setup
Guide for Data Engineering.
SAP Digital Manufacturing Integration Guide
Resource Orchestration Integration
PUBLIC 499
5 SAP Digital Manufacturing for edge
computing Integration
This section provides you with detailed information on the steps to integrate the Production Connector with
SAP Digital Manufacturing for edge computing.
Additionally, the SAP MQTT Broker on edge is provided by SAP. The broker is located on a Kubernetes cluster
fully operated by an SAP customer, as a capability of the SAP Digital Manufacturing for edge computing
solution. (See: SAP MQTT Broker [page 501])
For other existing integration scenarios such as integrating your own APIs and apps with SAP Digital
Manufacturing for edge computing, see API Integration and UI Integration.
5.1 Enable Production Connector to Invoke Edge Services
This topic describes steps on enabling Production Connector (Windows) to invoke APIs of SAP Digital
Manufacturing for edge computing.
Prerequisites
• You have obtained a client certicate issued for a technical user "dm-edge-services".
• You have obtained the CA certicate signing the SAP Digital Manufacturing for edge computing server
certicate. The CA certicate le must include the entire CA chain, starting with the signing CA and ending
with the root CA.
Procedure
1. Concatenate the client certicate and key and export to client.pfx. Below command assumes that the
client certicate le is client.crt and its key le is client.key.
openssl pkcs12 -export -out client.pfx -inkey client.key -in client.crt
2. In the Manage Computer Certicates window of the Windows machine where the Production Connector is
installed:
a. Import the CA certicate to the Trusted Root Certication
b. Import the client pfx le to the Web Machine Default
3. Copy the CA certicate to the
C:\ProgramData\SAP\ProdCon\CertificateStores\TrustedCertificates\certs folder.
500
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for edge computing Integration
4. Connect the Production Connector web server to the SAP Digital Manufacturing for edge computing
services type web server and choose the client certicate you have imported in step 2.b. This also ensures
that these services are available for use in the left panel of the production process designer. For details, see
Setting up Connections Between Web Servers and Edge Web Server.
5. Add the service to the connected web server. For details, see Adding and Deploying Services from a
Connected Web Server.
Related Information
Available Services and Subprocesses
Manage Subscriptions
5.2 SAP MQTT Broker
The SAP MQTT Broker is the central component in the MQTT-based communication system of SAP.
The SAP MQTT Broker is the central component in the MQTT-based communication system of SAP. The SAP
MQTT Broker acts as a message broker or message server that enables communication between the MQTT
clients. The broker receives messages published by clients on a certain topic and sends these messages to the
clients subscribed to the same topic. At SAP, the Production Connector is the MQTT client that connects to the
SAP MQTT Broker.
Note
You can congure and use only one SAP MQTT Broker per edge Kubernetes cluster.
The MQTT messages exchanged via the broker usually represent tags, events, or time series data generated by
MQTT clients, for example, to report the status of a machine on the shop oor.
Possible MQTT clients are machines, shop oor systems, or servers that can run an MQTT library and can
connect to the SAP MQTT Broker over the network. The Production Connector (on Windows) can also run
an MQTT client to connect to the SAP MQTT Broker, and thus exchange messages with other MQTT clients
on the shop oor. An MQTT client can take the role of a publisher or a subscriber. When the Production
Connector runs as a publisher, it publishes messages on a target topic that other MQTT clients will receive if
subscribed to that topic. Messages from the Production Connector can originate from custom processes in
SAP Digital Manufacturing, or from tags or events that the Production Connector reads from other shop oor
devices. When the Production Connector runs as a subscriber, it receives messages published by other MQTT
clients on certain topics that the Production Connector must be subscribed to. Such messages may represent
measured values from sensors or events from the shop oor. After receiving them, the Production Connector
may forward them to a destination within SAP Digital Manufacturing, or to other shop oor devices that the
Production Connector is connected to.
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for edge computing Integration
PUBLIC 501
The Manage Message Brokers app is part of the Production Connectivity Model in the cloud. The congured
data, such as certicates that are required for secure communication or authorization data to control the
access to MQTT topics, are sent to the edge Kubernetes cluster via the Cloud Connector after you have
deployed the conguration.
The conguration that controls access to the SAP MQTT Broker is performed in the Manage Message Brokers
app, in the Clients and Production Connectors sections:
• The Clients section congures the authorization policies that regulate access to the SAP MQTT Broker via
third-party clients. This conguration results in data that’s deployed to the SAP MQTT Broker.
Note
Third-party clients must also be congured so that they can successfully connect to the broker, as they
need to be provided with a valid client certicate, the MQTT URL, and so on. SAP takes no responsibility
for the provisioning of this conguration to third-party clients. You must ensure that clients have the
appropriate conguration to successfully connect to the SAP MQTT Broker.
• The Production Connectors section controls the conguration that enables a Production Connector to
connect to an SAP MQTT Broker. SAP takes the responsibility of propagating the required conguration on
both the SAP MQTT Broker and the Production Connector.
Note
The Production Connector only supports the payload of type JSON. Payload is a data structure that
contains the contents of an MQTT message that is to be transferred. It is possible to send images, text in
any encoding, encrypted data, and virtually all data in binary form.
Related Information
SAP MQTT Broker Deployment: An Introduction
502
PUBLIC
SAP Digital Manufacturing Integration Guide
SAP Digital Manufacturing for edge computing Integration
Important Disclaimers and Legal Information
Hyperlinks
Some links are classied 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 ocially 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 suciently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to inuence 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
Important Disclaimers and Legal Information
PUBLIC 503
www.sap.com/contactsap
© 2024 SAP SE or an SAP aliate 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
aliate 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 specications may vary.
These materials are provided by SAP SE or an SAP aliate company for
informational purposes only, without representation or warranty of any
kind, and SAP or its aliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP aliate 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 aliate 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
