SAP Knowledge Base Article - Preview

3100498 - PI Proxy messages are failing with error NO_RECEIVER_CASE_BE & No receiver could be determined

Symptom

You hava an ABAP Proxy (XI Adapter) interface but face following errors while processing XI messages.

<?xml version="1.0" encoding="UTF-8" standalone="true"?>
<!-- Inbound Message -->
<SAP:Error xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1/>
<SAP:P2/>
<SAP:P3/>
<SAP:P4/>
<SAP:AdditionalText/>
<SAP:Stack>No receiver could be determined </SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>


Read more...

Environment

  • SAP NetWeaver
  • SAP Process Integration

Product

SAP Process Integration all versions

Keywords

NO_RECEIVER_CASE_BE, No receiver could be determined, ABAP, proxy, XI, Message, SLD, RCVR_DETERMINATION, SLDCHECK, PI, PO, Integration, Process Integration, Process Orchestration , KBA , BC-XI-IS-DC , SXI_Cache / Abap Cache (Directory) , BC-XI-IS-IEN , Integration Engine , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.