Skip to Content

Collision occurs when there is a conflict between an open version and the baseline version or two open versions of a development object when a changelist is released. The following are some types of collisions and the scenarios in which they occur.

Predecessor Successor Collision
This collision occurs when SAP and customer enhance the same development object and customer tries to release his changelist after importing SAP’s changes. The following steps describe the scenario.
1. SAP creates a development object and transports it to the customer repository.
2. Based on customer specific requirements, a technical consultant enhances the original version of the development object. This is done in a side branch since SAP owns the development object.
3. SAP also enhances the original version of the development object and transports it to the customer repository.
4. When customer changes are released, Mobile Application Studio reports a collision between the version transported by SAP and customer’s own enhanced version.

Translation Collision
This collision occurs when SAP and customer translate the same development object separately. The following steps describe the scenario.
1. SAP creates a development object and transports it to the customer repository.
2. Customer does a translation into German.
3. SAP also does a translation of the same development object into German.
4. When the customer receives the new development object, Mobile Application Studio reports a collision.

Imported Deleted Notification Collision
This collision occurs when SAP deletes an development object which has been modified by the customer. The following steps describe the scenario.
1. SAP creates a development object and transports it to the customer repository.
2. Based on customer specific requirements, a technical consultant enhances the original version of the development object. This is done in a side branch since SAP owns the development object.
3. SAP deletes the original development object by placing it in a changelist for deletion.
4. When SAP’s delete changelist is transported, a collision occurs because the development object has been modified by the customer and Mobile Application Studio displays a notification of deletion.

Ownership Transfer Collision
This collision occurs when customer enhances a development object and SAP tries to transfer ownership of the development object to customer repository. The following steps describe the scenario.
1. SAP creates a development object and transports it to the customer repository.
2. Based on customer specific requirements, a technical consultant enhances the original version of the development object. This is done in a side branch since SAP owns the development object.
3. SAP tries to transfer the ownership of the development object to the customer repository.
4. When customer changes are released, Mobile Application Studio reports a collision because the baseline version cannot reside on a side branch.

These are the different types of collisions and we will have a look at some of the collision resolution methods in future blogs.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply