- SAP Managed Tags:
Hi All,
In the series of DQM blogs, we have seen how to configure basic validation and derivation rules for MDG central governance and Mass processing. We have also seen how to troubleshoot DQM rules.
If you have missed these blogs here are the links to those articles.
MDG DQM: Employing rules in central governance & mass processing in S/4 HANA
MDG DQM: Empowering Your Business with High-Quality Data in S/4HANA
MDG DQM: Enriching product master data with derivation rules in S/4 HANA
MDG DQM: Troubleshooting DQM validation rules for central governance - Product Master S/4 HANA
INTRODUCTION:
DQM rules in MDG are an option to replace the traditional BADI, BRF+ based validation and derivation rules that need to be built specifically for each MDG application context. Also these rules doesn't allow us to run the Data quality evaluations to identify potential issues in the master data.
Some challenges & complexities?
Parallel workflows
Currently DQM validation rules for central governance have only specific attributes in the context like change request type, status, priority etc. Change request step which is mostly commonly used to write validations is not available in the context at this juncture as a result when we are running a parallel workflow we need to identify the step for which the rule should be run, so that parallel approvers are not affected by unnecessary errors.
Using additional tables not available in context of DQM structures
We often need to use additional tables both standard & custom, in such scenarios we might need to use additional BRF+ options like database look up , procedure calls etc while modelling the rules.
MAIN CONTENT
In this blog post, we will see how we can model complex rules in MDG DQM using BRF+ procedure calls. The scenario i have taken is a parallel workflow and how to trigger step specific validations.
1. We need to create a rule using Validation rule app. You can follow the steps from my blog post
MDG DQM: Empowering Your Business with High-Quality Data in S/4HANA
2. In the condition expression in BRF+ we will have to model the rule differently for each rule stage like MDG central governance, Mass processing, consolidation, Since MDG central governance and mass processing have different underlying data models. We will create a case statement as below.
3. So for MDG central governance we create a boolean expression CHECK_MHDHB_MDF. Inside this boolean we will model the rule using a procedure call.
CHECK_CR_STEP_55 is the procedure call which will check if the CR step for the CR type is 55
4. In the procedure call, i am checking the CR step using the APP context class and set a flag as true when the step is 55 else it will be set as false.
CONCLUSION
With this blog post we saw how we can leverage additional BRF+ functions like procedure call to build complex rules. It also shows that DQM rules provides the flexibility to incorporate your own logic to build complex rules.The Data Quality Management (DQM) rule marks a significant evolution from BADI-based rules within Master Data Governance (MDG) systems. With DQM, the realm of rule creation transcends previous limitations, where MDG users are completely dependent on IT team to tell them what rules are built in the system, what are enabled/disabled. This provides transparency into the system and help in shaping future of data governance with unparalleled flexibility and precision.
Regards
Anirban
