SAP Knowledge Base Article - Preview

3477965 - Handling XI messages in Scheduled/Error status

Symptom

XI tables like SXMSCLUR and SXMSCLUP are growing in size. In t-code SE38, run report RSXMB_SHOW_STATUS, the output shows a number of messages in non-final status like Scheduled/Error. Only messages in a final status can be deleted / archived. Asynchronous messages with errors have to be cancelled first. After that by default these cancelled messages (asynchronous only) have to be archived and will be deleted! 


Read more...

Environment

  • SAP Process Integration
  • Integration Engine

Product

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP S/4HANA 1610 ; SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023 ; SAP S/4HANA 2025 ; SAP S/4HANA, on-premise edition 1511

Keywords

Archiving, Deletion, SXMSPMAST, SXMSPMAST2, SXMSCLUR, Scheduled, Error, XI Message status. , KBA , BC-XI-IS-PER , Persistence Layer (Archiving, Deletion, PCI) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.