DataSources Migration

Hello BWers,
I have in my system some 3.x DataSources (with PSA) which provide DSO...
I have to migrate them in version 7.
My question is :
If i migrate DataSources in BI 7 version, have I to do an INIT for PSA and delete data in DSO and reload totally DSO ?
Or after migration I can simply continue my Delta loads ?
Thanks for response.
<Removed - Points is for good answers - offering points does not guarantee good answers ... please do not solicit points for answers ....
Cheers,
Vince.
Edited by: Arun Varadarajan on Oct 17, 2008 4:54 PM

Hi,
While migrating, better would be to delete the data from the targets. Logically you need not do it, but its always better to do it.
After that you have to replicate the data.
Then create the Transformation and DTP. You can use the same InfoPackage which you used earlier. All your codes in the transfer rules and update rules are converted automatically.
Then load the data in the targets.
Hope this helps.

Similar Messages

Datasource migration error from 3.5 to BI 7.0 - SP16

During Master data/text Datasource migration from 3.5 to BI 7.0 using export option, system migrates the datasource and shows error message 'The OLTP source 0COSTCENTER_ATTR for source system EC3150 not present', at the same replicate data source does not find a datasource. At the same time unable to replicate datasource. If you go outside the session and come back, everything works fine.
BI 7.0 system package level is SP16, upgrade to the system was done some time back.
Pls. share your experience in migration 3.5 datasources to BI 7.0 for both Master data and Transaction data.
Did any one experience similar issue like this?

I get the same error with a different object after upgrading a BI Business Content data source from 3.x to 7.0
It tells me "The OLTP source 2LIS_08TRTK for source system RD1CLNT230 not present".
Thx,
Gregg

Datasource migration from 3.5 to 7

Hi Expert,
BI 7 was installed in the environment with datasource 3.5 actviated in source system. I am not sure do I need to migrate datasources from 3.5 to 7.0? Can experts please share with me on what are the features available in datasource 7.0? Will datasource 7.0 improve on delta loading? Is migration a must from datasources 3.5 to 7.0?
Your reply is much appreciated.
Thanks and regards,
Kang Ring

Hi,
As correctly pointed out, the datasource migration is not required unless you plan to achieve the following:
1. RDA (Real Time data acquisition)
2. Direct access to master data.
3. Remote activation of datasource (meaning from BW itself, you can acitvate DS in ECC)
However the only checkpoint is that if you are using hierarchies, those have to be loaded with 3.5 datasources as 7.0 does not support hierarchies. It is supported in 7.3
Also check the link for BI 7.0 new features.
http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm

BW - APO Datamart datasource migration issue

Hi,
Question : Can we migrate datasources exported as datamart from APO-DP system into BW, from 3.x to 7.0 or does it have to be a 3.x datasource with transfer rules, TS , update rules etc ...
1) I know we cannot migrate data marts with 8* or //8 but this datamart is replicated from our APO-DP system and begins with 9*.
Thanks .
HS

Hi Geetanjali,
Thanks for the reply.
My problem is that I am getting error message "No transfer structure available for infosource 9* in source system" when I run the infopkg to load in PSA ( which is default for 7.0 datasources).
This is the dataflow l I wanted to have which replaces old model as shown :
NEW 7.0 dataflow : Datasource -->infopkg --> psa --> dtp -->transformation --> cubes ( same source feeds 3 cubes ) .
OLD 3.x dataflow : DS >Infosource>Transfer rules--> infopkg --> update rules --> cubes.
Thanks .
HS

COPA Datasource Migration from 3.x to BI 7.0

Hi Experts,
I am facing an issue to restore the migrated COPA datasource from 3.5 to BI 7.0.
I am doing this migration as mentioned below
1.selected the 3.x datasource and in context menu used migrate
2.used option "with export"
3_.No transport request was requested_
4.successfully migrated.
I am not getting the option "restore datasource" in the context menu of the migrated datasource.
I want to use this option if the solution is not working in the new BI 7.0 flow.
Thank you in advance for your inputs.
PKC

Hi Raghavendra
Thank u for ur earlier response.
I have tried your proposal. But, could did not succeed.
My issue Is I am not getting the option "restore datasource" after the migration & transport request is not requested while migration and hence the migrated datasource is locked as local object.
Thank x
PKC

Datasource migration

Hello experts
we are using BI7
we have to extract data from R/3 to BI using LO (logistic) after replicating the datasource we wish to migrate the datasource , can any one pls guide how to migrate (migration with export and / or migrate without export ) the datasource and also transfur rules and update rules to transformations . is there any document available on this as how to.........................
thanks in advance
rk

Hi,
Its best practise to migrate the DS with the option With Export ,so that you can restore to 3.x DataSource later when you need.
Check this for more.
http://help.sap.com/saphelp_nw70/helpdata/en/42/fda7cf2a5f517be10000000a1553f6/frameset.htm
Hope this helps..

Migrating of 3.0 Datasource 0FI_GL_4 possible

Hi,
anyone got exeperience in or has migrated a 0FI_GL_4 ?
Can this be done without problems ?
ThanXs
Martin

Hi Martin,
Before DataSource Migration, you have to migrate the "Transfer Structure" first. Otherwise Datasource activation may become dicey.........
Regards,
Suman

Problem in mapping after migration from 3.x to 7.x infosource

HI Experts,
I have a problem while mapping the data source 2lis_03_bf to info cube 0ic_cs01.
we have a flow like this now after migration done.
Datasource->transfer rules->infosource->transformation->info cube
Now we dont require infosource and its respetive transformation, we are going to map directly from data source to info cube.but we have routines available in info cube related transformation.i.e. coming from infosource to info cube .
I would like to create a new transformation directly from Datasource to info cube but all the source fields are not available in target cube. How to map them.do i have to map all the target fields or i have to map according to the transfer rules target fields. what is the funda to make a transformation and mapping the source and target fields.
Could anyone please through some light here..
Thanks much in advance.

sunil kumar wrote:
Hi,
>
> As said above convert transfer rules to transformations (right click on transfer rules -> additional prop -> create transformation)
>
> Then right click on datasource -> Migrate
>
> After doing this, your datasource will be linked to Infocube directly with one transformations automatically.
>
> Regards,
> Sunil
Hi Sunil & Sravan,
THanks for ur quick reply.As you said click on transfer rules and create transformation.As i can see in my system i have a transformation from data source to infosource .i.e. starting with RSDS_ and then another transformation from info source to info cube.i.e. starting with TRCS_ . what i did was created a transformation by right click on info cube and by giving data source name as 2LIS_03_BF .this is a manual transformation i am mapping manually.Is this a correct way? Please tell me how to do it.
as i have to do this immediately.
Thanks in advance

BI 7.0 Master Data Migration

Hi Gurus,
I have seen few threads for BI 7.0 Datasource Migration for transaction data but is it necessary to migrate even master data datasources (Attr and text, I understand that Hier DS cannot be migrated).
Will there be any impact if we do not migrate master data to 7.0 but only migrate transactional datasources to 7.0 ?
thanks
Surya

Hi ,
I am trying to migrate the Transaction data sources before moving into the DEV from Sandbox.
So i have to delete the existing TR/UR's and trying to create the transformation, but while creating transformation fields mapping is not happend automatically. (For manul field mapping the transaction data is the time taking process)
We are using the spk 8 . Please let me know any one has faced the above problem .
Regards
Jose

Migration from 3.x to 7.0 - Approach

Hello -
Want to get a confirmation:
1/ If there is no migration from 3.x to 7.0
   - Cannot use Transformations
   - Cannot us DTP
2/ If there is a migration, then
- Have to reconstruct Datasource to Target Mapping Entirely
    (e.g., 0MATERIAL InfoObjects to 0MATERIAL_ATTR Datasource)
     The R/3 field mapping to InfoObjects has to be completely redone, since there
     is no proposal
