RCVR_DETERMINATION.NO_RECEIVER_CASE_BE

Hi,
I am trying to consume a web service (which published by a third party, out side of my network) through PI 7.11 . I have created the external definition via the web service WSDL then defined the Service Interfaces, Message Mappings and Operation Mapping in IR. Later i configured the scenario in ID and tested in Test Configuration in ID. It found correct receivers with the payload.
I also generated ABAP Proxy in ECC system and run test in SPROXY. It gave me "RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined" error message. I have run "http://<saphost>:<port>/CPACache/refresh?mode=full" many times but didnt help. I copied below TRACE message from SXMB_MONI.
I also noticed that there are two lines per test. One is sender and one is receiver but both Interfaces are same and outbound one.
What could be the problem?
KR,
Altug

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">User = XXXXXX</Trace>
<Trace level="1" type="T">Message ID = 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">system-ID = BPD</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = XXXXXX</Trace>
<Trace level="1" type="Timestamp">2010-06-09T06:04:21Z CET</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

<Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
</Trace>
<Trace level="1" type="T">An Exception has occured</Trace>
<Trace level="1" type="T">Error Text: No receiver could be determined</Trace>
<Trace level="1" type="T">SystemError message generated. Guid: 4C0C7AEFF2EC0079E10080000AA60016</Trace>
<Trace level="1" type="T">Error during execution of message : 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 4C0A5693C69C010DE10080000AA6001A</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

</SAP:Trace>

Similar Messages

WebService Call: RCVR_DETERMINATION: NO_RECEIVER_CASE_BE

Hello,
I want to call an external Web Service from my ABAP Code, but I get an error in transaction sxmb_moni:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have no idea, where this error message comes from... Have you any solution proposals?
Thank you

Hi Yu
for the error RCVR_DETERMINATION.NO_RECEIVER_CASE_BE error
look at these thrad discussed the same
Consume a Web Service: No receiver could be determined
Error in my HTTP > XI > RFC (BAPI) senario
Http to IDOC Error
Regards
Abhishek

Error:RCVR_DETERMINATION" NO_RECEIVER_CASE_BE

hi all,
In my soap-xi-rfc scenario this is the error i am getting in MONI when using .wsdl file from EP
<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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
but when i am testing the same data from HTTP client it is working fine.
I have deleted the receiver determination and interface determination and created again,but the error continues.
Also in MONI in the message list i can see the sender interface but i am not able to see the receiver system and interface
Can anyone help me out with this??
thanks and regards,
Nisheeta

Hi,
Check the trace in SXMB_MONI, and refresh cache.
Check you configred the determinations correctly or not,
check the receiver interfaces also in IR.
Please compare the entries in IB directory (receiver determination) with entries in Monitoring (SXMB_MONI): Service, Interface, Namespace
also see the below links
RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
Consume a Web Service: No receiver could be determined
Regards
Chilla
reward points if it is helpful..

RCVR_DETERMINATION.NO_RECEIVER_CASE_BE - encoded URL in WSDL

Hi
I have a SOAP to RFC scenario and generated the wsdl using PI 7.11 Integration Builder. The generated URL in the wsdl contains HTML encoded characters because the URL contains a URL e.g..
https://myhost/sap/xi/engine?type=entry&version=3.0&Sender.Service=BC_MY_SENDER&Interface=http%3A%2F%2Four_host%2Fsap%2Fabcd%5ESI_MY_PROCESS_OUTBOUND.
I have tried to use this URL in soapUI but it does not work and returns a message like the one in this thread's subject.
If you urldecode the url it works in soapUI. One of our clients who will use this web service to call us has to have the url encoded (with %) in it because of the url in a url. Problem is as soon as it hits PI, PI does not perform a urldecode and it fails.
Has anybody else encounter this problem?
Regards
Naas

