BPC 10 SP20 : duplicate member in hierarchy from 0GL_ACCOUNT

[Former Member]

Hi BPC experts,

I have the following issue : when loading an hierarchy from 0GL_ACCOUNT into Account dimension, I got some duplicate members.

These duplicates are actually normal in SAP : some accounts change their hierarchy according to the amounts in debit or in credit. For instance, if the account 415000 is in debit, then its hierarchy is in the node BALU441 while if the account 415000 is in credit, then it would be in the node BALU451.

I have read the post https://scn.sap.com/thread/3333412 that has the same case.

It seems the best ideas are :

- to create two account members by concatenating the node and the account

- to create a second hierarchy

- to remove the duplicates in BW

I was wondering if there are any other methods to solve this issue ?

Thank you in advance,

Dat

[Former Member · Accepted solution]

Hi Dat,

I have had this issue a number of times in the past, and I have found the best way is to handle this on the way in to BW. You shouldn't just create a second hierarchy because let's say for 3 entities the balance is in debit, but for the 4th entity the balance is in credit...when you look at the total of these 4 entities you would not have the correct placement of the GL account.

You could ask the BW administrator / developer to add a rule into the extraction from ERP process. This should broadly do the following tasks:

• Check GL master data to see whether each account has value-dependant hierarchies
• Create a second GL account, only in BW, for these cases (for example 400000 and 400000C)
• If the value is debit, it should go to the normal account (400000), and if it's credit it should go to 400000C
• BPC would then see both of these accounts as normal master data, and there would be no problem

I have found this approach works well.

Tom.

[Former Member]

Hi Dat,

in my past project we created a new attribute for 0GL_ACCOUNT in ecc then bring it into BW, the new attribute will tell if the account is A/L or I/E, then append the letter to that account, in BW we download the hierarchy, modify the hierarchy with the new ID (with a ABAP program), then upload back into BW, then load into BPC.

There are few options as you listed, involve the business and see which option is the best fits your project, keep in mind that maybe one day you want to use BPC data in BW, then you need to find a way to match the GL account.

Andy

[Former Member]

Also, if the first solution (concatenating a node and an account) is to be used, How can we implement this ? How can we make BPC understand that a specific account is to be recorded according to debit/credit amounts ?