Migrating data from SAP ECC to SAP S4/HANA with the migration cockpit

[marcobuescher]

Migrating data from SAP ECC to SAP S/4HANA is a crucial step for companies that want to benefit from the improved functionality and performance of S/4HANA. Effective data migration is crucial for a smooth transition and the success of your project. The Migration Cockpit is a powerful tool designed specifically for this purpose, helping companies to migrate data quickly, easily and reliably.

In its simplest terms, data migration involves extracting data from one system and loading it into another. In practice, however, this is rarely possible without transforming the extracted data before loading it into the target system. The transformation can contain formatting values that fit into the target fields. You can also use this phase to ensure the quality of your data (e.g. to identify and eliminate duplicate master data).

The data migration process follows the extract - transform - load approach. At the start of a project, you define the migration objects that you want to use. Each migration object describes a specific type of data, e.g. bank master record, customer, supplier, etc. In the migration cockpit, you can see which migration objects depend on others. For example, to migrate cost centers, you must first migrate your profit center structure.

The data migration process is based on an approach that includes extraction, transformation and loading. At the beginning, the migration objects are defined, which describe different types of data, such as bank master records, customers or suppliers. The dependencies between the migration objects become visible in the migration cockpit. For example, the migration of cost centers requires the prior migration of the profit center structure.

Once the relevant migration objects have been defined, the data is retrieved from the source system, depending on the migration method selected. The data is then assigned to the corresponding fields in SAP S/4HANA, with automatic mapping suggestions providing assistance. Transformations may also be necessary to adapt the data to the requirements of the SAP S/4HANA system, such as converting "GER" to "DE" for country codes.

Simulating the data migration makes it possible to identify potential errors without actually saving the data. After a successful simulation, the actual migration takes place, during which the data is saved in the system. In the event of errors, these can be identified, corrected and reprocessed in the migration cockpit.

 

The first approach to data migration uses staging tables, which serve as a cache for data. These tables are filled with data from the source system and the "Migrate data" app collects this data from the staging tables for migration.

The source system can either be an SAP system or a third-party system. With this approach, you have the option of downloading an Excel template into which you can load the data from your source system. You can then upload the content of the Excel file to the staging tables. Alternatively, you can fill the staging tables directly with SAP Data Services, your own SQL programming or a third-party ETL tool.

The third approach to data transfer is direct transfer. Here, the SAP S/4HANA system collects the data directly from the source system. The source system must be either an SAP Business Suite system, SAP Apparel and Footwear, SAP CRM or SAP EWM.

The advantage of this approach is that it is suitable for any amount of data. As the data is transferred directly from the source system, there is no intermediate step of storing it in staging tables. This can be particularly advantageous if real-time data transfer or large volumes of data are required.

Here I show you how to perform a migration.

App Migrate Open your data.
Migrate data using staging tables	Assign a name for the migration project
Assign the project to an existing package	At this point, you can select the migration object that you want to migrate.
It must then be checked.	It can be created by clicking on the "Create Project" button.
Progress can be observed in the monitoring map.	Basic mapping tasks must be carried out.
Download template	Upload completed file
First click the Upload button. The validation starts automatically.	This step can also be observed via Monitorig.
Progress can be observed under Monitoring.	Warnings Errors Successes can be viewed using the "Show messages" button.
	Any parameters can be mapped and confirmed under Mapping tasks.
Prepare migration.	Prepare staging tables. Click the Prepare staging tables button here.
This point can also be observed under Monitoring.	After completing the preparation, you can view the errors, warnings, successes and information and correct errors if necessary.
	You can then perform the mapping tasks again.
Mapping	Mapping
Next point, simulate.	For example, you can simulate with 10% of the data.
The progress can be observed in the monitoring.	Errors can be analyzed with "Show messages".
Trigger migration process	Trigger the migration of data.
Information message	Migration started,
The progress of the migration can also be monitored.
Unsuccessfully migrated data records can be reprocessed separately in a correction file. in this case 10 data records.	These ten data records can be reworked and must then be migrated again.