This document Describes  simple steps to  take performance trace at runtime  in Debugger.SAT ABAP TRACE helps to make the correct conclusions about genuine sources of poor performance. It pinpoints the ‘slow’ source code. For example, some ‘quick’ method triggers ‘slow’ determination. Classical SAT trace in this case shows that we have ‘slow’ method, while actually determination should be fixed or logic redesigned.

This following Step will explains how a developer can trace the performance for particular lines of code while Debugging and can also trace all the background process getting triggers for specific lines for which the trace has been activated.

Here we are not talking about taking the trace for entire execution but the given steps  will guide you through how one can trace a specific and only required code while debugging.

STEPS:


1. Set breakpoints at places that have already been identified as ‘slow’. All the following trace will be done between these breakpoints. Start execution of the logic. Press button ‘New tool’.

/wp-content/uploads/2016/05/tr1_946394.png

2. Choose ‘Trace (SE30/ST05)

/wp-content/uploads/2016/05/tr2_946395.png

3. Activate ABAP Trace. Continue execution the logic.

/wp-content/uploads/2016/05/tr3_946396.png

4. Deactivate trace. The icon of created trace file is to be shown.

/wp-content/uploads/2016/05/tr4_946397.png

5. Launch SAT transaction->’Evaluate’ tab. Make double click on the crated trace file.

/wp-content/uploads/2016/05/tr5_946398.png

6. Go to ‘Desktop 2’ tab and investigate the tree of calls

/wp-content/uploads/2016/05/tr6_963394.png

For More Detail Feel Free to Contact.:

To report this post you need to login first.

2 Comments

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

Leave a Reply