ST04 – A Magic Transaction for SAP performance tunning – II


***************** Index of Pages on the topic…. ****************************
1. SAP Tuning – Gather Symptoms.
2. ST04 – A Magic Transaction for SAP performance tuning – I
3. ST04 – A Magic Transaction for SAP performance tuning – II
4. ST02 – SAP Tuning – Another Magic transaction – I (Part 4)
5. ST02 – SAP Tuning – Important SAP Parameters – II
6. ST03n – The meter gauge for SAP tuning
7. A handy reference for SAP Memory
******************************************************************************

Go to the detail screen of ST04.

This has some exciting buttons – namely – Oracle Session, SQL request, Table access etc….These will actually lead you to see the facts inside SAP database.. What is happening? Who is killing your SAP? Unless there is a bug in the system, or some user is selecting parameters abnormally in the any report executing transaction, normally SAP system does not misbehave or slowdown. At least in that case you can directly refer to SAP support and get it done. Eliminating these two rest is the customised programs, for which SAP support can be accessed on charge basis.

Remember here you are getting free guidelines on SAP customized program tuning ;)…

Anyway, jokes apart,  out of all those buttons mentioned above, Oracle session is for something what helps to see the actual session which is being processed whereas SQL request is showing current as well as history of the SQL statements. This SQL statements are comming out as a result of OpenSQL statements used in ABAP.

Clicking on “SQL Request” button will show you another screen with parameters, keep everything empty there and execute. Roughly it will bring out most of the SQL statements with their calling program name (remember Program Name not the SAP Transaction ). The straight method is to

  1. Search for those lines which have maximum Disk Read and maximum buffer fetch per record.
  2. Now click on each of those line will show you the resource cost of the SQL statement.
  3. Also you can go the line of the abap code from the statement is generated.
  4. Show the same to the ABAPER and ask to tune. You may also look into the scenario of possibility of creating index or wrong/incomplete joins and dig further.
  5. If you are preparing a report and handover all the problematic situations together then also check out / include those programs which are using too much buffer but fetching relatively low number of records…These programs slow poisoning your system, they are not only running inefficiently but also not allowing other programs to use the resources required.

Some of you may raise your eyebrows and say I am not using Top Down Attitude of the tuning…But I storngly belive that if some thing can be tuned and built better even in incorrect global / system wide parameters, that will run more better in case of those global / system wide parameters are corrected.

This transaction also have a good button which allows different dynamic performance views (V$) which are a very good resource for looking into more deep..Memory analyzing etc…..

***************** Index of Pages on the topic…. ****************************
1. SAP Tuning – Gather Symptoms.
2. ST04 – A Magic Transaction for SAP performance tuning – I
3. ST04 – A Magic Transaction for SAP performance tuning – II
4. ST02 – SAP Tuning – Another Magic transaction – I (Part 4)
5. ST02 – SAP Tuning – Important SAP Parameters – II
6. ST03n – The meter gauge for SAP tuning
7. A handy reference for SAP Memory
******************************************************************************
Advertisements

3 thoughts on “ST04 – A Magic Transaction for SAP performance tunning – II”

  1. Excelente explicacion!!!!!!!!!!! me ha servido mucho para verificar la performance del sistema.
    Muchas gracias!!!!!!

  2. I don’t see the screen for ST04 just for ST02.

    Very useful documentation.

    Regards.

    Denis

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s