Send Process and Status Confirmation

Use

For internal sending the whole send process runs synchronously. The return codes for the Submit method are final in this case. Further status information is not obtained. No status event is triggered.

For external sending the status confirmation is more complex. Therefore, firstly the rough process of external sending will be presented:

1. The whole recipient list is broken down into individual recipients and a send order is placed in the queue for each individual recipient.

2. The next SAPconnect send process reads the send orders from the queue and determines the responsible nodes that represent the external communication systems in the SAP system.

3. The send orders are transferred to the relevant responsible external communication system, for example, to a fax server.

From the view of the sender, only the first step is synchronous. The rest of the process is asynchronous. The return codes that the Submit method returns can, therefore, only refer to the first, synchronous part. Furthermore, the fact that there are, for the most part, several recipients (for example, a distribution list) must also be taken into account. Thus, the Submit method returns the following return codes:

• SY-SUBRC after method call

  This is 0 as soon as the send order has been successfully placed in the queue for at least one recipient.

• Export parameter SentToAll

  This is 0 when the send orders have been successfully placed in the queue for all recipients.

• Export parameter RecipientsInfo (Table of structure SOSNDINF)

  This table contains the object keys and the return code for the broken down recipients. The return code for a recipient is 0 when the send order has been successfully placed in the queue for this recipient. Further status information is confirmed asynchronously by event. This exact object key is then reported in the event container under the parameter Address.