On the Downgrade Protection
tab, you can display information related to potential downgrades and conflicts.
The system has performed a downgrade check. Downgrade checks are performed automatically by the system, but you can also trigger a check manually from the Project Overview
or from the Changes
tab.
Whenever the system finds conflicts related to downgrade protection, the conflict types are displayed showing the criticality of a conflict. The following conflict types are possible:
Downgrade warning
When exporting transports (changes), you are notified of identical objects that have not been imported into the productive system yet.
Imminent downgrade
When importing transports (changes), you are notified of identical objects that have been released later and have already been imported.
Overtaker warning
When importing transports (changes), you are notified of identical objects that have been released earlier, but have not been imported yet.
Note
In Customizing, you can assign a conflict type to a check type. For each check type, you can configure the conflict criticality.
Example: If you set the conflict type for the release check to “Warning”, the system displays a conflict that is found when releasing a transport request as a warning.
The status of the conflict is displayed. “Open” means that the conflict has not been handled yet. When you explicitly ignored a conflict, the status changes to “Ignored”.
You can display details for each conflict. On the detail screen, you find more information on the conflict, for example, on the source transport and the objects involved.
You can ignore check results one by one by choosing Ignore
. You can also ignore several check results at the same time by selecting the relevant ones.
On the Changes
tab, you can trigger a downgrade check manually for the change and thus recheck it. Choose Refresh
to display the check results.