SAP CALL PROCEDURES EXTERN



Get Example source ABAP code based on a different SAP table
  



External Procedure Call
The following procedures of the same AS ABAP can be called externally:
Procedures which are intended for external calls:
Methods of global classes in class pools that are visible at the calling position, that is, public methods in all programs, protected methods in subclasses, and private methods in friends of the classes.
Function modules in function pools
Methods of local classes of other programs that are visible at the calling position if a reference variable with a reference to an object of the class was passed to the calling program
Procedures which are not intended for external calls but can still be called externally (but should not be):
Subroutines in executable programs, module pools, function pools, and subroutine pools
Static methods of local classes of a compilation unit that are visible at the call position, if the name of the class is specified dynamically using an absolute type name
During the first external call of a procedure of the same AS ABAP, its compilation unit is loaded into the ABAP_ISESS of the calling program if it has not yet been loaded. Except when loading class pools, the event LOAD-OF-PROGRAM is also raised, which calls the program constructor of the program. External calls of subroutines and methods of local classes are not recommended and are critical, since the assignment of the loaded compilation unit to a program group is usually not determined:
Program Groups in External Procedure Calls
Furthermore, external procedure calls may have different program properties between the calling and the called programs.
Fixed point arithmetic in external procedure calls

ABAP_PGL
Only call suitable procedures externally
ABAP_PGL_END



Latest notes:

Any subroutines and methods of local classes defined in an