Receiver determination wildcard in condition editor

Hi experts,
I have a question regarding the condition editor for receiver determinations on PI 7.1. I have an xpath expression on the left side and I need to have a condition on the right side that includes a certain pattern.
One example:
p1:myDocument/element = 1A2B*
There I would want to read the xml element "element" and redirect to a certain communcation component if the value of 'element' starts with 1A2B.. regardless if its 1A2B3 or 1A2BC and so on.
Is that possible? I tried like in the example to use * as a wildcard, but that didn't work.
Any help would be appreciated.

It should not be = operator ....it should be Contains Pattern Operator
Refer: http://help.sap.com/saphelp_nwpi71/helpdata/EN/67/49767669963545a071a190b77a9a23/content.htm
Regards,
Abhishek.

Similar Messages

Receiver Determination, Configure Receivers, Condition configuration alert

Hello Colleagues,
when i try to configure condition area under Configured Receivers at Receiver Determination i get following notification:
Message Interface does not exist in any software components installed on this business system.
Could tell me someone where is the problem?
Many thanks in advanced!
Regards,
Jochen

> Hi Krishna,
>
> the message type "INTERNAL_ORDER.INTERNAL_ORDER01"
> exist under Software Componenten Version\Imported
> Objects\IDocs at IR and is activated.
>
> Regards,
>
> Jochen
Under which SWCV it exists in IR?
As pointed by Bhavesh, you have to add the product that contains this SWCV to Technical System which contains the Business System you're trying to use that interface with. It's done in SLD.
When you select the product, make sure you mark the proper SWCV in the left panel, then save it. It'll be added to that Technical System. But you still need to go into the specific Business System and select that SWCV, in order to properly associate it to the BS.
In the future, as a project best practice, make sure you follow these steps b4 starting IR/ID development.
1. define your project SLD (Technical/Business Systems);
2. create/import the Products/SWCVs you're going to work with;
3. associate the Products/SWCVs to the relevant Technical/Business Systems in SLD.
Regards,
Henrique.

Receiver Determination.. Condition: Receiver has to pass greter than 7000.?

Hi All,
I need to
Send to receiver B when the RCVPRN value is > 7000
Send to receiver A when the RCVPRB value is <7000.
When I checked in the receivert determination condition tab, I found that there is no ">" symbol to put in the condition.
How can we achieve it?
Thanks
Deepthi.

