Before an SAP transport request can be transported using ActiveControl, a Transport Form must be created for the SAP transport request.
The Transport Form is a simple form that is used to document and categorise the changes made, so that Approvers, Testers and Auditors can immediately understand what the Transport is for.
Every SAP transport needs to have a corresponding Transport Form within ActiveControl. This is true of both ABAP transports and also non-ABAP changes being managed by ActiveControl using CTS+ or cloudTMS.
The Transport Form consists of several standard tabs, each containing various standard fields and other functionality. It is possible to add custom fields to the Transport Form via configuration. It is also possible to make most of the standard fields or custom fields optional or mandatory via configuration. Mandatory fields will show with a red asterisk *.
Figure: The ActiveControl Transport Form in the Web Platform.
How Transport Forms move through the Path / Workflow.
When a Transport Form is created, the transport request automatically flows to the “root” Target of the Path. Once a transport request finishes processing within a particular target, it flows to the targets that follow on the transport path. For example, if the Production target follows the Test target in the transport path tree, then a transport request that is assigned to the transport path will be imported into Production after it has been imported into the Test target – and potentially after the associated task has been tested and/or the changes approved out of the target (if these transport path options are enabled for the target).
The transport path also specifies whether transport requests need to be approved into, tested in and/or approved out of a target system (these are the Inbox, Test Queue and Outbox options respectively). Simply enable the desired options using the checkboxes that appear alongside each target system in the transport path tree.