Technique for switching ECC source systems in SAP BW Environment without affecting the
data modeling objects in the BW environment. By data modeling objects, we mean transformations, update rules and transfer rules getting inactive or getting deleted. Once the source system is switched, data reload needs to happen to have the initializations and deltas to come from the new source system. Also we have to ensure that the data from old source system( both transactional and master ) needs to be deleted in the BW system before reloading from the data from new source system to ensure consistency in the data from new system.
The following SCN Article describes the procedure
Step by Step on Changing ECC Source Systems without Affecting Data Modeling Objects in SAP BW
See also 110849 – “Error during insert in port table” (create source system) if the error occurs during the RSA1 / Source System / Restore step
1461926 – FAQ: BW report SAP_INFOCUBE_DESIGNS
In BW 3.5 the identification of characteristics and navigation attributes in MultiProviders did not need to be consistent. This means that for compounded characteristics, the assignments for each underlying infoprovider must be consistent with regards of compounded characteristics and compunding objects.(See Note 920416 – Checking compounding consistency in MultiProviders for details)
During activation this caused only a warning message up to BW 3.5.
As of BW 7.x this warning was changed to an error. This can cause problems to migrated Infoproviders.
Several notes were released to solve this. At some point the possibility to convert the error to a warning on the level of the individual Multiprovider has been added.
Yo can find the optional setting when editing/displaying the Multiprovider in RSA1, via the Extras menu entry.
Here is a list of notes to check in relation to this problem.
See also the following article in SDN.