Error receiver determination

Hi,
i have a problem whith the receiver determination. The receiver determination fails because the Sender Service is used in upper case by the XI. What i can't explain is, that the business system is written in lower case in the SLD and when this system is used as a receiver service it is in lower case. It only fails when it is used as a sender service.
Horrable to find the reason.
So i think the problem should be in the administration of the sld. I checked several points in the content maintenace but can't find the solution.
Another problem is to set the hostname in the sld with networkdomain. The SLD captures all letters after the first point. Also i am looking for the point of administration to change this.

Hi Lars,
If you have given the name of Business System in Upper /Lower case it should appear in configuration in same way.If you use a BS like sender / receiver it should appears to you as you define in SLD.
I guess there is an another problem check it out that or give that error description so that it is easy to give the better ideas
Cheers
Tiger Woods

Similar Messages

IDOC error "receiver determination" while sending from R3 to XI

Hi all,
I'm trying to send an IDOC from R3 to BW thro' XI.
I created 2 business system for R3 & BW.
I created communication channel for receiving BW with IDOC adapter.
I created the receiver determination, interface determination & receiver agreement.
I also used IDX1,IDX2 to configure the port to load to IDOC.
When I send IDOC from R/3, It gets received in XI with the error message
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
It didn't select the receiver.
Am I missing anything? Can anyone help me with this.
The same problem exists even I tried to get IDOC into a file in XI.
I appreciate all your help.
thanks
felix.

Hello Ujjwal,
Receiver is already defined in "Receiver Determination".
Even I refreshed CPA Chache many times but getting same 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="">
<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>
Thanks.
RP

Receiver Determination Not found Internal Error...Please help me

Hi Gurus..
I have done a file to File scenario and when i test my scenario i am getting this error
Receiver Determination
Internal Error
HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://sapserver:8001/sap/xi/simulation?sap-client= User: PIDIRUSER
So please please help to solve this problem.

Hello,
Seems that you should configure the RFC Destinations and also
maintain the correct password, which should be the SAME, for all
the service users.
Refer to note below according to your system version:
PI 7.1:
#999962 - PI 7.10: Change passwords of PI service users
XI 7.0
#936093 - XI 7.0: Changing the passwords of XI service users
XI 3.0
#721548 - XI 3.0: Changing the passwords of the XI service users
Regards,
Caio Cagnani

IDoc TO File: Receiver Determination did not find any receivers at all

Hi,
We have IDoc to file scenario, where based on attributes present in IDoc we have configured different receivers.
Everything was working fine and files were getting created based on the receiver determination criteria.
But there is one change done in custom IDoc to re position the attributes.
Idoc before changes was having NAME1 and NAME2 above KATR6 and KATR7 and after change it looks like below:
So there is no change in segment and no change in mapping but the attributes KATR6 and KATR7 are used to determine the receiver.
Cache refresh is done for both ESR and ID. I have re - entered the receiver determination criteria just to ensure that change should reflect.
But still when I am triggering outbound IDoc from ECC to PI, the transaction is getting errored out with below error:
"ErrText": "Processing error = Receiver Determination did not find any receivers at all",
Can any one providee some idea what could be the reason and what is the right approach to resolve this issue.
Thanks,
Vertika

Hi Krupa,
I have marked your answer as helpful answer and delete of metadata wasn't required.
Reload works . But thanks for your suggestion.
Thanks,
Vertika

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.

Error in Receiver Determination

Hi,
I am getting this error in the intergration engine, please help.
<?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: Exception CX_SWF_RLS_RULE 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: Exception CX_SWF_RLS_RULE occurred (program: CL_SWF_RLS_CONDITION==========CP, include: CL_SWF_RLS_CONDITION==========CM00Q, line: 160). Problem evaluating a condition: Exception CX_SWF_RLS_RULE occurred (program: CL_SWF_RLS_CONDITION==========CP, include: CL_SWF_RLS_CONDITION==========CM00Q, line: 160). Exception CX_SWF_RLS_RULE occurred (program: CL_SWF_RLS_CONDITION==========CP, include: CL_SWF_RLS_CONDITION==========CM00Q, line: 160). Exception CX_SWF_RLS_OPERAND_MISSING occurred (program: CL_SWF_RLS_COMPARISON=========CP, include: CL_SWF_RLS_COMPARISON=========CM002, line: 63). Exception CX_SWF_RLS_OPERAND_MISSING occurred (program: SAPMSSY1, include: , line: 0). Exception CX_SWF_EXP_EVALUATE occurred (program: CL_SWF_EXP_EXPRESSION=========CP, include: CL_SWF_EXP_EXPRESSION=========CM027, line: 38). Exception CX_SWF_EXP_EXPRESSION occurred (program: CL_SWF_EXP_EXPRESSION=========CP, include: CL_SWF_EXP_EXPRESSION=========CM01Z, line: 520). Exception CX_SWF_EXP_EXPRESSION occurred (program: CL_SAI_SWF_RULE_ENGINE========CP, include: CL_SAI_SWF_RULE_ENGINE========CM00S, line: 42). Problem when processing the XPath expression /MBGMCR02/IDOC/E1BP2017_GM_ITEM_CREATE/[normalize-space(STGE_LOC)]</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Dear Ravi Kanth,
As for as my knowledge its shows the Exception: Operand Missing CX_SWF_RLS_OPERAND_MISSING occurred,
Plz check in your condition in detemining Receivers used proper operands.
Best Regards
Praveen

Error in determining receiver

Hi Experts,
I am facing an error in one of the file to Proxy scenario. It's giving the following error.
SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML Document 411 Error when parsing receiver listLength of XML Document 411 An error occurred when deserializing in the simple transformation program SXI_PARSE_RECEIVERS Data loss occurred when converting ExceptionMessage: LookupValueNotFound: SourceContext: http://sap.com/xi/XI SourceAgency: SenderBusinessService SourceScheme: Payments TargetContext: http://sap.com/xi/XI TargetAgency: ReceiverBusinessSystem TargetScheme: ReceiverCheck KeyValue: BusService</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The same scenario is working fine in production but in quality,its giving teh above error. We have used the value mapping. I have checked each and everything. Every thing is matching with teh production. The XSLT mapping program is working well in production but in quality same program is not working. I have also checked the extended receiver configuration setting. Everything is same as in production.
Please help me out. I would be greatful to every one.
Thanks
Veeru

HI,
Error clerly says that there is error in value mapping ..
Check the target values exist for the source scheme and agency..
Check the cache is updated in RWB..
HTH
Rajesh

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

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.

Intermittent JDBC error in Enhanced Receiver Determination

Hi,
I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
The database is DB2 on i5/os 6.1
Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
But the same message with same values is successfull earlier.
This is not a design problem; the interface is working well 95% of the time.
I found some JDBC error in NWA java logs:
Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
Thrown:
com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
Any idea? Can high volume cause the JDBC Receiver to fail?
Martin

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

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

Reg: Error at Receiver determination

hi friends
i have designed a scenario for JDBC to RFC and while testing that scenario at configuration part i found the error that "receiver determination is not found" i also tested with file to file scenario and found the same error . can anyone suggest how to overcome this error and what might be the error.
with regards
sharmista

Hi Dadapure sharmishta,
Have you provided any conditions in the receiver determination? In that case make it sure that the condition is getting satisfied. Also check if all the objects are activated. Check the sxi_cache for cache related issues.
Thanks and Regards,
Sanjeev.

Error receiver determination

Similar Messages

Maybe you are looking for