Receiver Determination Understanding Question

Hi Guys,
I have a question regarding receiver determination in a scenario where I have to send Orders Idocs to multiple Suppliers. For each supplier I would create a new partner with a corresponding communication channel. Since I have one Business system sending the orders idoc I have to set up receiver determination to work correctly. Are there any documents for this kind of scenario?
Regards,
Michael

Hi Michael,
Why do you need any document? Its very simple, you can create it.
1. Create one Receiver determination.
2. Add as many receiver services in that single receiver determinaiton as you want.
3. Create interface determination and receiver agreement for each receiver services.
Pls reward points if it helps you!
BR,
Madan

Similar Messages

Question regardin Receiver Determination

Hi,
IS there any way to determine the receiver from multiple receivers based on value which is coming from User defined function?
I tried XPATH but I am able to populate only Sender Message Type in that. In my requirements I've to put condition based on value coming from User define function in message mapping
for example : I am getting values LOC1, LOC2, LOC3 from database. Now want to put condition like If LOC1 then Receiver1, If LOC2 the Receiver2 etc.. But I am not able to get LOC1 field in XPATH.
Anyone can suggest how to do this? Is there any alternative way to achieve this?
Please help me ASAP.
Thanks in advance.
Chintan

> 1) Enhanced Receiver determination can be used with Asynchronous Scenario. To use it with synchronous scenario we have to use BPM
Actually, it is possible. You just have to implement a few workarounds. Check this blog: /people/jin.shin/blog/2007/12/11/sap-netweaver-process-integration-enhanced-receiver-determination-for-synchronous-scenarios
Also, make sure your mapping for the enhanced receiver determination always result in at most 1 receiver (since sync scenarios can't process more than 1 receiver at once).
> 2) We can't evaluate User Define Function (which is created in Message mapping to get some external data) in XPATH Condition. In XPATH we can use only Source structure to put the condition and find the receiver.
The answer for this questions comes naturally once you understand a little further how XI works internally.
In the message pipeline, the receiver determintion step comes before the interface determination, which is the step that executes the mapping runtime. Hence, at receiver determination, no mapping has been exeucuted in the payload yet, so the evaluation is done over the sender (outbound) interface.
Regards,
Henrique.

Question about Receiver Determination step in BPM

Hello all,
I have a BPM process similar to Multicat BPM Pattern.
I have some questions regarding how the Receiver Determination works:
1. Does it have to have interface determination in the Integration Directory?
2. Does that interface determination (including the mapping) takes place when sending a message to a receiver from that Receiver Determination step,
or should I perform a Mapping step explicitly in the process?
Thanks ahead,
Yoav.

Yoav,
Am not sure if I understood your requirement compltely.
Case A:If you are using a send step without a Transformation Step.
Then Send will have message A being sent out from BPm and then , during Interface Determiantion this will be transformed into Message B by Mapping in Interface Determination and this message B will be received by receiver
Case B:If you have a transform and then a Send
In this case, the mapping has been done, so you have the message B with you and so, them message sent from the BPM will be message BHope this clarifies,
Regards,
Bhavesh
Message was edited by: Bhavesh Kantilal

Another question about receiver determination

Hi friends
Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
Let us say we have the message 1 sent to receiver_1 and receiver_2 no matter what , but the message 1 should only be sent to receiver_3 according to some conditions.
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
Thanks

Can we add a new receiver to the list of receivers in the receiver determination , based in some condition only for this new receiver.
yes you can add list of the receivers in the receiver determination , based on some condition .
my question if I can only put condition for the receiver_3 receiver determination , or do i have to write a UDF for mapping of the receiveres.
dont need to write any UDF's . u have to use Context Object/X-Path for REC3 in rec.det
for ex: field1 = 1000 -> rec3
field1 =900 ->rec1
Edited by: bhavanisankar.solasu on Feb 10, 2012 3:48 PM

Some PI questions regarding RFC and receiver determination

If we import the design objects in one customer system from another customer system , and in the original system there is an imported RFC ,
This RFC has been created in the new SAP customer system.
My question is do we have to import the RFC again , as it is already in the imported design objecs.
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the BPM ,
Thanks

My question is do we have to import the RFC again , as it is already in the imported design objecs
Yes....the RFC/ IDOC should be imported from the system to/ from which you will send/ receive the data.
If the RFC was in system1 earlier and now in system2.....then you have to delete the RFC imported from system1 (if it is not used) and then import it from system2
My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the
BPM ,
Irrespective of sync/ async send step.....you should create Receiver Determination....which will have BPM as sender and the TO_SYSTEM as receiver.....not separately for response....just once
Regards,
Abhishek.

