The ABAP keyword CALL METHOD calls the method m of the object obj. m can be literal or a variable.
Basic Form: CALL METHOD OF obj m.
Additions:
...
1. ... = f
2. ... EXPORTING p1 = f1... pn = fn
3. NO FLUSH.
The ABAP processor normally buffers all successive OLE statements and sends them in a bundle to the presentation server. However, a statement can still access the results of previous statements.
If you are working in debugging mode, then you should not forget that the return parameter values can only be displayed before the first non-OLE ABAP statement has been executed. A statement that refers to an object that has not yet been created by an OLE statement cancels the automatic bundling.
The return parameter SY-SUBRC displays whether all bundled statements have been executed successfully. It can have the following values:
● SY-SUBRC = 0:
All statements were executed successfully.
● SY-SUBRC = 1:
A system error occurred when communicating with the presentation server. Field SY-MSGLI contains a short description of the error.
● SY-SUBRC = 2:
A method call caused an error.
● SY-SUBRC = 3:
Setting an attribute caused an error.
● SY-SUBRC = 4:
Reading an attribute caused an error.
CALL METHOD is part of a group of keywords that you can use to process external objects in ABAP. At present, only the object model OLE2 is supported. All objects to be processed must therefore be of type OLE2_OBJECT. This type and other necessary data are defined in the INCLUDE module OLE2INCL.
● Addition 1 ... = f
The addition =f saves the return parameter of the method in the variable f. The return value can also be of type OLE2_OBJECT. This addition must always come before other additions.
● Addition 2 ... EXPORTING p1 = f1... pn = fn
The addition EXPORTING transfers values from fields to the parameters of the method. p1, p2, ... are either keyword parameters or position parameters.
If the parameters have to be ordered according to the sequence, then p1, p2, ... have to begin with a “#” followed by the position number of the parameter. Only position parameters are currently supported.
The EXPORTING parameters always come at the end of the statement.
● Addition 3 ... NO FLUSH.
The NO FLUSH addition continues with the bundling process even when the next statement is not an OLE statement. For example, this means that you can set a series of attributes in a loop and download them to the presentation server in a single transport operation.
As a programmer, when using NO FLUSH you must ensure that you do not rely on the content of the return parameters that have not yet been filled. All objects also have to be initialized as bundles, that is, they must already have been created by an OLE call that has already been executed.
The buffer is always downloaded for every FREE statement.

You open an EXCEL file using the ‘Open’ method.
INCLUDE OLE2INCL.
DATA
EXCEL TYPE OLE2_OBJECT.
DATA
WORKBOOK TYPE
OLE2_OBJECT.
CREATE OBJECT EXCEL
'Excel.Application'.
CALL METHOD OF EXCEL 'WORKBOOKS' =
WORKBOOK.
CALL METHOD OF WORKBOOK 'Open' EXPORTING #1 = 'C:\EX1.XLS'.
More information:
SET PROPERTY, GET PROPERTY, CREATE OBJECT and FREE OBJECT.