Optimizing Technical Downtime with Tools from SAP

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Summarize tools for downtime-optimization

TDO App: Analysis of Maintenance Events

Disclaimer: Please note that links in this course may require specific authorizations.

This section introduces the Technical Downtime Optimization (TDO) app. The TDO app helps you to analyze maintenance events based on the Software Update Manager (SUM) statistics file.

Technical Downtime Optimization Application

With the Technical Downtime Optimization (TDO) Application, SAP offers a tool to evaluate the runtime of a completed maintenance event with Software Update Manager (SUM). At the end of a SUM run, you are asked to provide feedback to SAP. The feedback includes the statistical data on the SUM run, encapsulated in a file called UPGANA.XML and, in case of conversions, also APPLANA.XML.

The application is available through SAP for Me. The tile is located in Services & SupportDiagnostics, Reporting & Analytics. It is named Technical Downtime Optimization. You can access the application also using the direct link: https://me.sap.com/app/downtimeoptimization.

Features of Technical Downtime Optimization App

After statistics, XML-files of a SUM run have been provided to the TDO app, the respective maintenance event can be accessed in the app. A chart visualizes the duration of uptime and technical downtime as well as the main phases of the technical downtime. Additionally, recommendations on how to potentially improve runtimes of SUM are available.

The Compare feature compares two SUM runs that have been uploaded to the TDO app. Additionally, TDO app offers Simulation features to estimate the potential downtime savings in case any downtime-optimization option is utilized. Following simulations are available (if applicable for the respective maintenance scenario):

  • Downtime reduction through data archiving
  • near-Zero Downtime Maintenance
  • Zero Downtime Option
  • downtime-optimized Database Migration Option
  • downtime-optimized Conversion

Additionally, a Cutover Plan feature is available. The runtime information from SUM as well as modifiable blocks for manual activities (such as modification adjustments or ramp-down activities) are presented in an easy-to-consume timeline to serve as a starting point for project planning.

Find out more about the Technical Downtime Optimization application in the following blog post in the SAP Community: https://blogs.sap.com/2020/09/16/downtime-optimization-get-insights-using-the-new-tdo-app/

Options of Software Update Manager

This section provides an overview on different downtime-optimization approaches that are available with tool Software Update Manager (SUM).

The landing page for the Software Logistics Toolset (SL Toolset) in the SAP support portal is the central entry point for generic information on Software Update Manager as well as for all information around updates and upgrades: http://support.sap.com/sltoolset.

Software Update Manager supports several scenarios like system conversion to SAP S/4HANA, database migration, and updating or upgrading ABAP-based systems. For some of them, downtime-optimized approaches are offered.

Downtime-Optimization Approaches for Maintenance Activities

ApproachAbbreviationScenarioAvailabilitySAP Note
Customer Transport IntegrationCTIUpdate/Upgrade/Conversion to SAP S/4HANAUnrestricted available1759080
near-Zero Downtime Maintenance (ABAP)nZDM (ABAP)Update/UpgradeUnrestricted available1678565
Zero Downtime OptionZDOUpdate/UpgradeAvailable for educated experts (ADM330e)2707731
downtime-optimized Database Migration Optiondowntime-optimized DMOMigration to SAP HANA databaseUnrestricted available2442926
downtime-optimized Conversion Conversion to SAP S/4HANAAvailable for educated experts (ADM329)3258077 (SUM 2.0 SP 16)
near-Zero Downtime Maintenance (JAVA)nZDM JavaUpdate/UpgradeUnrestricted available2847197 (SP 22)
Near-Zero Downtime TechnologyNZDTConversion to SAP S/4HANAService-based693168

The most current version of this list can be found in the SAP Support Portal on the dedicated sub-page for SUM: https://support.sap.com/en/tools/software-logistics-tools/software-update-manager.html. When you are there, navigate further to the section entitled Downtime Optimization.

Three Main Approaches for Updating or Upgrading SAP S/4HANA

More details on project planning and functional validation will be covered in unit 3.

