Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 1

Test Script PUBLIC

SAP S/4HANA Cloud - 13-04-20

Data Migration to SAP S/4HANA from File (BH5)

Table of Contents

1 Purpose 3

2 Prerequisites 4
2.1 System Access 4
2.2 Roles 4
2.2.1 Technical Roles 4
2.2.2 Business Roles 5

3 Migration Objects for SAP S/4HANA Cloud 6

4 Business Conditions 7

5 Preliminary Steps 8
5.1 Add Business Roles to the Data Migration User 8

6 Overview Table 9

7 Test Procedures 10
7.1 Start the SAP S/4HANA Migration Cockpit 10
7.2 Create Migration Project 11
7.3 Open Migration Object 12
7.4 Download Migration Template 13
7.5 Prepare Test Data 15
7.6 Upload Migration Template and Verify Data 17
7.7 Transfer Migration Template Data 20
7.8 Check Data Migration Status 23
7.9 Validate Imported Data using SAP S/4HANA Business Apps 26

8 Appendix 27
8.1 General Topics and Limitations 27
8.1.1 When to create a new project? 27
8.1.2 Dependent Migration Objects 27
8.1.3 Migration Template File Size 27
8.1.4 Convert Values 30
8.1.5 Unit of Measure Conversion 31
8.1.6 ALE/IDoc Distribution After Data Migration 32
8.2 Financials 32
8.2.1 Document Types for Data Migration 32
8.2.2 Document Date 32
8.2.3 Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1) 32
8.2.4 Value Date 33
8.2.5 Transfer Booking Account 34
8.2.6 Migrate Historical Balances 34
8.2.7 Fixed Assets: Available Fields per Asset Class 34
8.2.8 Migrate Financial Plan Data 35
8.3 Logistics 35
8.3.1 Advanced Variant Configuration 35
8.3.2 How to Handle Cross-Plant Material Status and Plant-Specific Material Status 36

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 2
1 Purpose

SAP S/4HANA Cloud customers can take advantage of a template-based migration approach built into SAP S/4HANA Cloud. SAP S/4HANA Cloud supports a limited set of data migration objects,
with support for additional objects planned for later inclusion.
Note SAP S/4HANA refers to the default on-premise suite on the SAP HANA platform, SAP S/4HANA Cloud refers to our cloud suite on SAP Cloud Platform.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.
Data protection legislation may require that personal data is deleted once the data has served its originally defined purpose and is also no longer subject to additional legal data retention
requirements. If data protection legislation is applicable in your case, then migrating personal data which should have been deleted could be interpreted as the processing of personal data without any
legally justified purpose.
Migration objects are built for initial migration of your data to your SAP S/4HANA or SAP S/4HANA Cloud system. This means that you can create data with a migration object, but you can't
change or update existing data with it.
For some migration objects there are "Extend" migration objects available, that you can use to extend existing data to other organizational levels. If you want to change or update existing data, use
the respective maintenance apps (available for all business objects) or mass processing apps (these are only available for selected business objects). Please note that such apps fall outwith the
responsibility of data migration development.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 3
2 Prerequisites

This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.

2.1 System Access

System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.

2.2 Roles

2.2.1 Technical Roles

Required Standard Role
Use the following standard role to access the Migrate Your Data - Migration Cockpit, Data Migration Status (F3280), and Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1) apps:

ID Name
SAP_BR_CONFIG_EXPERT_DATA_MI Configuration Expert - Data Migration
G
Key Mapping
Use the following standard role to access the Search Key Mapping (MDG_BS_WD_ANALYSE_IDM) and Manage Key Mapping (MDG_BS_WD_ID_MATCH_SERVICE) apps. You can use these
apps to check the key mappings that were entered in the Unified Key Mapping Service (UKMS) during the data load. Currently, UKMS supports the following migration objects:
● Customer
● Supplier
● FI-CA Contract partner
● FI-CA Contract account

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 4
● Material (deprecated)
● Product

ID Name
SAP_BR_ADMINISTRATOR_DATA_RE Administrator - Data Replication
PL

2.2.2 Business Roles

You can find an extensive table listing all migration objects available for SAP S/4HANA Cloud, as well as the required business roles, in the SAP S/4HANA Cloud product assistance.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 5
3 Migration Objects for SAP S/4HANA Cloud

You can find an extensive table listing all migration objects available for SAP S/4HANA Cloud, together with their respective migration object documentation, in the SAP S/4HANA Cloud product
assistance.
The data migration object documentation was moved to the SAP Help Portal with SAP S/4HANA Cloud 1905. If you encounter issues opening the documentation from the Migration Cockpit, refer
to SAP Note 2667053 and SAP Knowledge Base Article 2793425.
Find information on dependent migration objects in the Dependent Migration Objects [page ] 25 section. To create objects of a configuration model in SAP S/4HANA Cloud, see Advanced Variant
Configuration [page ] 32 section.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 6
4 Business Conditions

Before this scope item can be tested, the following business conditions to be met:

Business Condition
Content is activated.
Org. structures and additional settings are made.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 7
5 Preliminary Steps

