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 for WRITE (name)...TO
7. SET RUN TIME ANALYZER: Addition MODE obsolete.
8. Arithmetic using 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 of EDITOR-CALL FOR itab
The table is only returned with changes if saved in the editor. The new addition
... BACKUP INTO is used to return the table to its original state.
Return Code is used to indicate whether change operations were performed in the editor.
Modification 2
New variant DESCRIBE FIELD f INTO td
This new variant can be used to determine all of the attributes of a data object f.
Also, a simple DESCRIBE can be used with the addition "HELP-ID hlp" to determine which help ID belongs to f if any.
Modification 3
DATA: Fields 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 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 thousands separator is suppressed.
Modification 6
WRITE: Better Performance for WRITE (name) TO...
If the content of the field name is 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 used.
Modification 8
Arithmetic using 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 produced.
Modification 9
PERFORM form(prog): Better performance for addition IF FOUND
The PERFORM statement is ignored if the program specified cannot be found.
Modification 10
Contexts
An overview of contexts is provided here.
This translation does not reflect the current version of the documentation.