Product Information
Delete the mapping task in the migration cockpit (Fiori UI, Migrate your data app)
With this blog, I would like to show you how to delete the whole mapping task in the migration project. As I have already mentioned in other blogs, please be aware that:
- you can not delete the whole mapping tasks of a control parameter and fixed value type.
- this “workaround” is available since SAP S/4HANA 2021 release and in SAP S/4HANA Cloud
Description: In some cases, there is a need to get rid of the whole mapping task with all mapping values. In the LTMC (old app) it was possible to delete the mapping task directly in the migration cockpit. With the new “Migrate your data” app this functionality is not enabled.
If you need to have the possibility to delete the mapping tasks directly in the app, please vote for this idea in the Customer Influence portal. The session is devoted to the SAP S/4HANA Cloud customers and partners. Improvement Request Details – Customer Influence (sap.com)
Solutions: to delete the whole mapping task with all the mapping values, you need to upload the empty file to the migration project. There are 2 ways how you can do it:
- Solution A: You download the mapping values in a form of an excel file to your laptop, delete the mapping values and upload the empty excel file back to the migration project
- Solution B: You can download the empty template to your laptop and upload this mapping excel file back to the migration project
I prefer to use Solution B because it involves fewer steps and helps you to save time by downloading the excel template and uploading it back without even opening it.
Let’s assume, you would like to delete one of the erroneous mapping tasks, for example, “Mapping of Academic Title”.
Solution A: 1) Select the mapping task and click Download Values.
2) Accept the warning message and go to the Monitoring screen to download the excel file.
3) In the Monitoring screen, click Download File. The zip file will be downloaded to your laptop.
4) Unprotect the excel sheet and delete the rows with the right-click.
5) Save the empty excel file under the new name. Go back to your migration project and click Upload Values.
6) Drag and drop the empty excel file to the migration project.
7) In the additional settings, choose to Replace Existing Values as the option for Loading Values.
8) You will get a warning message that the mapping task will be deleted. This is exactly what we want. Select the mapping task and click Upload Values.
9) Go back to your Mapping Tasks screen and refresh the page.
10) After the page is refreshed, you can see that the Mapping of Academic Title is deleted.
Solution B: 1) Download the empty mapping template of “Academic Title”. Click Download Mapping Templates.
2) Select Mapping of Academic Title template and click Download. The excel file will be downloaded to your laptop.
4) Drap and drop the empty template to the Upload Mapping Values screen.
5) Choose Replace Existing Values as the options for loading values. 
6) Select the mapping task and click Upload Values.
8) Go back to your Mapping Task screen and refresh the page.
The mapping task has been deleted!
Best regards,
SAP S/4HANA migration cockpit, Product Management team
Hello, is the a function the the roadmap to "refresh" the Mapping tasks, while leaving the already confirmed values there?
We are iterating the source files and sometimes we now have values to be confirmed in the mapping tasks that don't exist in the staging tables anymore....
Please help!
Best regards,
Tarran
Hello, yes you can refresh the mapping tasks. When you use "upload values" button, you have 2 options: to "replace existing values" or to "add values". In your case, you probably would like to use "add values" option. You can also confirm the added values at once. Check the migration cockpit overview presentation - slide 78 https://www.sap.com/documents/2017/07/26113ac0-c47c-0010-82c7-eda71af511fa.html
Best regards,
Elizaveta
Hello Elizaveta,
thanks for your reply.
The problem is, if I use the method described in this blog post, all values get deleted.
I need the "confirmed" ones to remain. We have a team working on the mapping tasks while another team changes the data in the staging tables. Now the mapping team is trying to map tasks and values that don't exist anymore.
It would be really great to be able to refresh the tasks and "delete all unconfirmed"...
Is there any way to do this?
Best regards,
Tarran Durham
Hello, I see. I would propose the workaround - you download all the mapping values of your project locally (incl. the confirmed one). Delete the mappings that you don't need (that are not confirmed) in the XML..and upload everything back while using "replace" and "confirm values automatically". In the end, you will have all the mappings confirmed and unconfirmed deleted. Do you know what I mean?
I know this is only a workaround..it is already into consideration how to make it more convenient for the users.
Best regards,
Elizaveta
Hi
the problem with this is that we don't necessarily know what values are removed or it isn't efficient to go through every mapping task and do this several times a week...
Either we need a further column in the excel of the mapping task with "Status" or the cockpit has a refresh feature...
Thanks and best regards,
Tarran
Hello again,
to clarify: I have read your great post about updating tasks: https://blogs.sap.com/2022/04/11/maintaining-the-mapping-values-with-download-upload-functionality-sap-s-4hana-migration-cockpit/comment-page-1/#comment-626662
This is good, but we need to go one step further. Within a mapping task, when you click in to the task you see the entries. Here for your example we have 69 Suppliers and 50 of them are confirmed and 16 of them are filled in but not confirmed.
Now we change the underlying instances and remove the 16 suppliers. How do we update the mappings without knowing WHAT underlying data was removed? If I download the entire mapping Task "Mapping of Supplier" then I don't see which ones are not in the staging tables anymore....
Please help..
Best regards,
Tarran
Hello Tarran,
you can just leave the non-confirmed mappings and proceed with the simulation. You will not get any errors if the mappings for the remained instances are confirmed. If some of the mappings for remained instances are not confirmed - you get errors during simulation steps with the error messages where you can see which mappings should still be confirmed. You will not get any error messages for the mappings that do not belong to any instances, so you can just leave them open.
Best regards,
Elizaveta
Hello Elizaveta,
we are doing this, it just causes a lot of confusion for the users who have to do the mapping tasks. Is there any plan on implementing this feature request or should we change our approach?
Best regards,
Tarran
Hi Elizaveta Kozhevnikova , the described method isn't working. I downloaded empty templates, then uploaded them back and got a validation error:
Blank template validation error
"Show Messages" clearly indicates what the issue is:
Error message
Consequently, there are no available mapping tasks in the "Additional Settings" and therefore there is no way to replace existing values with the blank template:
Missing mapping tasks
If SAP closed this back door, then the feature of cleaning up/resetting/unconfirming value mappings is really needed. It will be appreciated by lots of people, i'm sure. It's a shame that not many know about the voting on this feature on the Ideas portal... But if I'm doing something incorrectly, please advise on how to clean up the value mappings. Thanks.
Kind regards,
Vlad.
Hello Vlad, this workaround to delete the mapping values is available in SAP S/4HANA Cloud and SAP S/4HANA on-prem since 2021 release (i assume you are on the lower SAP S/4HANA release). Thanks for mentioning it, it's worth emphasizing in the blog.
Yes, we know that deleting the mapping values directly in Fiori is highly requested instead of download/upload workaround, no worries, we take this request seriously. The status is changed to "accepted" in the Customer Influence portal.
Best regards,
Elizaveta