SAP MDG – Federated Deployment Option and its importance
In the process of Digital Transformations, Large Enterprises are opting Private, Public, Hybrid cloud-based applications. This gives the business processes are spread across various application systems that runs on wider application systems.
Data flows across different systems that gyrates around Master data. Some of the master data is Transaction dependent. Managing Golden set also a key to support Boardroom Analytics. Hence managing master data is a great challenge.
Enterprise Resource Planning(ERP) Business Process are running on on-premises/cloud-based ERPs by various industries. Some scenarios may need Master Data Management at ERP Application system level with no or very minimal governance.
Now the question comes How, Where, at What level, By Whom master data will be managed. In normal world, Head Quarter(HQ) Driven policies, process will be in place, while Business Units(BU) follows it. Sometimes Complete BU’s Driven Roles. Also need has come to diversify the role in cloud-based Applications. This leads to take a decision on the approach for MDM Deployment. Below are the variables that drives the decision.
- Corporate Strategy on Master Data and Analytics & Insights (MDAI)
- Business Strategy (Industry type like Manufacture, Life science, Retail, Pharma )
- Type Cloud ( Private, Public, Hybrid)
- Application Systems (like SAP S/4HANA ,SAP Ariba, SAP Concur, Sales Force, CRM, PLM, E-Commerce)
- Global / Local / Business Transaction based attributes
To come to decision on option, data driven analysis will provide a view to come to decision. The analysis can change based on customers requirement. Below are some examples:
Any option shall consider the big picture of Enterprise landscape. I remember, during early Industry3.0 Revolution, many processes and analysis supported Industries, like ISO,TQM (base for CMM). These can be leveraged now in Industry4.0 as well. It’s good to go through below options which are still good that were used in early 1980’s & 1990’s.
TOWS analysis on Industry, Business Process, Option.
- Fishbone Cause & Effect Analysis
Global Attributed are managed by HQ Personas and Local Attributes are managed by Bus. Sometimes Attribute will be Global but the data for the attribute will depend on local business. For an example Shoe product is same, but classification like Size, Raw Material to manufacture, Price etc. could be based on Region (NA,EU,APJ,AMEA). In this case Local Business Process will be varied and hence Master Data is depending on Local Conditions/Process which will be performed by BUs. Pricing also will be changed based on variables like Business Transactions, Season etc. in many scenarios, this is underneath siloed problem and hence leads to ‘Federated’ option. There might be increase in infrastructure but will meet local master data needs. Below picture
The option can be calibrated in a most pragmatic way that help local business needs and clear ownership of master data.
Future step can be migration of global attributes to SAP BTP based SAP MDG Cloud Edition based on availability matrix for data domains.
Hello Srinivasa Rao Sesham ,
Interesting blog. But, the MDI layer is missing in this complete setup, which i feel is a mandatory layer when we are talking about Federated MDG. Otherwise, i agree with this and thanks for Sharing.