The ActiveControl workflow is built to simulate the necessary steps (ie approvals, test, signoffs, imports) that need to be performed as part of moving a change through a customer’s SAP landscape.
At its core level, this workflow consists of Paths and Targets.
A Target within ActiveControl is typically an SAP System. Examples of Targets include:
i) S/4HANA Development
ii) S/4HANA Quality Assurance
iii) S/4HANA Production
A Path within ActiveControl is a collection of Targets that maps out the route by which a change (ie SAP transports) move through the landscape. Examples of Paths include:
i) S/4HANA Production Support path
ii) S/4HANA Project path
Figure: Targets and Path within ActiveControl.
Existing transport layers, transport groups and transport routes within TMS 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 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).