cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Datasphere: Analytic Model - Level Hierarchy issue

Cal_Loudon
Participant
0 Likes
3,273

Hi experts,

I'm wondering if anyone has any experience or guidance around Level Based Hierarchies within Datasphere - specifically for consumption within an Analytic Model.

I'm aware of how to create a level hierarchy within the Data Builder - Table screen - but accessing the hierarchy post association in my Analytic Model gives me the below error:
The query executed with errors. Caught exception : exception 42201: Column not found : aSrcName=, ([Column country/!EMPTY (unknown0.0.0) Aggregation: 0]) in view

Is there a way to create and use Level Hierarchies in a graphical / SQL view? I can get parent child hierarchies working fine this way but they won't work for my scenario.

I tried to get creative with the below approach but that gave an even bigger error:

Any suggestions would be appreciated.

Thanks all!

Cal

View Entire Topic
MKreitlein
Active Contributor

Hello Calladyn,

regarding the Level-based hierarchy... I did it for example in the material dimension. (sorry, for the German description):

What happens here is that we load the material master via CDS view I_PRODUCT.There you have one field for the Product hierarchy (String 18), we split this up into 5 different levels PH1 to PH5 and then we built in the Dimension view this level based hierarchy, where we sort the 6 fields, the 5 levels plus the material number as lowest field.In that dimension, we associate the product hierarchy texts to each PHx field, so that all levels have a text.This Dimension is associated to the transactional data field, to the material number, and then you have the hierarchy available in the Analytic Model.Hope this description helps?!BR, Martin
Cal_Loudon
Participant

Vielen dank Martin! With your explanation I think I understood what I was doing wrong and how I needed to fix things. In my simple example, it looks the error was creating the hierarchy on the texts rather than the hierarchy IDs themselves. Rookie mistake!

By fixing this and doing the correct text associations, I was able to get the hierarchy working nicely.

Thanks again.

Cal