Use

In these steps, you set up the necessary user settings for migrating your data.

5.1 Add Business Roles to the Data Migration User

Use
In this step, you assign the roles, which are necessary for migrating your data, to the data migration user. You can find a list of business roles per migration object here.
Procedure
1. Access the SAP Fiori screen in SAP S/4HANA Cloud.
1. On the Home screen, choose the Maintain Business Users (F1303) tile:
2. Enter the User Name given by your system administrator.

Field Name Description User Action and Values

User Name Name of the Data Migration user User name
3. Choose Go.
4. Select the user in the Users list.
5. Choose Edit.
6. Choose Add Business Roles.
7. In the Add Business Roles list, enter the needed business role into the Search field and press Enter.
8. Select the needed business roles and choose OK.
9. Choose Save.
10. Go back to the Home screen.
11. Go back to the previous screen.
Result
You have added the necessary roles for the specific data migration object to load.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 8
6 Overview Table

This scope item consists of several process steps provided in the table below.

Process Step UI Type Business Condition Expected Results

Start the SAP S/4HANA SAP Fiori launchpad This section describes how you start the SAP S/4HANA migration The migration cockpit is displayed.
Migration Cockpit [page ] 10 cockpit.
Create Migration Project [page ] Migration cockpit (Web This section describes how you create a migration project in the A migration project is created.
11 Dynpro via SAP Fiori migration cockpit.
launchpad)
Open Migration Object [page ] Migration cockpit (Web This section describes how you open a migration object in the A migration object is opened.
12 Dynpro via SAP Fiori migration project.
launchpad)
Download Migration Template Migration cockpit (Web This section describes how you download a migration template to The Microsoft Excel XML Spreadsheet 2003 template
[page ] 13 Dynpro via SAP Fiori facilitate the data transfer from Microsoft Excel spreadsheet is downloaded.
launchpad) templates to SAP S/4HANA.
Prepare Test Data [page ] 14 Microsoft Excel This section describes how you enter test data for migration to SAP Test data is entered into the Microsoft Excel XML
S/4HANA into the migration template. Spreadsheet 2003 template.
Upload Migration Template and Migration cockpit (Web This section describes how you upload the migration template and The migration template is uploaded, entries are
Verify Data [page ] 17 Dynpro via SAP Fiori verify its data. consistent, and the file does not contain any empty
launchpad) records.
Transfer Migration Template Migration cockpit (Web This section describes how you import the data from your migration The data is transferred from the Microsoft Excel XML
Data [page ] 19 Dynpro via SAP Fiori template into the SAP S/4HANA target system. Spreadsheet 2003 template to the SAP S/4HANA
launchpad) system.
Check Data Migration Status Data Migration Status app This section describes how you use the Data Migration Status You are up-to-date with the status of your migration
[page ] 22 (F3280) app to check the status of your migration projects and projects and objects. Necessary changes in migration
objects. projects can then be made.
Validate Imported Data using SAP Fiori launchpad This section describes how you validate completeness and All data from the Microsoft Excel XML Spreadsheet
SAP S/4HANA Business Apps correctness of the migrated data in the target SAP S/4HANA 2003 template can be found in the corresponding SAP
[page ] 24 system using corresponding business functions. S/4HANA business functions.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 9
7 Test Procedures

This section describes test procedures for each process step that belongs to this scope item.

7.1 Start the SAP S/4HANA Migration Cockpit

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you start the SAP S/4HANA migration cockpit.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Start SAP Fiori launchpad Log on to your SAP S/4HANA Cloud system. The Home page appears.
2 Open Migration Cockpit Choose the Migrate Your Data - Migration Cockpit tile.

Note For more information on the SAP S/4HANA Cloud Migration Cockpit, see the product assistance on the SAP Help Portal.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 10
Result

The Migrate Your Data home screen appears.

7.2 Create Migration Project

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you create a migration project in the migration cockpit.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1. Create Migration Project Choose Create on the Migrate Your Data home screen. The Create Migration Project dialog window
appears.
2. Add Name Make the required entry in Create Migration Project dialog
window:
● Name: Name of your migration project.
● Transfer Options: Transfer Data from File.
After making the required entries, choose Create.
Data Migration to SAP S/4HANA from File (BH5) PUBLIC
Purpose Error: Reference source not found 11
Note The system automatically generates a mass transfer ID that is used for your project. If required, you can enter an existing mass transfer ID. For example, if you want to use the same project
settings in a different system, you must enter a mass transfer ID that is unique for the participating systems. In this way, you can manually transport settings from a quality system to a production
system. For more information, see the application help for the migration cockpit. You can also generate a different mass transfer ID by choosing Generate New Mass Transfer ID. The system
generates the next available mass transfer ID.
After an SAP S/4HANA Cloud release upgrade, any new migration objects won’t get added to existing migration projects. To be able to use new migration objects, you need to create a new
migration project. If there are still migration objects missing after creating a new migration project, please see SAP Note 2538700 for further information.

Result

You have created a customer migration project. The project including all active migration objects is copied from the SAP standard project and is displayed on the screen. All migration objects are in
migration status Not Started.

