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:

  1. Introduction + Overview
  2. How to collect and display traces of:
  3. a) Specific user or task
  4. b) Work process
  5. c) A transaction or program
  6. Scheduling traces
  7. 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

Popular posts from this blog

EVENTS IN INTERACTIVE REPORTS OF SAP ABAP

-
INTERACTIVE REPORT AND ITS EVENTS: INTERACTIVE REPORT :  A report which can generate one basic & up to 20  interactive lists is called an interactive report. So first list is called basic list & next lists are called interactive lists. EVENTS IN INTERACTIVE REPORTS: 1. INITIALIZATION. 2. AT SELECTION-SCREEN. a. AT SELECTION-SCREEN ON <FIELD>. b. AT SELECTION-SCREEN OUTPUT. c. AT SELECTION-SCREEN ON VALUE-REQUEST FOR <FIELD>. 3. START-OF-SELECTION. 4. TOP-OF-PAGE. 5. END-OF-PAGE. 6. AT LINE-SELECTION. 7. AT USER-COMMAND. 8. TOP-OF-PAGE DURING LINE-SELECTION. INITIALIZATION  : It is the first event to be triggered. Also this event is triggered before  the selection screen is displayed. So this event is used to give default vales to selection screen  fields. AT SELECTION-SCREEN  : This event is triggered after giving input in selection screen  fields. So this event is used to handle the user actions on the sc...
Read more

CONCEPTS OF INNER JOIN AND OUTER JOIN in SAP ABAP

-
Image
CONCEPTS OF INNER JOIN AND OUTER JOIN: I want to get the data  from multiple tables than we have to go for joins. There are 2 types of joins available in  SAP.  They are… 1. Inner join. 2. Left outer join. It is very important to remember that whenever we want to join the tables it is  mandatory that there should be at least one common field between them. Without a  common field between the tables we can not join the tables. For taking the common field you  should not consider MANDT field. So common field may be primary key field / other  field. INNER JOIN  - This  is exactly like intersection / logical AND operator. Also this inner join  will fetch the data from the tables if the record is available in all the tables that you are  joining. So if it is not available in one of the tables, the data will not be fetched. LEFT OUTER JOIN  : This is like union. But it is not exactly like union. Whenever left  outer j...
Read more

MAIN DIFFERENCE BETWEEN EXECUTABLE PROGRAM AND MODULE POOL PROGRAM in SAP ABAP :

-
MAIN DIFFERENCE BETWEEN EXECUTABLE/REPORT PROGRAM AND DIALOG/MODULE POOL PROGRAM : 1).Report or Executable programs: A report is a program that typically reads & analyses data in database tables without changing the database. 2).Dialog/Module pool programs: If your ABAP program demands a user input, dialog programming is used. User dialog is any form of interaction between the user & the program and could be any of the following such as entering the data, choosing a menu item, clicking or double clicking the entry. EXECUTABLE/REPORT PROGRAM MODULE-POOL /DIALOG PROGRAM 1).Executable program contain only two screen that is input as Selection screen and output as list.   1).Module pool programs contain many screen that are logically linked together. 2). Reports are standalone programs [that is we don't need to link our program to any screen or any transaction code]. 2).Module pool programs  are not standalone programs [that ...
Read more