Display of Process Message Lists 
You can display lists of process messages on the overview screen of the message monitor: see
Accessing the Message Monitor.All messages that exist within process management can be displayed in the monitor. You can reduce the scope of the list using the following selection criteria:

The process order can only be used as a criterion for selecting a message if the characteristic PPPI_PROCESS_ORDER is contained in the message.
In the monitor, all messages are displayed with their creation time, message category, sender and send status. The messages are highlighted using different colors according to their status so that you can quickly spot those where an error occurred. For detailed information on the errors, you need to refer to the corresponding message logs (see
Process Message Logs ).The following table lists possible message statuses and their meaning:
Icon |
Status |
Meaning |
|
To be sent |
The process message is created but has not yet been sent to its destinations. |
|
Sent |
The process message has been sent to its destinations. |
|
Sent with warning |
The message log contains a warning message. The process message has been sent to its destinations despite the warning. |
|
To be resubmitted |
One of the message destinations was temporarily not available. |
|
To be resubmitted with warning |
One of the message destinations was temporarily not available. Additionally, a warning message was issued by one of the other destinations to which the message was sent. |
|
Message incomplete |
The process message does not contain all required characteristics of the message category. It has not been sent. |
|
Destination error |
The process message could not be processed by one of its destinations. |
|
Processing terminated |
The processing of the message was terminated due to an error. The message has not been sent to any of its destinations. |

If a process message is to be sent to an external system, its status is set to Sent or Sent with warning as soon as the message has been transferred to the corresponding tRFC (transactional remote function call). The execution of a tRFC is documented in a log which you can access from the message monitor (see