SAP Knowledge Base Article - Preview

2436955 - How to collect and analyze traces using ST12 (single transaction analysis)

Symptom

There is a need to analyze the performance of a particular transaction/report/job and would like to use transaction ST12 (also known as Single Transaction Analysis).

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

Transaction ST12 is available as of basis release 4.6B. It is delivered via the addon ST-A/PI (Application servicetools for EarlyWatch/GoingLive, see SAP Note 69455).

The ST-A/PI version should be 01F* or higher.

The feature to switch on the ABAP trace for another user requires:

  • on basis 4.6*: Addon ST-A/PI >= 01F*, Kernel 46D patchlevel >= 1805
  • on basis 6.x: Addon ST-A/PI >= 01G*, Kernel 640 patchlevel >= 83
  • on basis 7.0 or higher: Addon ST-A/PI 01G*

Keywords

ST12 trace , performance analysis tool , single transaction , high response time , st12 abap trace , net time , performance traces , SQL summary, stat records , ENQUEUE trace , RFC trace , ST05,SE30, /SSA/STA, Long, Report, slowness , KBA , csg_q , trace , http , workprocess , abap , st12 , analysis , SV-PERF , Performance Problems , SV-SMG-SDD , Service Data Download , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.