Skip to main content

SAP S/4HANA Migration Cockpit Direct Transfer

Published on 4 May 2021
SAP S/4HANA Migration Cockpit Direct Transfer
Sreeregha Nair
Sreeregha Nair
SAP Data Migration Associate

Sreeregha Nair has an extensive experience handling multiple Data migration projects for Retail SAP business and has worked on migration projects of Grocery chains as well as in numerous internal product development. Sreeregha is transforming data ecosystems for clients with innovative data migration technologies.

Chris Lloyd Fernandez works with Applexus as Data Migration Associate. He is passionate about the nuances of data processing and its migration across cross-platforms and have hands-on experience in assisting the industry leaders hand-in-hand in their multiple projects in Data migration.

Introduction

The SAP S/4HANA migration cockpit facilitates the transfer of business data from an SAP ERP source system to SAP S/4HANA. The SAP S/4HANA migration cockpit uses migration objects to identify and transfer the relevant data. A migration object describes how to migrate data for a specific business object to SAP S/4HANA. It contains information about the relevant source and target structures, as well as the relationships between these structures. It also 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. SAP provides predefined migration objects that you can use to transfer your data.

An RFC connection connects the SAP S/4HANA migration cockpit to the SAP ERP source system. The SAP S/4HANA migration cockpit selects data from the source system by using specific criteria. For example, suppose you are using the migration scenario SAP ERP to SAP S/4HANA, in that case the SAP S/4HANA migration cockpit selects data using company codes (you specify the relevant company codes when creating a project).

 

General Process

The general process for migrating data to SAP S/4HANA is as follows:

  • In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data app in the Fiori Launchpad.
  • You create a migration project and select the migration objects that are relevant to your project. Migration objects are delivered by SAP and describe how to migrate data from the source system (which tables are needed and the relationships between the tables) to SAP S/4HANA.
  • Note that you typically first create a project in a test system which is a copy of the production SAP S/4HANA system. For each new test transfer, you create a new migration project that includes any corrections or refinements identified in the previous test. When you are finally ready to transfer your data to the production SAP S/4HANA system, you can create a project in the production system.
  • For each migration object, the SAP S/4HANA migration cockpit selects the relevant data from the source system. Note that the system selects data from the source system based on specific criteria. For example, if you are using the migration scenario SAP ERP to SAP S/4HANA, then you select data using company codes (you specify the relevant company codes when creating a project).
  • For each migration object, you process any open mapping tasks.
    There are mapping tasks associated with migration objects that must be processed before the migration can proceed. Examples of mapping tasks include Value Mapping tasks (where you specify target values for corresponding source values) and Fixed Value tasks (where you set default values for target fields).
  • Optional: You simulate the transfer of data to the target SAP S/4HANA system.
  • You migrate data for the migration object to the target SAP S/4HANA system.

Migrate Your Data

With this app, you can migrate business data directly from an SAP ERP source system to SAP S/4HANA.

Key Features

You can use this app to:

  • Migrate data to SAP S/4HANA using the following supported migration scenarios:
    • SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA
    • SAP ERP to SAP S/4HANA
    • SAP EWM to Decentralized EWM
  • Create migration projects to specify the data that you want to transfer, and monitor the migration status.
  • Select the migration objects relevant for your migration scenario (the app uses migration objects to identify and transfer the relevant data).
  • Select data from the source system for the selected migration objects.
  • Process any mapping tasks for the migration objects.
  • Simulate the migration before migrating your data to SAP S/4HANA, and monitor the status of the simulation process.
  • Migrate your data to SAP S/4HANA, and monitor the status of the migration.
SAP S/4HANA Migration Cockpit Direct Transfer

Creating Migration Projects

Context

You use migration projects to facilitate the transfer of data from a source system to SAP S/4HANA. In order to migrate data to SAP S/4HANA, you must first create a migration project. You use a migration project to specify the data that you want to transfer and to monitor the status of the migration.

Typically, you first create a project in a test system which is a copy of the SAP S/4HANA production system. The more the data in the test system resembles the data in the production system, the more precise your test will be.

Usually, several test data migrations are required before you transfer data to the SAP S/4HANA production system. For each new test transfer, you create a new migration project in the test system that includes any corrections or refinements identified in the previous test. If you have adjusted migration objects using the SAP S/4HANA migration object modeler (transaction LTMOM), the changes need to be done again for any subsequent projects.

To avoid specifying all mapping values again in your newly created project, you can download the mapping values from your previous test and upload them to your new project. You download the mapping values using the SAP S/4HANA migration object modeler (transaction LTMOM).

