Report fetching data from staging table

[Dineshpullagura]

Hello,

I have a cube built on top of a view (V1) (which runs on top of another view (V2)) from which report is fetching data.

My report which is supposed to fetch data from V1 is getting data from the staging view V2. So, i replaced my view V1 with a table and the report is working as expected.

Is something wrong with using multiple views. Please share your ideas on why the report is fetching data from the staging table instead of the source when it is used as a view. 

Thanks for your time

[bdbits]

If the views work in your native query tool, they should generally work in Cognos.

What kind of cube? Where are you looking that is telling you where the data is coming from?

[Dineshpullagura]

Hi,

Thanks for the reply..

The view is working in the native query tool. I am able to query it and see the expected results.

I built a Cognos dynamic cube on top of the view. The view (V1) on which the cube is built is getting a subset of data from another view (V2). I am checking the result in cognos report studio using a list. In the list, i am getting data from view (V2) where as i am supposed to get data from view (V1).

Please let me know if you need any additional detail.

Thanks

[gpollock]

You're checking the work in a list right?  Does this mean you're using a Framework Manager package?  If so, does FM know about V1 and V2?  Check some samples in FM to see how it's getting from A to B.  Cognos will sometimes be helpful and re-do its SQL based on what it knows.  So if Cognos knows V1 is built on V2, it might try to skip V1 altogether for distincts and aggregates.  In most cases, it can be a benefit.

[Dineshpullagura]

Hi,

The framework manager package contains different cubes, and the cube i am referring to is built on V1. I am not sure whether cognos know about V2. Except the fact that V1 is built on V2, V2 is not used anywhere. If there's a way that cognos is referring to V2, is there a way that i can make it not refer to V2.

Thanks