Skip to Content
author's profile photo Former Member
Former Member

Universe design + hierarchically organised table

Hi,

I have in my database a table for categories, this table contains 3 level of categories, parent categories (level 0), sub categories (level 1) and child categories (level 2). Each category has an ID, a level, a name and a parent ID.

In terms of universe design (data foundation and business layer) I have no idea how to approach this...

I have another table containing metrics for each of the categories per day, the 2 tables link via the category ID, but ideally, I should be able to create a query, specify that I only want to see parent categories, or sub categories, or child categories, specify dates and all the aggregations should for automagic...

In the data foundation, should I have my category table only 1 time with a join to itself? Or should I use aliases?

In the business layer, should I create 1 dimension for each type of category? Or only 1 dimension and somehow later specify the level?

If anyone has any example it would be greatly appreciated!

Thanks!

Seb 😊

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Dec 06, 2012 at 12:29 PM

    You may want to look at the sample universe below where the sales organization hierarchy has been designed using aliases in the data foundation.

    http://scn.sap.com/docs/DOC-22145

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 06, 2012 at 11:51 AM

    Hi,

    What are you trying to achieve? Modelling a hierarchical relationship between the category levels?

    That would be done in the custom hierarchy editor - please search the appliction's help files for "

    About navigation paths for objects"

    Regards,

    H

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.