Purpose - wiki.myftp.orgwiki.myftp.org/sap/.../BH5_S4HANA1809_BPD_EN_XX.docx · Web viewSAP...

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

PUBLICError: Reference source not found 1

Test ScriptSAP S/4HANA - 28-08-18

PUBLIC

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

Table of Contents1 Purpose

2 Prerequisites2.1 System Access2.2 Roles

2.2.1 Technical Roles

3 Migration Objects for SAP S/4HANA

4 Business Conditions

5 Preliminary Steps5.1 Create Role from Template5.2 Create Data Migration User and Assign the Role

6 Overview Table

7 Test Procedures7.1 Start the SAP S/4HANA Migration Cockpit7.2 Create Migration Project

7.3 Open Migration Object7.4 Download Migration Template7.5 Prepare Test Data7.6 Upload Migration Template and Verify Data7.7 Transfer Migration Template Data7.8 Validate Imported Data using SAP S/4HANA Business Apps

8 Appendix8.1 General Topics and Limitations

8.1.1 When to create a new project?8.1.2 Dependent Migration Objects8.1.3 Migration Template File Size8.1.4 Convert Values

8.2 Logistics – Advanced Variant Configuration8.3 Logistics – Material

8.3.1 How to Handle Cross-Plant Material Status and Plant-Specific Material Status8.4 Logistics – Material Inventory Balance

8.4.1 Work with Different Files



1 Purpose

Implementation TypeThe 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 PrerequisitesThis section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and busi-ness conditions.

2.1 System Access

Sys-tem

Details

Sys-tem

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 RolesNote 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 DescriptionSAP S/4HANA Migration Cockpit SAP_CA_DMC_MC_USER S/4HANA Migration – Data TransferSAP S/4HANA Migration Object Mod-eler

SAP_CA_DMC_MC_DEVEL-OPER

S/4HANA Migration – Data Modeling and Data Transfer



3 Migration Objects for SAP S/4HANAIn the following table, please find the migration objects available for the On premise – Enterprise Management scope view of SAP S/4HANA. Please find infor-mation on dependent migration objects in the Dependent Migration Objects [page ] 31 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 structures of the relevant business processes are covered by this migration object, deprecated means that there is a newer ver-sion of this migration object available. Deprecated objects will be deleted after a couple of releases. Make sure you always read the migration object docu-mentation for these objects carefully.

Migration Cockpit Object Name

Business Ob-ject Name

Area Business Object Type

Additional Information

Activity price (re-stricted)

Activity Price CO Master data Must not be used to migrate activity prices for professional services.

Activity type Activity Type CO-OM-CCA-MD

Master data

Bank Bank Master Data

FI Master data

Bank account balance Bank Account FIN-FSCM-FQM

Transac-tional data

Batch (if Batch is unique at material level)

Batch LO-BM Master data

Batch (if Batch level is at plant level)

Batch LO-BM Master data

Cash memo record Bank Account FIN-FSCM-FQM

Transac-tional data

Characteristic Classification Characteristic

CA-CL Master data

Class Classification CA-CL Master data







ClassCondition contract Condition Con-

tractLO-GT-CHB

Master data

Consent Consent Record

CA Transac-tional data

Cost center Cost Center CO Master dataCustomer Customer LO-MD-

BP-CMMaster data The KTOKD field must be in sync with your customizing of the BU grouping. Other-

wise, the grouping will overwrite the account group.Customer (depre-cated)

Customer LO-MD-BP-CM

Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be removed with the next delivery. Use Customer instead.

Customer - extend existing record by new org levels

Customer LO-MD Master data

Customer -extend ex-ist record by new org levels (deprecated)

Customer LO-MD Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be removed with the next delivery. Use Customer - extend existing record by new org levels instead.

Customer material Customer Ma-terial

SD Master data

Equipment Equipment PM Master dataEquipment task list Maintenance

Task ListPM Master data

Exchange rate Exchange Rate

BC-SRV-BSF-CUR

Master data

FI – Accounts payable open item

Accounting Document

FI Transac-tional data

FI – Accounts receiv-able open item

Accounting Document


FI – G/L account bal-ance and open/line

Accounting Document








itemFixed asset (incl. bal-ances and transac-tions)

Fixed Asset FI Master data + Transac-tional data

Functional location Functional Lo-cation

PM Master data

Functional location task list

Maintenance Task List

PM Master data

G/L account General Ledger Ac-count

FI-GL-IS Master data

General task list Maintenance Task List

PM Master data

Inspection method Inspection Method

QM-PT-BD Master data

Inspection plan Inspection Plan

QM-PT-IP Master data

