Page tree
Skip to end of metadata
Go to start of metadata

After the technical upgrade from BW 3.x to BI 7.0, the client now wants to convert the objects that were created in the 3.x version to BI 7.0 version. Follow these steps to successfully migrate the 3.x objects (update rules, transfer rules, infosources, and datasources) to BI 7.0 objects (transformations, and DTPs)

    When we talk about migrating objects, it is always about the converting the rules, datasources and infosources. The info objects, info cubes, DOSs, Infosets and MPs are BI 7.0 compliant already.

    SAP has provided a Migration tool for this purpose which automatically does the job with little or no manual effort. During conversion most of the routines and formulas in the update rules and transfer rules automatically gets converted. The Migration tool cannot migrate scenarios of unlimited complexity. Therefore, the transformations created during the migration may be incomplete or incorrect in rare cases.

   A typical scenario is where the data is loaded from the source system in to a staging DSO(via a PSA or not) through an infosource and then from there is it further update in to one or more data targets (may be a second level DSO or a cube(s)). A migration of such a data flow would require the following actions...

1. Create a new infosource by copying the existing 3.x infosource.

2.  We start by converting the transfer rules into transformations. Choose "Create Transformation" from the context menu of the transfer rules. This results in a pop up message with two options, "Copy a 3.x infosource to new infosource" or "Use available infosource".

3. Select "Use available infosource" and select the new 7.0 infosource created in step 1.

4. An inactive transformation will be created based on the transfer rules. At this time you would know if the transformation requires a manual effort or not.A note 1052648 eloborates on different errors that can occur during the migration with a viable course of action for each case. Make necessary changes and activate the transformation.

5. From the context menu of the update rules choose "Create transformation".

6. Activate the inactive transformation.

At this stage you have the 7.0 infosource with transformations from the datasource and transformations to the data target. The data source is still in 3.x version. You would see that the update rules and transfer rules are still existing in parallel to the transformations.

7. Right click on the 3.x data source and choose "Migrate". In the next pop up screen choose With or Without export. The choice you make here will determine if you can bring back your 3.x datasource if needed. The "With Export" option will make it possible to revert back the migration process(using t-code RSDS) of the data source. Once the datasource is migrated to 7.0, the transfer rules are wiped out, using the "With Export" option the transfer rules can also be restored. When the datasource is migrated the Infopackage is automatically converted(you can see extra tabs in the infopack maintenance screen). And the "Only PSA" is selected automatically in the Update tab, since in 7.0 the infopacks load only to PSA.

8. The migration process will be complete with the creation of the DTP to load the data from the PSa to the data target.

If you have a second layer of data target and you have to convert that flow as well...

1. Convert the update rules between the first layer data target and the second layer data target to transformations using the above steps.

2. Create a DTP based on the transformations created above.

3. The DTP, by default, is a delta DTP. So when you execute the DTP for the first time it pulls everything from the first layer data target and that doubles up the records in the second layer data target. To avoid this, in the Execute tab of the DTP, change the Processing Mode to "No Data Transfer; Delta Status in Source: Fetched" and execute the DTP. You will see a request with 0 records loaded in the target with the status "delta status set in the source". This will set the delta pointer and the subsequent executions of the DTP will load the new records. If your first layer is a DSO, then choose the "Change Log" in the Delta Init Extraction From.. in the Extraction tab.

To guide you through the road blocks you can refer to Note 1052648.

Hope this is helpful...


  1. Very helpful piece of information, specially the DTP request in 3rd steps.

  2. Best approach technique in migration

  3. Former Member


    How do we approach 3.x to 7.x conversion of the dataflow for an export datasource (DS starting with 8*)?

    I could convert the transformation but getting error message for the datasource (with or without export option). Any clues?