7.3 Open Migration Object

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you open a migration object in the migration project. Find information on dependent migration objects in the Dependent Migration Objects [page ] 25 section.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 12
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1. Open Migration Choose the migration project you previously created in section Create Migration Project The Migration Project overview appears.
Project [page ] 11 on the Migrate Your Data home screen.
2. Optional: Filter on On the Migration Objects tab, select the Migration Status column and choose one of the The migration objects are filtered as per status.
Migration Status two statuses In Process or Not Started. You can find the different statuses at the bottom of Only objects with the selected status are
the context menu. displayed.
3. Open Migration On the Migration Objects tab, select the table row containing your migration object.
Object Once the confirm dialog window appears, choose OK to copy the selected migration
object to your customer project.

Result

The migration object has been copied from the SAP standard migration object into a customer migration object and the Migration Object Details screen appears.

7.4 Download Migration Template

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 13
Use

This section describes how you download a migration template to facilitate the data transfer from Microsoft Excel spreadsheet templates to SAP S/4HANA.

Procedure

Test Step # Test Step Name Instruction Expected Result Pass / Fail /
Comment
1. Download Choose Download Template on the Source Files tab of the Migration The migration template is downloaded and saved on
Template Object overview. your local PC.
The template will automatically be downloaded.

Note Depending on your internet browser and its version, a download dialog of the browser might appear. If it appears, choose Save to store the migration template on your local PC. If you are not
prompted to save the file, the migration template will automatically be stored in your default download folder.

Result

The Microsoft Excel XML Spreadsheet 2003 template is downloaded and saved on your local PC.
Note Depending on your internet browser, you might have to add the file extension .xml to your downloaded file.

7.5 Prepare Test Data

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 14
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you enter test data for migration to SAP S/4HANA into the migration template.

Prerequisite

In the Microsoft Excel file navigate to File > Options > Advanced . Under When calculating this workbook:, ensure that Set precision as displayed is selected.

Important Information

Caution The workbook and its sheets are protected. Never change the structure and don’t make any changes on the format of the migration template: Don’t delete, rename, or reorder any sheet in the
XML file, don’t change the cell formatting, don’t use formulas, and don’t hide, remove, or reorder any column in the XML file. Moreover, don't change data by Find and Replace function. If you
change data by Find and Replace you may also accidentally change the field names and corrupt the XML structure. A modified migration template will cause errors when trying to load into the
migration cockpit or will cause errors during the data migration process.
Caution When copying data into the migration template, always use the Paste Option: Values (V). Avoid to paste data including formatting and formulas into the template as this might lead to a
corrupted XML file.
● In migration cockpit there is value mapping available for most fields. This means that you can enter your source data value and later map it in the migration cockpit to a valid SAP S/4HANA
value.
● Some of the fields in the Microsoft Excel XML template are hidden as they are not used very often or serve as additional information only. To make the respective columns or rows visible,
proceed as follows: Open the migration template in Microsoft Excel. Highlight the columns or rows you want to unhide. Right-click on the column or row number and choose Unhide. The
columns or rows will no longer be hidden. For more information on field level, for example, increase line 8 of the migration template to make the additional field description visible.
● Find Sample Migration Templates in the SAP Help Portal.
● Find a Release Comparison of Migration Object Templates in the SAP Help Portal.
● Find information on the maximum file size of the migration template in the Migration Template File Size [page ] 25 section.
● The first sheet of the template is the Introduction, the second sheet is the Field List. The header section of the Field List contains the link and the path to the SAP Portal, where additional
information about the usage of the migration template is available. Also see Additional Information About Migration Templates in the SAP Help Portal.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 15
Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1. Open Downloaded The Microsoft Excel XML Spreadsheet 2003 migration template files consist of different sheets, which are Microsoft Excel displays the
Migration Template visible at the bottom of the file. You use the different sheets to specify the data belonging to different data migration template.
structures. Some sheets are mandatory, and some are optional.
Select the migration template on your local PC and open it using Microsoft Excel.
2. Read Introduction Read the Introduction to familiarize yourself with the template and its usage. Check the Field List to You know the mandatory
and Field List determine mandatory and optional sheets or structures. sheets and fields and how to
maintain the template.
3. Enter Test Data in Enter your test data in all mandatory sheets of your migration template. Fill all mandatory columns. The migration template
Mandatory Sheets Note Mandatory columns are marked with an asterisk (*). Fields are only mandatory if a record exists. It contains the data of the
Manually doesn’t make sense to provide records where only the key fields are filled. For further details, read the mandatory sheets.
Appendix and the respective migration object documentation.
4. Enter Test Data in Enter test data in the sheets of your migration template, which are not mandatory. The migration template
Optional Sheets Note Mandatory columns are marked with an asterisk (*). Although an optional sheet may contain mandatory contains data of sheets, which
Manually columns, if the sheet is not relevant for your project, there is no need to fill the mandatory columns in the are not mandatory.
sheet with data. For further details, read the Appendix and the respective migration object documentation.
5. Save the File To save the data on your local PC choose Save in the Microsoft Excel application. The migration template
Note If you save the file, be sure to only save it as Microsoft Excel XML Spreadsheet 2003 file. Other file containing test data is saved
types are not supported by the migration cockpit and lead to errors when trying to upload them. on your local PC.

