3/5/2016 9:36:41 AM
Perform an RFC trace from transaction ST12-Trace for "Tasks & HTTP". This Blog will show you to find the ABAP RFCs which get called from the Java web portal screen on applying any action on it. In my experience, there is a JAVA based web application which is used to create Purchase order or change purchase order and there is no IDoc or Proxy its an direct RFC call from JAVA portal and which is causing performance issue. This blog will give you step by step how to take RFC trace using ST12 transaction.
Please click here to activate and analyse ST12-ABAP trace using the single transaction analysis
Steps to perform ST12-Trace for "Tasks & HTTP"
1) Go to transaction ST12
2) Trace for "Tasks & HTTP"
Comment - Insert your own comment
Choose your server
Username - The RFC Username
Tasktype - RFC
ST12 is now prepared to run the trace
Perform your action on JAVA portal
Click End traces & collect
There are two traces that you can view.
- The ABAP trace will provide information on where in the code most of the time is being spent
- The Performance SQL trace will determine what table reads are taking the longest time.
At top of screen there will see something like below shot, here 58% of the time is spent in ABAP code.
If ABAP is high then most time is being spent on code, probably loops within a Function Module.
To determine, what Function is taking the longest click on the "Net" column and"Sort by descending order".
Making note of these Functions can be very useful in narrowing down the cause of the problem.
Performance (SQL) trace:
This collects all the calls to the database.
If the above screenshot shows that 'Database' is very high then most of the time is being spent accessing database tables.
There are two main causes of bad performance to look out for
- A very long table access
- A number of identical calls to the same table.
To check for long table accesses scroll down through the trace and note any red marks under the column "Duration".
To check for identical calls follow this path
Here the number of executions will show on the first column.
Note : The 'Tasks&HTTP' scenario is available as of SAP basis 6.10. It allows to specify a max. number of ABAP trace activation=ABAP trace files, and is therefore suitable to trace many incoming RFCs or BSP pages, where every screen element makes an own call to the R/3 system
If you like this blog, please share (Facebook/LinkedIn/Google+) to click below links so it will reach to others.