cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC-AAE receiver channel error in SAP PI 7.4

0 Kudos

Hello experts,

We are working on a File to IDOC scenario using a receiver IDOC-AAE adapter. The version we are using is SAP PI 7.4 JAVA single stack.

When this scenario is executed an error is thrown at the IDOC receiver channel as below:

Transmitting the message to endpoint
using connection File_http://sap.com/xi/XI/System failed, due to:

com.sap.aii.af.idoc.exception.IDOCAdapterException:
IDoc: Connection factory name for channel CC_IDOC_RECEIVER is null',

We tried all the possibilities to resolve this issue; Applied Default, Manual and From NWA options in IDOC-AAE channel. but nothing is working.

Please help us in resolving this issue.

Thanks in Advance

Nishant

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Nishant,

Instead of naming the receiver channel as CC_IDOC_RECEIVER, name it as 'GeneratedReceiverChannel_IDoc'.

Hope this works!!

Best Regards,

Souvik

abranjan
Active Participant
0 Kudos

Hi Nishant,

Don't know if you were able to resolve this issue or not. If not, then you can try refreshing the cache (comm channel) from ID. Even if the cache is updated/in green, update it again and see if the issue is resolved or not. It might help.

Regards,

Abhishek

Former Member
0 Kudos

Hi

Apply SAP note 1653715.

Check this for more details

iDoc_AAE Receiver Channel Error | SCN

0 Kudos

Hi Indrajit,

The note is holding information about a different error. This error Connection factory name is null is not answered in that.

Nishant

Former Member
0 Kudos

Hi

The thread I have mentioned having the same error description and it has been answered with the note

number I have mentioned.

Please give it a try and see if that works or not.

former_member184720
Active Contributor
0 Kudos

Look for the suggestion provided by Dimitri in the below thread -

Also If you had gone through the thread shared by Indrajit,even the user had to correct the RFC destination to resolve the issue.

So you might want to validate your configuration again..