Skip to Content
avatar image
Former Member

Regarding Anaysis requirements of BI client systems


I am into project, where a company gillete is sold to Proctor and gamble., gillete company has R/3 systems with

Proctor and gamble too has R/3 systems, now after aquisistion gillete data has to move to Proctor and gabmble.,

So gillete systems has master data, transactional data with Proctor and gamble has master data and transactional data.

now data conflict arises between gillete and Proctor and gamble, like same masterdata might have between gillete and

Proctor and gamble., invoice number ranges might be same between gillete and proctor and gamble, process keys might

be same between gillete and proctor and gamble while moving data of gillete to proctor and gamble.

Like above mentioned issues might have so many.

So what are the things that i have to be aware while analysis part of the systems.

Can anyone kindly give me suggestions or anyone has any standard document of checklist for data issues to be

analysed. Please share to me.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 20, 2010 at 02:53 PM


    Please do not disclose the customer name (client) anywhere, it may create a problem to you if your company have any privacy policy against it.

    Now, regarding your problem, If you have two source systems, it always better to use 'source system' compounding in all the infoobjects. Since you alrady have data in infoobjects, it will be difficult to include compounding. So you can create new infoobjects (for example if you have Z objects in your existing system you can create Y objects) and use source system compounding in these new objects to differentiate the data.

    If you already have source system, then map it from both the source systems.

    Also, do not forget to initialize deltas for delta datasource from both the systems.


    Add comment
    10|10000 characters needed characters exceeded