- What do most of the experienced folks do to ease the effort of reconstruction
3/ I understand that if there is no migration, cannot use RDA , remote activation of DS, error stack, and the items mentioned in point # 1, but these are nic to haves. Do you see a real advantage to the migration
Thanks - and points will be awarded
- abhi

Hello:
I think you are referring to DataSource migration?
1 - You CAN use transformations and you CAN use DTP without migrating the DataSource, this is known as an "emulated DataSource".
2 - NO "reconstruction" is required. Keep in mind that if you migrate a DataSource to 7.0 form, that transfer rules are deleted. Therefore, before DataSource migration you should use the "create transformation" functionality from existing transfer rules. This functionality will generate a proposed transformation, including proposed ABAP OO routines where ABAP routines had existed previously.
3 - you can use error stack with an emulated DataSource. In general, migrating to the new DataSource form ensures you have completely moved to the new dataflow concept in a consistent manner.   The new dataflow has good advantages from a performance standpoint, in that you can parallelize the data load. The error stack is a big advantage from a data quality standpoint. The overall approach using DTP's is a step forward in that the dataflow occurs in a more transparent manner in process chains and monitoring.
Thanks for any points you choose to assign.
Best Regards -
Ron Silberstein
SAP

BI7 and 3.5 Datasources

Hi
How to configure BI to extract v7 datasources instead of v3.5.
Im replicating a DS in ECC6 and Im getting a v3.5 DS in BI.
ie 0HAP_DOC_ID_ATTR.
Thanks in advance.

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=68%3A3x-70-datasource-migration&option=com_content&Itemid=77
Emulation, Migration and Restoring DataSources
http://help.sap.com/saphelp_nw04s/helpdata/en/43/682cacb88f297ee10000000a422035/content.htm
/thread/781655 [original link is broken]
/message/5051257#5051257 [original link is broken]
Migrating data source from 3.5 to 7.0
Hope this helps.
Thanks,
JituK

To convert BI DS to BW DS?

Hi,
Is there any way that i could convert BI 7.0 Datasource to BW 3.X datasource once it is replicated?
Because, ours is a newly upgraded system and all the datamodellings have been developed in BW 3.X
Now we have started developing new datamodels in BI 7.0
When i am trying to replicate the datasources in the Application , there were so many popups asking me to select the version of the datasource.
I am not so sure whether to go for 3.X DS s or BI 7.0 as every datamodel is different and for some we still want to be in 3.x
my question is:
suppose i had replicated a particulaar datasource as BI 7.0 datasource and wants to revert back to BW 3.x DS, what should be done to retain the old version Datasource once it is replicated as BI 7.0 DS?
Raj

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=68%3A3x-70-datasource-migration&option=com_content&Itemid=77
Emulation, Migration and Restoring DataSources
http://help.sap.com/saphelp_nw04s/helpdata/en/43/682cacb88f297ee10000000a422035/content.htm
/thread/781655 [original link is broken]
/message/5051257#5051257 [original link is broken]
Migrating data source from 3.5 to 7.0
Hope this helps.
Thanks,
JituK

BI 7 Inventory Transformations 0IC_C03

Hi,
any body implemented Inventory managment in BI 7 flow.
we are implemenating Inventory managment in BI 7 flow. issue is when installling transformations most of the keyfigures are not mapped, do we have to map/ write rouitnes, content will not give rouitnes for keyfigures.
transformations for 2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM.
can any one please help on this. transformations with routines are much helpful.
Regards
Raj

