Data Flow Migratioin From 3.5 to 7.1-33

Data Flow Migration from BW 3.5 to BI 7.X

Applies to:SAP NetWeaver Business Warehouse (Formerly BI). For more information, visit the EDW homepage.

SummaryThis article tells about the details of the objects which are used for Data Transfer from Source System ECC to Target System BW 3.5/BI 7.X.

Author:

Surendra Kumar Reddy Koduru

Company: ITC Infotech India Ltd. (Bangalore/INDIA) Created on: 20 June 2011

Author BioSurendra Kumar Reddy Koduru is a SAP BI/BO Lead Consultant currently working with ITC Infotech India Ltd (Bangalore/INDIA). He has got rich experience and worked on various BW/BI Implementation/Support Projects and he is the author for various Articles and Blogs (SAP-BW/BI) in SAP Community Network.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1


Table of ContentsIntroduction: ........................................................................................................................................................ 3 DataSource: ........................................................................................................................................................ 3 InfoSource:.......................................................................................................................................................... 3 Transfer Structure: .............................................................................................................................................. 4 Transfer Rules: ................................................................................................................................................... 4 Update Rules: ..................................................................................................................................................... 5 Transformations: ................................................................................................................................................. 5 Emulation, Migration, and Restoring DataSources: ........................................................................................... 6 Emulation: ........................................................................................................................................................... 6 Migration: ............................................................................................................................................................ 6 Restoring:............................................................................................................................................................ 6 Live Scenario: ................................................................................................................................................. 7Step # 1:....................................................................................................................................................................... 7 Step # 2:....................................................................................................................................................................... 8 Step # 3:..................................................................................................................................................................... 12 Step # 4:..................................................................................................................................................................... 14 Step # 5:..................................................................................................................................................................... 16 Step # 6:..................................................................................................................................................................... 16 Step # 7:..................................................................................................................................................................... 17 Step # 8:..................................................................................................................................................................... 18 Step # 9:..................................................................................................................................................................... 19 Step # 10:................................................................................................................................................................... 19 Step # 11:................................................................................................................................................................... 23 Step # 12:................................................................................................................................................................... 29 Step # 13:................................................................................................................................................................... 30

Related Content ................................................................................................................................................ 32 Disclaimer and Liability Notice .......................................................................................................................... 33




Introduction:After reading this article, you will know, what are all the objects which are used for data transfer from Source System ECC to Target System SAP BW/BI. In coming articles we will migrate the data flow from SAP BW 3.5. To SAP BI 7.X.

DataSource:A DataSource is a set of fields that provide the data for a business unit for data transfer into BI. From a technical viewpoint, the DataSource is a set of logically-related fields that are provided to transfer data into BI in a flat structure (the extraction structure), or in multiple flat structures (for hierarchies). There are four types of DataSource: DataSource for transaction data DataSource for master data DataSource for attributes DataSource for texts DataSource for hierarchies

Use: DataSources supply the metadata description of source data. They are used to extract data from a source system and to transfer the data to the BI system. They are also used for direct access to the source data from the BI system.

InfoSource:InfoSources specify the set of all data available for a business transaction or a type of business transaction (for example, cost center accounting). InfoSources are sets of logically-related information, summarized into a single unit. They serve to stage consolidated data that can be updated into additional InfoProviders. InfoSources can contain either transaction data or master data (attributes, texts, and hierarchies). Use: In the BI system, a DataSource is assigned to an InfoSource. If fields that logically belong together exist in different source systems, they can be grouped together in a single InfoSource in the BI system by assigning multiple DataSources to one InfoSource. In transfer rule maintenance, individual DataSource fields are assigned to the corresponding InfoObject of the InfoSource. Here you can also specify how the data of a DataSource is transferred to the InfoSource. The uploaded data is transformed using transfer rules. An extensive library of transformation functions that contain business logic can be used here to clean up data and allow it to be analyzed. The rules can be applied simply, without coding, by using formulas.




See the following screen, it will show how it will connect DataSource and Data InfoProviders.

Transfer Structure:The transfer structure is the structure in which the data is transported from the source system into BI. It is a selection of DataSource fields from a source system. Use: The transfer structure provides BI with all the source system information available for a business process. An InfoSource 3.x in BI needs at least a DataSource 3.x for data extraction. In an SAP source system, DataSource data that logically belongs together is staged in a flat structure, the extraction structure. In the source system, you are able to filter and enhance the extraction structure in order to determine the DataSource fields.

