Get Example source ABAP code based on a different SAP table
Further Changes in ABAP Release 4.0 ITOC
ABAP_MODIFICATION_NN Improved Behavior in 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. ABAP_SUBRC is used to indicate whether change operations were performed in the editor.
ABAP_MODIFICATION_NN 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.
ABAP_MODIFICATION_NN Invalid Declarations>
Fields ending with a '+' or '()' are no longer allowed in DATA>.
ABAP_MODIFICATION_NN ABAP Types 1 and 2>
In ABAP_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 ABAP_RELEASE 4.0.
ABAP_MODIFICATION_NN WRITE>: New Formatting OptionNO-GROUPING>>
If a field of type I> or type P> is displayed, its thousands separator is suppressed.
ABAP_MODIFICATION_NN WRITE>: Improved Behavior in WRITE (name)...TO>>
If the content of the field name> is invalid, a return code is set and the target field is left unchanged.
ABAP_MODIFICATION_NN SET RUN TIME ANALYZER ON/OFF>>
The addition MODE> is no longer used.
ABAP_MODIFICATION_NN Arithmetic Using DICTIONARY> TypesINT1> 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.
ABAP_MODIFICATION_NN PERFORM form(prog)>: Improved Behavior for Addition IF FOUND>>
The PERFORM> statement is ignored if the program specified cannot be found.