Technical Articles
SAP S/4HANA Migration Cockpit – Working with the Excel Template
Update – November 2022: check KBA 2728194
Hello all,
ín this blog I will provide some hints when working with the Excel Template, downloaded from the SAP S/4HANA Migration Cockpit.
The migration template is an Microsoft Excel XML Spreadsheet 2003 that is an XML file and not a normal Excel workbook. It consists of different sheets to specify the data that belongs to different data structures. Some sheets are mandatory, and some are optional.
Dos:
- Always download and fill the original template of the SAP S/4HANA release you want to upload your data to.
- Use sheet FIELD LIST to gain information which sheets are mandatory.
- The wildcard character (*) indicates that a field is mandatory.
- Maintain all mandatory fields in a mandatory sheet
- Mandatory fields in an optional sheet don´t need to be filled.
Dont´s
- Do not use a template from previous release.
- Never change the structure and don’t make any changes on the format.
- Don’t delete, rename, or reorder any sheet in the XML file.
- Don’t change the cell formatting, don’t use formulas, and don’t hide, remove, or reorder any column in the XML file
- Don’t change data by Find and Replace function. If you change data by Find and Replace you may also accidentally change the field names and corrupt the XML structure.
- Avoid empty lines in the XML (otherwise error message “… contains records with duplicate keys….” can arise).
A modified Migration Template will cause errors when trying to load into the migration cockpit or will cause errors during the data migration process
2470789 – SAP S/4HANA Migration Cockpit – Cloud data migration template samples
In the excel template you can unhide rows 4-6. Additionally, in row 8, you can view the field names in SAP S/4HANA, as well as additional information such as the expected format (for example the data type and length).
Formatting issues – Copying values
1. Within a migration template us Paste Option VALUES (V)
2. From somewhere else to the migration template use Past Option PASTE SPECIAL.. and then choose TEXT
3. From Notepad to the migration template use Past Option KEEP TEXT ONLY (T)
WIN10 Version and upgrade to new office Issues
- In case you get strange “Workbook” error when opening the template… we recommend to unflag the follwoing flag:
- Truncated decimal fields
In case you get Truncation warnings in the Cockpit when template is uploaded like:
see also note KBA 2728194
Background: If the Options “Set precision as displayed” is not checked (default setting = not checked), the value is stored longer into the XML then its definition.
Definition is Data Type „DEC“ Length „9“ Decimals „5“ and value entered and displayed in field is “45.12345”
The data is correct filled into the staging with 45.12345.
We recomment to flag the following:
Excel Options -> Advanced -> When calculating this workbench: “Set precision as displayed”
Hi Sybille
Great article, definitely serves as a handy instruction set for core-team members for filling out the templates.
Thanks for this.
Hi Sybille,
Thanks for the detailed info. I've just started trying out tcode LTMC and creation of materials. However, when it comes to updating a material master field (for example material group) nothing is changed. Does the Migration Cockpit support the update of previously created objects? If so, is there also a no data sign/value?
Thanks!
Hi R. Auer,
please check in detail the documentation for each migration object where it is explained what is the puprose of the object. Check the BAPI if there is an update possible.
For 1709 e.g. we deliver a new migration object called "Material - extend existing record by new org levels" - this is to extend an already existing object.
Sybille
Hi,
Thanks for the info! Have a question, how do you know if the sheet is mandatory or not? The fields are marked with '*' to denote it is mandatory. I don't see any where in the templates where it says a given sheet is mandatory or not.
Thanks
You can quickly get an overview of the mandatory and optional sheets by looking at the color of the sheet names at the bottom of the migration template. The name of the mandatory sheets have the color orange, while the optional sheets have the color blue.
Hi Sybille,
Trying to upload BP data via XML template, trying for BP grouping 'BP02, 'Please help to solve on the below errors/issues: let me know if need more info
Grouping BP02 has internal number assignment; do not enter a number
Message no. R1092
Customer ## / 1110 / 10 / 00: Data is incomplete; check data
Message no. CMD_API074
Mandatory partner function BP is missing for sales area 1110 10 00
Message no. MDG_BS_ECC_BP_CHECK040
Thanks and Regards,
Varahalu
Hello,
Thanks for the info. I have a question. When i upload my file, i still have a warning truncated message.
"Tab cost Center master Record,Ktext line 9 is truncated during upload, max data length is 20"
Can someone help me about this issue ?
Thank you
Could you solve the problem?
Hi,
Thanks for valuable information. I also have question about formatting.
Did you try to upload any negative values like "-5" , "-10" ?
In help.sap its given as "For negative numbers, ensure that a minus sign (‘-‘) directly precedes the number, for example ‘-100’. "
But whenever i upload data like this LTMC gives error BF020 - 'value can't be interp. as floating-point number or longer than 22 charac'. I tried different formatting but it didn't do any good, even tried giving it like "10-" but it didn't work.
Thank you.
Dear Sybille,
is it possible to CHANGE a material with the Data Migration Cockpit? If you, for example only have the Basic Data in the beginning and later have the data for Procurement. Can you upload the file twice? Will the System notice that only the Procurement view changed?
Kind regards
Mario Wolf.
Hi sybille,
An issue happened to me using ltmc, its when we have more than 1 blank space between words in descriptions for materials, adress stings also....it gives characters like #160 and it's very difficult to treatvall thise additional spaces that came with the original data.
Thanks
Dear Sybille,
I am occurring an issue when I am downloading the mapping task file.
Automatic is downloaded in csv format and even if I am translating in xls or xml 2003, I am not able to upload into Migration cockpit.
Do you have any recommendation for that issue?
Mention that Migration template I have downloaded correctly - xml 2003 extension.
Many thanks in advance,
danielaT
Hi Sybille,
please exchange the link to SAP Note 2563690 by the Link to KBA 2728194 - Decimal numbers are truncated during upload - warning message
The SAP Note is outdated and is put to be archived.
Best
Frank
Thanks Frank for the hint! br, sybille
Hi Sybille
I am working with the staging tables uploading suppliers as my first object from a legacy system.
However business would like to use SAP supplier numbers when loading the legacy data into SAP.
We also imagine we should define a SAP template supplier so we get default values created on the suppliers when they come into SAP ?
Do You have some documentation explaining these issues ?
Thank you in advance
regards Henrik
Hi Henrik,
please check the documentation of the migration object you use:
http://help.sap.com/S4_OP_MO - onPrem
http://help.sap.com/S4_CE_MO - public Cloud
best regards, Sybille
Hi Sybille,
We are using the template from SAP, and we add the data to template via our local system, then we have a new xml file with our added cell data, and it could be opened by excel without problem, and all the cell data are correct, but it could not be upload to SAP directly, otherwise we get the error "The format of the uploaded file test-2.xml is wrong. The file contains only one line." And
Some features in your workbook might be lost if you save it as Excel 2004 XML Spreadsheet (.xml)." , we click keep using this format, and then upload to SAP with the saved xml file ,it will be ok. Why is this issue case?
Best
Yiming
Hi Yiming,
in the XML template file, the first worksheet called INTRODUCTION gives very detailed explanation on how to use the XML files, how to fill with data.
Please read this carefully.
Besides you can check the following:
KBA 2693715
Blog Post How to correctly fill data into XML templates
In case you are using tools to fill the staging tables, I would recommend to use the CSV files instead.
Best regards,
Sybille Lackermeier, SAP S/4HANA migration cockpit Product Management
Thanks for your response Sybille, but we are wondering where we could find any more details about errors, we just find the errors CNV_DMC_MD_EXTRACTOR with number 10. If we have more error details, maybe we could find the root cause more easier. And if the xml data could be only saved manually and it is not possible to to save it via system