ENHANCED INTERFACE AND RECEIVER DETERMINATION

1)what is the use of enhanced interface determination and enhanced receiver determination and in scenarios we will use them and in what conditions ,and what differentiates it from standard interface/reciever determination?

1. <b>Standard receiver determination</b> to specify the receivers of the message (and optionally routing conditions) manually.You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
&#9679;     Select the receiver from the Integration Directory
&#9679;     Specify a constant value for the receiver
1.2You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
<b>Enhanced receiver determination</b> to have a mapping program determine the receivers of the message dynamically at runtimeInstead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
2.<b>Standard Interface Determination</b> :You can specify to which inbound interface at the receiver the message is to be sent at runtime. You also have the option of specifying a mapping and (when multiple inbound interfaces are defined) a condition for each inbound interface.
2.1 n an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
for receiver determination try this link also
http://help.sap.com/saphelp_nw70/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
Regards,
Mandeep Virk
*Reward if Helpful*

Similar Messages

  • Interface and Receiver determination steps

    Dear Experts,
    I have list of queries which I am facing issue in ID. I am working on SOAP<->SAP-PI<->PROXY scenario.
    1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
    My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the  node Communication Component without party). I created this Business System ABAP from the entries of SLD.
    2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
    3. In the Receiver Determination, I can see in the "Configuration Overview" tab
    that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
    but it shows SI_SOAP_OB.
    4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
    and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
    5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
    I need urgent suggestions from experts , kindly help.
    Regards
    Alice Rebecca

    1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
    My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
    ANS -
    For SOAP, anything like Legacy_filer can be created & used.
    For PROXY, use the business system of R/3 system maintained in SLD.
    2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
    ANS-
    Sender CC
    Sender Agreement
    Rec Determination
    Int Determination
    Rec CC
    Rec Agreement.
    Create the steps in COnfiguration Scenario directly.
    3. In the Receiver Determination, I can see in the "Configuration Overview" tab
    that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
    but it shows SI_SOAP_OB.
    4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
    and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
    ANS
    its cache error. Go for full cache refresh in IB>AdministrationData cahce--cache refresh.
    5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
    ANS
    Nope. create the structure in ESR & generate proxy for the same in ECC system. that's it. No need of WSDL here.
    -santosh.

  • Interface determination and Receiver Determination

    Any one can give the clear idea about Interface determination and Receiver Determination????????

    HI Gabriel
    <b>Interface Determination</b>
    An InterfaceDetermination specifies which interface is to be used for the inbound process of a message.
    Interface Determination is to specify which inbound interface of a receiver a message is to be forwarded to. We also specify which interface mapping from the Integration Repository is to be used for processing the message. Here it will know which kind of mapping you are using etc.
    <b> ReceiverDeterminatioin.</b>
    A ReceiverDetermintaion defines on or more receivers for a sender and an outbound interface.
    Receiver Determination is to specify which receivers a message is to be sent to.
    Cheers...
    Vasu
    <b>** REward Points if found useful **</b>

  • INTERFACE DETERMINATION AND RECEIVER DETERMINATION DOUBTS???

    Hi Team
    I am having doubts regarding the Interafce Determination and the receiver determination. In pur landscape in our objects, some times i am seeing a Condition is being defined in the Interafce Determination  and sometimes  am seeing a Condition is being defined in the receiver determination . could you please let me know the differences between the above two.
    thanx in advance.

    Hi Nabhinav,
    Condtions in receiver determination - These conditions are evaluated and executed to determine the receivers for this incoming message.
    Condtions in Interface determination - These conditions are evaluated and ececuted to determine the Interface mapping to be called in order to map the source message to the target message.
    Please take a loot at these links for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/ce2a8e3a8e5430e10000000a42189b/content.htm
    Also, search the SDN before posting you query.
    Regards, Gaurav.

  • PI 7.1 Sender Interface and Receiver Interface  gets interchanged

    Hi All,
    I m facing a strange problem in PI 7.1
    For many of my scenarios, the Sender Interface, sender namespace and receiver Interface, receiver namespace  information gets interchanged and displayed incorrectly.
    But sometimes its working fine.
    When we analysed the Log messages, found that, after xml validation step, the sender and reciever interface gets interchanged.
    Any idea why this happens?
    How to rectify this error?

    Aarthi,
    Please check your message interfaces once again. Sender is outbound and Receiver is inbound.
    Also please check your receiver determination.
    Regards,
    ---Satish

  • 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

  • Some PI questions regarding RFC and  receiver determination

    If we import the design objects in one customer system from another customer system , and in the original system there is an imported RFC ,
    This RFC has been created in the new SAP customer system.
    My question is do we have to import the RFC again , as it is already in the imported design objecs.
    My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the BPM ,
    Thanks

    My question is do we have to import the RFC again , as it is already in the imported design objecs
    Yes....the RFC/ IDOC should be imported from the system to/ from which you will send/ receive the data.
    If the RFC was in system1 earlier and now in system2.....then you have to delete the RFC imported from system1 (if it is not used) and then import it from system2
    My second question is , di we need to create a receiver determination for the answe in a synchronous send step of the
    BPM ,
    Irrespective of sync/ async send step.....you should create Receiver Determination....which will have BPM as sender and the TO_SYSTEM as receiver.....not separately for response....just once
    Regards,
    Abhishek.

  • XPATH and Receiver Determination

    In Reference to forum thread : Conditions in  Xpath (Receiver determination)
    Suppose I have MT as
    MT_Pickfile
       |_Header
       |_Body
       |_Trailer
    And i need to check;
    (field3 = "100" or field3 = "200" or field3 = "300" ) and(field5 = "AA" or field5 = "BB" or field5 = "CC")
    field3 is in Header and field5 is in Body
    I tried giving
    /p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and /p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
    It doesnt work. But then if both field3 and field5 are in Header then it works (as had been the case in the above mentioned thread which Stefan Grube replied to) i.e. to say
    /p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )] and [(field5 = "AA" or field5 = "BB" or field5 = "CC")] EX
    Can anybody put in their suggestions ?
    Thanx in Advance,
    ShaBZ

    Hi Shabarish,
    It is not possible to have <i>and</i> or <i>or</i> outside the brackets <i>[]</i>.
    Try following:
    /p1:MT_Pickfile[(Header/field3 = "100" or Header/field3 = "200" or Header/field3 = "300" ) and Body/field5 = "AA" or Body/field5 = "BB" or Body/field5 = "CC")]
    Another idea:
    Write two lines in receiver determination (use insert expression):
    1. line:
    /p1:MT_Pickfile/Header[(field3 = "100" or field3 = "200" or field3 = "300" )]
    2. line
    /p1:MT_Pickfile/Body[(field5 = "AA" or field5 = "BB" or field5 = "CC")]
    Hope that helps
    Stefan

  • Multi Mapping with out BPM and Receiver Determination Condition

    Hi Masters,
    My Requirement Was:
    Proxy will send the data to XI system, Based Customer group number[1000,2000,3000,4000], I need to split the message into 4 messages, and sent to 4 Different location, based on Customer Group condition.
    For message split, I fallowed below weblog.
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    Problem is file split correctly, but data goes to all customer groups..
    EX
    If they send the customer group 1000, I need to send the customer group 1000 file to BS1[Business Server1],
    If they send the customer group 2000, I need to send the customer group 2000 file to BS2[Business Server1],
    Please guide me,
    Thanks,
    ANU-

    Hi,
    Develope it like follow.
    Source Structure- Same for everything.
    Create 4 different structures for all targets, create 4 different msg types, 4 inbound message interface ( i think you are creating single Message type now, that is the mistake)
    In message maaping, add 4 target message types in same MM.. i hope i am clear..  ( same like in blog /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible he has created 2 message types USER_1 and Employee)
    keep occurence of all of them 0 to unbunded (not necessary)
    Now create mapping for each message type (same like USER_1 and Employee, imagine them like different message types virtually). 
    Map message type with the source field and mention the condition which you want test using graphical functions.  i will say if x e equla to 1 creatif --> target.
    I hope i m clear till now...
    thanks.

  • 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

  • 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 mapping is not visible in receiver determination

    Hi,
    I could not see interface mapping in my receiver determination in ID.
    I can see the message interface and receiver agreement in receiver determination
    my scenario is idoc to soap (SAP R3 to webservice)
    Thanks
    Ruban

    hi,
    could you plz check as Sheshagiri and Phani have said.
    Also wanted to know,are u using the configuration wizard for creating ur business scenario and not finding ur interface mapping?
    if so is the case then try creating manually ur reciever determination and add ur interface mapping(if u have already done as said by phani and seshagiri)  by inserting it.
    let us know how it went.
    thanks,
    ahmed

  • Receiver Determination Condition and XPATH

    Hi Everyone,
    I have a receiver determination with conditions and can not figure out why one thing is working, and the other isn't.
    As suggested in the following forum post, XPATH and RECEIVER DETERMINATION, I had to do the following to my XPATH expression to make it work.  The full xpath expression is this:
    (/p1:RenExtract_MT/Detail/CompanyCode = 9740)
    where
    p1 = http://company.com/xi/fin/
    but whenever I put in a condition it could not find a receiver.
    Hoewver, when I did this:
    //CompanyCode
    it worked.
    I did everything through the condition editor, many times, and didn't type anything in myself.  Is there a length limitation or something (I removed some data in here, the expression is really longer!).
    Any ideas?
    Peter

    Hi Peter,
    I do not have an explanation for this wired behaviour.
    But I can assure your, that your working solution, the //something expression is a good one and not inferior to a solution using an explicit, absolute path.
    Why is that: I can remember some benchmarks, where the //something expression always outperformed the other one.
    Regards
    Gregor

  • Receiver determination based on target msg???

    Hi All,
    Is it possible to do a receiver determination based on some field present in target msg. I know I can do the same if the field is present in source msg with the condition editor in receiver determination. But this will not help my scenario. I need to find the receiver based on a field in target msg. Is it possible?? If so, can u pls explain it???
    Thanks & Regards,
    Jai Shankar.

    Jai,
    Am on Sp14 and have not had the chance to try it out.
    but, <b>I dont think you will need a extra Receiver Determination for the Enhanced Receiver Determination.</b>
    What I understood out of that blog was that the  Interface mapping between Source Interface and Receiver Interface  will determine the receiver. So, you fill in the reciver service field with the actual receiver and this value will be taken as the receiver.
    The Receiver Interface will be taken from the SAP basis SWCV.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
    Regards,
    Bhavesh
    Regards,
    Bhavesh

  • 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

Maybe you are looking for