- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- SAP Role Re-design strategy
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SAP Role Re-design strategy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2012 2:27 PM
Hi Gurus,
We are going to re-design 845 single roles for our ECC system as part of SOX project. Currently, we have DEV->QAS->PRD landscape which is used for production support.
I would like to know, If we have two development and Quality box then it will be a good approach to the role re-design? Using two development and quality box for smooth transition of roll outs for different geographies. At a time one DEV-QAS-PRD will serve as a three system landscape for production support and the technical enhancements and maintenance activities for new roll outs will be carried out from DEV2 and QAS2.
Could you please advise if we really require DEV2 and QAS2 for the role re design and can't we use the existing DEV1 and QAS1 which is also used for production support ?
Regards,
Salman
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2012 4:10 PM
Hi,
I am not sure why you discuss system landscape. In my opinion it is irrelevant in your case.
What I would do:
1) start over (use extra character in role names for "new" roles so you can easily indetify them)
2) since I would start over, I would only repair old roles in cases where there is no other way. Then I would go to roles in "edit old status" mode, change the role, save, generate, finished.
3) for new roles I would use the old role menus as a template, structure it the same (I like it that way, other might prefer differently), remove what is obsolete or remove what is available in other roles (if you do SOX... what a funny way of calling a redesign project, but anyway..., it might mean that you will split one role into multiple smaller ones).
4) for every new role change it in "read old merge new" change mode in PFCG to use the up to date proposals (that means that no missing SU24/25 upgrades... otherwise start with the upgrade first).
5) while testing the role (first you when building the role to catch the low brainers + while users test the roles) move what`s suitable for it to SU24, "read old merge new" again...
...and voila... new authorization concept is born,
cheers Otto
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2012 4:10 PM
Hi,
I am not sure why you discuss system landscape. In my opinion it is irrelevant in your case.
What I would do:
1) start over (use extra character in role names for "new" roles so you can easily indetify them)
2) since I would start over, I would only repair old roles in cases where there is no other way. Then I would go to roles in "edit old status" mode, change the role, save, generate, finished.
3) for new roles I would use the old role menus as a template, structure it the same (I like it that way, other might prefer differently), remove what is obsolete or remove what is available in other roles (if you do SOX... what a funny way of calling a redesign project, but anyway..., it might mean that you will split one role into multiple smaller ones).
4) for every new role change it in "read old merge new" change mode in PFCG to use the up to date proposals (that means that no missing SU24/25 upgrades... otherwise start with the upgrade first).
5) while testing the role (first you when building the role to catch the low brainers + while users test the roles) move what`s suitable for it to SU24, "read old merge new" again...
...and voila... new authorization concept is born,
cheers Otto
- SAP Managed Tags:
- Security
