Conditions using xpath in Receiver determination

How to write conditions using xpath in receiver determaination. Please provide few examples.
Regards,
Suresh.

hi
Defining Conditions
You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
● If you want to specify a new condition for forwarding the message to a receiver, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert New Condition () and call the condition editor by using the input help ().
● If you want to specify a new condition for forwarding the message to multiple receivers, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert Line After Selection ( ) and call the condition editor by using the input help ().
In the condition editor, you can select an element from the message payload and specify a value with which the value of this element is to be compared at runtime.
check the link below
http://help.sap.com/saphelp_nw04/helpdata/en/67/49767669963545a071a190b77a9a23/content.htm
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Similar Messages

Using Xpath in Receiver Determination for greater than 500

Hi,
I am trying to use Xpath in the receiver Determination step and I want to check a field which is at item level and comes multiple times(0-unbounded) greater than 500.I tried with different options per SDN blogs,Xpath functions,but still I couldn't able to get what i am trying.I want to process the message when "quantity" is greater than 500,else I want to ignore the message with no errors.
I gave like this /p1: /LIST/item[quantity>499] EX
item loop is 0-unbounded and I need to check for every quantity.I selected the check box multi line as well.
I played around different options,but still did not get what I am looking for.
please suggest in this regard ,how I need to give the expression.
Thank you,
Sri

Hi,
For validating that the item field is occuring more than 500 times you need to choose the
2.The exact XPath would be in your case *(/p1: /LIST/itemquantity[499]EX)*
This means if the 500 th occurance of the item exists then the condition satisfies that is always true for 500 and above occurance of the item.
Please revert if the suggestion proves to be helpful.
cheers,
Abhishek.
Edited by: Abhishek Paul on May 6, 2010 10:55 PM
Edited by: Abhishek Paul on May 6, 2010 11:02 PM
Edited by: Abhishek Paul on May 6, 2010 11:08 PM

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

Conditions using xpath in interface determaination

how to write conditions using xpath in interface determaination. Please provide few examples.
Regards,
Suresh.

hi
Specifying Conditions (for Multiple Inbound Interfaces)
If you have assigned more than one inbound interface, you can specify the conditions for forwarding the message.
To do so, in the Condition column, call the condition editor ( icon).
This column is only available when you are assigning multiple inbound interfaces
check the link below on condition editor:
http://help.sap.com/saphelp_nw04/helpdata/en/67/49767669963545a071a190b77a9a23/content.htm
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Use of range in case of XPATH for receiver determination.

Hi Experts,
I need to achieve the following using standard receiver determination.
The material number in the source message structure has to lie within a perticular range and that should decide the receiver of the message.
For example:
MT_SRC
|---- Ele1
|----
MaterialNo.
If MaterialNo is between 100000100 and 100001000 then it should be sent to BS_TGT1 else it should be sent to BS_TGT2.
Is it possible to achieve this using the standard conditional receiver determination using XPATH and if yes, how exactly?
Regards,
Amol

Hi Amol,
I think its possible. Never tried though for a range.
Go through this link and check out what is described under the section "Notes Regarding the Use of XPath Expressions"
http://help.sap.com/saphelp_nw04/helpdata/en/43/a513f2632c332ce10000000a11466f/frameset.htm
I am not sure whether it will work for two conditions though, i.e. for a range( Greater than 100000100, less than 100001000).
Just try and let us know.
Regards,
Sanjeev.

Idoc structure not displying in XPATH at Receiver Determination..!!! Urgent

Hi All,
Doing Idoc to File Scenerio,
In the receiver determination, I need to select the XPATH from the Idoc structure and by based on the GLN number which is coming in one of the segment, I need to pass to different receivers.
Problem here is Iam not able to see the Idoc structure in the XPATH to provide the condition.
But when doing File to Idoc scenarios, Iam able to see the File structure.
Any idea why IDoc structure is not displaying over here??
Its a bit urgent for me..
Waiting for your replys.
Thanks&Regards
Seema.

