ABAP Keyword Documentation → ABAP − Release-Specific Changes → Changes in Releases 4.0 and 4.5
Further Changes in Release 4.0
1. EDITOR-CALL FOR itab: Better performance
3. DATA: Fields with '+' or '()' at the end
5. WRITE: New formatting option NO-GROUPING
6. WRITE: Better performance at WRITE (name)...TO
7. SET RUN TIME ANALYZER: Addition MODE no longer applies.
8. Arithmetic with DICTIONARY types INT1 and
INT2
9. PERFORM form(prog): Better performance for addition IF FOUND
10. Contexts
Other versions: 7.31 | 7.40 | 7.54
Modification 1
Better performance at EDITOR-CALL FOR itab
The table is only returned with changes if it has been saved in the Editor. Use
the new addition ... BACKUP INTO to return the table to its original condition.
Return Code informs you whether or not the change operations were carried out in the Editor.
Modification 2
New variant DESCRIBE FIELD f INTO td
You can use this new variant to determine all of the attributes of a data object f.
In addition, you can use a simple DESCRIBE with the addition
"HELP-ID hlp" to determine which help ID belongs to f if any.
Modification 3
DATA: Fields with ending with a '+' or '()' are no longer allowed.
Modification 4
ABAP types 1 and 2
In Release 3.x the ABAP types 1 and 2 were still supported in some areas
in a very basic manner in order to retain R/2 compatibility. This is no longer the case in Release 4.0.
Modification 5
WRITE: New formatting option NO-GROUPING
If a field of type I or type P is displayed, its triad separator is suppressed.
Modification 6
WRITE: Better Performance at WRITE (name) TO...
If the contents of field name are invalid, a return code is set and the target field is left unchanged.
Modification 7
SET RUN TIME ANALYZER ON/OFF
The addition MODE is no longer allowed.
Modification 8
Arithmetic with DICTIONARY types INT1 and INT2
Assignments and arithmetic using DICTIONARY types INT1 and INT2 as target fields must remain within the following value ranges:
-
INT1: 0 to 255 -
INT2: -32768 to 32767.
Otherwise a runtime error is triggered.
Modification 9
PERFORM form(prog): Better performance for addition IF FOUND
The PERFORM statement is ignored if the program entered cannot be found.
Modification 10
Contexts
For an overview of Contexts refer to this chapter.