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

Similar Messages

  • 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

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

  • 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

    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

  • Extended Receiver & Extended  Interface Determination

    Hi Experts,
    Can any tell me what is Extended Receiver & Extended  Interface Determination.
    And the Difference between Standard Receiver & Standard Interface Determination.
    were to use Extended Receiver & Extended  Interface Determination.
    Thanks in advance
    Shakif

    Hi,
    Standard Receiver Determination Features
    Specifying Receivers
    You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
    ●     Select the receiver from the Integration Directory
    ●     Specify a constant value for the receiver
    ●     Determine the receiver dynamically from the message content
    To enter the necessary details, use the following:
    ●     The party editor for specifying the receiver party
    ●     The service editor for specifying the receiver service
    To call the relevant editor, in the Display/Edit Receiver Determination editor in the Configured Receivers frame, call the Input Help ( ) in either the Party or Service column.
    Defining Conditions
    You 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).
    ●     If you want to specify a new condition for forwarding the message to a receiver, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert New Condition () and call the condition editor by using the input help ().
    ●     If you want to specify a new condition for forwarding the message to multiple receivers, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert Line After Selection ( ) and call the condition editor  by using the input help (). 
    In the condition editor, you can select an element from the message payload and specify a value with which the value of this element is to be compared at runtime.
    Enhanced Receiver Determination
    Use
    You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead 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.
    You can of course formulate conditions in a standard receiver determination that relate to the content of the message. However, you have to specify the names of the receivers (to which the message is sent under the formulated condition) explicitly in the receiver determination. If you create an enhanced receiver determination, you do not have to specify receiver names at this stage. 
    Integration
    During the definition of the interface mapping, you assign the abstract message interface ReceiverDetermination as the target interface. The message interface ReceiverDetermination is in the Integration Repository in the software component SAP BASIS (namespace http://sap.com/xi/XI/System).
    The message interface uses the message type Receivers and the data type Receivers. The data type Receivers describes a list of receivers and has the following structure:
    The following instance of the data type Receivers contains two receivers. The first receiver comprises a party and service and is identified by a DUNS number; the second receiver comprises a service without a party.
    <Receivers>
    <Receiver>
        <Party agency=“016“ scheme=“DUNS“>123456789</Party>
        <Service>MyService</Service>
    </Receiver>
    <Receiver>
        <Party agency=“http://sap.com/xi/XI“ scheme=“XIParty“></Party>
        <Service>ABC_200</Service>
    </Receiver>
    </Receivers>
    You can specify party and service for each receiver.
    Activities
           1.      Integration Repository: Define the interface mapping. Assign the message interface ReceiverDetermination as the target interface (see above).
           2.      Integration Repository: Define the message mapping or mapping program that is to determine the receivers at runtime. Assign the message mapping or mapping program to the interface mapping.
           3.      Integration Directory: Define an (enhanced) receiver determination.
    &#9675;     Enter the outbound interface of the interface mapping from step 1 in the key of the receiver determination as the outbound interface.
    &#9675;     Assign the interface mapping created in step 1 to the receiver determination.
    Standard Interface Determination
    Use
    You can specify to which inbound interfaces 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.
    Note the following fundamental cases when assigning multiple inbound interfaces:
    Multiple Different Inbound Interfaces
    Imagine you enter the following interface assignment.
    Inbound Interface
    Condition
    Interface Mapping
    IF_1
    M_1
    IF_2
    M_2
    After the interface determination is evaluated, this results in two messages with the same payload at runtime. A different mapping (either M1 or M_2) is executed for both messages and then they are forwarded to the two interfaces (either IF_1 or IF_2) at the receiver. 
    Multiple Identical Inbound Interfaces with Conditions
    Imagine you enter the following interface assignment.
    Inbound Interface
    Condition
    Interface Mapping
    IF_1
    B_1
    M_1
    IF_1
    B_2
    M_2
    In this case, the conditions are evaluated during the interface determination step. If condition B_1 is true, then mapping M_1 is executed; if condition B_2 is true, then mapping M_2 is executed. The message is forwarded to the same inbound interface at the receiver in both cases. Unlike in the case described above, this does not result in multiple messages with the same payload because only one condition can ever be true at runtime.
    Features
    You enter the assignment between the outbound interface and the inbound interface(s) in a table. Each table line represents exactly one assignment between the outbound interface and an inbound interface. To insert or delete lines, choose Insert One Line After Selection () or Delete Selected Line ().
    Enhanced (Mapping-Based) Interface Determination
    Use
    In an enhanced interface determination you do not enter the inbound interfaces manually, but instead 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 example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
    You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping).  In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
    You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
    Procedure at Runtime During Message Split
    Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
    Receiver Interfaces of Bulk Messages and Individual Messages
    The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
    If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
    You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
    Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types: 
    -          RFC Adapter
    -          SAP Business Connector Adapter
    -          File/FTP Adapter
    -          JDBC Adapter
    -          JMS Adapter
    -          SOAP adapter
    -          Marketplace adapter
    -          Mail Adapter
    -          RNIF adapter
    -          CIDX Adapter
    The adapters also have to all run on the same Adapter Engine.
    Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
    Attachments from the original message are not appended to the messages resulting from the message split.
    Activities
    To execute a mapping-based message split, perform the following steps:
           1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
           2.      Integration Directory: Define the interface determination.
    Note the following:
    &#9675;     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
    &#9675;     The interface determination type must be set to Enhanced.
    &#9675;     Select the multi-mapping you defined previously from the Integration Repository.
    To do so, call input help ().
    The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
    The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
    Regards,
    Phani
    Reward points if Helpful

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

  • 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

  • Runtime flow sequence of receiver or interface determinations is based on

    There is interface whose message flows as mentioned below.
    System A <=> System B <=> System c
    BPM: Receive -> sync send 1 -> sync send 2 -> async send
    System A sends the sync message to System B, System b response as request to System c and System C
    response as response to System A
    Receiver/interface determinations:
           i: RD/ID: System A to IP
          ii: RD/ID: IP to System B  (Operation mapping from IP to System B)
         iii: RD/ID: IP to system C  (Operation mapping from IP to System C)
    No conditions in Receiver/interface determination
    My query is how IE determines after i:RD/ID execution it should go to ii/iii: RD/ID ?
    Is it based on Message interface(Message type) i.e Receiver IP message interface should be similar to sender
    IP message interface ?
    Otherwise based on the sequence of creation of RD/ID in Configuration scenario ?

    Source Mesage interface in 2nd RD/ID is not dependent on previous target Message interface of RD/ID. Both interfaces can be any message interfaces ?
    So you are asking me if it's possible - then I would say yes.
    Let consider this - You have received a message in the BPM and this message has to be called on two different systems synchronously. In this case Both the synch step will have the Source interface as the message received in BPM correct? Does the 2nd Synch step Source Interface is dependant on 1st Synch step Target Interface? - NO.
    I hope it clears a bit.
    I'm not understanding your other question...

  • 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

  • Interface Determination under Enhanced Receiver Determination Scenario

    Hi,
    One of the very basic assumption for Enhanced Receiver Determination is that Receivers are found at run time, and one of the such requirement is that we don't know about Receiver  Business System at the time of configuration.
    Now for such scenarios, how do we configure "Interface Determination". For Interface Determination one of the input filed is "Receiver Service/Party", in addition to "Sender Service/Party" plus "Sender Interface"
    Since we don't know Receivers at config, what value(s) should come in "Receiver Service/Party" in Interface Determination at config time.
    Thanking all of you in advance

    Hi Rajan,
    You have to do the following things:-
    First, maintain Database Table in SAP XI. Which contains several keys like Sender, Receiver system and then according to that key combination we perform a JCO call and fetch the values which gives us the correct receiver and interface.
    Create a Data Type which will be having Two elements Service And Interface.
    Now careate a message type and message interface for this data type. This will be for your receiver.
    Then use source payload and perform a message mapping between Sender Payload & this Message Type.
    Use UDF and make a JCO call and fetch table entries for service and interface.
    Then in Directory perform extended determination and use this mapping into it. The result will be Service & Interface.
    Thanqs
    Biplab

  • Conditional Interface Determination with Flat Files

    Hello,
    I have one sender interface (dummy) which could either hold a flat file or an XML file. On receiver side there is one system with two receiver interfaces, one should be used for the XML structure and one for the flat structure.
    My requirement is to have a conditional interface determination with an (exclusive) OR logic. Pseudo code:
    The XML structure has "submission" as root node. So I use the condition (/submissioin) EX to determine whether it is an XML file and I check with not(/submission) EX to determine whether it is a flat file. However the condition does not work using a flat file ("Unable to find an inbound interface"). Could it be, that the conditional expression never is true in case a flat file arrives? How can I achieve this requirement?
    What I additionally do with the flat file is just calling a Java Mapping that sets dynamic attributes for a file receiver, the flatfile itself is dumped on a file system without any addtional conversion logic.
    Thank you for your advice.

    How can I ingnore a message in case a condition applies? I am just aware of the fact that you can ignore messages in case NO condition applies.
    Couldn't you simply reverse the logic and use "not equals"? Or perhaps you can use the EX operator to alter your conditions... here is more info on the EX (exists) operator
    Re: ConditionEditor: Check if element is empty
    What is best practice in this case? Should I use a "dummy receiver"? However if I use a dummy receiver I think I would receive a "interface determination not found" error. How would you do that?
    I've never found the need to work with dummy receivers so I cannot comment there.

  • Condition based Interface determination

    Hi ,
    Environment : PI 7.1.
    Scenario : File to Proxy.
    In this scenario , We have a single file interface which reads a file and routes the data to two different inbound interfaces.
    Steps followed to do this -
    >>Defined two inbound interfaces interface1 & interface2.
    >>Both interfaces are pointed to same ECC system.
    >>Read the file using a single sender file communication channel.
    >>Define receiver ECC in the receiver determination.
    >> Define interface determination based on a value of a field in the file structure(source structure). Used XPATH to define this content based routing and selected operation mapping specific to the interface.
    1 sender agreement
    1 receiver determination ( not using enhaced receiver determination because we have only one receiver)
    1 interface determination which has two receiving interfaces based on XPATH condition ( maintain order runtime is checked)
    2 Receiver agreements.
    2 Communication channels.
    For example if you have 10 lines in a file , out of which if 5 lines has a value related to interface 1 & 5 lines has a value related to interface 2. It should push the data into two different proxies as configured.
    We are facing a problem in this scenario -
    There is no consistency in the logic. Some times it runs interface 1 & some time it executes interface 2.
    based on condition 1 it routes the data to interface 1 successfully but the structure is not getting created for interface 2 so it is giving an error stating the interface 2 structure is not available.
    In SXMB_MONI the branching steps show two subnodes but if you see the log it shows that in subnode 1 the sender is sender interface & the receiver is interface 1 based on the filter condition. If you see the log for subnode 2 then it shows the sender is sender & the receiver as interface 2 below that it shows another entry which shows the reciver interface is interface2.
    Please evaluate and let us know if the approach we are following works or not. If there is any limitations please let us know how to achive this.
    Regards,
    Reddy

    Hi,
    Your design is correct but here you missed one point. Here the message is send either to receiver1 or receiver2  depending on the condition but not both. As this does not result in multiple messages with the same payload because only one condition can ever be true at runtime. For more details see the below link
    http://help.sap.com/saphelp_nw04/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
      If you want to create multiple message then you need do 1:n mapping :
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID2056393550DB10021342992851308291End?blog=/pub/wlg/2927
    Shweta.

  • XI Receiver Adapter: No receiver could be determined

    Hello guys,
    I'm at the moment connecting Contract Accounts Receivable and Payable 6.00
    http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm
    My scenario has a XI Receiver Adapter. I have set up the receiver agreement, Interface Determination and Receiver Determination as it says in the link provided.  I have succesfully tested the configuration with the TEST CONFIGURATION TOOL in ID.
    But at the moment of testing a real message, I'm getting in the SXMB_MONI the following error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>No receiver could be determined</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Does any one knows why if the configuration is correct (according to me and the test tool), I'm getting this error?
    Thanks for your help.
    Felipe

    Hi guys,
    I have resolved the issue.  Aamir you were rigth, the problem was with the sender attributes.
    What happened was that the sender Interface namespace was a differente one from the one in the configuration. In this link
    http://help.sap.com/erp2005_ehp_02/helpdata/en/9c/0d03d4beeb40848e15329b4e63976e/frameset.htm it said that the namespace had to be http://sap.com/FICA/Global, but it was using the namespace http://sap.com/xi/PI/FIN/Operational/Global, so I just need it to change.
    Thanks guys for your support.
    Felipe

  • 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