cancel
Showing results for 
Search instead for 
Did you mean: 

RFC DESTINATION FAILED

Former Member
0 Kudos

Hi

while doing client copy in ECC 6.0 i am getting this following error. can u pls help me to sort out this issue.

Regards,

Ravi

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

If someone else has same issue:

1) Create RFC to the to source client,

2) Go to tcode FINB_TR_DEST

3) Input relevant data about RFC.

former_member256962
Participant
0 Kudos

In such case,snc needs to be inactive for the user being used in the RFC .

Also the inactive mark needs to be checked for the RFC destination under Logon and security tab

former_member256962
Participant
0 Kudos

snc needs to be inactive

former_member256962
Participant
0 Kudos

snc needs to be inactive for the user that is being used in such case

Former Member
0 Kudos

Ravi

what is the error?

Also are you doing local or remote client copy?

if remote,then check for the RFC destination between source and target system

Rohit

Former Member
0 Kudos

Dear Rohit,

I am doing Local Client Copy. The following is the error i am getting.

RFC destination for client copy in systems with Financials Basis

(FINBASIS) component.

The system could not find any suitable RFC destination for processing

for client 800.

This note also appears if an RFC destination was found but this does not

work.

o RFC destination: FINBASIS_800

o Error text: Error during the retrieval of the logon data

Proceed as follows to eliminate this error:

1. Start the wizard to create a new RFC connection

or perform the following steps manually:

1. Create an RFC destination with the target ZK>source client of client

2. Check whether the RFC destination works in transaction SM59.

To avoid errors when assigning the password or the authorizations of

the RFC user, use the authorization test Test -> Authorization.

3. Enter the RFC destination:

- Transaction: FINB_TR_DEST (Destinations for Transport Methods of

the Financials Basis)

- Client: 800

4. Start the client copy again.

Regards,

Ravi

Former Member
0 Kudos

do exactly the same as this message is asking, in sm59 create the RFC inbetween both the clients inovlved in client copy and maintain the entry using FINB_TR_DEST tcode then.

Former Member
0 Kudos

Ravi

you will need to create the RFC as mentioned in the error

after that start copy again and you will not face any issues

Rohit

Former Member
0 Kudos

Refer following Notes too

568784 Termination with client copy (Financials Basis)

Note 912369 - FINB_TR_DEST, after import failures, transport errors

Former Member
0 Kudos

Dear Rohit,

I have created the RFC connections still i am facing the same issue.

Regards

Ravi

Former Member
0 Kudos

did you test the RFC,is it working fine

Rohit

Former Member
0 Kudos

Just one thing:

do you have the RFC FINBASIS_800 in SM59

open the RFC and do connection test and authorization test and let us know the results

I guess the problem is with the user who is maintained in the RFC destinaton

Rohit

Former Member
0 Kudos

Rohit,

The following is the error i am getting while checking connection test.

Note: I am checking this in the source client.

Logon Connection Error

Error Details Error during the retrieval of the logon data stored in secure storage

Regards

Ravi

Former Member
0 Kudos

give the user DDIC or else in the login details in rfc, which is not locked in the target client

Former Member
0 Kudos

check this in target client,because client copy will stary from target client only

so log on to target cleint ,check the RFC to source client and if it fails,maintain the suer id and password of a user in a target client

Rohit

Former Member
0 Kudos

I have checked the RFC in both the client, but it fails in both even though i changed the user as ddic still it fails.

Regards

Ravi

Former Member
0 Kudos

password should be correct, rfc can be created from either of two clients

In the rfc, user should be of destination client.

Former Member
0 Kudos

Ravi

RFC should be preferably be created in target client

in the user for RFC,maintain the source client user withe password,user can be anyone,ddic not required

Rohit