Who should use SM30?

[Former Member]

Hello,

Who should be using SM30 to maintain table data? Is this something appropriate for a user to have access to?

I have a table that I need a user to be able to update. I do not want to have to code an interface or program. I'm looking for a quick solution.

Is it normal to give a user access to SM30? Can that access be limited to a specific table?

Thank you in advanced.

Brett

[suresh_datti]

Hi Brett,

The table maintenance can restricted using the relevant authorization groups. And depending on the business need, it is appropriate to give SM30 access to the users.

Regards,

Suresh Datti

[Former Member]

It depends on tables .

some tables every one can use it , but some table they will restrict with authorizations.

if you don't want to restrict that user then you need to assign authorization key and assign that in table maintenance generator, and assign it in authorization option. then he can able to update, but others can't.

vijay

[Former Member]

Hi Bret,

SM30 is an all powerful transaction for maintaining tables, but unfortunately does not limit the user to a specific table. So auditors vehimently oppose giving this access to users in production.

Create a variant transaction or a parameter transaction. Look at the documentation in SE93 or SHD0 transactions.

Srinivas

[Former Member]

Nobody should have authorization to use SM30 or SM31 in production environment. The widely used practice for table maintenance is to create a parameter transaction based on SM30 transaction for given table/view. The users will have authorization object <b>S_TABU_DIS</b> in their role ( but no authorization for TCODE SM30 or 31). Also they will have authorization for new parameter transaction.

[Former Member]

Excellent information. Thanks everyone!