Security issues in OM Actions
I had customized some actions for PA and I could customized parameter UGR so that not all of them would be displayed in PA40 (depending on UGR parameter of each user)
Now, I have to deal with OM actions and I realize They dont use parameter UGR.... Is there any way to implement some security issues in these actions? How can I deny or grant access to OM actions to some users?
Please ANY comment will be very apreciated, thanks very much in advance.
Sharon Newton replied
I don't know of a parameter to help you with this but a couple ideas: obviously, standard security will restrict folks from using actions they're not supposed to, but they'll still see them in the drop down list in transaction PP03 - they just won't be able to use them; you can use the actual transactions for the actions and only give people authorization to the transactions they're supposed to use (these are listed in Table T77S0 under group 'TCODE' and you have to look for them b/c they're mixed in with other transactions - for example, the action 'Create Position' is PQ13); you could just use PPOCE/PPOME, which is much cleaner than actions and the method I have recommended my clients use since 4.6C. The client won't have to dig through a list of irrelevant actions.
One word of warning - don't delete the delivered actions you're not using. They're used throughout the system. For example, all the Training Management actions drive the screens in the Training Management function. If you delete them, the training screens will be gone. That may not matter now, but it could impact your client as they grow their footprint in the future.
Hope this helps.