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

Similar Messages

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

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

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?

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

OWB10gR2 - Cube with relations to a dimension with more than one hierarchy

Hi,
I have defined a time dimension with two hierarchies. The standard hierarchy with the levels year-> month-> day,
and a week hierarchy with the levels year-> week-> day.
When I define the cube i choose dim_time on the dimension tab of the cube and select the level day for that dimension since this is the lowest level of both hierarchies.
When I validate the cube I get the following error Message: VLD-0398: In the Cube test_cube, the dimension DIM_TIME has 2 hierarchies but Cube does not have reference to all lowest levels of these hierarchies.
Validation details: The Cube should refer to a leaf levels of all multiple hierarchies of the Dimension.
Do I have to add the dimension to the cube several times? or is it maybe another way to fix this? To me it seems a bit messy to add a dimension for each hierarchy.
And just as a comment, Yes i know OWB now has a time dimension wizard but I have chosen not to use this at the moment.. ;)
Regards Ragnar

Hi, i assume this logic is for Dimension formula?
If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
in FORMULAH1
[Account.H1].[Account_A] / [Account.H1].[Account_B]

Dimension with Level Dased Hierarchy

Hi everyone
I have one table in bussines model called items with columns item_code,item_descr,item_brand,item_category.
I also have a Dimension with Level Dased Hierarchy set as total_level,item_brand,item_category,item_code.
Data
===
item_brand 1, item_category 21, item_code code1
item_brand 2, item_category 21, item_code code2
In Answer when i use the above hierarchy i have the problem that when i expand item_brand 1 and then item_category 21 automatically answer expand also item_brand 2 showing only item_code code2.
It happens because item_brand 1,2 have the same item_category 21.
Is there any way to make it work?
Thanks
Hermes
Edited by: hermes on 24 Μαρ 2011 3:05 πμ

Hi hermes,
try this:
create two physical table with the rows ant import in your Physical Layer:
DIM_TABLE1
BRAND CATEGORY
item_brand 1, item_category 21
item_brand 2, item_category 21
And DIM_TABLE2
BRAND CATEGORY ITEM
item_brand 1, item_category 21, item_code code1
item_brand 2, item_category 21, item_code code2
Define the join like this:
DIM_TABLE1.BRAND = DIM_TABLE2.BRAND and DIM_TABLE1.CATEGORY = DIM_TABLE2.CATEGORY
In the Business Model create 1 Logical Table Source for your dimension with the source you two physical table, inner join.
Now map the logical column.
I hope it helps.
Regards,
Gianluca

Dimension with 2 roles and 2 hierarchies used in 2 cubes

Hi,
I have a dimension in which there are two dimension roles (roleA, roleB) defined as well as two hierarchies (hierarchyA, hierarchyB). Currently hierarchyA is set as default. (Not because that is in fact the default one, only because OWB forces one to choose a default)
I need to define two cubes (cubeA, cubeB). CubeA will use the dimension with roleA and cubeB will use the dimension with roleB.
Is it possible to tell cubeA to use/see/make available only hierarchyA and cubeB only hierarchyB? HierarchyA makes no sense in cubeB so I want to "specify" hierarchyB for cubeB.
Thanks,
Juanita

A different issue but possibly related:
I have a ROLAP cube with one of the dimensions containing multiple hierarchies. If I deploy this with deployment option set to "Deploy data only", it works 100%. As soon as I change the deployment option to "Deploy All", I get a VLD-0398 error.
I need to choose "Deploy all" since the cube metadata must be deployed to the OLAP catalog in order for Disco OLAP and BI Spreadsheet Add-In to see the cube.
First question:
Is it possible to deploy to the OLAP catalog if the cube has a dimension with multiple hierarchies?
Second question:
If it is not possible, what is the workaround?
Thanks,
Juanita

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".

Double click to open .sql files with sql developer on mac osx

hi,
I am trying to double click a .sql file and open it with SQL Developer on Mac OSX lion. I have associated .sql files to SQL Developer. On clicking the file it opens the SQL developer application but does not open the actual .sql file. Any ideas?
Thanks

