Tool Availability and Technical Requirements

The SQL Performance Tuning Worklist is available as part of the standard SAP NetWeaver delivery.

Supported SAP NetWeaver Releases

Before using the SQL Performance Tuning Worklist in an AS ABAP system, some preparation steps are required.

To launch the transaction (SWLT) itself, as a minimum, the display authorization profile for object S_DEVELOP (activity: 03) is required.
To use the complete functionality of this transaction, you need the authorization profile for object S_ADMI_FCD with the value SQMA for administration activities and the value SQMD for data read access.

For the execution of static checks (ABAP Test Cockpit or Code Inspector), we recommend using the predefined Code Inspector variant PERFORMANCE_DB. This variant contains a selection of checks particularly suited for identifying potential performance issues. In particular, this variant provides specific checks used in the SQL Performance Tuning Worklist tool to merge SQL Monitor data with static check results. See also: Section Recommended Code Inspector Variants in ABAP Test Cockpit and Code Inspector in Context of HANA Migration
In case you are only interested in static check results for SQL statements that definitely have been recorded by the SQL Monitor, we recommend using the Code Inspector object collector CL_CI_COLLECTOR_SQLM_SNAPSHOT ("Objects from SQLM-Snapshot created in SWLT"). This object collector allows you to restrict the inspection's object set to those objects that are definitely contained in a previously recorded SQL Monitor snapshot. In addition, this restriction helps you to optimize the performance and memory consumption of the used scan and analysis tools.