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 Client Properties<br />

l Facilitates the communication between application server<br />

and frontend via the RFC interface.<br />

l SpeciaI functions for OLE are implemented in the SAPGUI.<br />

l Collected calls<br />

© SAP AG<br />

n When the ABAP/4 processor encounters the first non-OLE<br />

statement, OLE 2.0 commands are sent to SAPGUI.<br />

l Language independence<br />

n The ABAP/4 processor uses the OLE object ID instead of the<br />

text names for properties and methods.<br />

Normally, all consecutive OLE statements are buffered by the ABAP/4 processor and sent to the<br />

frontend together. Here, a statement may also refer to the results of preceding statements.<br />

Even if the next command is not an OLE statement, developers can direct the collection to continue by<br />

setting a series of properties in a loop. For this functionality, you must use the NO FLUSH option with<br />

OLE calls.

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

Saved successfully!

Ooh no, something went wrong!