The default sequencing of transports for import within ActiveControl is based on the release date/time of the transports.
For example, if transport A is released at 15:00 on 1st January 2022, and transport B is released at 16:00 on 1st January 2022, and both transports are sitting in an Import Queue, then ActiveControl would ‘order’ Transport A to be imported before transport B.
It is possible to change this default transport sequencing by hardcoding Dependencies between transports.
ActiveControl allows for inter-dependencies to be defined between transports in the same system (for example, if a functional Customising transport is dependent on a particular Workbench transport), and also for cross-system dependencies between transports being deployed in different SAP development systems (for example, if a BW transport is dependent on a particular ECC transport)
In both cases, these Dependencies are defined on the Advanced Options tab of the Transport Form in the SAP GUI or Web Platform.
Technically, when ActiveControl checks a dependency where transport A is dependent on the prior import of transport B, it checks whether transport B has been applied to the SAP system that transport A is being applied to, or that transport B has been applied to at least one other SAP system with the same role as the SAP system that transport A is being applied to.
Business Task Relationships
Within ActiveControl, it is also possible to create relationships between Business Tasks. This can be useful in the scenario where there are no technical dependencies between Transports that necessitate two changes being imported at the same time or in a particular order, but where the user wants to ensure two Business Tasks get deployed through the landscape at the same time for other business reasons.
Business Task Relationships are set via the Dependencies subscreen on the Business Task.
Business Task Dependencies
Within ActiveControl, it is also possible to create dependencies between Business Tasks. This can be used by customers that prefer to manage transport sequencing based on change (ie Business Task) sequence. Business Task Dependencies is functionality that most SAP customers will likely not use as in most situations it makes more sense for the sequencing to be driven by the individual transports and their object contents, but for those that want to utilise this optional capability, Business Task Dependencies are also set via the Dependencies subscreen on the Business Task.