The simplest route to go from SELECT to RANGE
Today we’ll try to optimize the code to convert a SELECT into a RANGE
Let’s start with the simplest code, without any optimization attempt:
DATA: lt_kunnr TYPE STANDARD TABLE OF kunnr,
lr_kunnr TYPE RANGE OF kunnr,
wa_kunnr LIKE LINE OF lr_kunnr.
FIELD-SYMBOLS: <kunnr> LIKE LINE OF lt_kunnr.
SELECT kunnr
INTO CORRESPONDING FIELDS OF TABLE lt_kunnr
FROM kna1.
wa_kunnr-sign = 'I'.
wa_kunnr-option = 'EQ'.
LOOP AT lt_kunnr ASSIGNING <kunnr>.
wa_kunnr-low = <kunnr>.
APPEND wa_kunnr TO lr_kunnr.
ENDLOOP.-
7 commands
-
4 variabls
-
15 lines
Around 8 years ago I suggested that this could be improved:
DATA: r_kunnr TYPE RANGE OF kunnr,
wa_kunnr LIKE LINE OF r_kunnr.
SELECT kunnr AS low
INTO CORRESPONDING FIELDS OF TABLE r_kunnr
FROM kna1.
wa_kunnr-sign = 'I'.
wa_kunnr-option = 'EQ'.
MODIFY r_kunnr FROM wa_kunnr TRANSPORTING sign option WHERE low <> ''.-
4 commands
-
2 variables
-
10 lines
Meanwhile, with ABAP 7.40, manipulating internal tables became much simpler:
DATA r_kunnr TYPE RANGE OF kunnr.
SELECT kunnr AS low
INTO CORRESPONDING FIELDS OF TABLE r_kunnr
FROM lfa1.
r_kunnr = VALUE #( FOR wa IN r_kunnr
option = 'EQ' sign = 'I'
( low = wa-low ) ).-
2 commands
-
1 variables!
-
9 lines
But then Sérgio Fraga showed me that SQL also got better and now this can be done:
DATA r_kunnr TYPE RANGE OF kunnr.
SELECT 'EQ' AS option, 'I' AS sign, kunnr AS low
INTO CORRESPONDING FIELDS OF TABLE @r_kunnr
FROM lfa1.-
1 command!
-
1 variable!
-
5 lines
Not bad! The only possible improvement would be declaring that variable inline. But I don’t know how it could be done.
Update: Gabriel showed that it is indeed possible to declare the variable inline:
SELECT 'I' AS sign, 'EQ' AS option, kunnr AS low, kunnr AS high
INTO TABLE @DATA(r_kunnr)
FROM lfa1.-
1 command!
-
0 variables!
-
3 lines!
The 7 commands, 4 variables and 15 lines are now reduced down to 1 command and 3 lines. I dare say that now it is finally impossible to further simplify this.
Greetings from Abapinho.