Problem configured users in receiver determination

I am configuring idoc to proxy. My scenario is working fine without condition RCVPRN  SR4CLNTDRY . But if i give condtion it is showing this error in runtime workbench
Error Category
IDOC_ADAPTER 
Error Code  
ATTRIBUTE_INV_SND_SERV
bye

Check the point no 5:
Troubleshooting  File-to-IDOC Scenario in XI.
chirag

Similar Messages

  • Receiver Determination - Configuration Overview for Receiver Determination

    Hi All,
    I was trying on some tutorial for Calling RFC(sender) and creating a File at Receiver site.
    I've configured all the required setting at the Design: Integration Builder.
    As for Configuration: Integration Builder. Until the Step where I required to setup the Receiver Determination, there is this part "Configuration Overview for Receiver Determination". where i have to maintain the "Receiver Service", else i will hit this error "Enter the receiver service".
    The steps which i followed was :
    1. Create 2 Communication Channel for Sender/Receiver in the Business System.
    2. Create a Sender agreement.
    3. Create a Receiver agreement.
    4. Create a Interface determination.
    5. Lastly "Configure the Overview for Receiver Determination"  for   Receiver Determination
    The problem which I'm facing now is I have nothing in the "Configure the Overview for Receiver Determination" at all even i have created the sender/receiver agreement and interface determination.
    While some troubleshooting, under the If No Receiver Is Found, Proceed as Follows: I tried choosing the "Continue Message Processing with the Following Receiver" radio button and choose the Receiver for the Service then hit the save button.
    The error "Enter the receiver service". pop up but now, the Receiver service was shown under the "Configure the Overview for Receiver Determination". When i try choosing back the "Terminate Message Processing with Error (Restart Possible) and hit the Save button. The Receiver service goes missing again.
    Any Idea what happen ? or anything i missed out ? thanks in advance.

    Hello
    Check if you have the issue in the kba #1538009 Error When Executing Open - Object not found.
    Also see note #1466011 Usability Improvements in Directory:
    o Don't show deleted objects in navigation tree
    When you delete an object in Directory the link to this object is not
    automatically deleted from Configuration Scenario. You need to manually
    open every scenario and remove such 'broken' link. In scenario editor
    broken links are displayed in grey font and therefore can be easily
    identified. Unfortunately the navigation tree in 7.1 (in contrast to
    XI3.0) doesn't make difference between existing and broken links and
    shows them as they all leads to existing objects.
    Regards
    Mark

  • 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

  • Problem in receiver rule of configured receivers in receiver determination

    Hi, Experts!
    Can anyone please help me with an issue regarding the receiver determination part of IB? I currently have 2 different receiver rules, each having a different condition but under the same communication component. When I check the message status in the runtime workbench however, both rules are considered and thus 2 messages are sent instead of just 1 from the selection. Please help me send the message according to the selected interface. Thanks!

    Hi Brent,
    You may write the rule as follows:
    if (Receiver='CHDB') OR (Receiver='CIF') then send the incoming message to the relevant Receiver Business Component/System.
    You may use the X Path editor for configuring this rule in the Content based Receiver Determination of your scenario.
    I hope this will help.
    Regards, Gaurav

  • Receiver Determination, Configure Receivers, Condition configuration alert

    Hello Colleagues,
    when i try to configure condition area under Configured Receivers at Receiver Determination i get following notification:
    Message Interface does not exist in any software components installed on this business system.
    Could tell me someone where is the problem?
    Many thanks in advanced!
    Regards,
    Jochen

    > Hi Krishna,
    >
    > the message type "INTERNAL_ORDER.INTERNAL_ORDER01"
    > exist under Software Componenten Version\Imported
    > Objects\IDocs at IR and is activated.
    >
    > Regards,
    >
    > Jochen
    Under which SWCV it exists in IR?
    As pointed by Bhavesh, you have to add the product that contains this SWCV to Technical System which contains the Business System you're trying to use that interface with. It's done in SLD.
    When you select the product, make sure you mark the proper SWCV in the left panel, then save it. It'll be added to that Technical System. But you still need to go into the specific Business System and select that SWCV, in order to properly associate it to the BS.
    In the future, as a project best practice, make sure you follow these steps b4 starting IR/ID development.
    1. define your project SLD (Technical/Business Systems);
    2. create/import the Products/SWCVs you're going to work with;
    3. associate the Products/SWCVs to the relevant Technical/Business Systems in SLD.
    Regards,
    Henrique.

  • 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

  • Integration Process Receiver Determination Step

    Hi experts,
    May I know whether the "Receiver Determination Step" (in  Integration Process) that collects the list of receivers configured, can be used only to find list of asynchronous receivers?
    Can't we use this "Receiver Determination Step" in synchronous scenario? If yes, may i know how to?
    Thank you!
    Best Regards,
    Saravanan

    Thank you Gaurav!
    I can understand we can use multi-casting.
    To clearly put my scenario, I have to use synchronous send (so cannot split send and receive step, and so no need of correlation) in my BPM, which have to synchronously send (and so it receives within same step) message to multiple receivers. This is the reason I am trying to use receiver determination step first and in a loop trying to synchronously send message to each receiver and receiving response.
    Now my problem is in the receiver determination step, it is not identifying any of the receivers configured in the integration directory. The receiver determination list returns empty.
    So, I want to know whether this receiver determination step is only for async receivers or synchronous receivers also.
    Best Regards,
    Saravanan N

  • ACK for receiver determination with 2 interface determination

    Hi Forum,
    I have a XI scenario, with a BPM, where i have a Send step,
    this send step corrsponds to a receiver determination in Configuration,  and this receiver determination has 2 interface determination,
    because the send step is like,
    BPM to Receiver1, through sender message interface MI_Sender1, but there are 2 different receiver message interface namely MI_receiver1, and MI_receiver2,
    .......hence 2 interface determination and 2 interface mappings accordingly,
    and now when in BPM, i choose "transport acknowledgement" for this send step, my BPM stucks while waiting for the acknowledgement, but...in MONI, i am receivng both the acknowledgement, but in PE, workflow descrition, it waits for acknowledgement and finally fails,
    what's the reason,

    check the workitems of both sender/receiver (ack) in moni (problem might be in BPM config).

  • 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

  • Unable to find the Message Interface Receiver Determination

    Hi Everyone,
    I am unable to find the Message Interface Receiver Determination in the SAP BASIS 7.0 --> http://sap.com/xi/XI/System. in IR.
    I am using P.I 7.0 SP 15
    Could anyone let me know what could be the problem.
    Regards,
    Varun

    Hi Sridhar,
    I cant find the Message Interface Receiver Determination in IR under the standard SWCV SAP BASIS 7.0 and under the namespace http://sap.com/xi/XI/System. in IR.This Message Interface will be useful while configuring in enhanced Receiver Determination.
    http://help.sap.com/saphelp_nw2004s/helpdata/EN/84/e8763c997fda50e10000000a11405a/frameset.htm
    Regards,
    Varun

  • Receiver determination step in BPM

    Hi, I have open a topic about BLOCK in BPM, as this link
    Re: question on BLOCK in BPM
    I descript the symptom in it, you can have a look.
    But now I find that the problem is due to receiver determination step in BPM, not block.
    So I think I'd better post it as a new topic.
    Are there anyone familiar with the receiver determination step in BPM, or know how to correctly use receiver determination step in BPM. Specially the 'send context', how to set it and how to combine it in Integration Directory.
    Thanks a lot

    You use the send context to specify a condition in your recevier determination. If your BPM flow sends the same message type in different send steps to different destinations you can specify some unique text like "R3" or "LEGACY" in the send context of your send step. Then in the receiver determination you can specify a condition that says Process Step = "R3" send to R3 "Process Step="LEGACY" send to legacy system.
    Hope that helps.
    Regards,
    Jitendra

  • 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

  • My wife had an iPad for a year and synced to our computer with no problem.  I recently received an ipad2 and when I tried to sync using separate apple and iTunes passwords, under her computer user name, it appears I over-road her account and synced all he

    My wife had an iPad for a year and synced to our computer with no problem.  I recently received an ipad2 and when I tried to sync using separate apple and iTunes passwords, under her computer user name, it appears I over-road her account and synced all her apps with my apps on my iPad.  I then set myself up as a new user on our computer and tried to sync.  I now get the error that my iPad is synced to another library.  How can I start over without erasing all my data on the iPad?

    Go back to her login.  Unless you deliberately erased apps, they should all be there, both yours and hers!  Then, you need to set up each iPad separately.  You will notice that they have separate names for that very purpose.
    There is no problem with multiple Apple IDs on the same iTunes on the same computer except...  Apps are permanently associated with the ID that was originally used to obtain them.  If you choose to update an app from inside iTunes and you're logged into the "wrong" ID, you must log out and back in again.
    On the bright side, you can configure either or both iPads to sync with apps and music and movies, etc. from either or both IDs.  Further, if you choose to update the apps from the iPads themselves, there is no need to log out/in.  The device handles that.  All you need is the correct password.  In my case, I use the same password for both IDs to make things easier.

  • Configuring receiver determination with multiple messages in BPM

    I am configuring a BPM scenario which uses 3 abstract interfaces, one for receiving, 2 for sending. I need 2 abstract interfaces while sending because they use different message types. I have created a Receiver Determination for the 1st interface, but the problem is that when I try to create the second Receiver Determination the 2nd abstract interface is not listed after I select the Integration Process. Just the 1st interface is listed under the Integration Process. What might be the problem?

    Did you try to delete and reimport the BPM with the same name ?
    SKM

  • 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

Maybe you are looking for