Message Editor: Editor loads the wrong payload version
[abap] [barrett payload] [Engine] [integration.] [Message] [monitoring] [os.nb.payload] [payload] [payload size] [runtime] [RWB] [Workbench]
- Message Overview: redirect to Message Monitoring failsSymptom You click on one of the counters in the Message Overview, that shows the number of Messages of a certain scenario and in a certain status. A new window opens that...
- Different numbers in Message Overview and Message MonitoringSymptom Your system has several server nodes. The Message Overview shows a number of Messages that does not match the number of Messages shown in Message Monitoring or when directly checking the...
- Message Monitoring: Error displayed for some statusSymptom The user starts Message Monitoring for the Adapter Engine. In the filter, he selects a status that only exists for the Integration Engine (e.g. “Application Error”) and starts a search for...
- API for Gross update MessageSymptom Only updated fields information is distributed to the device in case of update message from middleware. Other terms SAP NetWeaver Mobile 7.10, Data Orchestration Engine (DOE), Gross message, DOE Connector, Mobile...
- Monitored Services do not appear in Monitoring Service/CCMSSymptom The Adapter Engine can report the backlog for XI Messages to the Java Monitoring service of the WebAS Java and from there to CCMS. The Monitoring is configured at Service level...
- Restricting the display in the RWB performance monitorSymptom You use the SAP NetWeaver Exchange Infrastructure and use performance monitoring in the Runtime Workbench. If you use a selection that leads to a very large result set, a memory bottleneck...
- Manual cancelling of Messages triggers AlertSymptom You have configured XI Alerts in Runtime Workbench for your scenarios. Manual cancelling of XI Messages of the Adapter Engine in Message Monitoring triggers Alerts. Other terms RWB, Runtime Workbench Reason...
Symptom
If you start the Message Editor for an XI message for which an application error has occurred in the target system, the system then loads an incorrect version of the payload. Instead of the original payload of the message, the system displays the returned application error in the editor window in the Message Editor.
Other terms
RWB, Runtime Workbench, Integration Engine, ABAP, message monitoring
Reason and Prerequisites
If an application error occurs, the payload is replaced with the application error in the last message version. The Message Editor loads this message version instead of the previous version that contains the actual payload.
Solution
The following and higher Support Packages enhance the editor with a selection box with which you can load any payload versions in the editor (if there are several versions of the message in the database):
XI 3.0 Support Package 25XI 7.0 Support Package 20XI 7.01 Support Package 05XI 7.02 Support Package 02PI 7.10 Support Package 09PI 7.11 Support Package 04PI 7.20 Support Package 01
In older Support Packages, we changed the behavior of the Message Editor so that it loads the previous message version by default. Therefore, the correct payload is loaded when you start the editor. Update the software components of the Adapter Engine to the patch levels specified in this SAP note under the section “SP Patch Level” or use higher versions.
Archives and the Support Package Stack Guide are available on SAP Service Marketplace as described in SAP Note 952402.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}