Hi,
This will help you now
Hi,
If you get the following msg while selecting the BS in Receiver Determination and if you are unable to view the Structure of the Source
"Message interface does not exist in any software components installed on this business system"
1) Open ID-----Double click on Business system that which u are using in the scenario
2) Check whether you are able to see the SWC in the Othere attributes TAB
3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
4) Click on Installed Products TAB
5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
7) Click on Installed products and Check the check box of your Product and then finally save that.
Now you should be able to see the SWC in the Othere attributes TAB in ID
Regards
Seshagiri

Customizing XPATH in Receiver Determination

Hello,
I am using this blog to write conditions /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination and accordingly call the receiver (either Receiver_1 or Receiver_2), never to call both the receivers simultaneously
I have a sample source message like:
<?xml version="1.0" encoding="UTF-8"?>
<ConsumerDetails>
 <UserId>91200024:123456</UserId> To check if UserId starts with 91200024: or not
 <Date>20111301161459</Date> To check if length of Date is 14 or not
 <Billing>RC</Billing> To check if Billing has value RC/ SB or not
 <Type>SE</Type> To check if Type has value SE/ CWE or not
</ConsumerDetails>
Accordingly wrote the below conditions:
Receiver_1 (Conditions working fine):
UserId (MiddleOperator --> ContainsPattern) --> 91200024:*
/ConsumerDetails[(string-length(Date)) = "14"] --> EX
/ConsumerDetails[(Billing = "RC") or (Billing = "SB")] --> EX
/ConsumerDetails[(Type = "SE") or (Type = "CWE")] --> EX
Receiver_2 (Conditions not working; except 1st condition):
/ConsumerDetails[not(starts-with(UserId,'91200024:'))] --> EX
/ConsumerDetails[(string-length(Date)) != "14"] --> EX
/ConsumerDetails[(Billing != "RC") or (Billing != "SB")] --> EX
/ConsumerDetails[(Type != "SE") or (Type != "CWE")] --> EX
Only Conditions for Receiver_1 are working fine; those for Receiver_2 are not. Can anybody please provide correct conditions to be written in the Condition Editor?
~Thanks.

Hello,
Have you tried using the condition as mentioned below:
/ConsumerDetails[not((string-length(Date)) = "14")] --> EX
/ConsumerDetails[not((Billing = "RC")) or not( (Billing = "SB"))] --> EX
/ConsumerDetails[not((Type = "SE")) or not((Type = "CWE"))] --> EX
i.e. use not() instead of '!' ??
-Rahul

XPATH in receiver determination

Hi,
We need to dynamically determine the receiver service based on the payload.
In the extended service editor we have succesfully used a simple XPATH expression to point out a specific field of the payload (just like using af context object) containing the service name.
However, in most cases the service name is a substring of a field of the payload and furthermore a constant is to be added to give the full service name. We have tried to solve this problem using the XPATH functions 'concat', 'string' and 'substring'. But as soon as we add just the simplest function to the XPATH expression, the receiver determination fails (unable to process the XPATH).
We have tested the XPATH with the actual message using XML Spy, and it works well.
The XPATH expression is: "concat('SAPR3_', substring(string(/p1:receipt/p1:identity), 2, 5))"
Any hints?
Regards
Lars

Hi Lars,
I just noticed, that you are talking about extended Service Editor - not a Condition - so my answer above is obviously rubbish.
What remains true is that the XPath you use has to result in a node, than the nodes string is taken as a service.
So I am afraid there is no easy solution for your problem...
If you do not have too many receivers and this list is rather static, you could of course use conditions in the receiver determination - something like:
receiver service = SAPR3_b if /.../ = abc
but this is of course not really applicable if the list of possible receivers gets too long.
Another possibility would be to use the substring as a receiver within the configuration. So take it from the payload in the receiver determination and use this 'service' for interface determination and receiver agreement.
Than, within the receiver agreement you can exchange this name by the 'real' name in the header mapping (which is performed as the very last step in the pipeline). Since you have a receiver agreement per receiver anyway, you would not have to create additional configuration objects. The downfall is of course, that to 'read' the configuration (or the message monitoring) one has to know about this mapping trick...

