Production to Quality System Refresh

[Former Member]

Hi

Could you please explain what exactly System Refesh takes care ...

We want to refresh the data in BW Quality from BW Production , for BW quality and Production system the Source systems are

Db connect and SAP R/3 Systems ,

After refresh data (in ODS , Cubes data Production ) will get copied into Quality ( corresponding ODS , Cubes ) ???

Before refresh and after refresh , how the source system connectivity takes care???

what would be the BW Consultant Roles as a part of the System refresh ??

Regards

Nagamani

[Former Member · Accepted solution]

Hi,

have a look at [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d0384b7b-374b-2b10-c290-865f84b9bed2&overridelayout=true].

The document shows how to do a system copy and also links to additional documentation.

Best regards,

Ralf

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Hi,

Generally the refresh from production to quality is done to have enough data for testing so that you can replicate most possible business scenarios while testing any requirement.

So when you do refresh all your modeling objects get copied in quality from production here it copies or rather I would say it will overwrite structural as well as data changes. It basically creates exact copy of production system.

The source system related objects get modified by running a transaction called "BDLS" i.e. the pointers referring to production source systems will not refer to quality source systems.

After refresh is completed work of BW consultant is basically to check whether all the modeling objects are active and contains proper data. Execute import queries or existing important reports and make sure that they are running fine.

From data loading perspective you need to execute process chains and make sure that source system connectivity is fine.

If you do this much your most of the validation will be done.

Regards,

Durgesh.

[former_member184494]

As far as system copy goes - it is making a copy of the production system into another box and overwriting your existing QA box with the copies one..(Overly simplified though )

Once a system copy is done - a ogical system conversion is run ( also called BDLS ) to convert the source system conversions...

As a BW consultant you will have to check :

1. Source system connections

2. If the data is copied and is reportable / loadable

3. Create new infopackages , execute process chains to fetch from QA

this is more of a sanity check to make sure that everything is fine. However when you copy from PRD to QA - all requests which are in QA and have not yet moved to PRD will be lost.

Edited by: Arun Varadarajan on Jul 7, 2011 11:08 PM

[Former Member]

Hi All,

Thanks for your responses ..

In our case we bulding up new QA system , and doing system copy of QA from Existing Prod environment and as well creating

new BIA Serrvers and New Portal server ..Existing QA Source systems ( DB connect and R3 ) we are connecting to the New

QA Environmnet .. and we are using Integrated planning and Broacasting as well ..

After system copy from PROD --> New QA System , any specific things we need to take care of as a part of

Intregrated planning , I views in Portal , Portal settings ??

Going forward we want load data from source systems to new QA Environment , So can we do the system copy of

New QA ( from PRDO ) Environment and source system refresh activities in paralell ??

Regards

Nagamani

[AK_BUILD]

AS a BI Consultant u need to refresh the data(transactional and master data) in BI as ECC QA and BI QA data will no longer match.

Delete the entire data from all the targets. If neccessory u will also have to replicate the Data sources and then just reload the data into all targets.

Check if all the Process chains are running fine.

As far as connectivity with ECC is concerned, Basis team will take care of it.