Transfer Rules:This is the place where we will map the ECC/Source System Fields and BW/BI InfoObjects. Use: When you have maintained the transfer structure and the communication structure, you use the transfer rules to determine how you want the transfer structure fields to be assigned to the communication structure InfoObjects. You can arrange for a 1:1 assignment. You can also fill InfoObjects using routines, formulas, or constants.




Update Rules:Update rules specify how data (key figures, time characteristics, characteristics) is updated into the InfoProvider from the communication structure of an InfoSource. You are therefore connecting an InfoSource with an InfoProvider. To select jobs to display and manage, refine your job selection by filling out each tab as required. Only jobs that meet all of your specification will be selected.

Transformations:Transfer Rules/Update Rules in BW 3.X are replaced with Transformations in BI 7.X. Use: The transformation process allows you to consolidate, cleanse, and integrate data. You can semantically synchronize data from heterogeneous sources. When you load data from one BI object into a further BI object, the data is passed through a transformation. A transformation converts the fields of the source into the format of the target. See the following figure, which will show the Data Flow using Transformation.




Emulation, Migration, and Restoring DataSources: Emulation:3.x DataSources (object type R3TR ISFS) exist in the BI database in the metadata tables that were available in releases prior to SAP NetWeaver 7.0. The emulation permits you to display and use the DataSource 3.x using the interfaces of the new DataSource concept. The DataSource (R3TR RSDS) is instantiated from the metadata tables of the DataSource 3.x.

Migration:You can migrate a 3.x DataSource that transfers data into BI from an SAP source system or a file or uses DB Connect to transfer data into a DataSource. 3.x XML DataSources and 3.x DataSources that use UD Connect to transfer data cannot be migrated directly. However, you can use the 3.x versions as a copy template for a Web service or UD Connect DataSource.

Restoring:You can restore a DataSource 3.x from the DataSource (R3TR RSDS) for SAP source systems, files, and DB Connect. The 3.x metadata objects must also be exported and archived with the migration of the DataSource 3.x into the original system for files and DB Connect. The system reproduces the 3.x DataSource (R3TR ISFS), mapping (R3TR ISMP), and transfer structure (R3TR ISTS) objects with their premigration status.




Live Scenario: In this example we are going to Migrate the BW 3.5 flow using DataSource 0CO_OM_CCA_9. Actually it is in BW 3.5 flow, but we will change it to BI 7.X flow. Follow the Steps Step # 1: Flow Diagram

In above diagram, we can see the BW 3.5 Data Flow i.e. from DataSource to InfoCube. The thump rule is, you can see the small Square on each Object in the above flow.




Step # 2: Creating Transformations for Old Transfer Rules. Now we will create the Transformations for the existing Transfer Rules, see the below diagram.

Right click on the old Transfer Rules and then choose Additional Functions and Create Transformation.

Then it will ask InfoSource Name, so you select Copy InfoSource 3.X to New InfoSource option and continue. If you select the above option then the new InfoSource will be created based on the Old InfoSource.




Give InfoSource Name, just adds Z in place of 0 for exiting SAP InfoSource.




See the below screen.

The InfoSource name is Z. Just add Z and give old InfoSource Technical Name.




Once you give the InfoSource name and Continue then it will copy all the mappings in between DataSource and InfoSource. See the above screen. If any problems then we need to see the error message and then correct the error and continue.




Step # 3:

Select our datasource and then Right Click on DataSource and choose Migrate.

Select With Export option, because, once you migrate the DataSource into BI 7.X flow and again you want to turn the DataSource into BW 3.5, this option is useful.




For further more information click on Info Button, you can see the below message.

Migration of a DataSource 3.x When a DataSource 3.x (R3TR ISFS) is migrated, it is deleted and transferred to the DataSource (R3TR RSDS). The dependent 3.x objects mapping (R3TR ISMP) and transfer structure (R3TR ISTS) are deleted. If they exist, (R3TR ISIP) and the PSA with requests that have already been loaded are transferred into the DataSource. The 3.x objects can also be exported as part of the migration process. This means it is possible to recover the metadata objects DataSource 3.x, the mapping and the transfer structure. Recovery of a DataSource 3.x It is only possible to recover a DataSource 3.x if it was migrated with export. This allows the objects DataSource 3.x (R3TR ISFS), mapping (R3TR ISMP), and transfer structure (R3TR ISTS) to recover the same status as they had before the migration. During the recovery the DataSource (R3TR RSDS) is deleted. The system tries to retain the PSA. This is, however, not possible if the PSA was initially generated for the DataSource because either there was no active transfer structure for DataSource 3.x or it was loaded using IDoc. The dependent objects transformation (R3TR TRFN), Data transfer process (R3TR DTPA), and InfoPackage (R3TR ISIP) are retained. If you want to delete them, you must do this manually.

So it is migrated, once again you Activate the complete flow and then load the Data. First execute the InfoPackage, it will load the data from Source to PSA then execute the DTP, it will load the data from PSA to InfoCube.




Step # 4: (Migration of Update 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.

Right click on Update rules and then navigate as per above screen and create Transformations.




It will ask InfoSource Name, so choose Use Available InfoSource and give the InfoSource we generated at the time of migrating Transfer Rules. (See above screens.)

We got errors, so see the error message and then correct it. This we will do at the time of Transformations activation, i.e. Transformations in between InfoSource and InfoCube. The reason for this error is, in BI 7.X the routines contains Source and Target Fields, so that we need to adjust.




Step # 5: See the BI 7.X Flow, but it is not Active.

Step # 6: In below screen, we can see the actual Routines in BW 3.5 flow Transfer rules.




Step # 7: If you see the above Transfer rules you can find some Routines in BW 3.5. version, now you can see the same routines in BI 7.X version.

See the routines and then activate the Transformations. Once you activate it then it will turn to Green, see the below screen.




In the same way Activate the Transformations between InfoSource and InfoCube, see the below screen. Here we are going to correct the above Errors (Previously we got some error at the time of Update Rules Migration). Step # 8: Go to change mode for Transformations, see below




Step # 9: Open the Start Routine

Step # 10: Check Syntax.

You can find some Syntax error message on the bottom of the code window. See the below screen.




See the existing code in the above screen and the same Im going to change in the next screen, see below.




I commented the old code and I written new code, you can see it in the above screen. And then check Syntax, it wont show any error and it is correct.




See the message in the above screen.




Step # 11: Then Save it and come back to original screen and then check the Syntax, again it will show some error.Note: This kind of errors are depends on Routines in your Transfer/Update Rules, in my case I have some routines in both places, so Im getting the errors, in your case it may differ.

See the error message in the below screen.




There is some problem in Target InfoObject Routine.

Then open the routine in Change Mode and correct it.

Once you open the Code window then Check Syntax.




There is some problem.




Corretc the code, it is just Source and Target Fields problem only.




Once you correct the code the save it and then click on Transfer Values, then only the changes will applicable.

Once again click on Syntax check and, it wont have any problem now, the same you can see in the Status bar, see below screen.







Step # 12: Activate the Transformations

Now you can see the Active Transformations in between DataSource and InfoSource and InfoSource and InfoCube.

In above screen you can differentiate the old and new flow.




Step # 13: Creating DTP




With this part we are migrated all obejcts which are there on the Top of the DataSource. In the next step we will migrate the DataSource also.




Related ContentAll Articles and Blogs For all Articles and Blogs by Surendra Kumar Reddy, Please visit this URL Using Customer Exit Variables in BW Reports Part - 5 Using Customer Exit Variables in BW Reports Part - 6 Using Customer Exit Variables in BW Reports: Part - 8 Using Customer Exit Variables in BW Reports: Part - 9 Using Customer Exit Variables in BW Reports: Part - 10 Using Customer Exit Variables in BW Reports: Part - 11 Using Customer Exit Variables in BW Reports: Part - 12 Using Customer Exit Variables in BW Reports: Part - 13 Using Customer Exit Variables in BW Reports: Part - 14 Using Customer Exit Variables in BW Reports: Part - 15 Using Customer Exit Variables in BW Reports: Part - 16 Using Customer Exit Variables in BW Reports: Part - 17 Using Customer Exit Variables in BW Reports: Part - 18 Checking the Data using Extractor Checker (RSA3) in ECC Delta Repeat Delta etc... Data Flow from LBWQ/SMQ1 to RSA7 in ECC and Delta Extraction in BI Open Hub Destination: Part 1 Open Hub Destination: Part 2 Analysis Process Designer (APD): Part - 1 Analysis Process Designer (APD): Part - 2 Analysis Process Designer (APD): Part - 3 Using Customer Exit Variables in BW Reports Part - 3 How to use Customer Exit Variables in BW Reports: Part - 2 Using Customer Exit Variables in BW or BI Reports Part - 1 Using Text Variables with Customer Exits in Report Headings For more information, visit the EDW homepage




Disclaimer and Liability NoticeThis document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.



Documents

Data Flow Migratioin From 3.5 to 7.1-33