Deciding on Appropriate Approach

Objective

After completing this lesson, you will be able to decide on an appropriate approach.

Deciding on Appropriate Approach

For an SAP system conversion, different approaches are offered by Software Update Manager. The following illustration shows the three main approaches.

This image illustrates the three available approaches of Software Update Manager for a system conversion to SAP S/4HANA: Standard approach, downtime-optimized Database Migration Option and downtime-optimized conversion.

When comparing the approaches, you have to keep in mind that only the technical downtime is reduced.

Between the standard conversion and the downtime-optimized conversion approach, there are two additional possibilities to reduce the downtime, both generally available: near-Zero Downtime Maintenance (nZDM) if no database migration is required as the source system is running on SAP HANA 2.0 database with a sufficient support package level, and downtime-optimized Database Migration Option (DMO) (for the migration case). Both approaches do not reduce the downtime parts of the data conversion.

  • nZDM: Moves table structure adaptations and import of new table content partly to uptime processing.
  • Downtime-optimized DMO: Migrates selected large application tables partly in uptime processing.
  • Downtime-optimized conversion: Moves migration and data conversion partly to uptime processing for a system conversion.

Caution

Please note that downtime-optimized conversion is available for educated experts only. To use the approach, a password is required. The password is obtained in a support ticket in which the Knowledge Badge for downtime-optimized conversion needs to be shared.

For DMO there are two approaches which differ (not only) in their means of data transfer:

  • DMO – transfers data based on memory pipes
  • DMO with System Move – transfers data based on data files

Caution

Please note that DMO with System Move cannot be combined with downtime-optimized DMO or downtime-optimized conversion.

If you're planning to move data centers, DMO is available in the flavor of Database Migration Option to SAP S/4HANA (on hyperscaler), short DMOVE2S4. It is an offering by Software Update Manager for the seamless transition to SAP S/4HANA Cloud Private Edition, combining the move from on-premise to the cloud with either a system conversion from SAP ERP 6.0 to SAP S/4HANA or an update/upgrade of SAP S/4HANA. Note that the target must be SAP S/4HANA. DMOVE2S4 can be combined with downtime-optimized DMO or downtime-optimized conversion. The approach requires sufficient network conditions as outlined in the respective guide. If those network conditions or other prerequisites cannot be met, DMO with System Move is an alternative.

For more information, feel free to visit the following sources of information:

This image shows two extracts from screenshots from Software Update Manager dialog in which the strategy is chosen. In both, downtime-optimized conversion is selected.

Caution

We strongly recommend avoiding downtime-optimized conversion on the same database if your current system is already using SAP HANA (so-called in-place conversion).

SAP offers tools to evaluate the appropriate approach. At the end of a Software Update Manager run, you are asked to provide feedback to SAP. The feedback includes the statistical data on the Software Update Manager run, encapsulated in a file called UPGANA.XML. As for a standard conversion run, this only contains the downtime parts of the Software Update Manager run, not considering the manual data conversion activities. Thus additional statistical data are relevant, part of the APPLANA.XML file. This file is provided with Early Watch Alert sessions. In addition, you can create it manually by report FINS_MIG_APPLANA_XML or in transaction FINS_MIG_STATUS using the following menu, GotoStatistics.

This image illustrates the usage of Software Update Manager statistic files for analytic purposes by Technical Downtime Optimization App and SAP Readiness Check.

The Technical Downtime Optimization (TDO) app is free-of-charge tool that offers an easy-to-consume visualization of the statistics data of UPGANA.XML and APPLANA.XML. You can also use the app to upload those files. TDO app can be extremely helpful in an early stage of the project as it offers optimization advise and simulation features to understand potential influence of archiving or different Software Update Manager approaches on the runtimes. Additionally, a cutover plan based on the achieved runtime can be accessed, modified and downloaded for future planning. The TDO app is available on https://tdo.cloud.sap

.

This image shows a screenshot of the Technical Downtime Optimization App and outlines its key facts as described in the text.

Find more on the TDO app in the following blog post in the SAP Community: Simply analyzing and improving maintenance events with Technical Downtime Optimization App .

The SAP Readiness Check for SAP S/4HANA offers a Planned Downtime Calculator, based on project statistics as well. This tool is intended for a first estimation without any existing data from a run. For more information refer to the following blog post: New Planned Downtime Calculator in SAP Readiness Check Is Now Live

Decide for an Approach

In the following exercise, you will learn how to decide for an approach for a system conversion of SAP S/4HANA.