Hi
If I use the suggested method I get this message:
Servlet com.sap.aii.adapter.soap.web.MessageServlet (Version $Id: //tc/xpi.adapters/NW711_05_REL/src/_soap_application_web_module/webm/api/com/sap/aii/adapter/soap/web/MessageServlet.java#6 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of $Proxy95
ModuleProcessorRemote not instantiated
I tried the following: (No party) where SI = Service Interface, BC = Buss. Comp and CC = Comm. Channel - all for the Sender.
http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:BC
http://myhost/XISOAPAdapter/MessageServlet?channel=:BC:CC
http://myhost/XISOAPAdapter/MessageServlet?channel=:SI:CC
http://myhost/XISOAPAdapter/MessageServlet?channel=:CC:BC
Then I tried the suggestion in point 1 of the note.
https://dpi.buw.bu.edu/XISOAPAdapter/MessageServlet?senderParty=&senderService=BC_TEST_SENDER&interface=SI_TEST_OUTBOUND&receiverParty=&receiverService=BC_TEST_RECEIVER&interfaceNamespace=http://myhost/sap/kcrm
What am I missing?
Naas

SAP GRC ERROR - NO_RECEIVER_CASE_BE

Hi All, I'm try implemented GRC and get this error (SXMB_MONI):
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
My receiver determination with the following values:
Service - GRC_NFE_CORE_70 (name of my BSystem)
Interface - SRVSC_nfeStatusServicoNF_SYNC_OB
Namespace - http://sap.com/xi/NFE/005a
Configured receivers
Service - SEFAZ_GO_HOMOLOG (name of my BService created)
Condition - (/ p1: nfeStatusServicoNF/p1: CUF = GO)
This error changes when configured to remove the condition receivers, this condition: Condition = (/ p1: nfeStatusServicoNF/p1: CUF = GO)
New Error:
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: unable to create a socket</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
Anybody help-me??
Thanks.
HMattos.

Venkat,
I make cache refresh full using the user PIDIRUSER, see result bellow:
CPA cache refresh (mode=full) successfully executed in 7077 milliseconds.
But the error persist..
Other sugestion?
Regards,
HMattos.

NO_RECEIVER_CASE_BE - No receiver could be determined error

Hi Experts,
Scenario: SOAP to JDBC BPM Scenario
Error: When I tried to execute the scenario, I am getting the below error. The interface mentioned in Integration Directory and SXMB_MONI are different. Where to do the correction?
Note :Refreshed the cache in SXI_CACHE and Administrator screen. I couldn't see the Integration Process in SXI_CACHE
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Regards
Sara

What was the resolution?

Unable to see ECC proxies in PI Service Registry

I am trying to consume ECC proxies in PI service registry but I cannot see any ECC backend proxies in PI. I have gone through several blogs, configuration guides and sdn forums to get this to work but could not. In ECC, if I use SOAMANAGER, I can see my proxy and web service in web service administration but I cannot see it in PI. I have done the following:
- System Global Settings
In Service Registry, I have defined proxy class as CO_SERVICES_REGISTRY_FLAT_SI, set to primary, logical port defined as default_port.
- On ECC WS administration, setup end points and binding.
- setup ID configuration objects for this scenario (WS to Proxy -> Proxy to WS Synchronous)
- Proxy creation in ECC also completed.
- Also checked in WSPARAM settings, same as WS Admin Service Registry.
- WSPUBLISH - getting error in ECC: RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No receiver could be determined, Error retrieving Services Registry (SR) version information, Error retreiving physical system from Services Registry, Exception raised during physical system publication. Code.
and in PI getting error: INTERNAL.PROXY_NOT_ALLOWED_ON_IS Proxy calls are not permitted on sender or receiver side on the IS (client), Error retrieving Services Registry (SR) version information, No Publication possible from Integration Server(IS).
- Created type H RFC destinations in both ECC and PI.
Since WSADMIN, WSCONFIG and LPCONFIG have been combined into SOAMANAGER, are there any other settings I have to do as far as ECC communicating with PI Web Service and PI consuming ECC proxies? Did I miss anything here?
Most of the PI documenation, blogs and guides are outdated for previous versions. We are using SAP EHP 1 for SAP NetWeaver 7.1.
Thank you!

Hi Viswa,
Try to recreate the EEWB project for this...
Assign business transaction and CUSTOMER_H and with ADD_NEW_FIELDS as the type of ehancement.
Shud solve ..
Siva

Receiver Determination Problem In Mail to File Scenario.

Hi All,
I am trying to do Mail to File Scenario. I defined two business systems, one s/w component in SLD and in IR I defined a DataType , MessageType and Two MessageInterfaces. In ID these are mail adapter settings I gave :-
Message Protocol :- POP3
Message Protocol :- XIPAYLOAD
MAIL ATTRIBUTES -- Enabled checkbox for "Use Mail Package"
 Content Encoding - "base64"
 Enabled checkbox for "Keep Attachments"
DEFAULT XI PARAMTERS --
 Default Interface Namespace -- http://mtf
 Default Interface Name -- mtf_mi1
And in Modules Tab I also defined the "PayloadSwapBean" module and swap.keyName and swap.keyValue.
Infact I followed all the steps specified in /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
But in SXMB_MONI this is the error I am getting :-
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please help me out.
Thanks All,
Madhu.

Hi,
Please verify letter by letter if you haven't make a typo here:
Default Interface Namespace -- http://mtf
Default Interface Name -- mtf_mi1
please also make a test of your scenario in integration directory
please also do not use best efort quality of service
/wg
Message was edited by:
 Wojciech Gasiorowski

Webservice to file (receiver determination problem)

Hi ...
I am doing webserive to file scenario in PI7.0 server. I have completed doing the scenario. But there is a problem in receiver side. In SXMB_MONI it is showing the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Could you please help me out in this.

hi,
When you have used the WSDL wizard in the Integration Directory and have clicked on "Propose URL" in the second screen, did you ever wonder, why the URL does not point to a sender SOAP adapter channel, it is the URL of the Integration Server instead?
When you want to use the inbound channel of the Integration Server, you have to use following URL for the web service client:
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
The namespace must be written with escaped characters. (%5E stands for "^")
Note: The WSDL wizard creates an address with the escape sequence & instead of &. Some SOAP clients (for example XPLSpy) do not automatically restore the character and you have to do this manually.
By default the SOAP call is treated as a synchronous call. If you want an asynchronous call, you have to add &QualityOfService=ExactlyOnce to the URL.
Additionally your web service client must provide the HTTP header parameter "SOAP action" = http://sap.com/xi/WebService/soap1.1
The Web Service Wizard of the Integration Repository creates a WSDL concerning this URL and this SOAP action automatically. Only for asynchronous calls you need to change the URL inside the WSDL file with an editor and add &QualityOfService=ExactlyOnce.
Advantage
When you send SOAP messages directly to the Integration Server, you reduce the message load on the adapter engine. This can improve the performance.
Restrictions
The SOAP inbound channel of the Integration Server does not support attachments. SOAP messages with content type "multipart" are rejected.
Hint
For testing purpose it is possible to add logon data directly to the URL. The parameters are the same as in the HTTP sender adapter: &sap-user=<username>&sap-password=<password>
/people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
regards
chandra

Error in Ws to File Scenario

Hi,
The Below error is displayed when executiong the proxy.
<?xml version="1.0" encoding="utf-8" ?>
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<SYSTEMFAULT href="#o239" />
</asx:values>
- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
- <cls:CX_AI_SYSTEM_FAULT id="o239">
- <CX_ROOT>
<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>97</PROGID>
<CONTID>3413</CONTID>
</INTERNAL_SOURCE_POS>
</CX_ROOT>
<CX_STATIC_CHECK />
- <CX_AI_SYSTEM_FAULT>
<CODECONTEXT />
<CODE>RCVR_DETERMINATION.NO_RECEIVER_CASE_BE</CODE>
<ERRORTEXT>No receiver could be determined</ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
</asx:heap>
</asx:abap>
I am using the Webservice URL:http://www.webservicex.net/CurrencyConvertor.asmx?wsdl.
Senderinterfacename:CurrencyConvertorSoap_out
SenderinterfacenameSpace:http://www.webserviceX.NET/
I am calling the above url (CurrencyConvertorSoap->http://www.webserviceX.NET/) by creating Proxy.
Up on executing the same ,I am Getting the above error as pasted.
Pl look in to it and let me know the solution.
Thanks,
Srinivasa

Hi Srini,
 Can you explain detail?
 How you used ws to file with proxy..
 I thing your creating outbound proxy.In that your calling the URL and passed some value and get the
 response back. You passed that response to XI.If that may right then there is no need for sender
 communication chennal and Sender Agreement.Create a Receiver Determination with your Business
 system Select your message interface.
Regards,
Prakasu

XI 3.0 SP14 Synchronous SOAP- XI- ABAP Proxy - fails with "System Error"

Hi All,
The synchronous response message fails at the stage "Receiver Identification".
It seems that the synchronous response XML has no "sender" attribute, so obviously the receiver determination fails.
In the message monitor I can see the correct payload coming from the ABAP proxy, so that part looks OK.
I have the same scenario working perfectly on another system landscape, so there might be a configuration side to it.
Thanks is advance,
Ofer
Message was edited by: Ofer Even-Tsur

Hi,
for the error information SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
looks like xi is not able to find a reciever of best case. Open up the scenario in COnfiguration, open up the modify(add spaces) and activate reciever determination / reciever communication channel.
cheers,
naveen

Call Inbound Proxy error

PI settings help
I am trying to transfer PR from ERP6.0 EHP4 to SRM7.0 using CPPR scenario.
I configured ERP/SRM and PI configuration in Integration directory.
But i get Reciever determination error in XML at ERP/SRM AND PI
RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
Error Text: No receiver could be determined
In SRM, Inbound Message(reciever) is green but Call Inbound Proxy is giving below error.
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing! <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
I tested configuration in Integration directory.
Sender aggreeemnt is green
Reciever determination is red and giving below error.
Internal Error : You do not have sufficient authorization for this operation.
I have done below setting in Integration directory.
Business system setting.
1.Selected Business System BC_MM_MXX_594
2.Create communication channel(Gen_Rec_xi) as Receiver
for above Business system BC_MM_MXX_594.
-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC MXX_Integration,
1.Selected Business System BC_SRM_SXX_300
2.Create communication channel(Gen_Rec_xi) as Receiver
for above Business system BC_SRM_SXX_300.
-Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC SXX_Integration.
-->>one doubt here? Should i have to create Comm channel for sender type also from ERP and SRM? pls confirm.
I created object in Integration directory as follows.
Create Object by selecting Business System BC_MM_MXX_594.
1)Selected Internal communication
2)Reciever Determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out
3)Specified Interface determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out BC_SRM_SXX_300.
4)Specified Reciever agreement BC_MM_MXX_594 BC_SRM_SXX_300 PurchaseRequestERPSourcingRequest_in(communication channel selected is Gen_Rec_xi)
5)Generated Objects and saved as CPPR_scenario.
6)Activated all objects created in CPPR_Scenario.
Pls suggest something wrong with Reciever determination?
How to find where the problem is located? at ERP or PI or SRM?.
Also onething i noted is Integrated configuration is empty in Integration directory.
Any configuration should be done for IOC.? pls confirm.
Regards
Chandra

