cancel
Showing results for 
Search instead for 
Did you mean: 

No trusted/login RFC connection for system BCP in TA SMSY

0 Kudos

Hi,

i got this error Early Watch Report for only production System.

No trusted/login RFC connection for system BCP in TA SMSY

Amit

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear Friends,

In this case we have one more option.

Go to solman

-> solman_setup

->Managed system configuration

Here under managed system configuration go to "Connected managed system".

There you can create/update Read and Back both RFCs.

This will automatically update all the roles and user and RFC connections.

Thanks,

Gopal Tamrkar

Former Member
0 Kudos

HI,

I hope the error message is straight forward.

Please Check whether you have established RFC connections to the BPC system and the same is avaiable under the RFC connections in TRXn SMSY-Your system -.Test the connections in SM59-BPCs-> READ and Trusted RFCs.

If its not present, Generate the RFCs again manually.

Hope this helps.

Revert for any issues.

Thanks,

Jagan

Edited by: jagadheeshan govindasamy on Oct 9, 2009 3:24 PM

0 Kudos

hi,

we check there its working RFC through to SM59.

we see sm37 there one is cancelled

At least one entry could not be found in object buffer.

Message no. CRM_ORDER_MISC106

Regards

amit gupta

9979886641

Former Member
0 Kudos

I think you are talking about 2 seperate issues

1) your EWA reports that the RFC is not working. I recommend you to delete the RFCs and recreate them via the SMSY wizard for your BCP<client>

2) you see a job in SM37 ending with CRM_ORDER_MISC106

--> check this note #1343699. This appears to be a bug

Nesimi

RajeevP
Advisor
Advisor
0 Kudos

Dear Amit,

Check from SMSY whether the trusted RFC connection to BCP system is working fine or not. Also check the remote login from the RFC. Make sure that in the login data tab of RFC, the RFC is mentioned as trusted one and it is not using any user name and password for the login. Also check from SMT1 that the authorization check is fine for BCP. If all these are working fine and stil you get the same error, you may need to recreate the RFC with user who has proper authorizations like S_RFCACL, S_RFC.

Hope this answer you.

Rajeev

Former Member
0 Kudos

Dear Rajiv,

What kind of RFC to be configured if my satellite system is only Java based, it is NW CE 7.1 EHP1

Please suggest.

Thanks,

Anand