SAP S/4HANA Migration Cockpit October 2018The information inthis presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement ot any other service fr subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein, This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information inthis presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantabilly ness fora particular purpose, or non-infringement, This presentation is for informational purposes and may not be incorporated into a contract. SAP. ‘assumes no responsibilty or errors or omissions in this presentation, except if such damages were caused by SAP's intentional or gross negligence. 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, which speak only as of their dates, {and they should not be relied upon in making purchasing decisionsAgenda * Introduction = Development News SAP S/4HANA Migration Cockpit = Migration Objects * Development News Migration Object Modeler = Outlook = Further informationSAP S/4HANA Migration Cockpit - Overview Cloud 1808 / On-Premise 1809 SAP S/4HANAY SAP S/4HANA Migration Cockpit oe Data Provisioning Process Content ‘Single pit fen Precontgurc miraton “Template File a amaaa ‘beds and mapping Upload, ied rocedire Eon Generation of migration Extract D> progam ata ranstoation entoxng ‘ata vadaton| Logs Intograton of custom ojocs tang Migraine Nodelee™ Legacy Migration Object Modeler Sete ene ec ge seerSAP S/4HANA Migration Cockpit — Migration Approaches Transfer Data Using Files + download template fle for elevant migration object qP ie + popu eth rlovent busines ta il + upload file to the SAP S/4HANA migration cockpit oe Pere Transfer Data Using Staging Tables + staging tables are created automatically (in an SAP HANA DB schema) * populate staging tables wih business data r bow * transfer data from staging tables to target SAP S/4HANA system Planned Recommended fori as of 1709 FPSO2 * access source system database directly (ABAP-based SAP source systems only) * transfer data from SAP source system to target SAP SI4HANA system + supports data migration scenarios from other applications, e.. from SAP Apparel and Footwear (AFS) = to S/4 Fashion and Vertical Business Pe @ Transfer Data Directly from SAP Source System (planned)Development News 1808 / 1809SAP S/4HANA Migration Cockpit - Skip Simulation New features with 1808 and 1809 [1] The usability of the Migration Cockpit has been improved by providing the following 2 new features to the Quided activity for the transfer process: (1) In the step ‘Convert Values’, a new button Skip ‘Simulate Import’ has been added. If you choose this button, the system skips the simulation step and proceeds directly to the step ‘Execute Import 23 Warning xSAP S/4HANA Migration Cockpit - Back to Convert Values New features with 1808 and 1809 [2] (2) In the step ‘Execute Import’, a new button ‘Back to ‘Convert Values" has been added. You can choose this button to return to the step ‘Convert Values’, which might be necessary in case of failed export due to missing mapping values or incorrect mapping values. Additional Enhancement in Guided Activity Previously, in the guided activity for the step ‘Convert Values’, an error occurred if target values were left empty. Now, if target values are left empty, the system displays the warning message ‘Contains empty target values’ Note that this feature is only possible if the value help of the object allows blank values. fSAP S/4HANA Migration Cockpit - Improving Performance Cloud Edition 1808 / On-Premise 1809 For Cloud 1808 Transfer multiple files in parallel For On-Premise 1809 Transfer multiple files or use more than one data transfer job to transfer staging tables To do so, use the field ‘No. of Data Transfer Jobs’ in the ‘Migration Object Details’ screen. (Up to 80 percent of available batch processes per migration objects possible in the Cloud). Note If the data transfer is currently in process for a migration object, changing the number of data transfer jobs for that object has no effect. For your changes to take effect, you can finish the transfer (button Finish) and choose the Start Transfer button againSAP S/4HANA Migration Cockpit — File Upload - Cloud qP Enhancements * Default size limit for each uploaded XML file 100 MB. Ifa file exceeds this limit, the message File size too large’ is displayed. cove come 208 wo K ue eo 100M n loud systems You can zip several files together. Note that the combined size of all the XML files you want to add to the zip file must not exceed 160MB Limit for zip file is still 100 MB.SAP S/4HANA Migration Cockpit — File Upload - on-Premise Enhancements = Default size limit for each uploaded XML 100 MB. 30MB = 30MB_-«100MB180MB. & ; , ey © Ifthe file exceeds this limit, the message ‘File size too large’ is displayed. ene = Ifyou need to upload larger files, there are two options: Some 20MB100Me_se0M8 - You can change a system parameter . (iemmMTTPImax. request size, KB) to increase the size limit for each Mf & uploaded XML file to 160MB. —=_ - You can zip several files together. Note that the combined size of all Pours the XML files you want to add to the zip file must not exceed 160MB. porometeris se Limit for zip file is still 160 MB with adjusted system parameter.SAP S/4HANA Migration Cockpit — File Approach Corrections Uploaded XML file: * Handling of empty lines is now possible. Download XML template: = Previously, when using Chrome (or another browser that was not Internet Explorer) to download the XML template, there was a missing ‘.xmI' extension in file name. This issue has been resolved.SAP S/4HANA Migration Cockpit - Transfer Data Using Staging Tables ems System Setup (On-Premise) l fl ‘SAP S/MHANA On-Premise or separate SAP HANA box" SAP S/SHANA On-Premise SAP S/4HANA eo Migration Cockpit | So“ ( Application Tables Application DataSAP S/4HANA Migration Cockpit - Transfer Data Using Staging Tables System Setup (Cloud — planned for 1811) ‘SAP Cloud Platform ‘SAP SISHANA Cloud it onac. SAP HANA DB schema SAP S/4HANA Migration Cockpit opac via DBaaS Customer ravi: ‘Communicaton Arrangement (Service) ls ‘SAP Clove Platform Account nae Customer must register fer 23S HANA Instance on SAP Cloud Platform ‘Gustomer ae to request he acation via tekst on component X_S4C-OPR-SRV (scope tom 202) s00 apoliation nolo ‘nSSAP S/4HANA Migration Cockpit - Staging Tables Enhancements / Corrections Staging tables = On the ‘Migration Object Details’ page, the links in the column ‘Description’ has been removed, and you can use the links in the column ‘Structure’ to display staging table documentation. = Previously, the order of staging table fields was different to staging table details screen and the staging table documentation. The order of the fields is consistent now.SAP S/4HANA Migration Cockpit New App: Data Migration Status Released 1805 Data Migration Status : Features Ready to use roar station Data Migration Ready mace status Log No ood to store & isto he Log gate Your Data Export to Exc! uc and E560 of faled records evaluation Status of every source record Svat data vlitation OQ wv [= a Direct Navigation Fle App I> Avplication Holp for Data Migration StatusDevelopment News 1808 / 1809SAP S/4HANA Migration Cockpit Preconfigured Migration Objects SAP S/4HANA 4P Shipment Every edition Actual no. £88 objects (1808) ‘Avaliable Macaton Objects S#H Cloud 1208 object ei . r SS —hCUrrti Xeeptonl case ~ Materia pice eh fo bal + Purchase scheduling agreement Sippten os new og a 3 + Purchasing contact + TRI - Bank gurantee + Purchasing nfo record extend existing record = ‘TRM- Commercial paper + Purchasing inf record wth condtons = TRM- Deposit nates » oqupat eno sate gape + TRM- Foren exchange spt ford vanaacton = OM selected set + TRI. Foreign exchange swap -convact + QM selected set code + TRM- FX option + Realestate contact + TR nerest ate instrument + Routing + TRI Interest ate ap + Sales convact += TRM-Positon Value Sales order only open SO) VC - Dependency net SEPA mandate + Vo~ Object Dependency scien eons STII FS Available Migration Objects S4H Cloud 1808 2Preconfigured Business Objects (On-Premise 1809) — Part 1 Migration of Master and Transactional Data ‘Atty Price (restricted) Atty Type Bank ‘Bank account balance Batch ( Batch is unique at mater eve) Batch (f Batch is unique at plant evel) ‘cash memo record Ccharactristic case Condition contract content Cost center customer ‘(Customer (Geprecsted) Customer extond existing record by new og levels Customer materia Equipment Equpment ask st Exchange rate FI ~Accounts payable open tem FI Accounts recatvabe open tam F1~GIL account balance and openine item Fed asset (rc. balances and tansacions) Funetionalocation Gib account ‘General ta9k tat Inspection method Inspection plan Intemal order (ested) Se ee Lin Nw tan SAP SHANA 1800 IS Auailable Migration Objects S4H OP 1809 eS Maintenance tem Maintenance plan Master inspection characterises Material Material BOM Material elaeseation| Material consumption Material - extend existing record by new org ove Material inspection sting Mate inventory balance Material ong text Material wade assiicaon Pricing condtion (genera) cing condition (puchasiog) Pricing condition (sles) Prasuction versionPreconfigured Business Objects (On-Premise 1809) — Part 2 Migration of Master and Transactional Data + Profit canter | Supplier ~ extn existing recor by naw org evs (deprecats) + Purchase order only en PO) = Work canter + [Purchase schedutng agreement) - (Ve = Vartan configuration prefle | + Purchasing contact + Work canter + Purchasing info record with condtons + QMPM catalog code grountcode + QM selected sot + QM selected sat cose + Routing + Sales order only open $0) + Source ist + Supper ~ Supplier (deprecated) + Supplier - extend exiting record by new or avesDevelopment News 1809Migration Object Modeler Structure Mapping and Field Mapping Screen = Change order of structures on structure mapping and field mapping screen = The position of the source structures and target structures can be switched via menu entry Settings > Switch Position of Structures = User selection is persistedMigration Object’ Modeler 1809 Field Mapping / Rule Assignment — New Rule Proposals [1] Sone New expert function available to have an automated rule proposal for the target fields in the field mapping screen. This feature is can support you with creating your own migration objects. Important: if you change the rules in delivered migration objects based on the rule proposals, SAP cannot provide support for such migration objects, i ar of on nae Bi sor ofrecocoate of) FEET [lent ortega ft) 280) i ur of ecru eyMigration Object Modeler 1809 le Field Mapping / Rule Assignment — New Rule Proposals [2] Es = On the rule proposals screen, you can view whether rule proposals exist for the fields in the target structure. * Matching rule proposals are based on domain and data element assignments in the respective rule. ® In addition, if a field in a target structure has the same name as the field in the source structure, the system proposes a MOVE rule. Documentation on Rule Proposal Screen (CE Estee de Propose 18 Rue roosts Tagetsoucure Flame ‘ute fe ooo ee Pras PME VOtecOTOLLDGARCONTROLNGAREA OTROS) CVT SOIRELS). A SowLuwunGe UNG ors) B__rocosreomreust _cosrcarren evr x0sT15) The following status values are possible: = Exactly one rule proposal exists (green LED icon) = More than one rule proposal exists (yellow LED icon) + If more than one rule proposal exists for a field, you can view them in the dropdown list.Migration Object Modeler 1809 Field Mapping / Rule Assignment — New Rule Proposals [3] COU GI erase sine) Fg vox contnoucan COUTOUMGAREA shoouwveusce uscd @___Tocosremmreust _cosTemren fermeowss) a aos) formeosnus) avr xostus) The system displays the information about where the field based rule was created in brackets: = (8): Subproject-Specific; the rule was created at subproject level and can be used by all migration objects in that subproject. = (M): Migration Object-Specific; the rule was created at migration object level and can only be used by that migration object.Migration Object Modeler Enhancements Field mapping = Amapping check can be performed, which lists incomplete mappings (i.e. missing parameters) as errors as well as source fields which haven't been assigned to any target field yet as warnings. CEE) HW ers J pees A | Be Target Structures + oP Create One or More Cost Centers < No)Migration Object Modeler Steps to Execute a Simulation Run for debugging — File approach Simulate Import: 1. Choose the migration object 2. Select the filled template Excel-XML file 3. Choose Execute (F8) Note: The file that you upload is only stored temporarily for the duration of the simulation, and is then deleted from the system, Documentation on Simulation / Debugging Simulate Import of Data from Fle e ¥ or aHoF eave RECO.Migration Object Modeler Breakpoints for debugging — File approach Breakpoint Before Conversion If you choose this option, a breakpoint is set before the conversion takes place. DaioF Breakpoint Before Posting If you choose this option, a breakpoint is set before the data is written to the target systemMigration Object Modeler file Debug in target system — File approach ae Option to Save data if Error Occurs EEE — If you choose this option the system will then save | S™wivte2meertoroutenomrie the relevant information about the first erroneous Debug Error from the menu.Migration Object Modeler Delete Debugging Run - File approach You can delete the simulation runs from the target system when you are finished by choosing Goto -> Delete Run from the menu. 5 aniosMigration Object Modeler 1809 Simulate Import for Staging Migration Objects Report DMC_MC_SIMULATE_IMPORT_STAGING (available in SAP Note 2665339 ) Import Simulation for Staging Migration Object arn oct urbe oF fr Suton You can choose one of the following options to decide, which entries should be taken for the simulation: + Select All Entries + Select Max. Number of Entries (random) + Select Specific Entries (There is currently a technical restriction, that the specific selection is not case sensitive)SAP S/4HANA Migration Cockpit and Migration Object Modeler Report DMC_NOTE_ANALYZER lists all notes from the Central SAP Note (Migration cockpit tool - not content), which have not been imported. Analyze SAP Notes 0 {49 Lnthap edo (2.1 pte Seer ae 2 Downe 0207) ‘Automatically filled depending on system releaseSAP S/4HANA Migration CockpitSAP S/4HANA Migration Cockpit - Outlook Extract Legacy TT] Data Provisioning poe Staging’ Planned! SAP S/4HANA’ SAP S/4HANA Migration Cockpit Process Data toa lSAP S/4HANA Migration Cockpit Transfer Data Directly from SAP Source System (planned for 1809 FPS01) lable migration objects relevant for the selected scenarioSAP S/4HANA Migration Cockpit Transfer Data Directly from SAP Source System (planned 1809 FPS01) re Tn Finance Migration to Si | ed ‘The cockpit guides you through the various steps of the data migration, but you can also flexibly choose which steps you want to do next (select, simulate, migrate).SAP S/4HANA Migration Cockpit Transfer Data Directly from SAP Source System (planned for 1809 FPS01) Tae Tomas You can maintain value mappings to transform values from the source system to the target systemSAP S/4HANA Migration CockpitSAP S/4HANA Migration Cockpit SAP Notes and KBAs Collective SAP Notes for Pre-filled migration Migration Content templates CA.GTF-MIG \w/ sample data and PDF that explains the data 2538700 Collective SAP Note and FAQ for 2470789 ‘SAP S/4HANA Migration Cockpit ‘SAP S/4HANA Migration Cockpit {Cloud) (Cloud) - Sample data migration templates 2537549 Collective SAP Note and FAQ for Currently only available SAP S/4HANA Migration Cockpit for SAP S/4HANA Cloud (on premise Central SAP Notes for Migration Cockpit Tool CA-LT-MC 2504002 Migration Cockpit & SLT on SHAR Ore Poems Eaton a = 2475034 Migration Cockpit & SLT on SIAHANA On-Premise Editon 2376533 Migration Cockpit & SLT on SIHANA On-Premise Eaton a 761Further Information LEARNING = Click Through Demos (based on 1610 PFS02) * Introducing SAP S/4HANA Migration Cockpit ‘+ SAP S/GHANA Migration Cockpit using staging tables * Working on a migration object withthe migration object modeler * Adding fields to a migration obiect * Creating a new migration object * Overview page including a try.it-yourself and the PDFs Open SAPcourse Data Migration to SAP S/4HANA http://help. sap com/s4hana pp SMHANA Cloud SAP S/4HANA Cloud 1802Further Information > High Level Video ‘SAP S/4HANA Migration Cockpit > Powerpoint presentation ‘SAP S/4HANA Migration Cockpit - Migrate your data to SAP S/4HANA, > Technical Brief Migrate our Data to SAP S/4HANA Quickly, Safely and Cost-Etfectively > Video: Migration Cockpit hitip://bit.ly/2Atby5K > Video: Migration Object Modeler http://bit.1y/2BHmUHm > SAP S/4HANA Community _https://www.sap.com/community/topic/s4hana. htm! > Blog: Migration Cockpit https:/iblogs sap.com/2017/07/05/starter-blog-for-sap-s4hana-migration-cockpit/ > Help Portal ‘SAP S/4HANA Help Portal “SD Orcontact SAP_S4HANA Migration Gockpit@sap.com directly