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

Framework manager - Analysis Studio

Started by cognos_users, 23 Oct 2009 03:29:39 PM

Previous topic - Next topic

cognos_users

Hi,

We are in Cognos 8.2. We have many frame work manager relational models and reports created. Now we are planning to build cubes. It is something like this - the data in the models is what we would want to have in each cube. So, my plan was to make a copy of the existing frame work model and convert the query subjects to Regular and Measure dims. Then publish the Dimensionally modelled package to use in Analysis Studio.

Now my question:
1. We have powerplay tool also. But upfront etc is not set up yet. Our goal is to access the cube from Analysis Studio. Please let me know what the best approach is. My manager is interested to have the model for the cube created through transformer rather than utilising the existing framework model. I am confused. Please respond a.s.a.p. Thanks!

DSR

Hi,

You Can use existing model....But better to create a new model for Multidimensional data....with all the levels/hierarchies.

The other better way is creating IQD's in FM by using the existing Model... Then Publishing those IQD's as external files and then using those IQD's as a datasources for your Powerplay transformer for creating the Cube....

I think the second approach will be easy and better to understand and debug...where the first approach is some times difficult to debug your self with the data....

Then after creating your cube ....you can just refresh the Cube as per your business needs....

Regards,
Sanjeev

david.stachon

no...using iqds is not the best approach in Transformer....this is a throw back to the series 7/impromptu days. if you go with PowerPlay cubes, use packages as your datasource.

...and no, you should not create another copy of your FM model. if you want to build a DMR model it should be within the same project and same model as your current relational model. This leverages your current meta-data and can support easy drill through from olap to relational data which is almost always a requirement.