In the Downgrade Protection
assignment block, you can trigger the manual downgrade check and display information related to potential downgrades and conflicts. The assignment block is available in the following change transactions:
Continual cycle
Phase cycle
Release cycle
Urgent change
Normal change
Defect correction
Whenever the system finds conflicts related to downgrade protection, the conflict types are displayed as icons 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 and an icon.
Example: If you set the conflict type for the release check to “Warning” and assign the warning icon, the system displays a conflict that is found when releasing a transport request as a warning and shows the yellow warning icon.
The status of the conflict is displayed. “Open” means that the conflict has not been handled yet. If you explicitly ignore a conflict, the status changes to “Ignored”.
You can display details for each conflict. The detail screen contains more information about the conflict, for example, 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.
You can trigger a downgrade check manually for the change transaction and recheck it. Choose Refresh
to display the check results.