Migration of Datasources

In SAP source system (ECC), the datasource is the relevant object that makes source data available in a flat structure for data transfer into BW.

In the source system, the datasource can have the SAP Delivery Version or Active Version.

There are two types of datasources in BI:

R/3 TR RSDS or 3.x DS R/3 TR ISFS

Since the datasource cannot exist in both of these versions simultaneously, you have to choose the form while replicating them to BW.

Replicated 3.x datasources can be used as Emulated datasources in BW for migration purposes.

SAP recommends migration of 3.x datasources if you are using RDA DTPs or Direct Data Access DTPs as emulated datasources does not support these two types of DTPs.

Note: You cannot migrate-

  1. Hierarchy datasources
  2. Datasources which use IDOC as data transfer method
  3. Export Datasources e.g. 8XXXXX, where 8 is the prefix to indicate export datsources. XXXXX is the name of the DSO
  4. Datasources which use BAPI interface

When you migrate a 3.x datasource, then its object type is R3 TR ISFS in the BW system.

During migration, the system generates a datasource of type R3TR RSDS with a transport connection.

The 3.x datasource is deleted along with the metadata object and the transfer structure because these are dependent on the datasource.

If PSA or Infopackage existed for the 3.x datasource, they are also transferred to the migrated datasource.

You can export the 3.x objects, 3.x datasources, mapping rules and transfer structure during migration.

There are two options available for migration:

  1. Migration with export: In this case, the migrated Datasource is stored in the table RSDSEXPORT. Hence, it is possible to rollback the datasource from BI 7.x to BI 3.x version.
  2. Migration without export: In this case, the datasource will be migrated without storing the datasource in the RSDSEXPORT table. Hence, the roll back of the datasource is not possible.

Note: When  you perform roll back, the Datasource entry in the table RSDSEXPORT will be deleted.

Other objects like infoobjects, infocubes, queries etc will be migrated automatically.

Sample Procedure:

Migration of Datasource (tcodes: RSDS, tables: RSDSEXPORT)

Make sure that the SAP BW 3.x objects are transported to SAP BW 7.0 (SAP BASIS job)

Aim: Transaction data loading from flat file to Infocube (SAP BW 3.x)

Tcodes: RSA1, RSA11, RSA12, RSA13, RSA14, RSD1, RSD5, RSDS, RSDCUBE, RSU1, RSMO, RSMON, LISTCUBE, SE11, SE16,…..

Part I: Data Modeling

Step 0: Make sure that the master data is maintained.

Step 1: Create flat file for the transaction data

SMID PQTY Unit Sales Profit Currency Date
S1 10 LB 3000 500 USD 20160301
S2 20 KG 4500 600 INR 20160302

Save the file in CSV format and close the file.

Step 2: Logon to BI

Step 3: Make sure that flat file source system ‘PC’ icon exist in BI tcode RSA1OLD-Source Systems.

mi1

Step 4: Create Infoobjects (RSD1, RSA14, RSD5)

Ex: SMID, PQTY, SALES, PROFIT

mi2

Step 5: Create application component and a flat file datasource

Step 6: Create InfoSource (tcode: RSA12)

Create application component and Infosource for transaction data.

mi3

Assign source system to your infosource-

mi4

Click continue.

Now create transfer structure by filling the infoobject column with your infoobjects. Select the selection check boxes if required.

mi6

Maintain update mode as ‘Full upload’. Apply the transfer rules. Maintain the transfer method as ‘PSA’ and activate the infosource.

Step 7: Select Datasource/Transfer structure tab. Select ‘Preview’ icon.

mi8

Select ‘Client Workstation’ CSV Data separator ‘,’. Give the file name. Header rows to be ignored as ‘1’. Continue.

Select the ‘Extras’ menu and select ‘Object Directory Entry’ as ‘Infosource’ and observe the object type.

mi9

Select ‘Continue’. Now select Object directory entry-Transfer Rules. Observe the object type – ‘R3TR ISTS …..’

Select ‘Continue’. Now select Object directory entry-Datasource. Observe the object type – ‘R3TR ISFS …..’

Press Enter.

Step 8: Create Infocube (tcode: RSA1) – Go to your infoarea in the infoproviders tab, and create cube. Use your infosource as a template.\

Rename dimension1 as ‘Salesman Dimension’. Activate the cube.

Step 9: Create Update rules for the infocube by selecting your infosource in the tcode RSA1OLD or RSU1.

mi10

Result: Data modeling is complete.

mi11

Step 10: Migrate your datasource.

Go to the tcode RSA13, select your flat file source system and click on ‘Display Datasource Tree’

Observe your datasource. Note the square icon in front of it, which denotes that it is a 3.x datasource.

Right click on it. In the context menu, select ‘Migrate’. Select ‘With Export’.

Migration completed successfully. Note that the emulate icon is removed.

Check the entries in the table ‘RSDSEXPORT’.

Datasource name exists in the table.

Rollback of datasource is possible.

In tcode RSA1OLD, check your infosource. You will find that Datasource assignment is not maintained.

Now go to tcode RSA1, double click on your datasource and observe the object type in object directory entry in the ‘Extras’menu.

Object type of the datasource is shown as ‘R3TR RSDS..’

Change your datasource by giving file path and data separator. Activate it and check the preview. Create infopackage and load the data to the PSA.

Step 11: Go to the infocube and create transformation. Load the data to the cube using DTP.

Leave a Reply

Your email address will not be published.