cancel
Showing results for 
Search instead for 
Did you mean: 

Login to Solman & R/3

Former Member
0 Kudos

Hi,

When CHARM is implemented developer & Tester can login to R/3 using ugent correction Logon to system.

Means no need to logon seperately for R/3.

But how can I restrict Developer & Tester for direct login to R/3. They are not suppose to login directly & do the work.

When we implement ChaRM does it means that all users have to login to satellite system only through Soluton Manager.

How to control direct login from R/3.

Regards

PK

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi PK,

see this post [;

Best regards,

Stéphane

Former Member
0 Kudos

Dear Stéphane,

We can control it through the SAP Logon authorization.

But then user has to login to R/3 only through Solaman(This is ok for ChaRM).But what about if user wants to login for some other purpose( Not ChaRM)., Then how he will login.

Is there any other way (Other than action Logon to System) to login to R/3.( Not through ChaRM Cycle).

Regards

PK

Former Member
0 Kudos

Hi again,

I'm not sure of what you are asking for. If you want to make the change management process using SolMan only as mandatory you can use the following IMG activity :

SAP Solution Manager --> Scenario-Specific Settings --> Change Request Management --> Standard Configuration --> Change Request Management --> Set Project Assignment of Requests as Mandatory

In that case you can reopen the access to R/3 from SAP logon.

If you want the user to be able to logon to the R/3 system from SolMan only, you will have to develop a specific transaction in SolMan that works like the 'Logon to system' action in ChaRM... I only see those two options, but perhaps someone else does see another one ?

Hope it helps.

Regards,

Stéphane.

Answers (0)