Reg. condition based receiver Determination

Hi,
    I need to send the records to two systems based upon the value
For Ex. All the material group record letz say (1,2,3,4,5,6) Shuld go to Receiver1 and only the records which belongs to material grp shud go to Receiver2.
I am trying using Condition based Receiver Determination
   For Receiver 1 :-
              I didnot give any condition.Coz all the records have to go to Reciver1.
   For Receiver 2 :-
                 I have written the condn in the Interface determination
            i.e) Material Group = 2.
But All the records are going to these two receivers.I have tried everything.
Thanks in advance
Regards
Anandan

Anandan,
Similar situation has worked for me. Please check the condition you have mention in Interface Determination.
In the Interface determination you need to have 2 inbound interfaces. Specify the respective condition for each inbound interface.
Example: if the Response field has the value as "Success" or "Failure" the message has to go to first interface. The message has to go to second interface only if the response is "Failure". so you can provided following condition in the interface determination:
<b>Condition 1:For first inbound interface</b> (/p1:MessageType/RecordSet/Response = F) OR (/p1:MT_RESPONSE_FROM_PS_BI/RS/Response = S)
<b>Condition 2:For second inbound interface</b> (/p1:MessageType/RecordSet/Response = F)
The above condition has worked for me. Hope this would be helpful to you.
Regards,
Sridhar

Similar Messages

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>

Condition Based Interface Determination in ICO (AAE) - PI 7.1 EHP1

Hi Friends,
We have PI 7.1 EHP1 - SP 04.
In our scenario, we have 1 outbound interface and 2 inbound interface. Based on condition, it needs to select the first inbound interface or second inbound interface.
In the normal configuration, we are able to select. (By click + icon and add condition in the Receiver Interfaces in Interface Determination Step)
When we create configuration using ICO (Integrated Configuration), there is no option in "Receiver Interfaces" Tab to add two inbound interfaces with condition.
Could you please clarify how do we do this in ICO?
Kind regards,
Jegathees P.

IMHO, condition based interface determination is not possible in ICO.
Use Multiple inbound service interfaces... You can handle in design level .. ESR level.
Check the Abhishek's blog... This might be helpful.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1571?quicklink=index&overridelayout=true
Note: Since in your case you need two receiver agreements, you cannot handle through ICO. The above link might be helpful to do multimapping without BPM.
Edited by: Baskar Gopal on Apr 26, 2011 9:53 AM

Condition in receiver determination

Hi,
I am using PI 7.1. My input message is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_EODReport xmlns:ns0="http://hsbc.com">
   <Record>
      <ReportDate></ReportDate>
      <ACHEODReportFlag></ACHEODReportFlag>
   </Record>
</ns0:MT_EODReport>
I want to put a condition in Receiver Determination to check whether   <ACHEODReportFlag> tag contains value 'X' . How should i put this condition?

>
Shilpa Korad wrote:
> Hi,
>
> I am using PI 7.1. My input message is
>
> <?xml version="1.0" encoding="UTF-8"?>
> <ns0:MT_EODReport xmlns:ns0="http://hsbc.com">
>    <Record>
>       <ReportDate></ReportDate>
>       <ACHEODReportFlag></ACHEODReportFlag>
>    </Record>
> </ns0:MT_EODReport>
>
> I want to put a condition in Receiver Determination to check whether   <ACHEODReportFlag> tag contains value 'X' . How should i put this condition?
Condition Editor of RD....Left operand select Xpath and choose the node that you want click Ok.......from the dropdown select = operator.....Right Operand select Constant and give the value as X....

Conditions in Receiver Determination

Hi
        I am doing a scenario in which we are sending PO from R3 to one of two different web-services through XI using RFC.We have already transported our scenario to Production.Using RFC we are executing Webservice.
        Now there on production we want to put conditions in receiver determination according to message data. In F4 help of condition it is not showing message feilds so I filled condition manually but it is not woking. Is there any other way to put conditions there?
       Have anyone face this problem?
       what is the soution of this problem.
       Its urgent!!
thanks in advance
Regards
Sami
Message was edited by:
        sami qureshi

Hi Sami,
Strongly suggested: Do the changes in Dev and re-transport.
in dev u may create a context obj and assign that to ur msg interface. and use this context obj for conditional routing.
Hope it helps.
Regards,
Latika.

CIN - with TAXINJ and "condition based excise determination"

Dear All,
Can I use TAXINJ with "condition based excise determination" for CIN implemenation. We already have TAXINJ and some plants are already working on it.
If anyone already using the same, please share the problems faced / experience.
Actually I done settings for above scenario, but while GRN I am getting Message as " BED, AED and SED for the excise item is zero". And BED not getting populated while doing GRn.
I have created a tax code "C1" and assigned to company code.
THen I have maintained condition record for JMOP in FV11 for BED. ALso settings done J1ID.
PO is created with this tax code C1, taxes are getting calculated when
checked at Invoice tab at PO.
But while making GRN message comes "BED, AED and SED for the excise
item is zero" and excise values dont shows at excise tab in MIGO
Regards

Go through
https://wiki.sdn.sap.com/wiki/display/ERPLO/CIN+Configuration
and
http://help.sap.com/saphelp_47x200/helpdata/en/09/ebf138cdd78a4be10000000a114084/frameset.htm
Hope you will get good idea

Special characters conditions in receiver determination

hi there,
i have the following problem:
There are conditions in receiver determination to find the proper xsl mapping for different segments in IDocs.
That works fine.
But if there are special characters like &, the interface mappings can't be found, because for the conditions the xml is already corrupt.
So, i've tried to replace all occurrences of & with & in a java mapping that is called before the xsl mappings.
It doesn't work, because in that case conditions are processed before the java and xsl mappings.
Do you have any idea how to replace special characters before conditions in receiver determination are processed?
thx in advance
Stefan

Handling the Special Characters in XI
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]
Find out which character encoding the receiver system expects and put the same to the receiver channel.
By default the file adapter would create a file with UTF-8, which might not be useable for the receiver.
check this thread.
Handling Special Characters
check the document :
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Depends upon encoding methods handling will differ,
you can use ISO-8859-1 or ISO-8859-2 instead of UTF-8 for some special characters.
check this blog:
Unicode File Handling in ABAP
*Suppress Special Character *
Suppress Special Character

XPATH condition in Receiver Determination in PI 7.1

Hi all,
I'm doing a Inbound 850 Scenario (no BPM involved)...based on the condition for (/LIST/S_ISA/S_GS/S_ST/S_BEG/D_353 = 00) its should either create ORDERS.ORDERS05 or create ORDCHG.ORDERS05 if (/LIST/S_ISA/S_GS/S_ST/S_BEG/D_353 = 04)...I'm giving the condition in interface determination and multiline selected in the Xpath editor
I'm using PI 7.1 and irrespective of the condition it always creats Orders.Orders05, I have 2 receiver agreements also for both receiving interfaces...
Any solution on how to debug?
Thanks,
Srini
Edited by: Srinivas Davuluri on May 12, 2009 10:56 AM

I forgot to give the prefix...mistake from my side

PI 7.1 - condition during receiver determination

Hi,
I am trying to do the receiver determination condition in the condition editor of integration directory but XPATH or context objects of my interface (corresponding to my software component version) do not appear in the window for maintaining the condition.
I had no difficulty when following the same process during 7.0 or earlier versions but it seems to be issue in PI 7.1.
Anyone else also faced a similar situation or is there any extra step I need to ensure before going for receiver determination (standard not enhanced)?
Your help would be appreciated.
Cheers.

My scenario is:
Source system -> PI (ccBPM) -> Target system
Now I have number of ccBPMs and there would be one picked up based on the payload from source system interface. For this my configuration objects are as follows:
Sender agreement with (source comm component and source system outbound interface)
Receiver determination - at this stage I want to figure out which ccBPM should get executed and hence condition based on payload
interface determination - goes to receiver step of ccBPM with message type same as outbound interface from source system
I have another receiver determination, interface determination for target system interfaces from ccBPM and then receiver agreement.
But in this overall scenario key part is first receiver determination step where ccBPM as receiver is to be determined.
I checked up all my objects again to find out any missing gap from my understanding. But I am not able to get the interface (source system interface) in the condition editor. I tried maintaining the XPATH manually but it ends in error during execution suggesting that receiver could not be determined.
Any more suggestions please?

Condition based Interface determination

Hi ,
Environment : PI 7.1.
Scenario : File to Proxy.
In this scenario , We have a single file interface which reads a file and routes the data to two different inbound interfaces.
Steps followed to do this -
>>Defined two inbound interfaces interface1 & interface2.
>>Both interfaces are pointed to same ECC system.
>>Read the file using a single sender file communication channel.
>>Define receiver ECC in the receiver determination.
>> Define interface determination based on a value of a field in the file structure(source structure). Used XPATH to define this content based routing and selected operation mapping specific to the interface.
1 sender agreement
1 receiver determination ( not using enhaced receiver determination because we have only one receiver)
1 interface determination which has two receiving interfaces based on XPATH condition ( maintain order runtime is checked)
2 Receiver agreements.
2 Communication channels.
For example if you have 10 lines in a file , out of which if 5 lines has a value related to interface 1 & 5 lines has a value related to interface 2. It should push the data into two different proxies as configured.
We are facing a problem in this scenario -
There is no consistency in the logic. Some times it runs interface 1 & some time it executes interface 2.
based on condition 1 it routes the data to interface 1 successfully but the structure is not getting created for interface 2 so it is giving an error stating the interface 2 structure is not available.
In SXMB_MONI the branching steps show two subnodes but if you see the log it shows that in subnode 1 the sender is sender interface & the receiver is interface 1 based on the filter condition. If you see the log for subnode 2 then it shows the sender is sender & the receiver as interface 2 below that it shows another entry which shows the reciver interface is interface2.
Please evaluate and let us know if the approach we are following works or not. If there is any limitations please let us know how to achive this.
Regards,
Reddy

