SSM7.5 - Dimension with Multiple Hierarchies

Hi all,
I'm facing here one problem in the SSM front-end when I'm trying to use one the possibilities that PAS database offers, in this case the use of a dimension with multiple hierarchies.
As you can see in this image, the dimension is created in PAS and works without problems in the dataview.
Hierarchy one:
[http://img121.imageshack.us/img121/334/pas1y.jpg]
Hierarchy two:
[http://img831.imageshack.us/img831/2586/pas2.jpg]
In the SSM front-end, when I try to use that dimension, by default appears the first hierarchy:
[http://img826.imageshack.us/img826/4043/hier3.jpg]
In the dimensional selector the dimension appears fine for the first hierarchy:
[http://img30.imageshack.us/img30/3103/hier1.jpg]
But when I select the second hierarchy...
[http://img34.imageshack.us/img34/1722/hier2.jpg]
The Internet Explorer crashes and close all the open windows. This happens in the scorecard and also in the reports.
Is not possible to use dimensions with multiple hierarchies in SSM? Did anyone had this problem before?
Thanks in advance
Pedro
Edited by: Pedro S. Costa on Sep 13, 2010 11:03 AM

Hi Shashi,
first of all, thanks for your answer.
But I don't understand when you say that "we cannot have two hierarchies on the same dimensions"?!?!?
I already have some years of experience with PAS database and it's not the first time I create a dimension with more than one hierarchy. I use also that in a productive system (before this SSM front-end) without problems. And in this latest version of PAS (version 7.5.6) it's still possible to use that feature. As you can see in my initial post, I put two screen shots of the dimension with two hierarchies in PAS dataview, and works fine, without problems in the drill-down/up.
From PAS online help:
HIERARCHY is a Dimension command that defines the members and levels that comprise a particular hierarchy level within a dimension. It also allows multiple consolidation structures that stem from a central root of inputs. Use hierarchies when the input members are consolidated into more than one output member. When a dimension has hierarchies, members can have more than one path for rolling up into output levels. If a dimension has only one hierarchy, no HIERARCHY statement is necessary.
Based on this, I create my example of a dimension (named MULTI) with two hierarchies (REGION and TYPE). Maybe the name I use for the second hierarchy create some confusion to you, because of the TYPE dimension that can exist in SSM. I just hope the problem I'm having in the SSM front-end is not related with the name I used for the second hierarchy!!!!
I will rename that and test again.
Regards
Pedro

Similar Messages

Dimension Design - Single Dimension with Multiple Hierarchies

Morning,
the purpose of this discussion is to understand how we should design a specific dimension with 3 levels and multiple hierarchies for optimal performance.
We have an institution dimension with the following characteristics:
Characteristics
Dimension: Institution
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
Hierarchies:
1. Some of the hierarchies have 3 levels and others have only 2 levels (Skip Level)
2. ALL the hierarchies have a TB level and an Institution level
3. None of the hierarchies have the same leafs
4. Some of the hierarchies leafs can overlap
Design:
We are considering two approaches for the institution dimension levels:
a)
Levels:
Hierarchy 1 TB Level
Hierarchy 1 PG Level
Hierarchy 1 Inst Level
Hierarchy 2 TB Level
Hierarchy 2 Inst Level
Hierarchy 3 TB Level
Hierarchy 3 Inst Level
Note:
This approach is working and the resulting dimension and cubes are used by OBIEE, but some of the OBIEE analysis takes a long time (more than a minute) to return the results.
At this point, we are not sure whether this approach will result in an optimal design from a performance perspective and are looking at restructuring the dimension to represent only the three conceptual levels as indicated below.
b)
Levels:
1. Total Bank (TB) Level
2. Peer Group (PG) Level
3. Institution Level
The rest of the dimension i.e. hierarchies, attributes and mappings are defined in the same way.
The cube associated with this dimension have approximately 80 million records.
Please advise on any best practices or design considerations that we need to take into account.
Thanks

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

OBIEE Parent-Child Dimension with multiple hierarchies

Is it possible to have in a parent-child dimension multiple hierarchies? I want to have the same botom childs to aggregate to different parrents. example.
Account Dimension
HR1-total
HR1-parrent1
CHILD1
HR1-parrent2
CHILD2
HR2-total
HR2-parrent1
CHILD1
CHILD2
Thanks in advance.

No, it is not possible to have multiple hiearchies in a PC logical dimension.
The concept of the Parent-Child (PC) hierarchy is completely different from the level-based hierarchy. Specifically the PC hierarchy expects a predefined / architected table with corresponding PC column/value structuring with or without attributes.
Short story even shorter it is not possible.
Longer...
In the RPD the BMM actually prevents you from adding a new logical level, child level, or parent level when you have selected that the logical dimension be a parent child logical dimension with Parent-Child hierarchy.
On another note...
Have you tried architecting/building your PC source table so that it represents the roll-up and bottom child-levels like you are seeking? That is, that same member in the child column more than once having a separate parent value. That should be doable.
That was a great question, please award points if this answered your question or it was helpful.
Cheers,
Christian
http://www.artofbi.com

Formulas in account dimension with multiple hierarchies

Hello all,
I am having troubles with finding the exact syntax for a formula in an account dimension that has two hierarchies:
- I have two parent accounts in H1 (accountA and accountB)
- I have one account in H2 that has to add up accountA and accountB
It was easy in V4, the formula would just say: accountA+accountB
Does anyone have the exact syntax for me in V5?
Some extra info:
- SAP BPC version: 5.1sp2
- SQL 2005
- I know that dimension formulas have a problem with performance, but believe me, in this case this, it is the only way
Hope someone can help me,
Alwin

Alwin,
There should be formulas in the MDXlib.lgl that look like the following examples:
*Function Hir1_P(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H1.currentMember,"+"))
*endfunction
*Function Hir2_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, rollupchildren(AccountL.H2.currentMember,"+"))
*endfunction
*Function Hir3_P(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, rollupchildren(AccountL.H3.currentMember,"+"))
*endfunction
*Function Hir1(%Arg%)
     iif(AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%,Null)
*endfunction
*Function Hir2(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H3.CurrentMember is [AccountL].[H3].[All AccountL.H3],%Arg%, Null)
*endfunction
*Function Hir3(%Arg%)
     iif(AccountL.H1.CurrentMember is [AccountL].[H1].[All AccountL.H1] and AccountL.H2.CurrentMember is [AccountL].[H2].[All AccountL.H2],%Arg%, Null)
*endfunction
These are functions that may be used to aggregate the values in version 5 across hierarchies. I don't think you need them all, but I included the set I have in a current application.
I hope this helps.
Petar

Using HLEVEL Property with Multiple Hierarchies

Hello,
I am trying to use the HLEVEL property on a dimension to indent the rows different amounts. Easy stuff, except I'm doing a row expansion on hierarchy 3 (H3). Using EVPRO(AppName, MemberID, "HLEVEL") always returns the HLEVEL from H1. If you select the same member ID in the member selector under different hierarchies and click the Properties button you can see a different value for HLEVEL, but I can't figure out how to get that in a report using EVPRO.
Is there a way to tell EVPRO specifically which hierarchy to use when returning the value for HLEVEL?
Thanks!
Paul Petersen
Akili

Mike,
please check the answer in this other post:
EVPRO with multiple hierarchies
It's for the MS platform, but it's the same for Netweaver.
EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
Regards,
Simmaco

Bug in Aggregate Persistence Wizard with multiple hierarchies

Hi,
Let's say you have a dimension with 2 hierarchies. In example:
product -> subcategory -> category -> all products
product -> subtype -> type -> all products
Then you run the "Aggregate Persistence Wizard" and generate the code for 2 aggregations, one for each hierarchy.
Then you execute the generated code wiithout errors.
But no aggregate fact table is created, not inside the rpd, neither in the database.
You only found the aggregated dimension tables (both in rpd and database), which btw generate consistency check errors due to the missing fact table.
Workaround:
The code generated by the Persistence Wizard contains a single "create aggregates" statement.
Multiple aggregation are separated by commas inside the same statement.
Instead create multiple "create aggregates" commands, one for each aggregation, each separated by a semicolon.
OBIEE 11.1.1.5
Hope it helps,
Corrado

Cosimo,
If you've built your business model correctly with the complex joins and the dimensions relating to your fact, then the wizard will pick them up normally and will allow you to generate a script like this:
prepare aggregates
"ag_Fact_Budget"
for "Core"."Fact - Budget"("Budget Amount")
at levels ("Core"."Conformed Date"."Fiscal Year")
using connection pool "Siebel Data Warehouse"."Data Warehouse Connection Pool"
in "Siebel Data Warehouse"."Catalog";
Check that your BM is consistent and sound (stars in physical and BM layer built right).
Documentation-wise, refer to the Oracle Business Intelligence Server Administration Guide Version 10.1.3.2, page 189 f. or the Server Architect course, module 9 "Using Aggregates".

ASO Time balancing with multiple hierarchies

Hello,
I have an Essbase 9.3 ASO cube with multiple hierarchies in the period dimension (set as type = Time), and I'm trying to set one of my Measures to Time Balance Last with SkipMissing.
When I validate the outline, I get:
"This prototype must have all its shared members as siblings of previous sibling."
on all the leaf level members in my period dimension.
any ideas?

We are on Essbase 9.3.0.1 and also tried to use ASO Time balance functions in conjunction with multiple hierarchies enabled.
I recommend you not to use the ASO time balance functions. We did and had to revert everything after complaints from our user base.
If you still use it, please test cases where you retrieve TB Last as well as flow values together with ytd and periodic values.

Using HLEVEL with multiple hierarchies

Hi all,
Is there a way to pass a parameter to the HLEVEL keyword to specifiy which hierarchy (Parent H1,H2, H3, etc.) to use when pulling the HLEVEL?
We would like to use HLEVEL for report formatting however we need the ability to choose the hiearchy.
Thanks!
Mike

Mike,
please check the answer in this other post:
EVPRO with multiple hierarchies
It's for the MS platform, but it's the same for Netweaver.
EVPRO can only retrieve the HLEVEL for the first hierarchy. You need to maintain further custom properties if you want to get the level of a member within multiple hierarchies.
Regards,
Simmaco

Logic Doubling in v7 SQL - Dimension with 3 hierarchies

I'm having a problem with logic doubling at a client where I have a dimension with 3 hierarchies in v7 SQL 2008. When I try to run logic off a property in this dimension, base members in all 3 hierarchies are doubling, whereas base members in only two hierarchies are not. I've tried using *Membersets, *Select, and *XDIM_Memberset statements to stop the values from doubling, but I'm not having success.
Any ideas? Has anyone else seen this?
Thank you,
Grant

Yes, sorry, I've been busy.
Basically, I had two rollups of data in one dimension, and when I was trying to reconcile the logic push that consolidated all the data from this dimension into one member, I was only looking at one of the rollups, and not the other one. So, it was really just a matter of writing logic and running it without taking into account all the data I was manipulating.
Thanks,
Grant

Dimension with 2 Hierarchies, Lowest Member w/ Different Long Descriptions

I'm trying to create a dimension that would allow Discoverer For OLAP users to choose between different LONG DESCRIPTIONs, and I am trying to accomplish this by using multiple hierarchies.
For example, when a user is trying to create a report and eventually stumbles upon the Dimensions part of the Workbook creation, he can choose a different description other than the default by choosing from the Hierarchy drop down list.
The following is the dimension details:
Dimension: TEST_DIM
Hierarchy #1: HIER_NAME
Levels: TOTAL_DIM_NAME
        TEST_LVL_NAME
Hierarchy #2: HIER_CODE
Levels: TOTAL_DIM_CODE
        TEST_LVL_CODE
Dimension View: V_TEST_DIM
Fields: TOTAL_DIMENSION_NAME_ID   ---mapped to--> TOTAL_DIM_NAME
        TOTAL_DIMENSION_NAME_DESC ---mapped to--> TOTAL_DIM_NAME_LONG_DESCRIPTION
        NAME_LEVEL_ID             ---mapped to--> TEST_LVL_NAME
        NAME_LEVEL_DESC           ---mapped to--> TEST_LVL_NAME_LONG_DESCRIPTION
        TOTAL_DIMENSION_CODE_ID   ---mapped to--> TOTAL_DIM_CODE
        TOTAL_DIMENSION_CODE_DESC ---mapped to--> TOTAL_DIM_CODE_LONG_DESCRIPTION
        CODE_LEVEL_ID             ---mapped to--> TEST_LVL_CODE
        CODE_LEVEL_DESC           ---mapped to--> TEST_LVL_CODE_LONG_DESCRIPTION
Cube: TEST_CUBE
Measure: TEST_MEASURE
-----------------------------------------------------------------------------------------With the above dimension having 2 hierarchies, Discoverer users can choose between HIER_NAME or HIER_CODE. The problem with this setup is that for this to work, different fields must be mapped to the lowest levels of each hierarchy, because the values of NAME_LEVEL_ID and CODE_LEVEL_ID fields from the V_TEST_DIM dimension view are different from each other, even though they share the same set of records, which means they can be considered as one.
The values of NAME_LEVEL_ID and CODE_LEVEL_ID must be different, because if they are not, I receive the following error during maintenance:
***Error Occured: Data for at least One of the Hierarchies for TEST_DIM.DIMENSION controdicts the Definition of such Hierarchy as Level
Based.After making the NAME_LEVEL_ID and CODE_LEVEL_ID values different from each other, I tried mapping the fact table to the cube. Mapping details are as follows:
Cube View: V_TEST_CUBE
Fields: TEST_VALUE       --mapped to--> TEST_MEASURE
        NAME_LEVEL_ID    --mapped to--> TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID
     CODE_LEVEL_ID    --mapped to--> TEST_DIM.TEST_LVL_CODE.CODE_LEVEL_ID
-----------------------------------------------------------------------------------------Unfortunately, the above mappings does not work, because I get the following error when I do so:
Invalid Mapping:
Levels in a dimension TEST_DIM have to be mapped to the same column for summary fact_tableBut despite the error(s) above, I've actually made this work, by leaving the one ID field (NAME_LEVEL_ID or CODE_LEVEL_ID) unmapped. Say, I map NAME_LEVEL_ID to TEST_DIM.TEST_LVL_NAME.NAME_LEVEL_ID but leave CODE_LEVEL_ID unmapped, then maintain to load data for TEST_DIM (HIER_NAME hierarchy). Then I unmap NAME_LEVEL_ID and map CODE_LEVEL_ID. I maintain the cube again to load data for the other hierarchy which is HIER_CODE.
Now, if that works, why won't AWM let me map NAME_LEVEL_ID and CODE_LEVEL_ID at the same time?
I tried running the following DML command to manually map the fields:
call set_measure_key_expression('TEST_CUBE.MAPGROUP1.CUBEMAPGROUP',NA,'TEST_DIM.HIER_NAME.LEVEL\nTEST_DIM.HIER_CODE.LEVEL','VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID',FALSE)I checked the mappings afterwards and the two fields are indeed mapped, but when I try to maintain, I got an error stating that 'VIEW_OWNER.V_TEST_DIM.NAME_LEVEL_ID\nVIEW_OWNER.V_TEST_DIM.CODE_LEVEL_ID' does not exits or something like that.
Does any know a better way to implement this?
Please help.

I understand what you are trying to achieve, and technically it should be possible. In practice, however, Disco caches dimensional information as it is not expecting information such as descriptions to change from one query to the next.
The complication is the description objects do not have any additional dimensionality beyond their base dimension, however, there is a language dimension that might be useful in this case. If you created an additional language with a formula that calls a program to set the underlying AWM language dimension you could assign this measure to the first worksheet in your workbook and allow users to swap between different versions of their long descriptions. However, this would be a session wide setting and not worksheet specific.
In the AWM tree you will need to add additional languages to your AW which can then be used a placeholders for your different descriptions. This will affect all your dimensions so you will need to either use OLAP DML to copy the base language descriptions to all the other languages or using the mapping editor.
In the dimension mapping tool you will now see multiple entry points for descriptions - English, French, German etc depending on which languages you picked. You can assign any column from your source view/table to these columns.
Should work - I did something similar for another customer. It is not ideal, and does require the users to open/create a worksheet to switch the descriptions but it was all I could think of at the time.
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Does that make sense?

Dimensions with multiple joins

Hi,
Discoverer Desktop 9.0.2
Discoverer Administrator 9.0.2
OWB 9.2
I have imported the dimensions and facts from OWB EEX file.
While I trying to create a report based on the dimensions, I found the problem in Dimensions used multiple times against the fact table.
For example,
I use the Time Dimension (TIME_DIM) for assigned date, open Date and Close dt. My fact table will have the foreign keys for these 3 columns.
TIME_DIM
DAY_ID
DAY_DAY
DAY_MONTH
DAY_YEAR
data
DAY_ID DAY_DAY DAY_MONTH DAY_YEAR
1 01-JAN-04 JANUARY 2004
2 01-FEB-04 FEBRUARY 2004
3 01-MAR-04 MARCH 2004
FACT_TABLE
DAY_ID
DAY_ID2
DAY_ID3
Data
DAY_ID DAY_ID2 DAY_ID3
1 2 3
1 1 2
While I am creating the report, in 'work book wizard: step 2' shows the TIME_DIM only one time, also it allows to select only one time with any one of these keys. Whereas I need to select the time dimension for each of the time keys in fact table.
Is their any work around to get these values in my reports?
I mean
My report will look like,
ASSIGNED DT OPEN DT CLOSE DT
01-JAN-04 01-FEB-04 01-MAR-04
01-JAN-04 01-JAN-04 01-FEB-04
I tried with creating hierarchies, modifying the SQL to add these keys manually and then import SQL, doesnt work at all.
Please help me !!
Thanks,
Shree

You have to load the table up several times into the EUL and create links to the different column in your fact table.

Drill with multiple Hierarchies

Hi,
I have defined multiple hierarchies in an OLAP universe (like state>region>customer>product or state>region>customer segmentation>Product or state>region>product ...) in order to use the drill functionnality in webi.
In our scenario, each webi report should use only one hierarchy and we don't want the user to have the choice between the different hierarchies when he drills down. So is there a way to define in a webi report what hierarchy should be used?
Thanks,
Gabriel

hi,
As 'State' object is the starting point for both the Hierarchies,
Please duplicate the state object and place it in other class. (as two objects with same name shouldn't exist in same class)
Now edit the second hierarchy such that new State Object will be the starting point.
Also , please ensure that 2nd WEBI report uses new State Object in Query Pane.
This will prevent 1st hierarchy in 2nd webi report.
I tried this out and it's working.
Regards,
Vamsee

Custom Dimension with multiple children defined as "Never Share"

Hyperion Planning - 11.1.1.3
There is Custom dimension "Appliance" with root defined as a "Never Share". It has multiple level 0 (SubAppl1, SubAppl2, SubAppl3 etc) members with "Store". Data is some times loaded at root level and some times at the lower levels and at times both. What is the expected result?
When POV is Appliance and when it is drilled down?
For Ex:
For Jan -
Appliance is 100, No other members loaded with data.
For Feb -
Appliance is 30
SubAppl1 is 10
SubAppl2 is 10
SubAppl3 is 5
POV
Appliance Jan - 100
Appliance Feb - 30 or 25? and why?
Trying to understand the behavior or "Never share" in this scenario.
Appreciate your feedback.
Edited by: 847514 on Mar 28, 2011 11:17 AM

Never Share has no bearing on your sample. The Never Share flag is to prevent a implicit sharing which will happen when you have one parent with a single child under it. Your structure is not setup such that an implicit share would occur based on your example.
I really do not recommend loading data at upper level members as this means you can never run a normal aggregation on your data. If you were to aggregate your data and you happened to have the AGGMISSG set to true you would see the data in your january example of 100 was removed due to the level 0 members not having any values.
So the question of your February being 30 or 25 is did you load 30 to February Appliance or did you load to the level 0 and then aggregate?
Regards,
John A. Booth
http://www.metavero.com

BW Universe with multiple hierarchies issue

Hi,
We created an OLAP universe off a BW BEx query that has 2 hierarchies enabled. Hierarchy 1 is 12 levels deep while Hierarchy 2 is only 5 levels. Level 00 was also generated for better hierarchy reporting. In Web Intelligence reporting, Hierarchy 1 is required to report starting on Level 4 and then drill as needed so L00, L01, L02, L03, L04 was included in the report. Hierarchy 2 is for grouping and only L00, L01 was included in the report along with key figures. This Web Intelligence result set works fine [Hierarchy 1: L00, L01, L02, L03, L04] , [Hierarchy 2: L00, L01] , measures/key figures.
If additional levels of Hierarchy 1 is added, at L06 and beyond, the query suddenly returns message "No Data to Fetch". In BEx, it was confirmed the query does run with the exact same drilldowns as Web Intelligence and it works in BEx. If Hierarchy 2 is removed from Web Intelligence, the report also can successfully fetch up to the lower levels up to L09. If other flat objects are added, the Web Intelligence report still works fine, it seems to get "No Data to Fetch" when Hierarchy 2 is added. Any information would be appreciated, thank you.
Issue: Web Intelligence report with two BW hierarchies gets "No Data to fetch" if Hierarchy 1 goes lower than L06.
Observations:
1) There are some empty nodes starting in Hierarchy 1 L06, but the Hierarchy 1 works fine by itself
2) The BEx and Universe has a hierarchy node variable prompt. We filtered at lower hierarchy nodes, levels where there is data, but it still does not work with Hierarchy 2
Environment:
- BOE XI 3.1 SP2
- SAP BI 7
- BEx query (2 hierarchies), OLAP universe, Web Intelligence

Please refer to: the below document page# 43. Hope this helps!
http://help.sap.com/businessobject/product_guides/boexir31/en/xi3-1_sap_olap_universes_en.pdf

Dimension with multiple leafs

Hello,
We want to set up the following hierarchy:
--- OXN
....|--- POT
....|....\--- RST
....|
....\--- OIN
.........\--- PJT
..............\--- RST
So this means OXN has 2 child levels (POT&OIN)
and RST has 2 parent levels (PJT&POT)
Now when we make this we get the following warning in the consistency checker:
Warning: [38073] Dimension "<dimension_name> has multiple leaf levels which are not identical
Does anybody know how we can solve this?
Thanx in advance,
Remc0

I'd really like to know what causes this error to occur in the first place.
For me I sat down to construct a time dimension.
Single source table. Single drill path...
Added year... Fine.
Added Month... Fine
Added Week... Fine.
Added Day... Failed???
Exactly the same process for Day as for week, month and year but for day I get the error.
If I knew what criteria was being used to identify the error then i could figure out how to get around it but at the moment it almost looks like a bug( in this circumstance).

SSM7.5 - Dimension with Multiple Hierarchies

Similar Messages

Maybe you are looking for