Problem RFC sender

[Former Member]

Hello,

I have a new Problem about a sending RFC in XI.

Once I send a test-RFC from R/3 se37 it reaches the rfc sender channel but there I get an error in cc-monitoring(the same is displayed in R/3 then as well).

The error says:

Processing error caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_RFC_sender_RFC2JDBC' (104238c5fe4c345e8e85752a84330c5c, party '', schema 'TechnicalSystem', identifier 'E10#400')

Can you help me?

I don't understand the error.

CPA-Cache Refreshs do not work.

[Former Member]

Hi,

if you need to refresh the Adapter cache have look at this:

[;

Regards

Emiliano

[prateek]

Refer SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15

Regards,

Prateek

[Former Member]

Where do I find SAP Notes? I did not use them before.

thanks.

[former_member208856]

Hi,

for checking the SAP note, login on service.sap.com

for clear the cache please use tcode sxi_cache. Please check your communication channel in SXI_CACHE before refreshing cache.

Regards,

Sandeep Kaushik

[prateek]

I hope u have service marhetplace id

http://www.service.sap.com/notes

Regards,

Prateek

[Former Member]

unfortunatley I don't have one I am doing my internship at the moment.

[prateek]

Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?

A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".

* Give correct appserver and gateway service details in XI.

* Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..

Regards,

Prateek

[Former Member]

thank you for posting the note.

I read this. So could there be a problem regarding that the used Business System is defined for client 100. The user I have for login in r/3 (that one I provided in the rfc cc) is for use with client 400. The User I use for sending the RFCs in R/3 is for client 400 as well.

Is this the problem?

thank you for your help.

[Former Member]

Hello,

I just got my Business System for Client 400 so everything should fit. But now when sending the rfc I get this message: alternativeServiceIdentifier: party/Service from channel configuration are not equal to party service from lookup of alternative.

Could there be a error at senderagreement?

Testing tool in ID says it won't find senderagreement.

DO you know where the error is?

[Former Member]

problem solved

[Former Member]

Try to refresh Adapter Cache.....again activate the channel and test it.

thanks

farooq

[Former Member]

Hi,

where do I refresh Adapter Cache?

restarting the channel in cc-monitoring didnt have a effect.