Practical Examples of Version Management (SAP Library - Changing the SAP Standard (BC))

Practical Examples of Version Management

The following sections describe the different statuses supported in version management to help you choose the correct version when comparing modified objects after an adjustment. During modification adjustment, version management is always used when Dictionary objects are adjusted, or when Repository objects must be adjusted manually in transaction SPAU.

Initial status

If an object is in its initial status, the system displays the following details in version management, for example:

This graphic is explained in the accompanying text

Initial status means that:

The object has not yet been modified in the system.
The object was imported from another system (the I flag in the Fla column is set only if at least one version exists in the version database).
The object could have been modified as a result of a patch or an upgrade.

After start of repair

The object (report RSVRSRS1 in this example) was added to task TDVK900219 of change request TDVK900218 (which is not displayed here). Version 1 (status before the change) was created.

This graphic is explained in the accompanying text

During modification

This graphic is explained in the accompanying text

Versions 2 and 3 were created as a result of a user request. These are temporary versions which are deleted when the request is released.

After release of the request

This graphic is explained in the accompanying text

The change request TDVK900218 was released. The system deleted the temporary versions and saved the status after the release as version 2. Version 2 is now identical with the active version. The date on which the object was last changed is displayed with the active version. The release date of the request which is, of course, later than the date of the last change is displayed with version 2.

After import and subsequent start of repair

This graphic is explained in the accompanying text

The object was imported with request TQAK900043, but no version was created. Afterwards, the object was added to task TDVK900221. Since the active version was modified as a result of the import and was therefore no longer identical with version 2, the system created version 3 when the object was added to task TDVK900221. Version 3 reflects the status after the import of request TQAK900043 which is therefore displayed with version 3.

After release of repair

This graphic is explained in the accompanying text

The change request TDVK900220 (which contains task TDVK900221) was released. The system created version 4.

Before the upgrade

This graphic is explained in the accompanying text

Status after the release of TDVK900220. Version 4 is identical with the active version.

Between determination of the objects to be adjusted (phase ADJUSTCHK) and SPDD/SPAU

This graphic is explained in the accompanying text

During this phase of an upgrade, the system creates versions of modified objects which are to be delivered again. All objects delivered again are marked with the I flag (request UPGRADE6.10). Since report RSVRSRS1 is imported during the upgrade, the I flag was set in the Fla column.

During SPDD/SPAU

This graphic is explained in the accompanying text

The user clicked the object RSVRSRS1 in SPAU. The system created version 5 (status after the Repository switch).

To make the necessary adjustment, you should compare version 4 (modified status before the upgrade) with version 5 (status after the upgrade) in a separate window. You should then edit the object itself (that is, its active version) in a second window.

After return to the SAP standard

Starting with Release 4.5, returning to the SAP standard means that the release-specific entry in the modification table (SMODILOG) is deleted (previously, a C flag was set instead).

Leaving content frame