Unable to edit maintenance view in SM30

[Former Member]

hi everyone.

need your help, I have one custom table, let's call it YTAB. This table has several maintenance views created for it, depending on company code. For YTAB, i have created a maintenance view YTABX.

When we moved YTABX to PRD, we cannot edit it in SM30. The user ID has the right authorization. The error message is "client 100 not modifiable". When I try to edit the mother table YTAB in PRD, I am able to go in and do the changes.

I have already compared the settings for YTABX with the other existing views, they are the same. My settings for the view are:

Access: Read, change, delete & insert

Delivery Class: C

In the table maintenance generator, i have a 2-step maintenance type, recording routine is Standard recording routine and compare flag is automatically adjustable.

Attributes for table YTAB also has delivery class C, table category is transparent table, table maintenance is allowed.

Thank you in advance.

[Former Member]

Hi,

In SE54 (maintenance dialog), try setting "no, or user, recording routine" instead of Standard recording routine".

Regards,

Mark

[venkat_o]

Hi, <li>While generating maintenance generator you give Authorization Group. Check what you have given there. Try to give &NC& (No authorization). Thanks Venkat.O

[Former Member]

While generating maintenance generator you give *Authorization Group*. Check what you have given there. Try to give *&NC&* (No authorization).

I don't think this is the issue. The message "Client xxx not modifiable" indicates that the system requires the changes to be recorded in a customizing change request.

[Former Member]

> Try to give &NC& (No authorization).

This is also an urban legend. "&NC&" means that it is "not classified", so the system assigns this symbolic group to the table.

It is a polite way from the system of saying that if you want to display the table directly, then you should create a view even although none was foreseen.

In blunt terms: You are being silly and short-sighted

Cheers,

Julius

[Former Member]

hi mark.

i tried your approach. i have already released the transport and just waiting for the transport window. i will let you know what happens.

thank you very much for your help.

[romanweise]

Hello roch,

the direction in which mark points is right but i think you should get some more information on the principles of table types and sap system landscape.

Usually you should not be able to directly maintain any table. This is not only bad style but also a huge risk for the system consistency. That's why application data is always maintained via some kind of application which ensures that the data is vilidated before it is stored.

Customizing data should only be maintained within a development system and then transported through the landscape. To maintain these table you can use generated views, customer developed maintenance views, view clusters which all include automatical link to the transport system. If you would maintain these tables directly in the productiion system it would have another configuration than the development and the quality/test system which makes them more or less useless as you can no longer make any serious test if the server configurations differ.

To prohibit changes of customizing tables on production and test servers the admins lock the systems which results in the message you got. This setting is made in TCODE SCC4. Even if you have for any reason the authorization to use this transaction you should in no case change these settings without approval of basis / system owner.

Kind Regards

Roman