You are on page 1of 6

Monitoring of XML Message Queues in R/3

1. Business Case

The information is a vital thing for any organization to make the strategic decisions. For these, information availability at
right time and right place is essential. This achieved through connecting SAP R/3 system and legacy system with the help
of XI (Now referred as PI-Process Integration). PI processes the data in XML format only. Also we can monitor the messages
sent to PI in R/3 system using T-Code ‘SXMB_MONI’. This article gives insight into how we can monitor XML messages in
R/3 system.

2. XML Messages in R/3 system

It is assumed that some messages are sent to the PI box from R/3 system and these messages are there in the message
queue also the outbound message interface is asynchronous.

Step 1: Run t-code: SXMB_MONI

Run t-code ‘SXMB_MONI’ in the R/3 system, which sends data to PI to get the following screen.

Step 2: After executing the above screen as shown above, we arrive at the

Monitoring screen for XML messages to be sent to PI. The message with ‘Green’ colored flag shows the messages are in
the queue and are thus scheduled for further processing. Also you can ‘Refresh’ or ‘Restart’ messages as shown in Red

Step 3: If we scroll to the right for a row, then we find the Queue ID as shown below.
Step 4: Click on the Queue ID to take you to following screen.

Step 5: Again drill down to Queue Name – XBTS0005 to take you to following screen .Our main objective is to unlock the
queue for the XML messages.

Here, click on the Unlock Button (RED Square) in the above picture to free the XML message stuck up in the queue.
Step 6: Now you can see the change in the status of the XML messages again in the


It’s changed to Checkered Flag.

3. Summary

Thus we can mo monitor XML messages in XI and R/3 as well with the help of transaction SXMB_MONI. The XML messages
stuck up in the queue are freed by unlocking queues in R/3 with the help of above transaction so that it reaches XI.

This functionality gives better Message Monitoring and Controlling.

Note: The GUI and Queue Names may change as per XI and R/3 versions.

Browse: Home › SAP › XI/PI: Dealing with Errors on the Outbound side

XI/PI: Dealing with Errors on the Outbound side

By Riyaz / 10 years ago — SAP

Sometimes the link between SAP XI and the target system (say ERP) goes down and messages fail on the
outbound side. It may not be possible to restart them from using RWB or the transactions like
SXI_MONITOR/SXMB_MONI. This article explains how to deal with such messages.

Generally, messages are picked up and sent via SAP XI when the link returns. However, in some scenarios, it
may be possible that SAP XI server could not finish conversation with ERP. Main status of messages is
“Processed successfully” – but there is an error in the outbound side as shown below. (Transactions –
These messages do not get picked up automatically – and it is not possible restart them from using RWB or the
transactions like SXI_MONITOR/SXMB_MONI.

Such messages could be processed in the following way:

 Send data directly to Integration Engine

 Change the status of failed message

This example shows how to solve the problem – two error messages are shown and one of them is solved here.

Step 1: Send data directly to Integration Engine

Go to Component Monitoring in SAP XI Runtime Workbench. Click on the Test Message tab for the Adapter
Engine. Specify the URL of SAP XI Integration engine to send the message to e.g. http://<XIServer>:<J2EE

Specify the header Information. Copy payload of the message using SXI_MONITOR/SXMB_MONI and paste
it into Payload area in RWB.
Send the message using Send Message button.

Step 2: Change the status of failed message

Call the transaction SWWL.

Delete appropriate work items.

Check that the messages are complete in SXI_MONITOR/SXMB_MONI.

Another simpler way to accomplish this is to use transaction SXMB_MONI_BPE . Select Continue Process
Following Error under Business Process Engine -> Monitoring and Execute (F8). Update the selection criteria
as required and Execute (F8). Choose the appropriate line item and click on Restart workflow button.

In these ways we can reprocess the messages failed on the outbound side. If the messages do not participate in
BPM process, then they can still be traced via outbound queues or SM58 logs and restarted.