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

Similar Messages

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.

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.

XPath Error in Receiver Determination

Hi All,
I hav an outbound message coming out of ERP (Non IDoc). I have to route the message based on the field DESTINATION in the message. The payload in the SXMB_MONI is as follows.
<?xml version="1.0" encoding="utf-8" ?>
<nr1:OLabelling_OB xmlns:nr1="http://cpe.com/cpe_ftp_wms/Labelling/OL">
<Label>
<DESTINATION>XXXX</DESTINATION>
<PRPRORD>0001005683</PRPRORD>
</Label>
</nr1:OLabelling_OB>
In the receiver determination, I hav chosen the XPath button and given the following value
/nr1:OLabelling_OB/Label/DESTINATION.
This doesn't work. i had also tried giving the namespace and the prefix as
nr1 http://cpe.com/cpe_ftp_wms/Labelling/OL. but that dint help either.
If i remove the condition, then it is working fine.
Any help in this regard?
Thnx in Advance.
Anil

I had activated and checked......it was not getting displayed.......
But i checked the xpath rules and used a work around solution for this. as per the xpath rules if i enter xpath as //DESTINATION, it picks up the DESTINATION field from anywhere in the document. and that worked.
Thnx for ur help so far...
anil

Runtime error in Receiver determination

Hi All,
While testing my configuration in ID, it shows an Runtime error message "Message is incomplete. No Sender found".
Note: I testing for a File to Idoc Scenario.
Regards,
Nithiyanandam

Hi,
 Message is incomplete. No Sender found". -- I guess you are not selected the Sender Service,Interface,Namespace and Receiver service in Header section.Before RUN the test configuration you need to check that have you choosen the proper sender and reciver in Header section.
Hope it will helps to you, Check it out the same and try to test the configuration.
Cheers
Veera

Error while doing Enhanced Receiver Determination

Hi,
My scenario is Fiel->XI->File with enhaced receiver determination that is i should get the receivers dynamically at runtime.
I gave Operation mapping in Receiver determination and created all other objects.
Even if i check message mapping i am getting multiple receivers but, in SXMB_MONI i am getting the following error
<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 144</SAP:P1>
<SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Problem while determining receivers using interface mapping: Error when parsing receiver listLength of XML document 144 Error when parsing receiver listLength of XML document 144 System expected the element 'Receivers'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Can anyone suggest
Regards,
Sunitha

Hi,
I am getting error in Receiver Determination step only. so, unable to see the receivers.
Is there any option to check that particular message which conists of receivers in PI.
"In every receiver root node only one receiver can exist.
you have to reapeat the root node for every receiver. "
ya i changed the occurance of the message type. In message mapping i am getting multiple root nodes at target but in SXMB_MONI i got that error.
Regards,
Sunitha

Receiver Determination Not Found

Hi all,
Currently we integrating SAP ECC with TM using PI ,we have followed the standard document given and done the configuration steps ,
"Installations and Upgrades - R" SAP Rapid Deployment solutions" SAP Transportation Planning for Shippers RDS" SAP TM DTP RDS" SAP TM DTP RDS V2.90",the reference document is from the above link.
ECC has triggered an workflow which is in format of XML ,but when we checked in SXMB_Moni,i am getting the below error.
Receiver Determination: No Receiver could be determined
2:26:30 PM
2:26:30 PM
SHDCLNT900
http://sap.com/xi/APPL/Global2
BusinessDocumentFlowTMInformationbyBusinessObjectReferenceQueryResponse_Out
CENTRAL
"Current Status"
Synchronous
BE
IENGINE
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
53EB863237550A10E10080000A1A016E
sender =>R/3 system
Receiver=>TM system .
Your help is badly needed

hi Hareesh,
please find the below screen shot of my ID objects ,we generated it using "Apply Model From ES repository".

No receiver determination found in spite of correct url

