Extended Receiver Determination

Hi
I have scenario like this.
Sending order file into SAP through XI
If the order is there in SAP it needs to be send mail along with details of
order else if this is new order then it needs to posted into SAP and create IDOC .I need to use RFC function module which is developed in SAP that returns 0 or 4
If SUBRC=0 then need to send mail as I mentioned above
If SUBRC=4 then need to create Idoc in SAP system.
Note : without BPM - Need a solution
Let me know how to use extened Receiver determination.
Till now I have designed like this:
In the IR :
I have created 3 message mappings for this.
1st one is to decide receiver.
           Source - file
           Target -  Receiver determination (structure - which available in SAP
Basis software componenet)
2nd one is to create IDOc
            Source - file
             Target - Idoc
3rd one is to create mail
            Source - file
            Target - Mail ( External defination)
In ID:
I am using extended receiver determination , their i have given the mapping program which ti determine the receiver.
Next i have created 2 Interface Determinations,Sender as well as Receiver agreements.
Finally Activated all .
While testing i am getting message in the MONI No Receiver agreement found
Could pls help this case.
Cheers
MMV

Hi Mrutynjaya,
Rest all seems to be fine, but are you using 2 sender agreements??? You need only 1 sender agreement,as you have only 1 sender. Correct me if i am wrong.
Regards,
Sanjeev.

