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. Reason: If the transport request released first is imported second, the conflict object is downgraded.

Prerequisites

See Downgrade Protection.

Activities

  1. You release a transport request.

  2. The system performs the downgrade check.

  3. When the system finds conflicts, the release is cancelled, and the conflicts are logged. The conflict check results are displayed in the Downgrade Protection assignment block in Change Request Management or in the Downgrade Protection tab in Quality Gate Management.

  4. If you want to ignore the conflicts, check the results on the assignment block and ignore them explicitly.

  5. You can then start the release of the transport request again.

Example

  1. You modify a function module, Z_TEST_FUNC1, and save it in transport request DEVK000001 in normal 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 normal change NC2, bypassing the CSOL warning in the managed system.

  4. When you try to release DEVK000002, a conflict message is shown and the release is canceled. The system displays the conflicts.

  5. To continue to release, the change manager must ignore those conflicts. Alternatively, you can import DEVK000001 into the production system by importing it into the quality assurance system through a project import, and then import it into the production system through a project import. DEVK000002 can then be released without conflicts.