Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SE16 - Create

former_member194669
Active Contributor
0 Kudos

All,

If you go to transaction code SE16 you can find a create button in the application toolbar. My question is what will be authority object behind this, because some of users in Production System using this button created some entries in one of the custom table. I need to restrict this.

I think it is checking table maintenance authorisation group. or its have some specific authorisation hebind this ?

6 REPLIES 6

Former Member
0 Kudos

The "New button" only works when you have table maintenanc generated.

There is an Authorization Group setting in Table Maintenance Generator screen.

0 Kudos

Thanks for your reply.

Table in which users created entry is customised table and that does not have a table maintenance

0 Kudos

I think it checks for Auth object S_TABU_DIS. If the user has activity 02 of S_TABU_DIS for your custom table, he/she will be able to create entries.

0 Kudos

Please check "Data Browser/Table view Main" setting Delivery and Maintenance tab of table in ABAP Dictionary. There is enough information F1 Help on this field.

If you are not able to change table attributes, then you may user Screen variants to disable this button and assign the authority group on it.

0 Kudos

Please check: SE11 -> "Delivery and maintenance" Tab ->"Data Browser/Table View Maint" setting.

Flag if Maintenance with Standard Tools is allowed

Definition

This indicator specifies whether it is possible to display/maintain a table or view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).

The indicator can be set for database views, projection views, maintenance views, mantenance view variants, and tables (referred to as Dictionary objects' below) using transaction SE11.

Note: The indicator is not available for help views since they are not relevant to SE54 and are used for search functions.

Usage

The indicator can have the following values:

Display/maintenance not allowed

The usage of standard table maintenance tools is not allowed.

Maintenance and display of this Dictionary object is not possible in transaction SE16.

Transaction SE54 does not allow the generation of a maintenance dialog, which means automatically that calling transactions SM30/SM34 for this Dictionary object is no longer possible.

Display/maintenance allowed to limited extent

Usage of standard table maintenance tools is allowed to a limited extent:

Transaction SE16 allows the display function for this Dictionary object, but no maintenance.

Generation of a maintenance dialog for this Dictionary object is possible using transaction SE54.

Transaction SM30 does not allow maintenance and display functions for this Dictionary object

Note: The generated dialog can be included in view clusters (data maintenance through transaction SM34) or called within a program through the function module View_Maintenance_Call.

Display/maintenance allowed

The usage of standard table maintenance tools is allowed:

Transaction SE16 allows the maintenance and display functions for this Dictionary object.

Note: If an SM30 maintenance dialog exists for this Dictionary object,

it is called.

Transaction SE54 allows the generation of a maintenance dialog for this Dictionary object.

Transaction SM30 allows the display and maintenance functions for this Dictionary object.

Note: The generated dialog can be included in view clusters (data maintenance through transaction SM34) or called through the function module View_Maintenance_Call in the same way as the transaction call SM30.

0 Kudos

Stony Lin,

You are right. If table "delivery and mainteance tab" with maintenance allowed then user can edit if it doesn't have table maintenance.

Problem solved . created table mainteance and assigned a custom auth object to that has solved the issue