Solution : https://service.sap.com/sap/support/notes/1106867 (SAP Service marketplace login required)
Summary :
After using transaction SMQ2 to delete a STOP entry in an XI queue, users may experience the queue status changing to SYSFAIL upon processing the next message, as detailed in this SAP Note. This status change is typically due to an error in the processing of a predecessor message, which disrupts the error handling in the application and affects subsequent messages. To resolve this, ensure the initial message processes successfully, then use SMQ2 to activate the queue from SYSFAIL status, referring to SAP Note 1579600 for further guidance on resolving the issue.
Key words :
error text refers, predecessor message caused, predecessor message, transaction smq2, stop entry, subsequently set, subsequent messages, correct serialization, eoio queue, subsequently changed
Related Notes :
| 1581151 | XI runtime: Selecting FEH EOIO message from queue |
| 1579600 | Determining the postprocessing order for XI messages |