Show TOC

Function documentationRelease Check

 

The system performs this downgrade check when you release a transport request. The system can detect conflicts for objects in different transport requests. If a transport request that was released first were to be imported second, the conflict object would be downgraded. The release check prevents this issue from occurring.

Prerequisites

For a list of prerequisites, see Downgrade Protection.

Activities

  1. You release a transport request.

  2. The system performs the downgrade check.

  3. If the system detects a conflict, you are prompted to either cancel the release or (depending on your authorizations) to ignore the conflict and continue with the release.

    • If you cancel the release, the conflicts that were detected are logged. The conflict check results are displayed in the Downgrade Protection assignment block in Change Request Management or in the Downgrade Protection dialog box in quality gate management.

    • If you ignore the conflicts and continue with the release, the conflicts are archived in the system.

Example

  1. You modify function module Z_TEST_FUNC1 and save it in transport request DEVK000001 in change NC1.

  2. You release DEVK000001 without noticing any conflicts.

  3. You modify the function module again and save it to another transport request, DEVK000002, in change NC2, bypassing the cross-system object lock warning in the managed system.

  4. When you try to release DEVK000002, a conflict is shown.

  5. To continue with the release, you can ignore these conflicts. Alternatively, you can import DEVK000001 into the production system by importing it into the quality assurance system, and then import it into the production system. DEVK000002 can then be released without conflicts.