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.

Similar Messages

  • 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

  • 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

  • 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

  • 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

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

  • 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

  • Receiver determination - Xpath expression problem with count

    I am working with a scenario where I pick up records from a JDBC connection and if the number of records I pick up is less than a certain number I want to call a webservice.  If it is greater than the number I want to write out a file to be processed by a different process on the receiving end.  I have created the receiver determination condition with the following conditions:
    (/p1:MT_HOG_Data/row[count(row) > 3] EX)
    (/p1:MT_HOG_Data/row[count(row) <= 3] EX)
    The integration is always processing the second condition no matter how many records come in.  I have tried with and without the multiline option.  Can anyone help with this?
    I have searched through the forum and checked the following links without any resolution:
    http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/13bf7191e73a4fb3560e767a2525fd/frameset.htm
    /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
    I can't find any examples where a count of records is checked in the expression editor.  Thanks in advance for any help.

    You can not use the EX operator in that case, because that is used only for node existence checks, not for value checks.
    Do you have a row number in your structure ? Then you could write the xpath expression with that counter tag and value
    Example: you want to send to receiver A if count > 3, else to B:
    you set  /rowNumber EQUAL 4 for sender A
    and /rowNumber NOT EQUAL 4 for sender B
    The condition is applied to the whole document. If one of the node/values are true for that condition, then the whole condition is set to true.
    Problem with that is that the second condition also will be true because nodes for that condition will be found
    better would be to have a rowcount tag in the structure. If that is not possible, you can use the "Enhanced Receiver determination" where you can define a mapping which determines the receivers. There you can do anything complicated you want.
    CSY

  • 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

  • "Problem evaluating a condition" at Receiver Determination

    Hi,
    I've created a complex mail to rfc interface, in which, message is being send as mail attachment  and service inbound interface has multiple operations (each for corresponding rfc).
    at Receiver Determination, rule was created with multiple conditions, in order to determine correct "Communication Component" (multiple receiver agreement and  interface determination were created to supported this "multi interfaces" scenario).
    If no receiver was found message is ignored.
    once in a while, bad non-xml messages (e.g., "asdfasdfasdfffdfdsasdf") are being send,  is this case, while PI is trying to determining the receiver (i.e., evaluate Receiver Determination conditions) exception is being thrown, message is therefor has system error status* (at sxmb_moni) and it can not be ignored (as i wanted it to be).
    how can i workaround this problematic scenario?
    Regards
    Uri
    *Error message (sxmb_moni)
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Determination
      -->
    - <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 evaluating a condition: An exception has occurred.</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Abhishek,
    10x for your replay, but as far as i understand this is exactly the case here.
    conditions are:
    cond1: (/rfc: RFC1 ~ *)
    cond2: (/rfc: RFC2 ~ *)
    this works as expected in cases of xml messages (in case no cond is satisfied) message is ignored. but, in case of non-xml message exception is being thrown while cond is assessed.
    Regards
    Uri

  • 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

  • Problems with Receiver Determination

    Hi everybody.
    I have started as XI developer 2 weeks ago.
    I'm trying to replicate de tbit40 exercises in our company system. when i try to make the 'Receiver Determination' somethings happen. It doesn't appear the part to write the system receiver.
    This is my scenario : file->XI->IDOC.
    I've defined in the SLD the hardware, including one PC, the XI server and the SAP 4.6c server.
    This is only a test in order to check the connectivity between the PC and SAP R3. I haven't configured yet the part of the IDOC in the R3 system. Is this necesary to view the 'subwindow' of system receiver?
    Thanks.

    Hi everybody,
    I'm having some problems with the sender agreement and the receiver determination, let me explain you the scenario: i'm trying to translate inbound plain text files to XML to a outbound interface for MDM.
    An XI consultant (expertise) has successfully created the inbound - outbound interface mappings for vendors catalog, it has worked good since he set it up, but now that i'm trying to create the materials mapping according to the manuals step by step, and when i try to create the receiver determination settings, i can't find my interface mappings, the pop-up window return 0 objects for interface mappings (that i have already created and linked with msg types).
    So what can i do? Do you have any idea?
    Regards.
    Gerardo.

Maybe you are looking for