17.08.2013 Views

Data Interfaces

Data Interfaces

Data Interfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

OLE 2.0 Programming Tools<br />

l Maintenance Transaction SOLE for all desktop applications<br />

that can be controlled from ABAP/4.<br />

l Automatic identification of desktop objects:<br />

© SAP AG<br />

R/3 report RSOLEINT (Transaction SOLI)<br />

w reads the OLE object register on the desktop<br />

w loads objects, methods and properties into R/3<br />

l Object Browser:<br />

R/3 report RSOLETI1 (Transaction SOLO)<br />

w Browser for OLE objects, properties and methods<br />

l Special OLE include for ABAP/4 programs<br />

OLE2INCL<br />

All applications controlled by ABAP/4 must be entered in the table TOLE which you maintain with the<br />

Transaction SOLE. This table also indicates whether type information exists for a particular<br />

application. Type information describes all the objects of an application, all its properties and methods,<br />

as well as its parameters.<br />

You can load type information into the R/3 System (table OLELOAD) with the Transaction SOLI. The<br />

ABAP/4 processor can then perform the necessary type conversions and be language-independent of the<br />

OLE application. For all OLE applications delivered as standard by SAP, the English version is supplied<br />

in the OLELOAD.<br />

In addition to runtime information in the table OLELOAD, you can also use the Transaction SOLI to<br />

load other information such as documentation and WinHelp references. You can then access this<br />

information in the SAP environment with the Object Browser (Transaction SOLO).<br />

For programming in the OLE environment, you must use the OLE-specific include OLE2INCL.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!