Page tree
Skip to end of metadata
Go to start of metadata


Purpose

The purpose of this page is to provide details on how to investigate the message status of messages within your Process Integration (PI) system. 

Overview

We will look at how report RSXMB_SHOW_STATUS is run, and how to determine what each message status means.  This wiki looks at message status in the Integration Engine, but not in the Adapter Framework.

Use of report RSXMB_SHOW_STATUS in Message Archiving  

In PI, messages can only be archived and deleted when they have a final status.  It is undesirable to have a large number of messages in a non-final status as it can lead to problems, e.g. rapid growth of database tables, slow start-up of systems etc.  Both the message status and adapter status of message needs to be final.  Messages with a non-final status need to be identified so that they can be fixed and processed accordingly, or cancelled.  Once messages have a final status they can then be archived and deleted. The report RSXMB_SHOW_STATUS can be run in transaction SE38 in order to determine what the status is of each message in the system.

To run the report, go to transaction SE38, enter the report RSXMB_SHOW_STATUS and select the Execute button.  Select "Current Container" for the current container table.  If the Switch Procedure is activated, then you can check the status for either of the containers.  Select the container for which you would like to view the status of messages.  Ensure that the checkbox "Check Message Status" is selected and hit the Execute button.

An overview will be displayed with the number of messages in each message status.  If you selected "Check Adapter Status", the adapter status will also be displayed.

Determining what each message status means 

Next we can determine the meaning behind the status of a message by checking a table in transaction SE16.  To do this go to transaction SE16, enter the table name SXMSMSTATT and hit enter, or select "Display Contents".  Select your preferred language and then select the Execute button.

 A list of the various statuses of the messages will be displayed in the column MSGSTATE, with the meaning of each one in the column MSGTXT.

 

How to proceed after Determining the Status of Messages 

You can now look at report RSXMB_SHOW_STATUS, understand the status of the messages in your system, and decide on the next steps for messages with a non-final status.

For example, if there are messages with status 012 (Recorded for Outbound Processing) or status 014 (System Error - Manual Restart Possible), you will need to either fix them and resend the messages, or cancel the messages manually and then archive and delete them. If there are message in status 003, these have the status "Processed Successfully", so they will be archived and deleted according to the configuration of your Archiving and Deletion procedure. 

Related Content

Related Documents

Archiving and Deletion in PI 

Processing Status

Related Notes 

SAP Note 944727 Status overview of XI messages

SAP Note 872388 Troubleshooting Archiving and Deletion in PI