Week 1: Staging Tables Approach and Migration Object Modeler Unit 1: Introduction to Data Migration Introduction to data migration Weekly learning objectives Week 1: Staging Tables Approach and Migration Object Modeler By the end of this week, learners will be able to ▪ Explain data migration requirements and tools to support you in your project ▪ Comprehend the migration process in the SAP S/4HANA migration cockpit, including executing a staging table project ▪ Understand special topics that are valid for SAP S/4HANA and SAP S/4HANA Cloud, private edition ▪ Work with the migration object modeler in a staging table project Check out the openSAP course “Migrating Data to SAP S/4HANA Cloud, Public Edition”. This course focuses on SAP S/4HANA Cloud, public edition and deep dives into migrating data using staging tables. Week 2: Direct Transfer Approach Week 3: Migration Object Modeler for Direct Transfer © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2 Introduction to data migration Agenda Data migration requirements in a “new implementation” transition scenario Supporting tools: SAP Activate methodology, SAP Signavio Process Navigator, Data Migration landing page Overview of SAP S/4HANA migration cockpit © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3 Introduction to data migration Transition paths recap Approach REUSE with in-place conversion Business Driver Start rapid modernization Transition Option System conversion Target SAP S/4HANA Cloud, private edition SAP S/4HANA versus REENGINEERING with data migration Customer tailored Highly standardized, with best practices and based on a clean core © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Selective business process optimization Business model innovation Selective data transition New implementation SAP S/4HANA Cloud, private edition SAP S/4HANA SAP S/4HANA Cloud, public edition SAP S/4HANA Cloud, private edition SAP S/4HANA 4 Introduction to data migration Focus: new implementation Approach REUSE with in-place conversion Business Driver Start rapid modernization Transition Option System conversion Target SAP S/4HANA Cloud, private edition SAP S/4HANA versus REENGINEERING with data migration Customer tailored Highly standardized, with best practices and based on a clean core Selective business process optimization Business model innovation Selective data transition New implementation SAP S/4HANA Cloud, private edition SAP S/4HANA SAP S/4HANA Cloud, public edition SAP S/4HANA Cloud, private edition SAP S/4HANA Mapping Your Journey to SAP S/4HANA – A Practical Guide for Senior IT Leadership © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5 Introduction to data migration Data migration requirements What are the sources / sender systems of the data? Number and type of source systems? Central master data management? Which data is needed from your source to operate SAP S/4HANA the way you want? Master data? Open items? Balances? Migrate data “as is” or transform on the fly? Data transformations needed? Data quality improvement necessary? Who needs to be involved? Decisions to be taken? Major stakeholder? Bottom Line: Start as early as possible to ensure high quality data © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6 Introduction to data migration Sources to support you in your migration process SAP Activate Methodology (Roadmap Viewer) ▪ Access implementation guidance for your digital transformation ▪ View and download SAP Activate methodology assets and accelerators ▪ https://go.support.sap.com/roadmap viewer/# © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC SAP Best Practices via SAP Signavio Process Navigator ▪ Access and download SAP Best Practices content ▪ Power your project with ready-to-run business processes Data Migration Landing Page on SAP Help ▪ Access documentation – Application Help ▪ View additional slide decks and training information ▪ http://help.sap.com/S4_OP_DM ▪ https://me.sap.com/processnavigator 7 Introduction to data migration Facilitate migration projects with SAP S/4HANA migration cockpit Out-of-the-box, included in SAP S/4HANA and SAP S/4HANA Cloud license and shipment Preconfigured SAP S/4HANAspecific migration content Guidance and simulation for the migration process SAP S/4HANA Migration Cockpit Integrated into SAP Activate methodology Automated mapping between source and target Lower migration time and costs No developer skills required Migration object modeler for custom requirements © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8 Introduction to data migration Data migration process with SAP S/4HANA migration cockpit SAP S/4HANA Cloud, public edition SAP S/4HANA Cloud, private edition Select migration objects Get data SAP Business Suite Map and transform data Model and design to reflect custom requirements Simulate Migrate SAP S/4HANA Legacy Migration programs are automatically generated – no programming required © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9 Introduction to data migration Migration approaches Two different migration approaches, depending on the source system: Migrate Data Using Staging Tables Migrate Data Directly from SAP System (Direct Transfer) ▪ Staging tables are created automatically in the SAP HANA DB (either locally or in a remote system) ▪ Connect source system (ABAP-based SAP source systems) via RFC connection ▪ Populate these staging tables with business data using: – XML template files – CSV template files – SAP or third-party ETL tools ▪ Selection – Based on predefined selection criteria (for example, company code for ERP source system) and selected migration objects – Can be adapted with the SAP S/4HANA migration object modeler ▪ Supports data migration scenarios from SAP ERP, SAP AFS, SAP APO SPP, SAP CRM, SAP EWM © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10 Introduction to data migration Migration objects Preconfigured SAP S/4HANA-specific migration content What is a migration object? ▪ Represents a business entity in SAP S/4HANA, such as a customer, sales order, or invoice ▪ Encapsulates the logic to create the specific business entities through the corresponding APIs offered by SAP S/4HANA ▪ Delivered by SAP based on SAP Best Practices configuration and ready for immediate use ▪ Categorized in master data and transactional data (no historical data) ▪ Contains rules for how values from source to target are handled – called “mapping” What is migration content? ▪ Migration content is the sum of all migration objects What about updates on migration objects delivered by SAP? ▪ Updates are shipped by SAP (e.g. a standard field was added) with a new release or via TCI notes © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11 Introduction to data migration What it is designed for (in/out of scope) Designed for: ▪ Initial load of data (master data, open transactional data, no historical data) ▪ Used in the context of a new implementation of SAP S/4HANA, SAP S/4HANA Cloud, private edition, and SAP S/4HANA Cloud, public edition ▪ Transport projects from DEV-Q-PROD via CTS ▪ Direct Transfer: Source system can also be a non-Unicode system Not designed for: ▪ Keeping data in sync across systems* ▪ Realizing a continuous exchange or flow of data* ▪ Establishing an integration scenario* ▪ Cleansing data ▪ Migrating data directly from SAP S/4HANA or SAP S/4HANA Cloud to SAP S/4HANA is currently not supported. * For this purpose, SAP products like SAP Master Data Governance, Central Finance, product data replication, SAP Landscape Transformation Replication Server, or SAP Data Intelligence are available (list does not claim to be complete) © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12 Introduction to data migration SAP S/4HANA migration cockpit does not migrate historical data Do you remember the last time you moved house? ▪ SAP S/4HANA migration cockpit is designed for a new implementation. ▪ No migration objects for historical data in migration cockpit*: ▪ Only the data necessary for a smooth business start is migrated. ▪ A comprehensive customer-specific evaluation makes sense. Solutions like Business Warehouse or side-by-side extensibility can be considered. Examples: ▪ The migration of closed documents leads to postings which are already included in the balances; there are no longer open items for those documents. ▪ For partially open items, only the remaining quantities or values should be migrated. * Exception: FI – Historical balance migration object see SAP Note 2943035 © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13 Introduction to data migration Migration strategy – General considerations It is important to determine how data is transferred from the legacy system to the new system as early as possible. There are many influencing factors that could drive the appropriate approach for a specific system. Some factors to consider include, but are not limited to: ▪ Amount of business data to be transferred and converted ▪ Permitted business downtime ▪ Data changes in scope during migration ▪ Type of data in scope for migration ▪ Business data quality of the source system ▪ Check Customizing Relevant Customizing in the target must be available (for example, organizational units, define document type for migration, define accounts for migration, remove account blocks) © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14 Introduction to data migration Key takeaways In this unit you have learned ▪ Why data migration in a new implementation scenario is important ▪ About SAP S/4HANA migration cockpit as the tool of choice DATA MIGRATION IS NECESSARY It is one key task during the transition to SAP S/4HANA. Unfortunately, it is often underestimated. It can’t be done by just pressing a button. Make sure to understand your data migration requirements early and plan for them accordingly. © 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15 Thank you. Contact information: open@sap.com Follow all of SAP www.sap.com/contactsap © 2023 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.