Transferring Design Objects

Use

You can transfer design objects within one ES Repository to other software component versions. The following use cases exist:

Release Transfer

You want to transfer objects from one software component version to another, where both software component versions are registered in the System Landscape Directory. You can transfer the following objects:

Objects from a current software component version to the subsequent version, once development in the current version is finished
Objects 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.
Objects 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.

Transferring Objects of a Local Software Component Version

The objects of a local software component version are intended for projects that are not yet developing delivery-relevant ESR content. To deliver such objects, you must transfer the objects from the local software component version to a software component version that is registered in the System Landscape Directory.

The function for both cases is the same. The same applies for the following information about using the function.

Prerequisites

You can only transfer active objects to a different software component version.

Features

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. More information: Selecting Individual Objects .

Options in Step 'Select Objects' for Single-Object Selection

Set of Objects	Further Options (Where Applicable)	Explanation of Option
Single Objects The deleted objects have the Delete Version ( ) icon next to them in the selection list. More information: Single-Object Selection	Export a Folder With Content	If selected, the entire contents of the folder (including content from sub folders) are transferred. If not selected, only the folder definition is transferred.
Add Dependent Objects from Models	If selected, any additional objects from models that are dependent on the following object types are automatically transferred: Filter, Templates, and Attribute Groups.
With Authorizations	If selected, the folders and namespace definitions selected in the list are transferred as well as the authorizations assigned to these objects.

Set of Objects

Further Options (Where Applicable)

Explanation of Option

Single Objects

The deleted objects have the Delete Version ( ) icon next to them in the selection list.

More information: Single-Object Selection

Export a Folder With Content

If selected, the entire contents of the folder (including content from sub folders) are transferred. If not selected, only the folder definition is transferred.

Add Dependent Objects from Models

If selected, any additional objects from models that are dependent on the following object types are automatically transferred: Filter, Templates, and Attribute Groups.

With Authorizations

If selected, the folders and namespace definitions selected in the list are transferred as well as the authorizations assigned to these 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 ES Builder 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 transfer of objects 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 ES Builder takes the object from the most recent version.

Preview

The preview is displayed before the object 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:

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.
Import the new software component version into the ES Repository (see: Importing Software Component Versions ).
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 design objects, proceed as follows:

In the ES Builder, choose Tools → Transfer Design Objects.
Follow the wizard's instructions.