cancel
Showing results for 
Search instead for 
Did you mean: 

InterfaceDetermination did not yield any actual interface

0 Kudos
4,501

Hello All,

Can anyone please help on below topic?

We are receiving below highlighted error.

Transmitting the message to endpoint {2} using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface



System Details: 1. We are using PO 7.3 Single stack

2. Scenario - IDOC to File(Using HTTP Adapter)



In Iflow, all the conditions are maintained properly.

Thanks & Regards,

Rajni

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member186851
Active Contributor

Hello Rajni,

Try removing the SWCV from ICO and check.

also ensure the objects are in place and cache is up to date.

0 Kudos

Hello All,

Thank you so much for your valuable inputs.

Removing SWCV means? I tried to remove whole configuration from Iflow and then deployed it.

And then again enter whole configuration but no luck.

Issue still exist and cache is also ok.

former_member186851
Active Contributor
0 Kudos

Are you using any message split here?

manoj_khavatkopp
Active Contributor
0 Kudos

Please add the screenshot of the message log so that to see at what step you are getting this error ?

Below is screenshot to remove SWCV.

0 Kudos

Hello Manoj,

We analyzed and reached to the point where exactly the error is occurring.

In Iflow, we are maintaining payer number in receiver determination condition from our end.

So I tried using another customer's payer number instead of actual payer number and it was successfully delivered the message to an endpoint.

So actual issue is with the payer number, but i don't understand what could be the reason, as IDOC is successfully transmitted from ECC side.

Kindly suggest some solution.

Regards,

Rajni

former_member190293
Active Contributor
0 Kudos

Hi Rajni!

Please provide your Interface determination screenshot along with source XML fragment containing your payer's number.

Regards, Evgeniy.

manoj_khavatkopp
Active Contributor
0 Kudos

How are you converting the IDOC-XML to File ? if you are using Module in the receiver channel cross check the message type and namespace mentioned in the module with your actual ESR message type.

If you are using Java to convert IDOC-XML to file then as mentioned remove the SWCV in receiver interfaces and outbound processing tab in ICO. Make a dummy change in ICO re-activate it and try again.

GauravKant
Contributor
0 Kudos

Hey Rajni,

Check receiver interface tab details of ICO and make sure it has correct details. Also check the cache status.