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.
Use Case
In the complex landscape having multiple systems, one of the major challenges is the lack of unified master data with unique definitions and quality.
SAP Master Data Governance (MDG) is the strategic tool by SAP to have master data managed in a governed way to achieve "Get Data Clean; Keep Data Clean".
There are multiple styles of having a master data journey started.
When SAP MDG is to be built at the start of the program, MDG has to be independent of the operational ERP systems.
SAP MDG will be implemented in the Hub model, meaning there will be a dedicated SAP S/4HANA instance on which MDG will be running.
In this blog, we will be focusing on the scenario: SAP MDG has been implemented in a central governance mode and connected to operational ERP systems.
As MDG has been getting started, there are multiple key factors to be considered and design aspects to be considered
Following are the key topics to be covered
Scope Finalisation
The very first thing is the scope of the master data objects to be governed in MDG to be decided. SAP provides Material, Vendor, Customer and Finance master data objects as out of the box solution.
A. Initial Setup
A.1. Baseline Configuration
The baseline configuration needed to be done for the identified fields (Will discuss in detail during the data model topic on identifying the fields needed for MDG).
Values Finalization
As there are 3 different SAP ECC systems, the drop-down values for the field need to be analysed to understand the cardinality (usages) in the master data in each ECC system.
Usages will be one of the key factors to consider for future MDG system
Values Analysis
SAP delivers the standard out-of-the-box data model which includes the drop-down values as well. These MDG values need to be compared against the finalised drop-down values of 3 ECC systems
There could be the following 4 combinations of occurrences on analysis
(i) Code and Description Matches → No Action as needed values already exist in MDG
(ii) Code Matches; Description doesn't match → Need to create a new code in MDG with the needed description and do value mapping against the ECC value.
(iii) Code doesn't match; Description match → Need to create a new code in MDG with the needed description and do value mapping against the ECC value.
(iv) Unique ECC Values don't match with MDG → Need to create a new code in MDG with the needed description and do value mapping against the ECC value ( if MDG follows a different code from ECC).
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 the last 17+ years. Has experience working across multiple large transformation programs on SAP S/4HANA . From tools, perspective, worked on SAP MDM, MDG and Data Migration tools.
This is my first SAP blog and looking forward to an exciting journey ahead.
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.
Use Case
Business Context
- In the current landscape, there are 3 separate SAP ECC instances for each region: APAC, Europe and the Americas
- The business process for both master data and transactional data is different by country within a single Region ( ECC instance) and also across regions ( Other ECC Instances)
- The best practices are not fully adhered to in many cases, so in the long run, it is expected to optimise/standardize the process for better efficiency
IT Context
- In the roadmap, a single instance of SAP S/4HANA to replace the 3 separate ECC instances in the phased manner
- A dedicated master data system to ensure the governance, data quality and unified master data sent across the landscape for business operations
Master Data Journey
In the complex landscape having multiple systems, one of the major challenges is the lack of unified master data with unique definitions and quality.
SAP Master Data Governance (MDG) is the strategic tool by SAP to have master data managed in a governed way to achieve "Get Data Clean; Keep Data Clean".
There are multiple styles of having a master data journey started.
When SAP MDG is to be built at the start of the program, MDG has to be independent of the operational ERP systems.
SAP MDG will be implemented in the Hub model, meaning there will be a dedicated SAP S/4HANA instance on which MDG will be running.
In this blog, we will be focusing on the scenario: SAP MDG has been implemented in a central governance mode and connected to operational ERP systems.
Advantages of starting MDG ahead of the S/4HANA Journey
- Early insight and opportunity of getting the master data prepared
- Work on business processes optimization using master data cleanup
- To start the work on “Get Data Clean” and “Keep Data Clean” through MDG
- Build a team with ownership defined
- Unified master data is created in one single place and sent it across the operational system.
Key Aspects of MDG Journey
As MDG has been getting started, there are multiple key factors to be considered and design aspects to be considered
Following are the key topics to be covered
A. Initial Setup
- Baseline Configuration
- Account Group Consolidation ( As needed)
- Number Ranges
B. MDG Specific
- Data Model
- User Interface
- Workflow
- Validation & Derivation
- Syndication
- Authorisation
C. Data Preparation
- Data Quality
- Cleansing
- Deduplication
- What's specific in SAP S/4HANA from ECC
- Data Migration
D. People
- Data Governance Organisation setup
E. Other Systems Remediation
- SAP ECC Remediation
- Downstream system remediation
- Middleware
Key Aspects for MDG: Deep Dive
Scope Finalisation
The very first thing is the scope of the master data objects to be governed in MDG to be decided. SAP provides Material, Vendor, Customer and Finance master data objects as out of the box solution.
A. Initial Setup
A.1. Baseline Configuration
The baseline configuration needed to be done for the identified fields (Will discuss in detail during the data model topic on identifying the fields needed for MDG).
Values Finalization
As there are 3 different SAP ECC systems, the drop-down values for the field need to be analysed to understand the cardinality (usages) in the master data in each ECC system.
Usages will be one of the key factors to consider for future MDG system
Values Analysis
SAP delivers the standard out-of-the-box data model which includes the drop-down values as well. These MDG values need to be compared against the finalised drop-down values of 3 ECC systems
There could be the following 4 combinations of occurrences on analysis
(i) Code and Description Matches → No Action as needed values already exist in MDG
(ii) Code Matches; Description doesn't match → Need to create a new code in MDG with the needed description and do value mapping against the ECC value.
(iii) Code doesn't match; Description match → Need to create a new code in MDG with the needed description and do value mapping against the ECC value.
(iv) Unique ECC Values don't match with MDG → Need to create a new code in MDG with the needed description and do value mapping against the ECC value ( if MDG follows a different code from ECC).
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 the last 17+ years. Has experience working across multiple large transformation programs on SAP S/4HANA . From tools, perspective, worked on SAP MDM, MDG and Data Migration tools.
This is my first SAP blog and looking forward to an exciting journey ahead.
- SAP Managed Tags:
6 Comments
