<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

Applying Error Handling in Production Processes

<div id="content"><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_2diibleo"></div></div><div class="note"><div class="noteTitle"><span class="noteIcon"><img title="Note" src="/icons/note.svg"></span><span class="noteTitleText">Note</span></div><div class="noteBody">Please check out this <a target="_blank" href="https://me.sap.com/notes/3375209">SAP Note</a> to find out which SAP DM APIs support idempotency.</div></div></div>

Apply Error Handling

Exploring Customization in SAP Digital Manufacturing

Adding the Error Handling to the Production Process 

In this video, we will add the error handling to the production process for assembling all components. In the last videos we learned that it is running into some error as soon as a component requires an assembly data field. The error handling to prevent the process from failing will be explained in this video. Like always, when changing an existing production process, we will navigate into the design and create a new version. production process. We can now add an error catch to the assemble component service. The error catch is placed on the existing element. Afterward, it will offer an additional outgoing logic flow. This outgoing logic flow can then be used to handle the error. In the error catch itself, you can configure the error codes which should be caught. The error codes offered are the HTTP error codes returned by the service. If you apply the error catch to a sub-process, you will also find a custom error codes thrown by the called process in the list. If you want to handle multiple errors at once, you can use the variable error code in a subsequent condition to handle the different codes separately. In our case, we will just catch error code 400 bad request and route it to the next action. Next to handling specific errors returned by the API, we can also leverage autoretries to improve the robustness of the production processes. The auto retries can help to make production processes robust to micro-downtimes of single-serving of SAPDM. On the other hand, please be aware that auto retries can also in rare constellations lead to double bookings. There are some APIs and DM that support idimpotency, so prevent these double bookings. Please refer to the SAP note provided in the info box below the video. The auto retry is always executed before the error catch. So in case you configure overlapping codes, the auto retry is executed first followed by the error catch. For our process, we will just take over the standard configuration and adjust the retry limit with this we have already addressed the errors found in the previous analysis however we should add some more logic what happens in our process if there is not a single component assigned to the operation nothing we would retrieve the planned components the condition would directly go to the else flow and the process would terminate sometimes it can be desired to give the information that nothing was done to the caller we will also do that in our production process. First step is to introduce another condition and an error end. The condition can leverage the V-Assembly counter process variable as well. If the variable is still null behind the loop, that shows that the counter-increased script task was never reached, therefore indicating that there was not a single component in the plan component list. You may also try out different conditions directly by checking the component list size. In the screen recording, you see me struggling a bit. The reason was that at first, the newly added condition didn't number the outgoing flows correctly. In the second attempt, it then worked, so save your progress regularly, so you can reload the screen if needed. For the error end, we will first need to create an error code on the header of the design, which we can then map into the error end. Each error code has a key and a message. After we create the error code, we can add to the error end and deploy the new version of the design.