The Risks
column in the changes overview shows the risks associated with transports in your change. This enables the quality manager to take action and react to critical situations appropriately.
You have created a scenario with the data required for quality gate management.
Before each phase or phase completion, the quality manager can assess whether all transports have been imported correctly into the next system, or whether measures must be undertaken to ensure that they do so.
To view the risks, proceed as follows:
Open the scenario for which you want to review the risks by clicking the link in the Scenario
column.
Choose the link in the Risks
column, or choose from the header area.
The upper table shows the systems for which there is a risk. It contains the following information:
Column | Meaning |
---|---|
| The logical system and client involved |
| The transport risk type (see below) |
| The number of transport risks in this system |
| The date and time when the data was last read from the remote system. |
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 | Meaning |
---|---|
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. A released transport request is reported as a missing transport for a target system if it is supposed to be imported into this system (that is, it is already in the system queue) but has not been 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 scenarios with more than one export system) |
For more information about how to work with transport risks, see Declaring a Transport Error as Repaired.