SAP ABAP troubleshooting – Collecting ABAP traces & performance traces using the Single Transaction Analysis tool ST12
SAP ABAP troubleshooting: Collecting ABAP traces & performance traces using the Single Transaction Analysis tool ST12:
The Single Transaction Analysis tool(Tcode ST12), has the ability to collect both ABAP traces & performance traces with an integrated user interface. It offers different methods for tracing & also allows the recording of traces of ABAP transactions, ABAP reports, Web dynpro pages, BSP pages & background jobs.
The traces collected by this tool can be used to investigate code errors & performance problems. This blog will show you how to collect & display the traces as well as common problems you may have to deal with while using ST12.
Overview:
- Introduction + Overview
- How to collect and display traces of:
- a) Specific user or task
- b) Work process
- c) A transaction or program
- Scheduling traces
- Common issues
Notes:
Service Tools for Applications (ST-A/PI)
https://support.sap.com/supporttools
Installation:
Note 69455 : Service tools for Applications ST-A/PI [tcode ST14, report - RTCCTOOL, tcode ST12]
How to use:
Note 755977 – Transaction ST12 “ABAP Trace for SAP Early Watch or Going Live”
Tcode ST12 – collects traces, mix of tcode SE30, tcode ST05.
Troubleshooting, program working, consider using Tcode ST12 Comes with ST-API
This will help to provide SAP a trace
This is Not officially supported, no official documentation
Let's Run the trace
Trace results -
Tips to enter the user name & then select the server : it will show the server and the user is connected to
Note: Avoid activating on all servers
Task type:
In the middle:
performance trace : Tcode ST05
ABAP trace : Tcode SE30
Statistical records : Tcode STAD
Internal tables : if selected then we will check for read or loop
Size and duration : 2 options provided , he usually selects the maximum
Context trace: it collect across multiple systems.
Further options dropdown -
If you trace your own user, this may track tcode ST12 itself & could be confusing:
Watch the size of the trace & the filters
Trace did not work : then yellow arrow
This is where to look for performance problems
Show or Hide option
Performance trace : equivalent of tcode ST05
Current mode : only collects for certain unit
Should schedule a trace to run for a job to run later
Some Questions and Answers for your reference:
Q1: The HTTP's trace us for Web dynpro application : does this also work for Floor Plan Manager (FPM)
Ans: Cannot tell: if it is http & connect to app server, yes.
Q2: How do I provide these traces to SAP in an OSS calls?
Ans: Collect traces, open incident & indicate which trace should be analyzed: this should speed up incident.
Q3: Is there any shortcut for switching the trace on & off? If yes what is it?
Ans: No.
Q4: Could this be used for Multi level End to End Scenario for example: iOS based Fiori App access the Gateway and Gateway access the ERP instance. lets know whether the issue is on Gateway or ERP instant.
Ans: Yes, backend call is http call for Fiori.
Hope this helps. Thank you everyone.
Comments
Post a Comment
If you have any doubts let me know