Raj,
Check note: [Note 1073268 - SAP Best Practices for BI V2.70|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1073268]
BI Scenario Inventory Analysis
Symptom:
You have activated InfoCube 0IC_C03 in dataflow before. The dataflow is available from the InfoCube downwards to the InfoSources in 7.0 technology (transformations). However there is no connection between the InfoSources and the DataSources, because all DataSources have been activated as 3.x DataSources.
Reason:
The Business Content for the InfoCube 0IC_C03 has changed and now uses the 7.0 technology for data flow.
Solution:
1. Migrate the follwing DataSources to 7.0 DataSources:
2LIS_03_BX
2LIS_03_BF
2LIS_03_UM
In transaction RSDS enter the relevant DataSource and the source system. From the menu choose DataSource -> Migration 3.x DataSource -> DataSource.
2. Reactivate the InfoCube 0IC_C03 in dataflow before.
3. Check the transformation TRCS 2LIS_03_BF_TR -> CUBE 0IC_C03. If it is not active, check if there is an error in the start routine. If this is the case, refer to SAPNote 1052648, section "Start Routine" for a solution.
Srini

Source system in Production doesnt exists Error RC- 8

Hello experts!
We connected a second source system to our 7.0 BW. We transported from development to quality system and everything is fine. Now we want to transport to production and we got RC=8 and the message that our "source system does not exist"
First we checked our source system. It is ok. we can replicate datasources, load units and currencies. But when we want to transport something what is directly connected to the source system we got everytime a RC=8 because of source system. For sure, we checked our "Conversion of logical source systems names". We checked if the mapping from development to productive is correct many times but we can find no error.
Is there something I can not see?
I tried to transport Transformations, DataSource Migration, other things connected to 7.0 and 3.x DataSources. Nothing works. I transported a transformation got a little different error like no rules exist because missing infoobjects in source or target or they are not activated. But target seems to be ok and source also have the fields.
Also I have searched the previous threads I have got what I have done but for sure some thing I am missing !!
Any Ideas???
Best regards,
Yash

Thanks Murali for your prompt reply,
I have manged to do the conversion settings again and now the source system client problem subsides !!!
But when I import the requests again from QA to PRD it says that some DS cannot be activated due to inconsistency in CRM production system. Actual message is.
Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
Mapping between data source 0CRM_SRV_CONTRACT_H and source system PC4CLNT400 is inconsistent
Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Activation Mode)
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active, total of 4 inactive InfoObjects
InfoObject Exchange Rate Date ( 0CRM_EXCDAT ) is not active
InfoObject Exchange Rate Type ( 0CRM_EXCTYP ) is not active
InfoObject Quotation GUID ( 0CRM_QUOGUI ) is not active
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
is that due to the DS .. some are in BI 7 cannot be mapped with 3.X ?
I will be importing a new request all the way from DEV to QA and Then in PRD as of now to see the inconsistency once again.
Cheers
Yash

Owb3i data flow connectors problem in mapping editor

Hi,
To define mappings between source and target, the manual says:
steps 1-3 and then,
"Repeat steps one through three until you have created all the data flow
connection appropriate for your situation."
The manual also says:
"To connect Mapping Operators, you draw lines from output attributes or output
attribute groups to input attributes or groups between the operators."
The question:
When I draw a lines for individual connections, it is fine. But I have a source/target with 201 columns. So I dragged my mouse between the groups. This created 201 additional attributes in the target. Am I doing it wrong or is it a 'feature'? How else I can make all the 201 connections less painfully?
TIA.
--Rao.

sunil kumar wrote:
Hi,
>
> As said above convert transfer rules to transformations (right click on transfer rules -> additional prop -> create transformation)
>
> Then right click on datasource -> Migrate
>
> After doing this, your datasource will be linked to Infocube directly with one transformations automatically.
>
> Regards,
> Sunil
Hi Sunil & Sravan,
THanks for ur quick reply.As you said click on transfer rules and create transformation.As i can see in my system i have a transformation from data source to infosource .i.e. starting with RSDS_ and then another transformation from info source to info cube.i.e. starting with TRCS_ . what i did was created a transformation by right click on info cube and by giving data source name as 2LIS_03_BF .this is a manual transformation i am mapping manually.Is this a correct way? Please tell me how to do it.
as i have to do this immediately.
Thanks in advance

DataSources Migration

Similar Messages

Maybe you are looking for