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

Similar Messages

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

  • 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

    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.

  • 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

  • File to RFC scenario - receiver determination problems

    Hi ,
    Im trying to work out a flat file to RFC scenario, and am facing problems in configuring the receiver determination .
    While creating my receiver determination, in the configured receivers, when i click on the F4 help to select service, i do not see the business system that i configured in SLD .
    This system i have configured as an WAS ABAP system and provided all relevant data. I can also import objects from this system into IR, so i dont think i have set it up wrongly. I have also created RFC destination .
    Is there some setting that has to be made that im missing ? Could somebody point out why im not able to see this system in the list of business services available at receiver configuration time ?
    Thanks,
    Joe
    I also cleared the SLD cache by the way.. that didnt work either .
    Message was edited by:
            Joe Stein

    Thanks a lot for you replies guys , but problems still not solved ;
    1. I looked at the blog given and ive done everything pretty much as given . My problem lies in not finding the business system itself  in the list of services for the configured receiver. How to implement this has not been shown in the blog.
    2. I tried refreshing the cache and checking again, but it still doesnt show me the necessary step.
    SOS !
    I checked in the inbound system , and found that an RFC wasnt created for the XI system . I created that but i still cant see this system as a business system when i try to create the receiver determination . Do i need to recreate the technical system in the landscape to incorporate this change ?
    Any pointers at all ??
    Message was edited by:
            Joe Stein

  • Regarding receiver determination problem in IDOC-XI-XML file scenario

    Dear All ,
    In IDOC-XI-xml file scenario , I have configured SLD , IR . But in ID , after file adapter , reciever agreement configuration when I am doing receiver determination configuration I am not able to insert mapping program in configuration overview of receiver determination as I am not getting "New Specific" option in mapping .
    Can anybody suggest what could be the reason behind this .
    Thanks in Advance
    Prabhat

    Hi PRabhat,
    In RCVR determination, you need to select the party & service (as appropriate) save the obeject
    then refresh the configuration overview of recr det.
    then you can see the partner/service
    then you can open it & add the necessary objects.
    Regards
    Vishnu

  • Configuration Scenario Builder - Receiver Determination Problem.

    Hi  I am Follows  configurates Integration Scenario to SRM-SUS scenario in XI
    In Model Configuration.  when I try create Object Bottom in Simulation Process .  generate the report show the next message for
    Component View Connection
    Receiver Determination light yellow color  SRD_009 | PurchaseOrderRequest_out
    Analisys ; Requiered Communication Component | SRD_009
                    a receiver determination was found for connection
                    Reciever are missing in the receiver determination found
    Results ;  the reuse receiver determination is already assigned to the configuration scenario
                   the missing receivers were inserted into receiver determination found
                   added receiver communication component SRD_008
    Notes;      Check the conditions for all receivers of the receiver determination. the default result value for the generated condition
                    is TRUE:
    thanks.

    Hi,
    Please verify letter by letter if you haven't make a typo here:
    Default Interface Namespace -- http://mtf
    Default Interface Name -- mtf_mi1
    please also make a test of your scenario in integration directory
    please also do not use best efort quality of service
    /wg
    Message was edited by:
            Wojciech Gasiorowski

  • File2file Receiver Determination Problem

    Hi All,
             I am doing File2file my IR part is activated in ID part I creater 2 CC in Business Service sender with FCC and Receiver with Normal XMLfile after this step Iam trying to create my Receiver Determination Its showing that NO OBJECTS FOUND in interface and Namesapce column.
    Regards,
    Eswar.

    In case your doubt is still not cleared:
    When you create Receiver Determination (ID --> New --> receiver Dtermination), in the pop-up window you select the Sender Business Service and the corresponding Sender Message/ Service Interface .....now this message interrface should be first assigned to the Business Service.....now after we create the RD, we enter the corresponding Receiver Service/ System thereby creating the first relationship between the Sender and Receiver Service/ System in XI/ PI.
    The above selection holds true for any scenario developed in XI/ PI.
    Regards,
    Abhishek.

  • Webservice to file (receiver determination problem)

    Hi ...
        I am doing webserive to file scenario in PI7.0 server. I have completed doing the scenario. But there is a problem in receiver side. In SXMB_MONI it is showing the below error.
    <?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</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>N</SAP:Retry>
      </SAP:Error>
    Could you please help me out in this.

    hi,
    When you have used the WSDL wizard in the Integration Directory and have clicked on "Propose URL" in the second screen, did you ever wonder, why the URL does not point to a sender SOAP adapter channel, it is the URL of the Integration Server instead?
    When you want to use the inbound channel of the Integration Server, you have to use following URL for the web service client:
    http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
    The namespace must be written with escaped characters. (%5E stands for "^")
    Note: The WSDL wizard creates an address with the escape sequence &amp; instead of &. Some SOAP clients (for example XPLSpy) do not automatically restore the character and you have to do this manually.
    By default the SOAP call is treated as a synchronous call. If you want an asynchronous call, you have to add &QualityOfService=ExactlyOnce to the URL.
    Additionally your web service client must provide the HTTP header parameter "SOAP action" = http://sap.com/xi/WebService/soap1.1
    The Web Service Wizard of the Integration Repository creates a WSDL concerning this URL and this SOAP action automatically. Only for asynchronous calls you need to change the URL inside the WSDL file with an editor and add &QualityOfService=ExactlyOnce.
    Advantage
    When you send SOAP messages directly to the Integration Server, you reduce the message load on the adapter engine. This can improve the performance.
    Restrictions
    The SOAP inbound channel of the Integration Server does not support attachments. SOAP messages with content type "multipart" are rejected.
    Hint
    For testing purpose it is possible to add logon data directly to the URL. The parameters are the same as in the HTTP sender adapter: &sap-user=<username>&sap-password=<password>
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    regards
    chandra

  • Receiver Determination Problem In Mail to File Scenario.

    Hi All,
    I am trying to do Mail to File Scenario. I defined two business systems, one s/w component in SLD and in IR I defined a DataType , MessageType and Two MessageInterfaces. In ID these are mail adapter settings I gave :-
    Message Protocol :- POP3
    Message Protocol :- XIPAYLOAD
    MAIL ATTRIBUTES -- Enabled checkbox for "Use Mail Package"
                                    Content Encoding - "base64"
                                    Enabled checkbox for "Keep Attachments"
    DEFAULT XI PARAMTERS --
                                    Default Interface Namespace -- http://mtf
                                    Default Interface Name         --  mtf_mi1
    And in Modules Tab I also defined the "PayloadSwapBean" module and swap.keyName and swap.keyValue.
    Infact I followed all the steps specified in /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step
    But in SXMB_MONI this is the error I am getting :-
      <b><?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="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</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>N</SAP:Retry>
      </SAP:Error></b>
    Please help me out.
    Thanks All,
    Madhu.

    Hi,
    Please verify letter by letter if you haven't make a typo here:
    Default Interface Namespace -- http://mtf
    Default Interface Name -- mtf_mi1
    please also make a test of your scenario in integration directory
    please also do not use best efort quality of service
    /wg
    Message was edited by:
            Wojciech Gasiorowski

  • RFC to WebService Receiver Determination Problem

    Hi,
      I am doing RFC to WebService with the help of this weblog
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2  In  Interface Determination - when picking  Inbound interface is coming as No objects found.
      How to resolve it?
    regards,
    Ansar.

    Ansar,
             In RFC to Web service the inbound interface should be the WSDL.
    Did you import WSDL under 'External Definations'.
    After importing you need to create a inbound message interface of the Message within the WSDL that you need to use.
    Regards,
    Ashish
    Message was edited by:
            Ashish Goyal

Maybe you are looking for