Version Conflict
Use
When you edit and save an object that has already been activated, the system creates a new object version. This version is closed when you activate again (see Object History). The Integration 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.
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:
● Several active versions of the same object are identified when objects are imported (Integration Repository) (see Conflicts when Importing Objects).
● An object is changed in the original software component version and in the follow-up version during the release transfer (Integration Repository).
See also: