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

Similar Messages

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

  • Intermittent JDBC error in Enhanced Receiver Determination

    Hi,
    I have an interface that use Enhanced Receiver Determination in PI 7.1 EHP1.
    The database is DB2 on i5/os 6.1
    Sometimes message ends in error :Error when determining the receiver: Problem while determining receivers using interface mapping: Runtime exception occurred during application mapping com/sap/xi/tf/_HI01_to_ReceiverDetermination_;
    But the same message with same values is successfull earlier.
    This is not a design problem; the interface is working well 95% of the time.
    I found some JDBC error in NWA java logs:
    Error in sax handler parsing request: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.
    Error when calling an adapter by using the communication channel CC_RECEIVER_JDBC_PIDB2 (Party: *, Service: INTEGRATION_SERVER_PX1, Object ID: cb7ea38fb2ac3a06b12d79f5ade2bcf7) XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
    Thrown:
    com.sap.aii.af.service.api.AFException: XI AF API call failed. Module exception: (No information available). Cause Exception: 'Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): java.sql.SQLException: [SQL0104] Token "BUSINESS_SYSTEM" was not valid. Valid tokens: FOR SKIP WITH FETCH ORDER UNION EXCEPT OPTIMIZE.'.
    at com.sap.aii.af.service.api.AdapterAccess.sendMsg(AdapterAccess.java:214)
    at com.sap.aii.af.service.api.AdapterAccess.execute(AdapterAccess.java:283)
    at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.execute(AdapterProxyLocal.java:119)
    at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.execute(SystemAccessorInternal.java:76)
    at com.sap.aii.mapping.lookup.DataBaseAccessor.execute(DataBaseAccessor.java:74)
    at com.sap.aii.mappingtool.flib7.SelectSingle.selectSingle(SelectSingle.java:54)
    at sun.reflect.GeneratedMethodAccessor607.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:592)
    Any idea? Can high volume cause the JDBC Receiver to fail?
    Martin

    hi,
    you r trying to impliment Lookup for the file adapter which is not synch in nature and hance u r not getting the responce back.
    please find the link which deals with how to impliment lookup for file adapter.
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/file%252blookup%252bin%252budf.
    now once u get rhe runtime receiver u can perform enhanced receiver determination (write a simple UDF)
    regards,
    navneet.

  • 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

  • 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

  • Enhanced receiver determination

    why we assign the abstract message interface ReceiverDetermination as the target interface.can we achieve enhanced receiver determination without this abstract interface.I have gone through sap help and some blocks of sdn also but still its not clear to me that whats the role of this abstract interface.

    Hi
    For receiver determination::- See
    http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
    About
    Abstract Interface :
    The abstract interface work both inbound and outbound interface(Bi directional).
    BPM can process messages only through "abstract interfaces" al though Receive and Send steps can have interfaces other then "abstract interfaces"  all other intermediat steps of BPM needs "abstract interfaces"
    Hope it helps
    regards
    Piyush

  • 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

  • Enhanced Receiver determination - Fatal Error.

    Hi All,
    We are using Enhanced Receiver Determination.
    We are getting Fatal error in SXMB_MONI though our Intarface mapping is working correctly but when tried testing from runtime work bench we are getting error.
    The error message shows
    SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
      <SAP:P1>Problem when determining the receiver when using the Interface Mapping: During the application mapping com/sap/xi/tf/_Find_Receiver_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
    Please suggest any setting needs to be done.
    Thanks
    Regards,
    Ashwin

    Hi Ashwin,
    Just check if the condtion is correct. Also, look for some typo error as the name is case sensitive.
    Also, trigger a delta cache refresh for this receiver determination object after modifying the object.
    This should solve your problem.
    Regards, Gaurav.

  • Enhanced Receiver Determination & Prioritize Queues

    Hi experts,
    In the SXMSQUEUE transaction i've customized the filters necessary to assign an message interface type in low-priority queues. On the other hand, I use the object as Enhanced Receiver Determination, ie use an operation mapping to determine the receivers.
    (A) In this way, determines the following types of queue:
    Inbound Queue: XBQ9... <<< Low priority Queue
    Outbound Queue: XBQO... <<< Standard Queue
    (B) If instead of using the Enhanced Receiver Determination I use the standard Receiver Determination, determines the following types of queue:
    Inbound Queue: XBQ9... <<< Low priority Queue
    Outbound Queue: XBQZ... <<< Low priority Queue
    I hope the results are in option B, but I'm forced to use Enhanced Receiver Determination (A).
    Version PI: 7.1 SP 7
    Any idea?
    Thanks,
    Jose.

    Hi experts,
    In the SXMSQUEUE transaction i've customized the filters necessary to assign an message interface type in low-priority queues. On the other hand, I use the object as Enhanced Receiver Determination, ie use an operation mapping to determine the receivers.
    (A) In this way, determines the following types of queue:
    Inbound Queue: XBQ9... <<< Low priority Queue
    Outbound Queue: XBQO... <<< Standard Queue
    (B) If instead of using the Enhanced Receiver Determination I use the standard Receiver Determination, determines the following types of queue:
    Inbound Queue: XBQ9... <<< Low priority Queue
    Outbound Queue: XBQZ... <<< Low priority Queue
    I hope the results are in option B, but I'm forced to use Enhanced Receiver Determination (A).
    Version PI: 7.1 SP 7
    Any idea?
    Thanks,
    Jose.

  • 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

  • Enhanced Receiver Determination - Hard-coded Receivers??

    Hi mates,
    I need to implment enhanced receiver determination. I see from the documentation and blogs that I need to hard-code the receiver service i.e. specifying the value in message mapping.
    What happens if I transport this mapping program to QA or PROD system? Do I need to take care of the Receiver system names in QA & PROD in the mapping.
    Isnt it hard-coding?
    Is there any better way of doing this, apart from using the BPM.
    I appreciate your inputs.
    thx in adv
    praveen

    Hi,
    If you are using enhanced receiver determination, you are going to provide Receiver Details in the Integration Directory right ? If so, anyway while doing Transport from the Dev to QA, you are creating a Transport Target for the business systems.. So here in the configuration it will take care ...
    http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
    But, I am not sure where are you refering about  Hard-Coding ?
    Rgds,
    moorthy

  • 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

  • Enhanced Receiver determination - for Integration Process

    Hi,
    Just wanted to confirm that if it is possible to have more than one Receivers, with Enhanced Receiver Determination and one of the Receiver happens to be Integration Process. I know with Enhanced Receiver Determinations you can find more than one Receivers at Run time, however the key question is, if in addition to normal Receiver Systems (like SAP R/3 or Web Services etc), if we can also kickoff Integration Process within Enhanced Receiver Determination.
    Thanking in advance.

    as said by Udo Martens
    Assumedly the different receivers are using different Inbound Interfaces (a BP is using an Abstract Interface). Therefore you would need for each different receiver a own Interface Determination referring a own mapping.
    refer this wiki  http://wiki.sdn.sap.com/wiki/pages/pointstab/viewpageversion.action?pageId=131760630&version=5 to Know how to  configure Enhanced receiver determination  and Interface determination for each receiver .
    In your case one of the receiver will be Integration process

  • 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

