Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Elizaveta2
Advisor
Advisor

Lately, it was recognized that some users have problems with deleting a large amount of data (uploaded file=uploaded instances). When you select all the instances and use the “delete instances” button, the first 50 instances will be deleted. This is a Fiori behavior, and, from the migration cockpit perspective, we can not influence it.


This is a good point to use Mass Processing! The functionality is available as of SAP S/4HANA 2020 and SAP S/4HANA Cloud 2008.


I would like to emphasize that if you delete the instances after the migration, the data will not be deleted in the target system. With the instance deletion, you just clear the instances from the staging tables. It is helpful for testing purposes.

Alternatively, you can check this 2-minutes video instead of reading it.

1) In Migration Object Instances view, click Mass Processing:


2) Choose Delete Instances action and proceed with Step 2:



3) If you want to delete all instances, just proceed with Step 3. Otherwise, apply the needed filtering.

4) Check the selected data and click Review.


5) Start the deletion process:


The uploaded data has been deleted! Refresh the screen.


The data is deleted!

Now you may want to delete the mapping tasks. They are not deleted automatically with the instances. I will explain the shortest way to do it. This is available since SAP S/4HANA 2021 release.

Go back and select the mapping tasks. To delete the mapping task (or many mapping tasks), you need to upload the empty mapping values in the format of XML files. The easiest way to do it is to download the mapping templates and upload these empty mapping templates back.

Congratulations! The mapping tasks have been deleted.

Best regards,

SAP S/4HANA migration cockpit, Product Management team
2 Comments