cancel
Showing results for 
Search instead for 
Did you mean: 

lookup of alternativeServiceIdentifier via CPA-cache failed for channel

Former Member
0 Kudos

Hi All,

Does anyone encountered this before?

Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_Rfc_Outbound' (dd6b294c0da6368c9b898d34fb18d246, party '', schema 'TechnicalSystem', identifier 'EQ1#100')

Some Interfaces using an RFC Sender Channel are encountering error but not all other are working fine.

Regards,

Alfred

Accepted Solutions (0)

Answers (1)

Answers (1)

prateek
Active Contributor
0 Kudos

Open the bussiness system associated with this RFC channel in ID. Then goto "Service" -> "Adapter-Specific Identifiers" and check whether ther value of client and System ID are appropriate or not.

Also perform a full CPACache refresh with PIDIRUSER.

http://XIHost:Port/CPACache/refresh?mode=full

Regards,

Prateek

Former Member
0 Kudos

Hi,

Yes the setup their is correct.

Regards,

Alfred

Former Member
0 Kudos

Hi Prateek,

I think the value of the logical system is diffent from what is in SLD business systems. But it's wierd because what I know is that we just press the button "Compare with SLD" and then you will get the value in what is configured in SLD. In our SLD MQACLNT100 is defined their but in ID when we retrieve the logical system it gets a different value. Before logical system in SLD is really wrong and we just changed it is it because we still need to do some refresh or something to get the correct value in order to prevent the error message I've show you above.

Regards,

Alfred

Former Member
0 Kudos

Hi Alfred,

Please cross-verify below items and also perform full CPA Cache refresh (http://<servername>:<port>/CPACache/refresh?mode=full).

1. 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.

1.a. - In change mode, you will also have a button for comparing with system landscape.

1.b. - Also please check the Business System in SLD to make sure that it's correct configured properties like - Business System

Type, etc...

2. 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".

3. If a non-ABAP system is used to send RFC-calls to the RFC-Adapter sender channel it may is not possible to set the SYS-ID and CLIENT values in this external RFC client. The checking of these values can be disabled in the 'RFC Server Parameter' settings in the sender channel. Choose 'Advanced Mode' and deselect 'Verify Sender System'

4. Check if you are using the same program ID in multiple scenarios. Maybe is you keep different the program ID names in

different RFC adapters

5. If all these does not solve, Please perform RZ70 in the Source System to re-register all the values in SLD and then perform full CPACache refresh (url mentioned at top).

Thanks

Sekhar