Also i noticed below
In ERP xml ->Inbound message(SENDER).
Does this error indicate problem while sending from ERP to SRM or SRM to ERP.
because i can see sender service and interface is empty and SAP reciever is having ERP service.
however reciever does not fetched the corresponding(purchaseRequestxxxxxxx) interface names.
- <SAP:Sender>
<SAP:Service />
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>BC_MM_MXX_594</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/APPL">QueryCodeList</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/APPL">QueryCodeList</SAP:Interface>
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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Chandra

Calling XI's SOAP Adapter from Webdynpro for java

Hello every one,
I have implemented a webservice scenario which involves soap message exchange,,I have checked the configuration from configuration tool -- it seems fine there -- than we had a check run from XML spy, using the WSDL generated by XI,,, that went through as well,, but now when I am trying to call the webservice through webservice adaptive model in NWDS, it returns :

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
this is the response message generated and viewed in SXMB_MONI
Now I cannot understand why its prompting error from application and not XML Spy,,
I am using following url to send msg to XI's SOAP sender adapter:
http://pep:8000/sap/xi/engine?type=entry&version=3.0&Sender.Service=BS_PROTOTYPE_WS_OUT&Interface=urn%3Apso%3Aws%3Abank%5ECC_CHK_ACC_SENDER&sap-user=<myuser>&sap-password=<myPwd>&sap-client=001&sap-language=EN
any help would be highly appreciative..
thanks

