2020 Jul 09 9:24 AM
Is anyone aware of a solution/fix, that allows SE16 to be granted to users, albeit with local company code restrictions (or plant/p/org etc). i.e. allows a user in country A to run SE16 with no risk of them sighting country B as it were. Any pointers or known out of the box solutions.
2020 Jul 09 10:14 AM
generally it's recommend to avoid granting SE16 access out to users (data privacy and system perform on large selections). However, most places I know put a Z-program wrapper around it to call the authority check to limit the data.
What system is this for?
If it's small tables like posting periods (old transaction OB52) then S_TABU_LIN can be used. However, this is not recommended for larger tables.
Regards
Colleen
2020 Jul 09 11:23 AM
Hi, thanks that sounds about right..... its not so much for downloads (performance risk), more so, number of entries and checks like that, where if you dont have it, you are flying blind to an extent with lots of manual intervention. Iget the data privacy issue, but that shouldn't stop all work as it were.....Thanks for feedback.