Show TOC

Function documentationRisks Tab


The Risks tab shows the risks associated with transports in your project. This enables the quality manager to take action and react to critical situations appropriately, and correctly assess the risks to the project.


You must have created a project with the data required for quality gate management.

Note Note

Collecting transport data from remote systems takes some time. Therefore, the system does not collect transport data when displaying the Risks tab in order to not decrease the performance. In order to display the latest state of software distribution, you can update the data by choosing Refresh on the right—hand side.

End of the note.


Before each phase or phase completion, the quality manager can assess whether all transports have run correctly into the next system, or whether measures must be undertaken to ensure that they do so. The upper table of the Risks tab contains the following columns:

To view the risks, proceed as follows:

  1. Choose a project for which you want to review the risks.

  2. Choose the Risks tab in the lower screen section.

  3. The upper table displays a list of systems in which risks have occurred. The list contains the following information:



    Logical System

    The logical system and client involved

    Transport Risk Type

    The transport risk type — see below for further information.

    Number of Risks

    The number of transport risks in this system


    The date/time when the data was last read from the remote system.

  4. Choose a system. In the lower table, the transport requests for a risk type in this system are displayed.

The following transport risk types may be displayed:

Transport Risk Type


Transport error (return code ≥ 8)

If an error occurs when importing a transport request, the transport error is reported as a transport risk for this target system.

Open transports

If a transport request is not released, it is reported as an open transport for the source system.

Missing transports

This applies only to released transport requests. Released transport requests are reported as missing transports for a target system if the transport request was supposed to be imported into this system, but was not imported so far. Missing transports are calculated for the respective system track, but are not reported for the source system.

Synchronization errors

Refers to transports that did not run synchronously (for example, synchronization errors in projects with more than one export system)

More Information

For more information on how to work with transport risks, see Declaring a Transport Error as Repaired.