Entering content frameFunction documentation Versioning of Info Objects Locate the document in its SAP Library structure

Use

Different versions are created when info objects are maintained in the Knowledge Warehouse:

Note

Structures have no language versions.

All versions of an info object refer to the same topic, in the case of online documentation to a particular aspect of the R/3 System and its use (e.g. a certain function, procedure, etc.).

The Knowledge Warehouse distinguishes between a logical info object and the associated physical info objects:

The logical info object (LOIO) represents all info objects that have the same topic. However, it does not have any attributes such as language, format, file size, etc.

The physical info objects (PHIO) belonging to a logical info object are the info objects that represent the contents, language and format versions of the topic.

The following graphic shows the relationship between logical and physical info objects in the Knowledge Warehouse:

This graphic is explained in the accompanying text

Integration

The Structure link context settings determine the version chosen in the Knowledge Warehouse.

All the contents except for those of the SAP standard are maintained in enhancement contexts: Maintaining Enhancement Contents. Enhancement contexts are created with the IMG activity Knowledge Management ® Settings in the Knowledge Warehouse system ® Development of info objects ® Contexts for version maintenance ® Enhancement contexts.

Activities

Every time an information object that has been edited is checked in (again), a new version, i.e. a new physical information object is automatically created in the Knowledge Warehouse. A new (HTML) display format version is created at check-in as well as the new contents or language version.

Note

No new version is created when an information object that was checked out but not changed or saved is checked back in.

During online processing with the SAPgui frontend, the versions (content or language version and format version) are created each time they are saved.

To create a version for a new release, you must check the information object out in the new release context and save it. When you check it back in, the new release version is stored in the Knowledge Warehouse.

During online processing, you have to edit and save the information object in the new release context. The new release version is stored in the Knowledge Warehouse after it has been saved.

Note

Once you have created a version for a new release, the changes that you make in the previous release do not affect the versions created in the new release.

You must maintain the changes in both releases if they are to take effect in both releases.

Recommendation

Maintain your information objects in the previous release if they are to be used in the next release as well.

See also: Versioning of Enhancements

Leaving content frame