Internal order (re-stricted)

Internal Order FI-GL-IS Transac-tional data

Legal transaction Legal Transac-tion

LCM-LT Transac-tional data

Maintenance item Maintenance Item

PM Master data

Maintenance plan Maintenance Plan

PM Master data

Master inspection characteristic

Inspection Specification


Material Material LO-MD-MM

Master data







Material BOM Bill of Material LO-MD-BOM

Master data

Material classification Classification Valuation/Product

CA-CL Master data

Material consumption Product LO-MD Master dataMaterial - extend ex-isting record by new org levels

Product LO-MD Master data

Material inspection setting

Product QM Master data

Material inventory balance

Material Stock MM-IM Transac-tional data

Currently not available for transfer option Transfer Data from Staging Tables.

Material long text Product LO-MD Master dataMaterial trade classifi-cation

Product MM-IM Master data A prerequisite for this object (previously named Material Commodity Code) to be vis-ible is that either the Intrastat Processing (BDT) or the SAP Global Trade Services In-tegration - 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 re-spective scope item.

Pricing condition (general)

Price Condi-tion

SD-MD-CM, CO, MM-PUR

Master data

Pricing condition (pur-chasing)

Price Condi-tion

MM Master data

Pricing condition (sales)

Price Condi-tion

SD Master data

Production version Production Version

PP Master data

Profit center Profit Center FI, CO Master data Currently not available for transfer option Transfer Data from Staging Tables.



https://rapid.sap.com/bp/scopeitems/1WA

https://rapid.sap.com/bp/scopeitems/BDT





Purchase order (only open PO)

Purchase Or-der

MM-PUR Transac-tional data

Purchase scheduling agreement

Purchase Scheduling Agreement


Purchasing contract Purchase Con-tract


Purchasing info record- extend exist-ing record

Purchasing Info Record

MM-PUR-VM

Master data

Purchasing info record with conditions

Purchasing Info Record

MM-PUR Master data

QM/PM catalog code group/code

Inspection Code Group


QM selected set Inspection Se-lected Set


QM selected set code Inspection Se-lected Set


Routing Routing PP-BD-RTG

Master data

Sales contract Sales Contract SD Transac-tional data

Sales order (only open SO)

Sales Order SD Transac-tional data

Software/Hardware constraint

Software Con-straint

PLM-ESD-ESC

Master data

Source list Source List MM-PUR Master dataSupplier Supplier LO-MD-

BP-VMMaster data The KTOKK field must be in sync with your customizing of the BU grouping. Other-

wise, the grouping will overwrite the account group.







Supplier (deprecated) Supplier LO-MD-BP-VM

Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be removed with the next delivery. Use Supplier instead.

Supplier - extend ex-isting record by new org levels

Supplier LO-MD Master data

Supplier- extend exist record by new org levels (deprecated)

Supplier LO-MD Master data This object is deprecated, because the underlying API will not be supported in future releases. It will be removed with the next delivery. Use Supplier - extend existing record by new org levels instead.

VC - Variant configu-ration profile

Variant Con-figuration Pro-file

LO-VC Master data

Work center Work Center PP-BD-WKC, QM

Master data

Xceptional case - Ma-terial price chng for global currencies

Product CO-PC-ACT

Master data

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 ca-pabilities of the underlying API to load the data. Starting with SAP S/4HANA 1610 FPS2, you can enhance customer projects based on these delivered stan-dard migration objects or you can create your own objects using the SAP S/4HANA migration object modeler (transaction LTMOM). We therefore recommend 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.



https://launchpad.support.sap.com/#/notes/2481235

4 Business ConditionsBefore this scope item can be tested, the following business conditions to be met:

Scope Item

Business Condition

Content is activatedOrg. structures and additional settings are made



5 Preliminary Steps

UseIn this step, you set up user settings that are necessary for migrating your data.

5.1 Create Role from TemplateUseIn this step you create the role from the Technical Roles section for the data migration user that is necessary for migrating your data.Procedure1. Access the Roles transaction using one of the following navigation options:

Option Navigation pathTransaction Code

PFCG

SAP Menu Tools > Administration > User Maintenance > Role Administra-tion > 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, 069. 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.ResultYou have created the role to use the SAP S/4HANA migration cockpit.

5.2 Create Data Migration User and Assign the RoleUseIn 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.Procedure1. Access the Users transaction using one of the following navigation options:

Option Navigation pathTransaction 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.ResultYou have created the data migration user and assigned the data migration role to it to use the SAP S/4HANA migration cockpit.



6 Overview TableThis scope item consists of several process steps provided in the table below.

