ABAP Runtime Analysis – variant setup
Runtime analysis can be used to quickly get to the bottom of which tables are referenced during a transaction/program/function-module call.
I like running SM30 over ST22 because you get a nicer presentation of what tables were hit. ST22 tends to bee too detailed in majority of my scenarios.
By default the report is initialized with the DEFAULT variant. This is limiting and will not give you as much information as you might want. Typically on a new system I set up my own variant that allows me to access more information.
Steps to set up your own variant:
Select the drop down option in the Variant selector panel- Click the green check-box on the next screen without changing the parameters of the Selection Criteria for Variants pop-up
- You will be presented with two default Variants – DEFAULT and TMP; ignore those and click on the Create button
- Type in the name and continue
Here’s the most important part of this trick. When you get to the main configuration page of the variant go to the third tab [Duratn/type] and in the Aggregation pick the None option.- Once done click Save as… button and you are ready to run your Analysis.
SAP: debugging in pop-up windows
Debugging in SAP is something that I do almost on a daily basis, most of the time I get by just by typing the /h command in the transaction window and executing the program but this is not always possible.
The scenario that I speak of occurs when you are debugging a pop-up window. When you are working with a pop-up window there is no convenient transaction window where you can turn on the debugger. So what do you do?
Simple.
Create a new file; lets call it debugger.txt and populate the contents of the file with the following lines:
[Function]
Title=Debugger Session
Command=/h
Type=SystemCommand
Save the file and leave it on your desktop.
Now when ever you get to a pop-up window that you want to debug simply drag the debugger.txt file in to the window and you will activate the debugging session.
Happy hunting!