You have an Asynchronous scenario with Quality of Service Exactly Once in Order. One of the messages in the sequence fail, the Quality of Service of the affected message changes to Best Effort and the status to Log Version.
The next messages in the sequence get stuck, and upon trying to cancel the message with status Log Version, it fails with Synchronous message can't be failed.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1
- SAP NetWeaver 7.3
- SAP enhancement package 1 for SAP NetWeaver 7.3
- SAP NetWeaver 7.4
- SAP NetWeaver 7.5
Log Version, Synchronous message can't be failed., async-sync, BE, EOIO, cancel, asynchronous-synchronous, synchronous message can't be failed, PI, PO, Process Orchestration, Process Integration, AEX , KBA , BC-XI-CON-MSG , Messaging System , Problem
About this pageThis 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.