Advanced Options – Dependencies

As mentioned in earlier Transport Sequencing section of this User Guide, the default sequencing of transports within ActiveControl is based on the release date/time of the transports.

Dependencies can also be manually set between Transport Forms. This is useful if SAP Transports have been released in the wrong order and you want to force ActiveControl to import them in a specific order – or in the more common scenario – where you want to set cross-system dependencies between transports (eg when a SAP CPI change has to be deployed only after a specific S/4HANA transport has been imported).

Dependencies are set via the Advanced Options subscreen of an individual Transport Form.

Setting a Dependency on this screen indicates that this particular Transport Form is dependent on the Transport Form that you add, ie it is the other Transport Form that should be approved/imported before or at the same time as this one.

Figure: Dependencies within the Advanced Options subscreen on a Transport Form.

Release Orchestration / Pending Import

If ActiveControl ‘Orchestration’ is configured by your local ActiveControl Administrator(s) , then if a dependent transport is in the Import Queue, it will sit in ‘Pending Import’ status until the pre-requisite transport has been imported. When the prerequisite gets imported, the dependent transport will also automatically be imported, regardless of when the next automated import is scheduled to occur. The pre-requisite transport can be viewed via the Global View or the Awaiting Import apps, by looking at the Import History.

Dependencies as part of Fast Import import method.

Whilst using the “One at a Time – AC Default Sequence”, any dependencies are taken into account of the calculated sequence. The same is also true as part of the “Fast Import Method – AC Default Sequence” import method – when you are selecting multiple transports for import and using the ActiveControl equivalent of SAP Block Import All to import a selection of transports.