You have noticed some differences related to localization in the Supplier template (XML downloaded file) when comparing with the sample or with other system ID.
You can face similar differences in the migration objects such as: Supplier - extend existing record by new org. levels, Customer, Customer - extend existing record by new org. levels.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
SAP S/4HANA Cloud.
- Migrate Your Data – Migration Cockpit (Old) app
- Migrate Your Data – Migration Cockpit app
Due to the calculated view, some country/region-specific fields will be available in the template only in case the solution for that country is activated in the system.
Structures and fields/field groups marked with an asterisk (*) are visible only if the configuration of your system covers the requirement for them at the time of the download.
From Supplier migration object documentation you can see the following:
Please, always check the Migration object documentation to see all the fields that will be made available depending on the system configuration.
Also note, this differences are not related to custom fields but to calculated view due localization. If you enhance your business object with custom fields in the app "Custom Fields and Logic" a new migration XML template must be downloaded and used.
SIF_VENDOR_2, SIF_CUSTOMER_2, SIF_CUST_EXT_2, SIF_VEND_EXT_2, Migration Object Supplier, Calculated view, XML template. , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content (LTMC) , CA-LT-MC , S/4HANA Migration Cockpit , How To