Internal Tables in ABAP Release 7.57 - ABAP Keyword Documentation

ABAP - Keyword Documentation → ABAP - ABAP Release News → News for ABAP Release 7.5x → News for ABAP Release 7.57 →

Internal Tables in ABAP Release 7.57

1. New Addition STEP for Defining Step Size and Processing Order

2. Exception when Mixing Index Access with Hash Key Access

3. Correction for FROM Addition

Modification 1

New Addition STEP for Defining Step Size and Processing Order

The new addition STEP defines the step size and the order for processing an internal table. For the statements LOOP and FOR, STEP can be used to control the step size and the processing order. For the statements APPEND, DELETE, INSERT, VALUE, and NEW, STEP can only be used to define the step size. It is not possible to change the processing order with STEP for these statements.

Modification 2

Exception when Mixing Index Access with Hash Key Access

Access to a table index when accessing an internal table using a hash key (accessing a hashed table using its primary key or accessing any internal table using a hashed secondary key) is not allowed. When a hashed key is specified dynamically behind USING KEY in statement LOOP AT or expression FOR ... IN, usage of FROM and TO must result in an exception. This was not the case before release 7.57.

From release 7.57 on, the runtime error ITAB_ILLEGAL_INDEX_OP occurs in such a situation. Before release 7.57, the behavior was undefined.

This change is slightly incompatible.

Modification 3

Correction for FROM Addition

When a negative value is specified for FROM in statement LOOP AT or expression FOR ... IN, it is set to 1 implicitly. Before release 7.57, this was not the case in the following situation:

The internal table is accessed using a sorted key.
The internal table contains more than 10 table lines.
A WHERE condition is specified that can be optimized.

The loop was not processed at all. From release 7.57 on, the loop is processed as documented.

This change is slightly incompatible.