1 Receiver Agreement, multiple Receiver Determinations

Hi Gurus,
Is this possible?
1 Receiver Agreement, multiple Receiver Determinations
I can't create a new receiver agreement because the object already exists.
I can't see the receiver agreement that was created before in the new receiver determination that i created.

Hi,
yes you can have one receiver agrement for multiple Receiver determinations..
let me explain one example.
Sender System File(BC_FILE) and receiver System SAP ECC.
suppose you have multiple secnerions between File System to SAP ECC,but mutiple scenarions sending data to ECC in the form of ORDERS IDoc, in this case you will crearte N number of receiver determinations but only one receiver agrement.
i hope i got you query correcttly.
Regards,
Raj

Similar Messages

Is multiple receiver determination possible in a Sync scenario

Hi I have a scenario - Syncronous interface -> RFC to JDBC. There are two target databases. based on the one of the input fields in the source message I have to route the database call to one of the two databases.
When i put the condition (which is mutually exclusive - one onlt receiver is always selected at a time) in the receiver determinationand executed the interface I got a message saying sync messages cannot have multiple receivers ... even though the condition was such that only BSwould have been selected..
Is there some work around for this?
regards,
Arvind R

Hey
As far as i know, its not possible to have multiple Syn receivers with regular Receiver Determination.
You can try 2 options:
1. Try using "Extended Receiver determination" instead of regular Receiver determination, not sure if it will work but worth a try.
2. Use BPM as given in below help.
http://help.sap.com/saphelp_nw04/helpdata/en/11/13283fd0ca8443e10000000a114084/frameset.htm
Thanks
Aamir

Receiver agreement not visible in receiver determination( ID)

Hi,
I could not see receiver agreement in receiver determination in ID.
Even i could see my receiver agreement in ID.
Give some inputs to solve this issue.
Thanks & regards,
Ruban

Hi,
I did as u said..even though i could not see receiver agreement in receiver determination.
One more issue is in interface determination, if i select type of interface determination as Enhanced i could able to select name and Name space in inbound interface and interface mapping.
If i select type of interface determination as standard i could not see name , name space for inbound interface and interface mapping.
Thanks
Ruban

Receiver Determination when multiple Product Versions / identical namespace

Hi,
How would the receiver determination be done when we have multiple product versions with identical namespaces and interface names ?
During development, when we do a release transfer to another product version, the namespaces and interface names remain same as the current objects.
How would XI resolve the correct interface in this case ?
thanks,
Manish

The XI does not care about the application systems. When a message is received by the application, it knows, what to do with the messages.
The receiver could be an RFC call, an IDOC, an Abap Proxy, here the correlation between interface and Abap code is unique.
The receiver could be a File, or JMS adapter, here the correlation between interface and communication channel is unique as well.
You might reuse IDOCs or RFCs or in rare situations other interfaces in different software components and install them for the same application system. But you can only generate proxies from one interface.
Regards
Stefan

About receiver determination. a message contains multiple records

there is a message which contains multiple records.
how to make receiver determination for the scenario.
like:
<root>
<orders>
 <order>
 <id>1<id/>
 <adress>A<adress/>
 <order/>
 <order>
 <id>2<id/>
 <adress>B<adress/>
 <order/>
 <order>
 <id>3<id/>
 <adress>C<adress/>
 <order/>
 <order>
 <id>4<id/>
 <adress>D<adress/>
 <order/>
 <order>
 <id>5<id/>
 <adress>E<adress/>
 <order/>
<orders>
<items>
 <item>
 <orderID>1<orderID>
 <productName>car<productName>
 <item/>
 <item>
 <orderID>1<orderID>
 <productName>computer<productName>
 <item/>
 <item>
 <orderID>2<orderID>
 <productName>apple<productName>
 <item/>
 <item>
 <orderID>3<orderID>
 <productName>shoe<productName>
 <item/>
 <item>
 <orderID>4<orderID>
 <productName>cup<productName>
 <item/>
 <item>
 <orderID>4<orderID>
 <productName>car<productName>
 <item/>
 <item>
 <orderID>5<orderID>
 <productName>book<productName>
 <item/>
 <item>
 <orderID>5<orderID>
 <productName>pen<productName>
 <item/>
