topic Re: TK430 - table maintenance problem in Application Development and Automation Discussions

TK430 - table maintenance problem

Former Member — Tue, 11 Aug 2009 06:20:36 GMT

Hi,

Table maintenance is done for a table and its working fine in development and quality system but not in production. When table maintenance is done in production i.e. thru SM30, it giving error TK430 i.e. "Client 100 has status 'not modifiable'. We are able to maintain other table with same settings and features and we are not able to maintain one table. Please suggest what can be the reason

Re: TK430 - table maintenance problem

Former Member — Tue, 11 Aug 2009 06:39:03 GMT

HI,

This is a problem to resolved by BASIS guys, so please contact them, this is nothing to do with the ABAP coding or transportation

Even erlier i had the same problem with a script inspite of activating and transporting to the PROD client the changes are not effective, my basis Admin using their tcodes he changed the Client status and the task was accomplished.

REgards

Ramchander Rao.k

Re: TK430 - table maintenance problem

Former Member — Tue, 11 Aug 2009 07:35:27 GMT

Hi,

The client is not open in production system.

Thats the reason why you get this message. Check with your BASIS consultant.

But you should not maintain entries directly in production system.

Maintain it in your development system and then transport the entries to production system.

Regards,

Ankur Parab

Re: TK430 - table maintenance problem

Former Member — Tue, 11 Aug 2009 09:59:39 GMT

Hi,

try t-code SCC4, I think this will help.

Thanks!

Prashant

Re: TK430 - table maintenance problem

Former Member — Mon, 09 Nov 2009 17:34:26 GMT

Go to Table Maintenance Dialog Generator (se11\GOTO).

In the box "Dialog Data Transport Detalis" you have to select "no, or user, recording routine" and Compare Flag "Automatically Adjustable".

regards

Re: TK430 - table maintenance problem

Former Member — Tue, 10 Nov 2009 15:35:33 GMT

Hello,

If you would like to change data via SM30 in a production environment without opening the customizing all times via SCC4 you have to take a look at OSS-note : Note 135028 - Transfer IMG activity to current setting

This OSS-note explains the "Current Settings" option that you can set for a series of tables.

When current settings are set for a specific table you can change customizing via SM30 without opening the customizing.

The OSS-note also explains the error message that you now receive and how to avoid it with the implementation of current settings.

In DEV and QA you don't have this problem because the customizing will be open there in tcode SCC4 (all tables can be changed then so never perform this in production !).

Success.

Wim

Edited by: Wim Van den Wyngaert on Nov 10, 2009 4:36 PM