). The following diagram shows the most important instances:
At runtime, the first step is to create a central instance to manage the Office integration. Its methods generate further objects that are required for control and communication during the session.
- The management instance contains technical data required to initialize the communication with the SAPgui using the CET interface. The CET interface communicates with special SAPgui controls that are connected to the office application by means of an OLE2 interface.
- The instance for document administration contains information about the URL address of documents. You can trigger office applications functions using the implemented methods. The instance also records office application events that you can react to in your ABAP program.
- There are two ways of transferring data between the R/3 System and the desktop application:
- Using the link server instance to administer embedded links in the office application to objects in the R/3 System (fields, tables, and so on)
- Using the Table Collection instance. This is particularly suitable for working with tables. You can also transfer data from the desktop application to the R/3 System.
- If the office application has a standard interface, you can use its functions to edit the document (select, copy, delete, ...). You may also create additional toolbars.
- If there are also specific interfaces available for a particular application, you can create instances of these as well. Desktop Office Integration contains the following interfaces:
Instances for SAP Desktop Office Integration