Skip to content

ABAP Keyword Documentation →  ABAP − Release-Specific Changes →  Changes in Release 6.40 

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 at LOAD-OF-PROGRAM



10. Revision of ABAP keyword documentation

Other versions: 7.31 | 7.40 | 7.54

Modification 1

VALUE addition for all DATAstatements

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 during for creation of linked table types. You can now also create constants with linked table types.

Modification 2

LEAVE TO CURRENT TRANSACTION

If you enter the new addition CURRENT TRANSACTION after LEAVE TO TRANSACTION, the current transaction is called with the transaction code you 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. You can also obtain the transaction code for the current transaction with the new static method GET_CURRENT_TRANSACTION of class CL_DYNPRO.


Note

This change was also transported to Release 6.20.

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.


Note

This change was also transported to Release 6.20.

Modification 4

IF FOUND addition for the INCLUDEstatement

With the new addition IF FOUND, you can prevent syntax errors in the INCLUDE statement if the specified program cannot be found.

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).


Note

This change was also transported to Release 6.20.

Modification 6

Random Generator

System classes for creating pseudo random numbers were introduced (see classes for mathematical operations).

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.

Modification 8

Variant MESSAGE oref for messages

If you use variant MESSAGE oref you can only enter one object reference variable 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.

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.

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 the ABAP Editor and Screen Painter analyzes the index and the glossary.

The colour code in the hyperlinks has been changed as follows:

  • Link in the keyword documentation
  • Link to a glossary entry
  • Link to the SAP Library
  • Linkto a program in the current AS ABAP.