abap

Unlike languages that are intended primarily for building software tools, the ABAP programming language has evolved for 20+ years, driven by the needs of business application development. Consequently, as an SAP application developer, ABAP offers you some unique features that are not typically available in other languages. In particular, the concept of dynamic programming enables you to easily add runtime customization to your ABAP programs in several ways. Mastering these techniques will make your ABAP programs more powerful and flexible.

Unlike languages that are intended primarily for building software tools, the ABAP programming language has evolved for 20+ years, driven by the needs of business application development. Consequently, as an SAP application developer, ABAP offers you some unique features that are not typically available in other languages. In particular, the concept of dynamic programming enables you to easily add runtime customization to your ABAP programs in several ways. Mastering these techniques will make your ABAP programs more powerful and flexible.

Unlike languages that are intended primarily for building software tools, the ABAP programming language has evolved for 20+ years, driven by the needs of business application development. Consequently, as an SAP application developer, ABAP offers you some unique features that are not typically available in other languages. In particular, the concept of dynamic programming enables you to easily add runtime customization to your ABAP programs in several ways. Mastering these techniques will make your ABAP programs more powerful and flexible.

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.

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.

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.

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.

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.

When the workflow starts you have an instance of the BOR object which is defined by the key fields that were instantiated and passed during the normal event creation. Now you want to instantiate the class which you are going to utilize. Leveraging the class we developed in the previous blogs, create a method that has in input parameter as which is the key to the class, and an export parameter that is a type reference to your class. The method ‘CREATE_INSTANCE’ is defined as static and public.

Creating a class that can be used by workflow is a little more time consuming than creating a copy of a standard SAP Business Object and delegating your new object, but once you have done it a few times it is rather simple and allows you to utilize ABAP OO.

Pin It on Pinterest

THIS WEBSITE USES COOKIES: By clicking "Accept", you agree to the use of cookies and similar technologies to enhance your browsing experience, and analyze your engagement with our content. Read our Privacy Policy.