<items>
<root/>
i wanna make receiver determination.
if <adress> is A, forwards corresponding order which includes both <order> and <item> to receiver A.
if <adress> is B, forwards corresponding order which includes both <order> and <item> to receiver B.
i don't know how to make receiver determination?
Edited by: joy zheng on Aug 29, 2009 6:03 AM

I think what you can do is, just create different mappings based on number of receivers and accordingly create different Interface mappings for your corresponding message mappings. While doing your mapping use the conditions to map only desired data. Now in your configuration do your RD and add all your receivers without any condition. Remember your Interface Determination should contain the corresponding interface mappings.
if do that as you described.
identic message need to be sent multiple times.
that is not my expectation.
it is only way to use bpm.
Edited by: joy zheng on Aug 31, 2009 5:14 AM

Tables for Receiver Determination and Receiver agreement

Hello Experts,
Is anyone aware if there is a some table which gets updated whenever we create a receiver determination or receiver agreement in PI. If possible can you guys give me the table names.
Thanks in advance,
~ Suraj

hi Suraj,
SAP XI is built having two stack the abap and the java stack. Its not all that correct that only cache info resides on the java stack and nothing on the abap stack.... Its like black box and the internal workings are hidden from end users ... only sap would be able to tell you. As someone in this thread has given his point of view that only cache info is stored on the java stack which may be correct but how much so is open to debate. I wonder whether you have played around with the table that you come across with the transaction sara.
Suggestions are most welcome
Regards
joel

Receiver Agreement and Interface determination

Hi
I have an input file that generates two output files. The two output files go to the same interface. One output file will have header and the other will have details. I want to kow how many receiver determination, interface determination, sender agreement and receiver agreements we need to create
Regards

Hi Ajith,
As perception, I understand that you would like to like to split the input file into two as Header and Details. For this requirement, you should need Integration Directory (Configuration) as below:
1. Need to Two Receiver agreements.
2. One Receiver determination.
3. One sender agreement.
4. One Interface determination ( Type: Enhanced)
Thanks,

Sender Uses Virtual Receiver - Receiver Determination & Sender Agreement

Hello all,
There is a Checkbox with Sender Uses Virtual Receiver while creating Receiver Determination & Sender Agreement.Could anyone tell when one shall use that checkbox & diffrence of using the same in Rx Determination & Sender agreement ? And Lastly What is the significance of using * in Party &
Service in that Sender Uses Virtual Receiver part ?

Hi,
we will use it when we are using B2B scenario......
More details... please check this.............
/people/shabarish.vijayakumar/blog/2008/09/16/virtual-receiver--why-do-you-really-need-it
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/virtual%252breceiver%252buse%252bin%252breceiver%252bdetermination%252bb2b(Idoc%252bto%252b(File%252cIdoc%252bor%252bany%252bother%252bsystem))
http://help.sap.com/saphelp_nw04/helpdata/en/b1/f29e7a56e18a439984a3c6630951d2/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/content.htm
Thanks

Clear explanation of Sender Agreement, Receiver Determination..etc

Hi Experts,
In Configuration, I know the terms Sender Agreement, Receiver Determination, Interface Determination and Receiver Agreement.
But I would like to understand cleary what exactly each of above term and what it does.
No direct technical definitions please.. as i already read those in help.sap.com
Can someone please explain in usual simple terms, which even a layman can also understand what is SenderAgreement, Receiver determiniation etc..
Thanks in advance.
Sree

Hi sree,
u need to give Receiver of ur message in receiver determination....if u hv more than one recivers of ur messages then u can also do this with condition
in receiver determination we give sender service, sender interface and receivers
now we must provide inbound interface( interface/structre of receiver)...so we provide it in interface determination 
Sender agreement contains sender communication channel...that is one who can understand message from sender...eg if ur sender is file ur sender Comm channel will b file.
Similarly Receiver agreement contains receiver communication channel...that is one who can convert message understandable to receiver...eg if ur receiver is RFC ,ur receiver Comm channel will b RFC.
is it clear??? if not u can ask again....we r here to help u
Thanks,
Maheshwari.

