last updated: 2026-02-11
Introduction
The article explains the SAP GUI – TCODE (Transaction Code): ST12 usage in details.
SAP GUI
- SAP Help Portal – SAP GUI for Windows
- SAP Community – SAP GUI – SAP GUI Family
- 147519 – Maintenance strategy / deadlines for SAP GUI for Windows / SAP GUI for Java
Description
Transaction Code ST12 developed to overview and analyze a single transaction.
- SAP Help Portal – Single Transaction Analysis
- SAP Help Portal – ST12 (Single Transaction Analysis)
Video explanation by SAP BASIS
Menu
ST12 – Single Transaction Analysis

Screen: Single transaction analysis
Initial screen where trace can be recorded, based on the measurements. Also the analyzation steps can be done from here.
During analyzation the following values are necessary (to identify the proper trace entry):
- Comment
- User
- Date

Click on the 'Full screen' button and open the overview screen of all the traces collected.
Screen: Trace analyses fullscreen list
Overview screen of all the traces collected. The proper one can be selected from the list.

Click on 'ABAP trace' button to move SE30.
Click on 'SQL trace summary' button to move ST05.
Screen: SQL Summary (ST05)
Detailed information about the SQL commands.

Click on 'Explain' button to move Display Execution Plan for SQL Statement screen.
Screen: Trace analysis (SE30) - ABAP Trace Per Call
Detailed information about the ABAP trace. In the below example the execution takes long time because of the database part. Header chart shows information about this, also the 'Net' and 'Gross in %' columns shows the same conclusion.

Further information available, click on 'DB' link.
Screen: SQL Summary for Code location

Screen: SQL Summary - Statement details

Investigate further: ST04 - - > Performance - - > SQL Plan Cache menu SAP GUI - Transaction Code - DBACOCKPIT (SQL Plan Cache) and find the SQL statement hash based on the SQL statement string.
Screen: Display Execution Plan for SQL Statement

What blog posts can be helpful?
- ST12 Trace – Step by step instruction on how to use it for analysis
- Question: Is ABAP performance tracing (ST12) still a topic?
- Single Transaction Analysis (ST12) getting started
- ST12 – tracing function modules
Which SAP Knowledge Base Article belongs to the topic?
- 755977 - ST12 "ABAP Trace for SAP EarlyWatch/GoingLive"
- 2540971 - How to run a ST12 Performance Trace
- 2436955 - How to collect and analyze traces using ST12 (single transaction analysis)
- 2169881 - How to trace background job using ST12
- 2511272 - How to schedule ST12 trace for long running background job in Kernel 721 and above
- 3212479 - How to identify whether it's a HANA Database performance problem according to ST12 trace
🔖 3428763 - Bookmark of frequently used SAP GUI transaction codes for SAP HANA related investigations
Do you have further questions?
Please do not hesitate to contact me if you have question or observation regarding the article.
SAP Community for SAP GUI: https://community.sap.com/topics/gui
Contribution
If you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.
Release Information
| Release Date | Description |
| 2023.09.07 | First/initial Release of the SAP Blog Post documentation (Product Information). |
| 2024.01.26 | SAP Community 2024 optimized content. |
| 2024.02.06 | Other articles in this series section maintained. |
| 2026.02.11 | Insert SAP BASIS video. - ST12 trace. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.