Unprocessed Message Occurrence and Recovery 

Process Flow

...

       1.      ConnTrans is executed.

       2.      Data import fails. There are two phases during the data import process.

                            a.      First phase - the message contents are obtained.

                            b.      Second phase - the messages are converted into map table format and operations are executed on the physical database.

       3.      The reasons for the failure (error information) are collected and sent to the outbound queue of the mobile client. The error information is also displayed to user by ConnTrans.

       4.      The unprocessed message that is stopping the import of other messages is deleted. The subsequent messages are imported unless another unprocessed message is encountered.

       5.      The error information is sent from the outbound queue of the mobile client to the CRM server where it is logged.

Details that are sent include message ID, message type, BDoc name and type, site name, and object ID (root ID).

       6.      This information is displayed to the user once the transaction CMWQ is executed in the CRM server.

       7.      The system administrator extracts data from the CDB and sends a replacement message for the one that was deleted in the inbound queue of the mobile client.

If the unprocessed message that is extracted has no object ID associated with it, then all objects that are subscribed by the site are extracted from the CDB and sent to the site.

The extraction of the replacement message is upto the discretion of the system administrator who must take into consideration the message type before starting the extract process.

The process is outlined here: