Part 3 – SAP MDG – A Stepping Stone for SAP S/4HANA Journey

[Antony_Prasanna]

Introduction

Clients across the globe are getting into the Transformation journey started with SAP S/4HANA.

In this blog, we will take one of the use cases to discuss how the master data (MDG)  journey will be the stepping stone for SAP S/4HANA Transformation and the needed steps to achieve it.

This is the third blog on this topic. For Part 1 & 2 , kindly refer

https://blogs.sap.com/2023/01/27/sap-mdg-a-stepping-stone-for-sap-s-4hana-journey-part-i/

https://community.sap.com/t5/technology-blogs-by-members/sap-mdg-a-stepping-stone-for-sap-s-4hana-jo...

Key Aspects for MDG : Deep Dive

B. MDG Specific

B.1 Data Model

As MDG going to the central master data systems catering for 3 ECC systems & future S/4 system, it is important to finalize the fields ( data model) to be governed & strategy for maintenance

Approach for Fields Finalization

3 ECC systems are using the same master data object ( Ex. Customer) with various fields depending upon the business process.

Following is the high-level overview through which the fields needed for MDG governance can be obtained

• As-Is Analysis: Field usages by Account Groups & ECC systems

The current usages of field across multiple account groups & ECC systems needs to be analysed

There are multiple tools which helps to get this data cardinality report from the given data sources.  Such reports need to be brought up for this analysis

There would be multiple scenarios in this case based on the report, a sample given below

For easy understanding, I have given as High, Medium and Low. In the real world, it needs to be defined as the % of data availability in that field.

• As-Is Analysis: Master Data Form

The next step would be to understand the fields used from the current business process perspective.

Master data forms used in the current process will help to understand the fields collected from businesses.

Also if there are any fields derived in the form/system as per business rules, then those fields also need to be understood and considered.

• To-Be Finalization

Based on the insights from the system & master data form , the To-Be fields need to be finalized as follows

There could be multiple combinations on this matrix. It needs business discussions & agreement for the fields if it needs to be excluded from To-Be scope

Once the list of fields are finalized, then it needs to be checked in MDG whether it is already available in Out of the Box data model. If its not the case, the below topic – Strategy for MDG governance should be considered

• Field Status (M/O/R/H)

Once the fields for the To-Be data model is finalized, the next step would be the field status finalization by each account groups

The below picture shows the current field status for each field by account group & systems ( As-Is state) which shows differences

M – Mandatory ; O – Optional ; R – Read-Only ; H – Hidden

The following would be the approach to finalizing the future Field status

If there are differences, then there needs a thinking on the future and take up the next steps.

Knowing the vision that SAP MDG would be the foundation of future SAP S/4HANA, however, it also needs to support the legacy world. So the solution design should be a bridge between the legacy & future world.

Also, not all business processes have been optimized & standardized as part of this program. So, there will be differences in terms of field being used and their field status.

Due to this, it calls for the flexibility of MDG solution in terms of the field status. One of the proposal would be

• Wherever the field status is the same (Either M/O/R/H) across all ECC systems, in the To-Be (MDG) it will be the same (Either M/O/R/H) and it will be configured at the back end
• However if the field status is different, then in the To-Be (MDG) , do the Optional be considered?
  • Say O- Optional is majority, then it can be configured at the back end
  • Also keeping Optional at the back end configuration will help to overcome the forced need of data enrichment at local systems for data migration in to MDG & also for CRUD process

The need for a specific ECC system field status ( Ex: Field 2 for ECC – Americas to be mandatory for Acc grp 1) to be catered via UI and/or validation. Solution approach will be described in their relevant sections

Strategy for MDG Governance

SAP provides out of the box data model for the master data objects ( Customer, Vendor, Material & Finance). Not all standard SAP fields are part of OOB data model.

However, SAP MDG supports the extensibility of the data model. It needs to be considered as development (WRICEF) in that case.

A strategic discussion & decision to be made in terms of the fields governance in MDG. There are a couple of options for this as described below

In the next blog, I will cover other topics in detail.

About the Author,

Antony Prasanna has been working in SAP master data space for 18+ years. Have experience working across multiple large transformation programs on SAP S/4HANA including SAP MDM, MDG and Data Migration tools.