XI/PI: Dealing with Errors on the Outbound side

December 9th, 2007 Riyaz
Tiny link: (useful for email) http://www.riyaz.net/?p=9
Add comments
Printer Friendly Version Printer Friendly Version
 

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 - SXI_MONITOR/SXMB_MONI).

image

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 Port>/sap/xi/engine?type=entry

image

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

image

Send the message using Send Message button.

Step 2: Change the status of failed message

Call the transaction SWWL.

image

Delete appropriate work items.

image

Check that the messages are complete in SXI_MONITOR/SXMB_MONI.

image

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.