You cant do this without considerable extra work.
Ask your development team to assign the view to a transaction (SE93) and assign the transaction to the user/s who need it.
To add to it, you can restrict the table by it's auth group, but then users will have access to all tables in that auth group. If you create a custom auth group for only that table, then users will still have access to the other auth groups which are in S_TABU_DIS in their role. It's unusual for users to not to have at least some values for this object.
Therefore, easiest way is to link the view (V_ tables are views) to a transaction and give the user the transaction rather than SM30.
Edited by: Alex Ayers on Mar 19, 2008 12:41 PM
