preparation for data migration to s4/hana€¦ · • sap have simplified some of their code. check...
Post on 04-Oct-2020
1 Views
Preview:
TRANSCRIPT
PREPARATION FOR DATA MIGRATION TO S4/HANA
J O N O L E E N S T R A3 r d A p r i l 2 0 1 9
A ge n d a
• Why prepare data - why now?
• Six steps to S4/HANA
• S4/HANA Readiness Assessment
• Prepare for your S4/HANA Migration
• Tips and Tricks from the trade
• Summary
‘’Data migration is often not highlighted as a key workstream for SAP S/4HANA projects’’
WHY PREPARE DATA – WHY NOW?
W hy P re p a re d a t a - w hy n o w ?
• The business case for data quality is always divided into either:– Statutory requirements – e.g., Data Protection Laws, Finance Laws, POPI– Financial gain – e.g.
• Fixing broken/sub optimal business processes that cost money• Reducing data fixes that cost time and money• Sub optimal data lifecycle management causing larger than required data sets, i.e.,
hardware and storage costs
• Data Governance is key for Digital Transformation• IoT• Big Data• Machine Learning• Mobility• Supplier Networks• Employee Engagement
• In summary, for the kind of investment that you are making in SAP, get your housekeeping in order
Wo u l d y o u m o ve y o u r d i r t w i t h y o u ?
Keep Clean – SAP Tools
Get Clean – Data Migration
D a t a Q u a l i t y t a ke s t i m e a n d e f fo r t
• Data migration with data clean-up and data governance post go-live is key by focussing on the following:
– Obsolete Data
– Data quality
– Master data management (for post go-live)
• Start Early
– SAP S/4 HANA requires all customers and vendors to be maintained as a business partner
– Consolidation and de-duplication of master data
– Data cleansing effort (source vs target)
– Data volumes: you can only do so much within a timeframe
– Data enrichment requirements - images, alternate UOM, business partners…
example: 5 minutes per record = 200 man days for 20,000 records!
Get Clean
Stay Clean
Right Size
Migrate /Integrate
ImplementS/4HANA
Determine Platform Strategy
1
2 3 4 5 6
Risk Free Journey to S/4HANA
0
S/4HANA Readiness
AssessmentTM
S ix S teps t o S4 /HANA
S4 HANA DATA PREPARATION ASSESSMENT
U n d e r s t a n d w h e r e y o u a r e b e f o r e s t a r t i n g t h e j o u r n e y t o S / 4 H A N A
• Data Quality / Unicode / Archive:
• When transitioning to S/4HANA, data matters big time
• Integration / Interfaces:
• Real-time enterprise management does not work well with batch interfaces
• Versions / Patches:
• Your systems have to fulfil certain minimum release levels before transitioning them to S/4HANA
• Modifications / Enhancements:
• SAP have simplified some of their code. Check your extensions for compatibility
• Configuration / Features:
• Not all SAP and 3rd party add-ons are S/4HANA ready yet. Check for compatibility
• User Experience / Analytics:
• SAP Fiori is the strategic user interface technology for S/4HANA. It will help if you already have experience with it
P l a n n i n g fo r a n E n t e r p r i s e D a t a M i g ra t i o n P ro j e c t
RISK
READINESS
1
RISK
READINESS
2
RISK
READINESS
3
RISK
READINESS
4
VALIDATED & AUTHORISED
RISK
READINESS
5
Op
era
tio
na
l R
ea
din
ess
Business Readiness
HIGH
HIGH
LOW
TECHNICALLY
VALID
BUSINESS
RELEVANT
BUSINESS
READY
RECONCILED
/ HARMONISED
VALIDATED &
AUTHORISED
P l a n n i n g fo r a n E n t e r p r i s e D a t a M i g ra t i o n P ro j e c t
PREPARE FOR S4/HANA MIGRATION
W h e re a n d h o w t o s t a r t p re p a r i n g
DEFINE THE RULES
EXCEPTION
REPORTING
CLEAN UP
AND ENRICH
MONITOR AND TRACK
DATA ASSESSMENT
1 2 3 4 5
D a t a d i s c o ve r y• Data Cleansing register with source
systems, defined object priority, stakeholders & RACI
• Profile data: determine volumes, field patterns, derive baseline rules
• Define business relevant records per object (apply the 80/20 principle)
• Train BA’s & Business
• Data Quality = Change Management
D a t a D i s c o ve r y
D e f i n e t h e r u l e s & re p o r t exc e p t i o n s
Exception Reports
Rules 1-3 Rules 4-7 Rules 8-10 Rules 11-20
50
100
200
150
Weeks
50 rules per week
Da
ta
S p r i nt S o l u t i o n s
Te a m st r u c t u re s - s a m p l e
Core Project Team
Process, Standards, Controls & Data Cleansing Technical enablers
Technical Data
Analyst
Technical Data
Analysts
Business Analyst
Manager
Master
Data Analyst
Business Stakeholders
Key Project Resources
Change Management
Training
Extended
Network
Business
Analysts
ProgramManager
Master Data
Project Manager
To o l s t o c o n s i d e r – D a t a Q u a l i t y D a s h b o a rd s
Tools to cons ider – SAP MDG Conso l idat ion
Standardise ValidateCalculate Best
RecordMatch Activate
DATA LOAD PROCESS FLOW
Validate and enrich address data
Possibility to connect to 3rd party tools for standardisation and enrichment
Find duplicates based on customer specific matching rules
Review match groups
Create Best Records based on approved match groups
Validate best records against backend customising verify whether records can be activated
Provide consolidated master data for analytical or operational use
Option to activate directly or indirectly triggering post processing using central governance
Topic: Master Data Governance focusing on Business Partners
Date: 11 April 2019
Time : 09:30 - 10:30 (CAT)
S D M S o l u t i o n P r i n c i p l e s
Data is validated at point of entry – including data related to transactions
and other complex business logic
Data is derived as far as possible e.g. MRP controller is derived based
on criteria such as Plant and Material type
Only relevant or required fields are editable and/or displayed.
All other fields are dynamically hidden or greyed (based on user roles)
Key data fields that need to be completed are highlighted
Exception reporting means you can proactively identify incorrect data for
correction
Validate
Derive
Hide
Highlight
Identify
Rules can also be applied to Z fields
The value in a field can be changed based on workflow
Can be role-based
M i g ra t i o n w i t h S A P R D S
Safely and successfully migrate legacy data to SAP ERP and
SAP CRM on SAP HANA or non-HANA
1
ANALYSIS
Governance and Visualization
5
LOAD
2
EXTRACT CLEAN
3
VALIDATE
4 6
RECONCILE
Tr u st e d D a t a M i g ra t i o n
Business Challenges
• Data migration projects that run over-budget and overtime
• Lengthy post-merger integration
• Poor quality data = Inability to meet compliance requirements, poor user satisfaction and inefficient business processes
• Untrusted reports, or labour-intensive efforts to create reports outside the system
• Poor ROI based on suspect data quality
Solution
Accelerate data migration with prebuilt best-practices
content for over 100 critical master and
transactional data objects.
DMOR: • Scope
• Data Object Responsible Touch Points
• Volumes and Complexity ratings
• Drives planning & resourcing
• Drives tracking (FMD delivery, ETLR delivery per phase)
FMD: • Source to Target mapping
• Mapping risks (Format, Length, Mandatory\Optional, LOV ID & mapping)
• Transformation and Validation rules
• Purification and Reconciliation considerations
DMPR: • Owned by Business
• Captures volumes \ effort \ plan
• Tracks delivery
RACI by activity / deliverable / role
D a t a M i g ra t i o n D e l i ve ra b l e s
Data Migration Object Register
Field Mapping Documents
Data Migration Purification Register
TIPS AND TRICKS FROM THE TRADE
T i p s a n d Tr i c k s f ro m t h e Tra d e
• Perform the necessary due diligence to define the road to S/4HANA
• In your consideration, factor in your customization of SAP (custom objects) by asking:
– Which ones are relevant?
– Do they support the end state business processes?
– And If so, do they need re-engineering/development?
– Do this by using SAP
• Run the SAP Custom Code Analyzer
• Compare the objects with SAP’s S/4HANA Simplification Database to understand where SAP has made changes that affect your code
• Review the Custom Code Migration Worklist to understand the changes associated with the simplification in HANA
• Plan, prioritize, and estimate the effort for your list of objects
T i p s a n d Tr i c k s f ro m t h e Tra d e ( c o n t . )
• If there are multiple businesses/business units/systems with their own set of data, see if it can be leveraged through consolidation and harmonization– Eg. ensure material masters and business partners are
harmonized between SAP ERP, EWM, and SAP CRM by consolidating the data sets and creating the “golden record” early on
– Again look at SAP tools to assist:• MDG consolidation (MDG 8.0 onwards)
• SAP Information Steward Match Review
• For data quality – define where and what to focus on– For the scope, prioritize data objects to a field level
– Focus on the “money” fields for defining standards/business rules
– To find out what the money fields are, look at the business processes and work backwards
T i p s a n d Tr i c k s f ro m t h e Tra d e ( c o n t . )
• For Data Clean-up, focus on the 80/20 principle:
• Get the data organization involved and gain executive sponsorship
• Data Quality = Change Management
SUMMARY
7 K E Y P O I N T S TO TA K E H O M E
1. Clearly define the business objectives for migration to S/4HANA
2. Gain executive sponsorship for the journey through the objectives
3. Perform the due diligence via a strategy and roadmap when deciding on your migration method
4. Focus on data quality now – don’t wait, no matter which upgrade path you choose
5. Consider tools for migration that can also be used for the project as well as post go-live
6. Make the most of data migration by establishing data governance up front
7. Invest in data management solutions to sustain your investment post go-live
Thank you
jonathan.leenstra@gluedata.com
+27 82 800 8346
top related