SAP MDG BP (Master Data Governance for Business partner) helps to govern business partner master data on a central system and replicate the data in other client systems. We use the business partner master data to add and retrieve business partner’s information and to schedule their activities. A business partner can be a customer, vendor or even a lead. Business partner information includes details such as the company info, addresses, telephone numbers etc.
Why SAP MDG BP?
In a traditional ERP that has a customer and vendor master, redundant data is very common. Storing redundant data beats the very concept of effective master data management. Hence, the business partner came into being as a single point of entry to maintain master data for business partners, customers and vendors.
Now, this enabled effective master data management. Governance of this business partner master data on a hub facilitating consistency, high quality and centralized data to drive the entire organization’s business processes forms the crux of SAP MDG BP.
MDG BP Segments
BP or the business object is the basis for an MDG Customer or an MDG Supplier. Every customer or supplier is based on a business partner. We cannot create a customer or a supplier without a corresponding business partner.
The segments covered by SAP MDG BP are:
Extensions of BP that aid in Business Partner Master Data Governance
SAP MDG C
This is an extension of BP or the business partner object. SAP MDG C adds specific parts of customer master data of SAP ERP to business partner governance. It covers customer segments such as general data, company codes, sales areas and contact persons (which are managed as BP relationships).
SAP MDG S
This is also an extension of BP and adds specific parts of vendor master data of SAP ERP to business partner governance. SAP MDG S covers vendor segments such as general data, company codes, purchasing organizations, sub-ranges and contact persons (which are maintained as BP relationships).
Integration of SAP MDG C and SAP MDG S
Both SAP MDG C and SAP MDG S are extensions of the business partner object. Hence, in MDG, the business partner is the leading object. A business partner is always the first one to be created using the MDG UI. Based on the CVI configuration and the entered data, either the customer or the vendor or both the objects are created in addition to the business partner object.
Data is maintained in the business partner for both customer governance and supplier governance. When a field is stored in a business partner table, an entry is made in the related customer master or vendor master. This aids in data replication. An external system such as SRM would use the business partner master data of SAP MDG BP and will not be aware of the customer or vendor ERP specific data. If an older ERP system is the target receiver, customer and vendor data can be replicated.
CVI synchronizes general data, address data, communication data, bank accounts, industry sectors and tax numbers. CVI synchronization in SAP MDG BP happens from the business partner to the customer or the vendor.
To enable synchronization direction from BP to either customer or vendor, one has to
- Define at least one business partner role that triggers the creation of a customer/vendor
- Define a mapping of the business partner group to its related customer/vendor group
- Check if further mapping on segment level is required.
We need to note that MDG processes do not necessarily require the synchronization direction to be set up. Direction needs to be set up only in the case of transferring existing customers or vendors to BPs.
Multiple assignment is a sub object used by SAP MDG C and SAP MDG S. It is only available on the MDG hub and not on the client systems. This object allows one to link more than one customer or vendor to a BP object.
Request a Callback
Would you like to reach to one of our
SAP & Salesforce Expert.
Just submit your contact details and we’ll be in touch shortly.
You can also email us if you would prefer