Indirect Connection using Message Control
Use
If your application already sends documents using Message Control, you can connect to the Business Communication Interface (BCI) indirectly.
Features
If you connect your application to the BCI using Message Control, not all of the BCI functions are available. You can use the following functions:
-
Linking of the Application Object with the Document Sent
Activities
The application object has to be a BOR object. A NAST object is not adequate.
The application BOR object must support the IFNAST interface so that the ConvertKey method can be used.
If the BOR object and the NAST object have different keys, you have to redefine the ConvertKey method with the actual conversion. The interface of the function module MESSAGING has been extended to include the BOR object type and the key of the NAST object for this purpose. They are transferred via the following import parameters:
Import Parameters
Description
PI_OBJTYPE
Type of application BOR object
MSG_OBJKY
NAST object key
Within Message Control, the BOR object key is then determined using the ConvertKey method and the object link is created using the BCI.
-
Activities
No further activities are necessary.
-
Status Confirmation by Events in the Application Object
Activities
The application object has to have been linked with the document sent (see above).
The application object must support the interface for the event triggered by the status confirmation.
-