Regarding Table maintenace

[Former Member]

I have already created the maintenance for the table, transported to staging.

Now if the requirement of some change in one of attribute came,

Do I require to delete and create table maintenance again or simply making the changes and storing in a new transport request will work?

Message was edited by:

SHEFALI GANGRADE

[Former Member]

u have to delete the table maintenance generator and create a new one for the changed attributes to get reflected....If u just save and generate the changed attributes will not be reflected...So, delete the existing one and create a new one...

[anversha_s]

hi,

1. do the changes.

2. activate and adjust the data base.

3. create a new table maintenence again.

Rgds

Anver

[Former Member]

hi,

you need to delete the existing table maintenance and recreate and generate again

[gopi_narendra]

Yes you will hve to delete the maintenance and regenerate the table maintenance for any change done to the table, or filed or attributes.

before that u need to adjust the table also.

Utilities - > Database Object - > Database Utility

Regards

- Gopi

[Former Member]

I have done the chages and transported to ST2.

The attributes which i have changed are reflecting in ST2. why table maintenance is required to create again?

will it create any problem when it will go to production?

Message was edited by:

SHEFALI GANGRADE

[anversha_s]

Hi,

it will not create any problem.

you create a new table maintenece generator and transport.

thats all.

rgd

anver

[Former Member]

Yes, the attributes will reflected while transporting from one system to another without creating a table maintainence generator again. but while creating the entries in the table it would not consider the changes. so, you have to create table maintanance generator again.

thanks

Sekhar.

[gopi_narendra]

Yes if you dont regenerate the table maintenance u will not be able to see the changes when u maintaint the data. still u see the changes being transported, but not maintenacen unless u regenerate it.

Regards

- Gopi

[Former Member]

I have changed following things at table and maintenance level:-

1. table delivery class

2. table data class

3. In maintenance screen

recording routine from 'standard' to 'no user'

4. in maintenance screen (to remove inconsistencies occured to change in delivery class and other attributes of table.)

Environment>maintenance object>

category= from CUST to APPL

transport = automatic to no transport

and saved in one trasnport request and transported to staging.

in staging these are reflected properly also the mainteanace is working fine.

these changes are yet to go to production, as these are working fine in staging then why new maintenece is required to create?

please help to clear my doubt.

[anversha_s]

Hi,

Its will reflect perfectly, only after creating a new table maintenece generator.

Rgds

anver

[Former Member]

"the attributes changes will reflecting while transporting to another system,

but without regenerating it will not work."

if this is the case then

1. why the changes done in the Developemnt are giving proper results while testing the changes without recreating the view again?

2. why in the staging or production, even though attribute changes are reflected but not considering the new attributes?

Is there any reason. please help to clear the doubt.

Message was edited by:

SHEFALI GANGRADE

[Former Member]

The run time object will not regenerated without the regeneration of tablemaintenace generator.

so we have to regerete the table if any changes in the attributes or inserted the new fields also.

Thanks

Sekhar

[Former Member]

Thanks for all your help.

as per your suggestion,

1 .I haave deleetd the maintenanace view.-- it is saved in one transport request.

2. Now form utilities>databse utility>

I have clicked on 'Activate and adjust databse'- it has not asked for any transport request.

what to do?

3. when i will create maintennece view, i will save in the same transport requesta as the one created while deleting the existing maintenance view, is this right?

please let me know about adjustment changes, what to do?

[Former Member]

yes right. u can save it to the same transport request.

For adjustment of data base utility you need not to attach to the transport request. it won't ask you to attach the transport request.

Thanks

Sekhar

[Former Member]

Just by putting deleted objects and created objects into one tansport request,

will solve by problem of table maintenance?

Do something else is required to do?

Do adjust utility required to run in prodution?

[Former Member]

Hi,

Here, you are not putting the deleted objects in the transport request.

while deleting the tablemaintanence generator it will ask the transport request ( it means it will delete that object from the request).

So we are not keeping deleted objects in the TR.

U need not to bother about production system.

just we have to regenerate the table maintenance generator.

you problem will be solved.

thanks

Sekhar.

[Former Member]

Hi Sekhar,

thanks for help.

My table and data maintenance are already in prduction.

so i had put the deleted and recreated objects in the same transport request so that when it will apply to production server, everything will go in sequence and will work fine.

only my concern is , as i have adjusted the database table, what to do about this sequence in production?

[Former Member]

Thanks to all,

The actual reason to recommend the recreation of table is as follows:-

when we create the table maintenance, the view's attributes are decided from the delivery class of table.

if we are doing any change to the table's delivery class, the corresponding change will not reflect in the view's property.

so either recreate the view again or

manually change the views property as follows:-

se11->utilities->table maintenanace generator--> in recording routine change from 'standard' to 'no user'

also in the same screen

environment>Maintenance object. diplay->

change the following attributes:-

Transport --from automatic to no transport

category -- CUSt to APPL.

if we are manualyy changing the view's property, no need to recreate the view agin.