Process Step UI Type Business Condition Expected ResultsStart the SAP S/4HANA Migration Cockpit [page ] 15

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

The migration cockpit is displayed.

Create Migration Project [page ] 16

Migration cockpit (Web Dynpro via SAP Fiori launchpad)

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

A migration project is created.

Open Migration Object [page ] 17


This section describes how you open a migration ob-ject in the migration project.

A migration object is opened.

Download Migration Template [page ] 19


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

The Microsoft Excel XML Spreadsheet 2003 template is downloaded.

Prepare Test Data [page ] 20

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

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

Upload Migration Tem-plate and Verify Data [page ] 23


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

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

Transfer Migration Tem-plate Data [page ] 25


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

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

Validate Imported Data using SAP S/4HANA Busi-ness Apps [page ] 29

SAP Fiori launchpad This section describes how you validate complete-ness and correctness of the migrated data in the tar-get SAP S/4HANA system using corresponding busi-ness functions.

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



7 Test ProceduresThis section describes test procedures for each process step that belongs to this scope item.

7.1 Start the SAP S/4HANA Migration Cockpit

Test AdministrationCustomer 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.

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

Procedure

Test Step #

Test Step Name Instruction Expected Re-sult

Pass / Fail / Com-ment

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 trans-



Test Step #

Test Step Name Instruction Expected Re-sult

Pass / Fail / Com-ment

action.

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.

ResultThe SAP S/4HANA migration cockpit appears.

7.2 Create Migration Project



Enter a test date.

Business Role(s)


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



https://help.sap.com/viewer/29193bf0ebdd4583930b2176cb993268/latest/en-US

Procedure

Test Step #

Test Step Name Instruction Expected Result Pass / Fail / Com-ment

1. Create Migration Project

Choose Create on the Migrate Your Data home screen.

The Create Migration Project dialog win-dow 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 exam-ple, 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.

ResultYou 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



Enter a test date.



Business Role(s)


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

Procedure

Test Step #

Test Step Name

Instruction Expected Result Pass / Fail / Com-ment

1. Open Migration Project

Choose the migration project you previously created in section Create Migration Project [page ] 16 on the Migrate Your Data home screen.

The Migration Project overview ap-pears.

2. Optional: Filter on Migration Status

On the Migration Objects tab, select the Migration Status column and choose one of the two statuses In Process or Not Started. You can find the different statuses at the bottom of the context menu.

The migration objects are filtered as per status. Only objects with the se-lected status are displayed.

3. Open Migration Object

On the Migration Objects tab, select the table row containing your mi-gration object.Once the confirm dialog window appears, choose OK to copy the se-lected migration object to your customer project.

ResultThe migration object has been copied from the SAP standard migration object into a customer migration object and the Migration Object Details screen ap-pears.



7.4 Download Migration Template



Enter a test date.

Business Role(s)


UseThis 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 Template

Choose Download Template on the Source Files tab of the Migration Object overview.The template will automatically be downloaded.

The migration template is downloaded and saved on your local PC.

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.



ResultThe 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



Enter a test date.

Business Role(s)


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

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



Important InformationCaution 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 dur-ing 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 migra-

tion 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 re-

spective 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 exam-ple, 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 ] 32 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 Step #

Test Step Name


1. Open Down-loaded Migration Template

The Microsoft Excel XML Spreadsheet 2003 migration template files consist of differ-ent sheets, which are visible at the bottom of the file. You use the different sheets to specify the data belonging to different data structures. Some sheets are mandatory, and some are optional.Select the migration template on your local PC and open it using Microsoft Excel.

Microsoft Excel displays the migration template.

2. Read Introduc-tion and Field List

Read the Introduction to familiarize yourself with the template and its usage. Check the Field List to determine mandatory and optional sheets or structures.

You know the manda-tory sheets and fields and how to maintain



https://help.sap.com/viewer/d5aa3caabab04bb68d9cc3352d003330

https://help.sap.com/viewer/25d2ae41d2d74803be976f9c4bda6986

https://help.sap.com/viewer/29193bf0ebdd4583930b2176cb993268/latest/en-US/974c5c1dded14529b786f95799de463f.html

Test Step #

Test Step Name


the template.3. Enter Test Data

in Mandatory Sheets Manually

Enter your test data in all mandatory sheets of your migration template. Fill all mandatory columns.Note Mandatory columns are marked with an asterisk (*). Fields are only mandatory if a record exists. It doesn’t make sense to provide records where only the key fields are filled. For further details, read the Appendix and the respective migration object docu-mentation.

The migration template contains the data of the mandatory sheets.

