lookup of alternativeServiceIdentifier via CPA-cache failed for channel

[Former Member]

Hi,

In RFC(ECC) to File(PI) scenaio i am facing the following error in sender CC:

Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC

-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')

I have done the following for RFC to File scenario:

ECC side:

1. Created a RFC and tagged it to BAPI

2. In the ABAP program, i am calling the RFC like below:

CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'

IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'

• EXPORTING

• INTERFACE =

IMPORTING

FILENAME = FILENAME

RETURN = RETURN

TABLES

ITAB10 = ITAB10

P_STATUS = P_STATUS

.

COMMIT WORK.

3. Created a RFC destination using SM59

RFC detination : Z_HR_OUTBOUND_DATA2

Connection type : TCP/IP

Enabled Registered Server Program

Program ID : ECCTOPI_OUTBOUND

Gateway host : ECC's host number

Gateway service : ECC's service number.

In PI side:

I have created :

1 DT for File Rcvr

1 MT for File Rcvr

1 SI for File Rcvr (async)

1 MM (sender RFC and receiver File)

1 OM

1 CC with RFc as sender with the following parameters:

Communication component : ECC's component

application server (gateway) : ecc's gateway

application server service(Gateway) : ecc's service number

Program id : ECCTOPI_OUTBOUND

inital connections 1

max. connections 1

And also gave ecc's details in application server , s/y number, auth. mode, logon user ,

pwd, ecc's client number

1 CC with File adapter and file content conversion

1 receiver determination

1 interface determination

1 sender agreement

1 receiver agreement

When i am executing the ABAP program in R/3 I am getting the following error:

Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC

-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')

Please let me know if any of my steps are wrong and how to rectify this error and make

the scenario working.

Thanks for your help.

[former_member200962]

lookup of alternativeServiceIdentifier via CPA-cache failed for channel

1) You seem to have not maintained Adapter Specific Identifiers properly for the Business System in ID.

Check Q15 of this SAP note: https://service.sap.com/sap/support/notes/730870

From the above SAP Note:

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

2) Hope that the Business System that you have defined in the SLD is pointing to the desired SAP system from which you are receiving the RFC message.

Regards,

Abhishek.

[Former Member]

I have mentioned the Adapter specific parameters properly.

It contains :

For ECC s/y(i.e for RFC)

Logical system : DECCLNT120

R/3 system ID : DEC

Client 120

For PI (i.e for File)

Logical system : DPICLNT100

R/3 system ID : DPI

Client 100

Since i am sending the Response of the RFc to the file, i have used a Service interface where i am passing the RFC.Response as Request.

if i am passing the RFC directly as i/p in Source operation of Operation mapping then it doesn't pick up the response in the souce message of the mapping program present in Operation mapping.

So i am passing the same SI_Sender_RFC in the Sender Agreement and it gives the error:

Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService 'DEC_RFC', toParty '', toService '', interface 'Z_HR_OUTBOUND_DATA2', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (channelId c78f5a88787131a09384c07c2db0e93b)

why is it so?

[Former Member]

The problem has been rectified by giving the adapter specific identifiers(R/3 System ID and Client) forIDOC and RFC Adapter in R/3 business system

[rajasekhar_reddy14]

Hi,

refer below link,and follow the steps it will solve your problem...

http://www.riyaz.net/blog/understanding-the-rfc-adapter/

Regards,

Raj

[Former Member]

any suggestions to solve my error