Data Migration To SAP S4HANA From File

Data Migration to SAP S/4HANA from File (BH5) Erro! Fonte de referência não encontrada.
Erro! Use a guia Página Inicial para aplicar Heading 1 ao texto que deverá aparecer aqui. © 2018 SAP SE or an SAP affiliate company. All rights reserved. 1
Test Script
SAP S/4HANA
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
3 Migration Objects for SAP S/4HANA 5
4 Business Conditions 11
5 Preliminary Steps 12
5.1 Create Role from Template 12
5.2 Create Data Migration User and Assign the Role 13
6 Overview Table 14
7 Test Procedures 15
7.1 Start the SAP S/4HANA Migration Cockpit 15
7.2 Create Migration Project 16
7.3 Open Migration Object 17
7.4 Download Migration Template 18
7.5 Prepare Test Data 20
7.6 Upload Migration Template and Verify Data 22
7.7 Transfer Migration Template Data 24
7.8 Validate Imported Data using SAP S/4HANA Business Apps 28
8 Appendix 30
8.1 General Topics and Limitations 30
8.1.1 When to create a new project? 30
8.1.2 Dependent Migration Objects 30
8.1.3 Migration Template File Size 31
8.1.4 Convert Values 31
8.2 Logistics – Advanced Variant Configuration 32
8.3 Logistics – Material 33
8.3.1 How to Handle Cross-Plant Material Status and Plant-Specific Material Status 33
8.4 Logistics – Material Inventory Balance 34
8.4.1 Work with Different Files 34

1 Purpose
Implementation Type
The following section is ONLY relevant for the on-premise version of SAP S/4HANA.
SAP S/4HANA customers can take advantage of a template-based migration approach built into SAP S/4HANA with rapid data migration to SAP S/4HANA. SAP S/4HANA 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.

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

Note The following SAP role templates are copied into the customers namespace by your system administrator and assigned to a user that migrates the data.
Purpose Role Role Description
SAP S/4HANA Migration Cockpit SAP_CA_DMC_MC_USER S/4HANA Migration – Data Transfer
SAP S/4HANA Migration Object Modeler SAP_CA_DMC_MC_DEVELOPER S/4HANA Migration – Data Modeling and Data Transfer

3 Migration Objects for SAP S/4HANA
In the following table, please find the migration objects available for the On premise – Enterprise Management scope view of SAP S/4HANA. Please find information on dependent migration
objects in the Dependent Migration Objects [page ] 30 section.
Note The On premise – Enterprise Management scope view is a template only to be used in an on-premise system.
Note For some migration objects there are additions to the migration cockpit object name. These additions include "restricted" and "deprecated". Restricted means that not all fields and struc-
tures of the relevant business processes are covered by this migration object, deprecated means that there is a newer version of this migration object available. Deprecated objects will be deleted
after a couple of releases. Make sure you always read the migration object documentation for these objects carefully.
Migration Cockpit Object Business Object Area Business Ob- Additional Information
Name Name ject Type
Activity price (restricted) Activity Price CO Master data Must not be used to migrate activity prices for professional services.
Activity type Activity Type CO-OM- Master data

CCA-MD
Bank Bank Master FI Master data

Data
Bank account balance Bank Account FIN-FSCM- Transactio-

FQM nal data
Batch (if Batch is unique at Batch LO-BM Master data

material level)
Batch (if Batch level is at Batch LO-BM Master data

plant level)
Cash memo record Bank Account FIN-FSCM- Transactio-

FQM nal data
Characteristic Classification CA-CL Master data

Characteristic
Class Classification CA-CL Master data

Class

Name Name ject Type
Condition contract Condition Con- LO-GT-CHB Master data
tract
Consent Consent Record CA Transactio-

nal data
Cost center Cost Center CO Master data
Customer Customer LO-MD-BP- Master data The KTOKD field must be in sync with your customizing of the BU grouping. Otherwise, the grouping will
CM overwrite the account group.
Customer (deprecated) Customer LO-MD-BP- Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be re-
CM moved with the next delivery. Use Customer instead.
Customer - extend existing Customer LO-MD Master data

record by new org levels
Customer -extend exist re- Customer LO-MD Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be re-
cord by new org levels (de- moved with the next delivery. Use Customer - extend existing record by new org levels instead.
precated)
Customer material Customer Ma- SD Master data

terial
Equipment Equipment PM Master data
Equipment task list Maintenance PM Master data

Task List
Exchange rate Exchange Rate BC-SRV- Master data

