Transport Expresso does not require changes to the TMS configuration, particularly the existing transport layers, transport groups and transport routes do not need to be changed – however note that Transport Expresso does not use this configuration. Also please note that there is absolutely no requirement for the Transport Expresso domain controller to be the same SAP system as the TMS domain controller – in fact a single Transport Expresso domain controller can manage transports for multiple TMS domains.
In order to maintain tidy import queues within TMS, it can be useful to change the transport routes for transportable changes to direct changes to a dummy virtual system. This is not a requirement, however it can prevent confusion caused by standard TMS functionality adding transport requests to the TMS import queue of recipient SAP systems in advance of when Transport Expresso determines the changes ready to be imported.
If you wish to use Transport Expresso backup functionality, then you must define an additional virtual system called BAK, as described in the previous section Backing Out Changes.
Finally, if you wish to import changes into other clients of the same (development) system in which the changes were originally made, then you should enable TMS’ extended transport control. This is not a requirement so much of Transport Expresso, but is required to avoid the unnecessary attempt to re-import the client independent content (which would usually result in an import error).