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

Similar Messages

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

How many Receiver determination in File to SOAP scenario

Hi,
I am trying a File -SOAP-File scenario, where file will be send to PI asynchronous. BPM is configured to receive the file and
call the web services and get the response (Synchronous call) .After that BPM send the file asynchronous to File via FTP .
It is basically asynchronous/ Synchronous bridge scenario.
To do this I have have configured the BPM & created 3 Communication channel . 1 sender (File) & 2 receivers ( SOAP & File)
But i got confused in Receiver determination. How many Receiver determinations do we require in this step? 2 or 3. If 3 how they will look like. I believe Interface determination is same as Receiver determination. I am suing Business System to send & recv the file.
Points will be rewarded for suitable answer.
Thanks

hi,
You require 3 receiver determinations.
one from File to BPM(XI)..
another from BPM to SOAP and other from SOAP to FILE.
This is exactly the same scenario.
RFC Scenario using BPM --Starter Kit
Thanks,
Vijaya

Dynamic receiver determination for synchron interface

Hello everybody,
I want to use dynamic receiver determination for a synchron scenario.
The problem is, that the interface 'ReceiverDetermination' (http://sap.com/xi/XI/System SAP BASIS 7.00) is a asynchron interface.
This leads to an error when activating the Interface-Mapping (synch source Interface -> asynch destination Interface ReceiverDetermination)
Is there a way to use the dynamic receiver determination for synchron interface?
Thanks a lot,
Thomas

Hi Thomas,
I guess your scenario is not possible ASIS, since XI doesn't support 1:n for sync interfaces (and even if your mapping condition reduces it to 1:1, actually it is still 1:n, since your receiver list is unbounded).
Theoretically, you could make it work with BPM, though.
But I've never worked with a Receiver Determination Step reading from an enhanced receiver determination in ID (though there should be no problems).
Use sync async bridge, then use receiver determination step to obtain the receiver from an enhanced Receiver Determination. Pay attention that this enhanced receiver determination is a dummy one, using a mapping from your async abstract interface to the ReceiverDetermination interface. Once your mapping has determined the receiver, the enhanced receiver determination will return that receiver to the Receiver Determination step in the BPM. Then use this receiver in the sync send step (in mode receiver from receiver list, not from context).
The receiver determination of the actual sync send step may be a standard one, with the several receivers there (even if there are several there, at the moment of the sending, only one will be used).
Maybe it will work, maybe not.
Just try it.
Regards,
Henrique.

Need of creating receiver determination and interface determination

what is the need of creating interface determination where as providing all the details in Receiver determination?

Hi,
The loose coupling between the Interface mapping and receiver determination have provided the compatibility for reusability.
The Interface determination maintained and just linked to receiver determination so you could have multiple receiver determinations with common interface determination or vice-versa.
If you provide all the information in receiver determination then, it would be very dfficult to have the various mappins for multiple receivers maintained in receiver determination.
Interface determination is applied at runtime to all messages to be processed. Thus from security point of view of transaction of data. its preferable.
Thanks
Swarup

Enhanced Receiver Determination in PI7.1

Hi,
We have a requirement where in we have to use the Enhanced Receiver Determination for one of our scenarios for choosing the receiver.We are on PI7.1.
As of now,we have mapped a constant rcvr(Test_Supplier) to the Service in the message mapping from our source to the target -Receivers, as we do for Enhanced Receiver determination.The rcvr determination choosing Extended and the correct Operation mapping has been configured.The coresponding Interface determination and Receiver agreements have also been configured.
When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is it necessary to map the party field also in the message mapping?Am I missing something here?Kindly advise.
Thanks and Regards,
Induja

When trying to test this by posting a payload through RWB,we get the No_Receiver_Case_Async error.
Is the Mapping which you developed to determine the receiver(s) able to give the appropriate output? Apart from cache problem, this can also be the issue when the mapping does not produce i.e. no proper service is populated in the corresponding node....the service must be actually present (and active) in ID
Regards,
Abhishek

Enhanced Receiver Determination in Synchronous Scenario

Hi,
my synch scenario with standard Receiver determination is working fine.
the service interfaces i used are SI_OutSynch_EmpInfo_Request and SI_InbSynch_EmpInfo_Provide.
I am now trying to apply enhanced Receiver determination for the same synch scenario.
For this, in ID, in my Receiver Determination object i selected the radio button Extended, then it is asking for an operation mapping. infact it is asking for an OM with sender Interface=SI_OutSynch_EmpInfo_Request (from my swcv) and Receiver Interface = ReceiverDetermination (from SAP BASIS swcv)..
So I logged into ESR, and created an OM_test_EnhancedRD, with sourceInterface=SI_OutSynch_EmpInfo_Request (from my swcv) and TargetInterface = ReceiverDetermination (from SAP BASIS swcv)
But when i tried to activate the OM_test_EnhancedRD, it is not getting activated, and giving below error:
Interface modi are different. Source interface Operation SI_OutSynch_EmpInfo_Request | http://mycomp.com/myns is synchronous. Target interface Operation ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
So my queries are:
1. is for synch scenarios, if receiver information is part of the request payload, how can we apply the extended Receiver Determination, so that the Receiver is determined dynamically.
2. or is there any synch version of ReceiverDetermination (from SAP BASIS swcv) available.
thanks in advance.
madhu.

in this case, does SAP provide synch version of ReceiverDetermination SI, so that we can use that in OM for enhanced Receiver Determination.
If you have a look at the blog-reference given by Ravi you will find a way on how to make the ReceiverDetermination Si synchronous or work with the same async SI.....for quick reference below is the way mentioned in the blog:
From the blog:
Option 1:
A quick and easy way to allow for synchronous enhanced receiver determination setup is to circumvent the check that prevents
a synchronous interface to be matched to an asynchronous interface in an interface mapping. This can be done simply by
manually entering the name and namespace of the ReceiverDetermination interface object (e.g. 'ReceiverDetermination'
and 'http://sap.com/xi/XI/System' respectively) for the target/receiver interface in the interface mapping, but leaving the value for
the Software Component Version empty.
Option 2:
Select Modify and then change the mode to synchronous. Since a synchronous interface requires an input message as well, you
can reuse the Receivers message type used in the output message - it doesn't really matter as long as some message type is
used.
Both of the above options are available under the Applying the Workarounds section of the blog
Regards,
Abhishek.

Any possiblity to use single Inbound Service Interface with multiple Receiver Agreements

Hi All,
Scenario: PROXY to FILE.
Requirement is to receive to two locations.
Is it possible to use single Inbound interface with multiple Receiver Agreements. I tried using two operation in the Inbound Service Interface, and Operation Specific in Determination. But couldnt proceed further. Do I need to use seperate Service Interface for two receiver locations?
Please suggest some solution.

Hi Naveen,
There is a possibility but in the case in the same server location with dynamic configuration: Placing file in two different directories using single receiver communication Channel
With different location you would need to develop a new adapter module as Amit Srivastava explains and develops here Send File to Two Different Locations using Adapter Module
Regards.

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

BPM - Do we need receiver determination step between trans and sync send?

Hi Gurus,
I have a 1:1 transformation step followed by a sync send step. The transformation step is executing fine. While the sync step is executing, I am getting an error says 'No receiver determination found'.
While I am executing this sync step in a separate, it is working fine.
Do I need to have 'Receiver determination step' between Transformation step and Sync send step? I think so. Can somebody confirms this?
Thanks for your kind help.
Kalyan

Hi,
I think there is no need of a Receiver determination step in the BPM.
You should have a proper receiver determination in configuration for this BPM scenario. (i.e) A receiver determination from BPM to the service configured for the synchronous interface.
Regards,
P.Venkat

Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

How to determine receiver from multiple receiver systems

Hi all,
I've scenario :
soap req -> XI -> req to external database -> resoponse from db to XI -> BAPI request -> response from BAPI to XI -> send response to SOAP Response.
In this scenario we have multiple SAP HR Systems. Now external database sends URL field and using that URL field I've to determine which SAP HR system is going to be used to get BAPI response. Each SAP HR system uses the same BAPI structure.
How can I determine particular SAP HR system based on URL field.
I am using BPM for this scenario.
Is there any way I can do this whole scenario without BPM?
Please help me on this issue.
Thank You,
Chintan

Hi Chintan,
Have you tried with the conditional routing with Receiver Determination.
That could probably help you to route to various SAP HR business systems based on the URL field.
For the whole flow you need BPM...but for SAP HR systems receiver determination will be sufficient.
Let me know if you need any more details on it.
also check with below links
Xpath expression
Illustration of Enhanced Receiver Determination - SP16
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
Customise your 'XPATH' Expressions in Receiver Determination
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
/people/shabarish.vijayakumar/blog/2005/08/03/xpath-to-show-the-path-multiple-receivers
http://help.sap.com/saphelp_nw04/helpdata/en/d6/e44fcf98baa24a9686a7643a33f26f/content.htm
Hack: Using XPATH in XI Message Mappings
/people/daniel.graversen/blog/2006/12/29/hack-using-xpath-in-xi-message-mappings
Thanks
Swarup
Edited by: Swarup Sawant on Apr 4, 2008 4:40 AM

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

Add Interface mapping to Receiver Determination is not possible

Hello,
I create some scenarios from R\3 to BW and R\3 to File.
When I want to add Interface mapping to Receiver Determination is not possible.
Not to choose from list and not with copy and paste.
Any ideas?
Regards
Elad

Hi Elad,
Just check whether ur interface mapping that u defined in IR is activated properly or not.It will be present in the hit list as soon as u click the help button of the interface mapping of the interface determination in the ID.
Regards,
Prasanthi.

Is multiple receiver determination possible in a Sync scenario

Similar Messages

Maybe you are looking for