Article

Standard Table is the most widely used table Type. It has performance drawbacks if not used properly.

Read more

Article

You would get insight from Performance perspective when not using the Keys in SELECT with FOR ALL ENTRIES. System would spend definitely more time when there mixture of Entries in the ITAB.

Read more

Article

Performance of ITAB Copy

on June 13, 2011

3, 9,130

Today, we’ll see another performance drainage – Internal Table Copy. If we don’t use the data properly, we’ll run into the situation where we’ll use lot of resoruces to perform the ITAB copy and end up reducing the performance of our application. Sometimes, we pass the ITAB from one application to diffrent FM / Method,…

Read more

Article

READ-ONLY is something different for the people who have worked on the OOP in the past. Like JAVA doesn’t have the read only addition. So, there is a hot discussion going on in SAP ABAP Objects world, why READ-ONLY is there and what is the purpose of it. Let’s unleash the READ-ONLY (and its power…

Read more

Article

Using transaction SE30 measure the Performance between breakpoints We can measure the runtime and check the performance of the program by using the transaction SE30. SAP Help on the Runtime Analysis using SE30. Today we will elaborate the option to measure the performance of the specific part of the code using the SE30. This option…

Read more

Article

To use the Field-symbols against the Work Area for Internal table processing. We’ll also measure the difference between both of the techniques. Basics Internal table processing is essential part of any ABAP program. Generally, we use the explicit work area to process the internal table like appending & modifying records. We can reduce the time…

Read more

More Post →
You seem to be new here. Subscribe to stay connected.