AS ABAP Release 758, ©Copyright 2024 SAP SE. All rights reserved.
ABAP - Keyword Documentation → ABAP - ABAP Release News → News for ABAP Release 7.0 and its EhPs → News for ABAP Release 7.0, EhP2 →
Mail Feedback
Lazy Loading of Programs in ABAP Release 7.0, EhP2
When compiling an ABAP program before ABAP release 7.0, EhP2, all associated include programs were loaded when first accessing a global class, a global interface, or a type pool. These includes contain declarations of the corresponding class, interface, or type pool which can be used globally.
From ABAP release 7.0, EhP2, these include programs are not loaded until an element declared in them is actually required. For example, a class class is no longer loaded when a TYPE REF TO class type reference is made, but when a component of the class is accessed or the class itself.
This internal optimization of ABAP Compiler has the following additional consequences:
1. Statement TYPE-POOLS is Obsolete
2. Addition LOAD for CLASS and INTERFACE is Obsolete
Statement TYPE-POOLS is Obsolete
The statement TYPE-POOLS is no longer required for the use of a data type, a constant, or a macro from a type pool. The elements of a type pool can now be addressed in the same way as all other objects in ABAP Dictionary without previously loading the type pool.
TYPE-POOLS statements are ignored by ABAP Compiler from ABAP release 7.0, EhP2, and can be deleted.
In list processing in particular, the include programs <LIST>, <SYMBOL>, <ICON>, <LINE>,
and <COLOR> are no longer needed, since they only contain TYPE-POOLS statements.
Addition LOAD for CLASS and INTERFACE is Obsolete
The now rarely used statements
are no longer required
From ABAP release 7.0, EhP2 these statements are ignored by ABAP Compiler and can be deleted.