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

Modeling for navigational attributes

The current modeling that we are working on has the 0DOC_NUMBER to have the nav atributes order reason and purchase order type of the 0DOC_NUMBER. The 0DOC_NUMBER is defined in the DSO.

Should these nav attributes be converted to be part of the transaciton data or left as is?

Will the conversion from the master data to transaciton data be a probelm with the modeling based on the limited dimensions.

We have already 13 dimensions.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 19, 2007 at 08:48 PM

    you can leave the attributes as it is, it should not be a problem.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      If you already have Nav. Attr. in the ODS (DSO) , its better to keep it as is.

      You can convince customer that there is no need to put it in transaction data.

      Only if the query performance is affecting due to these nav. attr. that you can think of converting those to characteristics (part of Trans. data).

      Any way if you have to convert it, that should not be a problem. But you have to delete and reload complete data for this.

      Regards

      SSS

  • author's profile photo Former Member
    Former Member
    Posted on Oct 20, 2007 at 11:25 AM

    You should convert this to transaction data

    Every sales document will be having one order reason field and associated purchase document number.It is very much part of transaction data and leaving as it is not the best approach

    You can include this order reason and purchase document type field in the transaction data and put them in same dimension as Sales document

    Further , you have settings for high cardinality also available in the cube

    Each dimension table can have maximum of 248 characteristics ( for your information )

    Message was edited by:

    SDBI

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 21, 2007 at 07:46 AM

    Hi,

    An important consideration for deciding this should be whether you require the history of attribute value changes over time. A track of changes would not be available if it is part of master data but would be available if it is part of transaction data.

    Mathew.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2007 at 05:09 AM

    u dont have to cconvert the nav attr into transaction data.when u running the query it the data cames from source system to cube at the time of running the query. so u need not assign the dimension for the navigational attr.

    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.