SAP Knowledge Base Article - Preview

2872892 - Payload is modified after MappingException which causes Receiver Determination error after re-processing


You have an Integrated Configuration (ICO) with EO Quality of Service, several receivers and multi-mappings. Under Advanced Settings tab, you use scenario-specific configuration for staging as below:

  • Message Preparation (step BI) => Store on error  (BI=1)
  • Inbound XML Validation (step VI) => None
  • Receiver Determination (step MS) => None
  • Mapping (step AM) => Store (AM=3)
  • Outbund XML validation (step VO) => None


When some MappingException occurs, the following tags will be added in the stored message payload:

<?xml version="1.0"?>
<sxi:Messages xmlns:sxi="">
     ... XML-payload 

When the error message is retried, the message processing fails with a different error:

Transmitting the message to endpoint using connection AFW failed, due to:
Receiver Determination did not find any receivers at all

You would like to know why the stored payload is modified and how to avoid Receiver Determination error when the message is retried.



  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5


SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.3


MappingException, Receiver Determination, multi-mappings, STORE_ON_ERROR, Store on error, BI, AM, MS, staging,, split, Process Integration 7.30, PI 7.30, Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, AEX , KBA , BC-XI-IBC-MAP , Mapping , Problem

About this page

This 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.