Rebuilding imported model results in error regarding [#NotInHierachies#]

[chaznosterous]

Hi experts,

While working with a simple excel file as data for an imported model, I have come across a scenario where I am getting the following error:

The error above means the Account dimension no longer has any measures attached.

I can reproduce error by repeating the following steps:

1. Create new model with excel data as source.

2. Create a calculation in the "Calculations" workspace and save the model.

3. Press Rebuild Model in the "Model Structure" workspace.

4. Press Rebuild Model again once the data wrangler window appears and the above error appears.

Have I completely missed this as being a restriction on model design? I found the following note: https://userapps.support.sap.com/sap/support/knowledge/en/2986333, but did not find it fitting to this scenario.

Our tenant is on version 2022.8.14.

Best regards

Rasmus

[Susanne_Helbig]

Dear rasmus.koldt.olesen,

there is an option to create the member 'Not in Hierarchies' automatically, there is no need to create that manually.
Access the dimension and in the 'Dimension Details' panel in 'Hierarchies' section you should see the following option, switching this option on should solve your issue.

Best regards
Susanne

[chaznosterous]

Hi Susanne,

Interesting, I do not have that option at all, below are examples of my account dimension and another dimension:

Could this be a role issue?

Regardless, surely this is not working as intended? Am I the only one experiencing this behavior in SAC?

BR

Rasmus

[Susanne_Helbig]

Hi chaznosterous,

this is what I found in the Help Portal regarding hierarchies and the 'Not in hierarchies' switch
Parent-child hierarchies with not-in-hierarchy member
I also did a quick test and I don't see this option when creating a dimension of type 'Account', only when creating a dimension of type 'Generic', when adding a hierarchy the switch automatically appears.

Best regards

Susanne

[N1kh1l]

Rasmus,

Today while working in my Account dimension I found this member and remembered your question. Try adding the member like below. Not sure if this will solve your issue.

-Nikhil

[Martin_Barth]

Hello to all of you in this thread!

Did anybody find a solution to this problem or is there already an incident in the knowledge base (I could not finde anything)?

Because we are facing a similar problem sometimes, when rebuilding import models based on imports from an SQL - database. We also get the #NotInHierachies# error sometimes at the end of the rebuilding process although there is no hierarchy activated in the models.
And with this error the process of rebuilding obviously does not end properly and all the accounts are gone then in the model... and obviously the model is crashed then and you have to build it again from the scratch.

Thanks a lot and best regards,
Martin

[N1kh1l]

Rasmus,

Just try adding a new property to any dimension or adding a new dimension to the model. That will force a rebuild from SAC side to the model. If still throws an error, I would suggest you to raise an incident with SAP.

Nikhil

[chaznosterous]

Hi Nikhil,

I tried this aswell, but either I am doing it wrong or it is just not working.

I think this will end up being an incident, thanks for your effort and feedback.

BR

Rasmus

[N1kh1l]

Rasmus,

You did it right. Just check if all dimensions in your model do have "Not in Hierarchy" member. If not try adding it. The error just says its missing but does not say which dimension.

Regards

Nikhil

[chaznosterous]

Hi Nikhil,

I tried to add it to all dimensions, with both "Not In Hierarchies" & "Not In Hierarchy" as id and description, but the error persists.

BR

Rasmus

[N1kh1l]

Rasmus,

Try adding the below to your account dimension and try again.

Regards

Nikhil

[chaznosterous]

Hi Nikhil,

Can you elaborate on where you add those values? I clicked on "Account" in the Model Structure workspace, but get the following window:

I tried to type in your solution in this window, but this did not fix the error, I suspect this is not the correct window to implement your solution (which still raises the question, why the error appears in the first place).

Thanks in advance

Rasmus