TMS Configuration

ActiveControl does not require changes to existing TMS configuration; existing transport layers, transport groups and transport routes do not need to be changed as part of implementing ActiveControl.

Also please note that there is absolutely no requirement for the ActiveControl domain controller to be the same SAP system as the TMS domain controller – in fact a single ActiveControl 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 ActiveControl determines the changes ready to be imported.

If you wish to use ActiveControl Backout functionality, then you must define an additional virtual system called BAK within TMS. This is described in more detail in the Backout section of this Administration Guide.

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 ActiveControl, but is required to avoid the unnecessary attempt to re-import the client independent content (which would usually result in an import error).