6. Close the File Choose Close in the Microsoft Excel application. The Microsoft Excel
application is closed.

Result

Test data is entered into the Microsoft Excel XML Spreadsheet 2003 template.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 16
7.6 Upload Migration Template and Verify Data

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you upload the migration template and verify its data.

Procedure

Test Test Step Instruction Expected Result Pass / Fail

Step # Name /
Comment
1. Open Migration Open Migrate Your Data. The Home page appears.
Cockpit
2. Open Migration Select the table row containing your project in the Available Migration Projects table Migration Project Details screen appears.
Project and choose Open.
3. Select Switch to the Migration Objects tab and select the table row containing your The Migration Object Details screen appears.
Migration migration object. Choose Open.
Object
4. Upload Choose Upload File. The File Upload dialog window appears.
Migration
Template

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 17
 5. Open File Choose Browse to select the corresponding migration template from your local PC. The file browser of your local PC appears in a dialog
Browser of your window.
local PC
6. Select File Select your migration template in the file explorer dialog, and choose Open. The file path of your local file is transferred to the File Path
of the File Upload dialog window.
7. File Upload Fill in the fields of the File Upload dialog box: Note If you choose an already existing file name, an error
● File Name: <Unique name of your migration template>. message tells you that the file named <File name> is already
assigned and prompt you to specify a different file name.
● Description: <Meaningful description>.
Note If you choose a migration template that is not
● Comment: <Optional comment>.
compatible with the structure of the current release, an error
message will tell you that the upload is canceled as the file
structure is not consistent with active view structure.
8. Upload Choose Upload to load the data from the migration template into the staging area of Your file appears in the overview list of the Source Files
Migrate Your Data. area.
Caution Dependent on your internet browser and the browser version, it might be that
you receive an error message, such as Error when uploading file XML: No virus scan
provider available for scanner group DEFAULT. If this message occurs, try to use
another browser or update your browser to a newer version.
9. Activate File for Select your file from the overview list of the Source Files area and choose Activate. Your file is active and marked with a green status icon.
Migration Note Should the overview list contain multiple files that have not yet been finished,
select the files and choose Deactivate to avoid reprocessing. Only activate those files
that you really want to load. If you start the transfer process, all(!) activated files are
transferred.
10. Open File to Select your file from the overview list of the Source Files area and choose Open. A new screen appears. The file details and the data record are
Verify the Data displayed.
In the Data Records area, the uploaded data records are
displayed. The structure resembles the migration template
structure. Each worksheet of the migration template is
displayed as a single tab.
11. Verify the Data Choose the different tabs and verify that the data of your migration template is The file is consistent and does not contain any empty
correctly loaded into the data staging area. records.
Check whether all records have a valid key and that no records are empty.
12. Finish the Choose the < Back button to go back to Migration Object Details screen.
Verification

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 18
Result

The migration template is uploaded, entries are consistent, and the file does not contain any empty records.

7.7 Transfer Migration Template Data

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you import the data from your migration template into the SAP S/4HANA target system.

Procedure

Test Test Step Instruction Expected Result Pass /

Step # Name Fail /
Commen
t
1. Open Open Migrate Your Data. The Home page appears.
Migration
Cockpit
2. Open Select the table row containing your project in the Available Migration The Migration Project Details screen appears.
Migration Projects table and choose Open.
Data Migration to SAP S/4HANA from File (BH5) PUBLIC
Purpose Error: Reference source not found 19
 Project
3. Select Switch to the Migration Objects tab and select the table row containing The Migration Object Details screen appears.
Migration your migration object. Choose Open.
Object
4. Start Select your file from the overview list of the Source Files area and choose The Guided Activity screen appears in a separate browser window and data
Transfer Start Transfer to migrate the data from your file. validation is in progress.
Note A guided activity controls the data migration process. Execute all
steps one after another.
5. Validate Choose Close to close the dialog window when the progress reaches The Validate Data screen is displayed, showing the notifications of the validation
Data 100%. run.
Note You can ignore error messages regarding value mappings. These are Note The message Information required; specify mapping values in step 'Convert
fixed in the Convert Values step. Correct all other occurring errors. In Values' is not an error message: You can transfer a record only once into a
case that data changes in your source file are required to solve the error, system. A unique record is identified by a combination of its value and
select the file, choose Download, and save it on your local PC. After associated key fields in the migration template. If you get the message Source
changing the data, repeat activity Transfer Migration Template Data record for example MATNR=M12345 already transferred to target system., it
[page ] 19 once again. means that the uploaded file contains source data values in fields where a value
mapping (translation) rule is assigned. These values are automatically added as
new source data values to the translation rule. It is assigned to a correct target
value in the Convert Values step.
Note The error Missing key relationship in <structure> will occur if you have
maintained records in this <structure> sheet. The key of this record is missing in
one of the superior sheets.
Note DMC_RT_MSG 622. The record where the key MATNR has value
M12345 in the migration template was already successfully transferred and
cannot be transferred anymore. Check your records in your migration template
and remove all related records. This message is not an error message and you see
it if you change the message log filter to All.
6. Navigate Choose Next to navigate to the next step. The Convert Values screen is displayed, showing a list of all your open tasks.
to Next
Step
7. Convert Convert values for data that needs to be mapped before it can be All values are properly mapped for conversion.
Values transferred to SAP S/4HANA. For more information on this step, refer to
the Convert Values [page ] 26 section in the appendix.
Note If you have entered correct target values into your sheet and you are
sure that they are correct, you can also select more than one open value
mapping from your Worklist and choose the Confirm Mapping Values
function. If the values are correct, all chosen open value mappings will be

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 20
 confirmed.
