The transaction to monitor the Queue is SMQ1. The outgoing IDOCs are sent to the Cloud through the Queue. The incoming IDOCs are processed using the Queue as well. By using the queue, we make sure, that the Documents are delivered and processed in the right order. However, the consequence of the queue is, that if the processing of the given document was not successful (e.g. because of the short dump, the connection failure between SAP and the Message Broker) the queue is stopped. As far as the incoming IDOCs are concerned an attempt to process the IDOC is performed and if the certain object could not be created in SAP (e.g. because of incorrect data) the IDOC gets the status 51 (the IDOC becomes red) and the processing is continued. In other words, only the critical errors (like short dumps or network errors) stop the Queue.
The following Queue identifiers are used:
Queue name | Description |
/PACG/ECM_STD_OUT | Outgoing IDOCs |
/PACG/ECM_STD_IN | Incoming IDOCs |
/PACG/ECM_FULLSYNC | Full Synchronization Requests sent from the Message Broker to the SAP |
Normally the Queue should be empty. If it is not empty but the processing takes place it points no malfunction as well (especially the full synchronization is very time-consuming operation – you can monitor the progress of handling the full synchronization by analyzing the content of the Queue):
...
Once the queue is blocked, its status will be red:
...
This status (RETRY) will be set if the connection between SAP and the Message Broker is lost. In that case the Queue is blocked. You could use the button below (after double-clicking the Queue) to push the Queue:
...
However normally it should not be needed, if you configure the scheduler for RFC Destination = none during the installation. Choose the following menu in SMQ1:
...
You will be presented with the Status of the Scheduler (consider RFC Destination = None):
...
If the Queue is blocked with the error RETRY, the queue will be pushed automatically by the Scheduler. Once the connection between SAP and Message Broker is reestablished, the messages will be sent to the Message Broker and finally to the Cloud. It can be also the case, that the Queue is blocked with the message SYSFAIL. This can occur if there is e.g. a short dump. In that case the SAP Scheduler will not push the Queue (it indicates the serious problem which is not a candidate for the resending). In that case the Queue has to be pushed manually (after solving the problem).
| Note |
|---|
The Message Queue should be monitored by the Administrator. |