Active Status Confirmation by Event

Use

If a status confirmation creates an event, this event can be processed further by a receiver. An event receiver could be a single-step task or a workflow created by the customer (or application). The status information is then processed within this receiver.

For more information on workflow, see SAP Business Workflow.

Integration

Business Communication Services (BCS) trigger one of the following events on the application object instance linked with a document sent, depending on the status of the document:

• ErrorSendStatusReached

• WarningSendStatusReached

• InfoSendStatusReached

The following parameters are passed using the event container:

• Send request

• Reference to the application object

• Reference to the recipient

• Reference to the sender

• Date of status

• Time of status

• Status information as a T100 message, that is with MSGID, MSGNO, MSGV1, MSGV2, MSGV3, MSGV4

The macro SX_GETREPTYPE from the type group SX classifies the statuses into the following categories using the message numbers:

• Delivery report

• Non-delivery report

• Read notification

• Non-read notification

• Information

Activities

The event is triggered by BCS if the application object (which must be implemented as a BOR object) supports the interface IFSNDSTAT2. Therefore, the application does not have to make any setting to specify that the event be triggered.