8. Navigate Choose Next to navigate to the next step. The Simulate Import screen is displayed.
to Next
Step
9. Simulate The target system validates the data. No data is posted to the target If no errors are found, proceed with the next step.
Import system.
Choose Close to close the dialog window when the progress reaches
100%.
If errors are found, correct them and choose Repeat Simulation to execute
the simulation again. Repeat this process until all errors are solved. If you
must change data in your source file to solve the error, select the file,
choose Download, and save it on your local PC. After changing the data,
repeat activity Transfer Migration Template Data [page ] 19 once again.
10. Navigate Choose Next to navigate to the next step. The Execute Import screen is displayed, showing the dialog window with the
to Next progress bar of the currently active import run.
Step
11. Execute Choose Close to close the dialog window when the progress reaches The data import is finished successfully without errors.
Import 100%.
Note Correct all possible errors and choose Repeat Import to execute the
import again. If you cannot solve all the errors, continue with the next
step.
12. Complete Choose Finish to complete the currently active Guided Activity. The guided activity window is closed and the Migration Object Details screen
the It is important to complete the file by choosing Finish, even if an error appears.
Process occurs. Never delete a file that is in the In process status, and then try to Note In the case of errors, a Delta File is created. The Delta File contains only
process the same file again. those records that have errors. To download it, choose Download, and save it to
your local PC. After you have corrected the errors, repeat the Transfer Migration
Template Data [page ] 19 activity once again using the Delta File.

Result

The data is transferred from the Microsoft Excel XML Spreadsheet 2003 template to the SAP S/4HANA system.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 21
7.8 Check Data Migration Status

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you use the Data Migration Status (F3280) app to check the status of your migration projects and objects.

Prerequisite

You've started migrating data to your SAP S/4HANA system for at least one migration object.

Procedure

Test Test Step Instruction Expected Result Pass /

Step # Name Fail /
Commen
t
1 Open Data Choose the Data Migration Status (F3280) app. The Data Migration Status page appears. Here you can see an overview
Migration of all migration objects that you've started using so far. The table shows
Status app the total number of records, the number of imported records, the number
of records that are ready for import, and the number of failed records. In
the right column you find a progress bar on the status of your objects.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 22
 2 Optional: You can apply filters on the overview table to find the object you're looking for The table is filtered according to your requirements.
Apply faster. Therefore, choose Expand Header and the filter header expands. You
Filters can use the first field for free text search, or you can use the Migration Period,
Migration Project, Object Name, and Record Status fields for your query. After
you've entered the desired values, choose Go.
3 Drill Down For more information on a migration object, just choose the name of the A pane opens on the right side. In the first table in this pane, you find an
on a respective object. overview of all Records of this migration object. This table shows the
Migration Source ID, Status, Description, Project, and Audit Status. In the second
Object table in this pane, you find an overview of all Messages of this migration
object. This table shows all Message Types, Messages, and the Number
of messages.
4 Optional: You can apply filters on both the Records and the Messages table to find the The table is filtered according to your requirements.
Apply record or message you're looking for faster. For the Records table, you can use
Filters the field for free text search on the right side, or you can use the dropdown list
on the left side to filter for the Status or the Audit Status of the records. For the
Messages table, you can use the message type options – Error and Warning –
to filter for the Message Type.
5 Drill Down For more information on a record or a message, just choose the name of the A pane opens on the right side. In this pane, you find detailed information
on a Record respective object. on the record or the message.
or a
Message
6 Close all You can close every pane by choosing the close symbol in the upper right The panes are closed and you're back on the Data Migration Status page.
Panes corner of the pane.

Result

You are up-to-date with the status of your migration projects and objects, and you can make the necessary changes in your migration projects.

Further Information

Make sure you read the SAP S/4HANA Cloud product assistance. There, you can find detailed information on the features of the Data Migration Status app, for example how to use the audit
function, how to set up notifications, and lots more.
You can find frequently asked questions relating to the Data Migration Status app in the SAP Note 2615787.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 23
7.9 Validate Imported Data using SAP S/4HANA Business Apps

Test Administration

Customer project: Fill in the project-specific parts.

Test Case ID <X.XX> Tester Name Testing Date Enter a test date.

