Version Management

You need version management if you want to adjust objects that are not supported by the Modification Assistant. Place your cursor on the object concerned and choose Version management.

You can use the version management function for Repository objects when making modification adjustments.

SPDD and SPAU need three versions for an adjustment:

  1. Version of the new release (active version)
  2. Version that existed before the object was modified by the customer
  3. Version that existed after the object was modified by the customer

For Which Objects Can Versions Be Created?

Report RSVCDI00 provides an overview of the objects for which versions can be created.

Creating Versions

The aim of version management is to keep track of all changes made to a Repository object. Therefore, the system automatically creates versions:

  • Before a Repository object is modified

Each object modified is added to a change request. If the newest version in version management is not identical with the active version, the system saves the object status that existed before the change was made in version management. Such backup copies are identifed by an S or I in the version overview.

  • When a change request is released

When you release the change request containing the objects modified, the system creates versions. The request number is displayed in the version overview together with the respective version.

To avoid impacts on runtime, no versions are created when objects are imported. In fact, this is not necessary because the change history of the object was completely recorded in the development system. The system nevertheless creates a note in the version overview when an object has changed as a result of an import.

If required, you can also create versions when importing objects. This makes sense, for example, if the development system is reinstalled at regular intervals and the versions recorded there are consequently lost.

As a prerequisite, you must set the profile parameter VERS_AT_IMP to ALWAYS in the Transport Management System (the default value is NEVER ).

The system then additionally creates versions:

  • Before the import

If the newest version in the version database is not identical with the active version, the system creates a backup copy immediately before the import. These versions are identified by an S in the version overview.

  • After the import

After the import, the system creates a version of every object imported. The number of the request imported is displayed in the version overview together with the version created. If an object is contained in several requests which are imported simultaneously (using tp import all , for example), the system creates only one version of this object after the last request has been imported.

In a production system, these versions then tell you exactly which status of an object was active at a particular time.

You can also set up your SAP System to create versions not for all imports but only for imports of objects which are relocated without being reassigned to a new package (or development class, which is the old term for a package). To do this, set the profile parameter VERS_AT_IMP to C_ONLY .

Besides the versions created automatically, you can create temporary versions at any time. To do this, you use the Create Version function in the maintenance transactions of the Repository objects. These temporary versions also help you to restore the previous status of an object during development. When you release the respective request, the temporary versions are deleted and replaced with the versions that are active at the time of the release.

Also read the following sections:

Displaying and Using Versions

Functions in the Version Overview

Practical Examples of Version Management