<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Exploring_Extensibility_in_SAP_Digital_Man_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-04-17T09:33:58.000Z

Exploring Interaction Between the POD and Production Processes

<div id="content"><p tabindex="0">This lesson shows how the POD and the Production Process Designer can be integrated. You have already learned about the possibilities to use POD Buttons to call production processes and learned that production processes can send POD messages. This is done in the two following demonstrations.</p><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_p5wjtcoa"></div></div><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_30pnteld"></div></div></div>

POD and the Production Process Designer Integration

Exploring Customization in SAP Digital Manufacturing

Integrating the POD and Production Process Designer

We will start by adding a pod message to the production process to assemble all components. Like in the last modifications we did, a new version of the production process will be created. First, we need to set up the production process as pod connection. This is done on the start element of the production process. At the moment, you can only select one pod type you want to send the messages to. If you want to send pod messages to multiple pod types, you will need to create different production processes for this. Then you need to select to which pod type. you want to send the messages. If you only specify the plant it will be sent to all pods that are open at this plant. In our case, we will specify the resources we got this at the input and try to send the message as an answer to the caller of the production process. Please note that if multiple pods are open using the same resource all will get the notification. For example, Adam and Beth are both working on the inspection center, which has space for two operators and offers two touch monitors to use SAPDM. Adam is now selecting the assemble all button for his SFC and sees the message that there are no components to be assembled at the inspection operation. At the same time, Beth will also see the message even though she didn't select the button on her pod. This is because they are working on the same resource. To resolve this, you might consider modeling it as two resources instead, because as long as it is one resource, the pod message will go to all pods that have selected that resource. When both are selected, the connection can be created. created. Now we will add the pod message element and do the configuration. To keep it simple, we will just add a message. When you want to generate a dynamic message, you can use the insert value help and also use the content of variables from your production process. This would have already been enough from the production process point of view. However, we will also slightly adjust the logic flow. We will remove the error end as it is kind of foreseen that sometimes people select the button for operations that don't have components assigned. When you then later analyze the production process monitor logs, you might think that there are many processes which completed with errors. And you need to check what is going on there, but it would just be some wrong clicks of users, which then might distract you from the real errors. We also remove it because otherwise, we will see two messages, one from the error end and one from the pod message. Save and deploy. In our work on the production process, we will see two messages, we will see two messages, is complete. As a little challenge, you could also add a success message to the production process as well.

Integrating the POD and Production Process Designer (Part 2)

In this video, we will learn how to call the production process from the pod and let the pod listen to pod messages. Therefore, we will navigate into the pod designer and select the pod we want to add the button. In the pod, we will navigate to the page and place where we want to add the action button. Then we can drag and drop the action button and perform the basic configuration by selecting the gear symbol. Connect it to the production process, we will select the assign actions control. After selecting the type production process, we can search the list of the list of published production processes for the one we want to add to the button. As a last step to finish the button, we need to map the inputs of the production process like we did for the events. In the Pod framework, we have some context data available from the pod, but we can also hand over constant values. Depending on where you add the button, it could be the case that some of the context information is not set. E.G. in this configuration, I would expect the process lot value to be null or not set, as we do not work with process lots in this example. once more a reminder to think about the context and perform testing after your configuration to check if everything behaves as expected. Before we start our testing, we also need to check the configuration of the pod notifications to ensure the pod is also listening to the messages the production process sends. The configuration for this is on the top right of the pod designer. Upon opening the configuration, I see it was already done for this pod and we can continue the testing. We need to have the resource and production process notification. selected as the signal is coming from a production process and in the start element configuration, we selected that we send the notifications to the resource. To be able to provoke the message, we will select the inspection as there are no components assigned there. Now watch closely. The pod message will appear at the bottom of the pod. We see our configuration was successful. In addition to the proof from the user's point of view, we can also examine the logs in the monitor production processes as.