Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert
0 Kudos


last updated: 2024-02-06

The article explains the SAP GUI – TCODE (Transaction Code): ST12 usage in details.


Transaction Code ST12 developed to overview and analyze a single transaction.

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 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?

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)
  • 3212479 - How to identify whether it's a HANA Database performance problem according to ST12 trace
Other articles in this series
🔖 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:

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 DateDescription
2023.09.07First/initial Release of the SAP Blog Post documentation (Product Information).
2024.01.26SAP Community 2024 optimized content.
2024.02.06Other articles in this series section maintained.