BSF-CUR
FI – Accounts payable open Accounting Do- FI Transactio-

item cument nal data
FI – Accounts receivable open Accounting Do- FI Transactio-

item cument nal data
FI – G/L account balance and Accounting Do- FI Transactio-

open/line item cument nal data

Name Name ject Type
Fixed asset (incl. balances Fixed Asset FI Master data
and transactions) + Transactio-
nal data
Functional location Functional Lo- PM Master data

cation
Functional location task list Maintenance PM Master data

Task List
G/L account General Ledger FI-GL-IS Master data

Account
General task list Maintenance PM Master data

Task List
Inspection method Inspection Me- QM-PT-BD Master data

thod
Inspection plan Inspection Plan QM-PT-IP Master data
Internal order (restricted) Internal Order FI-GL-IS Transactio-

nal data
Legal transaction Legal Transac- LCM-LT Transactio-

tion nal data
Maintenance item Maintenance PM Master data

Item
Maintenance plan Maintenance PM Master data

Plan
Master inspection characte- Inspection Spe- QM-PT-BD Master data

ristic cification
Material Material LO-MD-MM Master data
Material BOM Bill of Material LO-MD- Master data

BOM

Name Name ject Type
Material classification Classification CA-CL Master data
Valuation/Pro-
duct
Material consumption Product LO-MD Master data
Material - extend existing re- Product LO-MD Master data

cord by new org levels
Material inspection setting Product QM Master data
Material inventory balance Material Stock MM-IM Transactio- Currently not available for transfer option Transfer Data from Staging Tables.
nal data
Material long text Product LO-MD Master data
Material trade classification Product MM-IM Master data A prerequisite for this object (previously named Material Commodity Code) to be visible is that either the
Intrastat Processing (BDT) or the SAP Global Trade Services Integration - Primary Master Data (1WA) scope
item is activated. Refer to the Set-up instructions on SAP Best Practices Explorer for BDT and/or 1WA to
activate the respective scope item.
Pricing condition (general) Price Condition SD-MD-CM, Master data

CO, MM-
PUR
Pricing condition (purchasing) Price Condition MM Master data
Pricing condition (sales) Price Condition SD Master data
Production version Production Ver- PP Master data

sion
Profit center Profit Center FI, CO Master data Currently not available for transfer option Transfer Data from Staging Tables.
Purchase order (only open Purchase Order MM-PUR Transactio-

PO) nal data
Purchase scheduling agree- Purchase Sche- MM-PUR Transactio-

ment duling Agree- nal data
ment

Name Name ject Type
Purchasing contract Purchase Con- MM-PUR Transactio-
tract nal data
Purchasing info record- ex- Purchasing Info MM-PUR- Master data

tend existing record Record VM
Purchasing info record with Purchasing Info MM-PUR Master data

conditions Record
QM/PM catalog code Inspection QM-PT-BD Master data

group/code Code Group
QM selected set Inspection Se- QM-PT-BD Master data

lected Set
QM selected set code Inspection Se- QM-PT-BD Master data

lected Set
Routing Routing PP-BD-RTG Master data
Sales contract Sales Contract SD Transactio-

nal data
Sales order (only open SO) Sales Order SD Transactio-

nal data
Software/Hardware constra- Software Cons- PLM-ESD- Master data

int traint ESC
Source list Source List MM-PUR Master data
Supplier Supplier LO-MD-BP- Master data The KTOKK field must be in sync with your customizing of the BU grouping. Otherwise, the grouping will
VM overwrite the account group.
Supplier (deprecated) Supplier LO-MD-BP- Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be re-
VM moved with the next delivery. Use Supplier instead.
Supplier - extend existing re- Supplier LO-MD Master data

cord by new org levels

Name Name ject Type
Supplier- extend exist record Supplier LO-MD Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be re-
by new org levels (depreca- moved with the next delivery. Use Supplier - extend existing record by new org levels instead.
ted)
VC - Variant configuration Variant Confi- LO-VC Master data

profile guration Profile
Work center Work Center PP-BD- Master data

WKC, QM
Xceptional case - Material Product CO-PC-ACT Master data

