Question:
Hello everybody.
Is it advisable to use collective roles in organizational structure management (PPOMW)?
I see it seems quite a mess ... In my business I prefer to use collective roles to have the chance to merge all the standard paths together so all users can work with standard menu paths.
Now I am trying to add the use of PPOMW and see that "it likes to work" with individual roles ... am I right? I'd like to keep the use of collective roles for the fact written above; individual roles forces me to re-write all the paths in user menus, because they all starts with folder 'Logistics' ,so I should re-customize the paths for not having 15 folders called 'Logistics' in each user menu.
Any suggestion?
P.S. I am now using release 47.
Please let me know, if I need to be more precise in explanation.
Regards,
Max
Answer:
It is NEVER advisable to use collective anything, it violates the base security principle "Keep it SIMPLE".
SAP allows collective role creation to "cure" a symptom rather address the root problem, poor security design.
Answer:
... how do I solve the problem of merging together identical paths?
Is the personalization of menus paths the only way to work with individual roles?
Thanks in advance for any possible answer.
Max
Answer:
Simplify the roles so there ara minimum of duplicates and then search this site for the entries in SSM_CUST to sort, condense, etc. the menus.
Answer:
You could just train the users to use the standard SAP menu.
They WILL get used to it after a while and you don't need to worry about menu's
Answer:
You could just train the users to use the standard SAP menu.
They WILL get used to it after a while and you don't need to worry about menu's
This should be the definitive solution, I know.
I would have already chosen to set Sap standards menus for all users but I'm not the one who decides in my business actually, so I am trying to find a differente solution ... thanks again for your help.
I'll try to look for the suggestion of john above .. never hesrd about that..
Max
Answer:
Simplify the roles so there ara minimum of duplicates and then search this site for the entries in SSM_CUST to sort, condense, etc. the menus.
Thanks John, I'll try and have a look.
If something is not clear I'll be back again ... and try to ask you some help.
Regards.
Max
Answer:
Hi,
If training them to use standard menu is too hard, try training them to create their own favourites in SAP menu.
regards
Answer:
Hi,
If training them to use standard menu is too hard, try training them to create their own favourites in SAP menu.
regards
Hello aaristondo.
Users are already using Favorites and I should say quite well; so I have now decided to eliminate (turning it off) User menu and leave on just the Sap Standard; but I still have not understood how to give a folder with custom transactions to each user in the Sap standard Menu at this point(different custom transactions to different users).
I tried to use menu areas with SE43 but as soon as I create a menu area with custom transactions and assign it to a single user (in SU01), Sap standard Menu disappear, leaving the place to the new folder (menu area)... this of course is Sap usual reaction to this action ... I know, but I do not know how to work and solve this problem differently.
Tried a few other things, but now I have finished new ideas.
Any suggest?
Max
Answer:
Max,
Create a copy of area menu S000 and include the extra transactions. This will give you all the SAP standard menu items with the extra folders you create.
Cheers,
Al.
Answer:
Max,
Create a copy of area menu S000 and include the extra transactions. This will give you all the SAP standard menu items with the extra folders you create.
Cheers,
Al.
Thanks Al; I've already had this suggest, but my need is to give groups of custom transactions to different groups of users; If I create a the copy of S000 and fix it as the main start session of my Sap R3/System, I would be obliged to put all my custom transactions in ....
Is this the only way to do it? or ... I have not understood?
Thanks for your patience Al ... it is all a bit new for me.
Ciao.
Max
Answer:
Max,
Is there any strong business requirement for the groups of users NOT to be able to see the different transactions? Surely if there is no risk (because they cannot run them) the business shouldn't have a problem.
Cheers,
Al.
Answer:
Max,
Is there any strong business requirement for the groups of users NOT to be able to see the different transactions? Surely if there is no risk (because they cannot run them) the business shouldn't have a problem.
Cheers,
Al.
You are right Al; there shouldn't be any business requirement to hide completely custom transactions ... I'll suggest my boss and see if the plan is ok for him too.
Thanks again mate.
Max
Answer:
Hi,
I would like to weigh in here, I agree with the statments above reqarding composites etc, however, one area which does not seem to be covered is complex landscapes that are using workplace.
All the recommendations given are very security practical, but don't seem very business / user practical.
Users are business process orientated, are trained according to how business processes flow. To make the user experience better and not have to teach the user about APO, BW, R/3 CRM etc, structuring a role menu for multiple component systems makes their lives easier. In my experience this menu structuring is done in a workplace environment with composite roles.
Why should a user care on which system they run a transaction, rather the menu they see should present a process view and group togethor the functions that are performed as part of a process irrespective of which component system it runs on
For example the payment processing function in R/3 could be grouped with a BW report that shows what invoices are outstanding for a vendor and if any of the goods delivered are in dispute.
While the KISS principle applies, horses for courses is also relevant. In this case I would say composites are the right solution for menu structuring in a workplace environment.
Any feedback on your experience in a multi component environment with workplace and menus are appreciated.
Cheers
Peter
Answer:
Peter,
While disliking composites for reasons I have mentioned before, I agree with their place in workplace & multiple landscapes for the reasons you have outlined.
Whilst in principle I agree with the users experience being very important and security reflecting business processes I have also found that a pragmatic approach often is the best bet. After auditing many, many SAP implementations over the years there have been far too many instances of the extremes causing problems, obviously much of this is due to lack of business buy in for security etc. etc.
Welcome to the forum, great to see others with experience to offer
cheers
Al.