Hi everybody,
our partner tries to reach our XI on https adapter to start a synchronous process. The url is as follows:
https://[host]:[port]/sap/xi/adapter_plain?party=[PARTY]&service=[SERVICE]&interface=[INTERFACE]&namespace=[NAMESPACE]
I can see the message in the TA: sxmb_moni but there is always the error: No receiver determination found. But everything is correct. There IS a valid receiver determination set up. Are there any other parameters that have to be put into the url to get that connection online?
Regards.
Oliver.

Yes please...the reason i am asking you try this is that in the comments of the HTTP inbound handler...you see what is below....so i am asking you to put the parameters that seems to be mandatory from this...
call-syntax: XI 3
http://hostname:port/path
 ?namespace=???
 &interface=???
 &service=???
 &party=???
 &agency=???
 &scheme=???
 [&qos= EO|BE|EOIO]
 [&msgguid=???]
 [&queueid=???]
 [&trace=[1|2|3]]
Thanks,
Renjith

Redarding receiver determination

hi all
iam ajay,
here i faced a problem at xi server. even i created the receiver determination it alerts an error in receiver determination.i furnished my error below.
let me know the solution
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem extracting values from the message: The exception occurred (program: CL_SAI_SWF_RULE_ENGINE========CP, include CL_SAI_SWF_RULE_ENGINE========CM006, line: 93)</SAP:P1>
<SAP:P2 />

Hi Ajay,
Have you defined a rule for the receiver determination.
Please can you check on this thread. Same issue
Error evaluation condition in receiver determination
Regards
Vijaya

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>

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

Error: No Receiver could determined

Hi all:
I am setting up one scenario about ' XML to IDOC '.
When I send XML from one R3 system to XI , I meet with the following errors.
"No receiver could be determined"
Anybody could help? Thank you,
Mohamed.

Please find in below my configuration. I don't understand why it doesn't Apparently the XML goes well and it generates an Idoc Number when I see in SXMB_MONI. But when I type this number in WE05, there is nothing with that number.
Thank you,
Mohamed.
Configuration:
Display Receiver Determination:
Sender
Service : Z_SAP_ECC_BS
Interface: MI_Order_Outband1
Namespace :http://test.com/PI01/Idoc
Receiver:
Service: *
Display Interface Determination:
Sender
Service : Z_SAP_ECC_BS
Interface: MI_Order_Outband1
Namespace :http://test.com/PI01/Idoc
Receiver
                                 Inbound interface
Name:Cremas.Cremas05 Namespace:urn:sap-com:document:sap:idoc:messages
                                 Interface Mapping
Name:IM_Order_Idoc       Namespace:Z_SAP_ECC_00 , 1.0 of accenture
Display Sender Agreement:
Sender
Service: Z_SAP_ECC_BS
Interface: Z_SAP_ECC_00 , 1.0 of accenture
Namespace :http://test.com/PI01/Idoc
Receiver
Service :BS_ER6CLNT001
Display Receiver Agreement:
Sender
Service: Z_SAP_ECC_BS
Receiver
Service :BS_ER6CLNT001
Interface: CREMAS.CREMAS05
Namesapce: urn:sap-com:document:sap:idoc:messages
Receiver Communication Channel : GeneratedReceiverChannel_IDoc
Edited by: rahhaoui mohamed on Feb 11, 2009 5:10 PM

System Error: No receiver could be determined

Hi,
When i logged into the portal and click on Time management link which takes you to the time entry application (HRESS_C_CATS),and the below mentioned message is displayed. "System Error: No receiver could be determined ".
Could you pls let me know why this error shown.? This error appeared when a functional guy changed the employee profile.
Any idea how to solve this error?
Thanks,
Lakshmi.
Edited by: Lakshmi Atukury on Feb 13, 2012 7:30 AM

Check siddarth reply in below thread
http://forums.sdn.sap.com/thread.jspa?threadID=2135503
Regards
Srinivas

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.

Error in Receiver Determination

Similar Messages

Maybe you are looking for