Syniti RDG encourages an updated design to allow multi-level Parallel Workflow Maintenance

[pritikar]

Syniti Rapid Data Governance (RDG)  is an SAP-endorsed Cloud-Based UI5 application built on the SAP Business Technology Platform (BTP). SAP Master Data Governance is a powerful solution to improve the quality and consistency of information across organisations by consolidating and centrally governing master data. Syniti RDG automates the processes of MDG Data Model Maintenance, Workflow Configuration, and Business Rules with an intuitive, user-friendly, and elegant graphical interface.  

This blog is part of a series covering various key capabilities of Syniti RDG. 

Traditionally a user had to follow the standard guide to implement parallel workflow, which includes the following steps: 

• Creating a new change request type. 
• Defining service names. 
• Populating BRF+ Single, User, and Non-User Agent tables. 
• Create Enhancement implementation for BAdIs to customize Parallel and Dynamic tasks. 

• USMD_SSW_SERVICE_PROCESSOR 
• USMD_SSW_SYSTEM_METHOD_CALLER 
• USMD_SSW_DYNAMIC_AGENT_SELECT 

• Create filter and set service names for BADIs as a condition.

 Set up Parallel Workflow Tasks with BRF+ (BADI USMD_SSW_PARA_RESULT_HANDLER) 

 This blog describes the updated feature of RDG, allowing multi-level Parallel Workflow Maintenance by automating the BADI implementation and BRF+ steps in a user-friendly UI screen. 

Below are the steps to configure the multi-level Parallel Workflow: 

1. Open the UI of RDG and click on 'Manage MDG Workflow' from the home screen.   
2. Click the  ➕ icon to create a new change request or can copy from the existing stand change request.   
3.  Enter the required details and Save: 
   • CR Type 
   • Description 
   • Data Model 
   • Main Entity 
   • Business Activity                                                                                                                                 Leading Entities will default from Main Entity   
4. Select transport request.      
5. A successful message should appear. Select 🆗 and a standard workflow will be populated as shown.   
6. Click the ➕ icon of the Requestor, select the workflow position and Parallel Flow  .
7. Select transport request.
8. Add Attribute to be used as the condition for the Parallel workflow.                
9. Select Add Rule highlight and enter details for the rule: 
   • Attribute Value 
   • Approver Type 
   • Approver 
   • Step Type
   • In the above example for the same Company Code, the workflow will parallelly move to three users for approval.
10. Save the configuration by selecting the transport request.    
11. Select a package to save the configuration.  
12. After saving the conditions, both the opening and closing nodes of the parallel workflow can be seen (here shown as A1 and A2). If required, additional approvers can be added from A1. The workflow will come back together at A2.      
13. Add connections to the opening parallel node. In this case, the connection is made from the Requestor to the opening parallel node (A1). The connection for the Requestor node is as follows.   
14. Add connections from the opening parallel node (A1) to any additional approvers between A1 and A2, or directly to A2 if there are no other approvers between them.  
    In the above case, there are no additional approvers, so connections are made directly from A1 to A2.     
15. In this case, create connections between the closing parallel node (A2) and an additional approver, A3.   
16. Create a connection between the Approver node A3 to the Activation node.   
17. The last Activation node connection is as follows.  
18. The complete workflows look like the below picture in this example.    
19. Once all connections have been completed, select to validate the workflow. A validation message should appear.    
20. Save to complete the workflow.  
21. BRF decision tables are created and populated automatically when the workflow is saved. 
22. Use the tcode USMD_SSW_RULE and give the CR type created to view the decision tables created.       
23. The Non-User Agent Decision Table is as follows. 
24. The User-Agent Decision Table is as follows.
25. The Single Value Decision Table is as follows.  
26. BADI is getting implemented automatically.

• Check the Badi implementation and the auto-generated code. 
• Go to the transaction se18 and give Enhancement Spot as USMD_SSW_SERVICE_PROCESSOR 
• Select the Badi definition as USMD_SSW_PARA_RESULT_HANDLER and click on the implementation.  
• Click on the active enhancement implementation and check the filter service for the combination and the service name.                                              Click on the implementing class for the autogenerated code. 

Thus, a multi-level Parallel Workflow can be maintained even for complex scenarios in RDG with no prior knowledge of ABAP, BRF+ configuration, and Badi implementations. 

Syniti RDG is a certified SAP BTP solution and is available on SAP App Store. 

 To know more details about the product, check the blog Partner Add-on Solutions. 

Your opinions and feedback are highly appreciated and feel free to post them in comment section. 

Please follow and read more interesting blogs on SAP Master Data Governance | SAP | SAP Blogs 

You can also find and post questions about the product here: SAP Master Data Governance Community