BPC Data load - pre aggregation automatically?

[former_member233959]

Hey Folks,

my question is about transactional data loading (from BW infoprovider, using BPC 10.1 classic) and actual - plan mapping of accounts.

Please regard following case:

Source (Datarecords):

ACCOUNT - SEGMENT - PROFITCENTER - SIGNEDDATA
AC1                    SG1               PC1                    1

AC2                    SG1             PC2                   1

AC3                   SG1               PC2                   1

Conversionfile:

External          Internal

AC1                    AC1

AC2                    AC1

AC3                    AC1

In our case we load with overwrite (match key) and it seems to be the case that BPC overwrites already while loading the matching records instead of merging them.

After loading it appears like that:

ACCOUNT - SEGMENT - PROFITCENTER - SIGNEDDATA

AC1               SG1                    PC1                    1

AC1               SG1                    PC2                    1

But we would like to have it like:

ACCOUNT - SEGMENT - PROFITCENTER - SIGNEDDATA

AC1               SG1               PC1                         1

AC1               SG1               PC2                         2

Is there a way to preaggregate so that we get the desired effect of a merge?

Greetz
Max

[former_member186338]

First of all the idea to append data on load looks not perfect in general If for some reason you have to reload data then...

Can you explain the business logic of append load? You don't have some required dimension to load data separately or...?

[former_member233959]

Hello Vadim,

I hope I get your question right, but the Business logic is that they want to just map a few (actual) accounts (AC2, AC3) into one (planning) account (AC1).

We never experienced any Trouble with that because there were not completely similar (so the profitcenter was different or something else).

Here for the first time the data records become completely similar AC2 and AC3 become AC1 and they have the same SEGMENT and PROFITCENTER. So the behaviour of BPC is here to overwrite the value instead of append.

We could load AC3 separately of course - but that is not the way he wants. That's why i was asking if there is any pre-aggregation option within bpc in the load process on the SOURCE (not target). Or do we have to do this in the transformations of the layers below in the SAP BW?

Best regards
Max

[Former Member]

Hi Maximilian,

This is the standard behaviour of bpc database...it will only aggregate the data which has all the members of the full cross section same. Even one different member in the record in cross section will be treated as different! Nothing can be changed in this as far as I know......

If you need aggregation based on profit center then you can write an end routine for the same and run it in transformation file while loading the data.

Regards,

JP