If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Using regular dimension

Started by jive, 23 Jan 2012 08:52:56 AM

Previous topic - Next topic

jive

Hi everyone I hope someone can help me on this one.
I have build a physical and dimensionnal model for one business subject. Now  I have to add an other business subject, to shorter production time I want to reused already made dimension like time dimension, an some other. Is it possible to do that, if yes can someone point in the right documentation to realize that task.  I tried to find it but without succes.

My problem is if I reused the time dimension I saw information common to both business subject, one business subject strat in 1996 and the other 2008, when I do report I just saw information starting in 2008. I think somewhere I can make re-assing the time dimension to or a copy of the time dimension, and used it in the new business subject, but without succes .

Thanks for your help  :'(

blom0344

In case of a time dimension: In the model the regular dimension should be based on , say, a time table used as dimension table. There is NO point in having 2 regular time dimensions based on the SAME table.  If you model requires multiple subjects based on the time table then you should create alias subjects for them.

However, it is certainly possible to define multiple hierarchies within the 1 regular dimension that refer to different query subjects. This can be true for multifact models that have multiple paths based on different date keys in the fact.

Example: If the fact sales stores order_date and ship_date as keys, then it is possible to use 2 alias subjects against the time table and use these as seperate hierarchies in the regular time dimension. For analysis you would then use 1 out of the 2 hierarchies thereby triggering different query paths..

So , the answer will be in how you need to design the model. I have no clue - from your post - what you intend to build..

jive

HI bloom,

The problem where facing is we want to reused the dimension, to avoid diffenrent terminology and redoing the job again. The first sub model we do got 120 dimension is already validate and conform to the business lexicon. The model will have 20 sub business related item,  each one with a least 3 fact table and around 10 to 20, each sub will have is business related dimension, applicable only on that sub , plus the dimension presentation already done in previous sub. We also want all of them to be stand alone, because if the user ask for modification in one sub we don't want to impact the other. At the end of this project  everything will be connect with only 4 dimensions presents in every sub-model as: Organisation sturcture, time, employee name and file numerotation .

The solution we choose:
     Reimport the source in the current sub.
     Remap the already done dimension.
     That's mean we copy from previous presentation layer an definition, remove link to the old measure and reconnect it to the current fact table and source.

This solution is the best we can find because all new model have at least 70% of there dimension already in place in the first sub, it's fast, accurate and the user will see the same presentation accross all the sub. The other reason to do that is the granularity beteween sub is different and related to the conform dimension in different cardinality the user need for there reports.

And as you say earlier the time, organisation structure and employee are all conform dimension so we only have alias in all sub model with the exact same cardinality each time.

At that point we already have 12 of the 20 sub done, we only add 30 new dimensions, everything work fine and fast. The time to define new sub in FM is really fast less then 4 hours to be exact. The validation process is also fast, because the user only validate prsentation for the new dimension apply only on one sub.

Thanks for your help.

Lynn


MFGF

Quote from: Lynn on 13 Feb 2012 12:45:47 PM
Blom, not bloom

Hee hee hee - this is truly priceless! :) Right now I bet Ties is simmering nicely :)


Snet form my fumblefingers
iPhon 5 usig Tapatalk
Meep!

MFGF

Quote from: Lynn on 13 Feb 2012 12:45:47 PM
Blom, not bloom

Hee hee hee - this is truly priceless! :) Right now I bet Ties is simmering nicely :)


Snet form my fumblefingers
iPhon 5 usig Tapatalk
Meep!