Using BI Content as prototype and re-create the whole thing as custom obj

Question

Dear SDN fellows,
Currently in my project I encountered the case where 1 BW system is shared by 2 source systems (R/3 and ECC6) and the master data from the 2 source systems are overlapped (eg. same material no from R/3 and ECC6 have different meaning).
One of the suggestions is to use BI Content as prototype and re-create the whole thing as custom objects. For example:
0MATERIAL is created as ZMATERIAL, thus all "0" objects are for ECC6 source system and "Z" objects for R/3.
It will require enormous effort to do, and we try to automate as much as possible in every stage of development (to avoid human error as well) such as:
u2022 Re-create all BI Content InfoObjects programmatically using BAPI functions (BAPI_IOBJ_GETDETAIL, BAPI_IOBJ_CREATE and BAPI_IOBJ_ACTIVATE_MULTIPLE). Does anyone know what function module or ABAP class to get like "Create InfoObject from template in RSA1"?
u2022 Re-create all BI Content Transfer & Update Rules programmatically (copying and automatically changing the InfoObjects from "0" to "Z" in the mapping). We are still researching on class CL_RSAU_UPDR and function module RSAU_UPDR* for this.
Our main worries is when re-creating the transfer & update rules, as most of the SAP complex logics are implemented here using start routines, transformation routines, formulas, rule groups, etc. Using copy-paste & find-replace the routine may not be sufficient, full understanding of the logic might be required, and there are many of them, which makes it even more difficult.
If anyone ever did this approach before, please share how did you go about it? Thanks alot.
regards,
arie

Answer 1

Thanks Akashdeep for your input. Yes we are aware to add 0SOURSYSTEM compounding in all master data InfoObjects to handle multiple source systems.
We would like to get practical advice on how to do the re-creation of all BI Content objects (InfoObjects, Transfer & Update Rules, Queries, etc) in the most efficient way, probably programmatical way, to reduce the huge effort required and avoid human error if we are doing it manually.
Also our main worries with re-creating the transfer & update rules, as most of the SAP complex logics are implemented here using start routines, transformation routines, formulas, rule groups, etc. Using copy-paste & find-replace the routine may not be sufficient, full understanding of the logic might be required, and there are many of them, which makes it even more difficult.