Entering content frame

Component documentation Message Recovery Locate the document in its SAP Library structure

Purpose

Messages that are not imported to the mobile client from the CRM server may block the mobile client inbound queue and not allow other messages to be imported.

Such unprocessed messages will stop the processing of the current and subsequent messages, requiring manual intervention before processing can continue.

There is a mechanism that allows users to ignore unprocessed messages and continue with the import process. This ensures that the processing of the inbound queue on the mobile client requires minimal manual intervention.

System administrators are informed about the various activities and errors that occur during the lifetime of a message through Info Agents.

Import can fail due to many reasons, some of which are listed below:

·        Data corruption at the message body level

·        BDoc Layer recordset creation failure

·        Data-save failure in the IDES database

To use the Mobile Client Message Recovery, log on to the CRM server and choose Middleware àMonitoring àMobile Client àMessage Recovery (transaction code CMWQ).

This graphic is explained in the accompanying text

It is recommended that you have thorough knowledge about messages before you begin using Mobile Client Message Recovery.

Implementation Considerations

The system administrator must determine which message needs to be extracted based on the information that can be gathered from the unprocessed message. The extract can depend on the type of message that failed to reach the mobile client.

Integration

·        To import messages to the mobile client, use ConnTrans.

·        To enable or disable the recovery of unprocessed messages by using Mobile Client Message Recovery, you need to change the customization entry in the SMOFPARSFA table. For more information, see Enabling or Disabling the Recovery of Unprocessed Messages.

Features

You use the Message Recovery mechanism to:

·        Fetch at least the message header if the message body is corrupted.

·        Extract data from CDB and resend it to the mobile client.

·        Update Tlerror.dat whenever a failure occurs and send it to the inbound queue of the mobile client. This information can also be viewed on the CRM server.

·        View the unprocessed message information either in a site-based format or in the form of a list of BDoc types on the CRM server.

Leaving content frame