SAP ST12 Transaction Code: Single transaction analysis

The Single Transaction Analysis was developed to promote the usage of ABAP trace inside SAP Support. It integrates the ABAP- (SE30) and the Performance (ST05) Trace into one transaction. This blog will show how to take a trace with ST12 in the so called “Current Mode” scenario. Further options for performning traces and analysis will be presented in future blogs.

"Single Transaction Analysis (ST12) getting started | SAP Blogs"

https://blogs.sap.com/?p=50726

17 55 62,241

https://blogs.sap.com/?p=52696

In other blogs it was mentioned that ST12 only stores the ABAP trace in the database. While this is true there is an option which allows you to store additional information e.g. the summary of a SQL trace and additional information manually together with the trace. This blog shows this option together with some hints on how to manage the collected traces.

"ST12 storing additional information and managing traces | SAP Blogs"

https://blogs.sap.com/?p=51334

If you click “Start trace” (Nr. 5 in figure 1) you will see the following information in the small table that is just above this button.

"ST12 tracing user requests (Tasks & HTTP) | SAP Blogs"

https://blogs.sap.com/?p=52850

Imagine you change an order in VA02 and after clicking a specific button (e.g. the ATP (available to promise) check) it takes a while. Now you wonder what happens when you click this button and how you could trace exactly this click. In this blog we will explain how to trace a single dialog step with the “Particular Units” option in ST12. 

"ST12 tracing a single dialog step | SAP Blogs"

https://blogs.sap.com/?p=53487

http://service.sap.com/swdc – support packages and patches    – browse our download catalog      – plugins        – SAP Solution Tools          – ST-A/PI

"Comments on: ST12 01N_* SP1 new features"

https://blogs.sap.com/2011/12/07/st12-01n-sp1-new-features/feed

No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.

https://blogs.sap.com/2013/07/17/check-out-my-document-on-st12-trace

Check out my document on how to analyze ABAP code flow using ST12 trace. You can find my document in the below link, http://scn.sap.com/docs/DOC-44143

https://blogs.sap.com/2013/07/17/page/4

·       ST12 trace can be captured for “User/Tasks”, “Work Process”, “Current Mode” and “For a Schedule”

https://blogs.sap.com/2013/07/17/st12-trace-step-by-step-instruction-on-how-to-use-it-for-analysis

Hi. This blog is used for creating a checklist of what consultants, users, SAP support and admin needs to check when a performance issue occurs. For your issue that is posted in SCN and in here, if nobody was able to assist with their examples then it may be a new issue that may require an SAP incident/ticket if our current fix that is available online or during the ticket creation didn’t help out. Make sure to do due diligence in specifying the ST12 or test documentation (show what time the issue occured, who the user is) and the corresponding SMPServer-smp-server.log and Agentry logs as a re...

https://blogs.sap.com/2014/12/08/troubleshooting-sap-work-manager-performance-issue/feed

View the full list of resources, SAP Help/Wiki pages and Q&A for ST12