Skip to Content

BW Activities required while ECC new data integration/migration from new company

Hi Experts,

My client 'A' has acquired a new company B. company B is a Non-SAP system. New company B data is going to be integrated / migrated into exiting client 'A' SAP ECC 6.0 system through third party tool based on recording sessions.

Existing client 'A' is having BW 7.4 on HANA with SAP ECC as source. Since there is going to be new Master / Transaction data of 'B' company into 'A' company's ECC system, please let me know what that list of activities (pre, post & during migration) required for BW system to extract new data of ECC system into BW system till PSA.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 16, 2018 at 02:15 PM


    which steps/info did you already find by doing a search in these forums? if you provide your step by step you have created til now, we can easily check which steps to add, which steps to remove.


    Add comment
    10|10000 characters needed characters exceeded

  • Apr 17, 2018 at 11:09 AM

    Hi Mario,

    I have put below points as per my knowledge. I am not worried about data migration in ECC system, but only need to load new data from ECC to BW system. Please suggest and add few mandatory & relevant activities.

    Pre-requisite/ pre-activities of Data migration

    1. List down BW DataSources for which delta is based on specific fields rather than timestamp
    2. Check if delta loads are picking new Company ‘B’ Master/Trans data through a dry run in QA for both LO & Non-LO.
    3. Take pre-screenshots of critical BW reports with respect to current year data to compare post integration.
    4. Migration activity needs to be carried out first in Dev or QA system to do hands on, get accustomed and access the complexity before actually doing in production system.

    During migration activities

    1. Re-schedule all the process chains to facilitate data loads of new company ‘B’ data added in ECC system
    2. Do Master data load for newly added company ‘B’ master data until PSA
    3. Do history data load for newly added company ‘B’ transactional data until PSA
    4. In case of data miss user locks in ECC would be required to load data & initiate delta
    5. Continuous monitoring of Process chain data loads requires and take necessary action

    Post migration activities

    1. Adjust/enhance BW queries for new company ‘B’ data & entities
    2. New authorization/roles setting for the new entities
    3. Load additional new data of company ‘B’ from PSA to DSOs and Cubes

    Risk analysis

    1. BW reports might not be available with latest data to users during migration
    2. Increase in physical memory usage of HANA database due to new data
    3. Many BW reports may require enhancements for accommodate company ‘B’ new entities

    Add comment
    10|10000 characters needed characters exceeded

    • if the data for the new company is integrated into the source system, you have only two major points to look at:

      1. filters on company code: in infopackages, dtp's, reports, transformation routines... you need to adapt these accordingly

      2. sizing: you need to estimate the additional number of records coming into the bw system. all your deltas will infact become full loads for the new data the night after the source system migration ... you need to take this in account for you timing of the loads