Data Migration For S4hana-v1.2.pptx

S/4HANA 2 June 2017 http://ibm.biz/S4H_Learn1610

S/4HANA Data Migration

PRESENTERS Dharma Atluri SAP BO Product Lead, HANA/BW/BO Architect, Client Service Manager, CIC India Global Business Services [email protected]

Snehasish Ghosh BODS and S4HANA Migration Consultant Global Business Services [email protected]

Tejaswini Patil SAP BI/EIM BO Senior Solution Consultant Global Business Services [email protected]

AGENDA This session will cover the following topics:  Migration Cockpit  BODS  Migration Best Practice  Cloud Platform Data Services

Why data migration?

SAP S/4HANA: One Codeline, different products

Scenarios for moving to SAP S/4HANA: The three transition scenarios

What is data migration?

Data migration is the process of transferring data from one system to another, while changing the storage, database, or application. In reference to the ETL (Extract-Transform-Load) process, data migration always requires at least Extract and Load steps. Typically, data migration occurs during an upgrade of existing hardware or transfer to a completely new system. Examples include:  Migration to or from hardware platform  Upgrading a database or migrating to new software  Company-mergers when the parallel systems in the two companies need to be merged into one

There are three main options to accomplish data migration:  Merge the systems from the two companies into a brand new one  Migrate one of the systems to the other one  Leave the systems as they are but create a common view on top of them - a data warehouse

Phases in data migration Every data migration activity would involve a series of phases with defined activities that ensures to identify the data migration strategy. There is no exception in case of S/4 HANA Data Migration as well.

Main considerations in a typical Data Cycle

How to do data migration? Each of the data migration phases needs a combination of tools and processes to effectively achieve the outcome of each phase.

Characteristics of a typical data cycle and tools used

Typical Engagement Type

Typical Tools Used

Data Assessment Phase

Data Profiling Phase

Consulting Engagement

Consulting Engagement

• IBM-specific templates

• IBM Information Analyser

Data Extraction Phase

Data Transformation Phase

Data Loading Phase

Data Quality Maintenance Phase

System Integration Engagement

System Integration Engagement

System Integration Engagement

In-house COE Engagement

• Informatica

• Informatica

• Informatica

• SAP MDG

• IBM Infosphere

• IBM Infosphere

• IBM Infosphere

• SAP MDM

• SAP BODS

• SAP BODS

• SAP BODS

• SAS Dataflux

• BackOffice

• BackOffice

• BackOffice

• Oracle MDM

• Datiris

• Oracle Data Integration

• Oracle Data Integration

• Oracle Data Integration

• Web Methods One data

• Pervasisve

• Others

• Others

• Others

• Hybris

• S/4 HANA Data Migration Cockpit

• S/4 HANA Data Migration Cockpit

• S/4 HANA Data Migration Cockpit

• Tibco

• SAP HANA EIM Services

• SAP HANA EIM Services

• SAP HANA EIM Services

• Talend • Trillium

• SAP Information Steward

• SAP BODS • SAP HANA EIM Services • Information Steward

How to migrate your SAP Data? SAP has provided a comprehensive set of tools, well defined processes and methodology to migrate any SAP or non-SAP legacy data to a new SAP system like SAP BW on HANA or S/4 HANA Solutions.

SAP data migration methodology

Data Data migration migration is is aa major major task task and and key key for for aa successful successful SAP SAP implementation. implementation.

SAP SAP Rapid Rapid Data Data Migration Migration with with SAP SAP Data Data Services Services enables enables you you to to migrate migrate your your data, data, ensuring ensuring your your data data can can be be trusted trusted by by the the users users and and is is ready ready for for business business process process execution execution within within SAP SAP systems systems as as Business Business Suite Suite powered powered by by HANA, HANA, ERP, ERP, SAP SAP Business Business All-in-One, All-in-One, CRM, CRM, and and SAP SAP industry industry solutions solutions for for utilities. utilities.

SAP SAP rapid rapid data data migrations migrations has has three three major major components: components: Software Software driven driven by by SAP SAP Data Data Services Services (hereafter (hereafter Data Data Services) Services) Migration Migration content content developed developed by by SAP’s SAP’s rapid-deployment rapid-deployment solution solution organization organization consulting consulting services services provided provided by by SAP SAP services services and and partners partners

New New content content includes includes data data migration migration content content for for SAP’s SAP’s HCM HCM suite suite in in the the cloud cloud SuccessFactor SuccessFactor Employee Employee Central, Central, SAP SAP Cloud Cloud for for Customer, Customer, and and SAP SAP BW. BW.

Data migration using SAP BODS SAP BO Data Services is the preferred tool of data migration, if the volume of data is substantial and more customized, validation rules and data conversion logics needs to be implemented. SAP also provides Rapid Deployment Solution that is a pre-build set of data service interfaces that can be customized and configured to load data to S/4 HANA using different API like Function Modules , BAPI, or Idoc.

SAP S/4 HANA data Migration Cockpit

Migration objects SAP has outlined the list of objects for which data can be migrated using the cockpit and covers most of the necessary master data and transaction data objects.

Data migration process There are basically two steps for loading data using the cockpit: Data Preparation and Validation & Data Simulation and Import . Data Preparation and Validation  Standard data templates provided for each migration  Data template to be downloaded, filled, and uploaded  The transfer process to be activated which validates data and provides any warnings or errors  The errors and warnings to be fixed

Data Simulation and Import  Data Simulation: This step basically does a simulation of the loading process to identify any further issues with the data and provides a pre-load snapshot of what will happen when the import data process is run. It gives information, warnings, success, and errors.  Data Import: This step basically posts the data to the system. It gives information, warnings, success, and errors. Once you click Finish it gives the information that the file has been processed successfully.

Prepare the data For each Migration object, SAP has provided a definite data migration template, which needs to be filled up with the necessary data. We cannot use any other customized template for this purpose. The example of the template for Material Master is shown below:

Once the template is filled up and ready, use the “Upload” option to upload the file to the Migration Cockpit.

Data validation is already configured Once the validation is completed, it will give a set of messages classified as errors, warnings, information, and success. The next step is to fix this data either in excel or in the mapping step and save it.

Data loading using Migration Cockpit  All actions are performed at the background (as a batch-job/SM37), but you can wait until process is finished 100 % and then immediately see the results or let it run in background and come back later.  It helps if you are familiar with the Standard BAPI Structures and SAP Input Data (for example, how to create a material master).  ABAP Skills are not required, but ABAP debugging skills are useful for the root cause analysis, in cases where the Error Log isn’t enough.

SAP S/4HANA Migration Object Modeler

 The SAP S/4HANA Migration Object Modeler is an application that can be used to adjust the migration objects that are used in the SAP S/4HANA Migration Cockpit.  In the SAP S/4HANA Migration Cockpit, you use templates that specify the relevant data for each migration object. SAP provide templates (Microsoft Excel XML files) that you can use for each migration object.  If a template does not meet your business requirement (for example if the relevant Microsoft Excel XML file does not contain all the fields that you need for the target structure), you can use the SAP S/4HANA Migration Object Modeler to adjust the relevant migration object.  Note that the SAP S/4HANA Migration Object Modeler is only relevant for the on premise edition of SAP S/4HANA. In the SAP S/4HANA system, you can access the SAP S/4HANA Migration Object Modeler by using transaction LTMOM.  We will explain this using a demo video in sometime.

Best Practice - SAP Rapid Deployment Solutions for S/4HANA

Trusted data migration to SAP ERP: What all are included Rapid Data Migration to S4HANA The Rapid Data Migration to SAP® ERP allows you jump start a safe and trusted migration of fixed scope specific for ERP based on industry-leading software, and predefined services at a predictable price.

SAP DATA MIGRATION

1

2

ANALYSIS

EXTRACT

3

4

CLEAN

VALIDATE

5

6

LOAD

Governance and Visualization

RECONCILE

Detailed migration content scope

Pre-defined services for RDS Your path to Go-Live - Fast, efficient, and at predictable cost:  Fixed-price implementation services  Pre-defined project methodology  Ready-to-use accelerators 1

Start

2

Deploy

3

Run

 Project management

 Solution Realization

 Performance Tests

 Kick-off workshop participation

 Master Data Load

 End User Training

 Preparing technical infrastructure

 Refinement Workshop & Refinement Realization

 Sign off of solution

 Knowledge Transfer to Key Users

 Go-Live

Accelerators / Deliverables  Installation guide

 Post go-live support and activities

Accelerators / Deliverables  Consulting Delivery Guide  Project schedule  WBS

 Solution Documentation

 Go-Live Preparation

 Improvements and road map workshop

 Solution Manager content

Accelerators / Deliverables  Test cases

 Request for consultants template

 Best-Practices content (pre-configuration)

 Deliverable acceptance forms

 Process descriptions

 Configuration activities

 Training Materials – Process-flow recordings etc.

 Process-flow-documents

 Consulting Delivery Guide

 Go-Live Checklist

 Kick-off presentation

 Implementation Content

 Service Delivery Model, roles and responsibilities

 Consumption Guide  Pre-delivery requirements and checklist

Note: This slide represents a typical deployment. Exact details may differ according to solution.

Service options available for SAP S/4 HANA RDM

Base Module (Mandatory)  Base or frame service to kick off service and define the scope for implementing modules.  Base includes standard project activities that are generic and can be combined with all described modules

Installation Module (Optional)  Installation of SAP Data Services 4.2 (HANA or non-HANA), SAP Business Intelligence platform 4.2, and SAP  Information Steward 4.2 is the data migration platform

SAP S/4HANA Starter Module (Mandatory based on scope)  Specific setup of the migration starter service  Migration implementation of five objects (three master + two transaction) defined in the base module  Possible Service Flavors  Base module + installation module (if required) + starter module for SAP S/4HANA

RDS deployment scenario

Rapid Data Migration (RDS) to SAP S4HANA Content Download File names

Contents

Deployments

50126415.zip

Step-by-step guide for Rapid Data Migration ERP/CRM/HCM/RETAIL/Data Quality (contains all the RDS-Related documents and detail instructions)

Extract the zip file and double-click start.html in the extract folder. If the browser shows restricted block warning, right-click and select Allow Blocked Content. In the Security Warning dialog box, choose ‘YES’. The main window for the guide appears.

BIPCONTENT08P_4-10012108.zip

RDS BI Platform Content, which contains connection, universe, reports. For ERP/HCM/CRM//RETAIL/Data Quality.

Extract the zip file, all the Rapid Data Migration BI content can be found in the extract folder ‘rds_bip\ERP_CRM_DS’.

SAPRDSDSCONT07P_1-10012109.zip

RDS Data Services Content, which contains DS code, sample data, for ERP/HCM/CRM/RETAIL/Data Quality.

Extract the zip file, all the RDS Data Services content for the ERP/CRM /HCM/RETAIL/Data Quality can be found in the extract folder ‘rds_ds\ERP_CRM_DS’. Copy all these four folders(Migration_DQ, Migration_ERP, Migration_CRM, Migration_HCM, Migration_RETAIL) into Driver C.

MIGRATION03_0-10011631.zip

Migration Services Tool

Extract the zip file and the file MigrationServices.war can be found in the MigrationServices folder.

RDS: S4HANA BI content (1 of 3)

RDS: S4HANA BI content (2 of 3)

RDS – S4HANA BI content (3 of 3)

RDS: Data services templates / content  Activity Price IDOC Mapping Template

Microsoft Excel 97-2003 Worksheet

 Source File as IN for Activity Price

Microsoft Excel 97-2003 Worksheet

Business benefits

Key competitive differentiators

CASE STUDY - Veolia Data Migration

Case study: Veolia Data Migration SAP Rapid Deployment Solution (RDS) for SAP BODS was leveraged for Veolia Environment Services to migrate legacy data for three different divisions: Water, Energy, and Waste to S/4 HANA (Finance and Procurement modules). The implementation work included customization of the RDS Data Services Loading interfaces to suit the business requirement as well as create new interfaces and reconciliation reports to cater customer-specific needs.  Veolia Australia S/4 HANA implementation is focused on S/4 HANA (Finance and Procurement modules).  Veolia has three business divisions: ‒ Water ‒ Energy ‒ Waste

 Of these, the largest is Waste in terms of revenue and uses SAP-ISU. Water uses Sun Systems while Energy is using Pronto.  Veolia has 100+ secondary applications that support the above three ERPs.  40 interfaces are also included in scope using SAP Process Orchestration.

Interface development process SAP BODS performs the following roles sequentially:  As an ETL tool, to extract data from source systems  Connecting to SAP using SAP Application Type Data Store  Run transformations to apply data validation checks prior to load  Loading the data into the HANA system

It was observed that customization of the RDS jobs was necessary to cater actual business requirements, since the existing customer did not want all the components or all the fields as defined in RDS package to be migrated to S/4 HANA. Some of the reasons are as below:  Not all the components is necessary. For example, we have only loaded MARA, MARC, MBEW, MAKT, MARM for Material.  IDoc or BAPI method of loading is not working due to certain data restrictions or setup issues.  Need to use Function Module instead of BAPI / IDoc for data load. For example, WBS Element had to be loaded using Function Module BAPI_PROJECT_MAINTAIN though SAP provides IDOC PROJECT01.

36

Reconciliation reports SAP BODS RDS Package provides Standard Field Based Reconciliation Reports and IDoc status reports, which can be leveraged. However, the field based reconciliation report is on all fields and could be misleading and hence customization is necessary to identify and implement the correct set of fields necessary. In Veolia, two different type of reconciliation report were developed based on business needs: 1. Interface specific Overall Reconciliation report: This is to identify what was in source and what was loaded to SAP Tables. This has been done Key based for example, SAKNR for GL Account, and MATNR for Material, PARTNER for Vendor Master and Customer Master, PRCTR for Profit Center, KOSTL for Cost Center, and so on.

 The above flow was created for doing Overall reconciliation.  GL_SKA1_GROUP_ENR & GL_SKA1_OPERATING_ENR (Contains Cleansed data from SAP Legacy) are source tables and SAP_SKA1_DUMP is already loaded data extracted from SAP. 37

Reconciliation reports (continued) 2. Mandatory Field Based Reconciliation: Business expected to validate column specific data for mandatory fields in SAP against the data in the same columns as coming from source.

This flow was creating for doing mandatory field by field reconciliation. Here GL_SKA1_GROUP_ENR is source table The reconciliation reports are being created in such a way that they can be used as reusable asset in other projects. Currently they are interface specific and mandatory field based as expected in S/4 HANA tables.

38

Reconciliation data snapshot

LOADED_FLAG indicates whether the Account is loaded or not

39

The Flag Y indicates the field value in SAP target table and source table is matching

Material Master Load Program (SAP RDS)

 This is one of the SAP RDS job that we have leveraged with customization to load material master data.  One of the specific requirements handled is like directly feeding new material numbers as per S/4 HANA standards as well as not all the components are being used and we can dynamically flag which part to execute and which not to.  We have been able to load around 15000+ new materials in a expected runtime of around 9 hours

40

Material Master Load Program

The attached screen capture presents how the data is loaded from tables by creating the nested IDoc Structure using MATMAS_MASS_BAPI03.

41

Vendor Master Loading Program (SAP RDS)

 In S/4 HANA Vendor Master and Customer, Master are being loaded as Business Partner.  SAP RDS Business Partner Interface has been leveraged along with customization to load the data.  We have also worked with SAP to implement enhancement to load Partner Function that was currently not available in RDS.

42

Vendor Master Loading Program

The first figure presents how we are calling the function module RFC_CVI_EI_INBOUND_MAIN from Data Services to load the Business Partner data. A – Function Module is called B – Error Data is Returned The Second figure is a bit more detailed as how we are sending the various input data as well as returning error, if any.

43

Chart Of Accounts (GL Master) Loading Interface (IBM Developed)

 Framework built to extract data from source to staging tables from SKA1, SKB1 tables.  The other two snapshots present how we are processing the data and how we are loading data using GLMAST01.

44

Interfaces developed

45

SAP best practices for SAP S/4 HANA The SAP best practices for SAP S/4HANA are tailored specifically to accelerate and simplify the adoption of SAP S/4HANA, on-premise edition for faster time to value, by providing pre-configured content for core business processes with rolespecific, responsive, and simple user experience. The guided configuration allows a simpler configuration, automated testing, and life-cycle management to support agile adoption of continuous innovation even after go-live. Analytical content, such as operational reporting is now included as well as UX Fiori content providing the infrastructure for the deployment, testing, and extension of S/4HANA user interface components. SAP best practices for Migration complements the foundation and offers customers a non-disruptive, simplified transition to SAP S/4HANA. SAP best practices offers integration to cloud solutions from SAP such as SuccessFactors Employee Central and Ariba. The SAP best practices for SAP S/4HANA, on-premise edition can enable you to improve:  Manufacturing  Sales  Sourcing and Procurement  Supply Chain and Analytics The SAP best practices for the above can be explored using the below link: https://rapid.sap.com/bp

RESOURCES

Resources Read the Learning Hub blogs at: http://ibm.biz/LH_S4H_FIN on how to Search, Find, and Complete Learning Hub DS10 and DS30 are the top BODS courses

SAP Learning Journey https://training.sap.com/learning/journey/

Resources

Future Sessions S/4HANA Fiori Deep Dive (changes,new apps) on 30th June 2017 BW/4HANA – Deep Dive - TBD

Playback of previous sessions: https://w3-03.sso.ibm.com/services/lighthouse/bluetu be/series/681 Presentation of previous sessions http://ibm.biz/S4HANA_MOOC

Future IOT MOOC Series Only selected participants who have completed the challenges for SAP Cloud Platform and IOT MOOC.

Where to go for more information on S/4HANA? S/4HANA Overview

Join the Fiori Community on SCN

S/4HANA Business Scope

Use Case Blog on SCN

Best Practice Scope

S4HANA Product Scope

S/4HANA Cookbook

Innovation Key Use Cases

SAP Best Practice

S/4HANA Important Links S4 HANA Enterprise Management Community on Connections Cloud #S4HANA 1610 Help FPS02 #S4HANA 1610 Release information on one page

Learning Journey Blogs Best Practice Explorer

http://ibm.biz/S4HANA_EM https://help.sap.com/viewer/product/SAP_S4HANA_ON-PREMISE/ 1610%20002/en-US http://go.sap.com/product/enterprise-management/s4hana-erp/onpremise.details.html https://blogs.sap.com/2017/02/22/sap-s4hana-on-premise-edition1610-feature-pack-stack-1-fps01/ https://blogs.sap.com/2017/05/10/sap-s4hana-1610-feature-packstack-2-fps02/ http://ibm.biz/LH_S4H_LOG http://ibm.biz/LH_S4H_FIN https://rapid.sap.com/bp/

S4HANA White Paper

https://w3-03.sso.ibm.com/services/lighthouse/documents/P557407 V94571D56

SCN Blog on 1610 Use case (Business and Technical View Points including topics like AATP and EWM)

https://blogs.sap.com/2016/11/09/s4hana-1610-use-case-series-intro/

SAP S/4HANA Press Your first step toward SAP S/4HANA!  Learn how SAP S/4HANA enables digital transformation  Explore innovative financials and logistics functionality  Understand the technical foundation underlying SAP S/4HANA advances Purchase the book and e-book at: www.sap-press.com/4153  15% discount using the code SAPS4HANA15  Available as e-book as well as hardbound SAP S/4HANA: An Introduction Written by: Axel Baumgartl, Dmitry Chaadaev, Nga-Sze Choi, Mark Dudgeon, Asidhara Lahiri, Bert Meijerink, Andrew Worsley-Tonks, Devraj Bardhan 449 pages | 11/2016 | E-book: $59.99 | Print: $69.95 | Bundle: $79.99

Q&A