SM30 is not updating table

[Former Member]

Hi,

A table mainatenance was aleady existing for a z-table. now that Z-table had its delivery class as 'A'..and I was told to change that table so that the table becomes "a data table, instead of configuration table".

Fo that I changed the deliver class of that table to 'A' from 'C'.

In dveleopment client its working fine..(mean, changing the data with sm30).

But when the chnags were movd to quality system (cleint 555), any attempt to change the data is rasing an error msg "Clent 555 status 'not modifiable'".

please tell me what s th problem.

reward points guranteed.

Thanks,

Anid

[Former Member]

Anid,

The minute it becomes a customizing table, that means you should tranport the changes from your DEV to QA (555).

If its a application table, you can change it wherever you want.

Its like doing the customization settings in SPRO and transporting them.

Regards,

Ravi

[Former Member]

Hi Anid,

1. It seems that in DEV server,

the class of that table is now A (application data)

2. But in QA server, this has not been transported.

3. Make sure of the following two things :

a) In qa Server, the class is 'A'.

b) the revised table maintenance generator

(since class has changed, the table maintance

needs to be RE-GENERATED)

also needs to be transproted to QA server.

regards,

amit m.

[Former Member]

Hi Amit,

2. But in QA server, this has not been transported.

...it has been transported to QA also. but only thing could be, that sm30 is not re-genrated...so should it be re-generatd in DEV and then transpoted to QA or should b e-generatd in QA directly?

[Former Member]

Hi again,

1. It should be re-generated in DEV

AGAIN,

and then transported to QA Server.

2. After that things will get all right in QA Server.

regards,

amit m.

[Former Member]

I am sorry, I got it the other way around.

I guess you will to re-generate and transport the entire thing to QA.

Regards,

Ravi

[nishanthbhandar]

Anid,

The table maintenance generator need not be regenerated if there is no change made at the structure level of the table or to the maintenance condition under Delivery/Maintenance tab in SE11.

The change of a delivery class does not neccesitate the need to regenerate the table maintenance.The only thing that you need to ensure is whether you made any change to the maintenance condition in the DEV client.If so transport these changes to the Quality client(555).

After transport ensure that the versions are similar by doing a remote comparison.

Cheers

Nishanth

[Former Member]

Hi Nishant,

I guess you are correct..re-genarating is not solving the issue...furthermor it works fine in dev client without re-genaration. what could be wrong in QA?

Anybdy..please suggest me something.

Thanks,

Anid

Message was edited by: Anid

[Former Member]

Hi again,

1. What is the delivery class of this table

in QA Server.

(It should be 'A', ie. same as in DEV Server)

2. When the changes to DEV were made for 'A',

make sure that request has been transported

to QA Server.

3. If in QA server, its not 'A',

please make it 'A'

(by generating a new request in DEV server

and transporting it again)

-- There after, re-generate the table maintance,

and re-transport to qa server.

regards,

amit m.

[Former Member]

Amit,

The delivery class is 'A' in both dev and QA now..as I tranportd the chang, once it was done.

The thing is , old SM30 view of that z-table works here in dev without re-generation even after i change the delivery class from C to A, why it should not in QA?

why we need to re-generat it again?

[Former Member]

Hi again,

1. Have u (after re-generating the table maintance)

transported that request

to QA Server?

2. Transporting and getting activated in QA server

takes a little time.

(pls check whether the request (for re-generating)

has really been imported in QA server or not)

regards,

amit m.

[Former Member]

Hi Amit,

You wer right.your sugstion has solved my problem.