Overview of SAP Master Data Governance (MDG)

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 rules, monitor and control master data compliance, remediate errors directly
  • Master Data Consolidation
    Ensure that de-centrally managed master data is not redundant and of high quality

Central Data Governance


Data Quality Management


Master Data Consolidation


Pre-delivered Data Models




Deployment Options

There are two deployment options available for SAP MDG  
  1. Co-deployment
  2. Hub deployment

Co-deployment


  • In this, MDG functionality and other business processes like O2C, P2P, etc. are deployed in the same ERP system.
  • Can activate the MDG add-on to the same operational ERP system to run all MDG-related activities.
  • In this case, additional effort to migrate master data and related customization configurations isn’t required.

Hub Deployment


  • MDG is deployed in a separate dedicated system as a hub.
  • If there are multiple systems in the landscape, including SAP and non-SAP systems, then the ideal approach is to go with this option.
  • Additional effort required to customize configuration transports and master data migrations needs to be considered.

Comments

Post a Comment

Popular posts from this blog

Extend the MDG Business Partner – Node Extension (Reuse Option)

Image
So, here we are going to add a new entity to the company code data level, as shown in the above figure. Steps:- Extension of S4 API Structures To get the API structures, we need to go to the standard BP handler class. In Below structure, we need to add our own API structure. Class ‘ CL_MDG_BS_ECC_HANDLER ’. Table Type ‘ MDG_BS_BP_TT_ECC_EXTERN ’. Data Dictionary Object Creation Structures For Genil model extensions: Creation of Table to store this Secret number data in backend active table Extension of BP data model with new Entity Generate Data Model specific structures Create and Implement BP Handler Class Below methods we need to re-define GET_OBJECT_DATA_BY_ENTITY SORT_ENTITIES MAP_DATA_2API MAP_DATA_2STA PREPARE_EI_HEADER_MAP_2API READ_OBJECT_DATA SAVE_ADDITIONAL_OBJECT_DATA CONSTRUCTOR Below methods we have created newly READ_VENDOR_BY_LIFNR READ_VENDOR MAP_BP_ZSECRET_N_2API MAP_BP_ZSECRET_N_2STA CONSTRUCTOR METHOD  constructor .    ...
Read more

SAP MDG Data Modelling

Image
·        Data model is to define the structure of the data storage. ·        During Master data processing, a change request is used to store the data which is in process of changing in staging area. ·        The data model can define reuse area that is used for data storage after completion of change request. ·        In this case the system moves the data from staging area to a storage location using access class of the reuse area. This storage location is called active area. ·        In case no reuse area is defined, the same database table which is used for staging area, are also used to store active data. ·        Then no access class is involved, the system does not move the data to other system or any other table then MDG generated tables which is used as active area. In simple term, Data Mode...
Read more

SAP Customer/Vendor Integration (CVI)

Image
Customer Vendor Integration       CVI is separated into 2 part. 1. CVI Configuration in S4/HANA system 2.   CVI Synchronization CVI Configuration In S4/HANA, If we want to make it Business Partner as a Leading Object to maintain Customer or Vendor then we must do CVI Configuration. Limitation of Customer/Vendor objects without CVI -> Only single address we can maintain for each customer or vendor.        ->  No relation supports between customer and vendor       -> No  time dependency data we can have       -> In  S4/HANA we have single business objects as ‘BP’.       -> BP  is capable of centrally managing master data of BP, Customer, Vendor Customer ·         Customer is a BP to which we sell our Goods or Services. ·         Some customer information is specific to a company (Company code data) or ...
Read more