Data Interfaces

Programming Example in ABAP/4
l Example transaction in R/3: OLE
l
© SAP AG
INCLUDE OLE2INCL.
DATA: EXCEL TYPE OLE2_OBJECT.
DATA: BOOKS TYPE OLE2_OBJECT.
DATA: CELL TYPE OLE2_OBJECT.
DATA: FILENAME(50) = 'C:\TEMP\OLE1.XLS'.
DATA: VALUE(10).
CREATE OBJECT EXCEL 'EXCEL.APPLICATION'.
SET PROPERTY OF EXCEL 'VISIBLE' = 1.
CALL METHOD OF EXCEL 'WORKBOOKS' = BOOKS.
CALL METHOD OF BOOKS 'OPEN' EXPORTING #1 = FILENAME #2 = 1.
GET PROPERTY OF EXCEL 'ACTIVECELL' = CELL.
GET PROPERTY OF CELL 'VALUE' = VALUE.
WRITE: / 'Value:', VALUE.
CALL METHOD OF EXCEL 'QUIT'.
FREE OBJECT CELL.
FREE OBJECT BOOKS.
FREE OBJECT EXCEL.
The Transaction OLE is an example of OLE client functionality of ABAP/4 in the R/3 System. It allows
you direct access to the desktop applications MS Word, Excel and Visio.
Usage example for Excel:
The "Start" button generates the Excel application object and activates the application window.
There should be an Excel file on your PC. Please enter the complete path of this file in the document
area.
The "Edit File" button opens the specified file for processing in the Excel application object. At the
same time, it generates a spreadsheet object and activates the menu bars and the tools of the desktop
application.
The "Get Cell" button copies the contents of the active call in Excel to the field in the SAP data area.
You can then change this value and write it back to the active cell in Excel with "Transfer".
The "Release" button releases the OLE object
If you change the Excel sheet with "Transfer", Excel notes this and displays another dialog box for you
to confirm whether you want to save the modified file.
The example report RS41504A implements the above ABAP/4 code.