Preparation for Data Migration to S4/Hana
Total Page:16
File Type:pdf, Size:1020Kb
PREPARATION FOR DATA MIGRATION TO S4/HANA JONO LEENSTRA 3 r d A p r i l 2 0 1 9 Agenda • 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? Why Prepare data - why now? • 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 Would you move your dirt with you? Get Clean – Data Migration Keep Clean – SAP Tools Data Quality takes time and effort • 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! Six Steps to S4/HANA 2 3 4 5 6 0 Right Get Migrate / Implement Stay Size Clean Integrate S/4HANA Clean S/4HANA Readiness AssessmentTM 1 Determine Platform Strategy Risk Free Journey to S/4HANA S4 HANA DATA PREPARATION ASSESSMENT Understand where you are before starting the journey to S/4HANA • 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 Planning for an Enterprise Data Migration Project HIGH VALIDATED & AUTHORISED RECONCILED VALIDATED & / HARMONISED AUTHORISED BUSINESS READY BUSINESS RELEVANT READINESS TECHNICALLY READINESS VALID READINESS READINESS READINESS 5 2 3 4 1 RISK RISK Operational Readiness Operational RISK RISK RISK HIGH LOW Business Readiness Planning for an Enterprise Data Migration Project PREPARE FOR S4/HANA MIGRATION Where and how to start preparing 1 2 3 4 5 CLEAN UP MONITOR DATA DEFINE THE EXCEPTION AND AND TRACK ASSESSMENT RULES REPORTING ENRICH Data Discovery Data discovery • 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 Define the rules & report exceptions Sprint Solutions Rules 1-3 Rules 4-7 Rules 8-10 Rules 11-20 50 rules per week Exception Reports 200 150 Data 100 50 Weeks Team structures - sample Program Manager Core Project Team Master Data Project Manager Technical enablers Process, Standards, Controls & Data Cleansing Technical Data Business Analyst Analyst Manager Technical Data Analysts Business Master Analysts Data Analyst Key Project Resources Extended Network Business Stakeholders Change Management Training Tools to consider – Data Quality Dashboards Tools to consider – SAP MDG Consolidation DATA LOAD PROCESS FLOW Calculate Best Standardise Match Validate Activate Record Validate and enrich Find duplicates Create Best Records Validate best Provide address data based on customer based on approved records against consolidated specific matching match groups backend master data for Possibility to rules customising verify analytical or connect to 3rd party whether records operational use tools for Review match can be activated standardisation and groups Option to activate enrichment 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) SDM Solution Principles Identify Exception reporting means you can proactively identify incorrect data for correction Highlight Key data fields that need to be completed are highlighted Only relevant or required fields are editable and/or displayed. Hide All other fields are dynamically hidden or greyed (based on user roles) Data is derived as far as possible e.g. MRP controller is derived based Derive on criteria such as Plant and Material type Data is validated at point of entry – including data related to transactions Validate and other complex business logic Rules can also be applied to Z fields The value in a field can be changed based on workflow Can be role-based Migration with SAP RDS Safely and successfully migrate legacy data to SAP ERP and SAP CRM on SAP HANA or non-HANA 1 2 3 4 5 6 ANALYSIS EXTRACT CLEAN VALIDATE LOAD RECONCILE Governance and Visualization Trusted Data Migration Business Challenges • Data migration projects that run over- budget and overtime • Lengthy post-merger integration Solution • Poor quality data = Inability to meet compliance requirements, poor user Accelerate data migration satisfaction and inefficient business with prebuilt best-practices processes content for over 100 critical master and transactional data objects. • Untrusted reports, or labour-intensive efforts to create reports outside the system • Poor ROI based on suspect data quality Data Migration Deliverables DMOR: Data Migration Object Register • Scope • Data Object Responsible Touch Points • Volumes and Complexity ratings • Drives planning & resourcing • Drives tracking (FMD delivery, ETLR delivery per phase) FMD: Field Mapping Documents • Source to Target mapping • Mapping risks (Format, Length, Mandatory\Optional, LOV ID & mapping) • Transformation and Validation rules • Purification and Reconciliation considerations DMPR: Data Migration Purification Register • Owned by Business • Captures volumes \ effort \ plan • Tracks delivery RACI by activity / deliverable / role TIPS AND TRICKS FROM THE TRADE Tips and Tricks from the Trade • 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 Tips and Tricks from the Trade (cont.) • 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 Tips and Tricks from the Trade (cont.) • 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 KEY POINTS TO TAKE HOME 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 [email protected] +27 82 800 8346.