Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Transporting a Standard table

Former Member
0 Kudos

If I added a new field to a standard table in development environment appending a structure and I transport it to production it will erase the data content in production environment ??

1 ACCEPTED SOLUTION

JozsefSzikszai
Active Contributor
0 Kudos

NO! It will leave it, as it is.

6 REPLIES 6

JozsefSzikszai
Active Contributor
0 Kudos

NO! It will leave it, as it is.

former_member182485
Active Contributor
0 Kudos

If you transport the table with the option

Transport with entries then the data in Production will be overriden by the data in development but in normal tranport it will create one more field with empty entry it will not delete the data avilable in the production.

Hope this helps

Bikas

0 Kudos

Where is that option ?

0 Kudos

Don't worry about it. If you transport an APPEND structure, it does not affect the contents of the table.

Anyway, that's why you have three systems - so you can see what happens when you transport from Dev to Test, before it destroys your Prod system.

Former Member
0 Kudos

Hi,

You have to be careful while appending fields to a standard table through structure. Once you add fields to a standard table you have to adjust these fields in standard table through database utility. Execute transaction SE14 and adjust the fields of standard database table. Otherwise may be in some situations you may get transportation error that table is not active or it may lead to short dump when you are trying to display contents of the table in higher clients.

Regards,

Venkat

0 Kudos

> Once you add fields to a standard table you have to adjust these fields in standard table through database utility.

Not quite so. Only when fields are being deleted or changed in its definition, then an adjustment via SE14 is necessary (if not automatically done at time of import), not when new fields are being added. This is at least true for Oracle, probably for other DBs as well.

Thomas

P.S. I even had to learn recently that when deleting fields in reverse order of the time they had been added, then there is no adjustment necessary (Last in, first out, if you will...)