|
|
| There was a need to block users from accessing table PA0008 via
Transaction SE16.
Is there any objects I can set in the Authorizations? Ans: Recommendation Allowing SE16 can be a dangerous policy. I prefer not to grant SE16 and to create bespoke parameter transactions which call SM31 and 'hardcode' the table name. Transaction is SE93, choose create and then parameter transaction. Tell it to call SM31 and to use table name xxx. SE16 relies on the authorisation S_TABU_DIS, this can restrict the activity and the authorisation group. You could maintain an authorisation group on the table but this may count as a modification. Check out the documentation on S_TABU_DIS. Definition Authorizations for displaying or maintaining tables. The object only controls access using the standard table maintenance tool (transaction SM31), enhanced table maintenance (SM30) or the Data Browser, including access in Customizing. Defined fields The object contains the following fields: - Authorization group for DD objects: -- Authorization for tables by authorization class according to table TDDAT. --- Enter the name of the allowed classes. --- Table classes are defined in table TDDAT. - Activity: Allowed operations. -- Possible values: --- 02: Create, change or delete table entries --- 03: Display table entries only
Get help for your Basis problems
SAP Basis Admin Books
SAP Basis Tips
Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES
Best regards,
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|