Demo Script for SAP S/4HANA 2023 FPS00 - 2022 FPS01 Fully-Activated Appliance: Migration Cockpit – Staging Tables for Product Master Data
Public
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 Product Master Data
Demo Guide
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 Product Master Data
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 Product 4
2.1 Start the SAP S/4HANA Migration Cockpit 5
2.2 Create a migration project 6
2.3 Download migration template and prepare data 9
2.4 Upload migration template and transfer data to staging tables 16
2.5 Prepare staging tables 20
2.6 Maintain mapping tasks 21
2.7 Simulate the migration 26
2.8 Execute the migration to SAP S/4HANA 28
2.9 Validate the imported data using SAP S/4HANA Business Apps 30
2.10 Summary 32
Document History
Revision Date Change
1.0 June 2020 Release for Customer 1909 FPS02
2.0 December 2020 Release for customer 2020 FPS00
3.0 April 2021 Release for customer 2020 FPS01
4.0 July 2021 Release for customer 2020 FPS02
5.0 December 2021 Release for customer 2021 FPS00
6.0 April 2022 Release for customer 2021 FPS01
7.0 July 2022 Release for customer 2021 FPS02
8.0 April 2023 Release for customer 2022 FPS01
9.0 July 2023 Release for customer 2022 FPS02
10.0 December 2023 Release for customer 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 Product 4
2.1 Start the SAP S/4HANA Migration Cockpit 5
2.2 Create a migration project 6
2.3 Download migration template and prepare data 9
2.4 Upload migration template and transfer data to staging tables 16
2.5 Prepare staging tables 20
2.6 Maintain mapping tasks 21
2.7 Simulate the migration 26
2.8 Execute the migration to SAP S/4HANA 28
2.9 Validate the imported data using SAP S/4HANA Business Apps 30
2.10 Summary 32
Document History
Revision Date Change
1.0 June 2020 Release for Customer 1909 FPS02
2.0 December 2020 Release for customer 2020 FPS00
3.0 April 2021 Release for customer 2020 FPS01
4.0 July 2021 Release for customer 2020 FPS02
5.0 December 2021 Release for customer 2021 FPS00
6.0 April 2022 Release for customer 2021 FPS01
7.0 July 2022 Release for customer 2021 FPS02
8.0 April 2023 Release for customer 2022 FPS01
9.0 July 2023 Release for customer 2022 FPS02
10.0 December 2023 Release for customer 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 > Solutions > SAP S/4HANA 20223 or 2022 (FPS02 / FPS01) Fully-Activated
Appliance.
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.
Microsoft Excel:
The Remote Desktop does not contain Microsoft Excel. As we need to fill in the Source Data for Product.ZIP containing
CSV files with data, we need to use Excel from our local computer. You will be guided in the exercise when this is needed.
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 > Solutions > SAP S/4HANA 20223 or 2022 (FPS02 / FPS01) Fully-Activated
Appliance.
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.
Microsoft Excel:
The Remote Desktop does not contain Microsoft Excel. As we need to fill in the Source Data for Product.ZIP containing
CSV files with data, we need to use Excel from our local computer. You will be guided in the exercise when this is needed.
4
2 Demo Story: SAP S/4HANA Migration Cockpit
(Staging Tables Approach) - Migrating Product
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).
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 this demo exercise, we’ll walk you through the approach migrate data using staging tables. Therefore, we us the
migration object Product (master data) as an example. To populate the staging tables, we will use pre-delivered template
files (CSV format) that need to be filled with the actual data to be migrated.
For your convenience, we have put a filled CSV file 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 as described in
chapter 2.3.
For your project, consider that the size limit for each file uploaded to SAP S/4HANA Migration Cockpit is 160 MB. This
parameter can be changed if required – see detailed info in our Help Portal (link).
Exercise Description:
1. Start with the SAP S/4HANA migration cockpit
2. Create a migration project (migration object Product)
3. Download CSV migration template and prepare data (incl. maintaining mapping tasks for fixed
value and control parameter)
4. Upload migration template and transfer data to staging tables
5. Prepare staging tables
6. Maintain mapping tasks
7. Simulate the migration
8. Execute the migration to SAP S/4HANA
9. Validate the imported data using SAP S/4HANA Business Apps
2 Demo Story: SAP S/4HANA Migration Cockpit
(Staging Tables Approach) - Migrating Product
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).
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 this demo exercise, we’ll walk you through the approach migrate data using staging tables. Therefore, we us the
migration object Product (master data) as an example. To populate the staging tables, we will use pre-delivered template
files (CSV format) that need to be filled with the actual data to be migrated.
For your convenience, we have put a filled CSV file 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 as described in
chapter 2.3.
For your project, consider that the size limit for each file uploaded to SAP S/4HANA Migration Cockpit is 160 MB. This
parameter can be changed if required – see detailed info in our Help Portal (link).
Exercise Description:
1. Start with the SAP S/4HANA migration cockpit
2. Create a migration project (migration object Product)
3. Download CSV migration template and prepare data (incl. maintaining mapping tasks for fixed
value and control parameter)
4. Upload migration template and transfer data to staging tables
5. Prepare staging tables
6. Maintain mapping tasks
7. Simulate the migration
8. Execute the migration to SAP S/4HANA
9. Validate the imported data using SAP S/4HANA Business Apps
5
2.1 Start the SAP S/4HANA Migration Cockpit
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.
In this process step, you start the SAP S/4HANA migration cockpit.
Explanation Screenshot:
Use the following logon
data in the Fiori
Launchpad:
1. Enter User: S4H_MG
2. Enter PW: Welcome1
Client 100 is already
Suggested.
3. Click Log On .
Click “Data Migration” (tick
the tab in the header).
To access the SAP
S/4HANA migration
cockpit, choose the Migrate
Your Data – Migration
Cockpit app
2.1 Start the SAP S/4HANA Migration Cockpit
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.
In this process step, you start the SAP S/4HANA migration cockpit.
Explanation Screenshot:
Use the following logon
data in the Fiori
Launchpad:
1. Enter User: S4H_MG
2. Enter PW: Welcome1
Client 100 is already
Suggested.
3. Click Log On .
Click “Data Migration” (tick
the tab in the header).
To access the SAP
S/4HANA migration
cockpit, choose the Migrate
Your Data – Migration
Cockpit app