SAP NetWeaver AS ABAP Release 752, ©Copyright 2017 SAP AG. All rights reserved.ABAP - Keyword Documentation → ABAP - Release-Specific Changes → Changes in Release 7.0 and its EhPs → Changes in Release 7.0, EhP2 →
Lazy Loading of Programs in Release 7.0, EhP2
When compiling an ABAP program before Release 7.0, EhP2, all associated include programs were loaded when first accessing a global class, a global interface, or a type group. These includes contain declarations of the corresponding class, interface, or type pool which can be used globally.
From 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.The statement TYPE-POOLS is obsolete
2.The addition LOAD for CLASS and INTERFACE is obsolete
The 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 group. The elements of a type group can now be addressed in the same way as all other objects in ABAP Dictionary without previously loading the type group.
TYPE POOLS statements are ignored by ABAP Compiler from 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.
The addition LOAD for CLASS and INTERFACE is obsolete
The now rarely used statements
are no longer required
From Release 7.0, EhP2 these statements are ignored by ABAP Compiler and can be deleted.