Processing Status 
During message processing, each XML message passes through particular statuses. These statuses are represented by a corresponding icon in the Status or Acknowledgment Status column in the list of processed XML messages. You can display such a list of XML messages in the monitor for processed XML messages.
· If you have not called any versions of the XML message, then the system displays the overall processing status of the message. This corresponds to the status following the last processing step executed.
· If you have already called the versions of the message, then the system displays the status of the respective processing step.
Explanation of the Different Statuses
The following statuses refer to the statuses of synchronously and asynchronously processed XML messages.
The statuses in the first table each refer to a status whereby processing is complete, while the statuses in the second table refer to an error status.
Completed Processing of Synchronous and Asynchronous Messages
|
Status |
Meaning |
|
|
Message processed correctly. This might only apply for the current system for asynchronous processing. |
|
|
A message with this message ID already exists in the receiver system. Processing is therefore completed for the sender system. |
|
|
A message with errors was acknowledged and can therefore be deleted with the next delete job. |
|
|
The message has already been recorded but has not yet been released for processing. |
|
|
Receiver identification is complete and multiple receivers have been identified. As a result, the message will be branched. Message processing is complete for this message. The two new messages produced following branching are processed further, however. |
Error Statuses of Synchronous and Asynchronous Messages
|
Status |
Meaning |
|
|
A system error occurred during message processing in the SAP Exchange Infrastructure. In synchronous processing the error is returned to the sender. |
|
|
An application error occurred during message processing. For asynchronous processing, this status only occurs in the receiver system, for synchronous processing, it occurs in all systems involved. |
|
|
Receiver identification is complete and no receivers have been identified. Message processing is therefore complete for this message. |
The following statuses refer to intermediate statuses in message processing. They only apply to asynchronously processed messages.
Intermediate Processing Statuses of Asynchronous Messages
|
Status |
Meaning |
|
|
Message has been released for processing. This status indicates the inbound message, which is the original version of a message. |
|
|
Receiver identification is complete. Exactly one receiver was identified and the message was scheduled again for further processing. |
|
|
The message is in retry mode. This means that there was an automatic restart following errors in the HTTP connection. |
|
|
The message has been scheduled again. This is the status of the message when you restart a particular message version manually. |
|
|
The message contains errors, was changed manually and saved. |
|
|
The acknowledgment message was stopped. |
|
|
The message was sent to the Process Engine for further processing. |
|
|
The message version was merely generated by logging and does not a have a particular status. |
The following statuses display the contents of acknowledgments of synchronously processed messages in the Acknowledgment Status column.
Statuses for Acknowledgments of Asynchronous Messages
|
Status |
Meaning |
|
|
No acknowledgment message has arrived yet. |
|
|
The acknowledgment message does not contain any errors. Therefore, the message was received from the receiver without any errors, or it was processed by the application correctly, or both. |
|
|
The acknowledgment message contains a system or application error. This means that message processing was not successful. |
|
|
More than one receiver was identified during logical routing so the acknowledgment message has to be branched. Message processing is complete for this acknowledgment message. The two new acknowledgment messages produced following branching are processed further, however. |
|
|
The corresponding message was acknowledged and can therefore be deleted. |
|
|
The acknowledgment message cannot be sent. |