price chng for global curren-
cies
Note The pre-delivered data migration objects are built for SAP S/4HANA Cloud and the SAP S/4HANA Best Practices Content (cloud version). You can use these objects also for SAP S/4HANA (on
premise or private cloud) and the SAP S/4HANA Best Practices Content. Using SAP S/4HANA, the delivered standard migration objects are templates that can be enhanced according to your needs.
The enhancement is only limited by the functionality of the tool and the capabilities of the underlying API to load the data. Starting with SAP S/4HANA 1610 FPS2, you can enhance customer
projects based on these delivered standard migration objects or you can create your own objects using the SAP S/4HANA migration object modeler (transaction LTMOM). We therefore recom-
mend that you update your system to 1610 FPS2 to use the latest version of the migration object modeler. For further information, please see SAP Note 2481235.

4 Business Conditions
Before this scope item can be tested, the following business conditions to be met:
Scope Item Business Condition
Content is activated
Org. structures and additional settings are made

5 Preliminary Steps
Use
In this step, you set up user settings that are necessary for migrating your data.
5.1 Create Role from Template

Use
In this step you create the role from the Technical Roles section for the data migration user that is necessary for migrating your data.
Procedure
1. Access the Roles transaction using one of the following navigation options:
Option Navigation path
Transaction Code PFCG
SAP Menu Tools > Administration > User Maintenance > Role Administration > Roles
2. In the Role field, enter the name of the role to copy: SAP_CA_DMC_MC_USER.
3. Choose Role > Copy .
4. In the Query dialog box that appears, enter the name of the role according to your company naming convention, for example: Z_DMC_MC_USER in to role field.
5. Choose Copy All tab, then choose Change.
6. Enter the description Role to migrate data using the migration cockpit in the description field.
7. Choose Authorizations tab.
8. Choose Propose Profile Names in the Information About Authorization Profile section to generate a profile.
Note This user needs authorization to create a profile: Authorization object: S_USER_PROF Authorization values: ACTVT = 01, 06
9. Choose Change Authorization Data in the Edit Authorization data and Generate Profiles section.
10. In the appearing Save the role dialog box, choose Yes to save the role.
11. Read the Important information box and choose Enter.
12. Choose Save to save the role.
13. Choose Authorizations > Generate to generate the role.
Result
You have created the role to use the SAP S/4HANA migration cockpit.
5.2 Create Data Migration User and Assign the Role

Use
In this step, you create the data migration user and assign the roles. It is done from Create Role from Template [page ] 12 and enables in migration of the data.
Procedure
1. Access the Users transaction using one of the following navigation options:
Option Navigation path
Transaction Code SU01
SAP Menu Tools > Administration > User Maintenance > Users
2. In the User field, enter the name of the data migration user, for example: DM_USER.
3. Choose User > Create .
4. Enter Data Migration user in Last name field of the Address tab.
5. Choose Logon data tab.
6. Select System in the User Type field.
7. Enter the password in the New Password field and repeat the password in the Repeat Password field.
8. Choose Roles tab.
9. Enter the name of the role you have created in the previous section Create Role from Template [page ] 12, for example Z_DMC_MC_USER.
10. Choose Enter, and then choose Save.
Result
You have created the data migration user and assigned the data migration role to it to use the SAP S/4HANA migration cockpit.

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 Migra- SAP Fiori launchpad This section describes how you start the SAP S/4HANA migration The migration cockpit is displayed.
tion Cockpit [page ] 15 cockpit.
Create Migration Project [page Migration cockpit (Web This section describes how you create a migration project in the mi- A migration project is created.
] 16 Dynpro via SAP Fiori gration cockpit.
launchpad)
Open Migration Object [page ] Migration cockpit (Web This section describes how you open a migration object in the mi- A migration object is opened.
17 Dynpro via SAP Fiori gration 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 is
[page ] 18 Dynpro via SAP Fiori facilitate the data transfer from Microsoft Excel spreadsheet tem- downloaded.
launchpad) plates to SAP S/4HANA.
Prepare Test Data [page ] 20 Microsoft Excel This section describes how you enter test data for migration to SAP Test data is entered into the Microsoft Excel XML Spre-
S/4HANA into the migration template. adsheet 2003 template.
Upload Migration Template Migration cockpit (Web This section describes how you upload the migration template and The migration template is uploaded, entries are consis-
and Verify Data [page ] 22 Dynpro via SAP Fiori verify its data. tent, and the file does not contain any empty records.
launchpad)
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 ] 24 Dynpro via SAP Fiori template into the SAP S/4HANA target system. Spreadsheet 2003 template to the SAP S/4HANA sys-
launchpad) tem.
Validate Imported Data using SAP Fiori launchpad This section describes how you validate completeness and cor- All data from the Microsoft Excel XML Spreadsheet
SAP S/4HANA Business Apps rectness of the migrated data in the target SAP S/4HANA system 2003 template can be found in the corresponding SAP
[page ] 28 using corresponding business functions. S/4HANA business functions.

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. Log on to SAP S/4HANA Log on to your SAP S/4HANA back-end system.
2. Open migration cockpit Start the SAP S/4HANA migration cockpit using the LTMC transaction.