4. Enter Test Data in Optional Sheets Manually

Enter test data in the sheets of your migration template, which are not mandatory.Note Mandatory columns are marked with an asterisk (*). Although an optional sheet may contain mandatory columns, if the sheet is not relevant for your project, there is no need to fill the mandatory columns in the sheet with data. For further details, read the Appendix and the respective migration object documentation.

The migration template contains data of sheets, which are not manda-tory.

5. Save the File To save the data on your local PC choose Save in the Microsoft Excel application.Note If you save the file, be sure to only save it as Microsoft Excel XML Spreadsheet 2003 file. Other file types are not supported by the migration cockpit and lead to er-rors when trying to upload them.

The migration template containing test data is saved on your local PC.

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

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



7.6 Upload Migration Template and Verify Data



Enter a test date.

Business Role(s)


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

Procedure

Test Step #

Test Step Name


1. Open Migra-tion Cockpit

Open Migrate Your Data. The Home page appears.

2. Open Migra-tion Project

Select the table row containing your project in the Available Migration Projects table and choose Open.

Migration Project Details screen appears.

3. Select Migra-tion Object

Switch to the Migration Objects tab and select the table row containing your migration object. Choose Open.

The Migration Object Details screen appears.

4. Upload Mi- Choose Upload File. The File Upload dialog window appears.



Test Step #

Test Step Name


gration Tem-plate

5. Open File Browser of your local PC

Choose Browse to select the corresponding migration template from your local PC.

The file browser of your local PC appears in a dialog window.

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 win-dow.

7. File Upload Fill in the fields of the File Upload dialog box:● File Name: <Unique name of your migration template>.● Description: <Meaningful description>.● Comment: <Optional comment>.

Note The error File named <File name> al-ready assigned; specify a different file name will occur if you choose an already existing file name.Note The error Upload canceled; file struc-ture not consistent with active view struc-ture will occur if you choose a migration template that is not compatible with the structure of the current release.

8. Upload Choose Upload to load the data from the migration template into the staging area of Migrate Your Data.Caution Dependent on your internet browser and the browser version, it might be that you receive an error message, such as Error when up-loading 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.

Your file appears in the overview list of the Source Files area.

9. Activate File for Migration

Select your file from the overview list of the Source Files area and choose Activate.Note In case that the overview list contains multiple files that have not yet been finished, select the files and choose Deactivate to avoid re-processing. Only activate those files that you really want to load. If you start the transfer process, all(!) activated files are transferred.

Your file is active and marked with a green status icon.

10. Open File to Verify the

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 displayed.



Test Step #

Test Step Name


Data In the Data Records area, the uploaded data records are displayed. The structure resem-bles the migration template structure. Each worksheet of the migration template is dis-played as a single tab.

11. Verify the Data

Choose the different tabs and verify that the data of your migration template is correctly loaded into the data staging area.Check whether all records have a valid key and that no records are empty.

The file is consistent and does not contain any empty records.

12. Finish the Verification

Choose the < Back button to go back to Migration Object Details screen.

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

7.7 Transfer Migration Template Data



Enter a test date.

Business Role(s)




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

Procedure

Test Step #

Test Step Name


1. Open Migra-tion Cockpit

Open Migrate Your Data. The Home page appears.

2. Open Migra-tion Project

Select the table row containing your project in the Avail-able Migration Projects table and choose Open.

The Migration Project Details screen appears.

3. Select Migra-tion Ob-ject

Switch to the Migration Objects tab and select the table row containing your migration object. Choose Open.

The Migration Object Details screen appears.

4. Start Transfer

Select your file from the overview list of the Source Files area and choose Start Transfer to migrate the data from your file.Note A guided activity controls the data migration process. Execute all steps one after another.

The Guided Activity screen appears in a separate browser win-dow and data validation is in progress.

5. Validate Data

Choose Close to close the dialog window when the progress reaches 100%.Note You can ignore error messages regarding value mappings. These are fixed in the Convert Values step.

The Validate Data screen is displayed, showing the notifications of the validation run.Note The message Information required; specify mapping val-ues in step 'Convert Values' is not an error message: You can



Test Step #

Test Step Name


Correct all other occurring errors. In case that data changes in your source file are required to solve the er-ror, select the file, choose Download, and save it on your local PC. After changing the data, repeat activity Transfer Migration Template Data [page ] 25 once again.

transfer a record only once into a system. A unique record is identified by a combination of its value and associated key fields in the migration template. If you get the message Source record for example MATNR=M12345 already transferred to tar-get system., it 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 oc-cur 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 success-fully 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. Navi-gate to Next Step

