Correct if its R/3- ECC Prod to QA refresh,You would do that so that you have perfect real time scenario data for running test scripts in other words to do carry out proper functional testing.
BI Production to QA refresh to create a non-productive system landscape for testing, quality assurance or other purposes. Or you want to copy your productive landscape onto a new productive landscape to change some property of the systems like hardware, operating system or database.Also to test some proof of concept like NW2004s ,but scenario like POC(proof of concept) would be done in Sbox/Dev(Copy of Prod) and upgrade Sbox or Dev to QA and PRD.
The SAP BW system is refreshed without refreshing the Source System in
parallel. The following implications should be understood:
1)SAP BW Objects (in SAP BW and Source System) need to be re-synchronized
2)All data will be out of synchronization between SAP BW and Source Systems
3)Master, transactional, and global settings data re-synchronization is required.This effort can be considerable.
4)SAP BW is essentially an “island” until data is re-synchronized
5)SAP BW systems with multiple Source Systems may want to consider using the InfoObject 0LOGSYS in data models as it provides an easier mechanism for selecting data during Data synchronization
Hope it Helps
Chetan
@CP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.