Note For tool documentation on the SAP S/4HANA migration cockpit, navigate to SAP S/4HANA Migration Cockpit in the SAP Help Portal. You can choose your release from the Version
dropdown list in the upper right corner.
Result
The SAP S/4HANA migration cockpit appears.
7.2 Create Migration Project
Test Administration
Business Role(s)
Use
This section describes how you create a migration project in the migration cockpit.
Procedure
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.
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 the button Generate New Mass Transfer ID. The
system generates the next available mass transfer ID.
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
Business Role(s)

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 ] 30 section.
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 ] 16 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 two The migration objects are filtered as per sta-
Migration Status statuses In Process or Not Started. You can find the different statuses at the bottom of the tus. Only objects with the selected status are
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

Business Role(s)
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 / Com-
# ment
1. Download Tem- Choose Download Template on the Source Files tab of the Migration Ob- The migration template is downloaded and saved on
plate ject 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
Business Role(s)
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 ] 31 section.
● For additional information about migration templates, see Additional Information About Migration Templates in the SAP Help Portal. You can choose your release from the Version
dropdown list in the upper right corner.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail

Step # / Com-
ment
1. Open Downloaded The Microsoft Excel XML Spreadsheet 2003 migration template files consist of different sheets, which are visi- Microsoft Excel displays the
Migration Tem- ble at the bottom of the file. You use the different sheets to specify the data belonging to different data struc- migration template.
plate tures. 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 determine You know the mandatory
and Field List 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 con-
Mandatory Sheets Note Mandatory columns are marked with an asterisk (*). Fields are only mandatory if a record exists. It do- tains the data of the manda-
Manually esn’t make sense to provide records where only the key fields are filled. For further details, read the Appendix tory sheets.
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 con-
Optional Sheets Note Mandatory columns are marked with an asterisk (*). Although an optional sheet may contain mandatory tains 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.

Test Test Step Name Instruction Expected Result Pass / Fail
Step # / Com-
ment
5. Save the File To save the data on your local PC choose Save in the Microsoft Excel application. The migration template con-
Note If you save the file, be sure to only save it as Microsoft Excel XML Spreadsheet 2003 file. Other file types taining test data is saved on
are not supported by the migration cockpit and lead to errors when trying to upload them. your local PC.
6. Close the File Choose Close in the Microsoft Excel application. The Microsoft Excel applica-
tion is closed.
Result
Test data is entered into the Microsoft Excel XML Spreadsheet 2003 template.
7.6 Upload Migration Template and Verify Data
Test Administration
Business Role(s)
Use
This section describes how you upload the migration template and verify its data.

Procedure
Test Test Step Instruction Expected Result Pass /

Step Name Fail /
# Com-
ment
1. Open Migra- Open Migrate Your Data. The Home page appears.
tion Cockpit
2. Open Migra- Select the table row containing your project in the Available Migration Projects table and Migration Project Details screen appears.
tion Project choose Open.
3. Select Migra- Switch to the Migration Objects tab and select the table row containing your migration The Migration Object Details screen appears.
tion Object object. Choose Open.
4. Upload Migra- Choose Upload File. The File Upload dialog window appears.
tion Template
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 win-
Browser of dow.
your 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 The error File named <File name> already assig-
● File Name: <Unique name of your migration template>. ned; specify a different file name will occur if you choose
an already existing file name.
● Description: <Meaningful description>.
Note The error Upload canceled; file structure not consis-
● Comment: <Optional comment>.
tent with active view structure will occur if you choose a
migration template that is not compatible with the struc-
ture of the current release.
8. Upload Choose Upload to load the data from the migration template into the staging area of Mi- Your file appears in the overview list of the Source Files
grate 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 provi-
der available for scanner group DEFAULT. If this message occurs, try to use another
browser or update your browser to a newer version.

