Skip to Content
0

IDoc_AAE sender communication channel is not found

Dec 21, 2016 at 03:37 PM

667

avatar image
Former Member

Hi Experts,

I configured a PI scenario and sent an IDoc message from an ERP system to the PI system. The message stucks in SM58 of the sender system. The PI NW Adminstrator Log Viewer shows the reason: "IDoc_AAE sender communication channel is not found" - but there is a IDoc_AAE sender channel for this Business System.

The ERP system was created by system copy - i guess this might be the deeper reason, but i cant find out what to change to get the IDoc communication working.

Thanks for you help,

Udo

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

6 Answers

Evgeniy Kolmakov Dec 22, 2016 at 03:04 AM
0

Hi Udo!

Maybe you should check inbound resource adapter's settings and destinations in NWA as well?

Regards, Evgeniy.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Dec 22, 2016 at 11:16 AM
0

Hi Evegeniy,

thanks for the quick response. I checked and tested all destinations related to IDoc traffic between ERP and PI and checked as well the resource adapter settings, but i could not identify anything suspicious. Everything looks fine and i can compare the settings with the settings in our development system.

So i guess something went wrong in identification of the sending ERP system. Somehow PI cannot identify the ERP correctly and is giving in consequence the message that for the sending system there is no idoc sender adapter. This is at least my assumption but i dont know how to validate it and how to find out exactly the way of identification and finally i dont know how to solve the issue.

/Udo

Share
10 |10000 characters needed characters left characters exceeded
Manoj K Dec 22, 2016 at 04:09 PM
0

Udo,

Usually you get this error when you dont have an ICO for the corresponding Idoctyp.msgtyp.extension try to reactivate your ico again if its existing and also try to do a sender idoc ping channel.

If the issue persists restart the inboundRA.

Br,

Manoj

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Dec 23, 2016 at 08:55 AM
0

Hi Manoj,

thank you for your very interesting answer.

I checked each point, but unfortunately without success.

1. I compared Idoctyp.msgtyp.extension in WE02 with the values in our development system, exactly the same

2. I checked if the ICO is matching the IDoc and reactivated the ICO.

3. I pinged the channel and restarted it.

4. The inboundRA was again saved - as there is no restart button - I think that is what you mentioned

But the issue still exist. I would really like to find out how PI is identifying that the message comes from a certain ERP system, so how does PI get the Business System which is sending? If i could monitor this i guess i might be able to come closer to the reason.

/Udo

Share
10 |10000 characters needed characters left characters exceeded
Alberto Maeso Díez Dec 21, 2017 at 10:59 AM
0

Hello,

I have came across the same issue. The idoc communication was working for all the idocs, but suddenly one idoc is failing with this error.

How did you solve it?

I have re-redploy the ICOs and I am still facing the same error.

Regards,

Alberto.

Share
10 |10000 characters needed characters left characters exceeded
Liz Jin
Dec 23, 2017 at 06:05 AM
0

Hello Udo,

The IDoc_AAE sender communication channel is retrieved from the cache of the backend ERP system, to the smooth replication, in PO Integration Directory, find the corresponding Business System and there will be a tab called Logon Data, please make sure you have configured the PIDIRUSER and correct password. Please check the following help and screenshot in details.

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/cfd1d49bf23e49e10000000a421937/content.htm

2016-09-19_14-23-51.png

Best Regards,

Liz

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

Hi Liz,

I am facing the same issue. I have tried the solution you shared where the Logon Data is configured in the corresponding sender Business System.

This is part of our migration effort to PO 7.5. The non-B2B IDocs (sender partner type LS) are being successfully received in PO. We are only facing this issue for B2B IDocs (partner type KU/LI). I have tried a couple of configurations:

1. Sender party is NOT configured for business system.
-EnableDefaultSenderParty property in JavaIDoc Resource Adapter set to true
-DefaultSenderParty is blank
-ResolveVirtualReceiver set to true
-Identifiers are set in the receiver Party and Sender IDocAAE Communication Channel

2. Sender party is configured for sending business system
-EnableDefaultSenderParty property in JavaIDoc Resource Adapter set to false
-ResolveVirtualReceiver set to true
-Identifiers are set in the sender and receiver Party and Sender IDocAAE Communication Channel

However I am still getting the error below in both cases. Is there another solution to this issue?

com.sap.conn.idoc.IDocRuntimeException: IDoc_AAE sender communication channel is not found
0