Paths and Workflow

As mentioned earlier in this Administration Guide, a transport path is a hierarchy of target SAP systems, determining the systems that a transport request will be imported into and in what order. The transport path also determines whether changes need to be approved and/or tested.

Each transport request is associated with a single transport path when the Transport Form is completed. The transport path is usually selected automatically, according to the default settings made here, and ensures that transport requests are imported into the same systems, keeping the landscape in sync.

Usually only one transport path is necessary per development stream. For example, you might have one transport path for transporting between the development, test and production R/3 systems, and another transport path for transporting between the development, test and production BW systems.

Transport Paths, and the associated Workflow are created and edited by ActiveControl Administrators via the Paths and Workflow app tile. The configuration process consists of four steps:

1) Create Path.
2) Drag and Drop Targets into the Path.
3) Switch on the required Control Point workflow.
4) Add Deployment Statuses to each Control Point.

Paths and Workflow configuration screen within the ActiveControl Web Platform.