Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

version management

Former Member
0 Kudos

Pls give me the use of version management.


Former Member
0 Kudos

Version management serves different purposes and user groups:

1.The developer can keep track of his or her work ("What have I changed?")

2.The developer can restore a previous version by reactivating it.

3.The system administrator can monitor work ("Which objects were changed and how in a specific time interval?")

4.It provides a basis for any auditor who requires a complete history of changes.

5.It enables customers to use the system to adjust data after they have upgraded to a new release.

You can access version management from the following:

Object Navigator (SE80)

Transport Organizer (SE09)

Display and maintenance transactions for Repository objects.

0 Kudos

hello ,

some more on this .

whenever we do a change suppose d0123 is request number for this change .

using version management , you can see the status of this change ie. when it has been done , bu whom the change is done , date , time etc .

now suppose to the same program , you have done a new change and the d0124 is the request number for this .

now someone wants to view what changes you have done as compared to the previous request change . then we use version management to compare the two changes .

thanks .

    • reward if useful

Former Member
0 Kudos



Version management in the Integration Repository permits versioning as follows:

· The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.

· Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.

Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.

However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.


You can also export objects of an Integration Repository or an Integration Directory to import them into another repository or directory (for example, during system relocation). In doing so, versioning of the corresponding software component version is taken into account.

See also: Transporting XI Objects.


Change Lists

The Integration Builder supports object versioning for both the repository and for the directory using the user-specific change lists. When an object is saved for the first time, a new object version is created, which is added to the change list. When an object in the change list is activated, the object version is closed and is made visible for other users.