Migration Cockpit - A basic guide

[Former Member]

I have created this guide to show the basic steps to create and execute a project using the Migration Cockpit.  It was documented using S/4 Hana 2022 On Premise.

Configuration within each system will vary so these steps may need to be modified to address your needs but this basic scenario will help you to get started.

Migration Cockpit

Fiori App F3473 Migrate Your Data

Information on standard user roles required to complete these steps can be found in the Fiori Apps Library for the mentioned app.

 

Example Scenario

In this example I will assign the Class “CONTROLLER” to Material 000000000000000015 with value “NAV_COMM” for Characteristic “AVIONICS”

Material Classification view before migration shows there is no Class assigned currently:

Create Project

Create your project using Staging Tables.  This will allow for import of data from excel template files.

Migrating Data Directly from SAP System requires RFC connection set up to the source system and would be used for Extraction of data from that source system.

Select the objects in scope.  Note there may be more than one version of an object.  In the case of Classifications there is the general template and the object specific templates.  Select objects by checking the box to the left and then use the right arrow in the middle of the screen to add them to your scope. Then click on the Review button

Where relevant, you will receive a warning regarding predecessor objects.  It is not always necessary to include each of these in your scope as you may be managing them via alternative methods, including manually, or they may already exist – perhaps your migration project is simply to update existing objects.   Review the list and update your scope as necessary.

Review your settings, edit if necessary and then click Create Project.

Edit Project

It is possible to edit some of the settings you made in the Create Project step but there are also some additional settings that can be made.

From the home screen select your project and then click Edit

In General Data you can rename your project and define Custom Scope

In Migration Objects you can change the scope of objects

In CSV File Options you can manage some technical settings for the file import

In Technical Information you can define the retention period for the data in the staging tables.

Managing Your Project

Enter your project to begin managing each object

For each object there is a set list of steps or Actions.  Select your object and then the next Action from the dropdown menu.   Each Action is described in the following sections.

 

Download Template

There are two options for downloading the object templates:  xml and csv.  The xml file is actually presented in Excel and includes instructions, a field list (which can also be used as the basis of a field mapping document) and a separate sheet for each sub object.   These correlate to the sections in the field list, which are tables in the structure.

The csv option will provide you with a zip file containing the csv files for each of the sub objects/tables.  These correlate back to each sheet in the xml.

The xml is a little more user friendly.

In this screenshot you can see that the Header sheet in the xml is managed as a separate csv file in the master zip file. 

Upload Template

When choosing the Upload Template action, in addition to uploading your csv or xml files – or drag and dropping them – you can also review the staging table structure and review documentation about the migration object.  This is very useful information.

Drag and drop or upload your completed template.  The system will validate and notify you of issues.  Once resolved it should confirm successful import of the file.

Prepare

If you are using standard template files the system checks the consistency of the data in the staging tables but it will provide the option to perform this check at this point for those who imported data via another tool.

Once you choose to Prepare Staging Tables you can monitor progress via the Monitoring button in menu bar

Resolve any errors before proceeding to Mapping Tasks.  You may need to delete the uploaded data, correct the issue in the file and then re-upload.

Mapping Tasks

You can proceed to the Mapping Tasks step directly from the previous step as shown in previous screenshot or from the home screen for the project.

You now need to map your data :

For each attribute, confirm the source to target mapping.  The system will default the target value to be the same as the source value.  You can overwrite this if you need to.  Each value must be Confirmed, even if you are accepting the defaulted value.

Simulate

You will now perform a simulation run to validate the data load and expectations.  It can be run for all instances, random or custom selections.  Errors will be presented and must be resolved until your simulation run is clean and “Migrate” is available as the next Action.

Migrate

Click on the Action value “Migrate” and then choose which records to process.  Start your migration.

As before, the screen will refresh periodically to show progress but you can also choose the Monitoring button to get up to date progress.  Final status will be presented to the screen.

All data was successfully migrated and we can now check the results.

Material Classification view after migration, shows Class and Characteristic value assigned.

The Action step reverts to “Upload” to allow you to run additional files.  Note, you will need to map any new values that appear in the source data each time.  It is possible to enhance the mapping behavior of each object within a migration project using Gui transaction LTMOM which is the Migration Object Modeler.   This would be considered more of a technical task.

Finishing a Project

When all migration activities are completed for a project it is expected that you will mark it as Finished.  This will prevent any further activities being performed or changes being made.  It will also begin the countdown with regard to the data retention period.

If you are creating a project for ongoing upload of data then do not set it to Finished.