Вы находитесь на странице: 1из 5

How to migrate BI 3.x to BI 7.

0 in ETL
Cause: As we all know, the design and implement of ETL between BI 3.x and BI 7.0 is different. In BI 3.x, InfoSource is mandatory for ETL and transfer rule and update rule are used to populate data from Source (Data Source, DSO ,InfoSource or Cube) to Data Target (DSO, InfoSource or Cube). But in BI 7.0, the InfoSource is option and transformation combine both functions in transfer rule and update rule, meanwhile it provide better graphic interface. What is worse is that BI 7.0 does not provide sufficient BI Content corresponding to the BI Content in BI 3.5. Thus if we still want use many useful BI Content, we have to firstly install the BI Content in 3.x and then migrate whole ETL from BI 3.x to BI 7.0. This causes why we so need the method to migrate BI 3.x to BI 7.0 currently.

Figure 1 ETL in BI 3.x

Figure 2 ETL in BI 7.0

Scenario: Currently we have installed the Cube (0PABN_C01) from BI Content in 3.x, we want to migrate this ETL to BI 7.0. In update rule, some key figures and characteristics are calculated by routine and some characteristics are updated through reading the attribute of Info Object. We have a complex problem to solve. Method: First option: One transfer rule -> One transformation One update rule -> One transformation One data package -> One DTP and One infopackage In first option, the Info Source will be still required. Second option: One transfer rule and one update rule -> One transformation One data package -> One DTP and One infopackage

Second option is also based on first option. When you have finished the first option, then you should combine these two transformations into one transformation. Implement: Because first option is more basic, more deep focus will be paid on it. First option: 1. Migrate the transfer rule into one transformation. Right click on the transfer rule, and then choose Additional Function -> Create Transformation

2. Copy InfoSource 3.x to New InfoSource

The new InfoSource name should be Z + original InfoSource Name 3. Check and activate InfoSource and Transformation

You can see the objects, either InforSource or Transformation, have no small white square before the object name. 4. Modify the update rule If the key figures or characteristics are updated by routine, you should do nothing and let migration program do whole change for you. And ABAP program is totally different between BI 3.x and BI 7.0. BI 3.x treats the routine as a program or module function, BI 7.0 treats the routine as an object and its methods. If there exist characteristics reading from attribute of InfoObject, you should modify them with Initial Value. Otherwise you will have dump screen when you migrate the update to one transformation. And you should carefully take notes about these characteristics and their corresponding reference InfoObjects. However, you will lose the mapping logic.

5. Migrate update rule to into one transformation

Right click on the update rule, and then choose Additional Function -> Create Transformation

6. Update the transformation, modify the Initial value characteristics by assigning the reading Master Data 7. Check and Activate the transformation 8. Migrate the 3.x DataSource to new DataSource Right click the DataSource and press Migrate

9. Create the Info Package for new DataSource and extract data 10. Create the DTP and extract data form DataSource 11. Check the cube data

Second option: Copy and paste the routine from one to another.

Вам также может понравиться