Symptom
The download process in web browsers such as Google Chrome or Firefox automatically removes the '.XML' extension from the template file. Saving the file with a non-XML extension (such as '.XLSX') creates a structurally invalid file.
Although the data appears correctly displayed in Excel, it is shifted to incorrect fields in the migration cockpit's staging table. This mismatch results in unusual error messages from the API during import and causes the data to be stored in the wrong database fields.
Example: In the BANK Data template file, SWIFT codes are uploaded to the STREET field in the staging area.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Read more...
Environment
SAP S/4HANA Cloud Public Edition
- "Migrate Your Data – Migration Cockpit" app
- Migrate Data Using Staging Tables
SAP S/4HANA, SAP S/4HANA Cloud Private Edition
- Transaction "LTMC"
- Transferring Data Using Files
- Transferring Data Using Staging Tables
- "Migrate Your Data – Migration Cockpit" app
- Migrate Data Using Staging Tables
Product
Keywords
LTMC, File extension, downloading template, data migration, staging table, template file, XML, Google Chrome, Firefox, Spreadsheet 2003, migration cockpit , KBA , CA-LT-MC , S/4HANA Migration Cockpit , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview