migration of datasources

[Former Member]

Hi All

I want to migrate datasources related to FI application component.( masters and Transactions ).

All the datasources already replicated from r/3.

all they are in 3.x.

IS THEREANY POSSIBILTY TO MIGRATE ALL DATASOURCES AT ATIME BASED ON APPLICATION COMPONENT?

Tx

[Former Member · Accepted solution]

there is no mass datasource migration tool - you need to do it manually one by one

[Former Member]

There is no way to migrate all the DS at a time based on app comp... have to migrate individually...

Raghava

[former_member345199]

Hi,

How to Migrate a 3.x DataSource to a 7.0 DataSource

Currently there are many people upgrading from 3.x to 7.0. The biggest question is how and when do we upgrade objects that were developed within the old 3.x functionality? What does this mean for someone that is still understanding the differences?

The biggest question out of the above ones is when do you upgrade and how do you do it. Most of the time, it is easiest to do a technical upgrade at first and as you start a new development phase, you start upgrading your objects and security. For people that don't know what a technical upgrade is, it is basically upgrading the platform that you are working on, which includes the new functionality but the capability to continue using the 3.x development that has already been done. Also remember 3.x security will no longer be supported when you upgrade to 7.0 functionality and you don't want to use this security methodology either because of the better functionality that is offered within 7.0.

The following steps are one of the many ways to upgrade currently developed 3.x objects to 7.0 functionality:

1. Find the InfoSource that the upgraded DataSource is attached to

2. Create a new transformation against the data target or the infoobject that is to be upgraded. In the case that it is Master Data and it is flexible, you can still create a transformation directly against the InfoObject(s) because a DataSource can be tied to multiple transformations.

3. Create DTP(s) for this transformation(s) and Activate

4. Right click on the DataSource and choose Migration

5. A pop up screen will come up next and will ask you if you want to migrate with export OR without export.

1. Differences between the 2

1. With Export - Allows you to revert back to 3.x DataSource, Transfer Rules, etc...when you choose this option (Recommended)

2. Without Export - Does not allow you to ever revert back to the 3.x DataSource.

6. A transport should be requested after you choose one of the above mentioned because the transfer rules will be deleted and the emulated 3.x DataSource will be converted to 7.0 DataSource.

Now, the next decision that needs to be made is in how you convert 3.x objects and in past experience it should be a phased approach. If you are still in the a development phase, you should upgrade each of the current developed objects and do not upgrade objects that have been through development cycles. If an object that has been through the full development cycle and needs to be upgraded due to a defect, these objects should be next. After all of these new/current developed objects have been upgraded to 7.0 functionality, then I personally would start upgrading past development objects.

Note**That I have seen in some cases that the transfer rules deletion is not added in the transport, one way to avoid this from occurring is after you create the new transformation with the datasource assignment, you can manually delete the old transfer rules and the associated datasource assignment. his will request another transport request and you can use the same one when migrating the datasource.

Refer

http://www.econsultantresources.com/index.php?view=article&catid=48%3Asap-business-intelligence&id=6...

Emulation, Migration and Restoring DataSources

http://help.sap.com/saphelp_nw04s/helpdata/en/43/682cacb88f297ee10000000a422035/content.htm

Hope this helps.

Thanks,

JituK

[Former Member]

Good question to my knowledge do not think you can migrate DS application comp wise

use Tcode - RSDS

Under the menu 'Datasource' you will find the options.

While migrate use EXPORT option so that later if you want to revert back from 7.0 to 3.x ,you can stil achieve.

Hopeit Helps

Chetan

@CP..

[Former Member]

Hi suman naidu,

After Upgradation to BI7.0 your Info Sources , Data Sources, Transfer and Communication Structures will remain as in the 3.5.

you can check everything in BI7 for your 3.5 IS, DS and IP.but it will be in 3.5 only.

If you want seen in BI7, you need to Migrate all.

DS should be Migrated and total infrastructure will changes.

There is no need of Update rules, Transfer rules in BI7, you have to create Transformations.

yes you can copy the existing IP from 3.5 to 7.0, but only change is you have to create Transformations.

If it is R/3 then no need to create DS seperately, you can Migrate them.

One more option :Emulated DataSource_--> means ---upgraded 3.x datasource(you will see square symbol on the emulated datasource) which could also use BI 7.0 capabilities along with 3.x loading methodlogy.(both paths are available).

But once you migrate an emulated DataSource it completely becomes BI 7.0 datasource(using transformation and DTP) and you no longer can use the 3.x way of loading (using transfer rule ,update rule etc).

Check properly the new way of loading before migration of datasources to bi 7.

Please have a look into the FAQ in the SDN.

https://www.sdn.sap.com/irj/sdn/docs?rid=/library/uuid/7c2a7c65-0901-0010-5e8c-be0ad9c05a31

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/77712b896f3457e10000000a422035/content.htm

Also find the below threads which helps u lot...

Assign points if this helps u...

Regards,

KK.