My system is 4.6C, Oracle 8.1.7, Win2K.

Rightly or wrongly we have created roles for our users based on job description. We did not want to create individual roles for users because we figured there would be too many. Each role (eg: Z_AP_Entry_Clerk) contains only those transaction codes needed to do the job. We restrict each role at the Organisational levels mainly by Company Code and Plant (and of course the objects are maintained throughout). The problem we have with this method is that each users menu looks pretty untidy (it's just a long list of transaction codes). In the case where a user has more than one role (and some of them have about 15 !!), the list just gets longer and longer. If they switch to the Standard SAP menu, they see everything and have to go hunting for the transactions they have access to. Is there another alternative to either the transaction-based menu or the SAP Standard menu for users with multiple roles?

I have yet to come across any literature which gives examples of good role creation practice. The texts I have read only describe the best ways to create and maintain a role, but I guess they assume that each user should only have one role each.

Can anyone share their practices or point me to some case studies in this area?

We have the same problem. One way for it to look tidy is to go to each role and create a top level folder named after the role and put all the subfolders in it.  That way the users can navigate the menu by function/role.

A role should define either a position (no of jobs / tasks) or jobs themselves.   I can depend on the level of security employed in the organisation, and how much maintenance you want to conduct, ie a business change can upset security in a big way!
 

Beam Back -> SAP Cafe for Basis Components