Skip to Content

1. Step by step instructions on how to use ST12 trace for analysis 2436955 176 Views

In first, we have a staple KBA that takes you step by step on how to take an ST12 trace. The transaction ST12 can be utilized to trace the ABAP/DB activity a single user performs.

It can also be utilized to trace a transaction or a program at the moment it starts. This transaction would be very useful in finding how much runtime is allocated for each ABAP Step and DB activity, which in turn will be useful for optimizations or identifying and assist in root cause analysis.

 

2. High RFC time: Performance troubleshooting 2418936 155 Views

In second place we have a troubleshooting KBA regarding a high RFC time seen in ST03. Discover how we analyze problems that may lead to multiple reasons why you are seeing a high value in this indicator. Some examples you may see in this document are :

Network performance issues
The result of communication and high data volume issues

Slow running jobs between different SAP systems (for example ERP and BW)
Indicated by high roll wait time in the ST03 monitor.
In this scenario, a job that is running between SAP systems can take a long time to complete on the target system, which can be an application, hardware or database specific issue.

Unavailable RFC resources
Individual RFC resources are overutilized on the target system which can generate high wait time.

A misreported response time which is not related to an actual performance issue, but rather a bug related in manner.
In this case, the response time will be unrealistically high.

High RFC time is provided in Early watch alert.
An Early watch alert will highlight RFC response time as yellow if it exceeds the monthly average threshold of 2400ms and red if it exceeds the average threshold of 3600ms.

 

 

3. How to use the SAP Performance Monitor SDF/MON tool to analysis 2383809 80 Views

In third place, we have the KBA instruction manual on how to utilize the /SDF/MON monitor to analyze performance problems you may be having. Scheduling this monitor will allow you to view the SM50 snapshots of an instance to analyze the information. This particular tool is quite helpful when the issue occurs randomly or that the problem seems to arise during specific time intervals.

 

 

 

 

 

4. How to analyze high GUI time on SAP systems 2428353 72 Views

In fourth place, we have a KBA dedicated to the analysis of high GUI times seen in ST03 and STAD. It walks you through a single transaction or programs in STAD which can also be found in the Workload Monitor. There are many scenarios that you may see high GUI time including:

-Large volume of data transfer from the application server to presentation servers (frontend GUI).

-Low network transfer rate between application server to presentation servers (frontend GUI).

-Long time on executing/interpreting the RFC calls on presentation servers (frontend GUI).

-The display time on the frontend is long due to the performance of frontend PC is considerable bad.

Have a short glimpse of how to use tools like Performance trace with this KBA.

5. Performance problems with OLE_FLUSH_CALL, how to analyse. 2457530 45 Views

In fifth place, we have “Performance problems with OLE_FLUSH_CALL, how to analyse”. You may often see this in your ST12 traces and we all know the struggle of troubleshooting this part.

A few points that are covered in this KBA are:
-Determining if the runtime is the problem
-The number of times OLE_FLUSH_CALL is called
-Network Infrastructure and Traces
-SAPGUI Version management
-Performance GUI Traces

Add this KBA to your list of staple KBAs, it may help you in the near future.

 

 

 

 

 

6. Survival Guide for performance analysis on SAP system 2442365 42 Views

In sixth place, we have the “Survival Guide for performance analysis on SAP Systems”, which I find surprising because this is truly the bible for general performance problems. Refer to this guide whenever you are looking for information on General performance and this includes cross-platform integration problems.

What is Cross-Platform Integration Problems? A great example I like to use is a CRM UI user trying to access a list of the employees but the loading is far too slow. The goal of this guide is to assist you in finding if the problem lies in the frontend, network, application layer, or the database layer and more.

This documentation covers:

-System initial analysis
-Key performance analysis transactions
-Workload analysis
-Network performance analysis
-Database related performance analysis
-Useful performance analysis tools
-SAP service process

 

 

 

7. General Performance: Troubleshooting Questions 2399769 34 Views

During out troubleshooting phase, we have many questions to ask and depending on your answers and results from monitors in the R/3 system, we are able to narrow down the problem.

Some of the questions you would find a Performance Engineer ask you are:
Is the Performance issue sporadic/random or does it occur at a fixed time?
If the performance issue is sporadic, run the /n/SDF/MON performance monitoring tool to check your overall system performance.
If this occurs at a specific time, it is always recommended to document this within the incident
Is this issue transaction /job specific?
Does the system performance degrade gradually throughout the day or is this a spike in poor performance?
This could indicate issues with your buffer areas. This can be checked in ST02. You should generally have no more than 10,000 swaps per day.
Can you identify a time when the performance of the system degraded?
This will help in identifying the time period in ST03N.
Have you recently implemented any changes to your system landscape?
Is this isolated to a single server?

With answers to these questions early on, we can identify the problem much faster.

 

 

 

 

8. High Wait Time analysis in SAP system 2432675 28 Views

In eight place, we have “High Wait Time analysis in the SAP System” which covers the ‘Wait Time’ value seen in Business Transaction Analysis (STAD), Workload Monitor(ST03/ST03n) or Solution Manager.

The answer to most problems like this are :
1. No sufficient work processes configured for the system
2. Work processes were occupied by long-running programs

Find out if these solutions are applicable to your problems with this KBA.

 

 

 

 

9. How to configure SSO for Fiori to Business Objects using log 2507718 26 Views

A very new but popular KBA coming from the Authentication pillar of the General Performance family. This KBA will help those who need help with Single Sign-On (SSO) for Fiori Apps that connect to Business Objects reporting.

 

 

10. Performance issue definition and determination 2456218 25 Views

This KBA is unique in a way that it offers scenarios that you may have and give advice in order to proceed with the problem. Many performance problems can encompass a single transaction or an entire SAP landscape. The aim is to identify the exact root cause in order to give suggestions or optimizations.

Some of the problems are:
Performance issue experienced by user
Long-running report
High peak loads and multiple slow transactions
ST03 high times
EarlyWatch Alert

 

 

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply