Release Transfer 

Use

Using the release transfer function, you can transfer design objects within an Integration Repository to other software component versions as follows:

·        From a current software component version to the subsequent version, once development in the current version is finished

·        From a software component version to an older version of the same software component, for example to make a correction available in an older version.

·        From a software component version to a version of another software component. For example, this may be necessary because you may want to stop objects of software components that are based on each other from being available in the sub-software component, and only make them available in the superior software component.

Features

In the release transfer you can transfer the following object sets:

·        All objects of a software component version

·        All objects of a particular namespace of a software component version

·        Individual objects of a software component version, see also: Selecting Individual Objects.

Version Conflicts

As a rule, you transfer all objects of a software component version or a namespace once. Development then continues in the new software component version. You can transfer individual objects to the new version at a later stage if corrections need to be made in the old version that must then be transferred to the new version. If one of these objects has already been changed in the new version, then the release transfer reports a version conflict. You can then display a list of those objects that caused the conflict and exclude them from the transfer process as required.

To conclude, a version conflict only occurs during the release transfer if an object has been changed in both software component versions. If an object has only been changed in one of the software component versions, then the release transfer function takes the object from the most recent version.

Preview

The preview is displayed before the release transfer is executed and shows whether each object will be transferred. Note the following cases:

Case	Explanation
Transfer	The object is transferred because it has been changed in the source software component version but not in the target software component version.
No transfer	The object is not transferred because it is identical in the source and target software component versions or because it has not been changed in the source software component version.
Conflict	The object causes a conflict because it has been changed in the source and target software component versions.

You can deactivate the preview by selecting the Skip Previewcheckbox.

Activities

Perform the following preparatory steps before executing the release transfer:

...

       1.      The new software component version that you want to transfer the objects to must be entered in the System Landscape Directory (SLD). SAP software component versions are imported from PPMS. A customer can create his own software component versions in the System Landscape Directory.

       2.      Import the new software component version into the Integration Repository (see: Importing Software Component Versions).

       3.      To be able to transfer objects to the imported software component version, you must first assign namespaces to it. The namespaces must have the same names as those namespaces from which you want to transfer the objects.

To actually transfer the repository objects, proceed as follows:

...

...

       1.      Choose Tools ® Release Transfer... on the design maintenance screen of the Integration Builder.

       2.      Follow the wizard’s instructions.