RFC destinations for Earlywatch and MOPZ

[Former Member]

Hi,

I´m setting the earlywatch reports and MOPZ, but I´m having problems with the rfc destinations.

When I call the the SDCC from Solution Manager to Satellite system I get this error message:

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

I´ve deleted the RFC in solution and satellite system, and users used for to make this rfc destinations, but when I tried again for create the rfc destinations from smsy I get this message error:

RFC destination SM_SIDCLNT200_TRUSTED creation error. RFC destination may have errors

RFC destination SM_SIDCLNT200_TRUSTED generation error

What can i do?

[Miguel_Ariño]

Hello there,

Maintenance Optimizer uses the '_READ' RFCs to get switch framework information from the satellite systems.

The read RFCs are mandatory only for ERP / EHP for ERP systems. If they are not configured in SMSY , or if there are credentials or authorizations issues with the RFC user, you may get the infamous 'No RFCs available to get switch framework information' error message in Maintenance Optimizer.

If you have configured the READ RFC , and also have made sure the credentials of the RFC user are fine, make sure that the RFC user in the satellite system has authorizations to use function module OCS_GET_SFW_COMPONENTS.

Best regards,

Miguel Ariñ

[Former Member]

Also please note:

The Trusted RFC connection is used for several functions like executing

'Self Diagnosis', activating the SDCCN of satellite systems, executing

some background jobs. Also, when you clicked on the button the 'Call

Service Data Control Center' to generate the EWA report, it uses the

Trusted RFC connection to get the EWA session data.

Therefore, if you want to use those functions, the Trusted RFC

connection should be generated and has no problem.

If you want to generate the EWA report immediately, then you need to use

the button 'Call Service Data Control Center'. That requires to use the

Trusted RFC destination. However, scheduled EWA sessions in the

Solution Manager doesn't need to use the Trusted RFC destination.

[Former Member]

Hi,

Please generate the trusted RFC destination, then it should resolve the

error. You can create the trusted RFC destination with the following

methods.

- Using the wizard of SMSY

• Please select 'Trusted System RFC Connection'

- Transaction SOLMAN_SETUP

-> Managed System Configuration

-> Select HCP

-> Configure Technical System

-> Step 1

• Please select the radio button 'Trusted-destination'

Thanks

Regards,

Vikram

[Former Member]

Thanks Vikram for your answer,

But you can explain with more detail the next steps:

-> Managed System Configuration

-> Select HCP

-> Configure Technical System

-> Step 1

• Please select the radio button 'Trusted-destination'

[Former Member]

Hi,

please check:

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm

Thanks

regards,

Vikram

[Former Member]

Thanks Vikram,

But there are a customizing for to create this rfc automatically with the defaulta paramaters and authorizations for the users?

This steps I don´t make before.

[Former Member]

I´m very confuse about the concepts trusting/trusted systems. I´ve found the next steps for to recreate the RFC, but What is the part of the solution manager and what of satellite system? More thanks

On the Trusting System

1. Create the Trusted RFC connection in sm59

a. RFC destination =

5. Save

6. Enter Target Host and System Number information

7. Click Logon Security Tab

8. Trusted system= yes

9. Enter language and client information

10. Check the current user option

[Gordon_Goh]

Hello Ruben,

Please go through the note 1627901 which covers Trusted RFC issue between Solution Manager system and managed system.

Hope this helps.

Kind regards,

Gordon

[Former Member]

Hi,

seems you were nt clear on some of the basic setups.

best to read this initial blog to understand your handling

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Managed_Systems

Thanks

Jansi

[Former Member]

Thanks Gordon for the note,

But I´m very confuse about some things.

I had deleted the the RFC TRUSTING_SYSTEM@S00.

Every time that I try to regenerate the RFC from each system from the wizard of SMSY I get the error that the rfc cannot be created. I don´t understand that the call of SDCC from the Solution Manager for create the tasks refresh sessions was worked, and now It will be necessary to adjust the rol SAP_S_RFCACL... If I must to create the SAP_S_RFCACL role in the solution manager in the field RFC_SYSID, I´ve to put * If the user that uses this rol, will connect to different satellite systems.

The authorization object S_RFCACL that it´s included in the role SAP_S_RFCACL, this rol must to be adjusted in solution manager and satellite system? In the note expose the example of client and server. What is it the role of satellite system o solution manager?

More thanks

Edited by: Ruben Torres on Mar 9, 2012 11:14 AM