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

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

Receiver Determination - Configuration Overview for Receiver Determination

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

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

"Problem evaluating a condition" at Receiver Determination

Hi,
I've created a complex mail to rfc interface, in which, message is being send as mail attachment and service inbound interface has multiple operations (each for corresponding rfc).
at Receiver Determination, rule was created with multiple conditions, in order to determine correct "Communication Component" (multiple receiver agreement and interface determination were created to supported this "multi interfaces" scenario).
If no receiver was found message is ignored.
once in a while, bad non-xml messages (e.g., "asdfasdfasdfffdfdsasdf") are being send, is this case, while PI is trying to determining the receiver (i.e., evaluate Receiver Determination conditions) exception is being thrown, message is therefor has system error status* (at sxmb_moni) and it can not be ignored (as i wanted it to be).
how can i workaround this problematic scenario?
Regards
Uri
*Error message (sxmb_moni)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Abhishek,
10x for your replay, but as far as i understand this is exactly the case here.
conditions are:
cond1: (/rfc: RFC1 ~ *)
cond2: (/rfc: RFC2 ~ *)
this works as expected in cases of xml messages (in case no cond is satisfied) message is ignored. but, in case of non-xml message exception is being thrown while cond is assessed.
Regards
Uri

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

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
Interface Determination
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.
 ReceiverDeterminatioin.
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
** REward Points if found useful **

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.

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

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. Standard receiver determination 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:
● Select the receiver from the Integration Directory
● 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).
Enhanced receiver determination 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.Standard Interface Determination :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*

Receiver determination step in the BPM and multiline container

i have made a file2file scenario where:
there is a BPM,
the BPM has a send step which contains a receive step,
a transformation that mapps the incomin message to two messages(Split-messgae case),
and then a FORK step which sends the two messges to through 2 SEND steps to the intended receiver services.
It didnt work......and i followed a blog-> /people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure ............... which suggested to have a
"receiver-determination" step in the BPM before the SEND step.... it says that this
"receiver-determination" step will put the message in a MULTILINE container..
i m confused bout this step ........ can anybody explain.....
please help

HI,
In receiver determination step selctthe multi line container element.in container editor create the one element with type as receiver and select the check box.
A Receiver Determination step returns set of receivers configured for the output abs interfaces in the directory and puts it into receiver which is a multiline container receiver element
Regards
Chilla

Dynamic Receiver Determination [W/O using BPM] Sync interface

I have been exploring options w.r.t. performance sensitive service interface.
This has following issues :
1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.
2. Prominent answer would be Enhanced receiver determination step but that doesnt work in sync case.
3. Classic Receiver Determination needs the condition to be evaluated in source msg. which is not going to happen.
4. Use BPM i designed one but performance its not all acceptable it has a round trip of 10Sec.
are there any ways to overcome this ?

Hi Bujji,
can you explain the point 1.
1. Gets a org code looking up instance and route the msg. accordingly to an RFC and get response back.
Thanks and Regards,
Himadri
null

Receiver Determination and Interface Determination

Similar Messages

Maybe you are looking for