Hello,
Did you find any solution to your problem ? My SQL Developer worked fine and could open additional SQL files. Now it only opens the first one when starting SQL Developer. Additionnal files cannot be opened. Even running sqldeveloper.exe from command line with a SQL file as parameter doesn't help.
I'm on Windows 7, 64 bit, but the environment may not necessarily be the cause.
Regards
-- Alwin

The Dimension with ID ... doesn't exist in the collection

BPC 7.5 SP3, MS SQL 2005
I am processing an applicaiton using the Admin console. Choosing "Modify Application", checking the "Process Application" checkbox and clicking "Modify Application" to rebuild the app. The result is successful completion with an error on the details portion of the display under "Modify Fact Table" that lists and exception in the Log. The log in the management console shows the error
Microsoft.AnalysisServices.ItemNotFoundException: The "Dimension" with "ID" = PROFITCENTER doesn't exist in the collection.
The ProfitCenter dimension is one of the application's dimensions.
I can process the ProfitCenter dimension and process this application as part of the dimension processing and it is successful.
I can optimize this application and it is successful.
The application appears to be working properly.
I can open the cube in SQL Server Analysis Services and I can see the ProfitCenter dimension and browse its members. I can open the application cube and browse it.
I checked the profitcenter dimension member table and compared it to the fact tables and all the facts are base level members that are not calculated members.
Has anyone seen this error? Is this just a spurious message I can ignore or is there something really wrong?

We were able to solve this issue today. We turned off Insight and reprocessed the application. The error did not appear. I hope this works for you too.

SQL editor with tree view

We are working on some extraordiary long SQL stored procedure. Due to the shear size and IF/ELSE nesting it is very tedious to understand the logic .
What I am looking for is an SQL editor with tree view, where we can see IF/ ELSE, LOOP etc block as nodes. For example expand a node and see all blcoks of code within it.
+ IF block 1
expand---
-IF blcok 1
+IF block 1.1
+IF block 1.2
further expand
-IF blcok 1
+IF block 1.1
-IF block 1.2
IF block 1.2.1

Do some Google searches for a text editor that supports "folding".

Order Menbers in Dimension with Planning v3.3

Hi all,
I have a problem with menbers order in a old version of Hyperion Planning v3.3
I have the dimension Years with this order of menbers:
FY09
FY10
FY08
when i add another year, i received an error saying that FY09 is already created, in this version of planning don't exist buttons to reorder menbers or cuts and paste options.
I tried to find the order id in the planning repository but i have only see dimensions with a field for the order of apearence.
I think that planning uses the Id of creation to order the menbers in planning, then i tried to change the id in the repository to resolve the problem but with no success.
Anyone can give me any sugestion.

Hi,
You could have a similiar post about moving year members :- Re: Non standard Year member in Planning Years dimension
The post is about moving "No Year" but the logic is the same for other years.
Cheers
John
http://john-goodwin.blogspot.com/

How to migrate an existing Microsoft SSIS deployment if it is decided to replace SQL Server with an Oracle database?

Hi Oracle Gurus!
Currently, I am designing an ETL solution that transforms and loads a lot of data from flat files and sends it to an SQL Server 2008 R2 database for storage. However, at a future point of time, it may be decided to add or even replace SQL Server with an Oracle 11g database.
Currently, I am writing script transforms in C# to dynamically generate SSIS packages to tansform and load the data into SQL Server. But considering that in future, an Oracle 11g or 12c database might be added to, or replace the SQL Server database, how do I make my script transforms (or whatever else I am developing currently for SQL Server) reusable to the extent possible?
Or more precisely, what steps do I take, from an Oracle point of view, to ensure that any future migration of data to an Oracle database would be smooth to the extent possible?
Looking up to my Oracle Gurus for enlightenment in this matter!
Novice Kid

When you're writing your on C# code to load data into the SQL Server you have to modify the routines so that they will work with Oracle.
One approach is to use the extproc agent which would allow you to directly call external programs with all the logic in it to perform the load of your files and to put the data into the Oracle database. Another option would be to use utl_file package (or equivalents) which will allow you to open external files from your Oracle database and to directly read its content and then to pass it to the related tables.

Logic Doubling in v7 SQL - Dimension with 3 hierarchies

Similar Messages

Maybe you are looking for