Hi,
Your design is correct but here you missed one point. Here the message is send either to receiver1 or receiver2 depending on the condition but not both. As this does not result in multiple messages with the same payload because only one condition can ever be true at runtime. For more details see the below link
http://help.sap.com/saphelp_nw04/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
If you want to create multiple message then you need do 1:n mapping :
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID2056393550DB10021342992851308291End?blog=/pub/wlg/2927
Shweta.

Content based receiver determination with Seeburger AS2 adapter

We are planning to use the Seeburger AS2 adapter on our XI 3.0 installation to post custom XML documents to XI from external business partners. The problem we have is to do the receiver and interface determination based on the xml message type that is submitted. How can we identify what is the name of the root xml node (which is representing the message type that was submitted to us) during the receiver determination and specify conditions for the receiver determination based on this? We can not use the Seeburger Classifier module here as this is only determining the mapping name to be used for an EDI conversion but can not handle any type of XML message.

Rudy,
I think the easiest way would still be the ReceiverDetermination and creating an XSD that contains the main important TAGs from the different messages.
That should allow you to test for the existing of certain important TAGs or check the value of some TAGS.
I don´t know about aedaptive-adapters, but I don´t think that they are Drummond-Certified. Check out...
http://www.drummondgroup.com/html-v2/as2-companies.html
Without this certification, a lot of your partners might not allow you to use this adapter if you wanna make AS2 with them.
Greetings
Stefan

Generic condition in Receiver Determination

hi,
in receiver determination, we can define a Condition, but in condition editor, under "context object", we have only some standard parameters of PI adapter like "FileName" like http://sap.com./xi/XI/System/file used in Dynamicconfiguration. I saw also some of seeburger... so...
How can we define our own "_generic_" condition ? Do I need to create an Adapter ?
Note: I do NOT want to define a context object (in ESR) and affect it to a field of a service service, because it's limited to one interface , and I want a generic context which could be used for all interfaces (already developped and to be developped).
Thanks.
Mickael

hi Himadri,
thanks for your interest, but no, that's not my subject. I want neither a specific context object based on only one service interface (your blog) nor to define dynamically the receiver by using mapping functions... I would like to have my own predefined context in Context Objects like these of SAP, example: Filename from DynamicConfiguration of a FILE adapter.
I know my topic is a litle too technic... but it's a part of a more global solution (*) to do a pre-control on all my existing interfaces (!). so the solution should be as less intrusive as possible: I do not want to change in depth all my interfaces... supens...
Regards.
Mickael
(*) I'm studying different ways, and this topic is one of them

Reg:Xpath in receiver determination

Hello,
My message strcture looks like below.
Record
Level1
item
field1
Level2
item
field2
Level3
item
field3
There can be multiple items for each level.
Here goes my condition.
I have to send the message to the receiver system "A" only when filed2 value is same across all items under level2 i.e. if there are three items under level2, then field2 should have the same value across the items.
Can you please let me know how do we impliment this in the reciver determination step using xpath?
Regards,
Rahul

Rahul,
Your scenario can be achieved using Enhanced Receiver Determination. Using Xpath in Receiver Determination might become complex for your condition.
Refer below links for Enhanced Receiver Determination.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3343
Regards,
Geetha

Routing condition in receiver determination

Hi,
In my RFC to JMS scenario, i encountered with a strange routing condition for the receiver determination.
I have routing condition like " string length (one field in Bapi)<1" .
Could any one help me how to implement this?
Regards,
Vishnu.

HI check the below links for reference
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=transactional
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a1a0eb43-0b01-0010-23aa-908cc4eaabcd
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/pcd!3aportal_content!2fcom.sap.sdn.folder.sdn!2fco...
note:reward points if solution found helpfull.....
regards
chandrakanth.k

"Problem evaluating a condition" at Receiver Determination

Hi,
I've created a complex mail to rfc interface, in which, message is being send as mail attachment and service inbound interface has multiple operations (each for corresponding rfc).
at Receiver Determination, rule was created with multiple conditions, in order to determine correct "Communication Component" (multiple receiver agreement and interface determination were created to supported this "multi interfaces" scenario).
If no receiver was found message is ignored.
once in a while, bad non-xml messages (e.g., "asdfasdfasdfffdfdsasdf") are being send, is this case, while PI is trying to determining the receiver (i.e., evaluate Receiver Determination conditions) exception is being thrown, message is therefor has system error status* (at sxmb_moni) and it can not be ignored (as i wanted it to be).
how can i workaround this problematic scenario?
Regards
Uri
*Error message (sxmb_moni)
<?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: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Abhishek,
10x for your replay, but as far as i understand this is exactly the case here.
conditions are:
cond1: (/rfc: RFC1 ~ *)
cond2: (/rfc: RFC2 ~ *)
this works as expected in cases of xml messages (in case no cond is satisfied) message is ignored. but, in case of non-xml message exception is being thrown while cond is assessed.
Regards
Uri

Reg. condition based receiver Determination

Similar Messages

Maybe you are looking for