Show TOC

Function documentationConflict Analysis Scenarios

 

You can either use the default conflict analysis scenario, which is cross-cycle (cycle relation Cross, change type relation Urgent Only) or define a different scenario in the /TMWFLOW/CONFIG_CSOL report using the expert mode.

Features

The conflict analysis function differentiates between the following:

  • Conflicts between transport requests that belong to the same cycle and conflicts between transport requests that belong to different cycles

  • Conflicts for urgent changes and conflicts between transactions of another type (a conflict between an urgent change and a normal change, or a conflict between normal changes, for example)

Note Note

Whether you can continue to change an object depends on the analysis scenario configured and the conflict scenarios involved.

End of the note.
Scenarios

The following list describes the different cross-system object lock scenarios that you can use. Only conflicts that lead to an error are described. All other conflicts in the scenarios trigger a warning only; you can decide whether to change the object.

  • Cross-Cycle, Urgent Only

    If an object conflict arises between two urgent changes, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests, both within one cycle and in two different cycles.

  • Cross-Cycle, Partial Overlapping

    If an object conflict arises between two transport requests and at least one of them is contained in an urgent change, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests, both within one cycle and in two different cycles.

  • Cross-Cycle, Overlapping

    If an object conflict arises between two transport requests for any change type, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests, both within one cycle and in two different cycles.

  • Cycle-Specific, Urgent Only

    If an object conflict arises between two urgent changes, the system displays an error and does not allow you to change the object. This applies within one cycle only.

  • Cycle-Specific, Partial Overlapping

    If an object conflict arises between two transport requests and at least one of them is contained in an urgent change, the system displays an error and does not allow you to change the object. This applies within one cycle only.

  • Cycle-Specific, Overlapping

    If an object conflict arises between two transport requests for any change type, the system displays an error and does not allow you to change the object. This applies within one cycle only.

  • Different Cycle, Urgent Only

    If an object conflict arises between two urgent changes, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests from different cycles.

  • Different Cycle, Partial Overlapping

    If an object conflict arises between two transport requests and at least one of them is contained in an urgent change, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests from different cycles.

  • Different Cycle, Overlapping

    If an object conflict arises between two transport requests for any change type, the system displays an error and does not allow you to change the object. This applies to conflicts between two transport requests from different cycles.