Show TOC Entering content frame

Object documentation Collision Locate the document in its SAP Library structure

Definition

A conflict occurs between an open version and the baseline version or two open versions of a development object when a change list is released.

Structure

Different types of collisions and the scenarios in which these collisions occur are listed in the table below.

Collision type

Scenario

Predecessor Successor Collision

User A has created an object in the mobile application repository (MAR1) and transported it to MAR2. User B has modified this object (successor) on a side branch in MAR2. As a result of this, the baseline shifts to the side branch in MAR2.

Simultaneously, user A has been modifying the same object (predecessor) on the main branch in MAR1. The baseline stays in the same main branch, however, shifts to the new version.

When user B releases the modified object in MAR2, it gets transported into MAR1, and the predecessor successor collision occurs. For more information, see Predecessor Successor Collision.

Translation Collision

User A has transported a text object from MAR1 to MAR2. After the transport, user A has created a translation object for the text object in English in MAR1.

Simultaneously, user B has also created a translation object for the imported text object in English in MAR2.

When user B release the object in MAR2, it gets transported into MAR1, and the translation collision occurs. For more information, see Translation Collision.

Imported Deleted Notification Collision

User A has created an object in MAR1 and transported it to MAR2. User B has been modifying the imported object in MAR2.

At the same time, user A has deleted the object and transported the deleted version to MAR2. As a result of this operation, the imported deleted notification collision occurs. For more information, see Imported Deleted Notification Collision

Note

This collision occurs only if the user B is modifying the object in MAR2. Otherwise, the object will be deleted automatically in MAR2.

Ownership Transfer Collision

User A has created an object in MAR1 and transported it to MAR2. In this scenario, the object is owned in MAR1.

Since the object is not owned in MAR2, user B has modified the object on a side branch and released it. As a result of this operation, baseline shifts to the side branch.

User A has transferred the ownership of the object from MAR1 to MAR2. As a result of this, the ownership transfer collision occurs. For more information, see Ownership Transfer Collision.

Note

This collision occurs if user A transfers the ownership only after user B starts modifying the object in MAR2. Otherwise, ownership of the object will be transferred without the collision.

See also:

 

Resolving Collisions

 

Leaving content frame