cancel
Showing results for 
Search instead for 
Did you mean: 

S_RFCACL

Former Member
0 Kudos

Hi,

I just installed version 7 and am having problems getting the RFCs generated for the Solution Manager system itself. I'm getting what appears to be a common problem "No authorization to log on as a trusted system (Trusted RC = 2). It looked initially that I could get the required authorizations by assigning role SAP_S_RFCACL to the userID on the trusted and trusting system, but that does not appear to be working.

Do I need to maintain object S_RFCACL on both the trusted and trusting system to get this to work?

Is role SAP_S_RFCACL not sufficient?

Does the RFC_Client need to be 000?

Thanks,

Points will be awarded.

Russ

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Russ

In the satelite systems you need 2 authorisation objects

S_RFC & S_RFCACL

Lets presume your customzing client in Solution manager is 100

Lets assume the SID of solution manager is SOL

Lets assume your customizing client in the satelite system is 200

Lets assume the SID of the Satelite system is ABC

Then the role in the satelite system must contain the authorisation objects S_RFC

Configured as following

Activity All activities

Name of RFC to be protected *

Type of RFC object to be prote Function group

and authorisation object S_RFCACL

Activity All activities

RFC client or domain 100

RFC same user ID Call by the same user is possible

RFC information

System ID (for R/3 and externa SOL

RFC transaction code ' ', SMEN

RFC User (R/3 or external) ' '

Remark ' '= [open single quote] space [close single quote]

the role in the solution manager system must contain the authorisation objects S_RFC

Activity All activities

Name of RFC to be protected *

Type of RFC object to be prote Function group

the role in the solution manager system must contain the authorisation objects S_RFCACL

Activity All activities

RFC client or domain 200

RFC same user ID Call by the same user is possible

RFC information

System ID (for R/3 and externa ABC

RFC transaction code ' ', SMEN

RFC User (R/3 or external) ' '

This role must be assigned to the user in the systems for whom you created the trusted connections

So lets presume during the generation of the trusted connections you defined to connect to system ABC with user xyz then this user xyz must be assigned the role we created in the satelite system

If user qrs will be used to access the solution manager from the satelite system then user qrs in SOL must have the role we created in the solution manager.

Hope this clears things out.

If you still have a problem with the trusted connections then delete all RFC connections between the 2 systems through SM59.

Also start SMT1 and delete the entry for the trusted system in both systems

Then try to recreate the trusted RFC connections through the wizzard in SMSY

Kind Regards

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Russ,

Well, there is a concept called trusting system and trusted system. When we create a Trusted RFC connection, this Trusting and Trusted concept plays most important role. The source system will the Trusted system and the destination will be the Trusting system.

For example, from PRD to DEV you are creating a Trusted RFC connection, which doesn't require a usre name and password, the PRD will become Trusted system and DEV will become Trusting system.

Try performing the following steps to recreate the Trusted RFC connection between the system.

On the Trusting System

1.Create the Trusted RFC connection in sm59

a. RFC destination = <trustedSID>TRUSTED

b. Connection Type = 3

c. Description = SID Trusted System

d. Click save

e. Target host= <hostname of trusted system)

f. Enter System #

g. Click save

2. Create the Trusted System

a. smt1

b. Click create

c. Enter the name of the rfc connection created in step 1

d. Enter the client, userid, and password information

On the Trusted system

1. Create an RFC connection (sm59 create)

2. RFC Destination = <trustingSID>CLNT<trustingclient#> ex. CKDCLNT500

3. Connection type = 3

4. Description = <trustingSID> Client <trustingclient#>

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

11. Save

I hope this is helpful.

Regards,

Satish