Again, problems with maintaining authorizations for each table for an individual user.Requires developing a standalone program for each table which again is a problem as it ends up in hundreds of programs to maintain hundreds of tables.When there are many entries to be entered in the table, there is no option to upload the entries from an Excel or CSV etc.The screen is a narrow container and the user interaction is not so comfortable especially when the table has many fields or has long text fields.Not so easy to restrict authorizations for a particular table for each individual user.Logs the changes (Tcode – SCU3), but doesn’t record the field specific changes clearly (check table ‘DBTABLOG’).The concerns with each of this are listed below: Usually, a table in SAP can be maintained in three ways, Many times a business ends up with hundreds of custom tables and always their maintenance is a real cause of concern as the usual maintenance tools in SAP have their own issues. Apart from the standard tables that SAP has, a business will usually have to create many ‘Z’ tables for its custom development. Whether it is a functional or technical transaction or a basis transaction, everything in SAP or for that matter in any technology, boils down to database, and as we know database means tables. Ĭheck this document regularly for latest version source code.
#S TABU DIS RIGHTS TO CHANGE TABLE SM30 CODE#
Please find the Source Code and User Manual as links below.
0 kommentar(er)
