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
Do you have
a SAP Basis Question?
SAP Basis Admin Books
SAP
System Administration, Security, Authorization, ALE, Performance Tuning
Reference Books
SAP Basis Tips
SAP BC Tips and
Basis Components Discussion Forum
Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES
Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
All product names are trademarks of their respective
companies. The site www.erpgreat.com is in no way affiliated with
SAP AG.
Every effort is made to ensure the content integrity.
Information used on this site is at your own risk.
The content on this site may not be reproduced
or redistributed without the express written permission of
www.erpgreat.com or the content authors.
