Entering content frame

This graphic is explained in the accompanying text Predecessor Successor Collision Locate the document in its SAP Library structure

Scenario

SAP creates an object and transports a version of the object to the Customer repository. Now, both the SAP and the Customer repositories have the same baseline version of the object.

 

This graphic is explained in the accompanying text

  1. SAP transports original version V1 to the Customer repository.
  2. In the Customer repository, the technical consultant enhances the original version V1 based on customer specific requirements. Since SAP owns the object, the changes for the open version V1a are made in a side branch.
  3.  

    This graphic is explained in the accompanying text

  4. SAP enhances the utility of the original version to V2.
  5. SAP transports V2 to the Customer repository.
  6. When the customer changes are released, the Mobile Application Studio reports a collision between versions V2 and V1a.

Analysis

In the Customer repository, changes are made to the original version in V1a, which is derived from the baseline version V1. Hence, V1 becomes the predecessor of V1a. At the same time the Customer repository imports an enhanced version from SAP and as a result the baseline shifts from V1 to V2. When V1a is released, a collision occurs because V1a is not a successor of V2.

See also:

Collisions

Leaving content frame