transport issue..

[Former Member]

hi,

i created a table in sap system 1. created its related technical settings and enhancement category etc. all these were stored in a single transport request.

later i noticed that i dont need this table and hence in SE09 i removed the entry of this table from the "Table" and "Table defintion" node. I missed removing the corresponding entry from "Technical attributes of a table". But I did not remove the table physically from the system ! Then released the transport.

Now when this transport was moved to another system, transport errors were encountered saying "This table is not an active table". My understanding is that during transport movement, it checks if this table existed in the new system. As it does not and also as it is not part of the transport request, it is not able to move the technical attributes also . Am i right ?

So what is the solution ? Can i just recreate that table in the new system (target) and try to re import the transports ? Wil this solve the issue ? pl advise. thks

[Former Member]

hi,

i created a table in sap system 1. created its related technical settings and enhancement category etc. all these were stored in a single transport request.

later i noticed that i dont need this table and hence in SE09 i removed the entry of this table from the "Table" and "Table defintion" node. I missed removing the corresponding entry from "Technical attributes of a table". But I did not remove the table physically from the system ! Then released the transport.

Now when this transport was moved to another system, transport errors were encountered saying "This table is not an active table". My understanding is that during transport movement, it checks if this table existed in the new system. As it does not and also as it is not part of the transport request, it is not able to move the technical attributes also . Am i right ?

So what is the solution ? Can i just recreate that table in the new system (target) and try to re import the transports ? Wil this solve the issue ? pl advise. thks

[JozsefSzikszai]

"As it does not and also as it is not part of the transport request, it is not able to move the technical attributes also . Am i right ?"

yes, you are right

"So what is the solution ? Can i just recreate that table in the new system (target) and try to re import the transports ? Wil this solve the issue ? pl advise. thks"

The question is: do you need that table in the target system? If no, than you don't have to do anything, if yes, than create a transport request with one line in it: R3TR TABL name_of_table Then release and import as usual. This will take everything related to the table.

hope this helps

ec

[Former Member]

The important thing to learn here is not to manually fiddle with transport requests!

If you don't want an object in the target system then delete it in the source, assigned to your transport and still move that transport through the systems.

Whilst it can be easy to manually add/remove entries from transport requests it is also very easy to muck things up doing this. It's much better to work with the objects themselves and let the transport just carry the changes you make.

I've been on systems were the transport system is riddled with random transports in all sorts of states with objects missing, deleted, manually added etc and it just becomes a nightmare over time. I personally think it is much better to ensure you apply all transports through your landscape in the correct manner - if you move something through you don't actually want then follow it up with a corrective transport. If nothing else, it gives you a more obvious audit trail to see what has happened to objects.

Gareth.

[Former Member]

Thanks Eric, I do not need this table in the new system.

[Former Member]

Thanks Gareth. Actually my next question is based on what you said. I wil post that in a separate thread. hks