Show TOC

Usage ScenariosLocate this document in the navigation structure

Figure 1: Interplay of Various Analysis Tools and Utilities

Monitoring and other activities are typically distributed to several systems:

In the Productive System, you can use the following tools to perform these activities:

SQL Monitor tools (transactions: SQLM and SQLMD)
  • To record runtime data for the SQL statements executed in your business processes, switch on the SQL Monitor for a sufficiently long time in your productive system.
  • After approximately 7 days of monitoring, the SQL monitor results enable you to identify performance hotspots and determine optimization potential on code level.
  • You can archive the collected SQL Monitor data in order to have it available for further analysis. For this purpose, generate so-called SQL snapshots.
Runtime Check Monitor (transaction: SRTCM)
  • The Runtime Check Monitor allows you to activate certain runtime checks that complement the corresponding static checks with aspects that can only be checked during runtime.

In the Quality or Test System, you can perform the following activities:

ABAP Test Cockpit (ATC) or Code Inspector
  • Static check tools are used in the development system to check the code during development. The test system contains the consolidated code base and is therefore suited for regular static code regression check runs. Code Inspector provides a wide range of checks which cover aspects like functional correctness, usability, robustness and performance. The Code Inspector checks can be used in the Code Inspector tool itself or in the new ABAP Test Cockpit. In this documentation we focus on the performance and DB-related static checks.

In the Development or Correction System, you can perform the following activities:

SQL Performance Tuning Worklist (transaction SWLT)
  • To analyze runtime data, you need to create snapshots in the development system, based on the SQL snapshot that has been exported from the productive system.
  • To analyze static code data, you need to select the code inspections or the corresponding ATC run series that you executed previously in the Code Inspector or ABAP Test Cockpit tools.
  • Results from different data sources are matched and combined by their source position. This enables you to find ABAP SQL code that has potential for performance improvement in productive processes.
Runtime Check Monitor (transaction: SRTCM)
  • You have the option to import snapshots into the development system, based on the runtime check data that has been exported from the productive system.
ABAP Source Editor
  • Solve the functional issues as detected by static checks or using the Runtime Check Monitor.
  • Solve the performance issues as identified in your productive system.