Solution : https://service.sap.com/sap/support/notes/813993 (SAP Service marketplace login required)
Summary :
This SAP Note details XML message status inquiries in the context of SAP XI 3.0, emphasizing distinctions between statuses in the Integration Engine (ABAP) and Adapter Engine (Java). It specifies the functionalities of different message statuses - whether they denote completion or require further action. Descriptions include whether messages can be restarted, deleted, or archived based on their status. Translations and equivalences in ABAP monitoring are clarified. The note explains changes in deletion and archiving permissions post-upgrade to XI 3.0 SP11 and outlines the visibility and functionalities of statuses in the message display tool (MDT), including manual adjustments and error handling strategies.
Key words :
adapter framework core patch 02, central/decentralized adapter engine, pck homepage -> message monitor, exact english-german translation, monitoring integration engine english, monitor adapter engine messages, monitoring adapter engine successful, monitoring integration engine successful, partner connectivity kit, higher version systems
Related Notes :
| 885880 | EOIO messages in status HOLD with duplicate sequence numbers |
| 885879 | EOIO message in HOLD without predecessor cannot be restarted |
| 821268 | XI 3.0 / PI 7.0 AF: Overview of available FAQ notes |
| 816022 | FAQ: XI/PI 3.0/7.0/7.1 J2EE Adapter Engine/Messaging System |
| 811864 | EOIO queue in the J2EE Adapter Engine is blocked |
| 807615 | Removing/archiving of non-expired messages |
| 791379 | XI Adapter service properties documentation |