BPC 10.1 NW incorrect Hierarchy in Excel but correct in Web Admin

[abhishekkhatti]

Hi,

We ran into a strange problem where the hierarchy in our entity type dimension was not showing correct hierarchy (PARENTH1, PARENTH2, etc.) in Excel but the master was still correct when checked in Web Admin.

In Excel, some levels were thrown out of our regular hierarchy structure were showing without a parent, but the node name was correct in PARENTH1 property in Web Admin.

We tried running UJXO_CLEAN_DIM_CACHE, UJA_REFRESH_DIM_CACHE and also checked data/hierarchy issues using UJA_DATA_CHECKER and RSRV tests, but nothing showed up.

The only thing that worked for us was removing the node, processing dimension and adding it back and processing dimension. This fixed most of the "hanging" base members and mid-nodes in that hierarchy.

I am wondering if some one has faced similar problems and if any one else has found a fix for it. So far, I am unable to find any SAP Note or solutions for it. If we run into similar problem again, we would like to understand what could be the cause of this and how to fix/avoid this in future.

Technical details: Close to 50K members in entity dimension.

Versions:

EPM Addin - SP38.0

NW 7.5 SP18

Any help will be appreciated!

Thanks

Abhi

[former_member186338]

May be screenshot?

[abhishekkhatti]

Hi Vadim,

Thanks for your response. We ended up fixing the hierarchy manually, since it was a production system. So getting screenshots would not be possible, unfortunately.

But if it helps, lets say

1. Entity base member 123 has PARENTH1 PC123. It was still showing correctly in Web Admin, but in Excel EPM Context it would be displayed out of the main hierarchy like there is no parent H1.

2. Like that, there were a ton of members shown out of hierarchy.

3. Removing PC123 from PH1, processing, adding it back and processing dimension again. This fixed the display and all the members from the same hierarchy level again were displayed where it should be within hierarchy.

4. We did this for all problem nodes/base members for their respective hiearchy levels.

5. We found that there was a cancelled job while processing the dimension before this problem occurred (screenshot attached of failed job). No short dumps associated with this. In the past we had this "different children" error, but never messed up the master data.

I hope this gives an idea on what went down.

Thanks

Abhi

[vinoogan]

HI akhatti

We are also having same issue. Please let us know how you fixed the issue

hope as Suggested by Vadim this worked fine ?

Thanks

Vinoo

[former_member186338]

vinoogan

Please, write a new question and provide all details!

[former_member186338]

The issues like mentioned may happen if you have multiple hierarchies and you are using the same parent in multiple hierarchies. Always try to avoid this case.