Many factors can cause sluggish execution of a transaction or a report. 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 runtime problems is lurking there. But how do you approach such an exercise? This article demonstrates how to leverage SAP performance analysis tools to identify the critical actions or code sequences that are causing poor runtime. Depending on the results of your analysis, you can then implement the necessary corrections. The next installment of this two-part series presents commonly found performance bugs and recommended solutions.
Werner Schwarz
Werner Schwarz joined SAP Retail Solutions in October 1998 after working as a developer at two other IT companies. Today, he is the development team contact for all performance-related issues concerning the IBS-CI (Industry Business Sector - Consumer Industries). Werner’s major tasks include information rollout and support of his colleagues regarding performance during both development and maintenance.
You may contact the author at werner.schwarz@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Premium
