Message monitoring in the IE

Use transaction SXMB_MONI to monitor the messages.

Monitor for Processed XML Messages

Transaction code SXMB_MONI. Note the transaction SXI_MONITOR directly launches the “Monitor for Processed XML messages” . Use this function to determine all XML messages processed by the IE according to the following selection criteria:

Date Sent or Date Executed or both
Sender/Receiver Definition
Logical pipeline ID
Technical inbound channel/technical outbound channel
Message ID
Error Code
Client/User

By selecting a message status or condition or both you can further restrict the selection.

In each case the system displays a list of all XML messages, sorted according to the time and date they were processed, that satisfies the given selection criteria. From the list you can directly display the individual XML messages and go to their data.

The monitor for processed XML Messages provides a selection screen to specify attributes of the messages to be monitored.

Messages can be selected by execution status and by execution date. Furthermore it is possible to select messages using the SOAP header information like sender service, sender interface, etc.

Apart from these standard selection criteria the image below shows the advanced selection criteria:

The message ID for example can be used as selection criteria when the PI message to a received IDoc in R/3 needs to be found.

After you have finished the selection of messages a list of corresponding messages will be shown:

This list can be ordered by each column. It shows the status of the message execution in the integration engine in the first column.

The following status type exists:

In case of messages in an error status that allows a manual restart these messages either need to be restarted after the error was corrected or they need to be canceled in case the error cannot be connected. This is usually the case when the mapping fails because of missing information in the source message. In order to restart or cancel messages these messages need to be marked and the corresponding button needs to be clicked:

To get to the details of a message the corresponding line in the overview needs to be double clicked

On the left side you can see the different execution steps a message had passed. You can use a split view to view and compare the documents shown on the left side. For checking the execution of the mapping you can open the original payload in the upper window and the payload after the mapping step in the lower window

Monitor for archived XML messages

The monitor for archived XML messages provides very simple selection options. You can either select the archive run or the message ID

In case the archive run was selected a list of messages contained in that run is shown

A double click on a line leads to the same detail view as for the not yet archived messages. The selection by message ID directly leads to the detail view.

Link between IDoc and PI message

Link IDoc from R/3 to PI

Transaction IDX5 can be used to find the corresponding message in PI.

Just fill in the same IDoc number as the IDoc has in R/3:

From the result list a double click on one of the lines leads to the XML message monitoring as described before.

Link IDoc from PI to R/3

For example in the R/3 IDoc monitoring (WE02, WE05 or WE09) you have an IDoc that you want to trace back in PI. In order to get the PI message ID you have to take a look at the IDoc control record. In the field EDI archive key you will find the PI message ID: