Digital Manufacturing Cloud Integration

Dear SAP Friends,

In this Blog will try to Understand Some of the important integration enhancements and new features with S/4HANA added to SAP Digital Manufacturing Cloud (DMC) – Manufacturing Execution.

Before we go in Detail about DMC hear is an overview

DMC has been Integrated with below each functionality, Will see each integration Steps From ECC / S/4 HANA —> DMC

DMC Integration with Multiple ERP systems by single CPI

DMC Master BOM Integration

DMC Master Routing Integration

DMC Goods Issue / Goods Receipt Integration w/o yield confirmation

DMC Message Monitoring Enhancement

DMC Integration with Multiple ERP systems by single CPI

First CPI – Cloud Platform Integration.

• There is no need for a customer to subscribe to multiple CPIs for each ERP system to integrate with DMC for Execution since 1905.
• In ‘Manage Supported Plants’, set ‘Integration Mode’ to ‘S/4HANA’ for the integration with S/4HANA system.
• In ‘ERP Destination’, fill the ‘Destination Name’ which is configured in CPI SAP Cloud Platform -> Connectivity -> Destination.

The plants must be unique across multiple ERP systems at Client level.

DMC Master BOM Integration

• In ERP, the customer creates BOM by transaction CS01.
• By using transaction BD30, the material BOM can be transferred to DMC as Master BOM.
• BOM name has the following structure: Material Number (MATNR) + “-“ + BOM Usage (STLAN) + “-“ + Alternative BOM (STLAL) (for example, DME_BOM_TEST2-1-1).
• Once the Master BOM is transferred to DMC, the customer can set the component allocation manually.

DMC Production Routing Integration

• In ERP, the customer creates Routing by transaction CA01.
• By using transaction POIM or DRF, the material Routing can be transferred to DMC as Production Routing.
• Routing name has the following structure: Key for Task List Group (PLNNR) + “-” + Group Counter (PLNAL) (for example, 50001829-1).
• The Operations in the Routing will be created automatically with the following name convention:
• The MES Operation name (ME_OPERATION_ID) and MES Revision (ME_REVISION), if they are maintained in ERP Operation master data. If ME_REVISION is empty, use “ERP001” as the default version.
• Otherwise, Key for Task List Group (PLNNR) + “-” + Group Counter (PLNAL) + “-” + Sequence (PLNFL) + “-” + Operation (VORNR) (for example, 50001829-1-0-0010).

DMC Goods Issue / Goods Receipt Integration w/o yield confirmation

Pre-Requisition

• The Plant for integration is setup in DMC.
• The goods movement integration is setup in ERP. (Note 1555198)
• The material for consumption is transferred to DMC, and Data to Collect on Assembly is configured in DMC:
• INV_SFC (Contains: INVENTORY_ID_SFC and BATCH_NUMBER and ERP_SERIAL_NUMBER)
• INV (Contains: INVENTORY_ID and BATCH_NUMBER and ERP_SERIAL_NUMBER) for floor stock Inventory/Batch consumption.
• The production order is transferred from ERP to DMC.
• Collaboration COLLABORATION_SFC_COMPONENT_ADD is setup with collaboration directive ERP_COMPONENT_ADD.
• Collaboration COLLABORATION_ERP_YIELD_CONFIRMATION is setup with collaboration directive ERP_YIELD_CONFIRMATION.

once Prerequesit is completed We can Transferring a Goods Movement Independent of Yield Confirmation

• Release and Start Shop Floor Control.
• Assemble component to Shop Floor Control.
• The goods issue request will be sent to ERP.
• The component is consumed in ERP with goods movement 261.

Transferring a Goods Movement within Yield/Scrap Confirmation

• Release and Start Shop Floor Control.
• Assemble component to Shop Floor Control.
• Complete SFC at last operation.
• The goods receipt request will be sent to ERP
• The finish goods are received in ERP with goods movement 101.

In this way, we can Integrate Manufacturing Execution to Digital Manufacturing Cloud, That’s all for Part 1

In Part 2 will see more about POD & POD Designer.

Please share, Like and Comment anything else if you want to share or add points.

Thanks & Regards

Ruthvik Chowdary

SME – S/4 HANA Manufacturing & Procurement

SAP Ariba P2P