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.

Similar Messages

  • Enhanced Receiver Determination for synchronous interface.

    Hello!
    Was anyone faced with the Enhanced Receiver Determination? When I try to create
    the definition of the Interface Mapping, I get the error:
    "Interface modi are different. Source interface Message Interface MI_My_sync_iface | urn:my is synchronous. Target interface Message Interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous"
    Thank you.

    Hi ,
    U can go through below limks  :
    Illustration of Enhanced Receiver Determination - SP16
    SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios
    Enhanced Receiver Determination in SAP XI - Exchange Infrastructure - Wiki
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhanced%2breceiver%2bdetermination%2bin%2bsap%2bxi
    Thanks

  • Enhanced Receiver Determination synchronous

    Hi all,
    I am running into a bit of a problem when using enhanced receiver determination on a SOAP - XI - RFC scenario on a NW2004 SP17 XI system.
    According to the help.sap.com (http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm) I have to make an interface mapping to the "ReceiverDetermination" async abstract interface.
    Here is my problem: "ReceiverDetermination" is asynchronous and my source (SOAP) interface is synchronous, but it seems impossible to define a interface mapping between a synchronous and asynchronous interface.
    Do any of you have any ideas and/or suggestions to solve my current predicament?
    Steven

    Hi,
    After some experimentation I found a solution.
    It involves building a sync/sync bridge in an Integration Process and using a Receiver Determination step in that Integration Process.
    The Integration Process forces you to store the request/response messages in an abstract ASYNC interface. When the Receiver Determination step calls the Receiver Determination Object in the directory, it uses the abstract async interface of the request message, instead of normal sync interface.
    This enables you to build an enhanced receiver determination interface mapping using the abstract async interface used to store the message in the integration process.
    Steven

  • Interface Determination under Enhanced Receiver Determination Scenario

    Hi,
    One of the very basic assumption for Enhanced Receiver Determination is that Receivers are found at run time, and one of the such requirement is that we don't know about Receiver  Business System at the time of configuration.
    Now for such scenarios, how do we configure "Interface Determination". For Interface Determination one of the input filed is "Receiver Service/Party", in addition to "Sender Service/Party" plus "Sender Interface"
    Since we don't know Receivers at config, what value(s) should come in "Receiver Service/Party" in Interface Determination at config time.
    Thanking all of you in advance

    Hi Rajan,
    You have to do the following things:-
    First, maintain Database Table in SAP XI. Which contains several keys like Sender, Receiver system and then according to that key combination we perform a JCO call and fetch the values which gives us the correct receiver and interface.
    Create a Data Type which will be having Two elements Service And Interface.
    Now careate a message type and message interface for this data type. This will be for your receiver.
    Then use source payload and perform a message mapping between Sender Payload & this Message Type.
    Use UDF and make a JCO call and fetch table entries for service and interface.
    Then in Directory perform extended determination and use this mapping into it. The result will be Service & Interface.
    Thanqs
    Biplab

  • Using Enhanced Receiver Determination with a Synchronous Service Interface

    Hi Experts,
    I want to use ERD on a Synchronous Interface. Is that possible? Perhaps it has no sense, because in an ERD you can choice multiple receivers and that its against the synchronous philosophy: what if you declare 2 or more receivers, from wich one has the right response to be taken?
    In technical terms I build the operation mapping as it is written both in the blog (/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16) and the SAP HELP.
    But in my OM I have as source service interface one Abstract Synchronous and in the target I have one Abstract Asynchronous wich is not possible. So I tried many tricks like creating my own synchronous ReceiverDetermination Service Interface in my SWC, but it is not detected. Other trick will be modifying the standart SI, but it will affect the next guy trying to use ERD with an Asynchronous interface
    The point its that it is a little funny that the receiver determination allows using ERD with a synchronous SI wich makes me think that it will be possible...
    Is it possible to use ERD with a Synchronous Interface?
    Regards
    Gonzalo

    i have seen Enhanced RD with lookups that work. Have to say it was not a RFC lookup used but rather a DB look in one of the implementations i had worked with. But still I really dont think a RFC lookup should be an issue.
    Troubleshoot the lookup mapping to be working other than in the enhanced RD (i.e independently) .
    if you head no where, i suggest opening a OSS note.

  • Enhanced receiver determination - Idoc 2 Idoc scenario

    Hi,
    I am trying Enhanced receiver determination - in an Idoc 2 Idoc scenario.
    But when I selected Enhanced receiver determination in ID, it is asking for interface mapping.As it is an Idoc 2 Idoc scenario, I did not create any mapping objects in IR.
    Is there any round about for this.
    reg,

    Hi,
    if you are planning to send the Idoc to two systems then you do not need Enhanced Recieevr Determination.
    You can add multiple Receivers In the receiver Determination under Configured Receivers and now the same idoc will be sent to 2 receivers.
    Like mentioned by moorhty, Enahnced Receievr Determination allows you to dynamically determine receivers using a mapping program.! I dont think that is needed in your case
    Regards
    Bhavesh

  • 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.

  • Purpose of Enhanced Receiver Determination

    Hi
       i go thrown  the some sap help link  .. But I did't understand.. so, can  any of you plz explain the what is the purpose of the  Enhanced Receiver determination..
    for this.. in mapping side does we need to do any special  things.. or for a normal  scenario also.. can we use this..
    I want to use this   Enhanced  Recever determination in  my scenario.. for that what are the steps  i need to  follow..
    Regards
    Babu

    Hi !
    Enhanced Receiver Determination:
    You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    also check this
    Please Check
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
    /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    Also check ....
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm -
    >Enhanced Interface determination.
    /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination --->Customised XPath
    Also check the following threads
    Enhanced Receiver Determination
    Enhanced Receiver Determination synchronous
    /people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
    have alook at thses URl's also
    http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
    :Dynamic file and variable substitution
    Similarly Extended Receiver determination is used to determine the receiver at runtime.
    Refer my reply:Re: Condition In Receiver Determination Not Working
    enhancement in ID
    Enhanced Receiver Determination:
    You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    Enhanced (Mapping-Based) Interface Determination
    In an enhanced interface determination you do not enter the inbound interfaces manually, but instead first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
    You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
    http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    Thanks

  • Interface Mapping for enhanced Receiver Determ. in Integration Scenario

    Hi guys,
    Defining Integration scenario is a pleasant way working with XI.
    But how to define the step "enhanced receiver determination" via message mapping in a scenario?
    has anybody come along to this issue?
    Kind regards
    Jochen

    hi,
       You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
    A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
    http://www.****************/Tutorials/XI/RecvDetermination/Enhancement.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    Edited by: murali krishna on Sep 1, 2008 5:49 PM
    Edited by: murali krishna on Sep 1, 2008 6:03 PM

  • Problem with Enhanced Receiver Determination

    Hi Friends,
    I am doing the enhanced receiver determination scenario,  But it is giving the
    error in SXMB_MONI like this
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Identification
      -->
    - <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 while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error when determining the receiver: Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Problem while determining receivers using interface mapping: Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 Fehler beim Parsen der Empfänger-Liste.Länge des XML-Dokuments 264 System expected the element 'Receivers'</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    this is error is coming in the SXMB_MONI
    THE DATA type(Receivers) we create in basis component is comes automatically?
    are we have to create?
    in my scenario i creted manually,
    is it compulsory to specify the properties for the party and agency?
    is it compulsory to create 2 Receiver structures in msg structure?
    if yes what r those, actually i used from sap.help.com,
    Can any body should give me the solution for this, regarding mapping and configuration , if anybody experienced this scenario. Pls . give me  the guidelines to do.

    Hi,
    the mapping creating the receiver list is not producing the required element "Receivers" from Namespace "'http://sap.com/xi/XI/System". Look to the operation mapping given in the enhance Receiver Determination (IB Directory)  and detect the corresponding mapping program (ESR).  Copy the source payload from MONI, test the mapping program and correct it.
    Regards,
    Udo

  • PI 7.1 - Parameter in enhanced receiver determination

    Hello experts,
    I am working on PI 7.1.
    I defined a scenario where I am using an enhanced Receiver determination to determine the list of target services thanks to an operation mapping and its related message mapping. I'd like to pass a constant value from this receiver determination to use it in the message mapping.
    To do so, I set an import parameter in the operation mapping and the message mapping and made the needed binding.
    I can then see this parameter in the receiver determination, but I can not put a constant value in it and then activate my configuration..
    Do you know why ?

    Hi
    I have not used this feature yet, however I dont think that this is a bug.
    the Parameterized mapping feature is for ID->OM->MM & not for RD.
    more info
    http://help.sap.com/saphelp_nwpi71/helpdata/en/43/bbb7fd90f5332ee10000000a11466f/frameset.htm
    /people/jin.shin/blog/2008/02/14/sap-pi-71-mapping-enhancements-series-parameterized-message-mappings
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/909e33f0-738c-2a10-4f87-ce73398bcf08
    Regards
    Vishnu

  • Can I Using Enhance Receiver Determination?

    Hi,
    Can I used Enhanced Receiver Determination to push data to Receiver 2 , based on the response coming from Receiver 1 ( a BPM that that has a synchronous send step and fetches response from SAP through a proxy) ? If yes, how ?
    thanks & regards,
    XA

    We can have just a send step and for that send step we can configure a condition based receiver Determination right?
    yeah correct
    > and Can you throw some light on how to deal with queues, in case if the response doesnt come from SAP to PI due to some reason, which can happen in real time?
    it will thhrow time out exception or message expired exception, if you want to do exception handling do it accrodingly using Control step.
    Regards,
    Raj

  • 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 and value mapping

    I want to use enhanced receiver determination functionality in my scenario.
    I couldn't see any message interface or data type under http://sap.com/xi/XI/System.
    we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.
    I don't want to hard code my business service name in mapping.How can I achieve this?
    Thanks,
    Rekha.
    Message was edited by:
            Rekha Lather

    Hi,
    ><i> couldn't see any message interface or data type under http://sap.com/xi/XI/System.
    we are on Sp08 nw04s and SAP BASIS 7.0 software component in IR.</i>
    After upgradation to SP08 on NW04s , did you reimport the SAP BASIS Component into your IR? Ask your basis admin team to reimport the SAP basis Component into the IR.
    ><i>I don't want to hard code my business service name in mapping.How can I achieve this?</i>
    Similar discussion available in the comments section of this blog,
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
    Would suggest you use value Mapping.
    Regards
    Bhavesh

  • Problem while determining receivers in enhanced receiver determination

    i am doing scenario FILE-TO-FILE (with one sender and 2 receivers, dynamic receiver identification based on mapping)using enhanced receiver determination,
    it is giving following error in MONI,
    <b>Problem while determining receivers using interface mapping
    System expected the element 'Receivers'</b>
    pls. help me if anybody experienced this scenario,
    i am doing  this scenario based on the below blog.
    /people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16

    Have u properly followed the weblog,
    Integration Repository Step No 2 and Step No 5
    <i>2. </i><i>In order to use the enhanced receiver determination, create a message mapping which has the target message as “Receiver Determination” in the SAP BASIS --> http://sap.com/xi/XI/System.</i>
    <i>5. Create the Interface Mapping </i>
    U must have checked that ur Xi is on SP 16 or above )
    Regards,
    Prateek

Maybe you are looking for