Double Members after Hierarchy change

[johannes_knaub4]

Dear Experts,

we are facing an issue on BPC 10.1 Standard on HANA.

If we are changing the hierarchy e.g. in Time Dimension by pulling 2017.TOTAL below 2016.TOTAL we are getting an error when processing.

the Error is: Detected dublicate Member ID (in this case 2017.Total).

This happns to all Dimensions.

System:

BW: 740 SP014

CPMBPC: 810 SP009

POASBC: 100_731 SP006

HANABPC: 810 SP009

Thanks

Johannes

[johannes_knaub4 · Accepted solution]

Hi Vadim,

Thanks for your Help.

In the End, it turns out that Note

https://launchpad.support.sap.com/#/notes/2404956/E

is solving the issue, I do not exactly understand why...

Cheers

Johannes

[former_member186338]

Please look also on this note: https://launchpad.support.sap.com/#/notes/2296133

Also: https://launchpad.support.sap.com/#/notes/2338935

[johannes_knaub4]

actually no, but it should not matter.

We opened a Ticket, but no solution yet, I could not find anything in SAP Notes and hope that someone already faced this issue.

[former_member186338]

Please test the same with some dimension with a single hierarchy (like my test with ACCOUNT from ENVIRONMENTSHEL)

[former_member186338]

Just tested the same for some user defined dimension with multiple hierarchies in BPC 10 - also no issues!

P.S. Have you tried to use UJA_REFRESH_DIM_CACHE?

[johannes_knaub4]

Refresh dim cache helps to get the initial setup, but trying is once again results in same error...

[former_member186338]

Read notes 🙂

Looks like SP11 has some fixes!

[johannes_knaub4]

Hi Vadim,

unbenannt.jpg

actually I am trying to change the sequence of a hierarchy.

When doing so, the moved member gets double in the dimension and the process fails.

This is happening in all dimensions.

Thanks

Johannes

[former_member186338]

Unable to test it in BPC 10.1, but in BPC 10 Environmentshel copy it's working fine (just tested on the ACCOUNT dimension). Hope you have single hierarchy in the dimension?

[johannes_knaub4]

HI Vadim,

you are completely right, but we are facing the same issue in User defined dimensions.

Actually Time is not really the problem, I thought this will be a good example and standarized for a lot of applications.

The problem occur in each dimension.

[former_member186338]

Can you explain your actions step by step with some screenshots? Not 100% clear what are you doing...

[former_member186338]

TIME dimension is a special dimension with some rules for hierarchy and properties!

Please show screenshot of your existing TIME dimension administration and explain the change you want to perform!

[johannes_knaub4]

unbenannt.jpgThe Error Message: