Data Migration

The data import framework accepts only XML, but your extract is CSV. What lets you still use file import?

A data import run into the staging area finished successfully. Is that master data now active?

Loading legacy records into MDG, why is it unsafe to assume the MDG object ID equals the downstream system's ID?

For a small key-mapping load already prepared in Excel, what loader fits better than the data import framework?

What does value mapping map, as distinct from key mapping?

In the file upload 'Delete All and Add Records' mode, what happens to existing records that are not in your file?

How does 'Overwrite or Add Records' differ from 'Overwrite or Add Attributes' in file upload?

The 2019 book lists LSMW among direct-to-active load options — what caveat applies on current S/4HANA?

In a co-deployed MDG landscape (MDG on the operational ERP), which objects still require migration and which do not?

You must load master data into MDG and are choosing between the data import framework and the file upload framework. Which capabilities separate them?

How do you load master data hierarchies into MDG?

Can the file upload framework write master data straight into the active area to skip governance?

Why must financial 0G (flex-mode) objects go through the MDG staging area while customer, supplier and material objects need not?

For which extraction is Transaction MDMGX the wrong tool, despite being the generic MDG extractor?

Migrating suppliers and customers into MDG via ALE/IDoc, what setup is easy to overlook?

Why might SOA-based extraction not be an option for a given source SAP ERP system?