Technical Basics of Migration and Conversion
Depending on the project, high-performance technology and methodology is available within SAP Landscape Transformation
that you can use to convert the data in your system. The data conversion can be migration or conversion and relate to one or several systems.
Note
Since both types of conversion are carried out by table (not application-related), content checks cannot be performed during migration or conversion. Extensive tests are essential before the start and in the copied test system.
Both technologies differ as follows:
Migration |
Conversion |
|---|---|
Based on two systems: Sender and receiver system |
Takes place in one client of a system only: Execution system |
Sender system is read and remains unchanged |
Changes are made directly to the database: New values replace old ones |
Changes are made using the central system directly to the database of the receiver system |
Changes are made in the execution system |
The runtime estimation estimates how long the conversion will take. The actual conversion takes place during a system downtime (usually on a weekend).
On the basis of tables and their fields, the generation program creates individual conversion programs that replace each of the old values with new values using an included rule.
After the last conversion or migration program has run, postprocessing steps are recommended. These are listed and described in the process tree.
Prerequisites
You are using the SAP Landscape Transformation
solution.