Scroll Top

technology framework

Home Tag

By Anthony Cecchini ABAP Database SAP Tools & Utilities

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.

By Anthony Cecchini SAP Tools & Utilities

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.

By Anthony Cecchini SAP Tools & Utilities

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.

clients

By Anthony Cecchini SAP Tools & Utilities

15 Sep: ABAP Runtime Analysis Using The New SAT Transaction – Part 1

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.

By Anthony Cecchini SAP Tools & Utilities

10 Aug: Using Memory Inspector to Analyze Usage in Real Time

As of Release 7.0 EHP2, the New ABAP Debugger offers a suite of three tools for analyzing memory use in a program that you are debugging. These three tools are the following…The Memory Analysis tool. This is the general purpose tool for memory analysis. You can see how much memory is in use, which objects are using the memory, and the containment hierarchy (Dominator Tree) in the memory objects. This tool is quite similar in its function set to the Memory Inspector. However, in the Debugger, you can also display the contents of memory objects. For example, you can see the lines in the body of an internal table. From the Memory Analysis tool, you can create a memory snapshot for later analysis in the Memory Inspector. Choose Create Memory Snapshot from the context menu or by choosing Services of the Tool (Services of the Tool). You can also start the Memory Inspector directly from the Debugger to compare memory snapshots.

By Anthony Cecchini SAP Tools & Utilities

13 Jul: Evaluating the Quality of Your ABAP with Code Inspector – Part 3

ABAP is a powerful language for building sophisticated applications. But as any developer is understands, even the most carefully written and tested objects can wind up terminating with a runtime errors, producing unexpected messages, returning incorrect results, or causing application performance problems. As a result, SAP provides a comprehensive set of specialized tools for performing static code checks, coverage analysis, post-mortem analysis, runtime traces, and debugging as part of the standard delivery of SAP Web Application Server (Web AS).

By Anthony Cecchini SAP Tools & Utilities

15 Jun: Evaluating the Quality of Your ABAP with Code Inspector – Part 2

ABAP is a powerful language for building sophisticated applications. But as any developer is understands, even the most carefully written and tested objects can wind up terminating with a runtime errors, producing unexpected messages, returning incorrect results, or causing application performance problems. As a result, SAP provides a comprehensive set of specialized tools for performing static code checks, coverage analysis, post-mortem analysis, runtime traces, and debugging as part of the standard delivery of SAP Web Application Server (Web AS).

By Anthony Cecchini SAP Tools & Utilities

16 May: Evaluating the Quality of Your ABAP with Code Inspector – Part 1

ABAP is a powerful language for building sophisticated applications. But as any developer is understands, even the most carefully written and tested objects can wind up terminating with a runtime errors, producing unexpected messages, returning incorrect results, or causing application performance problems. As a result, SAP provides a comprehensive set of specialized tools for performing static code checks, coverage analysis, post-mortem analysis, runtime traces, and debugging as part of the standard delivery of SAP Web Application Server (Web AS).

By Anthony Cecchini SAP Tools & Utilities

12 Apr: The Quality of your ABAP Development

ABAP is a powerful language for building sophisticated applications. But as any developer is understands, even the most carefully written and tested objects can wind up terminating with a runtime errors, producing unexpected messages, returning incorrect results, or causing application performance problems. As a result, SAP provides a comprehensive set of specialized tools for performing static code checks, coverage analysis, post-mortem analysis, runtime traces, and debugging as part of the standard delivery of SAP Web Application Server (Web AS).

By Anthony Cecchini Functionally Technical

18 Feb: Debugging ABAP for Functional Teams – Part 1

Debugging is the way to find the root cause of certain SAP transactional behavior (e.g., finding a reason why a certain value in a field was updated or determining why users receive an error, warning, or abnormal termination message during the processing of a transaction). Debugging is necessary if the root cause cannot be determined from functional methods such as checking customizing or master data.

Since ABAP is the backbone of SAP, at one point or another, every member of a functional team must have had to deal with SAP development technicalities behind the business functionality. This need for technical details can occur during various phases, such as writing functional specifications or analyzing a production environment issues.

1 2