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,
>In both the case we specify sender -> outbound interface -> Receiver Service - Interface mapping
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

Similar Messages

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.

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

INTERFACE MAPPING wa not Displaying in Receiver Determination (Extended)

Hi friends,
I'm doing Enhanced Receiver determination.. but in this if i select Extended radio button in the receiver determination .. I'm not gettting any search help for selecting my Interface mappings..
what misteqe i did.. for getting those interface mappings in Receiver Determination does we need to do..any special things .
i followed the bellow blog.. but like that i'm not getting... and how many interface mappings do we need to create for this..
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
plz suggest me..
thanks
BABU

how many interface mappings do we need to create for this..
One
Make sure u have activated ur Interface Mapping. Also recheck the sender interface and the interface u r selecting in Interface Determination step.
Regards,
Prateek

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 not 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.
MONI for RD
- <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.
MONI for ID
<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

Enhanced Receiver Determination for synchronous interface.

Hello!
Was anyone faced with the Enhanced Receiver Determination? When I try to create
the definition of the Interface Mapping, I get the error:
"Interface modi are different. Source interface Message Interface MI_My_sync_iface | urn:my is synchronous. Target interface Message Interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous"
Thank you.

Hi ,
U can go through below limks :
Illustration of Enhanced Receiver Determination - SP16
SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios
Enhanced Receiver Determination in SAP XI - Exchange Infrastructure - Wiki
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/enhanced%2breceiver%2bdetermination%2bin%2bsap%2bxi
Thanks

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
 <gesellschaft>03</gesellschaft>
 <filiale>000</filiale>
 <satzart>11</satzart>
 <datum>00000000</datum>
 <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

Message Interface not found during Receiver determination

Hi Folks,
While doing Receiver determination i found this error
Problem Loading Schema Description: Message interface does not exist in any software components installed on this business system
i checked it in SLD also for Product assigned to Particular Business System. Even i tried with creating a new one and assigning the product and software component to it.
When i imported the Business system from SLD, i m not able to see any inbound and outbound interface for particular business system.
But it is working for another scenario where inbound interfaces are used.
plz help me out
Sachin

Sachin,
>DEV and QA is having diff. SLD so i created the SWC and products in SLD again.
You should export the SWCV from your Old SLD and import in into your new SLD.
and then import the same in Integration Respository.
When you try to export SWCV from SLD, you will get a .CIM file which you need to save in your local desktop and then import this in the new environment.
More in this article,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Regards
Bhavesh

ACK for receiver determination with 2 interface determination

Hi Forum,
I have a XI scenario, with a BPM, where i have a Send step,
this send step corrsponds to a receiver determination in Configuration, and this receiver determination has 2 interface determination,
because the send step is like,
BPM to Receiver1, through sender message interface MI_Sender1, but there are 2 different receiver message interface namely MI_receiver1, and MI_receiver2,
.......hence 2 interface determination and 2 interface mappings accordingly,
and now when in BPM, i choose "transport acknowledgement" for this send step, my BPM stucks while waiting for the acknowledgement, but...in MONI, i am receivng both the acknowledgement, but in PE, workflow descrition, it waits for acknowledgement and finally fails,
what's the reason,

check the workitems of both sender/receiver (ack) in moni (problem might be in BPM config).

Interface Mappings are not displayed in Receiver Determination

Hi friends,
 I'm doing Enhanced Receiver determination.. but in this if i select Extended radio button in the receiver determination .. I'm not gettting any search help for selecting my Interface mappings..
what misteqe i did.. for getting those interface mappings does we need to do..any special things .
i followed the bellow blog.. but like that i'm not getting... and how many interface mappings do we need to create for this..
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
plz suggest me..
thanks
BABU

Hi Prabhu..
 Thank you for ur spontenious respnose ..I Mentioned the receiver business services in the user defined function which i creted in the message mappings .. is there any other place also do we nned to mention..
actuvally , i have one source struturce that and Two Receiver strutures..
1) Sendor_DT
 PERSON
 NAME
 AGE
 ADRESS
2) Receiver_DT_1 ( this is for Male person details )
 PERSON
 NAME
 AGE
 ADRESS
3) Receiver_DT_2 (this is for Female Person Details )
 PERSON
 NAME
 AGE
 ADRESS
for this.. i created Three message mappings.. ( one for soource to first recevier )
and next for ( source to second receiver)
and for third for source to RECEIVERS ( MESSAGE TYPE FROM SAP -BASIS component )
in the mapping
i created one user defined function and i map that to split message..
in that user defined function i wrote the bellow coding
int i;
int mr=0;
int ms=0;
for(i=0; i<a.length;i++)
 if( a.substring(0,2).equals("Mr") && mr==0)
 result.addValue("AATRNG_TEST_4_BS_IB1");
 mr=1;
 if( a.substring(0,2).equals("Ms") && ms==0)
 result.addValue("AATRNG_TEST_4_BS_IB2");
 ms=1;
</textarea>
and i created two interface mappings .. and i created three business services.. three communication channels. and two recever aggriments.. and two interface determinations .. and one sendor aggriment and receiver determination with EXTENDED . and i used those interface mappings in recever detrmination ....
but why file was not loaded into receiver side..
thanks
Babu

Receiver determination not found for one interface

Hi,
I am receiving the message via SOAP and then sending to SAP as IDOC.
The communication is party o partyless communication.
I have configured 2 receiver determination for the same sender and receiver but with 2 different interfaces.
When i test the scenario via SOAP tool only one gets executed and the second one neither throws an error nor getting executed.
I think i have a error in the configuration that i did for the 2nd interface since i am using the 1st receiver determination which has been created already ?
but in the Quick Test tool and Test tool in ID both the receiver determination is working fine.please provide the inputs
Thanks in advance,
Rgds,
Vasanth.

Hi All,
Thanks for all of your replies.
I have activated all the objects and checked it again once.
As i said earlier the sender and receiver are same and that's why i have been pushed to create 2 receiver determinations for the same file(not IDOC as i said above) to be dropped in to two different locations.
Also the configuration is party in sender to partyless in receiver.
To give a clear explantion:
All the objetcs are activated and works fine when i test in the test tool in ID by specifying the inetrface and namespace.
Sender1 - Int1 - sap1.com - SA - RD - ID - RA -Receiver1 = working fine when tested by ID test tool
Sender1 - Int2 - sap2.com -SA- RD - ID - RA Receiver2 = working fine when tested by ID test tool
RD = Receiver determination / SA = Sender Agreement
It is not working when i send the same file thru SOAP client tool and only one receiver determination is working and another is not.
Any idea ?
Thanks,
RGds,
Vasanth.
Message was edited by:
Vasanthakumar Balasubramani
Message was edited by:
Vasanthakumar Balasubramani

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.

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 Vs Interface determination

Similar Messages

Maybe you are looking for