data edit in table trough SM30

[Former Member]

We have made a z table and create table maintainace without restriction type . More than one person has put and edit multipe time the values in table . many time some one has edited the row which was updated before and after by different person and saved in different request number .

Finally table has all values and there is 4 requests . I want to move all these entry in one request only . How can be possible, Shall i use transport mensioned in SM30 and create a new request , will it have the all values .

I am not moveing the multiple request bcoz the sequesnce of request is not proper as some one edited some one created and saved in different request numbers .. . bla bla

pls suggest .

Thanks

[Former Member]

We have made a z table and create table maintainace without restriction type . More than one person has put and edit multipe time the values in table . many time some one has edited the row which was updated before and after by different person and saved in different request number .

Finally table has all values and there is 4 requests . I want to move all these entry in one request only . How can be possible, Shall i use transport mensioned in SM30 and create a new request , will it have the all values .

I am not moveing the multiple request bcoz the sequesnce of request is not proper as some one edited some one created and saved in different request numbers .. . bla bla

pls suggest .

Thanks

[ThomasZloch]

You can merge the object lists of several transport requests into a new one using tx SE03 transport tools, then delete the old ones and only work with the new one. Alternatively, use utilities -> reorganize -> merge requests from within SE10.

Next time, try to combine related tasks by different users into one transport request right away.

Thomas

[Tamas_Hoznek]

If those four requests are not released yet, they only contain table key values, not the actual table entries that the person modified.

You can create a new request and specify the four keys or just enter * as the table key (client+* if the table is client-delendent) in case you want to transport the complete content of the table. The current entries will be transported then.

[RaymondGiuseppi]

You can merge the requests via SE03, or you may transport the four requests together as the imports will be executed in the same sequence that they were released, and the result should be correct.

If you merge requests you will transport the current value of those records, if you transport the four request in the good sequence (implicitly if transported together) you will get the value of the last change at release time which may differ only if some records have been changed after the release of the last order which contain them.

Regards,

Raymond