Configuring receiver determination with multiple messages in BPM

I am configuring a BPM scenario which uses 3 abstract interfaces, one for receiving, 2 for sending. I need 2 abstract interfaces while sending because they use different message types. I have created a Receiver Determination for the 1st interface, but the problem is that when I try to create the second Receiver Determination the 2nd abstract interface is not listed after I select the Integration Process. Just the 1st interface is listed under the Integration Process. What might be the problem?

Did you try to delete and reimport the BPM with the same name ?
SKM

Multiple targets using extended receiver determination

Hello,
One quick question related to extended receiver determination
for same receiver 4 conditions exists.
at the same time 3 can become true.
will the extended receiver determination has the capability to create 3 records for the same receiver depending on the condition?
if cond1 -->> target1
if cond2 -->> target1
if cond3 -->> target1
if cond4 -->> target1
( I am using ext interface determination so that my message inputs to receiver determination is also many )
but now when I execute, its executing only first condition n generating records generated with the first condition only.
regards,
nikhil.

im using extended receiver determination n giving 4 diff conditions as inputs to the receiver.
however, thanks...
answer is you can do it
its working

BPM : Receiver Determination Step

Hi,
I was wondering why we need a Reciever determination step since on send step xi automatically find that there are multiple receiver and sends them accordingly to the different system as per reciever agreement.
Is it that the receiver determination is only useful for multicast which is for send and waiting for the message response from those receiver.
Kindly let me know your comments.
THnks

Hello chinna,
You need receiver determination step becoz even though in BPM u define what are ur receivers but not what service its handling. Lets say this is the scenario :
File>RFC>FILE
ex: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
You dont specify in the receivers of BPM where to write the file and how to write the file?
Please elaborate ur scenario i coudlnt get the second part?
Vara
[PLEASE REWARD FOR POSTING]

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

"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

Extended Receiver Determination problem

Hi,
I am making use of extended receiver determination to send 1 source to multiple target systems. When I was testing so that the interface would just send to 1 target system while still making use of the extended receiver determination, I got the following error CO_TXT_OUTBINDING_NOT_FOUND and "No receiver agreement found". The red flag error occurs during Technical Routing and when I checked the details SOAP Header -> Main, I found that the following:
Sender Service: ServiceA (correct)
Sender Interface: InterfaceA (correct)
Sender namespace: NamespaceA (correct)
Receiver Service: ServiceB (correct)
Receiver Interface: InterfaceA (wrong)
Receiver namespace: InterfaceA (wrong)
It seems that extended receiver determination was able to successfully determine the receiver service but fail in determining the correct receiver interface and receiver namespace. Does anybody know why this happen and how to correct the problem?
Some investigation that I already done:
1.) I temporarily changed the extended receiver determination to a standard receiver determination and specifying the 1 target system explicity without changing any other object in both IR and ID as well as using the same test file. The result is that this worked and the file was sent succefully to my intended target system. This tells me that the problem might either be in the extended receiver determination or in the message mapping or message interface Receivers. Also, this means that all the other objects in ID for this interface is configured correctly.
2.) I tried hard coding the target system as a constant in the message mapping for the Receivers message type and still make use of the extended receiver determination and I got the same problem mentioned above.
3.) I tried deleting the receiver determination, activating the changes, re-create the object and activate it and I still got the problem
4.) I tried checking sxi_cache and everything is up to date and correct
Any suggestions is highly appreciated.

Elbert,
I you are doing only standard receiver determination only and using certain condition you are sending to different targets. If yes check this url:
/people/prasadbabu.nemalikanti3/blog/2006/09/20/receiver-determination-based-on-the-payload-of-input-dataextended-xpathcontext-object
Can you please put the payload after message mapping and the xpath condition you mentioned. or if you are doing enhanced receiver determination please check this:
Re: Error in enhanced receiver determination
---Satish
Edited by: Satish Reddy on Jun 23, 2009 9:08 AM

1 Receiver Agreement, multiple Receiver Determinations

Similar Messages

Maybe you are looking for