Solution Manager Security

[Former Member]

I have joined implementation project team which is in the project preparation phase and will be going to blueprinting stage soon.

Project Manager and few consultants are one site. My role is to assign appropriate authorizations(for now in Solution Manager) to project team members and possibly liaise with Project managers and resolving issues raised by technical and functional consultants in this respect.

Scenario:

We have a solution manager 4.0 and development systems configured as raw systems by hosting company, and to begin with, clients and users were already created and assigned some SAP delivered authorizations.

Beginning with Solution Manager, I have to reorganize the roles of the project members and liaise with Project Management to assign correct roles.

Sofar, I did not get much input from the project manager about the roles, but, I would like to kick of in this front, but not sure where to begin with (this is my first project working at this stage). I have gone through the “Roles and Authorizations” part in the Solution manager (sp12) configuration guide from service market place and gained some familiarity with roles in general.

I came to this site about a week ago, and for now I understood the landscape and attended few meetings etc, so making few plans to progress the project in best possible way.

Question:

How much awareness will the project manager will have in terms of authorizations. Of course I can assign them and perform the tasks related to that technically. But, Am right in thinking they will not have specific awareness related what are the roles that may exist (technical aspect)? If so, what is the best approach to start taking requirements in terms of solution manager security?, what kind of information should I actually expect ? or to begin with properly, should I go to him myself with the list of available roles and ask them to pick ?

Please advice…

My question is more of communication issue rather than technical ..

[Former Member]

Hi Nick,

You are right in the PM's are unlikely to know much about auths or security, though that's not to say that they won't necessarily have an opinion.........

What I tend to do is to start at the highest level - not technical & find out what are the different roles people performing in the system.

Once you have the different roles that will be performed you can then identify the activities that they will need to perform & this is usually mappable to transactions etc.

At this point you can find out if there is any segregation needed (e.g. by project) and create the roles based on the activities required and any variants for restrictions etc.

Next step is to test them & assign to users.

Hope that helps

Cheers

Alex

[Former Member]

Brilliant ! You have replied me with precisely what I am looking for.

I might come back to you if I have any questions in this front when I actually start dialog.

Much appriciated.

Nick.

[Former Member]

Brilliant ! You have replied me with precisely what I am looking for.

I might come back to you if I have any questions in this front when I actually start dialog.

Much appriciated.

Nick.

[Former Member]

Glad to help, the technical side is usually the straightforward part!