cancel
Showing results for 
Search instead for 
Did you mean: 

RFC error lookup of alternativeServiceIdentifier via CPA-cache failed for c

Former Member
0 Kudos

Hi All,

When i execute RFC from R3 to call Webservice through XI, i am getting the following error "lookup of alternativeServiceIdentifier via CPA-cache failed for channel". I refreshed the CPA cache and compared Business System in ID with SLD. The RFC destinations are created as TCP/IP and logical destination with reference as TCP/IP. What else to check and do? Any suggestions would be appreciated.

Thanks

Deno

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Deno,

This exception usually occurs if the Sender Business System and Sender Agreement are not proper.Check whether you have done te following Activities.

1.Created a Business System for that R/3 and created a sender RFC Communication channel under that system.

2.Created a Sender Agreement for the Business system that u created in Previous step with RFC as the sender Interface.

3.Created Receiver Determination, Interface Determination and Receiver Agreement with Business System as sender service and RFC as Sender Interface.

PS: Check if u have used RFC directly as the Sender Interface in IR and created Interface Mapping.

Regards,

Sudharshan

Former Member
0 Kudos

Hi,

I have done everything needed for resolving the error according to my knowledge. But still somewhere something is missing which is out of my knowledge. If any new helps, much appreciated//:(

Thanks

Deno

SD78
Explorer
0 Kudos

Hi Deno,

I have the same problem and I find a solution.

In this case I have RFC Call from SAP System with different clients to XI.

The solution is described in the SAP Note 730870 Q22:

Q 22: Which value should be chosen for the field 'Program ID' for RFC sender channels?

A: A RfcAdapter sender channel registers itself with this Program ID as a RFC-Server at the SAP Gateway. The sending system uses the same Program ID to identify the RFC-Server at the SAP Gateway. If the sending system is a SAP system, this Program ID has to be maintained in the RFC destination (transaction SM59).

During the sending system sends some RFC calls, the SAP Gateway will search its registration list for the Program ID supplied by the sending system. If there are more than one RFC-Server registered with the same Program ID, it will automaticaly schedule the RFC calles to each of the RFC-Servers using the round robin approach. This is done to distribute the load over all RFC-Servers equally.

To identify a XI RfcAdapter sender channel within the SAP Gateway it is important that its Program ID is unique within this Gateway. So try to avoid using common phrases as Program ID like 'rfcadapter' or 'rfcToXmb'.

To check which Program IDs are registered at the SAP Gateway the gateway-monitor can be used via transaction SMGW. Select Goto -> Logged on Clients. Registered RFC-Servers have a System-Type of 'REGISTER_TP'. The Program ID of the registered RFC-Servrer can be found in column 'TP name'. Unfortunately the list within SMGW only shows the truncated version of the Program ID (column 'TP name'). To get the full name, the details of an entry have to be selected. As an alternative the report RSGETALL_REG_SERVERS can be executed in transaction SE38. The output of this report will show the full names of the Program ID in column 'Registered PROGID'. This functionality is also available in the function module GWY_READ_CONNECTED_SYSTEMS which can be executed in transaction SE37.

Note that if the RFC sender channel is configured to use more than one connection to the SAP Gateway, there will be one registration at the SAP Gateway for each connection. If the RfcAdapter runs on a J2EE cluster with more than one server node, the number of registrations at the SAP Gateway is the number of connections configured in the RFC sender channel multiplied by the number of cluster nodes on which the RfcAdapter runs.

Also in SDN

My solution locks as follows:

I use/activate only one RFC sender adapter for all different clients and its works now.

Bye

Stefan

moorthy
Active Contributor
0 Kudos

Hi,

Have a look into SAP Note - 730870

Question no 15.

Also verify the Adapter Identifiers in the Business system.

shortdump problem is solved now ?

Regards,

Moorthy

Former Member
0 Kudos

Thanks Moorthy! I checked those but still the error is coming up. When I clicked on compare SLD in ID, the screen doesn't change. I guess it means that SLD check is completed and updated. Please tell me if anything else do i need to look up....

Former Member
0 Kudos

Hi,

I checkd in Runtime workbench and MONI> The error is not in RFC side, its in the Receiver SOAP adapter and shows that SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'getName_DT'. The name is not getting returned from the webservice, w

Thanks

Deno

Former Member
0 Kudos

Could anyone throw some light on this error

moorthy
Active Contributor
0 Kudos

I am sure that RFC error whatever mentioned, is not because of this.

wrt SOAP error -As it shows me that , you are calling a method called getName_DT, but there is no structure for this in your wsdl. Check the case. Go thru clearly.

Cross verify is the WebService is running or not.

Check these blogs-/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

and part 2 of this.

Regards,

Moorthy

Former Member
0 Kudos

Hello Krishna,

Where I can find the:

Adapter Identifiers in the Business system

Regards

Elad