Similar Messages

  • Extended receiver determination and Dynamic attributes

    Hello,
    is it possible to access dynamic attributes within an extended receiver determination? Can I modify / set dynamic attributes of an XI message within an UDF in the extended receiver determination mapping?
    In detail: In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions.
    Thanks,
    Chris

    Hi,
    In my scenario I want to use an extended rec. determination, make a lookup in a DB inside the determination in order to define the receiver, and based on the lookup result I want to add some information as dynamic attributes to the XI message, which then can be accessed in the interface determination as conditions - See you can do a DB lookup in a msg mapping........but by the time you have reached msg mapping your receiver determination will be done......so  your receiver is already decided............Extended recever determination is for dynamically choosing a recever based on source msg's data.........
    Regards,
    Rajeev Gupta

  • Error in Extended Receiver Determination

    Hello Experts,
    We are working on a scenario where, we are using Extended Receiver Determination.
    In this reveiver determination mapping we are doing JDBC lookup and some receivers are determined on that basis.
    Also, we have a default receiver in mapping.
    We are using: SAP PO 7.4 SP 7
    We are getting below error while testing from WSnavigator/SOAP UI, but mapping works when we test it in ESR.
    Error:
    <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>
              <context>XIAdapter</context>
              <code>ADAPTER.JAVA_EXCEPTION</code>
              <text><![CDATA[
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.xi.routing.RoutingException: Error while executing receiver determination mapping.
    at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:773)
    at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:530)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
    at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
    Kindly help.

    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.

  • Want to Use Extended Receiver Determination

    Dear All,
    As my last post I came to know that i was using invaild data in input payload so i now have tested with proper data.
    i am getting lot of invaild things in my input like space ,# and all from ECC side in first step of pipeline(Receiver Determination). so thinking to use extended reciver determination so that there i can validate the input paylaod there only..........is this possible
    Plz suggset.....
    Regards
    Abhay Agarwal

    Hi Abhay,
    As i read the all the posts in this thread.. and ur error status is..
    <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">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    <SAP:P1 />
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>No receiver could be determined</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    This problem is not from the mapping which will be in interface determination... also,
    the mapping(interface determination) comes only after the receiver determination...
    So the problem lies in the receiver determination configuration....
    please delete the receiver determination once and recreate it once more(some times due to cache problem's)
    For ur requirement dont create the extended receiver determination...(it's required only when u want to determine the receivers in run time)
    To delete the spaces and special chars...
    u can solve these in mapping,using the stringReplace and trim functions....
    Also i doubt if at all the incoming source XML is proper structure or not... please check once in the SXMB_MONI.. the incoming payload.
    Still some problem... please post the problem in detail .. so that others can also understand..
    Babu

  • Extended Receiver Determination in 7.31 IDApi

    Hi,
    I'm using the 7.31 IDApi to create\change an ICO in 7.31 AEX. Currently this is working fine. However, I also need to create an ICO using the Extended receiver determination but I do not see ay function for this in the existing wsdls that SAP has provided.
    I have also referred to William Li's blogs for IDAPi for this.
    Using PI 7.3’s Directory API
    Could you please let me know if creating an ICO with Extended receviver determination from IDApi is possible and any pointers as to how it can be done would be very helpful.
    Regards

    Hi Shiladitya
    I can see that there is a option for dynamic receiver rule in the receiver determination of ICO.
    You can find the same in
    IntegratedConfigurationCreateChangeIn----> IntegratedConfiguration--->Receivers--->DynamicReceiverRule
    I am in 7.31 dual stack SP 07.

  • 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

  • Extended Receiver Determination option missing

    Hi All,
    In the Receiver Determination the extended receiver determination option is missing. We are on PI 7.0. I would like to know as to which patch level i need to upgrade it to see this option.
    Thanx for all your help in advance
    Regards,
    Abhy

    hi,
    you need to go for: SPS07 which is SP16 in 3.0
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • 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

  • Extended Receiver Determinatipon and Interface Determination?

    Hi,
    Where exactly (In which business cases) we can implement or required Extended Receiver Determination and Interface Determination?
    Thanks,
    Naidu.

    Hi,
    There are only two modes standard and Extended, Enhanced receiver determinatrion is Extended receiver determination only.
    Enhanced(Extended) receiver determination  -->
    Whenever list of receivers is determined dynamically at runtime, using a message mapping then it is called enhanced.
    Enhanced Interface Determination--> It is when you want the target interfaces to be defined dynamically based on the multimapping, that is called enhanced interface determination.
    Refre SAP help for more detail
    http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
    Thanks!
    Edited by: Sudhir Tiwari on Dec 5, 2008 6:34 AM

  • Extended receiver and enhanced interface determination

    Hi,
    Can somebody list me the business cases when we use the extended receiver and enhanced interface determination.In which scenarios we have to use them?
    Where we can use these features and whom they can replace?
    Regards,
    Anoop

    Hi Anoop
    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
    <b>enhanced interface determination</b>
    /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 .
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
    Thanks
    Pls reward if useful

  • Condition check (based on sender file name) at receiver determination step

    Hi,
    My scenario is File to AS2 (Sender side file adapter and receiver side AS2 adapter)
    We have 5 customers, but the source location is same to pick the files, Here we are not using any ESR objects.
    Based on the source file name PI need to determine to whoom this file need to send at receiver determination step
    Craeted objects
    1 Sender CC,
    1 Sender agreement,
    1 Receiver determination
    5 Interface determinations
    5 Receiver agreements
    5 Receiver CCs.
    Could you please provide me your valuable inputs.
    Thanks
    Ramesh

    Hi Venkataramesh,
    I understand your scenario as, picking files (different file naming standard for different target customer) from one source folder. Based on file name, that payload should be sent to corresponding target customer. You have mentioned u201CHere we are not using any ESR objectsu201D. I can see two reasons for this decision
    1. PI is used to route the messages, i.e., no need to transform the payload. OR
    2. Files can binary files like PDF, ZIP, JPG, GIFu2026
    Now I can see two possible solutions
    1.     Simple solution, as proposed by u201CPrabhu Rajesh Janardananu201D, make it into 5 different scenarios  (5 sender channels).
    2.     Bit complex solution, only one sender channel, using extended receiver determination
    Step 1:- In Sender File channel check u201CAdapter u2013 Specific Message Adapteru201D in Advanced tab. File Name should be checked.
    Step 2:- In Receiver Determination, Select Type of Receiver Determination as u201CExtendedu201D. http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a423a8e5430e10000000a42189b/frameset.htm
    Step 3:- Do a Graphical Mapping (use it Operation Mapping in Receiver Determination).
    Step 4:-
    Source and target of graphical mapping will be same (below), because you donu2019t want to access input payload (it can be XML, flat file, JGP, GIF and you donu2019t have its structure).
    <Receivers>
       <Receiver>
          <Party agency="" scheme=""></Party>
          <Service></Service>
       </Receiver>
    </Receivers>
    Step 5:- Write a UDF in Graphical mapping as below. http://help.sap.com/saphelp_nwpi71/helpdata/EN/43/03612cdecc6e76e10000000a422035/frameset.htm Pay attention to method declaration
    public String Determine_Receiver( Container container) throws StreamTransformationException
    DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
    DynamicConfigurationKey key = DynamicConfigurationKey.create(u201Chttp://sap.com/xi/XI/System/Fileu201D,u201CFileNameu201D);
    String valueOld = conf.get(key);
    //Put your logic here
    if (valueOld.equal(u201Cuser1u201D)) {
    return u201Cuser1u201D;}
    if (valueOld.equal(u201Cuser2u201D)) {
    return u201Cuser2u201D;}
    if (valueOld.equal(u201Cuser3u201D)) {
    return u201Cuser3u201D;}
    Step 6: Now use this UDF to map to u201CReceiveru201D and u201C Serviceu201D.
    This solution need more fine tuning.
    Regards,
    Raghu_Vamsee
    Edited by: Raghu Vamsee on Jan 8, 2011 5:56 PM

  • Problem in receiver determination

    hi experts
           I am working on a idoc to file bypass scenario where i am using extended receiver determination ,abap class is being used for abstract interface mapping ,It is working fine with other interfaces.but on a particular idoc its started showing error in sxmb_moni that"Error when determining the receiver: Problem wh
    determining receivers using interface mapping:
    Error in mapping program
    /GLB/CL_ZGTIS_GNERIC_ROUTING (type SAP-ABAP,
    kernel error ID CREATE_OBJECT_CLASS_NOT_FOUND)" so can u tell where is the problem i have crosscheked the abap class very well all entries r right.
    plz update its urgent

    hey i have done a mistake in writing the class name in the mapping ............

  • Alert to Error in Receiver determination mapping

    Hi everyboy.
    Im using a mapping to decide the receiver determination (ReceiverDetermination - http://sap.com/xi/XI/System).
    I can´t configure an alert when the mapping fails.
    How could I do that????
    Thanks a lot

    Hi Christian,
    As per my understanding you are using extended receiver determination by creating an interface mapping in between your outbound interface and standard receiver interface of SAP BASIS.Do you mean to say that if source data doesnot fulfill the condition to determine any receiver.If so, then I believe in SXMB_MONI we can find the error as unable to determine receiver.Since it belongs to mapping so it will be executed in Integration engine.
    create an alert category in ALRTCATDEF
    Define Alert Rule in RWB -> Alert Configuration
    Select the our own Alert Category
    Click to Add Rule and activate the corresponding rule
    Regards,
    Nutan

  • Interface Mapping not listing in the Extended Reciever Determination

    Hi,
    The Interface Mapping is not shown in my Extended receiver determination. I have created and activated the IM & MM using the MT - Receivers within the SAP Basis.
    Regards
    Unni

    Hi,
    You can only choose the Interface mapping for the Enhanced recevier determination in the extended tab of Receiver determination. & I dont see the Interface mapping in the select list.
    Where do I have to check for the proper outbound message???
    Regards

  • 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

Maybe you are looking for