Receiver determination in IDOC

Hi Experts,
For one scenarion of ALE IDOC , i need to determine the receiver system dynamically depending on a value of a segment field.
Can you tell me what configuration is needed for this?
I Appriciate your help.
Regards,
Ashish

Hi Ashish,
couldn't you use the filter definition in your distribution model?
Regards
Bernd

Similar Messages

  • Receiver Determination error -  IDOC TO FILE

    Hi ,
        Scenario :  IDOC TO File
         Error generated while iam doing this scenario. Please help me.
          <?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">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>
    Regards,
    Venubabu.

    Hi
    Check for  sender details . Sender interface must be the IDOC.
    Open SXMB_MONI and check your msg fro the sender system details. They match exactly the details in Receiver Determination.
    Check the Receiver Determination is configured correctly. i.e R/3
    Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
    You can test your configuration with sample
    payload.
    In ID goto to TOOLS -
    > Test Configuration for testing.
    Hope in this way you can still find at which point the interface goes wrong

  • Receiver determination for Split Message - Bulk message handling

    All,
    I have a scenario where MATMAS message is split to multiple receivers via multi mapping 1:n; the split is based on plant specific data, all works fine the mapping splits the message perfectly.
    The problem I have is in configuring the receiver determiniation. I have put conditions based on plant specific data the message should be distributed to the appropriate receiver. At runtime the MATMAS message received is treated as a bulk message and it produces mutiple sub-documents however in my case if the MATMAS has 3 plant specific data the data is send to all the 3 receivers instead of sending just one message per plant to the appropriate receiver.
    Its IDOC to File scenario on XI 3.0, SP20.
    Receiver Determination:
    /MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'xxxx' -> send to XXXX_receiver
    /MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'yyyy' -> send to YYYY_receiver
    Though the receiver determiniation splits the message by plant it could be that a material is maintained for both xxxx and yyyy plants and in this case both should receive the message but the contents would be different. The problem I have is both messages are delivered to both receivers.
    I appreciate those who have taken the time to read the thread and thank you all in advance supporting with advices.
    / Saj

    Please find attached the source xml before transormation used for the xpath that I have indicated in my original message. From the below message E1MARCM-BESKZ differs on each plant and also has a corresponding warehouse view E1MLGNM where for example LHMG1 value differs for each warehouse.
      <?xml version="1.0" encoding="UTF-8" ?>
    - <MATMAS05>
    - <IDOC BEGIN="1">
    - <E1MARAM SEGMENT="1">
      <MSGFN>005</MSGFN>
      <MATNR>000000000001002201</MATNR>
      <MTART>ZFGS</MTART>
      <MATKL>1111003</MATKL>
    - <E1MAKTM SEGMENT="1">
      <MSGFN>005</MSGFN>
      <SPRAS>E</SPRAS>
      <MAKTX>AA Ni-MH Rechargeable Batteries</MAKTX>
      </E1MAKTM>
    - <E1MARCM SEGMENT="1">
      <WERKS>4911</WERKS>
      <BESKZ>F</BESKZ>
      </E1MARCM>
    - <E1MARCM SEGMENT="1">
      <WERKS>4912</WERKS>
      <BESKZ>X</BESKZ>
      </E1MARCM>
    - <E1MARCM SEGMENT="1">
      <WERKS>5020</WERKS>
      <BESKZ>E</BESKZ>
      </E1MARCM>
    - <E1MARMM SEGMENT="1">
      <MEINH>CS</MEINH>
      </E1MARMM>
    - <E1MLGNM SEGMENT="1">
      <LGNUM>020</LGNUM>
      <LHMG1>2020.000</LHMG1>
      <LETY1>E2</LETY1>
      </E1MLGNM>
    - <E1MLGNM SEGMENT="1">
      <LGNUM>023</LGNUM>
      <LHMG1>2323.000</LHMG1>
      <LETY1>E2</LETY1>
      </E1MLGNM>
    - <E1MLGNM SEGMENT="1">
      <LGNUM>024</LGNUM>
      <LHMG1>2424.000</LHMG1>
      <LETY1>E2</LETY1>
      </E1MLGNM>
    - <E1MVKEM SEGMENT="1">
      <VKORG>4900</VKORG>
      <PRAT1>X</PRAT1>
      </E1MVKEM>
    - <E1MVKEM SEGMENT="1">
      <VKORG>5000</VKORG>
      <PRAT1>/</PRAT1>
      </E1MVKEM>
      </E1MARAM>
      </IDOC>
      </MATMAS05>
    so in this example above:
    Receiver 4911 (WERKS) should receive:
    F + 2020 (BESKZ + LHMG1)
    Receiver 4912 (WERKS) should receive:
    F + 2323 (BESKZ + LHMG1)
    Receiver 5020 (WERKS) should receive:
    F + 2424 (BESKZ + LHMG1)
    The problem is all these 3 messages are delivered to all the 3 plants thus making it 9 messages delivered in total as against 3.
    / Saj

  • How to Take source value remove zero and use it In receiver Determination

    Hi
    I am working On IDOc to Soap channel.
    In idoc Fields ,I am using EMPST field from IDOC and accordingly I am putting Condition in Receiver Determination.
    IF EMPST 111 Then Revceive1
    IF EMPST 222 Then Revceive2
    IF EMPST 333 Then Revceive3
    But sometimes values also Come as 000111 or 00111 or 0111 same for Others.
    I have used follwong condition in Receiver Determination.
    IDOC/E1EDK01/EMPST u2248 *111
    But it working fime for leading zero.
    But if values come as 8111 or 78111 it is also routing message to Revceive1.
    same for others.
    Can you plz suggest solution?

    you can use enhanced receiver determination ,, where you can specify your logic in the mapping
    http://wiki.sdn.sap.com/wiki/display/XI/EnhancedReceiverDeterminationinSAP+XI
    http://wiki.sdn.sap.com/wiki/display/SI/StepbyStepguidetoExplainEnhancedReceiver+Determination
    in the UDF you can write the logic to  remove leading zeros if required:
    Re: removing leading zeros

  • 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

  • IDoc TO File: Receiver Determination did not find any receivers at all

    Hi,
    We have IDoc to file scenario, where based on attributes present in IDoc we have configured different receivers.
    Everything was working fine and files were getting created based on the receiver determination criteria.
    But there is one change done in custom IDoc to re position the attributes.
    Idoc before changes was having NAME1 and NAME2 above KATR6 and KATR7 and after change it looks like below:
    So there is no change in segment and no change in mapping but the attributes KATR6 and KATR7 are used to determine the receiver.
    Cache refresh is done for both ESR and ID. I have re - entered the receiver determination criteria just to ensure that change should reflect.
    But still when I am triggering outbound IDoc from ECC to PI, the transaction is getting errored out with below error:
    "ErrText": "Processing error = Receiver Determination did not find any receivers at all",
    Can any one providee some idea what could be the reason and what is the right approach to resolve this issue.
    Thanks,
    Vertika

    Hi Krupa,
    I have marked your answer as helpful answer and delete of metadata wasn't required.
    Reload works . But thanks for your suggestion.
    Thanks,
    Vertika

  • IDoc to IDoc - conditional receiver determination issue

    Hello All,
    We are using XI 3.0 and this is my scenario:
    Sender: IDOC from SAP system
    Receivers: There are 2 receivers (one SAP and one non sap system).
    I want conditional receiver determination based on the idoc field RCVPRN.
    Integration Repository: I imported standard SAP IDOC FIDCC2 into IR and it is in "urn:sap-com:document:sap:idoc:messages" namespace of my SWCV. I am not creating data types, message types or message interfaces as I want to use the IDOC type directly as the interface name in Integration directory.
    Integration directory: When I am creating receiver determination, I am getting a warning 'Message interface does not exist in any software components installed on this business system'. When I got to condition editor and want to choose the idoc field RCVPRN using XPATH, it is not showing the idoc structure.
    In SLD, the correct product is installed on my sender ABAP technical system, and correct SWCV (into which i imported the IDOC) is installed on my business system. I refreshed cache and cleared SLD cache in ID. Still i get the same warning 'Message interface does not exist in any software components installed on this business system'.
    How can i solve this issue? Any help is highly appreciated.
    Thanks,
    Chandra

    Hi Chandra,
    Can you check whether you have assigned or linked the SWCV with the Business system in SLD.
    Just go to SLD and open the SWCV and check if it is linked with the BS od the sender system.
    Since the sender is ABAP, you must have created the TS and BS using rz70, then see that that the SWCV is attached to the BS correctly. Under TS add the Product and then the corresponding SWCV.
    Also check one thing: are u selecting the correct Communication component, under which the Interface is present.
    Lastly if these doesnot work: In Integration Directory, Go to Environment-> Clear SLD Data Cache. Then try once again.
    Cheers,
    Souvik
    Edited by: Souvik Chatterjee on May 16, 2011 3:39 PM

  • Receiver determination doesn't work for same IDoc type but in differentSWCV

    hi guys,
    we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
    1. The process flow is : R/3 IDoc -> XI -> Third party system
    2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
    3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
    Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
    Does anyone encounter this problem? really need and appreciate your help.
    -Eddie

    information from monitor:
    Status     Sender               Service Sender Namespace                         Sender Interface
    reschedul  XXXCLNT100     urn:sap-com:document:sap:idoc:messages   ORDRSP.ORDERS05
    columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
    And then double click records in monitor, go into detail information...
    Normally there's lots of setps existed, such as
    Inbound Message ( CENTRAL )
    Receiver Identification
    Interface Determination
    Receiver Grouping
    Message Branch According to Receiver List
    Technical Routing
    Call Adapter
    But now there's only one setp -
    "Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
    And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

  • Idoc structure not displying in XPATH at Receiver Determination..!!! Urgent

    Hi All,
    Doing Idoc to File Scenerio,
    In the receiver determination, I need to select the XPATH from the Idoc structure and by based on the GLN number which is coming in one of the segment, I need to pass to different receivers.
    Problem here is Iam not able to see the Idoc structure in the  XPATH to provide the condition.
    But when doing File to Idoc scenarios, Iam able to see the File structure.
    Any idea why IDoc structure is not displaying over here??
    Its a bit urgent for me..
    Waiting for your replys.
    Thanks&Regards
    Seema.

    Hi,
    This will help you now
    Hi,
    If you get the following msg while selecting the BS in Receiver Determination and if you are unable to view the Structure of the Source
    "Message interface does not exist in any software components installed on this business system"
    1) Open ID-----Double click on Business system that which u are using in the scenario
    2) Check whether you are able to see the SWC in the Othere attributes TAB
    3) If it is not there means goto SLD----Open the Technical System of R/3 by choosing Web as ABAp type
    4) Click on Installed Products TAB
    5) Click on Add New product and add your Product of the SWC whcih you are using for developement and Save it
    6) Then goto Business systems TAB in the same Technical systems window and click on the Business System appears in the window.
    7) Click on Installed products and Check the check box of your Product and then finally save that.
    Now you should be able to see the SWC in the Othere attributes TAB in ID
    Regards
    Seshagiri

  • Context Object for IDOC in Receiver Determination

    hi,
    I am trying to filter the receivers based on the vendor values in IDOC ORDERS using Context Object.
    I don't see the vendor field where i could filter the value.
    Any ideas would be greatful.
    Thanks,
    Tirumal

    hi,
    Conditional Receiver determaintion is possible only on the Source Message. the reason being that the integration engine will first execute receiver determiantion--> interface determiantion --> message mapping.
    If you are getting the IDOC as a source, then you can use the XPATH to do conditional receiver determination.
    Regards,
    Bhavesh

  • Flat Idoc and receiver determination

    Hi Folks,
    I have a scenario in which the Idoc is sent to XI in a flat format (Flat Idoc) using tunneling mechanism. The receiver determination configured is conditional based (Verifies the values in the specified fields of the Idoc).
    Now my question is as we know flat Idoc doesn't contain any fields like XML in the input payload, how the receiver can be identified?
    Reminder: (Receiver determination is conditional based and verifies some field values in the Idoc structure)
    Thanks,
    SPMD

    Hi Shabbirmdpasha,
    You can use file adapter channel to get idoc flatfile and convert to xml idoc in the module of the file adapter (available in PI 7.1). You only need to make a relation with the type of idoc with the name of the file: for example, DESADV_xxxxxx.txt for all files with DESADV flatfile idoc's.
    With this method, you know the interface of the outbound interface, and in the receiver determination you can check in the header of the idoc (dc40) to determine the target system.
    PD: Sorry for me english...
    Edited by: Oscar Navas on Dec 1, 2010 4:11 PM

  • IDOC error "receiver determination" while sending from R3 to XI

    Hi all,
    I'm trying to send an IDOC from R3 to BW thro' XI.
    I created 2 business system for R3 & BW.
    I created communication channel for receiving BW with IDOC adapter.
    I created the receiver determination, interface determination & receiver agreement.
    I also used IDX1,IDX2 to configure the port to load to IDOC.
    When I send IDOC from R/3, It gets received in XI with the error message
    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    It didn't select the receiver.
    Am I missing anything?  Can anyone help me with this.
    The same problem exists even I tried to get IDOC into a file in XI.
    I appreciate all your help.
    thanks
    felix.

    Hello Ujjwal,
    Receiver is already defined in "Receiver Determination".
    Even I refreshed CPA Chache many times but getting same 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="">
      <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>
    Thanks.
    RP

  • Enhanced receiver determination - Idoc 2 Idoc scenario

    Hi,
    I am trying Enhanced receiver determination - in an Idoc 2 Idoc scenario.
    But when I selected Enhanced receiver determination in ID, it is asking for interface mapping.As it is an Idoc 2 Idoc scenario, I did not create any mapping objects in IR.
    Is there any round about for this.
    reg,

    Hi,
    if you are planning to send the Idoc to two systems then you do not need Enhanced Recieevr Determination.
    You can add multiple Receivers In the receiver Determination under Configured Receivers and now the same idoc will be sent to 2 receivers.
    Like mentioned by moorhty, Enahnced Receievr Determination allows you to dynamically determine receivers using a mapping program.! I dont think that is needed in your case
    Regards
    Bhavesh

  • Error in receiver determination - Client proxy to IDOC using PI-IS

    Hi,
      I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
    <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:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
    I am using the standard SAP message interface in the sproxy.
    Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
    Thanks,
    Menaga

    <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
    The above error occurs due to:
    1) You have configured a wrong receiver service in the Receiver Determination
    2) You have configured the correct receiver but the cache is not updated
    So check if the receiver service exists and the cache is updated.
    Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
    be created without DT".
    Check if you get any lead from this thread:
    Failed to time to generate proxy - TRX SPROXY
    Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
    Regards,
    Abhishek.

  • No Receiver Agreement found - IDOC RCVPRN = Party

    Hello,
    I have created all the receiver agreements required and they are in the configuration scenario. 
    I have a receiver determination that is using the IDOC vendor number (RCVPRN) to determine the party for delivering purchase orders and another RD with the same config for delivering po changes. 
    In tests my POs are sending successfully and my PO Changes are failing even though they use the same party setup/config.  In SXMB_MONI I can see that the receiver determination for the POs are creating the correct party:
    PO Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Ventura</SAP:Party>
    But the PO Changes seem unable to connect the vendor number to the party:
    PO Change Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">0000557129</SAP:Party>
    In the sample above the party Ventura is set up under the party identifiers as follows:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    How is it that PI 7.10 is getting the same value in RCVPRN and assigning the Party correctly in one case and incorrectly in another?
    Any ideas?
    Thanks,
    Matt

    Sometimes you just need to walk a way for a day or two...  I rechecked the standard configurations over and over.  But I didn't review the Party Extended selection.  In the Receiver Determination I chose to use RCVPRN to identify the Party but upon further investigation I realized I was using the wrong scheme and agency on the Party extension.
    So my party had the following:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    My Receiver Determination was not using http://stc.com/pi/SAPR3 Vendor 0000557129 to determine the Party it was attempting to use http://sap.com/xi/SI XIParty Ventura.  So it was unable to find a matchinig party using the Vendor Numbers.
    Thanks for all the help.
    Matt

Maybe you are looking for