Further Changes in Release 6.40
1 VALUE addition for all DATA statements
2 LEAVE TO CURRENT TRANSACTION
3 INTO addition for the CLEANUP statement
4 IF FOUND addition for the INCLUDE statement
5 Data compression with GZIP
6 Random number generator
7 New method in CL_SYSTEM_TRANSACTION_STATE
8 Variant MESSAGE oref for messages
9 Behavior of error messages after LOAD-OF-PROGRAM
10 Revision of ABAP keyword documentation
ABAP_MODIFICATION_1 VALUE addition for all DATA
statements
The VALUE can now be used in all variants of the
DATA statement and in all related statements, like
CONSTANTS . Previously, the addition could
not be used when creating bound table types. It is now also possible to
create constants with bound table types.
ABAP_MODIFICATION_2 LEAVE TO CURRENT TRANSACTION
If the new addition CURRENT TRANSACTION is specified after
LEAVE TO TRANSACTION, the
current transaction is called using the
transaction code used to call CALL TRANSACTION or LEAVE TO
TRANSACTION . Except in the case of a
parameter transaction or
variant transactions , this is the
same transaction code as in the sy-tcode system field. For
parameter or variant transactions it is their transaction code, while
sy-tcode contains the name of the implicitly called
dialog transaction . The
transaction code for the current transaction can also be obtained using
the new static method GET_CURRENT_TRANSACTION of class
CL_DYNPRO .
Latest notes: This change was also transported to Release 6.20.
ABAP_MODIFICATION_3 INTO addition for the CLEANUP
statement
With the new addition INTO for statement
CLEANUP , a reference is made to the exception object in the
specified reference variable.
Latest notes: This change was also transported to Release 6.20.
ABAP_MODIFICATION_4 IF FOUND addition for the INCLUDE
statement
The new addition IF FOUND can be used to prevent syntax errors
in the INCLUDE statement if the
specified program cannot be found.
ABAP_MODIFICATION_5 Data compression with GZIP
System classes with methods for compressing character chains and byte
chains with GZIP were introduced (see
classes for compressing data ).
Latest notes: This change was also transported to Release 6.20.
ABAP_MODIFICATION_6 Random number generator
System classes for creating pseudo random numbers were introduced (see
classes for mathematical operations ).
ABAP_MODIFICATION_7
New method in CL_SYSTEM_TRANSACTION_STATE
In class CL_SYSTEM_TRANSACTION_STATE
there is a new method GET_SAP_LUW_KEY for determining the
update key.
ABAP_MODIFICATION_8 Variant MESSAGE oref for messages
If the variant MESSAGE oref is used,
only one object reference variable can be specified whose dynamic type
implements the system interface
IF_T100_MESSAGE for oref . The attributes of the interface
identify the message to be sent in table T100 . The use of classes
(introduced in Release 6.20) that only implement the interface
IF_MESSAGE is obsolete and only allowed for compatibility reasons.
ABAP_MODIFICATION_9 Behavior of error messages at
LOAD-OF-PROGRAM
As of Release 6.40 , a program is terminated with the runtime
error SYSTEM_LOAD_OF_PROGRAM_FAILED if the event block for
LOAD-OF-PROGRAM contains an error
message . Before release 6.40 , the system behaved according to
the context where the program was loaded.
ABAP_MODIFICATION_10 Revision of ABAP keyword documentation
The ABAP keyword documentation has been completely revised. An
alphabetic short reference , an
ABAP glossary and an alphabetic
ABAP index have been added. F1 Help in
ABAP Editor and Screen Painter analyzes the index and the
glossary.
The color code in the hyperlinks has been changed as
follows:
Link in the keyword documentation
Link to a glossary entry
Link to the SAP
Library
Link to a program in the current
AS ABAP .
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved