Webservices receiver determination error

Hi...
i am doing webservices to file scenario. In that i have done everything fine. But i am getting the error category as
RCVR_DETERMINATION.
I have checked in Tools------>Test Configuration.
In that it is showing Interface mapping problem.It is displayinf as
Runtime error
Interface mapping Object ID 7C4A2690D561349FB04484680A71CBE3 Software Component F6D2A9E0E2B811D7C59AECB40A1145A5 does not exist in runtime cache
Please kindly help in this issue

testing Config in ID but no Interface mapping found!
Interface mapping Object does not exist in runtime cache
What is Cache refreshing in XI ? Why and when we will do that ?

Similar Messages

Q? Receiver determination error ????

Hi all.
I wana transfer from R3 IDOC to XML with FTP service.
Although I think configuration completely was finished, happens error.
How can i correct?
It's results from test configuration.
    Receiver Determination <Not found>
       Internal Error
       HTTP connection to ABAP Runtime failed.
       Error: 403 Forbidden
       URL: http://R3:8000/sap/xi/simulation?sap-client=
       User: XIDIRUSER Check
=======================================================
Scenario : R3 IDOC -> FTP XML (import Ext Definition DTD)
1) create Business Service System     : R3, FTP
2) create Message Interface about FTP : MI_FTP_in
3) create Interface Mapping R3 & FTP : IM_R3_to_FTP
4) import business system about FTP server : FTP
5) create Receiver Determination : |R3|IDOC_inf
     sender : R3
           - interface : IDOC interface
     configured Receivers
           - Service   : FTP
           - Receiver : FTP
           - interface : MI_FTP_in
           - Mapping   : IM_R3_to_FTP
           - Receiver Agreement: FTP_file_adapter
6) create Interface Determination: |R3|IDOC_inf||FTP
     Sender   : R3
           - interface : IDOC interface
     receiver : FTP
     Configured Inbound Interface
           - Inbound interface : MI_FTP_in
           - interface Mapping : IM_R3_to_FTP
7) create Receiver Agreement : |R3|IDOC_inf|MI_FTP_in
     Sender   : R3
     Receiver : FTP
           - interface : MI_FTP_in
           - Receiver Channel : FTP_File_Adapter
========================================================

Hi,
Please can you check you Cache is updated or not.If cache is succesfull then check the Port & RFC Destination and Partner profiles R/3 side and XI side.
R u testing this scenario using WE19.
If using we 19 then check the your sender information and receiver information (I mean to say Port,Parner...with outbound parameters )
Regards,
Venu.

Receiver Determination error - IDOC TO FILE

Hi ,
    Scenario : IDOC TO File
     Error generated while iam doing this scenario. Please help me.
      <?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</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>
Regards,
Venubabu.

Hi
Check for sender details . Sender interface must be the IDOC.
Open SXMB_MONI and check your msg fro the sender system details. They match exactly the details in Receiver Determination.
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong

Receiver Determination error in Xpath

In   receiver determination step, I am specifying two condition check.
The problem is that XI server is checking the second condition ahead of the first condition.
Eg:
I have a structure like Record in the input file:
Record:
   Field1
   Field2
   Field3
In specifying condition, I have a condition like this:
If   field1 = XY AND field2 = AB
Then   (do..)
But the XI server is reading field2 first and not field1 . Why is this so?
Thanks a lot.
Shaily

Check the "AND" condition properly make sure it is not a "OR" condition in xPath.
Refresh the cache by tcode sxi_cache and try again.

IDoc2FIle:Receiver Determination Error

Hi all,
I have done idoc2 file scenario and i got the status as receiver could not be determined in SXMB_MONI.
Please Can anyone solve this issue?
Thanks,
Radhika

Hi,
I think you are not configured the receiver determination properly,
Check you Xi Configuration in ID with the help of this Blog
Test Your XI Configuration With The New Test Tool
Regards
Seshagiri

RFC to WebService Receiver Determination Problem

Hi,
I am doing RFC to WebService with the help of this weblog
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2 In Interface Determination - when picking Inbound interface is coming as No objects found.
How to resolve it?
regards,
Ansar.

Ansar,
In RFC to Web service the inbound interface should be the WSDL.
Did you import WSDL under 'External Definations'.
After importing you need to create a inbound message interface of the Message within the WSDL that you need to use.
Regards,
Ashish
Message was edited by:
Ashish Goyal

Receiver determination error

we have sap proxy -> pi scenario.
the interface was working fine, recently we had a client refresh ( test systems) and now when the message reaches xi it reaches with sernder service name as 'ABTCLNT100' which is logical dest name , but the business system in sld is defined as 'ABT100' preveiously before the refresh it was coming as ABT100 but now it comes as ABTCLNT100 which fails the message once it reaches XI. Any ideas where can I look in backend system ?

In TA SCC4, for the specific client you can change the logical system name.

Receiver Determination Internal error

When I try to test a Configuration that I just created, I get the following Receiver Determination error:
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://rommi:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER
Can someody please tell me what the issue is here and how to resolve it?
I have currently two or three posts running here concurrently which may be reated to the same problems; it is a new system install, and there are clearly a few niggling issues still with it.
Kind Regards,
Tony.

Did you check this blog
<a href="/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi Errors</a>

ABAP PROXY CLIENT - NO RECEIVER DETERMINATION

Hi,
I am working in the following senario: ABAP PROXY -> XI -> RFC
I also created Receiver Agreement, Interface Determination and Receiver Determination. All the 3 are associated to a party.
When I execute the abap program the following message appears:
<?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>
I appreciate all of inputs

Hi,
<i><SAP:Stack>No receiver could be determined</SAP:Stack></i> is the problem when the receiver Determinaiton is not mentioned properly.
By the way u have mentioned that all the three are associated to a party. So when u were defining Business system (For the system from whihc proxies are being sent), directly under <b>"Service without Party"</b> or under <b>"party"</b>.
If u ahve mentioned your System from whihc proxies are being triggered in "Service without Party", then that should have been causing receiver determination errors.

Error in Extended Receiver Determination

Hello Experts,
We are working on a scenario where, we are using Extended Receiver Determination.
In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
Also, we have a default receiver in mapping.
We are using: SAP PO 7.4 SP 7
We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
Error:
<s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
          <context>XIAdapter</context>
          <code>ADAPTER.JAVA_EXCEPTION</code>
          <text><![CDATA[
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
Kindly help.

hi,
you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
please find the link which deals with how to impliment lookup for file adapter.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
regards,
navneet.

Error evaluation condition in receiver determination

Hi,
In XI 3.0 stack 11, for the incoming file, the receivers are determined based on the content of the input data.
In the receiver determination the conditions were given for each receiver and it was working fine.
Now, all of a sudden, its giving error as 'error in evaluating the condition in receiver determination' with some program name as CL_SAI_SWF_RULE_ENGINE (CX_RD_PLSRV).
Could any one help me resolving this issue? Let me know if you need any more details w.r.t the issue.
Thanks in advance!!
Regards,
Sasikumar

Hi,
I'm experiencing the same problem. See message below. Also running SP11. What might be wrong with the xpath expression? I have removed all namespaces from the xpath and the input xml message. Any suggestion is more than welcome!
Kind regards, Guy Crets
<?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="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 160)</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: The exception occurred (program: CL_SWF_RLS_CONDITION==========CP, include CL_SWF_RLS_CONDITION==========CM00Q, line: 160)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Alert to Error in Receiver determination mapping

Hi everyboy.
Im using a mapping to decide the receiver determination (ReceiverDetermination - http://sap.com/xi/XI/System).
I can´t configure an alert when the mapping fails.
How could I do that????
Thanks a lot

Hi Christian,
As per my understanding you are using extended receiver determination by creating an interface mapping in between your outbound interface and standard receiver interface of SAP BASIS.Do you mean to say that if source data doesnot fulfill the condition to determine any receiver.If so, then I believe in SXMB_MONI we can find the error as unable to determine receiver.Since it belongs to mapping so it will be executed in Integration engine.
create an alert category in ALRTCATDEF
Define Alert Rule in RWB -> Alert Configuration
Select the our own Alert Category
Click to Add Rule and activate the corresponding rule
Regards,
Nutan

Error in receiver determination - Client proxy to IDOC using PI-IS

Hi,
I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</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>
I am using the standard SAP message interface in the sproxy.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
Thanks,
Menaga

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
The above error occurs due to:
1) You have configured a wrong receiver service in the Receiver Determination
2) You have configured the correct receiver but the cache is not updated
So check if the receiver service exists and the cache is updated.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
be created without DT".
Check if you get any lead from this thread:
Failed to time to generate proxy - TRX SPROXY
Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
Regards,
Abhishek.

No receiver could be determined error in AAE - File Adapter

Dear Friends,
We have PI 7.1, EHP1.
We are doing migration of our existing configuration scenarios into AAE.
While do testing the interfaces after migration, we face one issue.
In a File to SOAP scenario (Async), once the file is polled from the source directory and failed with the error 'No Receiver Determination' in the sender channel, the source file will not be moved to the archive directory. (Processing Mode : Archive).
Due to this problem, the source file is keep on polling with the intervals specified in the channel and failed. We see this error in Sender Communication Channel.
But, If the receiver is determined, this problem will not come. File is picked up, moved to the archive directory and processed successfully.
Friends, can you clarify how to solve this issue? (We tried with Processing Mode as 'Delete' , in that case also file is not deleted when error 'No Receiver determination')
Thanking you,
Kind Regards,
Jegathees P.

Hello Friends,
Thanks for your reply. For the testing purpose, I removed the condition to determine receiver, to force the message fail. Purpose is to test how AAE behaves for different errors.
My doubt is, in the classical method, for the same error, the file will be moved to the archive directory and further polling will not happen, we know that. In this new method, why the system did not move the file to archive directory though the error comes.
Kind Regards,
Jegathees P.

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

Webservices receiver determination error

Similar Messages

Maybe you are looking for