Editing Version Conflicts

When you edit and save an object that has already been activated, the system creates a new object version. This version is completed the next time you activate. The Enterprise Services Repository can only contain one active version of an object. This requirement is met if object versions follow each other continuously. A version conflict occurs if this continuity is interrupted.

More information: Object History

A version conflict occurs if the new version is not a successor to the version that was previously active, but has been generated on the basis of an older version that is no longer active.

The following situations can trigger a version conflict:

• Multiple versions of an object collide when you import it

  More information: Conflicts when Importing Objects

• An object is modified in the original software component version and in the follow-up version during the release transfer.

  More information: Transferring Design Objects

Use the conflict editor to process version conflicts.

More information: Conflict Editor