topic Re: Table transportation in Application Development and Automation Discussions

Table transportation

Former Member — Wed, 24 Oct 2007 01:37:56 GMT

Hello,

I have a custom table with delivery class A. We transported this table into QA and Production environments one month back. Everything is working fine.

Now we are planning to add one more field to the same table in Dev. While moving these changes to QA and Production environments will it cause any discrepancy to the existing data?

Please help me on this.

Thanks,

John

Re: Table transportation

gopi_narendra — Wed, 24 Oct 2007 01:49:29 GMT

The data will not be disturbed when you insert a new field into the existing table.

Even when transporting to QA or PRODUCTION will also not affect the existing data.

But make sure you ADJUST the database table after inserting the new field. You can adjust the table using SE14 and chose the option Activate & Adjust Table.

Regards

Gopi

Re: Table transportation

Former Member — Wed, 24 Oct 2007 02:02:10 GMT

Hello Gopi,

Thanks for your reply.

If I move this new transport(after adding the new field), will it contains Dev system table entries?

For example, the same table have 10 entries in Development , 20 entries in QA.

After transportation, these 10 entries from Dev will move to QA? How to identify that?

Waiting for your answer.

Thanks,

John

Re: Table transportation

Former Member — Wed, 24 Oct 2007 02:08:00 GMT

Hi john,

I think you are not getting the point which Gopi is telling. There are two things related to table one is table defination and other is data in the table.

When you make changes in DEV you are making changes to table defination and transporting that defination to QAS-> PRD. So because of change in the table defination you need to adjust your data and that can be done using SE14.

Regards,

Atish

Re: Table transportation

gopi_narendra — Wed, 24 Oct 2007 02:23:44 GMT

Hi John,

Tell me this first.

1). Do you want to transport the new field into QA and then Production.

2). Do you want to transport the data as well after inserting the new field to QA and then Production.

The one which i told in my above post is for Point 1).

Please revert if you have any queries

Regards

Gopi

Re: Table transportation

Former Member — Wed, 24 Oct 2007 02:23:54 GMT

Hello Atish,

Sorry for the confusion.

Actually Gopi's answer addressing my first question very helpful.

My second question is different from the earlier one, I would have used different thread for this.

Once again I am sorry about that.

Regards,

John

Re: Table transportation

Former Member — Wed, 24 Oct 2007 02:34:41 GMT

Hi Gopi,

Thanks for your concern.

1). Do you want to transport the new field into QA and then Production.

- <b>Yes, I got the answer from you.</b>

2). Do you want to transport the data as well after inserting the new field to QA and then Production.

-<b> I do not want to transport the data from Dev to other environment. I have a program to maintain the custom table data. My worry is does this transport( which is having new field) will also move the dev.data as well which I do not need.</b>

Thanks,

John

Re: Table transportation

Former Member — Wed, 24 Oct 2007 03:42:08 GMT

No when you add field to table and and assign a transport, it will not move data with the transport.

ashish