Naimesh Patel | Last Updated on July 29, 2015

Parallel Cursor – To speed up performance of Nested LOOP

Technique to speed up the performance of the Nested LOOP – Parllel Cursor Today, we will tackle down the biggest performance related issue around the Nested Loops. Preface Traditionally in ABAP, we use the LOOP using the WHERE clause for Nested loops. This type of nested loops are very common in our day-to-day programming. But,…

Parallel Cursor – 2: without using READ

Parallel Cursor without using READ In previous post , we have seen a technique how to speed up the performance of the nested LOOP constructs in ABAP. In today’s post, we will see another variance of the Parallel cursor technique. In this technique, we will exit out the inner LOOP when both keys are not…

Use of Field-symbols vs Work area

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…

Measure the Performance between Break-Points using SE30

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-ONLY attribute vs GETTER methods

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…

Performance of ITAB Copy

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,…

Performance of Using Keys in SELECT with FOR ALL ENTRIES

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.

ABAP Internal Table Performance for STANDARD, SORTED and HASHED Table

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

ABAP Internal Table Secondary Key Performance comparison

Performance is the driving factor when using the Secondary Keys on the ABAP Internal Tables. So, Lets check out ABAP Internal Table Secondary Key Performance comparison.

ABAP build a table with Unique Keys – Performance Comparison

Lets check out various different options to build up table with unique Keys along with Performance Comparison.

ABAP Parallel Cursor – Things to Remember

ABAP Parallel cursor is a nice technique to improve the performance of the nested loops. There are always few things to remember while implementing the parallel cursor.

Use of REFERENCE variable vs Workarea vs Field-Symbols

Along with ASSIGNING addition for the itab processing, we have REFERENCE INTO. Let’s take a deep dive into its usage.

FOR ALL ENTRIES – Why you need to include KEY fields

ABAP FOR ALL ENTRIES is handy, but would create lot of data inconsistencies if you don’t use it properly.

ABAP Performance for DELETE on ITAB

DELETE on ITAB is widely used when you need to filter out the entries. Lets see the performance for different Delete statements.