Integrating 0COSTELMNT and 0GL_ACCOUNT into ACCOUNT DIMENSION (SAP BPC 10.0 NW)

[former_member233959]

Hello experts!

I am searching for a solution regarding the possibility to load 0GLACCOUNT and 0COSTELMNT Master Data into the Account dimension.

Actually we need 100% of the 0GL_ACCOUNT members and additionally the members of 0COSTELMNT of 4 CO_AREAs are necessary. So there are equal members within 0COSTELMNT but in different CO_AREAs (and not every account is in all of the 4 CO_AREAs). And additionally you will find some of the members of 0COSTELMNT in 0GL_ACCOUNT.

So we are loading the data of 0COSTELMNT to get the data delta between 0GL_ACCOUNT and 0COSTELMNT also into our ACCOUNT dimension via the transformation file / conversion file of the Data Manager.

To be able to use the hierarchies of 0COSTELMNT (which are also being loaded into BPC)

This is quite tricky as we would like to consolidate the members of 0COSTELMNT who are the same and regardsless the CO_AREA.

So e.g. reduce the records 0COSTELMNT 0070020000 CO_AREA 0001 and 0COSTELMNT 0070020000 CO_AREA 0002 to 0COSTELMNT 0070020000 and load this member into the ACCOUNT dimension if it is not existing there already (because of the 0GL_ACCOUNT load before).

My first approaches ended up in having duplicate member IDs as I couldn't consolidate. And probably I could do a few single transformations and load each CO_AREA in a single transformation and overwrite, overwrite and overwrite until all necessary members of 0COSTELMNT and 0GL_ACCOUNT are included. But this solution doesn't sounds very professional.

Does somebody has an experience in doing this and some kind of good or best practice?

Thanks in advance!
Max

[former_member233959 · Accepted solution]

Ok finally,

if you are mostly just interested in having all ACCOUNT Members and not that you are having absolutely all attributes in it for all the ACCOUNT members which are duplicates you could choose the solution to just set VALIDATERECORDS=No in the *OPTIONS section in the transformation file.

This worked perfectly for us. The thing is that the attributes among the members of 0COSTELMNT would be anyways the same except for the 0CO_AREA so we were happy enough to just get one record of each.

BPC is not putting duplicates in the Dimension member just one of each following any logic.

Thanks and best greetings

Max

[former_member233959]

Hi Andy,

thanks for your response I will have look on this approach!

But if some people have further ideas or experiences - please share!

Thanks

[Former Member]

Hi Max,

you can use routine in your transformation file to eliminate all the duplicate members before it updates into BPC. you need a ABAP resource.

Andy