Receiver Agreement and Interface determination

Hi
I have an input file that generates two output files. The two output files go to the same interface. One output file will have header and the other will have details. I want to kow how many receiver determination, interface determination, sender agreement and receiver agreements we need to create
Regards

Hi Ajith,
As perception, I understand that you would like to like to split the input file into two as Header and Details. For this requirement, you should need Integration Directory (Configuration) as below:
1. Need to Two Receiver agreements.
2. One Receiver determination.
3. One sender agreement.
4. One Interface determination ( Type: Enhanced)
Thanks,

Similar Messages

  • 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

  • Receiver Determination and Interface Determination Condition conflict in ICO

    Hi,
    I found a strange issue today while configuring two receivers using the Receiver and Interface Determination conditions.
    Sender - Proxy Service
    Receiver1 - ReceiverA
    Receiver2 - ReceiverB
    Receiver Determination Condition : When Field1 = 100, message should flow to ReceiverA and ReceiverB
    Interface Determination Condition (ReceiverA) : When Field1=100 and Field2=50 message should flow to a specific interface in ReceiverA
    There is no Interface Determination condition for ReceiverB, for all messages having Field1=100, it should go to ReceiverB.
    Test Scenarios:
    1) Field1=100, Field2=50 : Message flows successfully to ReceiverA and ReceiverB
    2) Field1=100, Field2=89 : Message fails to process from ECC itself throwing Interface Determination not found error. Ideally this is a positive scenario for ReceiverB and it should send the message to ReceiverB without any errors. But, this did not happen in this case
    I tried the same by configuring the conditions completely in Receiver Determination itself without using the Interface Determination, it worked perfectly fine. But, just wanted to understand that if this is an expected behavior.

    Hi Sherin,
    As there are two receivers Receiver A and Receiver B.You need to create two bussiness components and two communcication channels for two receivers and one Reciver Determination, two Interface Determination,two Receiver Agreement.In Receiver Determination you need to keep the below and condition.
    In the above screenshot the two receiver are Receiver B and Receiver C and Field 1 is Key_Value and Field2 is Emp_ID.
    If the Key_Value=100 and Emp_ID =22 then the message should go to both the receivers B & C by keeping the following AND condition
    If the Key_Value=100 and Emp_ID is not equal to 22 then the message should go only to Receiver B by keeping the following condition
    You need not keep any condition in Interface Determination just create 2 Interface determination for two receivers.
    Hope this helps you.
    Thanks,
    Durga.

  • Receiver and Interface determination

    Hi,
    My senario is File to IDOC and mail.
    The condition here is the count of Idoc generated has to be sent as a mail and the mail has to  be sent only after the IDoc has been generated successfully.
    So i am using two receiver services one is for IDOC and other is for mail and  in one receiver determination I am refering TWO reciver Service without any condition.
    now  i have to use only one interface determination to maintain the order at runtime. so that the interface mapping for mail will be triggered only after the Idoc interfacemapping is successfull.
    but in receiver agreement  i am not able to refer the Receiver channel for Mail. because the receiver service is still poiting to the Idoc Serveice.
    Plz advice.

    Hi!
    I think the above requirement will also work by using a simple BPM. just try with below steps.
    Steps in BPM::
    1. Receive step to receive File from a third party by using File Sender CC.
    2. SEND ASYNCH step to send IDOC generated Structure data.
    3. Before going to next step please find any constant value which will be coming into IDOC from file that
        means for example if your IDOC cotnains any field like ORDER_Generated_By or 
        GENERATED_BY:: AMAR  name is same in all the data that is coming into IDOC remember that Field
        Name name and insert it in the swtich statement condition editor.
    4. Now Insert Switch Condition with 2 branches A & B,
         a) Branch A contains control statement and this branch executes only if the condition statisfies with
            If that IDOC Field lets say name XXXX is equal to constant value AMAR then raise/throws  an alert
            mail by uising Control Step.
        b) In Branch B also you ill be including Control Step but this control Step will says that  MAIL
            INDICATION  No IDOC is generated by using another control step.
    5) Remaining all other configurations like 2 receiver agreements and every thing aare same.
    6) But you need to confgure ALert configuration settings okay.
    You can also achive this by using without BPM.::
    In ID part:: you need to enter a condition in Receiver Determination with two receiver business systems and that condition will be once the IDOC field like XXXXX(generated_by is equal to some constant like AMAR ) then it needs to active the Mail Business System.
    but this would be little but confusion and but u can achive the above requirement by using simple BPM.
    Note:: Only diadvantage will be some performance issue will come if goes through BPM but it works
              very 100 systamatic way because you can review where exactly your Scenario strucks and also
              u can check whether your IDOC generated or not whether mail sent or not in the BPM WORK
               FLOW in the BUSINESS PROCESS ENGINE.
    Regards::
    Amar Srinivas Eli

  • Receiver Determination and Interface Determination

    Hi,
    Please, can anyone explain what is the concept of 'Receiver determination' and 'Interface Determination'?
    Thanks,
    Harikumar. S

    Hi,
    >>>>Receiver determination
    its about finding the receiver system for particular source system and outbound interface.
    Suppose,you want to send data from file->XI->SAP and CRM based on some condition
    in this scenario you need to determine whether to send file data to SAP or CRM system,this decision you will do in Receiver determination
    in Receiver determination screen you need to provide the following details
    1.Source system(ex: File system)
    2.Outbound Interface(File Message Interface)
    3.condition and receiving system(ex:if some x field value in source payload is 1 go to SAP elseif '0' go to CRM system)
    >>>>>>Interface Determination
    suppose in above scenario you determined the receiver i.e SAP,you will have number of IDOCs (Inbound Interfaces)in SAP.
    so to which IDOC you will send file data?This decision you will make in Interface determination(we can it as Inbound Interface determination).if you find the IDOC is CREMAS then how will transfer file structure data to IDOC structure? answer is Message Mapping
    From all the above decisions you need to provide following details in Interface determination screen
    1.Source System
    2.Outbound Interface
    3.Receiver System
    4.Inbound Interface(IDOC type)
    5.Message Mapping(i.e file to IDOC)
    Even in Interface determination you can specify the condition to select Inbound Interfaces(ex.IDOCs)
    if you have any doubts please lets know.
    Cheers,
    Jag

  • Receiver and Interface Determination, Sender and Receiver Agreement

    Hi Experts,
    Could you please tell me, what Receiver Determination, Interface Determination, Sender Agreement and Receiver Agreement we have to use for the below blog.
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]
    Regards
    Sara

    Hi Sara,
    WS->BP
    Receiver Determination: Sender IF, Sender NS, Sender BS determine the BP
    Interface Determination: Sender IF, Sender NS, Sender BS determine your start msg IF (abstr IF) and IF mapping
    Sender Agreement: SOAP sender channel for that Sender IF, Sender NS, Sender BS
    Receiver Agreement: not reqired
    BP->DB
    Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (DB)
    Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
    Sender Agreement: not reqired
    Receiver Agreement: JDBC receiver channel for that Inbound IF, NS and 3rd party BS
    BP->File
    Receiver Determination: BP IF (abstr), BP IF NS, BP determine the 3rd party BS (File)
    Interface Determination: BP IF (abstr), BP IF NS, BP determine Inbound-IF and IF mapping
    Sender Agreement: not required
    Receiver Agreement: File receiver channel for that Inbound IF, NS and 3rd party BS
    Regards,
    Udo

  • Need of creating receiver determination and interface determination

    what is the need of creating interface determination where as providing all the details in Receiver determination?

    Hi,
    The loose coupling between the Interface mapping and receiver determination have provided the compatibility for reusability.
    The Interface determination maintained and just linked to receiver determination so you could have multiple receiver determinations with common interface determination or vice-versa.
    If you provide all the information in receiver determination then, it would be very dfficult to have the various mappins for multiple receivers maintained in receiver determination.
    Interface determination is applied at runtime to all messages to be processed. Thus from security point of view of transaction of data. its preferable.
    Thanks
    Swarup

  • Interface Determination causing issue in Receiver Determination

    Hi
    I am having an issue with interface and receiver determination as follows:
    - Inbound message may be sent to two receivers.
    - Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is <b>not </b>the issue.
    - Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
    Is there a way to resolve this? Appreciate any help. Thx, Duncan

    Again, thanks for the replies.
    <b>MONI for RD</b>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="3" type="T">...create rule engine</Trace>
      <Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
      <Trace level="2" type="T">......extracting values found: 1</Trace>
      <Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
      <Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
      <Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:2</Trace>
      </Trace>
      </Trace>
      </Trace>
    Here, you see that both receivers are found.
    <b>MONI for ID</b>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...create rule engine</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
      <Trace level="2" type="T">......extracting values found: 0</Trace>
      <Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
      <Trace level="2" type="T">......extracting values found: 2</Trace>
      <Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
      <Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
      <Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
      <Trace level="2" type="T">......extracting values found: 1</Trace>
      <Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
    Any ideas? Thx, Duncan

  • Receiver determination Vs Interface determination

    Hi Experts,
          What is the difference between Receiver determination and Interface determination?
    In both the case we specify sender -> outbound interface -> Receiver Service -> Interface mapping
    Can't we use only interface mapping? Why SAP is providing these two determinations?
    Thanks
    Gopal

    Hi,
    ><i>In both the case we specify sender -> outbound interface -> Receiver Service - Interface mapping</i>
    In receiver determination you only mention the Sender Service, Sender Interface and Reciever Service. You do not mention the Inbound Interafce and interface mapping. You do this in the Interface Determination.
    The split between Receiver Determination and Interfacedetermiantion is so that you can add send the same message to Multiple Receivers and then fior each of the receivers , if needed you can add multiple Inbound Interafces / mappings!!
    And you can add multiple conditions as well!! makes sense to me!
    regards
    Bhavesh

  • Error : Receiver agreement not found

    Hi all,
    My scenario is RFC to JDBC.
    Its showing the below error, when 'I try to send data through test configuration after configuring ESR and ID part.
    Receiver Agreement
    Runtime error
    Problem occurred in receiver agreement for sender -SAP_BL_ISU to receiver -RFC_To_JDBC_Async_R_SQL_bllmstest,urn:sap-com:document:sap:rfc:functions.ZTEST_TIPS_DOI1: No standard agreement found for , SAP_BL_ISU, , RFC_To_JDBC_Async_R_SQL_bllmstest, urn:sap-com:document:sap:rfc:functions, ZTEST_TIPS_DOI1
    <Trace level="1" type="B">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
    <Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
    <Trace level="2" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">determine OUTBOUND BINDING for: </Trace>
    <Trace level="2" type="T">-SAP_BL_ISU </Trace>
    <Trace level="2" type="T">-RFC_To_JDBC_Async_R_SQL_bllmstest </Trace>
    <Trace level="2" type="T">urn:sap-com:document:sap:rfc:functions.ZTEST_TIPS_DOI1 </Trace>
    <Trace level="1" type="T">error with outbound binding. </Trace>
    <Trace level="1" type="T">No standard agreement found for , SAP_BL_ISU, , RFC_To_JDBC_Async_R_SQL_bllmstest, urn:sap-com:document:sap:rfc:functions, ZTEST_TIPS_DOI1 </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>
    please suggest me...

    Hi,
    This is configuration issue, please check the ESR sender/Receiver interfaces and the associated
    Sender / Receiver agreement and the associated communication channels are configured correctly.
    Try to test the configuration using Test configuration / send a test message from RWB to this interface.
    If the configuration is correct and you are facing the same issue. try to delete the ID configuration and recreate it.
    Before re-creating the configuration, do cache refresh.
    Regards
    Bhargava Krishna

  • Use of Enhanced option in Interface Determination

    Hello All,
    I am stuck up with a problem, where I need your expertised help.
    The scenario is IDOC --> Files 
    what I mean by files is:  I have one sender (ecc system) and two receivers (ftp destinations using file adapters).  I created multi mappings (1:n); based on the content of the IDOC field, either Message Type1 or MessageType2 are populated in the message mapping.  Each MessageType belongs to separate receivers.  Message mapping working good when tested in the test tab.
    Now, coming to configuration side; I have created one interfaced determination with enhanced mode and gave the Message interface information, which populated both Message Interfaces below automatically.  Interface is failing with "No receiver Agreement for the sender receiver combinatio".  I checked all the cache refresh and also the receiver agreements.  I have both receiver agreeements defined, one of each receiver.  I guess something to do with Interface Determination definition. 
    Questions:
    1) In the interface determination, what receiver system we need to specify.  I have two receivers here; I don't see space to specify both when selected enhanced option.
    2) How do I specify receiver determination for this?
    Thanks for your help..RP

    I just looked into the error message deeply.  This is why it is errroring out.  any idea is a great help.
    In the Interface determination, I have * for the receiver.
    In the Receiver determination, I have both receivers defined. 
    In the bottom section of the Receiver Determination, It is showing both message interfaces for each receiver like below
    Receiver1
       MessageInterface1  --  Interface Mapping -- Receiver Agreement
       MessageInterface2  --  Interface Mapping -- Does Not Exist
    Receiver2
       MessageInterface1  --  Interface Mapping -- Does Not Exist
       MessageInterface2  --  Interface Mapping -- Receiver Agreement
    In the Moni, I see two child messages as they are supposed to, one for each receiver and and both failed.
    Both messages failed with the similar message statinng that 'No receiver agreement found for sender xx and receiver combination'.  This error is for the other message interface which does not beloing to that receiver (MI information also shown in the message). 
    Thanks for your help..

  • IDoc-Tunneling -- No Receiver Agreement

    Hi, i am trying to do the IDoc-Tunneling scenario from Michal.
    Well everything looks fine so far except that i get following error:
    +<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="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>-Q01CLNT010</SAP:P1>
      <SAP:P2>0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -Q01CLNT010 zum Empfänger 0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01 gefunden werden</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>+
    Well i have Receiver Agreement that looks like:
    Sender Service: Q01CLNT010
    Receiver Service: EDI
    Interface: DELFOR.DELFOR02
    Namespace: urn:sap-com:document:sap:idoc:messages
    CC: IDOC_RECEIVER_EDI
    In this Receiver-CC i also activated
    - Apply Control Record Values
    - Take sender from payload
    However, i have no clue what is wrong.
    Can somebody help? br Jens

    Hi Jens
    (6) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
    The problem is in Technical routing.
    Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
    check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
    Please refer the follwoing blog for details
    <b>/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Thanks
    AbhishekMahajan
    *****Please reward points if helpful*********

  • Problem in Creating Receiver Agreement

    Hi,
    I had created a namespace in IR and did a simple idoc to file scenario.
    In the IR, the MI and MT are not been shown while creating the receiver agreement and receiver determination.
    Do let me know what would have been wrong.
    I tried entering it manually and it gave error like schema not recognized.
    Regards
    Krish

    Hi,
    when u r Doing Idoc to file scenario, sender side u have to use a ABAP business sysytem.
    hope u have imported the same in configuration scenario.
    in that u have to select u r MI. then onlly it will reflect in the Reciver Determination
    Regards,
    Madhav
    Note: Points If Useful.

  • Meaning of multiple interface determination

    I'm still starting with XI and some doubts are appearing while I get deeper into it. My doubt here is what's the sense in configuring more than one inbound interface in interface determination.
    As you specificy sender and receiver services, and interface, how does it makes sense? I mean, the specified interface is forcing implicitily the inbound interface, so it doesn't make sense to define two different inbound interfaces.
    Unless of course you choose the same inbound interface more than once, with different interface mappings, but then, which one would be chosen for an actual communication?
    Thanks in advance.
    (Environment XI 7.0)

    I don't think you answered my question. I'm talking about configuration of two inbound interfaces in a single interface determination object.
    In this image you can see one of my interface determinations:
    [picture|http://img26.imageshack.us/my.php?image=interfacedet1ju7.jpg]
    Sender service and sender interface are set and can't be modified, just as receiver service. This configuration is making mandatory that in the "configured interfaces" section, the inbound interface is BAPI_MATERIAL_GETALL, because that is the output message type of MI_OUT_S_0422_BAPI_MATERIAL_GETALL.
    So what's the sense of adding a new line in the "configured interfaces" section?
    It would only make sense using BAPI_MATERIAL_GETALL as inbound interface (is mandatory as I wrote before), and specify a different interface mapping. However, in that case, which one of those two would be used in runtime?
    (Please answer directly to my questions and not just a general paragrafh. Otherwise I don't think we will get a successful communication. If what I write can't be understood please ask me.)
    Thanks.

  • Multiple Interface Determination

    Hello everybody,
    I am working on the following szenarion:
    - one sender and sender interface (incoming IDOC).
    - one receiver with two different receiver interfaces (outgoing BAPIs). For one of these interfaces there exit two different interface and message mappings. So, 1 incoming interface => 3 outgoing with 2 different interfaces
    So in the interface determination I want to rout the message by use of XPath expression to use one of the two interface (no problem at all), but also to choose one of two interface mappings for the same interface. If I try this by creating three lines in the interface determination and using different XPaths, the last entered interface always is deleted automatically.
    Thanks for your help.

    Hi,
    To do what you want you may have to use both Receiver Determination and Interface Determination.  XPath expressions can be used in both places.
    In Receiver Determination, you will have 2 receiver services.  Then, in one of the receiver services, you will have 2 Interface Determinations.  So, you will end up with something like the following:
    Receiver service1:  interface1
    Receiver service2:  interface1, interface2
    Regards,
    Bill

Maybe you are looking for

  • How to find out sub site name from which sub site template is created - in solution gallery

    hi,  i am having an issue in my "save site as a template". i have created  a subsite few weeks back with doc libs and  splists, disc.forum and  based on the template subsite I have created new subsites. now  as  per my new requirement i need to add n

  • What's wrong with this simple method

    i'm having compile troubles with this simple method, and i think it's got to be something in my syntax. public String setTime() String timeString = new String("The time is " + getHours() + ":" + getMinutes() + ":" + getSeconds() + " " + getIsAM()); r

  • Text module constrained to single page?

    I have added a page to the "standard" smart form for purchase order printing. The purpose is to print standard terms and conditions, which are stored in a text module. This should be a piece of cake I thought, but apparently not... A command to go to

  • ANOTHER Lightroom 5 Bug??

    This is another bug that I had during the Beta which I hoped would have been solved. It is difficult to reproduce but happens frequent enough to be a real pain. Using the adjustment brush or gradient tool, I can apply settings to photos. Then when I

  • Read color/shortcut keys for Actions in Actions Palette?

    Is it possible to use Javascript to read the color and shortcut key assigned to an action using Javascript? I'm looping through and building a list of actionsets/actions into an XML file and would like to include the color and shortcut  as well. Than