It sounds great, we improved the performance, but we still need to define them, before
using them. :(
1 FIELD-SYMBOLS <fs_flight_schedule> TYPE spfli.
2
3 LOOP AT flight_schedules ASSIGNING <fs_flight_schedule>.
4 ...
5 ENDLOOP.
NEW VERSION
From 7.4 SP02, we can define Field Symbols as embedded into the given context (for
example into a LOOP). It means, that our <fs_flight_schedule> field symbol is valid
only inside of the LOOP statement.
1 LOOP AT flight_schedules ASSIGNING FIELD-SYMBOL(<fs_flight_schedule>).
2 ...
3 ENDLOOP.
If we can perform inline field symbol declaration in case of LOOPs, then of course we
can use them in case of READ TABLE statements!
OLD VERSION
Before 7.4, we need to declare a field symbol separately, before using it.
1 FIELD-SYMBOLS <fs_flight> TYPE sflight.
2
3 READ TABLE flights ASSIGNING <fs_flight> INDEX 1.
4 ...
NEW VERSION
The code speaks for itself!
1
READ TABLE flights ASSIGNING FIELD-SYMBOL(<fs_flight>) INDEX 1.
2