Changing the datasource of LO cockpit inR/3..need a backup plan

Question

Hi gurus,
i am going to change the datasource in production system i have done everything in Dev and QAs but my client is asking for a backup plan if something goes wrong.
like if the transport fails he want everthing to normal without effecting the setup of deltas and data in BW
can somebody suggest me what i can do as a backup plan if something goes wrong.
thanks and regards
neelu

Answer 1

Hi Neel
If something goes wrong and it mess up your deltas in Production system then what is the backup plan?
This is what I think -
If your data source is LO cockpit extractor then ensure following -
Before your R/3 transports ,stop V3 batch job .
Lock the users (transaction lock) ,
Stop batch jobs that will update base tables of extracor
Drain the delta queue into BW till you get 0 LUWs in RSA7 for that datasource in R/3 system.
Activate the last request in ODS and also send the data into Infocube . Now you have all data till that time into BW.
Import your transports. Then execute V3 job in R/3 and run Info package from BW .
If something is messed up then immdiately push another transport that will repair it .Then  do Init without data transfer and resume deltas.
For other extractors just ensure to Drain the delta queue into BW till you get 0 LUWs in RSA7 for that datasource in R/3 system.(I assume that you will take care of batch jobs /transactional update - they should be stopped for any extractor)
Hope this plan helps you .
Please let me know if you still have questions.
Best of luck
Pradip