I was asked recently to assist in creating a virtual system in order to be able to move some BI objects from a ringfenced POC system into a development system for some upgrade work.

The TMS configuration was simple to do, but the colleagues had problems when trying to assign the package to the TMS route. I documented this for them how to do this, and they thought that others may find this useful. So hope you do!

Sometimes you want to do things in TMS that is not the normal 3 or 2-tier configuration, and you need to modify so that you export / import a transport into a different system.
Remember to be able to export a transport - you MUST be able to create a datafile and a cofile (in /usr/sap/trans/data and cofile respectively).

That means that you need to assign a transport target in SE01 (header) that is NOT $TMP i.e. local. 





So in this example - you want to assign some specific objects to another system e.g. ABC.
You can do this by creating a virtual system in TMS, and then assigning the route ZBW3 from the source system to the target.
However you will find that the objects may belong to a package that is not bound to ZBW3, and it could be bound to ZNW3 ...

So how do you change the package assignment?
Easy ...
Identify the package the object belongs to via SE38 / SE37 or SE16 etc.





And so in this example you need ZTEST to be a real transport, so you can bind this to ZBW3 (even if this was bound to ZNW3 it would create .. but this could be Prod and doesn't have another route!).

OK so in SE80 you need to assign the transport layer to the package...





Drop down on the package, and then click on change... modify the transport layer attibute.

Save it and you can then add the object to the transport, assign the transport to the target and you are done after you release the transport.

You can now copy the cofile / datafile and move manually to where you need to the system you want to import.

Jeff Forshaw, Support Services Technical Team Lead, Bluefin Solutions