Test Test Step Instruction Expected Result Pass /
Step Name Fail /
# Com-
ment
9. Activate File 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.
for Migration Note In case that the overview list contains 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 transfer-
red.
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
Verify the are displayed.
Data In the Data Records area, the uploaded data records are
displayed. The structure resembles the migration tem-
plate structure. Each worksheet of the migration template
is displayed as a single tab.
11. Verify the Choose the different tabs and verify that the data of your migration template is correctly The file is consistent and does not contain any empty re-
Data loaded into the data staging area. cords.
Check whether all records have a valid key and that no records are empty.
12. Finish the Ve- Choose the < Back button to go back to Migration Object Details screen.
rification
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

Business Role(s)
Use
This section describes how you import the data from your migration template into the SAP S/4HANA target system.
Procedure
Test Test Instruction Expected Result Pass /

Step Step Fail /
# Name Com-
ment
1. Open Open Migrate Your Data. The Home page appears.

Migra-
tion
Cockpit
2. Open Select the table row containing your project in the Available Migration The Migration Project Details screen appears.
Migra- Projects table and choose Open.
tion Pro-
ject
3. Select Switch to the Migration Objects tab and select the table row contai- The Migration Object Details screen appears.
Migra- ning your migration object. Choose Open.
tion Ob-
ject
4. Start Select your file from the overview list of the Source Files area and The Guided Activity screen appears in a separate browser window and data valida-
Transfer choose Start Transfer to migrate the data from your file. tion is in progress.

Step Step Fail /
# Name Com-
ment
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 run.
Data 100%. Note The message Information required; specify mapping values in step 'Convert Va-
Note You can ignore error messages regarding value mappings. These lues' is not an error message: You can transfer a record only once into a system. A
are fixed in the Convert Values step. Correct all other occurring errors. unique record is identified by a combination of its value and associated key fields in
In case that data changes in your source file are required to solve the the migration template. If you get the message Source record for example
error, select the file, choose Download, and save it on your local PC. MATNR=M12345 already transferred to target system., it means that the uploaded
After changing the data, repeat activity Transfer Migration Template file contains source data values in fields where a value mapping (translation) rule is
Data [page ] 24 once again. 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 maintai-
ned 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 re-
cords. 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 ] 31 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 Map-
ping Values function. If the values are correct, all chosen open value
mappings will be confirmed.

Step Step Fail /
# Name Com-
ment
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 ] 24 once again.
10. Navigate Choose Next to navigate to the next step. The Execute Import screen is displayed, showing the dialog window with the progress
to Next 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. Com- Choose Finish to complete the currently active Guided Activity. The guided activity window is closed and the Migration Object Details screen appe-
plete the Note In case of errors, a Delta File is created. The Delta File contains ars.
Process only the erroneous records. To download it, choose Download, and
save it to your local PC. After you have corrected the errors, repeat ac-
tivity Transfer Migration Template Data [page ] 24 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.
7.8 Validate Imported Data using SAP S/4HANA Business Apps
Test Administration
Business Role(s)
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 Correspon- Open the corresponding app or transaction of the SAP S/4HANA All data from the Microsoft Excel XML Spreadsheet Template 2003 is
ding App or Transaction system and check completeness of the imported data. displayed in the corresponding SAP S/4HANA app or transaction.
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.

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 Assets) 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 to SAP S/4HANA. When you have transferred all dependent objects, you process the migration
object that has the dependent objects, and transfer the data in the file to SAP S/4HANA.
You can find all the dependencies of a migration object in the Prerequisites section of the migration object documentation in Migration Cockpit.
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 default size limit for each uploaded file is 100MB. If required, you can increase this limit to 160MB. For on-premise systems, parameter icm/HTTP/max_request_size_KB controls the size of the
http request. The value of this parameter is the maximum size (in KB) of an HTTP request. This parameter has the standard value 102400KB (100MB) but can be changed if required. For more
information, see help on the icm/HTTP/max_request_size_KB parameter in the SAP Help Portal.
You can upload multiple XML files at once by using a zip file. Note that the same restrictions regarding the file size limit apply.
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.
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 speci-
fied 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".

Task Type Description
Control Parameters With a control parameter you can for example choose whether you want to use internal or external numbering for specific objects.
2. 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 charac-
ters 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).
3. Choose Save.
4. 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.
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.2 Logistics – Advanced Variant Configuration

To create objects of a configuration model in SAP S/4HANA 1802, create the objects in the following order:
# Object Name Manual Creation Comments

Only
1. Change number (opti- X If you want to use a change number, create a new change number first.
onal)
# Object Name Manual Creation Comments
Only
2. Document info record X
3. Characteristic Dependencies must be added manually.
4. Class
5. VC - Variant table
structure
6. VC - Variant table en-