When you are finally ready to transfer your data to the SAP S/4HANA production system, you create a project in the production system. The migration is client-specific, so you create your project in the relevant client of the target SAP S/4HANA system.

To create a migration project, proceed as follows:

  • In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data app in the Fiori Launchpad.
  • Select Create. The system displays the New Migration Project screen.
  • On the New Migration Project screen, under Header, you specify the following information:

Scenario:

The migration scenario. The following migration scenarios are available:

  • SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA
  • SAP ERP to SAP S/4HANA
  • SAP EWM to Decentralized EWM

Note: Different migration objects are relevant for different scenarios. The system displays the relevant migration objects based on the selected scenario.

Connection to Source System:

The RFC connection from the SAP S/4HANA system to the source system.

  • Under Select Data, you specify the relevant criteria that is used to select the data for the relevant migration objects.

Note: The SAP S/4HANA migration cockpit uses migration objects to transfer data to the target SAP S/4HANA system. The data for the migration objects are selected from the source system based on specific criteria such as company codes. For example, if you use company codes, only data relevant to the specified company codes will be selected from the source system. In this way, you restrict the data that is transferred to the target SAP S/4HANA system for the relevant migration objects.

In the SAP S/4HANA migration cockpit, you can only restrict the selection using specific criteria such as company codes. In the SAP S/4HANA migration object modeler (transaction LTMOM), you further restrict the selection if required.

  • Under Migration Objects, the system displays the relevant migration objects based on the selected migration scenario. You select the migration objects that are relevant to your project.

Used in Projects:

You can view whether the migration object is used in any other projects.

Description:

To view detailed documentation for the migration object, select the Description link.

  • Review your settings, and click Save to create your project.

STEP : 1

SAP S/4HANA Migration Cockpit Direct Transfer

STEP : 2

SAP S/4HANA Migration Cockpit Direct Transfer

STEP : 3

SAP S/4HANA Migration Cockpit Direct Transfer

STEP : 4

SAP S/4HANA Migration Cockpit Direct Transfer

The Migration Project Screen

When you open a migration project, the system displays the Migration Project screen. On the Migration Project screen, you trigger all the steps that are required to transfer the data for each migration object to the target SAP S/4HANA system.

For each migration object, these steps are:

  • Selecting the data from the source system
  • Processing any open mapping tasks
  • Simulating the migration to the target SAP S/4HANA system (optional)
  • Migrating the data for the migration object to the target SAP S/4HANA system

You carry out these steps for each migration object that is part of your project. If a migration object has a predecessor object, the predecessor object must be processed first. You can view whether a migration object has a predecessor object in the Migration Object column.

The Migration Project screen contains the following columns:

Migration Object

In this column, you can view the name of the migration object and also any predecessor objects. To view detailed information about a migration object, click a migration object name in this column. The system displays the Migration Object screen. For more information, see Additional Information About Migration Objects.

In this column, you can also adjust the maximum number of background jobs that are used for the migration object. Note that the default number of background jobs for a project is 15. By default, the jobs are distributed equally among the migration objects. You can change the number of background jobs for a project in the Project Settings screen. To open the Project Settings screen, choose Settings.

Data

In this column, you can view the number of migration object instances that have been selected from the source system for each migration object. You can also view the number of excluded migration object instances.

Mapping Tasks

In this column, you can view the number of open and completed mapping tasks for each migration object.

Simulation

In this column, you can view the number of migration object instances that have been simulated successfully and the number of instances for which errors exist.

Migration

In this column, you can view the number of migration object instances that still have to be migrated to the target SAP S/4HANA system, as well as the number of migration object instances that have been migrated successfully, and the number of instances for which errors exist.

Migration Progress

In this column, you can view the status of the migration. If the migration has not started for a migration object, the text Migration Not Started is displayed. If the migration has begun for a migration object, you can view the following percentage values:

  • Percentage of instances migrated successfully
  • Percentage of instances with errors
  • Percentage of instances not yet started

Additional Information

Activity Tracking

To view a log of all activities, choose the Show Activity Tracking button. The system displays the Activity Tracking screen area. You can view the active activities (for example Migration Started) and completed activities (for example Migration Completed).

Mapping Tasks

You can view a list of all mapping tasks for all the migration objects in your project. For more information about tasks, see Mapping Tasks.

Finishing a Project

When you have finished your migration project, you can set the status of the project to Finished. When you set the status of a project to Finished, no further changes are possible. However, you can still view the project. To set the status of a project to Finished, choose the Finish button.

