cancel
Showing results for 
Search instead for 
Did you mean: 

strange:alternativeServiceIdentifier via CPA-cache failed for channel

Former Member
0 Kudos

Hi all,

I have setup a simple RFC->XI communication channel.

SM59 works fine.

Now I get the following error in adapter engine

<i>Error: 2006-09-04 11:59:07 CEST: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'EU_RFC_SND_XYZ_100_VAT' (be242c9c7c423e71bc33c269521a070b, party '', schema 'TechnicalSystem', identifier 'XYZ#100'</i>

business System Service is checked for adapter specific identificators <b>according to OSS Note 730870</b>-everything ok from this side.

Caches are up to date.

Do you have any idea?

(I have setup a similar communication channel for our dev system..without any problem...now on XYZ our qual system the channel is not working:-(

)

thanks in advance

jo

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

problem is solved by deactivating the checkbox

'check sender system' in the rfc communication channel configuration.

Former Member
0 Kudos

Hello,

I've got the same error and also if I deactivate this checkbox

the error doesn't appear anymore. But the SAP documentation says that

I can deselect this checkbox, if the calling system is NOT a SAP-System.

But the RFC call is raised by Enterprise Portal and so it should also

work with this checkbox!!

I did the adapter specific identificators check like SAP note 730870 says,

but the R/3 System ID and the Client field are empty. And I can't do a

comparison. So why it isn't filled?? I checked my Business system and

technical system but can't find any field to fill these information. I can see, that the field client in my Business system is empty, but I can't edit it.

Any ideas how can I do this?

thanks

chris

Message was edited by:

Christian Riekenberg

Former Member
0 Kudos

Hey,

strange thread. Everyone find a solution for himself. Like this Thread:

I also have to use a Business System based on a Web AS ABAP and not

on Web AS Java.

It's logical, because the RFC communication needs an ABAP stack.

thanks

regards

chris