
You can use this report, RSXMB_SWITCH_DEL_OLD_ENTRIES to logically delete PI messages or physically delete messages from the database beforehand.

Prerequisites
To execute this report, your user must be assigned the following authorization:
Object: S_XMB_AUTH
SXMBAREA: MESSAGE
ACTVT: 65
The role SAP_XI_ADMINISTRATOR_ABAP contains this authorization by default.
Furthermore, the report RSXMB_TABLE_SWITCH cannot be executed at the same time.
Execution
The interface of the report consists of the following blocks: Execution Time of Message, Delete Messages Logically, Delete Messages from the Database, Table-Container, and the input field Number of Lines per Loop
- Execution Time of Message Block
- Enter the period for which you want to edit messages. Times are entered in the time zone of the current user.
- Delete Messages Logically Block
- Select this option to flag messages as logically deleted. Logically deleted messages are no longer visible for the PI runtime and are no longer displayed in the monitor, but they are kept in the database until they are physically deleted.
- Delete Messages from the Database Block
- In this section you specify which messages are to be physically deleted from the database:
- Logically deleted messages:
- Messages that have been logically deleted using the standard delete report RSXMB_DELETE_MESSAGES or the report RSXMB_SWITCH_DEL_OLD_ENTRIES (see previous block).
- Messages that have already been copied:
- Messages that have been copied from the inactive container to the active container by a previous run of the report RSXMB_TABLE_SWITCH.
- Logically deleted messages:
- In this section you specify which messages are to be physically deleted from the database:
- Table Container Block
- Here you decide whether the actions that have been defined are to be executed on the active container or the inactive container.
- Input field Number of Lines per Loop
- You use this input field to define the number of messages that are to be handled at the same time. The default setting is 1000 messages per loop pass.
Result
The number of messages that have been edited is updated continually and output at the end of the execution:
- In the status line of the GUI (if the report is executed in a dialog)
- In the job log (if the report was scheduled as a background job)
The output is updated every 3 minutes.