Choose Next to navigate to the next step. The Convert Values screen is displayed, showing a list of all your open tasks.

7. Convert Values

Convert values for data that needs to be mapped before it can be transferred to SAP S/4HANA. For more informa-tion on this step, refer to the Convert Values [page ] 32 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 func-tion. If the values are correct, all chosen open value map-pings will be confirmed.

All values are properly mapped for conversion.

8. Navi-gate to

Choose Next to navigate to the next step. The Simulate Import screen is displayed.



Test Step #

Test Step Name


Next Step

9. Simu-late Im-port

The target system validates the data. No data is posted to the target system.Choose Close to close the dialog window when the progress reaches 100%.If errors are found, correct them and choose Repeat Sim-ulation 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 ] 25 once again.

If no errors are found, proceed with the next step.

10. Navi-gate to Next Step

Choose Next to navigate to the next step. The Execute Import screen is displayed, showing the dialog win-dow with the progress bar of the currently active import run.

11. Execute Import

Choose Close to close the dialog window when the progress reaches 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.

The data import is finished successfully without errors.

12. Com-plete the Process

Choose Finish to complete the currently active Guided Ac-tivity.Note In case of errors, a Delta File is created. The Delta File contains only the erroneous records. To download it, choose Download, and save it to your local PC. After you have corrected the errors, repeat activity Transfer Migra-tion Template Data [page ] 25 once again using the Delta File.

The guided activity window is closed and the Migration Object Details screen appears.



ResultThe 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



Enter a test date.

Business Role(s)


UseThis 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 Step #


1. Access the Corre-sponding App or Transaction

Open the corresponding app or transaction of the SAP S/4HANA system and check completeness of the imported data.

All data from the Microsoft Excel XML Spreadsheet Template 2003 is displayed in the corresponding SAP S/4HANA app or transaction.



Test Step #


Note Check the migration object documentation for the app and the needed business role to vali-date the data in the system.

ResultAll 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 ObjectsSome 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.ExampleThe 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 on-wards. You process the dependent migration objects, including Material BOM and Activity type. You ensure that the data you specify in the files for these ob-jects is only valid from 10 January 2015 onwards.



8.1.3 Migration Template File SizeThe 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_re-quest_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 stan-dard 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

UseA 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 be-tween 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.

PrerequisiteIn 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.

Procedure1. 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 DescriptionFixed 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.Data Migration to SAP S/4HANA from File (BH5)Purpose


https://help.sap.com/viewer/fe1dfb6e6c551014b6f1befabc903d5d/7.02.19/en-US/483e87b3ca6b72d0e10000000a42189c.html

Task Type DescriptionMapping Rules Here you can map source values to target values. The rule names always start with the word "mapping".Control Parame-ters

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 al-lows 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).

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.

ResultYou 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 ConfigurationTo create objects of a configuration model in SAP S/4HANA 1802, create the objects in the following order:



# Object Name Manual Cre-ation Only

Comments

1. Change number (optional)

X If you want to use a change number, create a new change number first.

2. Document info record

X

3. Characteristic Dependencies must be added manually.4. Class5. VC - Variant table

structure6. VC - Variant table

entry7. VC - Object depen-

dencyOnly for global dependencies. Create object dependencies with status Released. In case of a syntax error in the dependency the creation of this dependency will be prevented.

8. Material9. Material classifica-

tion10.

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 StatusIf 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.

ExampleIn 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 mes-sage 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 FilesThe 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.

ExampleYou 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.Data Migration to SAP S/4HANA from File (BH5)Purpose


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, push-buttons 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 data-base tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Exam-ple>

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, F2 or ENTER .



www.sap.com/contactsap

© 2018 SAP SE or an SAP affiliate company. All rights re-served.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permis-sion 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 Ger-many and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for addi-tional trademark information and notices.Some software products marketed by SAP SE and its distribu-tors contain proprietary software components of other soft-ware vendors.National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representa-tion or warranty of any kind, and SAP SE or its affiliated com-panies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affili-ate 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 addi-tional warranty. In particular, SAP SE or its affiliated companies have no obli-gation to pursue any course of business outlined in this docu-ment 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 platform 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 obliga-tion to deliver any material, code, or functionality. All for-ward-looking statements are subject to various risks and un-certainties 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.

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark

Purpose - wiki.myftp.orgwiki.myftp.org/sap/.../BH5_S4HANA1809_BPD_EN_XX.docx · Web viewSAP...

Documents

Transcript of Purpose - wiki.myftp.orgwiki.myftp.org/sap/.../BH5_S4HANA1809_BPD_EN_XX.docx · Web viewSAP...