Types of Messages 

Messages are divided into four categories:

·        Transactional Messages:-

There are three types of transactional messages:

¡        Transaction Messages:- These messages are sent from the mobile client to the CRM server. They are requests that the CRM server gets to execute the transaction and return the result and status of the execution back to the mobile client via a confirmation or an error message.

¡        Confirmation Messages:- These messages contain the confirmation from the CRM server stating that the transaction initiated by the client was successful and data has been changed on all the concerned systems. These messages are generated by the CRM server in response to transaction messages from the client.

¡        Rejection Messages:-If the transaction is not completed successfully by the CRM server, then the mobile client receives a rejection message.

¡        UnprocessedValidation:- This message is generated only for unprocessed messages of type Confirmation or Rejection. The code for this message type is 3 instead of Q, which is normally the code for an unprocessed message. This message type is introduced to resolve the problem with the pending confirmation counter, as the same is not decremented if the message type of the replacement message is Q for an unprocessed message of type Confirmation or Rejection.

During the import of messages, the BDoc layer uses the same method to process the messages of type Unprocessedvalidation and Q. In addition, the BDoc layer decrements the pending confirmation counter if the message is successfully imported.

·        Synchronization Messages:- Synchronization messages are sent from the CRM server to mobile clients. These can be further classified into

¡        Import Messages:- Modifications from other mobile clients, the OLTP R/3 system or any other leading system are shipped to clients through import messages. They are generated in response to changes that occur in the consolidated database (CDB). Import messages are used for inserting, updating and deleting data on the client and are also used for initial download and delta download changes.

¡        Archive Messages:- This message type indicates that the data it affects is not often used and must be archived. They are usually generated by warehousing components that decide whether data is relevant for day-to-day business transactions. For example, appointments that were created a year ago could be irrelevant in the current business process and can therefore be archived.

¡        Zap Messages:- These messages are primarily used to perform large-scale deletion of data on the mobile client database. They are used to perform object-level data deletion from the database. Deletions are carried out by checking the entire BDoc hierarchy and removing those records that match the selection criteria as specified in the BDoc message.

If an unprocessed message information for a zap message (Message Type ‘Z’) has an object ID available, i.e. when the client was able to interpret the blocking message and retrieve the object ID, then the recovery message would be an import message with delete task. Otherwise, if no object ID is available, then a zap message (Message Type ‘Z’) for the referred BDoc type is sent as recovery. This recovery message is similar to the original unprocessed message. The zap message will clear all the contents of the tables mapped to the root segment. It will also clear those records of the tables that are mapped to the child segments that have foreign keys mapped to the root segment’s map table.

¡        Current State:- These messages highlight the current contents of the CDB for those records that are present in the root segment of the message. They are initiated by the leading system at certain intervals when data in the leading system and the CDB becomes inconsistent. The CRM server processes these messages and updates the CDB with the new contents. In addition, the CRM server forwards this message to the mobile clients so that their local database can be updated.

·        Service-oriented Messages :- These messages are initiated from the CRM server and are received by the client. User-defined commands are executed on the mobile client using this message. Typically these messages are used when an administrator sends upgrade information to mobile clients.

·        Bulk Messages:- The CRM server sends bulk messages to mobile clients. These messages contain data that have to be inserted into the local database of the mobile client. They are useful when a new mobile client is set up, since insertion of data in bulk mode is much more efficient and faster than inserting one row at a time. For example, sending data to clients that have newly subscribed to existing publications is done via bulk messages.

The following is applicable only for messages of type confirmation, rejection, import, bulk, and current state. The messages of type confirmation and rejection contain one object instance per message (i.e. one object ID per message), whereas the rest may contain one or more object instances. So when you trigger an extract for messages with one object ID, the recovery message has only one object ID. If no object ID is present, you will be asked if you want to extract all the objects.