Solution : https://service.sap.com/sap/support/notes/885879 (SAP Service marketplace login required)
Summary :
In SAP XI 3.0 Adapter Engine, EOIO messages stuck in HOLD due to lack of predecessor in the sequence can pose a challenge. Typically, the stuck message awaits a predecessor to reach a final state (DLVD or FAIL). However, a precedent needs considering when the first EOIO message, without prior messages, is still manually non-retryable in Message Display Tool due to automatic retries exceeding, leading to NLVD status. To address such scenarios, patches are now available: patch 9 for SP13 and patch 4 for SP14 in ADAPTERFRAMEWORK CORE 3.0. These allow administrators to restart these EOIO messages, ensuring the smooth flow of message sequences.
Key words :
sp-stacks -> sap netweaver'04 -> sap stack documentation, terms sap xi adapter engine, sap exchange infrastructure xi 3, netweaver 04 support package stackguide, detailed message status descriptions, direct predecessor message beeing, sap service marketplaceunder, xi adapterframework core 3, manual admin action, message display tool
Related Notes :
| 816022 | FAQ: XI/PI 3.0/7.0/7.1 J2EE Adapter Engine/Messaging System |
| 813993 | FAQ: Message status in the adapter framework |