Get Example source ABAP code based on a different SAP table
ABAP Objects in ABAP Release 6.40 ITOC
ABAP_MODIFICATION_NN Data Types and Constants in the Visibility Section of Global Classes
From ABAP_RELEASE 6.40, data types and constants can be created in the public visibility section of global classes and interfaces, which was not previously possible. Classes and interfaces therefore make the use of type pools superfluous, whereas for types and constants names that are longer than the names in the type pools are possible.
ABAP_MODIFICATION_NN Access to Static Components of Object Types
The statements CLASS cl DEFINITION LOAD and INTERFACE in LOAD are now only necessary if source code contains recursive accesses to global classes or interfaces. Until now, these statements always had to be specified if static components of global classes or interfaces were being accessed for the first time. Transaction SYNT, to which a trace for these object types has been added, can be used to detect recursive class and interface definitions.
Latest notes: This change was also transported back to ABAP_RELEASE 6.20. ABAP_HINT_END
ABAP_MODIFICATION_NN Use of Alias Names
From ABAP_RELEASE 6.40, it is possible to specify the alias names of the methods defined using ALIASES in the implementation of methods using the statement METHOD and in the redefinition of methods using the statement METHODS ...REDEFINITION. At the same time, however, from ABAP_RELEASE 6.40 there will be a warning about the syntax check if identical components are accessed within a class declaration or a method with different names.
ABAP_MODIFICATION_NN Unused Private Components
From ABAP_RELEASE 6.40, all unused private components of a class produce a warning in the extended program check. Private methods must be called and private events must be both raised and handled.
