Problem in RFC connection

[Former Member]

Hello,

I have scenario R\3 to RFC via xi.

The scenario work ok in dev environment.

I want to add the scenario to test environment and I have a problem with the connection between R\3-test to XI-test.

I checked the connection in SM59 and it's work find.

I checked the connection details and it's looks ok.

When I try to send RFC to from R\3 to XI I received the message:

<b>"lookup of alternativeServiceIdentifier via CPA-cache failed for channel </b>

I need to transfer the scenario to production and is very important to check it in the test system.

Do you have any idea?

Regards

Elad

[Former Member · Accepted solution]

Make some dummy change in the communication channel and activate it and try the scenario again.

Regards,

Jai Shankar

[Former Member · Accepted solution]

Hello Jai,

I try this before and it's not solved the problem

Thank you

Elad

[Former Member · Accepted solution]

Hello,

In the SAP notes number 730870 I see the sentance:

<b>A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers".</b>

Where I can found this Service in XI system.

Regards

Elad

[prateek · Accepted solution]

Doble click ur business system or business service name. There in the right-pane there would be a menu. There a menu tab would be "Service"

Regards,

Prateek

[Former Member · Accepted solution]

Hello,

I can't found any right-pane.

Do you have any idea?

Elad

[prateek · Accepted solution]

Whenevr u double click a business system <b>name</b> e.g. if name of ur Business system is "BS_Legacy", then double click BS_Legacy and it will open a window. In that opened window there will be a menu with menu tab "Service"

[Reward if helpful]

Regards,

Prateek

[Former Member · Accepted solution]

Hello Prateek,

I found this button and when click in the:

R\3 system ID and client is empty

Any idea?

Thank you

Elad

[prateek · Accepted solution]

Fill it urself

R\3 system ID - the three letter system ID e.g. "XID"

Client - Client number xxx

Regards,

Prateek

[agasthuri_doss]

Hi,

SLD cache and reactivating the Channel will solve this issue.

Regards

Agasthuri Doss

[Former Member]

oops misread the question.

Regards,

Sumit

Message was edited by:

Sumit Khetawat

[former_member529475]

Hi Elad,

Same kind of problem is discussed and solved here...

have a look at the following thread....

https://forums.sdn.sap.com/click.jspa?searchID=3788952&messageID=1966250

Cheers..

Vasu

<b>** REward POints if found useful **</b>