Dear Nicholas,
When portal server is installed, it assigns a specific port for running the portal. Normally the port is 500XX when xx is your instance number. There seems to be some problem in your case.
Please carry out following steps to see/resolve the issue:
1. Open the visual administrator
2. Navigate to Dispatcher -> Services -> HTTP Provider
This HTTP Provider specifies the ports used by portal.
You change the ports to something like : (Port:80,Type:http)(Port:443,Type:ssl)
Save your settings and now open the browser and open the portal like http://<host>/irj/portal (because 80 is default port). If you specify some other port you need to enter like http://<host>:<port>/irj/portal
This should resolve your issue:
Enjoy
Best Regards,
Ravi

XI Receiver Adapter: No receiver could be determined

Hello guys,
I'm at the moment connecting Contract Accounts Receivable and Payable 6.00
http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm
My scenario has a XI Receiver Adapter. I have set up the receiver agreement, Interface Determination and Receiver Determination as it says in the link provided. I have succesfully tested the configuration with the TEST CONFIGURATION TOOL in ID.
But at the moment of testing a real message, I'm getting in the SXMB_MONI the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Does any one knows why if the configuration is correct (according to me and the test tool), I'm getting this error?
Thanks for your help.
Felipe

Hi guys,
I have resolved the issue. Aamir you were rigth, the problem was with the sender attributes.
What happened was that the sender Interface namespace was a differente one from the one in the configuration. In this link
http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm it said that the namespace had to be http://sap.com/FICA/Global, but it was using the namespace http://sap.com/xi/PI/FIN/Operational/Global, so I just need it to change.
Thanks guys for your support.
Felipe

