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

Many records in BPC cube after import transaction data

Hi!

Can someone explain one thing. Then we import some data to BPC cube (for example, Import from NW inforpovider), BPC generate too many unnecessary records. For example, there is one record in BPC:

Account1 1000

and one record in BW cube:

Account1 1000.

After we perform import package it generates 2 records in BPC:

Account1 1000

Account1 -1000

Account1 1000.

I mean, even if the new record is equal to existing in all fields, it first generate negative records to get null in cube, and then write new record. Equal record!

10 imports of the same data - 21 record in cube, and still 1000 in result. So we need to collapse data in cube (run light optimization) after each import of data in BPC ideally? In other case it dramatically reduce the perfomance.

Is that normal? How we can avoid this?

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 20, 2011 at 12:58 PM

    Hi Anton,

    Thats the normal behaviour. Could you please check the snote 1502996 which is an explanatory note about the data load options. This note gives a good view of how the records get created.

    Light Optimization with zero elimination after compression would get rid of the offsetting records. Its good to run this package regularly as per your requirements.

    Thanks,

    Sreeni

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Gersh Voldman

      No, for JAN and FEB only. But every time you load JAN and FEB number of records in BPC cube increases by four records. Ten loads - plus 40 records without any changes in keyfigures.

      Let's say you have 100 000 source records in actual data (BW cube, for example, with actual sales). And you planned daily load in BPC with LOAD_INFOPROV_UI from that cube. Even with no changes in source data you will have 2 800 000 records in BPC cube just in two weeks (if without Optimization).

      Edited by: Anton Kuznetsov on Oct 24, 2011 8:53 AM

  • author's profile photo Former Member
    Former Member
    Posted on Oct 26, 2011 at 02:07 PM

    Problem still have no appropriate resolution, there is only "explaination note" by SAP.

    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.