try
7. VC - Object depen- Only for global dependencies. Create object dependencies with status Released. In case of a syntax error in the dependency the creation
dency of this dependency will be prevented.
8. Material
9. Material classification
10. VC – Constraint net X
11. VC – Constraint X
12. VC – Configuration
profile
13. Material BOM
Note Migration of local dependencies is currently not supported.
8.3 Logistics – Material
8.3.1 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 for Product Data business role (SAP_BR_PRODMASTER_SPECIALIST) 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.
8.4 Logistics – Material Inventory Balance
8.4.1 Work with Different Files

The key for Material inventory balance is the material number. All kind of stock for one material must therefore be imported with a single file. Once a stock is imported for one specific material,
you can no longer load any stock for this material.
Example
You want to load an additional stock for a different stock type. It is not possible to import stocks for the same material with different files in one project.
Therefore, we strongly recommend importing all related stocks for one material in one file.

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.

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.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

www.sap.com/contactsap
© 2018 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affiliate
company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.
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 in-
formational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or omis-
sions with respect to the materials. The only warranties for SAP SE or SAP af-
filiate company products and
services are those that are set forth in the express warranty statements ac-
companying 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 presenta-
tion, or to develop or release any functionality mentioned therein. This doc-
ument, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform direc-
tions 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 obliga-
tion to deliver any material, code, or functionality. All forward-looking state-
ments 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.

Data Migration To SAP S4HANA From File

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Migration To SAP S4HANA From File

Uploaded by

Copyright:

Available Formats

Data Migration to SAP S/4HANA from File (BH5) Erro! Fonte de referência não encontrada.

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

3 Migration Objects for SAP S/4HANA 5

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

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

2.1 System Access

2.2.1 Technical Roles

Purpose Role Role Description

SAP S/4HANA Migration Cockpit SAP_CA_DMC_MC_USER S/4HANA Migration – Data Transfer

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

Activity type Activity Type CO-OM- Master data

Bank Bank Master FI Master data

Bank account balance Bank Account FIN-FSCM- Transactio-

Batch (if Batch is unique at Batch LO-BM Master data

Batch (if Batch level is at Batch LO-BM Master data

Cash memo record Bank Account FIN-FSCM- Transactio-

Characteristic Classification CA-CL Master data

Class Classification CA-CL Master data

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

Consent Consent Record CA Transactio-

Cost center Cost Center CO Master data

Customer - extend existing Customer LO-MD Master data

Customer material Customer Ma- SD Master data

Equipment Equipment PM Master data

Equipment task list Maintenance PM Master data

Exchange rate Exchange Rate BC-SRV- Master data

FI – Accounts payable open Accounting Do- FI Transactio-

FI – Accounts receivable open Accounting Do- FI Transactio-

FI – G/L account balance and Accounting Do- FI Transactio-

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

Functional location Functional Lo- PM Master data

Functional location task list Maintenance PM Master data

G/L account General Ledger FI-GL-IS Master data

General task list Maintenance PM Master data

Inspection method Inspection Me- QM-PT-BD Master data

Inspection plan Inspection Plan QM-PT-IP Master data

Internal order (restricted) Internal Order FI-GL-IS Transactio-

Legal transaction Legal Transac- LCM-LT Transactio-

Maintenance item Maintenance PM Master data

Maintenance plan Maintenance PM Master data

Master inspection characte- Inspection Spe- QM-PT-BD Master data

Material Material LO-MD-MM Master data

Material BOM Bill of Material LO-MD- Master data

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

Material consumption Product LO-MD Master data

Material - extend existing re- Product LO-MD Master data

Material inspection setting Product QM Master data

Material long text Product LO-MD Master data

Pricing condition (general) Price Condition SD-MD-CM, Master data

Pricing condition (purchasing) Price Condition MM Master data

Pricing condition (sales) Price Condition SD Master data

Production version Production Ver- PP Master data

Purchase order (only open Purchase Order MM-PUR Transactio-

Purchase scheduling agree- Purchase Sche- MM-PUR Transactio-

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

Purchasing info record- ex- Purchasing Info MM-PUR- Master data

Purchasing info record with Purchasing Info MM-PUR Master data

QM/PM catalog code Inspection QM-PT-BD Master data

QM selected set Inspection Se- QM-PT-BD Master data

QM selected set code Inspection Se- QM-PT-BD Master data

Routing Routing PP-BD-RTG Master data

Sales contract Sales Contract SD Transactio-

Sales order (only open SO) Sales Order SD Transactio-