Downtime-optimized Conversion Approach of SUM
- The approach can be used for a system conversion from SAP ERP 6.0 to SAP S/4HANA
- It reduces the technical downtime by executing data conversion and migration (if required) in uptime
- Approach is possible for source systems on SAP HANA or on non - SAP HANA database
- Approach will require additional effort for project planning, impact analysis, and additional test runs
- Project requires an educated experts that has taken the respective training ADM329 and successfully passed the Knowledge Assessment ADM329k (requires access to SAP Learning Hub).
- If you are interested to leverage SAP Services and Support for Planning, Execution and Safeguarding (for Premium Engagement customers) please reach out to your responsible account management team.
The approach is based on the idea to move downtime activities (like data conversion from old to new data model) and database migration (in case of source system on non-HANA database) to uptime processing of SUM. For a standard conversion, the FIN data conversion has to be executed after the SUM has finished, by respective IMG activities (e.g. FIN customizing, FIN data migration). The downtime-optimized approach will even move the FIN data migration (partly) into the SUM uptime processing.
Data conversion is moved to uptime processing. If the source system is not yet on SAP HANA database, the database migration of the affected tables is then done in uptime as well, prior to this data conversion. [Affected tables: tables that are part of the old data model of SAP ERP but not part of the new data model of SAP S/4HANA – table content has to be converted from old to new table]
In addition, the field conversion for tables KONV and VBFA is moved to uptime processing as well. These two tables remain in the new data model, but fields have to be adapted.
In case the source system is not yet on SAP HANA database, selected large application tables (which are not affected by the new data model) will be migrated by SUM in uptime as well. [This is the approach named Uptime Migration respective downtime-optimized DMO, see https://blogs.sap.com/2014/09/08/dmo-downtime-optimization-by-migrating-app-tables-during-uptime-preview/ ].