Business Role(s)

Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.

Use

This section describes how you validate completeness and correctness of the migrated data in the target SAP S/4HANA system using corresponding business functions.

Procedure

Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Access the Corresponding Open the corresponding app or transaction of the SAP All data from the Microsoft Excel XML Spreadsheet Template 2003
App or Transaction S/4HANA system and check completeness of the imported is displayed in the corresponding SAP S/4HANA app or transaction.
data.
Note Check the migration object documentation for the app
and the needed business role to validate the data in the system.

Result

All data from the Microsoft Excel XML Spreadsheet 2003 template can be found in the corresponding SAP S/4HANA business functions.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 24
8 Appendix

8.1 General Topics and Limitations

8.1.1 When to create a new project?

We recommend that you create a new project if you encounter one of the following situations:
● You load data for an object from different systems with different value mappings.
● For some objects (for example Fixed asset) there could be data constellations existing where it is necessary to create two projects.
For example: Assets that belong to different charts of depreciation cannot be migrated with a single upload file if the depreciation areas differ. You will have to double-check the mapping of the
depreciation areas if the uploaded assets belong to a different chart of depreciation than the one used in the previous upload. This limitation will not be relevant, if you create separate migration
projects by company code.

8.1.2 Dependent Migration Objects

Some migration objects may have a dependent migration object. In general, if a migration object has a dependent object, then the dependent object must be processed first. After you have processed
the dependent migration objects, you transfer the data specified in the relevant files. When you have transferred all dependent objects, you process the migration object that has the dependent objects,
and transfer the data in the file.
You can find all the dependencies of a migration object in the Prerequisites section of the migration object documentation.
Note If a migration object is valid for a certain period, then not only must any dependent objects be processed first, they must also fit to the specified validity period.
Example The migration object Routing has dependent migration objects, including Material BOM and Activity type. The migration object Routing is valid for a certain period; in the file for the
migration object Routing, you specify the key date 10 January 2015. This means that the migration object is valid from this date onwards. You process the dependent migration objects, including
Material BOM and Activity type. You ensure that the data you specify in the files for these objects is only valid from 10 January 2015 onwards.

8.1.3 Migration Template File Size

The maximum size limit for an uploaded file is 100MB.
You can upload either a single XML file or a ZIP file containing multiple XML files. The limit of 100MB is valid for both a single XML file or a ZIP file.
It is possible for the XML files compressed in the ZIP file to have a total of up to 160MB. However, before upload, make sure that the size of the final generated ZIP file does not exceed 100MB.
Data Migration to SAP S/4HANA from File (BH5) PUBLIC
Purpose Error: Reference source not found 25
8.1.4 Convert Values

Use

A migration object contains mapping information for the relevant fields, as well as any rules used to convert values that are migrated from source fields to target fields. However, when migrating
your data, you might be prompted to convert values after the Validation step. This means that some data may need to be mapped before it can be transferred to SAP S/4HANA. In the Convert Values
step of the migration process, you maintain and confirm the mapping between the source file data values and the target system field values. This section explains how to perform these mappings
before you can proceed with the next step of the migration process.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 26
Prerequisite

In the migration process, after the Validation step, there are one or more tasks displayed in the Notifications from Validation pane. These tasks state that some mapping values need to be specified
and confirmed in the next step, Convert Values.

Procedure

1. In the Worklist pane of the Convert Values screen, choose the name of one of the open tasks. A red indicator in the Status column shows open tasks. There are different task types:

Task Type Description

Fixed Values Here you can maintain a fixed value, for example the global value for the controlling area. Fixed value tasks normally include "fix" or "set" in their name.
Mapping Rules Here you can map source values to target values. The rule names always start with the word "mapping".
Control Parameters With a control parameter you can for example choose whether you want to use internal or external numbering for specific objects.
12. Proceed by performing one of the following actions.
1. If you want to change a default mapping to a customized mapping, choose the desired option from the dropdown list in the Customizing column. Then choose Save.
Example: The default mapping is external numbering and you want to change this default to internal numbering, choose internal numbering from the dropdown list in the Customizing
column.
2. If you want to confirm a mapping, choose the respective row and confirm it by choosing the green checkmark.
3. If the value in the Target Value column is not correct, choose the respective row and enter the correct value in the field. Alternatively, you can select the correct value from the target
search list by choosing it from the value help options. Confirm the value by choosing the green check mark. These incorrect target values are caused by migration objects with identifiers
in the source system that do not correspond to the identifiers in SAP S/4HANA. That's why you have to translate these source system identifiers to the identifiers in SAP S/4HANA.
Example: The value in the Source Value 1 column is GERMANY and in the Target Value column it has been truncated to GER, because SAP S/4HANA allows a maximum of three
characters for this field. However, this does not match the format expected by SAP S/4HANA, which in this case is DE (ISO code). Therefore, change GER to DE or select DE from the
target search list by selecting it from the value help options.
Note Legacy values are automatically mapped. Nevertheless, you must confirm the mapping (see step 2b).
13. Choose Save.
14. Continue to map all rows in all field mapping lists following one of the methods described above.
Tip When you confirm values, they are marked with a green indicator, showing that the mapping is completed and there are no more tasks.
Depending on the Filter settings of the screen, migration settings may not be displayed. By setting the Filter to All, all migration settings are listed again.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 27
Result

