Inbound interface found several times (for same sender and receiver)

[Former Member]

Hi,

I have this error in PI. when using message split in interface determination.

<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="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>

<SAP:P1>Inbound interface found several times (for same sender and receiver) for the outbound interface http://XYZ/PaymentData.PaymentData_Async_Out</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error when determining the inbound interface: Inbound interface found several times (for same sender and receiver) for the outbound interface http://XYZ/PaymentData.PaymentData_Async_Out Inbound interface found several times (for same sender and receiver) for the outbound interface http://XYZ/PaymentData.PaymentData_Async_Out</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Help is appriciated.

[baskar_gopalakrishnan2 · Accepted solution]

What is your PI version? Are you using PI 7.3 java stack?  Just few cents...

If you use message splits and the receiver adapters are in both adapter engine and integration engine then this would not support. You will get this type of errors.  Plus if you use abap proxy then it will not support multimapping too. When  you describe errrors, I would recommend you to provide more details to the problem.

refer help link for multimappings

http://help.sap.com/saphelp_nw04s/helpdata/en/42/f3b31d48fb1bc8e10000000a11466f/content.htm

Example:

If you use PI 7.1 and if your receivers say example: http , file and idoc then this would not work. Message split could happen only if the adapters that comes in the adapter engine. idoc and http are in the abap stack in pi 7.1

Hope this helps

[Former Member · Accepted solution]

Thanks Baskar,

I'm on PI 7.1

and My scenario is one file sender and two receivers: file receiver and Mail receiver.

I have given details above in the reply, to greg.

and using

ESR:

2 operation mapping with diffrent service interface and messageType

ID:

1 sender Agreement

1 recvr determination

1 interface determination

2 recvr agreement.

3 commincation channels

[baskar_gopalakrishnan2 · Accepted solution]

Are you using enhanced interface determination ?  Do you have conditions in the interface determination? You can also refer this link for the enhanced determination.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90dcc6f4-0829-2d10-b0b2-c892473f1...

Please refer multiple inbound interfaces section

Suggestions:

You can reference both service interfaces in the same operation mapping in target side and create just one OM. And one mapping object for both as given in the above link too.

[Former Member · Accepted solution]

Baskar,

I'm on 7.1,  so Enhanced Determination is already taken care.

and I dont want to give any condition, both interface should run all the time. if i give dummy condtion which is true for one and false for other it will work; but again it wont run if make condition true for both; it gives the same error.  is there a way i can make both run or is the only way to have diffrent recvr component all together.

Thanks for your time.

[former_member184681 · Accepted solution]

Hi,

Correct me if I'm wrong, but I think you only use Enhanced Interface Determination for mapping-based message split (multimapping without BPM). For your scenario (two separate operation mappings), simply switch to Standard Interface Determination and it should be fine.

Hope this helps,

Greg

[Former Member · Accepted solution]

Thanks Greg,

i unchecked "Maintain order at runtime" that is Switching to Standard Interface Determination, this did not work for me..

[rajasekhar_reddy14 · Accepted solution]

Hi ,

Create two bussiness components for Mail and File and create two interface determinations , definetly ti works.

I used interface determination with multiple mappings for one type of cumminjctaion channel but in your case it is different may be that is causing the issue but not sure this is a limitation or not.

Best Regards,

Raj

[Former Member · Accepted solution]

Thank you Raj. that is what i was going to try.

But I'm afraid, what if one interface runs sucessful, and anotehr fails? that doesnt serve my purpose.

example.. if my file interface creates 2 files but mail adapter fails for some reason to deliver emails OR for some reason File adapter fails but there is email delivered saying there are 2 files created today. then that is wrong info to business folks..

wondering is there any way, PI can send email only if there are files created.

[rajasekhar_reddy14 · Accepted solution]

If that is the case then devide requirement in to two different interfaces , first place file FTP using first interface, then develop file to mail interface , poll FTP directory if file found in directory then use receiver mail adapter to send an email.

This is very easy process.

[Former Member · Accepted solution]

Ya that would work too but, i have another dependency there; once the file is placed in directory, there is another interface which will read these files and acrhive it..

[rajasekhar_reddy14 · Accepted solution]

Create one more dummy directory place files in original and dummy and File to mail scenario should poll to dummy directory. this should work.

However consider below replay only because vry rare case you may face Communication channel errors.

Raja Sekhar Reddy        May 3, 2012 5:18 PM                                    (in response to Prema Boodi)               

[Former Member · Accepted solution]

Raja, i considered your solution to the problem:

-------

Create two bussiness components for Mail and File and create two interface determinations , definetly ti works.

-------

But there was situation where the email was sent saying the files were created but the File interface failed due to wrong password in the File communication channel and error email was ALSO sent.  So we are giving wrong info to the business folks, this is related to FI. its sensitive; cant give wrong info.. thats the reason i have opened another thread: 

http://scn.sap.com/thread/3190363   

closing this thread

[former_member184681]

Hi,

Most probably you have mutliple interface determination for your scenario. For instance, you could have one ID for: Sender System | Sender Service Interface | | * (all receiver systems) and one more "specific", like: Sender System | Sender Interface | | Receiver System. In this case, PI doesn't know how to determine the right ID to be used and throws an error.

You can check the Configuration Overview in Receiver Determination or Configuration Scenario to confirm that.

Hope this helps,

Greg

[Former Member]

Thanks Greg,

here is my configuration. but i see * infront of CommChannel,