Show TOC

Creating and Editing Migration ProjectsLocate this document in the navigation structure

Procedure

  1. In the object tree under Modeling in the Data Warehousing Workbench (transaction RSA1), select one of the following source objects for migration of a 3.x data flow:

    • 3.x DataSource

    • InfoSource 3.x (flexible update)

    • InfoSource 3.x (direct update) that active transfer rules exist for

    • DataStore Object

    • InfoCube

    To ensure consistent migration, we recommend using the 3.x InfoSource as a source object.

  2. In the context menu for the object, choose Migrate Data Flow.

  3. A dialog appears where you can assign a name to the migration project.

    Note

    If the object is already contained in a another migration project, the name of this project is displayed. Using the input help for the Migration Project field, you can display a list of migration projects that contain the object. Overwrite the existing project name if necessary.

  4. Choose Create.

    The migration project maintenance screen opens. The system displays a tree containing the objects of the data flow for the starting object and for any relevant process chains. The tree display is the same as the object tree display in the Data Warehousing Workbench.

    Note

    Alternatively you can use the transaction RSMIGRATE to access the migration project screen. In this case, you can select the starting object for the migration project using Add Data Flow (after you have specified a name for the project and switched to the project editing screen).

  5. Use the Object Selection column to select the objects that you want to include in the migration project.

    The system recognizes the dependencies between objects and includes them in the selection (dependent objects are automatically selected). For example, a transfer rule requires the 3.x InfoSource. When you select a transfer rule, the 3.x InfoSource is automatically selected as well.

    Note

    • The selected objects are locked and can only by migrated in this project. These objects cannot be selected in other migration projects. An exception displays the 3.x InfoSource; it can still be selected in other projects (despite already being selected) because it can be copied to different, independent InfoSources of type R3TR TRCS.

    • We recommend creating the migration project in such a way that all migration-relevant processes in the participating process chains are migrated in a single project. This means that multiple data flows might be migrated together in a single migration project. By pressing Add Data Flow, you can add further data flows to the migration project with the associated process chains.

  6. Save the migration project.

Functions for Editing the Project

The following functions are available for editing the project:

Pushbutton

Description

Expand Subtree

Displays the lower-level objects of the selected data flow object.

The system only reads the information for a process chain after you expand the Associated Process Chains tree.

Compress Subtree

Hides the lower-level objects for the selected object.

Find

Searches for an object in the selected data flows.

Find Next

Displays the next search hit if multiple hits were found.

Refresh Entire Tree

Refreshes the display of data flows and process chains.

Select All

-

Remove All Selections

-

Add Data Flow

Adds additional data flows with associated process chains to the migration project. To do this, select the starting object by specifying the object type and object name in the dialog box.

Remove Data Flow

Removes a data flow and the associated process chain for a selected starting project from the migration project.

The Refresh Status and Tree function on the toolbar in the migration project maintenance screen refreshes the data flows, process chains and the status of the migration project.

More information

Read Notes on Handling Special Objects During Migration.