How enhanced receiver determination works..?

hi all,
In enhanced receiver determination Interface mapping(which has java mapping) I have also included logic to make some change in content of input file and dynamic configuration for output file name. My input and output are flat files. So I m using dummy structure. In interface determination i m not referring any Interface mapping.
Receiver determination is working properly But neither dynamic file name nor the changes in content of file are reflecting in out put file.
Is it mandatory to use separate mapping in interface determination to change the content of file and dynamic file name?
Thanks
Jai
Edited by: Jaideep Baid on May 29, 2010 6:27 PM

Is it mandatory to use separate mapping in interface determination to change the content of file and dynamic file name?
The mapping used to in receiver Determination is to decide the Receiver.....the mapping used in Interface Determination is to create the target structure....both are to be developed and used separately (one in Receiver Determination and other in Interface Determination respectively)....this wiki gives you an example:
http://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
Regards,
Abhishek.

Similar Messages

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

  • 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

  • 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

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

  • Enhanced Receiver Determination with RFC Lookup

    Hi All,
    I am building an interface with Enhanced Receiver Determination. Scenario would be that the Receiver Systems would be stored in a Z table in SAP ECC, and in PI Receiver Determination I am doing an RFC look up to find the systems, and using those.
    I built the mapping for Receiver Determination, and it tested fine in ESR. But while Creating the Receiver Determination in Integration Directory, After I specify the Receiver mapping name, and put the RFC channel name for the RFC parameter, it doesnt allow me to save the Receiver Agreement with a run time error message
    "Link from Receiver Determination  | <Sender>| <Interface>| * | * to object type "Channel" with role "122474913b1311deaadb42057dd8b002" is not permitted"
    My question is a) if the RFC lookup allowed in the mapping for Receiver Determination?
    B) if yes, am I missing someting or is it a system issue?

    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.

  • 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

  • Problem in enhanced receiver determination

    hi all
          I was doing enhanced receiver determination in that i got following problem
    at first i copied  abstract interface ReceiverDetermination from SAP BASIS to my component then i created my mapping program containing one udf related to my scenario.I also created one interface mapping but when i went in the directory then
    my this mapping is not coming when i have to choose it after clicking to extended receiver determination in receiver determination.
    my objects are already activated in design.the udf is also working properly.
    Please reply. This is an urgent issue.

    Hi-
    Check this link
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm

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

  • Error in enhanced receiver determination

    Hi Experts,
    I am trying to implement a scenario in which  i have to get the receivers at run time by doing a  lookup to a file which stores the destinations.
    i am getting the error that no receivers could be determined.
    thanks,
    Anika

    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.

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

  • 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

Maybe you are looking for