Demo Script for SAP S/4HANA 2023 FPS00 - 2022 FPS01 Fully-Activated Appliance: Migration Cockpit - Staging Tables GL Accounts
SAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-Activated Appliance
December 2023
English
PUBLIC
SAP 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 staging
tables
Demo Guide
December 2023
English
PUBLIC
SAP 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 staging
tables
Demo Guide
2
Table of Contents
1 Where Can This Script Be Used? 3
2 Demo Story: SAP S/4HANA Migration Cockpit (Staging Tables Approach) - Migrating G/L Accounts 4
2.1 Start the SAP S/4HANA Migration Cockpit 5
2.2 Create a migration project 6
2.3 Check and fill the Staging Tables 8
2.3.1 Fill the Staging Tables with XML file 11
2.3.2 Fill the Staging Tables with CSV file 15
2.3.3 Fill the Staging Tables directly with a provided report 16
2.4 Prepare staging tables 19
2.5 Maintain mapping tasks 21
2.6 Simulate the migration 25
2.7 Execute the migration to SAP S/4HANA 27
2.8 Validate the imported data 29
2.9 Summary 32
Document History
Revision Date Change
1.0 <2020-06-19> Release for customer
2.0 <2020-12-03> Release for customer
3.0 <2021-03-31> Release for customer
4.0 <2021-07-15> Release for customer
5.0 <2021-12-06> Release for customer
6.0 <2022-04-26> Release for customer
7.0 <2022-07-14> Release for customer
8.0 <2023-04-20> Release for customer
9.0 <2023-07-05> Release for customer
10.0 <2023-12-05> Release for customer S/4HANA 2023 SP00
Table of Contents
1 Where Can This Script Be Used? 3
2 Demo Story: SAP S/4HANA Migration Cockpit (Staging Tables Approach) - Migrating G/L Accounts 4
2.1 Start the SAP S/4HANA Migration Cockpit 5
2.2 Create a migration project 6
2.3 Check and fill the Staging Tables 8
2.3.1 Fill the Staging Tables with XML file 11
2.3.2 Fill the Staging Tables with CSV file 15
2.3.3 Fill the Staging Tables directly with a provided report 16
2.4 Prepare staging tables 19
2.5 Maintain mapping tasks 21
2.6 Simulate the migration 25
2.7 Execute the migration to SAP S/4HANA 27
2.8 Validate the imported data 29
2.9 Summary 32
Document History
Revision Date Change
1.0 <2020-06-19> Release for customer
2.0 <2020-12-03> Release for customer
3.0 <2021-03-31> Release for customer
4.0 <2021-07-15> Release for customer
5.0 <2021-12-06> Release for customer
6.0 <2022-04-26> Release for customer
7.0 <2022-07-14> Release for customer
8.0 <2023-04-20> Release for customer
9.0 <2023-07-05> Release for customer
10.0 <2023-12-05> Release for customer S/4HANA 2023 SP00
3
1 Where Can This Script Be Used?
This demo script has been written for usage with the SAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-Activated
Appliance (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-2
hours from https://cal.sap.com
2. 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 information
about necessary preparations, especially any post-deployment steps to ensure the full functionality of your appliance.
These steps are covered in sections;
B) General Remarks
C) Post-deployment Steps
D) Log-on to the system
Besides this, you will also find links to all demo scripts on this page.
1 Where Can This Script Be Used?
This demo script has been written for usage with the SAP S/4HANA 2023 & 2022 FPS02/FPS01 Fully-Activated
Appliance (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-2
hours from https://cal.sap.com
2. 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 information
about necessary preparations, especially any post-deployment steps to ensure the full functionality of your appliance.
These steps are covered in sections;
B) General Remarks
C) Post-deployment Steps
D) Log-on to the system
Besides this, you will also find links to all demo scripts on this page.
4
2 Demo Story: SAP S/4HANA Migration Cockpit
(Staging Tables Approach) - Migrating G/L
Accounts
When implementing your SAP S/4HANA solution, you can migrate your master data and business data from SAP
systems 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 Tables
The SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your
project 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 staging
tables with data. Alternatively, you can fill the staging tables by using your preferred tools (for example SAP
Data 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 will
generate 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 a
remote SAP HANA system and the SAP S/4HANA migration cockpit will generate the staging tables
there.
2. Migrate Data Directly from SAP System
An RFC connection connects the SAP S/4HANA migration cockpit to the SAP ERP source system. The SAP
S/4HANA migration cockpit selects data from the source system by using specific criteria. For example, if you
are using the migration scenario SAP ERP to SAP S/4HANA, then the SAP S/4HANA migration cockpit selects
data using company codes (you specify the relevant company codes when creating a project). Note the
following 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_DM
Link SAP S/4HANA Cloud: https://help.sap.com/S4_CE_DM
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.
For your convenience, we have put filled files with some sample migration data on the remote desktop of the
appliance (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 look
a bit different due to different Fiori themes used. You can toggle the Fiori themes under User profile
→ Settings.
2 Demo Story: SAP S/4HANA Migration Cockpit
(Staging Tables Approach) - Migrating G/L
Accounts
When implementing your SAP S/4HANA solution, you can migrate your master data and business data from SAP
systems 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 Tables
The SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your
project 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 staging
tables with data. Alternatively, you can fill the staging tables by using your preferred tools (for example SAP
Data 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 will
generate 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 a
remote SAP HANA system and the SAP S/4HANA migration cockpit will generate the staging tables
there.
2. Migrate Data Directly from SAP System
An RFC connection connects the SAP S/4HANA migration cockpit to the SAP ERP source system. The SAP
S/4HANA migration cockpit selects data from the source system by using specific criteria. For example, if you
are using the migration scenario SAP ERP to SAP S/4HANA, then the SAP S/4HANA migration cockpit selects
data using company codes (you specify the relevant company codes when creating a project). Note the
following 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_DM
Link SAP S/4HANA Cloud: https://help.sap.com/S4_CE_DM
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.
For your convenience, we have put filled files with some sample migration data on the remote desktop of the
appliance (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 look
a bit different due to different Fiori themes used. You can toggle the Fiori themes under User profile
→ Settings.