Maybe you are looking for

  • How can I read my incoming emails in one folder?Like I do in Live mail and Outlook express.

    Now we can only read emails in different folders if I am managing multiple email accounts. It does not feel so comfortable as we use Live mail and Outlook express.

  • RuntimeException in Message-Mapping transformatio

    Hi all, My XI server is successfully picking up a comma separated file from an FTP server and generating the corresponding XML: <?xml version="1.0" encoding="utf-8" ?> <ns:CondRec_MT xmlns:ns="http://namespace-ConditionRecords"> <Recordset> <Conditio

  • IC webclient organisational data determination

    Dear Experts, We are using CRM 5.0 IC webclient We start with the identify account screen to select the business partner. The business partner may potentially belong to 5 different sales areas. After confirming the BP, I go to the complaint creation

  • How can I see previously ViewNX2-edited photos (raw) in Lightroom 3?

    I recently bought Lightroom 3, and after importing my previously ViewNX 2-edited photos (in RAW, NEF), I saw that Lightroom doesn't show those changes. I can only see the photos in its original form. Is there a way to import them to Lightroom 3 and s

  • Payment with Boleto Bancario - Brazil

    Dear SAP experts, Do you know if for payments with Boleto in Brazil, there is a fixed length for the boleto codification? I know that the boleto should be inserted in bank reference fields in AP lline (invoice)..but what about the boleto's length? Is