topic Re: Table Maintainance Generator in Application Development and Automation Discussions

Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:22:48 GMT

I have created a table maintainance generator for a table and assigned it to a Transaction code.

When I run the transaction Code I see the following message

"Client XXX has status 'not modifiable'".

This is happening only in one client.Not in any other client.

Can someone tell me why this is happening and how we can resolve it?

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:24:43 GMT

Try to get SM30 authorisation for that client from Basis.

Regards

Abhishek

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:26:23 GMT

Hope it will help you.

Reward pts if help.

table maintanance Generator is used to manually

input values using transaction sm30

follow below steps

1) go to se11 check table maintanance check box under

attributes tab

2) utilities-table maintanance Generator->

create function group and assign it under

function group input box.

also assign authorization group default &NC& .

select standard recording routine radio in table

table mainitainence generator to move table

contents to quality and production by assigning

it to request.

4) select maintaience type as single step.

5) maintainence screen as system generated numbers

this dialog box appears when you click on create

button

6) save and activate table

http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm

http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm

/message/2831202#2831202 [original link is broken]

One step, two step in Table Maintenance Generator

Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.

Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:30:17 GMT

Actually its a maintainance its a Maintainance View.

Not a transparent table.

While creating the tcode I gave the reference transaction as SM30 and screen number as 0.

What has to be done?

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:32:10 GMT

Hi,

If u r in same client it must allow to change.

Check it is same client or not once again and any authrization objects assigend to that table.

Regards,

Narasimha

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 04:45:07 GMT

They are different clients.

Are Maintainance Generators not modifiable in the non-modifiable clients?

I see the message long text as this

"Client 210 has status 'not modifiable'

Message no. TK430

Diagnosis

The system administrator has set your logon client to the 'not

modifiable' status.

Client-specific objects can not be changed in this client.

System Response

The function terminates.

Procedure

Contact the system administrator.

For more information, see the SAP Library under Change and Transport

System."

Re: Table Maintainance Generator

Former Member — Wed, 14 May 2008 19:15:18 GMT

Thanks

Re: Table Maintainance Generator

Former Member — Wed, 08 Jun 2011 08:38:29 GMT

Problem can be solved by following snote#301665.

Solution:

In the live system, set the "Current settings" (CURSETTING) indicator in the OBJH table for the detailed screen of the overhead rates, the V_KONX view. Depending on your release, proceed as follows:

As of Release 4.6

As of Release 4.6, you can set the "Current settings" indicator for the V_KONX view directly. To do this, call transaction SOBJ and select the V_KONX object. Select "Details" (magnifying glass, F2) for the V_KONX object. Select the "Current settings" indicator on the detail screen in the "Derived attributes" group box and save this setting. Transfer this change to the OBJH table in the live system.

Reset the 'Current settings' indicator in a client that is not flagged as live, since the indicator prevents the inclusion of the add-ons in a transfer order (if the corrections from Notes 709504, 733777 and 820955 have been implemented in the system).