BPM Sync/Async Problem

I am trying to setup the sync/Async bridge.Scenario is below.
Receive (Open Sync/Async Bridge) --> Send Async > Receive Async> Send (Close sync/Async)
I am doing exactly those steps which is provided in Pattern.
Following are in the interfaces.
Sync Interface to post message to BPM (OutBound)
(This interface is exposed as WebService)
Abstract Sync Interface used by BPM.
Async Abstract Interface for Request Message used by Container.
Async Abstract Interface for Response Message used by Container.
Async Inbound Interface to receive message sent by BPM in Async Send Process.
Async Outbound Interface to send message to BPM by Async Receive.
All the configuration Sender agreement/receieve agreement/interface determination/Receive Determination looks fine.
On posting soap data I get the following exception.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" 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:ApplicationFaultMessage namespace=""/>
 <SAP:Stack>No receiver could be determined</SAP:Stack>
 <SAP:Retry>N</SAP:Retry>
</SAP:Error>
Any pointers will be great help!
Thanks,
Samir

Hi Samir
As you are trying Sync/Async BPM scenario and having a webservice as your sender,go through this link as it is quite similar to your scenario--
https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
If you still face error then post it in forum.
Regards
Arpit Seth

RCVR_DETERMINATION.NO_RECEIVER_CASE_BE

Similar Messages

Maybe you are looking for