SAP Tools & Utilities

13 Sep: Layer-Aware Debugging (SLAD) in SAP Demystified

How many of us have had this happen during debugging? You need to analyze a bug, or you want to find out how an application works. And you don’t know where exactly to set a breakpoint. So you start the ABAP Debugger and start stepping through the code. And you keep on stepping through the code, endlessly, without reaching any of the application logic in which you are interested! Well there is a solution and its Software Layer-Aware Debugging (SLAD), sometimes referred to as Profile Controlled Debugging.

23 Aug: World Class Utility Makes getting a WHERE-USED on a RFC Push Button Easy – Part 2

Typically, you use the delivered WHERE-USED functionality of the Repository Information System (SE84) inside an SAP instance to discover where the subject object is called or referenced. But what if the objects calling reference is not in the system that has the RFC? You could log on to every SAP system and do a Where-Used, or we can learn from Henry and use his tool. Part 2 of this series does a deep dive into the ALV design and programming, and delivers the user the entire code base.

19 Jul: World Class Utility Makes getting a WHERE-USED on a RFC Push Button Easy – Part 1

Typically, you use the delivered WHERE-USED functionality of the Repository Information System (SE84) inside an SAP instance to discover where the subject object is called or referenced. But what if the objects calling reference is not in the system that has the RFC? You could log on to every SAP system and do a Where-Used, or we can learn from Henry and use his tool. Part 1 of this series lays the foundation for understanding the problem and how to address it.

10 Jan: ABAP Database SQL Analysis Using The Performance Trace – Part 2

ots of factors can give rise to slow execution of a transaction or a report. Sometimes there are general system problems. Sometimes users use the program in a way it was not designed for. Sometimes the nature of the application and workload calls for parallel processing. And sometimes the source of the performance issue can be traced back to your ABAP code, mainly the construction of your OPEN SQL.

While there are many reasons other than database performance that could be causing the performance problem, this blog series will focus on just this aspect. If you’ve ruled out deficiencies in the system setup, mishandling by users, or the need for parallel processing, then you need to revisit your code and see if the source of your performance problem is hiding there.

21 Dec: ABAP Database SQL Analysis Using The Performance Trace – Part 1

Lots of factors can give rise to slow execution of a transaction or a report. Sometimes there are general system problems. Sometimes users use the program in a way it was not designed for. Sometimes the nature of the application and workload calls for parallel processing. And sometimes the source of the performance issue can be traced back to your ABAP code, mainly the construction of your OPEN SQL.

While there are many reasons other than database performance that could be causing the performance problem, this blog series will focus on just this aspect. If you’ve ruled out deficiencies in the system setup, mishandling by users, or the need for parallel processing, then you need to revisit your code and see if the source of your performance problem is hiding there.

14 Nov: ABAP Runtime Analysis Using The New SAT Transaction – Part 3

SAT is the transaction name of the new ABAP Runtime Analysis Tool, which is one of the most significant improvements in ABAP in the NetWeaver 7.0 EhP2. For those of you who are already familiar with the transaction SE30, the former ABAP Runtime Analysis Tool, transaction SAT is the successor of SE30. SAP has completely enhanced the tool with effective new analysis tools and features.

19 Oct: ABAP Runtime Analysis Using The New SAT Transaction – Part 2

SAT is the transaction name of the new ABAP Runtime Analysis Tool, which is one of the most significant improvements in ABAP in the NetWeaver 7.0 EhP2. For those of you who are already familiar with the transaction SE30, the former ABAP Runtime Analysis Tool, transaction SAT is the successor of SE30. SAP has completely enhanced the tool with effective new analysis tools and features.