Also here the problem is that I have master data, customizing data and even application data and logs in some of these tables in the development system which I cannot loose, in addition to needing the developments there in future as well.
Unfortunately the trick with the empty sandbox and releasing a transport with the object list in it did not work. R3trans spotted it and instead of converting into a deletion request (which is what I was hoping...) it stopped the export.
That is of course much worse than what I originally anticipated... :-(
I discovered that TADIR actually has a table mainenance view to add entries directly (which very much surprised me actually...). In that case one can maintain the entries before releasing the transport and then r3trans should remove them again on export and change it to a deletion request. That is how the normal was of recording an object which you then delete works as well.
Somehow I think I am not "back to standard" using this approach... but am optimistic that I am getting warmer and it will not be impossible.
***holding thumbs***
Cheers,
Julius