When you set the status of a project to Finished, you can specify a data retention period. The retention period is the length of time (in days) that the project and all associated data are kept in the system after you have set the status of the project to Finished. To do this, set the option Data Retention Period to On. The data will be deleted from the SAP S/4HANA system when the data retention time expires. If you set the option Data Retention Period to Off, then the project and all associated data will be kept in the system indefinitely. If required, you can change the retention time for finished projects. To do this, open the relevant project and choose the Settings button. You can find the settings for retention time on the Technical Information tab.

Project Settings

You can view the current settings for your project at any time by choosing the Settings button. The system displays the Project Settings screen, where you can view the following information:

  • The migration project name.

    If required, you can change the name of the migration project. To this, choose the Edit button, and enter a new name in the Name field.
  • The migration scenario.
  • The RFC connection from the SAP S/4HANA system to the source system.

In addition, you can view the following sections:

  • Select Data

    Under Select Data, you can view the relevant criteria that are used to select the data for the relevant migration objects.
  • Migration Objects

    Under Migration Objects, you can view the migration objects in the project. If required, you can add additional migration objects to your project. To do this, choose the Edit button, select the relevant objects and choose Save.
  • History

    Under History, you can view the different actions for the project (for example, Project Created or Simulation Failed). You can view the user who started the action and the start time and date, and the end time and date. You can also view the log for each action.
  • Technical Information

    Under Technical Information, you can view the following information:
    • Data Retention Period

      The retention period is the length of time (in days) that the project and all associated data are kept in the system after you have set the status of the project to Finished. If required, you can change the retention time for finished projects.
    • Number of Background Jobs for Projects

      You can adjust the maximum number of background jobs that are used for your project. The default number of background jobs for a project is 15. By default, the jobs are distributed equally among the migration objects. If required, you can also adjust the number of background jobs for specific migration objects. You can do this on the Migration Project screen.

      Example 1. You specify 20 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 10 background jobs for migration object A and 10 jobs for migration object B. Result: 10 jobs will run parallel to process migration object A, and 10 jobs will run in parallel to process migration object B.

      Example 2. You specify 20 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 100 background jobs for migration object A and 5 jobs for migration object B. Result: A maximum of 20 jobs will be used for object A, and a maximum of 5 jobs will be used for object B. The overall number of active background jobs for the project will not exceed 20 jobs.

      Example 3. You specify 1 background job for your project (in the Maximum Number of Background Jobs for Project field). You then specify 5 background jobs for migration object A and 5 jobs for migration object B. Result: 1 job will process migration object A and migration object B in a round-robin procedure.

Under Technical Information, you can also view general technical information about the project, such as the object ID. If you need to contact SAP for support, this information might be required.

Mapping Tasks

After the system has selected the data for a migration object from the source system, you need to process any open mapping tasks for the migration object before proceeding with the simulation or the migration. Examples of mapping tasks include Value Mapping tasks (where you specify target values for corresponding source values) and Fixed Value tasks (where you set default values for target fields).

On the Migration Project screen, you can view the number of open and completed tasks for each migration object in the Mapping Tasks column.

If a migration object has open tasks, click the relevant entry in the Mapping Tasks column. The system displays the Mapping Tasks screen. Alternatively, you can select the relevant migration object and choose the Mapping Tasks button.

 

Note

You can also display all mapping tasks for a project by choosing the Mapping Tasks button located in the top-right screen area.

Mapping Tasks Screen

On the Mapping Tasks screen, you can view the open mapping tasks (open mapping tasks have the status To be Confirmed) as well as any confirmed mapping tasks. The system displays the mapping tasks in a list. You can view the following information for each mapping task:

  • Mapping Tasks

    The name of the task.
  • Status

    The status of the mapping task. Mapping tasks can have the status Confirmed or To be Confirmed.
  • Type

    The type of mapping task. There are Value Mapping tasks (where you specify target values for corresponding source values) and Fixed Value tasks (where you set default values for target fields).
  • Values

    The number of values for the task, for example, a Value Mapping task, could involve specifying 10 target values.

You need to process the task by entering the relevant target values and confirming these target values. You can then set the status of the task to Confirmed. Once all mapping tasks for a migration object have the status Confirmed, you can proceed with the simulation or migration process for the migration object.

Add new comment

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.

About

We are professional and reliable provider since we offer customers the most powerful and beautiful themes. Besides, we always catch the latest technology and adapt to follow world’s new trends to deliver the best themes to the market.