Skip to Content
author's profile photo Former Member
Former Member

Merging Two BW Environments issue

Hi All,

We are going to Merging two BW 7.0 systems.

Before I have experience on Up gradation & Migration projects in single environment.

But this time migration is based on two environments(merging)

please share some valuable inputs based on following issues.

ex1: one common master data Info object merging

ex2: one Z (uncommon) master data Info object merging

ex3: one common transaction data merging

ex4: one Z(uncommon) transaction data merging

or Physical Year Periods in Two Systems.

Note: We need to create same data flows in Target system(if less no of objects in 2nd BW system) or Need to copy.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jul 30, 2012 at 05:51 AM


    It is always better to add an extra infoobject in DSOs and Cubes to differentiate the data as per the source systems. It will be very useful.

    Suppose you have data coming from ECC and CRM systems, you should consider creating an infoobject to type CHAR 6 and inserted a constant in the transformations and put the values as 'ECCPRD' and 'CRMPRD' in respective transformations.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 01, 2012 at 12:17 PM


    Merging depends on the data present in the objects and not on the objects present in the system.

    1) if master data is common.

    Merging is a difficult job if the master data has same value but corresponds to different items. Lets say if material 100 in system A corresponds to material A and material 100 in system B corresponds to material B. So u if same material is loaded to 0material in BW the last one will overwrite the previous one. Inorder to avoid this u have to compound source system to all ur master data. If the system already has data then you have to drop all the data and then compound the infoobject with souce system. This will not be accepted by most customers.

    2) if master data is not common and transaction data is common

    If sales data is present in both the system and if same sales order number is present in both the system then how will u differentiate this? You can either add source system as a keyfield to the existing DSO and cube or store the data in two different infoproviders for 2 different system and then see the entire data using a multiprovider.

    There are lot of possibilities. You have to first understand what type of data each system holds and the relationship between them to formulate a merging startegy.You can also use MDM tool if u want to merge master data.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Manu,

      My company combined 2 BW systems together several years ago so I hope my experience could help you.

      First, it's good news that you just have 7 common master data InfoObjects. As other gurus suggested, please make sure these InfoObjects are compounded with source system (0SOURSYSTEM) if they are linked with different source systems. And it's the same for text InfoObjects. We need to distinguish the master data/text.

      Second, transport is the best way for such project ( and I think it might be the only way ). For basis, it's easy, they just need to setup a transport path between your 2 BW systems. I'd like to suggest transport from your BW1 production machine to your BW2 development machine. This is because production is always clean and reliable.

      For BW consultants/developers, they need to create transports to package corresponding objects. You may need to setup different rules for different objects:

      Common InfoObject: add 0SOURSYSTEM, manually change them in the target machine to make sure it contains all attributes in the 2 machines.

      Uncommon InfoObject: just package them and transport.

      Common transaction data: compare the DSO/Cubes in the 2 BW systems. Add 0SOURSYSTEM into them and manually change in target machine to make sure it contains all fields in the 2 machines.

      Uncommon transaction data: just package them and transport.

      By the way, do you need to transport front end objects like queries/workbooks?



  • Posted on Aug 01, 2012 at 01:14 PM


    I think in case you want to have distinction on different source systems for data you need to have say sourcesystem and logsys mapped..

    In the master data in the compunding u can have SOURCESYSTEM object say with CHAR 2 OR 3 or as u want?

    u can always keep it constant as per source system when you will fetch the data from source..

    also in case of transaction data u can always distinguish the data based on the source system and logsys mapping ok..

    then u can merge the transaction data say by removing these fields say at cube level if u want..

    Thanks and regards


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.