<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

Testing and Analyzing Errors in Production Processes

Testing a Production Process

Exploring Customization in SAP Digital Manufacturing

Testing the Production Process Build 

In this video, we will test the production process built in a previous lesson. Just as a reminder, the purpose of the production process was to assemble all components assigned to a given operation. Let's start with having a look at the data in a pod. So we have proper input data with some components assigned so that it makes sense to test with it. The SFCs, we are looking for a located at the assembly work center with an assigned resource selected. When navigating into the operation, we find five components assigned which are all not assembled yet. So we have some nice testing data we can leverage. In your own system, you would need to build up some own testing data. Before we run the process, we will set the log level for the process so that we have all logs available for analysis later. In the next unit, we will also discuss the possibilities of the production process administration app in some more detail. For now, we will just see. set the log level of our process to debug. That way, we get the highest information level possible. Like for the previous testing, we will navigate into the process and execute a test run. For this, the pod is open in another window so you know the data you need to hand over. Apparently, we made a mistake. Let's investigate what is going on here. The error tells us that we missed filling out a mandatory assembly data field called manufacturer. In the mandatory parameters of the API, we didn't see the field when we implemented the process. We will check out the logs to possibly get some more insights. In the entry screen of the Monitor Production Processes app, we have some luck that no other processes have been executed in the last hour. Usually, when you enter the app, you will see a couple of hundred processes and need to filter first to find the correct logs. On the detail screen, you see some general information on the execution on top. On the left, you will find all executed steps and on the right side. You will find the process visualization. Later on, we will switch the view on the right side to retrieve some more details. First, we check which steps have been executed on the left side of the screen. In the list, you can see that the Assemble component service was successfully executed three times and failed for the fourth component. It seems that it is not a general issue with the service, but some special. case we did not consider. When selecting an element in the process instant step list and then navigating to the detailed information tab, you will see all inputs and outputs related to the steps selected. The component wheel, chain and saddle all went well, and no assembly data fields were required. However, for the shift, the data is required and we don't hand it over as an input. Just because we don't have the data. Next, we will add some error handling for this case, and so that possible following components without this requirement can be reached. The worker would only need to manually assemble the components where additional information is needed. Lastly, let's have a short look at the log view. In the log, you can even find some more details like the results of condition evaluations. In our case, we already found the error, so no need for further look into details. In the pod, we can have one more look at the business data. In the component list, we can observe that there is even one more component to be assembled which our process didn't T reach. As we cannot determine the content of the assembly data fields in the production process, the idea to improve the process is to catch that error and go to the next assembly. That way all components without manufacturing data fields could be assembled with the automation and the open ones could be added manually in the UI. In the next video, we will add this error handling.