This content has been marked as final. Show 9 replies
Have you set the content tab with proper levels?1 person found this helpful
By any chance did you check the physical query?
Edited by: Srini VEERAVALLI on Dec 6, 2012 11:55 AM
Hi user,1 person found this helpful
Have you set content tab at each logical table in Bmm layer?
You'll were right, I hadn't set the content tab in the logical tables. However, on doing that the hierarchy runs perfectly from Date --> All the fields of Account. At the end of Account, on adding a field from Instrument, I again lose all the values from Rate Shocks.
Answer is same check content tab for levels.. if it doesn't work let us know with more details with data.
Appreciate if you mark when given info helpful.
I made two Hierarchies
1) Date --> All the Account fields
2) Grand Total --> Instrument (primary key Instrument ID )
On adding the Instrument underneath the Account fields in the first Hierarchies, I would lose the Rate Shocks on the very first macro view of the report itself..by adding the other Hierarchy, everything works fine, values are seen until the last field of the Account field, until I drill down further from there to Instrument, where it shows the IDs but no Rate Shocks..
I thought by connecting the two hierarchies, the data would still be available.
hmm need to know more about 'Rate Shocks' like is it level base or what granularity?
Did you see the physical query to know what (GROUP clause) is causing?
If possible can you send me email with screenshot?
Well Rate Shocks is not part of the hierarchy at all. It is a fact table having all the metrics defined within itself. All I would want is at each granular level of the Account, Instrument and Position, the metrics of Rate Shocks are visible.
For this purpose, should the metrics also be part of the hierarchy? But they do show for all the granular levels above the Instrument ID..
Make sure you have content levels set Account, Instrument and Position to the fact table.1 person found this helpful
Just in case check the Implicit fact column mapping( on Subject area properties) to make sure its not pointing to any other fact table.
If still you see same issue then I need to see the rpd ;)
I did set the Source of the fact tables to the two Hierarchies..still no results at the most granular level.
Its not allowing me to set the source of the Instrument table by giving an error that it is pointing to multiple dimensions..