Get Example source ABAP code based on a different SAP table
VERSION 5 GREY
Subroutines Before the introduction of ABAP Objects, subroutines were mainly used for the local modularization of an ABAP program, however, they can also be called externally. Their functions are implemented between the statements FORM and ENDFORM . A subroutine is declared immediately when implemented. Subroutines should no longer be created in new programs for the following reasons:
The parameter interface has clear weaknesses when compared with the parameter interface of methods, such as:
Positional parameters instead of keyword parameters
No real input parameters in pass by reference
Typing is only optional
No optional parameters
Every subroutine belongs implicitly to the public interface of its program, which is generally not desired.
Calling subroutines externally is critical with respect to the assignment of the compilation unit to a program group in the ABAP_ISESS . This assignment cannot generally be defined statically. In those places where subroutines cannot yet be replaced by methods ( PERFORM ON COMMIT$|ROLLBACK, GENERATE SUBROUTINE POOL), they should be used purely as wrappers for method calls and must not contain any other functional code.
Latest notes: NON_V5_HINTS The syntax allows the definition of a subroutine to be split between a declaration part and an implementation part using the statements FORM ... DEFINITION and FORM ... IMPLEMENTATION, but this is not supported by all tools and should be avoided. ABAP_HINT_END
