Migration of Update Rules, 3.x InfoSources, and Transfer Rules 

Use

You can create a transformation using update rules or transfer rules. In doing so, the corresponding 3.x InfoSource is converted into a (new) InfoSource. This allows you to migrate existing objects to the new transformation concept after you upgrade.

When you create the transformation and the (new) InfoSource, the system retains the update rules, 3.x InfoSources, and transfer rules. To ensure that the loading process is performed using the transformation and not the update rules or transfer rules, data has to be loaded using a data transfer process.

Procedure

1. Data Flow Between Two InfoProviders: Creating Transformations Using Update Rules

...

       1.      You are in the Modeling functional area of the Data Warehousing Workbench. In the context menu of the update rule you want to convert, choose Additional Functions → Create Transformation. No export DataSource is now needed for the data flow between two InfoProviders (Myself Data Mart). The transformation for which you create another data transfer process is sufficient.

2. Data Flow Between DataSource and InfoProvider: Creating Transformations Using Update Rules

...

...

       1.      You are in the Modeling functional area of the Data Warehousing Workbench. In the context menu of the update rule you want to convert, choose Additional Functions → Create Transformation.

       2.      You can choose whether you want to create a new InfoSource or use an existing one.

       3.      Choose  Okay. The system generates a log for the conversion. The InfoSource is activated immediately; the transformation is saved without being activated. If you want to use routines in the rules, you might have to edit the transformation manually.

3. Creating Transformations from Transfer Rules

...

       1.      You are in the Modeling functional area of the Data Warehousing Workbench. In the context menu of the transfer rule you want to convert, choose Additional Functions →Create Transformation.

       2.      You can choose whether you want to create a new InfoSource or use an existing one. If you have already converted the update rules, a converted version of the related InfoSource already exists.

       3.      Choose  Okay. The system generates a log for the conversion. The transformation is saved without being activated. If you want to use routines in the rules, you might have to edit the transformation manually.

4. Editing Transformations

...

       1.      Routines are copied straight to the global part 2. Using a PERFORM, the routine for the converted rule is called from the routine for the transformation. Comments on the conversion are retained in the routines. You can use these comments to modify the routine to improve performance.

If you programmed the routine dynamically, you should check it by performing a before-after check. Since the fields of the source structure are removed during migration, errors that cannot be checked by the system could occur in the converted routine. If fields that are used in the routine are not filled, an error occurs.

More information: Differences in Routine Concepts

       2.      Return tables in routines cannot be converted. We recommend that you use an end routine instead.

       3.      Inversion routines in transfer rules are not converted. If the transfer rules contain inversion routines, you have to recreate these in the transformation.

The following example may be of use: Example for Migration of an Inversion Routine

       4.      Activate your transformation.

Result

You can create a data transfer process for the new objects.