What does it do? Both statements have the same semantics and call the method that is specified statically with the name meth>>.
The first statement prefixes the standalone method call> with a CALL METHOD>.
The second statement does not have any parentheses for filling the parameter interface. Instead, either an explicit parameter list> is specified or no parameter list at all. In the second variant without parentheses, no chained method calls> are possible and the operators NEW>> and CAST>> cannot be used to specify the method.
Latest notes:
The static method call described here must not be confused with the call of static methods>. A static method call is the static specification of an instance method> or a static method. In addition, there is the dynamic method call>, for which the methods are specified dynamically. The statement CALL METHOD> is now only intended for dynamic method calls> and distinguishes them clearly from static calls. NON_V5_HINTS
CALL METHOD> is no longer recommended > for static method calls>.
It is not necessary to prefix the recommended syntax> with CALL METHOD> since this would make programs harder to read.
The syntax without parentheses is based on function module calls> and is obsolete. The syntax involving parentheses, however, standardizes both standalone and functional method calls. ABAP_HINT_END
ABAP_EXAMPLE_VX5 The three method calls in the following source code section have the same meaning. The first two calls are the obsolete variants with CALL METHOD>: one without parentheses and one with. The third call is the recommended variant without CALL METHOD>. ABEXA 00076 ABAP_EXAMPLE_END