3140364 - Cannot migrate data for migration objects after upgrading to SAP S/4HANA 2202 – Migrate Your Data App - Staging Approach

You want to migrate data for a migration object that was copied from an existing project. The system informs you that it is not possible to migrate data for such migration objects.

SAP S/4HANA Cloud

• Migrate Your Data – Migration Cockpit
  
  • Migrate Data Using Staging Tables

With SAP S/4HANA Cloud 2111, it is possible to create a new project that is a copy of an existing project. However, the migration objects that are copied to the new project cannot be updated with content from SAP and so cannot be used to migrate data in later SAP S/4HANA Cloud releases.

As the migration objects that were copied to the new project cannot be updated with content from SAP, newer versions of these objects may be available. Using older versions of migration object to migrate data to SAP S/4HANA could result in serious inconsistencies and is therefore not permitted.

Example

In SAP S/4HANA Cloud 2111, you create a new project that is a copy of an existing project. You upgrade your system to SAP S/4HANA Cloud 2202. You can access your copied project but cannot use the copied migration objects in the project to migrate data to SAP S/4HANA Cloud.

We recommend creating a new project in your SAP Cloud 2202 system, and adding the relevant migration objects to the project.

Note that you can still access the copied project and download mapping values for the migration objects. If required, you can then upload these mapping values for the relevant migration objects.

S4HC, cloud, copy, copied, migration object, migration project, upgrade, mapping values, 2202, 2111 , KBA , CA-LT-MC , S/4HANA Migration Cockpit , Problem