Demo Script for SAP S/4HANA 2023 FPS00 - 2022 FPS01 Fully-Activated Appliance: Migration Cockpit - Staging Tables GL Accounts

In the following exercises you will migrate G/L account data to SAP S/4HANA. We will use the Local SAP S/4HANA Database Schema. To populate the staging tables we will use a program to generate example data. In real projects, this task is done by the customer or partner. Download the Document

SAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-Activated ApplianceDecember 2023EnglishPUBLICSAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-Activated Appliance:SAP S/4HANA Migration Cockpit Migrate Data Using Staging Tables:Migrating G/L Accounts using XML, or CSV, or fill data directly in stagingtablesDemo Guide
2Table of Contents1 Where Can This Script Be Used? 32 Demo Story: SAP S/4HANA Migration Cockpit (Staging Tables Approach) - Migrating G/L Accounts 42.1 Start the SAP S/4HANA Migration Cockpit 52.2 Create a migration project 62.3 Check and fill the Staging Tables 82.3.1 Fill the Staging Tables with XML file 112.3.2 Fill the Staging Tables with CSV file 152.3.3 Fill the Staging Tables directly with a provided report 162.4 Prepare staging tables 192.5 Maintain mapping tasks 212.6 Simulate the migration 252.7 Execute the migration to SAP S/4HANA 272.8 Validate the imported data 292.9 Summary 32Document HistoryRevision Date Change1.0 <2020-06-19> Release for customer2.0 <2020-12-03> Release for customer3.0 <2021-03-31> Release for customer4.0 <2021-07-15> Release for customer5.0 <2021-12-06> Release for customer6.0 <2022-04-26> Release for customer7.0 <2022-07-14> Release for customer8.0 <2023-04-20> Release for customer9.0 <2023-07-05> Release for customer10.0 <2023-12-05> Release for customer S/4HANA 2023 SP00
31 Where Can This Script Be Used?This demo script has been written for usage with the SAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-ActivatedAppliance (in short “appliance” in this script), hence you will need such an appliance to make use of this guide.The appliance can be brought up in two ways, and the demo scenario in this script is largely the same for both:1. Via SAP Cloud Appliance Library (hosted on cloud providers)You need a cloud provider account at AWS, MS Azure, or GCP. With this, you can deploy the appliance within 1-2hours from https://cal.sap.com2. Via installing it on your own on-premise hardware.You need to provide your own hardware, and order & install the appliance as explained in SAP Note 2041140.If you are new to the SAP S/4HANA Fully-Activated Appliance, introductory information can be found here:https://blogs.sap.com/2018/12/12/sap-s4hana-fully-activated-appliance-create-your-sap-s4hana-1809-system-in-a-fraction-of-the-usual-setup-time/Important:Before you start your demo, please read SAP S/4HANA Fully-Activated Appliance: Demo Scripts for informationabout necessary preparations, especially any post-deployment steps to ensure the full functionality of your appliance.These steps are covered in sections;B) General RemarksC) Post-deployment StepsD) Log-on to the systemBesides this, you will also find links to all demo scripts on this page.
42 Demo Story: SAP S/4HANA Migration Cockpit(Staging Tables Approach) - Migrating G/LAccountsWhen implementing your SAP S/4HANA solution, you can migrate your master data and business data from SAPsystems and non-SAP systems to SAP S/4HANA. To do this, you use the SAP S/4HANA migration cockpit.There are two migration approaches available:1. Migrate Data Using Staging TablesThe SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for yourproject and migrates data from these staging tables to the target SAP S/4HANA system.Template files are provided for every migration object. You can use these template files to fill the stagingtables with data. Alternatively, you can fill the staging tables by using your preferred tools (for example SAPData Services).There are two options where the staging tables can be located: If you use the option Local SAP S/4HANA Database Schema, the SAP S/4HANA migration cockpit willgenerate the staging tables in the local ABAP schema of the SAP S/4HANA system. If you use the option Remote SAP HANA Database Schema, you specify the relevant connection to aremote SAP HANA system and the SAP S/4HANA migration cockpit will generate the staging tablesthere.2. Migrate Data Directly from SAP SystemAn RFC connection connects the SAP S/4HANA migration cockpit to the SAP ERP source system. The SAPS/4HANA migration cockpit selects data from the source system by using specific criteria. For example, if youare using the migration scenario SAP ERP to SAP S/4HANA, then the SAP S/4HANA migration cockpit selectsdata using company codes (you specify the relevant company codes when creating a project). Note thefollowing information for the migration scenarios:More information on the SAP S/4HANA Migration Cockpit can be found on our central landing page:Link SAP S/4HANA: https://help.sap.com/S4_OP_DMLink SAP S/4HANA Cloud: https://help.sap.com/S4_CE_DMIn the following exercises you will migrate G/L account data to SAP S/4HANA. We will use the Local SAP S/4HANADatabase Schema. To populate the staging tables, we will use a program to generate example data. In real projects,this task is done by the customer or partner.For your convenience, we have put filled files with some sample migration data on the remote desktop of theappliance (see chapter 2.3). We recommend using this file, but you can also fill an empty file manually.Note:Depending on the release / feature package stack (FPS) that you are using, the screens might looka bit different due to different Fiori themes used. You can toggle the Fiori themes under User profile Settings.