<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

Creating a Business Rule to Print a Label on Order Release

Create a Business Rule to Print a Label on Order Release

Exploring Customization in SAP Digital Manufacturing

Automating a Trigger

It is a common scenario that at the first operation you print a label and stick it to the product to track the SFC throughout production. Therefore, we will automate this in this demonstration, where a label is printed for each product at the beginning of the production. To achieve this, we will navigate to the Manage Automatic Triggers app and select the business rules tab. On the tab, you see that no business rule is created in the DM 2000 plant yet. To create a new one, we will select the create button. We will now work through the new rule form and fill out everything needed. Some of the options should already sound familiar from the explanation in the last lesson. In the described use case, we don't need to interact with the event itself. Therefore, we don't need to use the event-type business service. We take the simpler event. Now, there are two events which could be interesting. One, the order release as the SFC is created there and processing could start afterward. The disadvantage is that this could still be some time before the end. actual work starts. The second option is to use the start SFC event with a filter on the first operation. In this case, depending on the product, there could be different first operations, and you need to configure multiple events. Based on this simple example, you already notice, that you need to be very close to the business process and the requirements you want to implement at this point. For simplicity, we will just configure one event on the order release. The next section of the screen shows the conditions. It is mandatory to have a filter on the plant to prevent side effects between production sites. Additionally, you can define more filters based on the data provided by the event, for example. You could specify that you only want to perform the action for certain materials. The system offers different operators to help you to define the filter. For this demonstration, we don't want to limit the event further than the plant, so we can remove the material again. In the action section section, we will now select a production process that was prepared to trigger the printing. This course will not show you how to set up this production process for printing. With what you already learned on the process designer, you should be able to do it on your own with some additional research in the SAP Help Portal to set up the printing correctly. If you also want to configure an event in your system, you can just let the event call one of the previous processes. We just didn't do so in the demonstration as the printing use case makes more sense here. When the action is selected, you need to configure the input parameter of the process you selected. The event will offer its context so you can just map most of the data. In this case, it is the plant and SFC, but the event does not provide information on the printer or the document template you want to use. These values can be specified here in double quotations. In the future, when you are developing a production process that needs to respond to an event, you may wonder what data is available from the event context. To find the answer, you can refer to the event documentation linked in the last lesson, or you can look it up in the system. When saving the business rule, it is not active yet. You need to deploy it like you do for production processes. After being deployed, it is active and will trigger the production process on order release. If needed, you can pause or delete it later. We will now test if it is working. In this case, we only test it from the UI, but I recommend testing it for all use cases you need it for. For example, if you also release some orders via API, you should also check if the event reacts to that is expected as well. To check if the production process is correctly triggered, we will search for a releaseable order and release it. Afterwards, we can check the logs in the Production Process Monitor Act. In the production process monitor, you see five print label processes. The four others were created when the content for this demonstration was developed and the event was tested. When we navigate to the first one, we can see that the process successfully called the print service.