Welcome to SAP World!

Overview In SAP MDG, every change to master data is initiated using a change request. After a change request is initiated, it needs to be processed before activation or rollback by applying governance rules and collaborations. The process model provides the required input (metadata) for change request creation and processing, e.g., workflow, CR steps, and objects that can be processes. Submit and activate/rollback are mandatory steps in a change request. MDG reuses the SAP Business Workflow component of an underlying SAP business suite. SAP MDG workflow is an instance of SAP Business Object BUS2250. If the request has parallel processing, then each parallel step of the change request will have one BUS2250 instance. Define Governance Scope: Here we can define governance scope on the entity as well as the attribute level. For example, we have kept ‘NO’ to the below custom entity. As a result of MDG UI, the UIBB for this entity will only be in read-only mode. Business Object An ...

Overview SAP Master Data Governance is a state-of-the-art master data management application, providing preconfigured, domain-specific master data governance to monitor and remediate eventual data quality issues, to centrally create, change, and distribute master data, or to consolidate master data across your complete enterprise system landscape. The application helps you consolidate and govern your master data centrally and improve the quality of your business-critical information. It provides a central hub for master data management and governance, which can help you improve process efficiency and decision-making with a unified, trusted version of the truth and help drive your digital transformation. Architechture Key Features Central Data Governance Ensure that master data complies with company standards from the beginning, before it gets activated Data Quality Management Ensure and control master data quality. Define business rule...

In this blog, we will see how to derive MDG attributes using BADI. Derivations can be divided into two types.  Single-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from same entity. For this, we use 'USMD_RULE_SERVICE' BADI definition. Cross-entity derivation:  Automatically populating some attribute value in one entity based on an attribute value from another entity. For this, we use 'USMD_RULE_SERVICE_CROSS_ET' BADI definition. First, we will see a single entity derivation. Scenario:  We are going to make language English as the default if the user gives the country as India. Steps: 1. Go to SE18. 2. In 'USMD_RULE_SERVICE' BADI defination, create BADI Implementation.  3. For creating BADI Implementation, first we need to create Enhancement Implementation.  4. Give the properties as below. 5. Now, create BADI Implmentation and give following properties. 6. Maintain the filter values. H...

 We have some standard data quality solutions provided by SAP MDG framework as follows.  1. Search applications 2. Duplicate check configuration 3. Validation and Derivation (BRF+ , BADI) 4. Data Quality Management rules Search Applications: ·        For all the Out of the Box Standard Master Data Application, SAP provided Standard Search Application. ·        For MM, BP, AR, EAM, FI all having standard Search application. ·        For MM before S4/HANA use Enterprise search. After Introducing S4/HANA it uses HANA Search. ·        For Adding our Custom Attribute into the search criteria in Enterprise search it is complex, but in HANA search its very easy to bring. ·        In Fresh system, it’s not recommended to activate the standard search view provided by SAP. ·        It’s recommended t...