Skip to Content
1

Interface Determination cannot be found anymore. Manual action is required

Jan 16, 2017 at 08:19 AM

655

avatar image

Hello Everyone,

I have one Interface of Scenario SFTP to Proxy. This interface was failing due to a mapping issue. I fixed the mapping error by changing the mapping accordingly and when I try to resend the message, I am facing the below mentioned error.

mapping "<unknown>/<unknown" failed to execute Routing Exception: Interface Determination could not be found anymore. Manual action is required

Attached is also the detailed error which I am facing.

Can you please help me resolve this error at the earliest?

Regards,

Nitin Deshpande

10 |10000 characters needed characters left characters exceeded

Hi Nitin,

we are facing the same issue can you please let me know the solution if you have

we have a Scenario ERP to C4C via PI, from last two days Outbound IDOCs are not processing but Inbound IDOCs were processing good,

we are getting error as "Cannot retrieve InterfaceDetermination to find receiver agreement for determining the VirusScanConfiguration due to: InterfaceDetermination cannot be found anymore. Manual action is required"

please see attached snapshot of error-log.jpg

error-log.jpg (129.5 kB)
0

could you please help us

Thanks inadvance

0
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Mark Dihiansan May 02, 2017 at 01:54 AM
2

Hi,

Please check 1948123 - AAE: Tool to repair messages which are undeliverable after structural changes to Integrated Configuration

Regards,

Mark

Share
10 |10000 characters needed characters left characters exceeded
Moritz Feuerbach Jan 16, 2017 at 09:55 AM
0

Hi Nitin,

did you change the mapping itself or did you create a new one?

Also, try and do a cache refresh if you did not already. Then retry.

Kind regards

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello Moritz,

I just changed the mapping, i did not create a new one.

Regards,

Nitin Deshpande

0
Raghuraman S Jan 16, 2017 at 09:57 AM
0

Are you using any condition based routing Nitin?

Show 3 Share
10 |10000 characters needed characters left characters exceeded

Hello Raghu,

No, i am not using any condition in routing the message either in Interface determination or Receiver determination.

Regards,

Nitin Deshpande

0

Ok Nitin,

Then as Manoj suggested there could be some problem with FCC parameters which is resulting wrong formation of XM

0

Hi Raghu,

I have the same issue as Nitin mentioned. 

we have scenario like ECC to C4C via PI,till the last week all the interfaces are working fine. but now we are facing a issue only in Outbound IDOCs, after mapping execution the messages are getting failed as

"using connection IDoc_AAE_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to create listener AFWListener for connection IDoc_AAE_http://sap.com/xi/XI/System. Reason: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Failed to lookup object from JNDI for name AFWListener. Reason: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of AFWListener. in PI

as I tried more but i can't see any related blogs,

i have attached the message log and error log viewer,, please review and help us

Thanks in advance

Best Regards, log-viwer.jpgmessage-log.jpg

Ramana Kola

log-viwer.jpg (146.3 kB)
message-log.jpg (85.5 kB)
log-viwer.jpg (146.3 kB)
message-log.jpg (85.5 kB)
0
Manoj K Jan 16, 2017 at 01:18 PM
0

Nitin,

If you are using FCC/MTB in sender SFTP channel make sure you have mentioned correct message type and namespace over there .

Ideally the XML which is appearing in your interface determination should match you Message type mention in your outbound service interface.

Or Try removing SWCV from Interface determination.

Br,

Mnaoj

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello Manoj,

I am facing the problem only with the old messages which are in system error status due to failure of mapping. All the new messages are getting processed in an expected manner.

When i try to restart the old messages which are in error i am facing this problem.

And there is no FCC used. Sender Interface structure matches the data format of the file.

Regards,

Nitin Deshpande

0