Or you can create a custom transaction that goes into SE16 and then into the table. How to create a custom transaction for SE16:
SE93 > enter custom transaction name > Create > Description in short text field > select transaction with parameters > enter text of your choice in the Transaction text field > enter SE16 in the transaction field > select skip initial screen > save your new transaction code. >Local object> now in lower part of screen you will see default values name of screen field value select the name of screen field. Press F4 and choose DATABROWSE-TABLENAME, and enter the name of the table in the value field you are giving access to.
Save > local object
Now test it by entering in the transaction code. It should skip past SE16 and give the same access to the table as though the user had used SE16.
You could use this method if protection through S_TABU_DIS and the authorization group was not a good solution for you.