Emulated datasource Migration

[Former Member]

Gurus,

If I have to decide between not migrating the datasource and just emulating it as per the posts seen on SDN ,what would be the effects ??

are we losing major things here or its just temporary adjustments for migration.

thanks

[Former Member · Accepted solution]

The following features are only supported for new SAP NetWeaver 7.0 (2004s) DataSources (and not for emulated ones):

Data reconciliation

Remote activation of DataSources

Real-time Data acquisition

Direct access to master Data in source system

Hope it Helps

Chetan

@CP..

[former_member441329]

Hi...

<b>Emulated DataSource</b> 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<b> migrate</b> 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.

[Former Member]

paul,

Simple words on Migration... If you migrate it ... DS pretty much works as object in Bi instead of SAp R/3. We can maintain DS in bi... we can activate it etc.

If it is emulated... we don't have those options. that is the difference.

if you plan to it... do it " With Export" option only.

Nagesh Ganisetti.

• assign points if it helps.

[Former Member]

If you byepass infi source, you will be fine. Take the data from the data source to DSO and then you do data marting to other info providers.

Ravi Thothadri

[Former Member]

If I have to decide between not migrating the datasource and just emulating it as per the posts seen on SDN ,what would be the effects ??

There are no adverse effects, either way it will work fine

are we losing major things here or its just temporary adjustments for migration.

The major thing that i can think is, you would stuck with attaching one datasource only to one infosource and routing that IS to different providers(which was the way in 3.x and you might already have that set up), but with RSDS, you have a option to directly link one DS to many dataproviders