We don't give SM30 authorization to the business users at all and found that using custom transactions that allow for additional authorization checks (e.g. by an organization code) works better for us. I wrote on this a while ago and there are also more recent blogs on SCN on using maintenance views. In some cases we have one program call maintenance view for several Z tables. Although the best approach is to avoid direct table maintenance altogether, I think. Image may be NSFW.
Clik here to view.
↧
Re: Authorization group changes for Security reason
↧