XPATH and Receiver Determination

In Reference to forum thread : Conditions in Xpath (Receiver determination)
Suppose I have MT as
MT_Pickfile
 |_Header
 |_Body
 |_Trailer
And i need to check;
(field3 = "100" or field3 = "200" or field3 = "300" ) and(field5 = "AA" or field5 = "BB" or field5 = "CC")
field3 is in Header and field5 is in Body
I tried giving
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and /p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
It doesnt work. But then if both field3 and field5 are in Header then it works (as had been the case in the above mentioned thread which Stefan Grube replied to) i.e. to say
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and [(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
Can anybody put in their suggestions ?
Thanx in Advance,
ShaBZ

Hi Shabarish,
It is not possible to have and or or outside the brackets [].
Try following:
/p1:MT_Pickfile[(Header/field3 = "100" or Header/field3 = "200" or Header/field3 = "300" ) and Body/field5 = "AA" or Body/field5 = "BB" or Body/field5 = "CC")]
Another idea:
Write two lines in receiver determination (use insert expression):
1. line:
/p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )]
2. line
/p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")]
Hope that helps
Stefan

XPath in receiver determination: Check content of elements that exist 0..n

Hi all,
I have a simple requirement in a receiver determination. In the structure of the XML message, there is a node "STATUS" with an element STATUS_CODE. This STATUS node can appear 0 or 9999 times.
I want to check if there is ANY STATUS with STATUS_CODE = "0", and if so, the message should be sent to a certain receiver. How to to that?
Will that be the solution: (//STATUS/STATUS_CODE = 0)?
Thanks,
CHRIS

> So it seems to me that the operator != can't be used to check a 1...n element? What might be the reason for this?
I am not sure how != works, it is not documented well.
I suppose NE means: does not exist.
So if any node STATUS_CODE with value 1 exists, then the result is false.
If you want an existence check if this, you should apply this:
//STATUS [STATUS_CODE != "1"] EX
See also:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/13bf7191e73a4fb3560e767a2525fd/frameset.htm
(scroll to the bottom)
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination

How to Take source value remove zero and use it In receiver Determination

Hi
I am working On IDOc to Soap channel.
In idoc Fields ,I am using EMPST field from IDOC and accordingly I am putting Condition in Receiver Determination.
IF EMPST 111 Then Revceive1
IF EMPST 222 Then Revceive2
IF EMPST 333 Then Revceive3
But sometimes values also Come as 000111 or 00111 or 0111 same for Others.
I have used follwong condition in Receiver Determination.
IDOC/E1EDK01/EMPST u2248 *111
But it working fime for leading zero.
But if values come as 8111 or 78111 it is also routing message to Revceive1.
same for others.
Can you plz suggest solution?

you can use enhanced receiver determination ,, where you can specify your logic in the mapping
http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI
http://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
in the UDF you can write the logic to remove leading zeros if required:
Re: removing leading zeros

Receiver Determination Condition and XPATH

Hi Everyone,
I have a receiver determination with conditions and can not figure out why one thing is working, and the other isn't.
As suggested in the following forum post, XPATH and RECEIVER DETERMINATION, I had to do the following to my XPATH expression to make it work. The full xpath expression is this:
(/p1:RenExtract_MT/Detail/CompanyCode = 9740)
where
p1 = http://company.com/xi/fin/
but whenever I put in a condition it could not find a receiver.
Hoewver, when I did this:
//CompanyCode
it worked.
I did everything through the condition editor, many times, and didn't type anything in myself. Is there a length limitation or something (I removed some data in here, the expression is really longer!).
Any ideas?
Peter

Hi Peter,
I do not have an explanation for this wired behaviour.
But I can assure your, that your working solution, the //something expression is a good one and not inferior to a solution using an explicit, absolute path.
Why is that: I can remember some benchmarks, where the //something expression always outperformed the other one.
Regards
Gregor

Receiver determination Condition. XPATH suggestion

Hi All,
I got a condition to put in receiver determination like..
Condition 1 --> System_A
//ZORDER03/IDOC/E1EDKA1(PARVW='LF')/ILNNR = SA       AND
//ZORDER03/IDOC/E1EDKA1(PARVW='LF')/PARTN = 0000050570      AND
//ZORDER03/IDOC/E1EDKA1(PARVW='WE')/LIFNR = 1433            AND.
It it satisfies above condition, message should goto System_A
Condition 2 --> System_B
//ZORDER03/IDOC/E1EDKA1(PARVW='LF')/PARTN # 0000050570      AND
//ZORDER03/IDOC/E1EDKA1(PARVW='WE')/LIFNR # 1433
The values will be coming differently for E1EDKA1(PARVW='LF')/ILNNR like XMl,KNF,DHD,File etc apart from 'SA'.
It is working correctly only for 'SA', not working for remaining values.
Is there any simple way to insert this conditions? Kindly suggest.
Thanks
Deepthi.

Hello,
Kindly check the below condition, assuming PARVW, ILNNR, PARTN are under same parent node i.e. E1EDKA1:
For System A:
//ZORDER03/IDOC/E1EDKA1[( (PARVW = 'LF') and ((ILNNR = 'SA') or (PARTN = '0000050570'))) or ((PARVW = 'WE') and (LIFNR = '1433'))] EX
For System B:
//ZORDER03/IDOC/E1EDKA1[not (((PARVW = 'LF') and ((PARTN = '0000050570'))) or ((PARVW = 'WE') and (LIFNR = '1433')))] EX
-Rahul

Receiver determination - Xpath expression problem with count

I am working with a scenario where I pick up records from a JDBC connection and if the number of records I pick up is less than a certain number I want to call a webservice. If it is greater than the number I want to write out a file to be processed by a different process on the receiving end. I have created the receiver determination condition with the following conditions:
(/p1:MT_HOG_Data/row[count(row) > 3] EX)
(/p1:MT_HOG_Data/row[count(row) <= 3] EX)
The integration is always processing the second condition no matter how many records come in. I have tried with and without the multiline option. Can anyone help with this?
I have searched through the forum and checked the following links without any resolution:
http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/13bf7191e73a4fb3560e767a2525fd/frameset.htm
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
I can't find any examples where a count of records is checked in the expression editor. Thanks in advance for any help.

You can not use the EX operator in that case, because that is used only for node existence checks, not for value checks.
Do you have a row number in your structure ? Then you could write the xpath expression with that counter tag and value
Example: you want to send to receiver A if count > 3, else to B:
you set /rowNumber EQUAL 4 for sender A
and /rowNumber NOT EQUAL 4 for sender B
The condition is applied to the whole document. If one of the node/values are true for that condition, then the whole condition is set to true.
Problem with that is that the second condition also will be true because nodes for that condition will be found
better would be to have a rowcount tag in the structure. If that is not possible, you can use the "Enhanced Receiver determination" where you can define a mapping which determines the receivers. There you can do anything complicated you want.
CSY

Xpath expression in Left and Right operand for Receiver determination

Hi Experts,
Is it possible to use an Xpath expression in both the Left and Right operand inside the Receiver determination e.g.
(/Message/line/IDNumber = /Message/line/IDNo)
Any help will be appreciated.
Thank you,
Brendon

in standard receiver determination you can only specify value for the right operand.
that is one of the reasons you go for enhanced receiver determination
as mentioned in the sap help
If you are using the condition editor to define receiver determinations or interface determinations, you can only use the expression editor to create an expression for the left operand. You must specify a value for the right operand.

Conditions using xpath in Receiver determination

Similar Messages

Maybe you are looking for