Question regarding Receiver Determination and Differente Namespaces

Dear sirs,
I have the following scenario:
I have a mail account read by a sender communication channel IMAP4 in namespace http://a. The message is sent to a receiver communication channel type XI delivering to an ABAP Proxy at the same namespace. Everything works fine here.
I need to split the route: Reading the same mail account and depending on the message received send it to an ABAP Proxy of namespace http://A or namespace http://B. The receiver determination does not allow to configure destinations of different namespaces.
Please someone could give me an idea how to solve this issue?
Thank you in advance.
Fabio Purcino

Hi,
I have already two receiver agreement and two mapping programs but I'm not able to set these programs on interface mapping because it's on a different namespace.
I attached a image of my interface determination configuration.
[http://img683.imageshack.us/img683/7909/imagenamespacepi.jpg]
Best Regards,
Fabio Purcino

Receiver Determination Question

Dear all,
I have to determine the receiver based on one input field.
If Status is PICKUP or DELIVERY OR READY TO DELIVER, i have to send it to ECC, else i have to send to Error folder.
I did with Receiver determination X-path, and working fine.The issue is if i give "PICKUP" in lower case like "pickup" it is going to error folder.
Means this is case sensitive, How to handle this. In mapping we can transform to Upper case but how in x-path editor to handle this?
Regards

Hi Bhavana,
 Best way, as you already suggested is that in the message mapping where you are putting values into the field Status, convert characters to upper case.Like this UDF below will convert all character to upper case thus receiver determination will work properly. The name of the UDF is changeCase. I have always used upper case for receiver determination.
INPUT to the UDF=" PIckup"
OUTPUT string= "PICKUP"
public class UpperCase {
@param args
 public static String changeCase(String s)
 String a="";
 try
 int i,l;
 l=s.length();
 for(i=0;i<l;++i)
 if(s.charAt(i)>='a' && s.charAt(i)<='z')
 a+=(char)((int)s.charAt(i)- ('a'-'A'));
 else
 a+=s.charAt(i);
 catch(Exception e)
 e.printStackTrace();
 return a;
 public static void main(String[] args) {
 // TODO Auto-generated method stub
 String s="pickupa";
 System.out.println(changeCase(s));
regards
Anupam
Edited by: anupamsap on Feb 27, 2011 4:31 AM
Edited by: anupamsap on Feb 27, 2011 4:43 AM

Receiver determination step - Send context

Hi Experts,
I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
Please validate whether my understand is right or not?
If its correct, then my question is can we populate this value dyanmically, say field value from another message.
Please clarify.
Thanks,
Kar

Check if the below link is of any interest to you:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
From the link:
Condition: when the AirlineID field in the message payload has the value LH, then the message is
forwarded to the receiver business system BUS_100. A context object of the same name from the ES
Repository is used to access the AirlineID field in the message.
It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

Multi Mapping using condition & Dynamic Receiver determination – Used XSLT Mapping

Dear Experts,
 I am struggling to identify an error on the Technical Routing. Firstly according to my scenario, I receive an XML file with multiple PO's and I have to split the file to 2 different target messages. and also according to the source payload I have to send the file to 2 different receivers. first receiver is ABAP Proxy to the back end system and the 2nd one is to a file location. I have used XSLT to split the message into 2 target message type and I have used a XSLT mapping for receiver determination. Does any one have any idea of what I am doing wrong.
Note: some time I will only be able to fill in on target message.
I have attached my XSLT message split mapping with this post, please let me know if you have further question.
Your help is more appreciated.
Advance Thanks,
Pradeep
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vPONUM" select="POTRACKING/Lines[1]/PONumber"/>
<xsl:template match="/">
 <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
 <ns1:MT_Tracking xmlns:ns1="http://www.findel-education.co.uk/axapta">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:if test="$vFlag = 0">
 <Lines>
 <DDate>
 <xsl:value-of select="DespatchDate"/>
 </DDate>
 <PONumber>
 <xsl:value-of select="PONumber"/>
 </PONumber>
 <POLine>
 <xsl:value-of select="POLine"/>
 </POLine>
 <QTY>
 <xsl:value-of select="Quantity"/>
 </QTY>
 <VendorMaterial>
 <xsl:value-of select="VendorMaterialNumber"/>
 </VendorMaterial>
 <AccountRef>
 <xsl:value-of select="AccountReference"/>
 </AccountRef>
 <ConsignNumber>
 <xsl:value-of select="ConsignmentNumber"/>
 </ConsignNumber>
 <CarrierURL>
 <xsl:value-of select="CarrierURL"/>
 </CarrierURL>
 <ConsignURL>
 <xsl:value-of select="ConsignmentURL"/>
 </ConsignURL>
 </Lines>
 </xsl:if>
 </xsl:for-each>
 </ns1:MT_Tracking>
 </ns0:Message1>
 <ns0:Message2>
 <ns2:MT_Tracking xmlns:ns2="http://www.findel-education.co.uk/ecc/ax/po/ftp">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:if test="$vFlag = 1">
 <Lines>
 <DDate>
 <xsl:value-of select="DespatchDate"/>
 </DDate>
 <PONumber>
 <xsl:value-of select="PONumber"/>
 </PONumber>
 <POLine>
 <xsl:value-of select="POLine"/>
 </POLine>
 <QTY>
 <xsl:value-of select="Quantity"/>
 </QTY>
 <VendorMaterial>
 <xsl:value-of select="VendorMaterialNumber"/>
 </VendorMaterial>
 <AccountRef>
 <xsl:value-of select="AccountReference"/>
 </AccountRef>
 <ConsignNumber>
 <xsl:value-of select="ConsignmentNumber"/>
 </ConsignNumber>
 <CarrierURL>
 <xsl:value-of select="CarrierURL"/>
 </CarrierURL>
 <ConsignURL>
 <xsl:value-of select="ConsignmentURL"/>
 </ConsignURL>
 </Lines>
 </xsl:if>
 </xsl:for-each>
 </ns2:MT_Tracking>
 </ns0:Message2>
 </ns0:Messages>
</xsl:template>
</xsl:stylesheet>

Hi Hareesh,
Please find my determination in the XSLT below, I am using enhanced receiver determination.
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/sapxsl" xmlns:p1="http://sap.com/xi/XI/System" xmlns:ns="urn:sap-com:document:sap:idoc:messages" version="1.0">
<xsl:variable name="vFlag"/>
<xsl:variable name="vAX" select="0"/>
<xsl:variable name="vSAP" select="0"/>
<xsl:variable name="vBoth" select="0"/>

<xsl:template match="/">
 <xsl:for-each select="POTRACKING/Lines">
 <sap:call-external class="ZCL_VNAP_OBJECTS" method="CHECK_PO_EXIST">
 <sap:callvalue param="IP_EBELN" select="string(PONumber)"/>
 <sap:callvariable name="vFlag" param="EP_BOLEAN" type="string"/>
 </sap:call-external>
 <xsl:choose>
 <xsl:when test="$vFlag = 0">
 
 <xsl:variable name="vAX" select="$vAX + 1"/>
 </xsl:when>
 <xsl:when test="$vFlag = 1">
 
 <xsl:variable name="vSAP" select="$vSAP + 1"/>
 </xsl:when>
 </xsl:choose>
 </xsl:for-each>
 <xsl:if test="$vSAP > 0">
 <xsl:if test="$vAX > 0">
 <xsl:variable name="vBoth" select="$vBoth + 1"/>
 <xsl:variable name="vSAP" select="0"/>
 <xsl:variable name="vAX" select="0"/>
 </xsl:if>
 </xsl:if>
 <xsl:if test="$vBoth > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_AXAPTA_TST</xsl:text>
 </Service>
 </Receiver>
 <Receiver>
 <Service>
 <xsl:text>BS_ECQCLNT300</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
 <xsl:if test="$vAX > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_AXAPTA_TST</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
 <xsl:if test="$vSAP > 0">
 <p1:Receivers>
 <Receiver>
 <Service>
 <xsl:text>BS_ECQCLNT300</xsl:text>
 </Service>
 </Receiver>
 </p1:Receivers>
 </xsl:if>
</xsl:template>
</xsl:transform>

Receiver Determination and Interface Determination Condition conflict in ICO

Hi,
I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
Sender - Proxy Service
Receiver1 - ReceiverA
Receiver2 - ReceiverB
Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
Test Scenarios:
1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

Hi Sherin,
As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
Hope this helps you.
Thanks,
Durga.

Receiver determination in BPM

Hi Folks,
I wanted to send a message to 2 receivers from 1 sender using BPM. People on SDN advice that I have to use 3 receiver determinations for it. I just can't understand why to use 2 receiver determinations where as I have only 2 receivers. Why shall I use a receiver determination for the sender ? Can anybody explain this logic ?
Regards,
Santosh

HI Chandra,
There will be only one reciever determination.
In reciever determination what can be done is one sender and recievers will be two as
well as ineterface determination and reciever agreement will be 2.
Can you explain how is this possible?....In the first receiver determination the connection will be done for Sender --> BPM.....
In second BPM---> Receiver1
In third BPM--->Receiver2
Regards,
Abhishek.

Condition check (based on sender file name) at receiver determination step

Hi,
My scenario is File to AS2 (Sender side file adapter and receiver side AS2 adapter)
We have 5 customers, but the source location is same to pick the files, Here we are not using any ESR objects.
Based on the source file name PI need to determine to whoom this file need to send at receiver determination step
Craeted objects
1 Sender CC,
1 Sender agreement,
1 Receiver determination
5 Interface determinations
5 Receiver agreements
5 Receiver CCs.
Could you please provide me your valuable inputs.
Thanks
Ramesh

Hi Venkataramesh,
I understand your scenario as, picking files (different file naming standard for different target customer) from one source folder. Based on file name, that payload should be sent to corresponding target customer. You have mentioned u201CHere we are not using any ESR objectsu201D. I can see two reasons for this decision
1. PI is used to route the messages, i.e., no need to transform the payload. OR
2. Files can binary files like PDF, ZIP, JPG, GIFu2026
Now I can see two possible solutions
1. Simple solution, as proposed by u201CPrabhu Rajesh Janardananu201D, make it into 5 different scenarios (5 sender channels).
2. Bit complex solution, only one sender channel, using extended receiver determination
Step 1:- In Sender File channel check u201CAdapter u2013 Specific Message Adapteru201D in Advanced tab. File Name should be checked.
Step 2:- In Receiver Determination, Select Type of Receiver Determination as u201CExtendedu201D. http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/frameset.htm
Step 3:- Do a Graphical Mapping (use it Operation Mapping in Receiver Determination).
Step 4:-
Source and target of graphical mapping will be same (below), because you donu2019t want to access input payload (it can be XML, flat file, JGP, GIF and you donu2019t have its structure).
<Receivers>
 <Receiver>
 <Party agency="" scheme=""></Party>
 <Service></Service>
 </Receiver>
</Receivers>
Step 5:- Write a UDF in Graphical mapping as below. http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm Pay attention to method declaration
public String Determine_Receiver( Container container) throws StreamTransformationException
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
String valueOld = conf.get(key);
//Put your logic here
if (valueOld.equal(u201Cuser1u201D)) {
return u201Cuser1u201D;}
if (valueOld.equal(u201Cuser2u201D)) {
return u201Cuser2u201D;}
if (valueOld.equal(u201Cuser3u201D)) {
return u201Cuser3u201D;}
Step 6: Now use this UDF to map to u201CReceiveru201D and u201C Serviceu201D.
This solution need more fine tuning.
Regards,
Raghu_Vamsee
Edited by: Raghu Vamsee on Jan 8, 2011 5:56 PM

Integration Process Receiver Determination Step

Hi experts,
May I know whether the "Receiver Determination Step" (in Integration Process) that collects the list of receivers configured, can be used only to find list of asynchronous receivers?
Can't we use this "Receiver Determination Step" in synchronous scenario? If yes, may i know how to?
Thank you!
Best Regards,
Saravanan

Thank you Gaurav!
I can understand we can use multi-casting.
To clearly put my scenario, I have to use synchronous send (so cannot split send and receive step, and so no need of correlation) in my BPM, which have to synchronously send (and so it receives within same step) message to multiple receivers. This is the reason I am trying to use receiver determination step first and in a loop trying to synchronously send message to each receiver and receiving response.
Now my problem is in the receiver determination step, it is not identifying any of the receivers configured in the integration directory. The receiver determination list returns empty.
So, I want to know whether this receiver determination step is only for async receivers or synchronous receivers also.
Best Regards,
Saravanan N

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.

Use of Receiver determination step in BPM

Hi,
I am not clear about the exact use of Receiver determination step in BPM. From my understanding, it is used for synchronous communication with many receivers configured, for eg. Multicast etc. Can anybody explain the use of receiver determination with any specific requirement example.
Regards,
Santosh

HI,
The usage of Receiver Determination depends on how you have designed your BPM. You can have the mapping getting executed in your BPM itself using a TRANSFORM step or you can do it in your Inteface Determination if you are not doing it in your BPM.
If you do the mapping inside the BPM using Transformation step, then you need to send the Message i.e. Mapped message . In this case, your Interface determination will only determine the Receiver Interface, and it will not execute the interface mapping . (if you are not providing the Interface mapping in the Interface determination).
Example is given here-
http://help.sap.com/saphelp_nw2004s/helpdata/en/14/d5283fd0ca8443e10000000a114084/content.htm
Thanks
Swarup

Receiver Determination Understanding Question

Similar Messages

Maybe you are looking for