ABAP Keyword Documentation → ABAP - Release-Specific Changes → Changes in Release 3.0
OLE2 Automation Controller in Release 3.0
In Release 3.0, the ABAP interpreter command set has been extended to include key words that allow application programmers to process external objects. OLE2 was supported as the first object model. With the new key words
CREATE OBJECT SET PROPERTY GET PROPERTY CALL METHOD FREE OBJECT
you can link to all applications with functionality in the form of an OLE2 Automation Server from ABAP. Examples of this would be Microsoft products such as EXCEL or WINWORD.
All applications to be accessed from ABAP must be entered in a table maintained with the transaction
SOLE. This table determines whether type information exists for an application.
The type information describes all the objects that an application can handle, all their methods and properties, as well as their parameters. It can be loaded into the
AS ABAP so that the ABAP
processor can perform the necessary type conversions and is not dependent on the language of the OLE application.
SAP recommends that you use only English names for methods and object attributes in ABAP, but the ABAP program can still process applications installed in another language.
The transaction OLE allows you to activate 3 OLE servers, and to test methods and properties by pressing certain keys.
Apart from the ABAP enhancements, an OLE-compatible SAPgui for 3.0 must also be active.
Other versions: 7.31 | 7.40 | 7.54
AS ABAP as OLE Automation Server
An AS ABAP can itself be
used as an Automation Server, i.e. you can call function modules that support Remote Function Calls
from any OLE Automation Controller. For this purpose, the server program RFCSRV.EXE must be installed on the front-end. For further information, see the RFC Automation User's Guide.