You have processed all open tasks in the worklist and all tasks show green indicators. Continue with the next step, Simulate Import, by choosing Next.

8.1.5 Unit of Measure Conversion

The migration objects used to transfer data to SAP S/4HANA and SAP S/4HANA Cloud use ISO codes for unit of measure (UoM) values. This means that you need to map the UOM values that you
have entered in the migration template or in the staging table to a valid ISO code (T006-ISOCODE) that is unique. During the Convert Values [page ] 26 step, we recommend that you select a valid
ISO code by using the value help dialog for the S/4HANA Target Value field. The value help displays the ISO code, the commercial (language-dependent) UoM, and the description.
If the message No measure unit is assigned to ISO code is displayed while verifying the data, there are three possible reasons.
1. There is a UOM with no ISO code assigned.
To resolve this issue, assign a unique ISO code to the UOM.
15. There is more than one entry for the ISO code, and none of them is flagged as PRIMARY.
To resolve this issue, flag one entry as PRIMARY.
16. There is more than one entry for the ISO code, and more than one entry is flagged as PRIMARY.
To resolve this issue, make sure that only one entry is flagged as PRIMARY. Remove the flag from the other entries.
For further information, also see SAP Knowledge Base Articles 2660271 and 2665837.

8.1.6 ALE/IDoc Distribution After Data Migration

If you want to distribute data from your SAP S/4HANA or SAP S/4HANA Cloud system to other systems via Application Link Enabling (ALE), carefully read SAP Knowledge Base Article
2764437 before you start migrating the data using the migration cockpit.

8.2 Financials

8.2.1 Document Types for Data Migration

The document type for all open item and open balance migration objects can be freely chosen and entered into the Document Type field.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 28
For migration of general ledger balances, we recommend the document type UE, and for open item migration objects, we recommend the document types DR (Customer Invoice) and KR (Vendor
Invoice), respectively.

8.2.2 Document Date

The document date must be the same date as in the original data record.

8.2.3 Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1)

Migration Key Date/Posting Date for Financial Documents

Before you go live with SAP S/4HANA, you may want to do an initial transfer of open balances and open items from a legacy system to your SAP S/4HANA system. You transfer such data using
the SAP S/4HANA Migration Cockpit.
To enable the cockpit to transfer your legacy financial transactional data properly, use the Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1) app to maintain the migration key date
on which you want to complete all preparatory activities for each company code before the actual data transfer.
The migration key date must allow for you to complete the following actions:
● Complete all postings available up to this date, in full, in the source system
● Reconcile and close the journals in the source system for the period
● Extract source data and enter it into the migration templates
● Clean and convert data as needed
● Validate the imported data against your legacy system
The date chosen is usually the end of a period (month, quarter, year) since this will fit in with the normal reconciliation cycle.
Please note that the migration key date is also used as the posting date when the legacy data is actually transferred to your SAP S/4HANA system.
Set the Legacy Data Transfer Status for each migration key date provided:
● In Preparation: migration key date is still unclear (migration of transactional data is not possible)
● Ongoing: required for the initial data transfer (migration of transactional data is possible)
● Completed: after successful completion of the initial data transfer (migration of transactional data is not possible)
For the following financial objects, the posting date will be automatically derived by the predefined migration key date for the related company code which is maintained via the aforementioned app:
● FI - Accounts payable open item
● FI - Accounts receivable open item
● FI - G/L account balance and open/line item
Data Migration to SAP S/4HANA from File (BH5) PUBLIC
Purpose Error: Reference source not found 29
● Material inventory balance
● FI - Historical balance (migration key date is required to allow the migration of historical balances only up until this initial transfer date)

Exception

● For the financial object FI-CA Open item, a field for posting date is available on the migration template. The posting date is marked as mandatory on the template and must be provided for each
data record. The migration key date has no additional effect on the provided posting date.
● For the financial object Fixed asset - Master data, use the Make Company Code Settings - Asset Accounting-Specific (FAA_CMP) app to specify the data transfer date, document type, and the
legacy data transfer status.
See also General Ledger Accounting > Current Settings in the SAP S/4HANA Cloud product assistance for further information on the configuration of the Migration Key Date before migrating
transactional data.

8.2.4 Value Date

The value date must be the same date as in the original data record.

8.2.5 Transfer Booking Account

The transfer booking accounts to be used for the Open item and Open balance migration objects are as follows:

Account Description Migration Cockpit Object Name