Hi Deepthi,
I think there is some problem with display here in reply...
try using these .. (i m not having access to system right now, so i cann't test)
(/DESADV01/IDOC square Brace start ( E1EDK07/RECIPNT_NO < 0000007000 ) square brace end EX )
OR
(/DESADV01/IDOC square Brace start E1EDK07/RECIPNT_NO < 0000007000 square Brace end EX )
Sachin
Edited by: Sachin Dhingra on Mar 26, 2009 1:06 PM

Receiver Determination, condition to select receiver doesn't extract values

Dear all!
I have SAP PI 7.1
I am facing problem in Receiver Determination while using Condition to select receiver based on the values in the payload.
I need, if Identificador = 1 then receiver BC_1 and if Identificador = 2 then the receiver BC_2
My payload has the value:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:p1="http://pruebas.endesa.es/AME4S_2">
<soap:Body>
    <p1:MT_WS_SENDER_Q>
      <IDENTIFICADOR>1</IDENTIFICADOR>
      <OBJECT_ID>7600000009</OBJECT_ID>
    </p1:MT_WS_SENDER_Q>
</soap:Body>
</soap:Envelope>
But, the trace shows following:
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:MT_WS_SENDER_Q/IDENTIFICADOR </Trace>
<Trace level="2" type="T">......extracting values found: 0 </Trace>
I tried with double quotes, simple quotes, without quotes...
I tried too with a Receiver Rule (with context) and local rule with xpath....
Can someone please advise?
Thanks in advanced!!

Hello,
/p1:MT_WS_SENDER_Q/IDENTIFICADOR = 1
Can you try //p1:MT_WS_SENDER_Q/IDENTIFICADOR = 1 ? I'm sure I read it somewhere here in SDN regarding the xPath difference for stateless and stateless XI 3.0 compatible version is an additional /. It's worth to try
Hope this helps,
Mark

Dynamic Receiver Determination [W/O using BPM] Sync interface

I have been exploring options w.r.t. performance sensitive service interface.
This has following issues :
1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.
2. Prominent answer would be Enhanced receiver determination step but that doesnt work in sync case.
3. Classic Receiver Determination needs the condition to be evaluated in source msg. which is not going to happen.
4. Use BPM i designed one but performance its not all acceptable it has a round trip of 10Sec.
are there any ways to overcome this ?

Hi Bujji,
can you explain the point 1.
<i>1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.</i>
Thanks and Regards,
Himadri
null

How does Receiver Determination Step in BPM work?

Hi,
I'm still in trouble with the Receiver determination step in the BPM...
Normally, when you use the send step, it sends the message in the flow context. Am I right, when I suppose, that when you put the receiver determination step before this send step, the send step sends the message in the context of the receiver determination - that means: if in the Integration Directory, there is receiver determination (with some conditions) and these are matched with the message in the send step, the send step sends it into the receiver, that is defined for the condition and not in the flow context... Right?
Please, write me just your experiences and not links to the documentation. I read it all, but... :O(
Thanx 4 your help, Peter

Hi Peter,
The receiver determination step is used to get a list of receivers for a subsequent send step.It makes a call to the receiver determination you configured in the Integration Directory and returns the receiver list.
Here you specify the send context and the multiline container element for the receiver list.
The send context is a string.The send context can have any string value and depending upon the condition in recvr determination you can route to multiple receivers.
Regards
Priyanka

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

Receiver Determination

Hi,
We are running SAP PI 7.11.
Input message:
<?xml version="1.0" standalone="yes"?>
<SITE_ERROR xmlns="http://test.com/SITE_Error">
<ERROR_DATA>
    <ERROR_DATE>20110120</ERROR_DATE>
    <ERROR_TIME>060002</ERROR_TIME>
</ERROR_DATA>
<SITE_INFO>
    <SITEID>AZAZ</SITEID>
</SITE_INFO>
<ERRORS>
    <ERROR>Version 2.00</ERROR>
    <ERROR>Bla Bla 1</ERROR>
    <ERROR>Bla Bla 2</ERROR>
    <ERROR>Bla Bla 3</ERROR>
</ERRORS>
</SITE_ERROR>
I require to route the message for delivery if a second node in XPATH /SITE_ERROR/ERRORS/ERROR occurs else it will not be delivered.
It seems that receiver determination with a condition in the form of a XPATH expression should solve this problem as I would be able to determine if there is a second "ERROR" node and if there is then route it for delivery. However when the rule is not satisfied then for "If No Receivers Is Found, Process as follows:" rule I set "ignore".
Please could you leant some assistance in constructing the XPATH expression? I have it down as:
(/SITE_ERROR/ERRORS/ERROR[(2)] EX )
Your assistance in this matter will be greatly valued.
Regards
Willie Hugo

your Xpath condition seems fine as you have used EX in that it will check for existance of the field element and will route that interface to mentioed system..
which is right.. but as you mentioed its not working I think there is possibility that its problem of cache ..
just to rechcek..
-- check Cache status..
-- go to SXI_CACHE and check status for your receiver determination object..
-- if everything is not green then try to activate receiver determination one more time.. just to be on safer side you can reactivate all ID side objects..
then again check your scenario..
this is about Xpath..and as you mentioed "If No Receivers Is Found" you have selected igonre then in this case it wll just ignore this message and will not show in SXMB_MONI also..
here you can select alternate business system or for timebeing select same receiver system and check.. if it is working..
it should work as your configuration looks fine..
Thanks,
Bhupesh

Drop messages in Receiver Determination?

Hello,
we are using SAP XI 3.0 and have a simple File-to-IDoc-Scenario.
Now, the files coming from a new supplier (specific ID) should be dropped on the XI.
I've tried a solution at the Receiver Determination with XPath condition, but I would need to configure a dummy receiver, right?
The option "If No Receiver is Found,... End Message Procesing Without Error" is not suitable for us, too.
Does anyone know an easy way to simply drop messages with a specific condition?
Thanks in advance!
Juergen

Hi Grallert,
You can create a module and then check the supplier and put this module in sender file communication channel before the file adapter is converted. Then if it not that supplier then it gives to file adapter else dont process the file. Then it will not process, but your file still will be there in the location. So copy it to a different location.
Once if you read the file and if it is in xi then you may not do anythign except if no receiver found end message processing without errors or dummy reciever, which you dont want.
Regards,
---Satish

What is context objects and how we can use it Receiver Determination

hi,
i have situation here a idoc is triggered into the xi and i need to use the conditions in the receiverdetermination in that condition i need to use context object how i can use it? and what is the difference it makes and why i need to use it?
thanks in advance
Amaresh

HI,
Context objects are alternative to XPATH expressions. It is like macros in other programming langugage. If you define this , you can use this object in the receiver determination while doing conditional receiver determination
For more-
http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Regards,
Moorthy

Flat Idoc and receiver determination

Hi Folks,
I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
Thanks,
SPMD

Hi Shabbirmdpasha,
You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
PD: Sorry for me english...
Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

Receiver determination based on the filename of the incoming xml file

hi folks,
is it possible to base the receiver determination from the filename (pattern) of the incoming xml file?
suppose, if the filename is partner1.xml, then the receiver determination has a condition of partner1. in this case, the message is received by partner1.
any advise please?
thanks!
-lex

Hi Lex,
You can use Enhanced Receiver Determination for this. Do your normal mapping from source to target. And another mapping for the receiver determination. In that mapping you can use the UDF for Dynamic Configuration and set the filename as the receiver service name.
Use the following blog for Enhanced Receiver Determination:
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
This blog explains the usage of Dynamic Configuration:
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
Regards,
Sanjeev.

Receiver Determination - condition editor

Hi,
I have a receiver determination which receives files and the filename determines where the file is sent/routed. I am using the condition editor for this functionality and need some help. The filename contains the following format 'xxxxxx010xxx20070101.out' where xxx represents different codes depending on the extraction. I used the following in the condition editor:
++++++010* I understood each + to represent a character. This is not working, any ideas?
Thanks,
Leanne

you can utilize XPATH functions in your conditions to acheive the same.
Try to take the help of the following weblog and maybe the string functions of xpath to achieve your results.
ref:
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
http://www.w3schools.com/xpath/xpath_functions.asp#string

Condition editor in receiver determination does not show payload fields

Hi !
We are trying to create some conditions for the receiver determination in a RFC->XI->File scenario, but when we open the condition editor, under the XPATH option we do not set any payload fields to create conditions!!
Any clues?
Thanks,
Matias.

Hi,
Check in SLD if your software component is installed on your business system and then clear SLD cache in ID.
You will see interfaces assigned to your business system and also the payload fields in condition editor
Thanks,
Beena

How to compare two fields in condition editor in receiver determination

Hello,
Is it possible to compare to fields frrom the source in the condition editor of Receiver Determination?
Because on the right hand operand we can specify only constants right and not the source field.
For eg: If field1 != field2 then Reciever = Receiver1
Thanks,
Loveena

In standard receiver determination while defining the condition, you can only specify an element from the message payload using expression editor to create an expression for the left operand and you must specify a fixed value in the right operand, against which the value of the element will be compared at runtime. You can use only these (=,, ,EX) operators. So the functionalities are limited.
so you have to use Enhanced Receiver Determination, In this Instead of creating the receivers in the receiver determination manually, you assign an Interface mapping to the receiver determination and this returns a list of receivers at runtime.
refer this wiki for more details
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=133562771

Receiver determination wildcard in condition editor

Similar Messages

Maybe you are looking for