SAP BW System Copy: Issues and Resolution
This document describes about SAP BW system copy from Production to pre production system in parallel to ECC system copy. It is providing guidelines about preliminary checking and preparation before copying the system and post copy check with issues fixing. It is having high level details about task needs to be performed by SAP BW consultant. Task needs to be performed by SAP BASIS team is not in the scope of this document.
SAP BW Production system and Pre Production System.
A template checklist prepared about the task needs to be performed before copy and after copy is embedded here for reference.
Post copy issues & resolution
For some infoobjects(eg 0Profit_ctr,0Project,=comp_code.0GL_acct etc.) while loading data from source system it ended with error “No source system ID exists for source system (logical system) <old Source System Name>”
Info object 0logsys contains a transfer routine through which if it is intial it gets value of source system.
Reactivate transfer rule by using SAP Standard Program RS_TRANSTRU_ACTIVATE_ALL
Info package missings for another source system which is not copied.
Refer to SAP Note 1330317 – InfoPackages for DSs missing when collecting for system copy.
In Our case we resolved issue by recollecting info package because having less number of info packages.
Myself system (export datasource flow for dso missing)
Insert/delete/activation failed for dso with message export datasource does not exist.
Right click on DSO, generate export datassource, goto datasource tree, search export datasource (Name will be prefix with 8 followed by DSO technical name). Right click on datasource and select replicate meta data.
ITAB_DUPLICATE_KEY error during Insert/delete/activation for DSO.
Refer to SAP Note 1129654 and note 1298661 to fix this issue.
SAP Note 886102 System Landscape Copy for SAP NetWeaver BW