39911000 Initial Entry of Raw Material Balances Material inventory balance
39912000 Initial Entry SF & Finish Gds Balances Material inventory balance
39913000 Initial FI-AM offset Fixed asset - Postings
39914000 Initial FI-AR offset FI - Accounts receivable open item
39915000 Initial FI-AP offset FI - Accounts payable open item
39916000 Initial other G/L offset FI - G/L account balance and open/line item
39917000 Initial other Open Item G/L offset FI - G/L account balance and open/line item

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 30
8.2.6 Migrate Historical Balances
If you want to migrate historical financial balances to your SAP S/4HANA Cloud system using the SAP S/4HANA migration cockpit, use the FI - Historical balance migration object. For further
information on this migration object, see the migration object documentation.

8.2.7 Fixed Assets: Available Fields per Asset Class

The migration template for Fixed asset - Master data provides fields for the asset class you want to migrate. These fields might be hidden or read-only. If you enter data into such fields or if you miss
data in mandatory fields, you get error messages during the data migration such as AY 219: Field ... is not ready for input, for example Field Inventory Number is
not ready for input.
To avoid such errors, SAP delivers documentation via the SAP Help Portal that gives an extensive and comprehensive release dependent overview of the screen layout for asset master data, both for
assigned logical field groups and not assigned logical field groups. Its purpose is to provide a detailed explanation and listing of asset classes and available fields per asset class to support you when
you fill out the data migration template for Fixed asset - Master data. The field status that defines a field as hidden, read-only, mandatory, or optional depends on the asset class and the assigned
screen layout. In the document attached to the SAP Note you can find the fields that are necessary for an asset class. It also helps you to fill out the data migration template for your asset data
migration.

Related Links

● Fixed Assets: Available Fields per Asset Class

● Migration object documentation for Fixed asset - Master data

8.2.8 Migrate Financial Plan Data

If you have financial plan data in your legacy system that you want to import to your SAP S/4HANA system, you may do so by using the Import Financial Plan Data (F1711)
This app is available to users with the following business roles:
● SAP_BR_OVERHEAD_ACCOUNTANT
● SAP_BR_SALES_ACCOUNTANT
● SAP_BR_PROJ_FIN_CONTROLLER
By using this app, you can import periodic financial plan data for the following planning areas:
● Cost Centers
● Projects
Data Migration to SAP S/4HANA from File (BH5) PUBLIC
Purpose Error: Reference source not found 31
● Profit Centers
● Market Segments
● P&L
● Balance Sheet
● Functional Areas
For further information on this app, check the SAP Fiori apps reference library and refer to the online help.

8.3 Logistics

8.3.1 Advanced Variant Configuration

To create objects of a configuration model, create the objects in the following order:

# Object Name Manual Creation Comments

Only
1 Change number X If you want to use a change number, create a new change number first.
(optional)
2 Document info record X
3 Characteristic Dependencies must be added manually.
4 Class
5 VC - Variant table
structure
6 VC - Variant table
entry
7 VC - Object Only for global dependencies. Create object dependencies with status Released. In case of a syntax error in the dependency the creation of
dependencies this dependency will be prevented.
8 Product
9 Object classification
10 VC - Constraint
11 VC - Dependency net

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 32
 12 VC - Configuration
profile
13 Material BOM
Note Migration of local dependencies is currently not supported for all objects. Please read the migration object documentation carefully to determine which objects support this.

8.3.2 How to Handle Cross-Plant Material Status and Plant-Specific Material Status
If you set the material status during initial load of the materials, consider that, depending on which status you want to assign, follow-on migration objects can't be posted as the posting may lead to an
error depending on the settings of the status.

Example

In SAP standard delivery, the material status '01' is configured in such a way that, during posting of inventory, you will receive an error message. Consider that by assigning the status, the use of the
material can be restricted. Depending on the status, the system issues either a warning message or an error message for follow-on postings. Therefore, SAP recommends that you consider this field
carefully so that you will not run into follow-on problems during the data migration process. You can easily set the content of these fields after the initial data migration using the Mass Maintenance
app.
The Master Data Specialist - Product Data (SAP_BR_PRODMASTER_SPECIALIST) business role provides you with several tiles to manage and start the Mass Maintenance app. The app can be
launched from the SAP Fiori launchpad. You can import a file with changed data (supported formats are Comma-Separated Values (CSV) and Office Open XML spreadsheet (XLSX). You have to
provide the following details:
● Which master data objects are updated.
● Which tables and fields to update and the respective values.
For further information, refer to the online documentation of the Mass Maintenance app.

Data Migration to SAP S/4HANA from File (BH5) PUBLIC

Purpose Error: Reference source not found 33
Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions. www.sap.com/contactsap
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and
INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and
parameters, source text, and names of installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the
documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system. © 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R . for any purpose without the express permission of SAP SE or an SAP
affiliate company.
The information contained herein may be changed without prior notice. Some
software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any course of business outlined in this document or any related presentation,
or to develop or release any functionality mentioned therein. This document,
or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platforms,
directions, and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. 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, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their
Data Migration to SAP S/4HANA from File (BH5) respective logos are trademarks or registered trademarksPUBLIC
of SAP SE (or an
Purpose Error:and
SAP affiliate company) in Germany Reference source not
other countries. Allfound
other product 34
and service names mentioned are the trademarks of their respective
companies.

See www.sap.com/copyright for additional trademark information and

notices.