The Software Update Manager (SUM) Toolbox

This section introduces the features delivered with Software Update Manager (SUM) Toolbox.

Software Update Manager (SUM) Toolbox is an ABAP-based transaction that allows you to run certain tools and reports related to the various scenarios offered by Software Update Manager 2.0, especially tools required for downtime-optimized approaches are in the focus of SUM Toolbox.

SUM Toolbox is shipped with the regular software delivery of SAP_BASIS. Additionally, SUM Toolbox is delivered using the TCI SAP Note (see SAP Note 3092738).

Tools and checks delivered with the SUM Toolbox, which are especially relevant in context of ZDO, are as follows:

  • ZDO Preliminary checks
  • Export data for Impact Analysis
  • Impact Analysis of SUM
  • DB Table Lock Analyzer
This list is non-exhaustive. Additional checks and tools are added to SUM Toolbox and may be used for the execution of ZDO maintenance events. For more information on available checks, see SAP Note 3092738 and respective SAP Note of latest available version of the SUM Toolbox.

ZDO Preliminary Checks

ZDO Preliminary Checks of the SUM Toolbox are executed on a system, which is planned to be maintained using ZDO. This collection bundles several checks that you can use to verify the prerequisites of ZDO before the SUM is started. More information can be found in the section, "Preparing the System for an Upgrade or Update with Zero Downtime Option".

The checks contain the following:

  • BW - Check for Active Usage of Business Warehouse ZDO does not support updates/upgrades on systems where embedded Business Warehouse (BW) with the use case of data warehousing is active and used. Only if the use case Embedded Analytics is active, ZDO is possible. The check shows all BW objects that are not ZDO-compliant and cannot be used during a ZDO upgrade.
  • SDMI - Check for Unfinished Silent Data Migrations Migration of application data usually happens during the downtime of release upgrades or updates. In contrast, the Silent Data Migration Infrastructure (SDMI) allows zero downtime upgrades and runs after the upgrade in parallel to regular operations. Before starting a zero downtime upgrade, it is essential that all relevant silent data migration classes in all clients from the previous release upgrade have been executed successfully.
  • DDIC - Check for Inconsistent Objects in the Data DictionaryInconsistent objects, or objects that are not defined in Data Dictionary (DDIC), might have an impact on the ZDO procedure, especially when tables need to be cloned. Therefore, this check provides a consistency check of missing DB objects and DB objects that are not defined in DDIC.
  • HANA_CONTENT - Check Deploy Ability and Consistency of HANA ContentHANA content needs to be deployable during the ZDO procedure. This check validates the consistency of all HANA content deployed by HTC, HTA or HDI.
  • Nametab - Check Consistency of Active NametabsInconsistent nametabs might have impact on the ZDO procedure, especially when tables need to be cloned. Therefore, this check provides a consistency check if all active nametabs have a corresponding object in Data Dictionary and on the database.
  • DBTRIGGER - Check ZDO Compliance of database triggersThis check validates whether database triggers are used in the system and whether the setup is ZDO-compliant and how these database triggers might have an impact on a ZDO upgrade. This also includes checks of SLT replication triggers, which are supported by ZDO.

Export Data for Impact Analysis

This feature exports table statistics to a compressed file (that is, ZDIMPA­NA.ZIP), which can then be used by SUM for Impact Analysis or for manual execution of Impact Analysis with SUM Toolbox). Take note that data should be exported from production system. Impact Analysis is described in detail in later units.

Impact Analysis of SUM

This is the dialog version of the Impact Analysis. It can be utilized as soon table statistics from production and table classification from any SUM run that applies the planned stack with ZDO is available (for example, after a sandbox update or upgrade). Impact Analysis is described in detail in later units.

DB Table Lock Analyzer

The Database Table Lock Analyzer tool can be used to find a suitable time interval to run lock-intensive SUM phases, such as the Smart Switch (SUM Phase EU_SWITCH_ZDM) of the Zero Downtime upgrade procedure.

Save progress to your learning plan by logging in or creating an account

Login or Register