What is Table Maintenance Allowed ?

[Former Member]

What is the Table Maintenance Allowed in Table attributes... And where it is utilized in practical environment ?

[Former Member]

What is the Table Maintenance Allowed in Table attributes... And where it is utilized in practical environment ?

[Former Member]

Hi saurabh,

By keeping Table Maintenance Allowed = True, one can edit the contents of the table, enter values into the table, can also delete the contents of the table.

Thanks & Regds,

Ravikiran.

[Former Member]

Hi,

If you switch the table maintenance on then you will be able to insert/delete/update the entries of that particular table, for that you need to generate this using SM30 transaction.

Rgds,

[Former Member]

Sir..

I what case we switched off that and in what cases on ?

and what is the practical use of it?

[nishanthbhandar]

Hi Saurabh,

The databrowser/tablemaintenance allows you to define whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).This can be set for database views, projection views, maintenance views, mantenance view variants, and tables (called 'Table/ View' below) using transaction SE11.

See the below three options and their usage :

Display/maintenance not allowed :The usage of standard table maintenance tools is not allowed.Maintenance and display of this table/view 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 table/view 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 table/view, but no maintenance.Generation of a maintenance dialog for this table/view is possible through

through transaction SE54.Transaction SM30 does not allow maintenance and display functions for this table/view.Transaction SM30 does not allow maintenance and display functions for this table/view.

Display/maintenance allowed :The usage of standard table maintenance tools is allowed,Transaction SE16 allows the maintenance and display functions for this table/view.If an SM30 maintenance dialog exists, this is called.

Transaction SE54 allows the generation of a maintenance dialog for this table/view.Transaction SM30 allows the display and maintenance functions for this table/view.

Cheers

Nishanth

[Former Member]

Sir.. that is fine that with 3 options on maintenance we can open table through certain transactions. Sir maintanance allowed or not allowed related to the data it is containing ? or the System setting like delivery class, buffering setting etc ?

[Former Member]

Hi Saurabh,

Whether a table should be allowed for maintenance is something that depends on the kind of data that the table contains.

Let us say consider the table VBAK - which contains the header details for the Sales Documents in R/3. The delivery class for this table would be "A" - meaning that this table contains master and transaction data. Obviously, this data has to come from a program, typically a transaction. A user can , for example, create a sales order through the VA01 transaction and the header data will be stored in this table on saving the Sales Order.

Now consider the table T001. This table contains the company codes in the R/3 system. This table has the delivery class "C" - meaning that it contains customizing information. This data will be used in thousands of other transactions and tables. There are very few things that you would maintain for a company code. So it can as well be maintained through a table control (which you see in the table maintenance screen).

Hope the point is clear...

Regards,

Anand Mandalika.

[Former Member]

It means that for table VBAK I'll use table maintenance allowed but with restrictions and for table T000 i'll use table maintenance not allowed ?

Is it like that ?

Sir that maintenance is also for technical setting of the table ?

Sir I'm confusing with that this option is for Table data or table settings ? Sir is this option we have to keep in mind for doing projects or can we handle though programming also because we do dialog programming for user and user can never access the table.. is it possible for user then to change anything in table??

What if I change the data element or domain of the table it has data ? Will it just give me waning for data lost or it has any relation with that table maintenance option ?

Sir table maintenance option is for End-user only or it for testing team also ?

[Former Member]

Hi,

The option Table Maintenance allowed with restrictions means -

Display/maintenance is allowed to limited extent.

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

- Transaction SE16 allows the display function for this

table/view, but no maintenance.

- Generation of a maintenance dialog for this table/view is

possible through transaction SE54.

- Transaction SM30 does not allow maintenance and display

functions for this table/view.

For more information about what the other two options mean, just place your cursor on that field and click on F1.

No, the maintenance is only for the table's contents (data).

If the table is allowed for maintenance, then the user will be able to go to the SE16 / SM30 transaction and change / delte the contents of the table. So, we would generally use the Authorization concept to see to it that this does not happen. But even if the user is not able to change anything in SE16, it simple doesn't make sense to make the table table with transaction data maintainable.

If you change the data element and / or domain of the table fields, then you will have to use the <b>database utility</b> (you can find this under the Utilities menu). The database utility takes care of any possible data truncation etc., and will tell you whether this table can be altered.

Strictly speaking, Table maintenance option is intended for the end-users. But in some cases, I have known the testing teams to enable the table maintainable and populate it with various test data to test the functionality for various cases. Finally, when they are through with testing, the table maintenance is again disallowed and the table is delivered to the production system. This might be desirable because when the table is newly created in the development environment, it would not be having any data in it. so we might have to create some data in it ourselves for testing purposes.

Hope that is clear.

Regards,

Anand Mandalika.