Conflicts can occur when a change comparison is run to determine the change steps for adapting a network to a new characteristic value assignment.

Certain conflict situations have been pre-defined in the system. In addition you must define change profiles in Customizing by choosing Structures ® Operative Structures ® Networks. In these profiles you define the conflict character of further change steps. If steps cannot be executed automatically because of conflicts, you have to trigger execution manually in the change step overview after removing the cause of the conflict, if required.

The system reacts as follows:

• Conflicts with information character: The change step is executed automatically and you receive a message in the change step overview.
• Conflicts with warning character: The change step is not executed automatically. You receive a message in the change step overview, from where you execute the step manually.
• Conflicts with error character: The change step is not executed. You receive a message in the change step overview, from where you execute the step manually after you have remedied the cause of the conflict.

The status Manual adjustment necessary and the business transactions Delete automatically and Change automatically are used to control the system behavior during configuration changes.

• Status management (set deletion flag) negative
• Commitments/balance not balanced
• Subnetwork exists
• Business transaction Delete automatically forbidden at header or activity level.

• Activity/element with the same activity number already exists
• Business transaction Change automatically forbidden at header or activity level.
• Activity has status Technically completed or Completed

• Superior activity has status Technically completed or Completed
• Business transaction Change automatically forbidden at header or activity level.