Ragged Hierarchy - aggregation problem
I build dimension with Ragged Hierarchy as posted in [|http://oracleolap.blogspot.com/2008/01/olap-workshop-4-managing-different.html]
in "*Skip, Ragged and Ragged-Skip Level Hiearchies*" section.
I use scott schema for test
_1- build dimension emp with 4 levels using this data_
==> these data come from relation between EMPNO and MGR columns of EMP table
LVL1_CODE, LVL1_DESC, LVL2_CODE, LVL2_DESC, LVL3_CODE, LVL3_DESC, LVL4_CODE, LVL4_DESC
7839, KING
7839, KING , 7566, JONES
7839, KING, 7566, JONES, 7788, SCOTT
7839, KING, 7566, JONES, 7788, SCOTT, 7876, ADAMS
7839, KING, 7566, JONES, 7902, FORD
7839, KING , 7566, JONES, 7902, FORD, 7369, SMITH
7839, KING , 7698, BLAKE
7839, KING , 7698, BLAKE, 7499, ALLEN
7839, KING , 7698, BLAKE, 7521, WARD
7839, KING , 7698, BLAKE, 7654, MARTIN
7839, KING , 7698, BLAKE, 7844, TURNER
7839, KING , 7698, BLAKE, 7900, JAMES
7839, KING , 7782, CLARK
7839, KING , 7782, CLARK, 7934 MILLER
_2- build cube salary cube using this data_
EMPNO SAL
7369 800
7499 1600
7521 1250
7566 2975
7654 1250
7698 2850
7782 2450
7788 3000
7839 5000
7844 1500
7876 1100
7900 950
7902 3000
7934 1300
The total sum of salary on the top of hierarchy "KING" is 9,750$ and the correct value must be 29,025$.
I Notice that, in any node in hierachy that has childern the value of salary sum is the summation of its chiildern only without its value.
so what is the problem??
EMPNO SAL
7369 800
7499 1600
7521 1250
7566 2975
7654 1250
7698 2850
7782 2450
7788 3000
7839 5000
7844 1500
7876 1100
7900 950
7902 3000
7934 1300I can see the above data and looks like you are loading some values at higher level i.e. for emp no 7566. In DWH you will be loading data at leaf level and OLAP engine does aggregation(solve) and store data at higher level. What you are seeing is correct as any node's value is equal to the sum of values of its children.
Thanks,
Brijesh
Similar Messages
-
I'm trying to create ragged hierarchy with no success. I need to hide the middle level (level 3) and I put the same code and name to the level 3 as in Level 2 (which is higher). But I keep seen all the levels. I'm using "OnlyChildWithParentName"
option and I'm connected with MDX Compatibility=2 (I don't know how to set this property in the other way) .
Do you have a solution to my problem?Hi Tatyanaa,
According to your description, you are trying to create ragged hierarchy with no success, right?
Generally, if we want to turn a user hierarchy into a ragged hierarchy (perhaps to avoid using a parent child hierarchy) we need to use the HideMemberIf property on the user hierarchy. Here is a blog which describe Ragged Hierarchies, HideMemberIf and MDX Compatibility,
please see:
http://cwebbbi.wordpress.com/2009/11/11/ragged-hierarchies-hidememberif-and-mdx-compatibility/
Regards,
Charlie Liao
TechNet Community Support -
Building hierarchy trees (ragged hierarchy) in OBIEE
We want to build a hierarchy tree to drill into the different levels of our organization. (ragged hierarchy) In OBIEE Answers or like product is there a way to expand down the page in a tree format? I am looking for what others have done to display that UI drill down similar to how the Windows registry/file system expands. Building filters across the page will not work for us. Any thoughts would be greatly appreciated. Thanks.
Edited by: jonloring on Jun 30, 2009 12:40 PMI did read it and was helpful, but I am trying to solve a UI formating problem. All the BI products seem to go across the page with filtering, not down the page in a tree format.
-
Ragged hierarchy does not aggregate
Hi,
I have a dimension with ragged hierarchy of three levels:
level 1-> level 2 -> level 3
Some of the level 2 data do not have children (level 3). I mapped the dimension to cube with both level 2 and level 3 as required. Data is loaded into the cube but not those level 2 that have children.
Any suggestions are appreciated.
JuneI see two possible cases here.
(1) The source data may be loaded for the level 2 members without children, but the subsequent SOLVE step gets rid of them again.
(2) The source data is not loaded for the level 2 members in the first place.
You say that there are no rejected records, so problem (2) doesn't seem likely. But you can check that easily enough using the following script. This will clear the cube and load the leaf data, but will not aggregate. Obviously you should change "my_cube" to the name of your cube and set the parallelism appropriately based on your system and the amount of data you have.
exec dbms_cube.build('my_cube using (clear, load)', add_dimensions=>false, parallelism=>2)If there is still no data for the level 2 members after this, then you are having problem number (2). If the data is there, then it is problem (1). I will hold off from giving possible causes of (1) and (2) until we know which it is. -
Failed validation as a non-ragged hierarchy
After I define a TIME dimension and try to Maintain Dimension (Loading data at first time), it encounters error as below:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01714: "TIME_TEST_HA.TIME_TEST_HA" failed validation as a non-ragged hierarchy, Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Here is the data from related table TIME_TEST:
SELECT * FROM TIME_TEST;
YEAR QUARTER MONTH DAY
2008 4 11 5
2008 1 2 6
2008 4 10 7
2009 1 1 1
2009 1 1 5
Any help will be appreciate!
Thanks,
SatineHi Stuart,
My OLAP version is 11.1.0.7, upgrading from 11.1.0.6.
Here is the XML file for the dimension.
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.1">
<TimeDimension
Name="DAD"
ETViewName="DAD_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETDimensionOrderColumnName="DIM_ORDER"
ETHierarchyOrderColumnName="HIER_ORDER">
<Hierarchy>
<LevelHierarchy
IsSkipLevel="False"
IsRagged="False"
Name="SAD"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="DAD_SAD_VIEW">
<HierarchyLevel
DimensionLevel="YEAR">
<HierarchyLevelMap
KeyExpression="TEST_TEST."YEAR""
Query="TEST_TEST">
<AttributeMap
Name="DAD_YEAR_ID"
Expression="TEST_TEST."YEAR"">
<Attribute
Name="DAD_YEAR_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="YEAR_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="YEAR_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="YEAR_TIME_SPAN"
Expression="200">
<Attribute
Name="YEAR_TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="QUARTER">
<HierarchyLevelMap
KeyExpression="TEST_TEST."QUARTER""
Query="TEST_TEST">
<AttributeMap
Name="DAD_QUARTER_ID"
Expression="TEST_TEST."QUARTER"">
<Attribute
Name="DAD_QUARTER_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="QUARTER_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_TIME_SPAN"
Expression="200">
<Attribute
Name="QUARTER_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MONTH">
<HierarchyLevelMap
KeyExpression="TEST_TEST."MONTH""
Query="TEST_TEST">
<AttributeMap
Name="DAD_MONTH_ID"
Expression="TEST_TEST."MONTH"">
<Attribute
Name="DAD_MONTH_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="MONTH_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_TIME_SPAN"
Expression="200">
<Attribute
Name="MONTH_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="Description"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Sad">
</Description>
</LevelHierarchy>
</Hierarchy>
<DimensionLevel
Name="YEAR"
ETKeyColumnName="YEAR">
<Description
Type="Description"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year">
</Description>
<UniqueKeyAttribute
Name="DAD_YEAR_ID"/>
<VisibleAttribute
Name="YEAR_END_DATE"/>
<VisibleAttribute
Name="YEAR_TIME_SPAN"/>
<VisibleAttribute
Name="YEAR_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="YEAR_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="QUARTER"
ETKeyColumnName="QUARTER">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<UniqueKeyAttribute
Name="DAD_QUARTER_ID"/>
<VisibleAttribute
Name="QUARTER_END_DATE"/>
<VisibleAttribute
Name="QUARTER_TIME_SPAN"/>
<VisibleAttribute
Name="QUARTER_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="QUARTER_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="MONTH"
ETKeyColumnName="MONTH">
<Description
Type="Description"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month">
</Description>
<UniqueKeyAttribute
Name="DAD_MONTH_ID"/>
<VisibleAttribute
Name="MONTH_END_DATE"/>
<VisibleAttribute
Name="MONTH_TIME_SPAN"/>
<VisibleAttribute
Name="MONTH_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="MONTH_SHORT_DESCRIPTION"/>
</DimensionLevel>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="END_DATE"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="END_DATE">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="TIME_SPAN">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="LONG_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="SHORT_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="YEAR_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="YEAR_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="YEAR_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="YEAR_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="QUARTER_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="QUARTER_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="QUARTER_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="QUARTER_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_SHORT_DESCRIPTIO"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="MONTH_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="MONTH_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="MONTH_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="MONTH_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_YEAR_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_YEAR_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_QUARTER_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_QUARTER_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(6)"
ETAttributeColumnName="DAD_MONTH_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_MONTH_ID">
</BaseAttribute>
</Attribute>
<Organization>
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="STAR_CONSISTENT"
AddUniqueKeyPrefix="True">
<MVCreationOptions
RefreshOn="DEMAND"
RefreshType="COMPLETE"
EnableRewriteMV="False"
UsingConstraintsClause="ENFORCED">
</MVCreationOptions>
<AttributeOrganization
CreateIndex="False"
Attribute="END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_YEAR_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_QUARTER_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_MONTH_ID">
</AttributeOrganization>
<AW
Name="&AW_NAME;"/>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
</AWPrimaryDimensionOrganization>
</Organization>
<Description
Type="Description"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<TimeSpanAttribute
Name="TIME_SPAN"/>
<EndDateAttribute
Name="END_DATE"/>
<DefaultHierarchy
Name="SAD"/>
<ValueDescriptionAttribute
Name="LONG_DESCRIPTION"/>
<ShortValueDescriptionAttribute
Name="SHORT_DESCRIPTION"/>
</TimeDimension>
</Metadata>
You may want to have a test to change IsRagged="False" to IsRagged="True", then it woks well but the result is very stange.
And I find if the hierarchy is only with levels: YEAR and Quarter, then you can maintain it, but, for sure, the YEAR2009,QUARTER1 will overwrite YEAR2008,QUARTER1. If defining the hierarchy with levels:YEAR,QUARTER,MONTH, then you can't maintain it. On my opinion, it may because the data in third level MONTH can't identified the right routine to the higher level QUARTER.
Thanks,
Satine -
Ragged Hierarchy and Skip Level Hierarchy
Hi all,
I am confused with ragged and skip level hierarchy, as i read some documents related to obiee 11g.
Will you please explain with an example the difference between ragged hierarchy and skip level hierarchy and also when to use these hierarchies?
regards
chandra kanth.Chandra Kanth,
Hope this helps you
http://blogs.simba.com/.a/6a00e3932f172e88340133f4d758b5970b-800wi
Thanks,
Saichand.v -
Can Oracle OLAP (9.2 or higher) handle a ragged hierarchy?
eg: custom ownership chart
**\C100\
**\C100\C101\
**\C100\C101\102\
**\C100\C101\103\
**\C100\C101\103\104
**\C100\C101\103\104\105\106\107
**\C200\C201
**\C300\C301
**\C300\C301\C302
In other words, where a dimension may not have the same number of levels in its hierarchy? I guess more of a PC hierarchy than a LEVEL hierarcy?Do you have a link to more info/examples of this?
I have a fact table with UNIT, ACCOUNT and TIME dimensions
UNIT, ACCOUNT are each P.C hierarchies that I had to turn into LVLs for dimensions like so.
LVL1 LVL2 LVL3 LVL4 LVL5
CBC 261
CBC BC
CBC BC NBA
CBC BC NBA 240
CBC BC MAD
CBC BC MAD 241
CBC BC MAD BLDGS
CBC BC MAD BLDGS 231
CBC BC MAD BLDGS 232
CBC BC MAD BLDGS 233
Accounts are done the same way
I created hierarchies
LVL1->LVL2->LVL3->LVL4->LVL5 etc for ACCOUNT and UNIT
I want to pre-aggregate at the lowest level for each dimension.
How does AW do it if some records at LVL5 are NULL? -
Hi.
I'm trying to design the implementation of a department dimension that has a ragged hierarchy and I'm seeking advice on how to do this.
I'd like to start a dialog on the community's experience and best demonstrated practices on how to do this.
Has anyone done this successfully? If so, what did you learn in the process and what did you do to ensure success.
Thanks.
DanHi. Sorry for the long delay...Got pulled in another direction...
So, I'm revisiting ragged hierarchies. I understand pushing down/replicating the levels. Some more back story. I used the OWB Create dimension expert to generate the dimension, mapping, etc for me and it worked well. However, it does not push down the levels. For example, I have a leaf at level 5, but need it to be pushed down into levels 6 - 8.
Has anyone out there done this sort of work in OWB before, if so, can you offer advice, tips, tricks, diagrams, code, anything? I'm simply stuck at this point.
Thanks for your time.
Dan -
Query rewrite complains about ragged hierarchy when it does not exist
Hi -
I have a customer dimension with only one level. The lowest level of detai.
When I enable the query rewrite I get an error (see below) about ragged or skipped level hierarchy in my customer dimension. I am trying to figure out what the issue is so I created a one level customer hierarchy (lowest level) and I still get the error.
I do not understand how I can have a skipped/ragged hierarchy when my dimension is at the lowest level.
I am using the lastest versions of AWM and 11G.
Thanks in advance for any help you can provide,
Frank
Invalid Metadata Objects:
Invalid Object "MYTEST.CUST_SALES": "XOQ-01957: The cube has REWRITE MVs and also contains either a ragged or skip-level hierarchy. The hierarchy is "MYTEST.CUST_DIM.STANDARD"."
Edited by: bmwrider on Oct 16, 2009 9:01 AMHi there,
See this:- Error when trying to enable cube MV query rewrite
Thanks,
Stuart Bunby
OLAP Blog: http://oracleOLAP.blogspot.com
OLAP Wiki: http://wiki.oracle.com/page/Oracle+OLAP+Option
OLAP on OTN: http://www.oracle.com/technology/products/bi/olap/index.html
DW on OTN : http://www.oracle.com/technology/products/bi/db/11g/index.html -
Ragged Hierarchy Snowflake Displays Dimension Key as Descriptor
Hello All -
I am having an issue with OWB 10gR2 and any help would be appreciated.
I have created a Product Dimension using the "ROLAP" - "Manual" storage method which I've modeled as a snowflake to support our ragged hierarchy.
I can create, validate, and view the data in the dimension and it is correct ... but the only level of my three levels (All Products, Products, Sub Products) to display the descriptor is the Sub Products level. The other two levels display the Surrogate ID - regardless of what settings I change.
I know this might sound trivial but it does make a huge difference when you're working with a large number of product hierarchies or demonstrating to non-technical superiors.
Thanks in advance for any assistance!I took a look at this thread, but I think you have a different issue than mine. My Snowflake dimension isn't implemented as MANUAL. I use the Snowflake option and it isn't a "ragged" hierarchy.
In reality I do, but I "force" the levels to the maximum number. This lets me attach all facts at the base level and have a single grain. For example if I had a mix of 2 level and 3 level hierarchies, I repeat level 2 into level 3 for the 2 level items.
I rarely use the data viewer, but I did see that if I use it on the table objects, I see my short descriptors. If I use it on the dimension objects it doesn't work - probably because I only implement relational objects. -
Aggregation problem in Qery design
Hi folks,
I have the following situation:
- Characteristics as line items, shown as a hierarchie.
- KFs and Formulars in columns
I want the formulars to be calculated on the basis of a combination of two of the characteristics (the bottom two in the lines hierarchy) and then aggregated.
Exception aggregation allows me to choose "total" based on one characteristic, but not a combination of two.
One solution would be, of course, to create a new characteristic in the cube that is a combination of the two existing characteristics in question and then use this for exception aggregation. This would be a bit complicated though, as the two characteristics are in fact navigational attributes of characteristics that appear in the data source and the cube.
Therefore, I'd prefer a solution that is in the scope of query designer rather than cube design.
Any ideas?
PS: The formulars show correct values on the level of the bottom most characteristic in the lines hierarchy if I choose that characteristic for exception aggregation. The results are not correct one level up from there as I can not get the system to sum the results up along the hierarchy. Instead, they are calculated for the aggregated values of the KFs used in the formular.
Apparently the "show lines as hierarchy" function really only affects display of the lines, not calculations.Hi John,
I understood your problem. Solution is easy:
Make formula 1, exception aggregation as total , ref char as char 1
Then make another formula 2 on formula 1, exception aggregation as total , ref char as char 2.
And in the report show formula 2 and hide formula 1.
Best Wishes,
Mayank -
NQSError: 15019, Hierarchy / Aggregates problem
Hello,
I have a problem with a hierarchy when I want to implement an aggregate fact and dimension table in the repository.
I have a logical dimension table Time, a logical fact table and a hierarchy Time with the following levels: All,Years, YearWeeks, Days).
The logical time dimension table has now two sources:
Calendar (Logical level: Day)
YearWeeks Calendar (Logical level: YearWeek)
The logical fact table has also two sources:
Day Facts (Logical level: Day)
Week Facts (Logical level: YearWeek)
I have also mapped the logical columns to the correct source tables, also for those columns which have multiple source tables.
When I check on global consistency I get the following error:
[nQSError: 15019] Table Time is functionally dependent upon level YearWeek, but a more detailed child level has associated columns from that same table or a more detailed table.
I don't know how to resolve this problem. Is there something I forgot or something I have to check? Thanks for your help!
Regards,
Stijnhi,
you must understand that when you are making a hieracly from a dimension table the lowest level must be unique!
@@the data is at city-> country-> Region level.
in your example region level,this means, that the key for the fact must be region level and the others...
rebuild your table
hope i helped...
http://greekoraclebi.blogspot.com/ -
Hi
I have a parent child ragged hisrarchy. I want to build level wise dimension to be able to report using crystal .
The PC table I have is like
Child Parent
A11 A1
A12 A1
A111 A11
A112 A11
A113 A11
A121 A12
A122 A12
A1121 A112
A1221 A122
A1222 A122
I want to solve this as a level based hierarchy using universe like:
LEV1 LEV2 LEV3 LEV4
A1 A12 A122 A1222
A1 A12 A122 A1221
A1 A11 A112 A1121
A1 A12 A122
A1 A12 A121
A1 A11 A113
A1 A11 A112
A1 A11 A111
A1 A12
A1 A11
Can somebody please put some light on this how can I achieve this?
Thanks
AtulHi Atul,
You can use a Derived Table that flatten the hierarchy.
Here is a sample based on the example you provided, you just have to replace "child", "parent" and "myTable" strings by the corrseponding column and table names:
SELECT DISTINCT
Z.child,
A.parent_1,
A.child_1,
A.parent_2,
A.child_2,
A.parent_3,
A.child_3,
Z.parent AS parent_4,
Z.child AS child_4
FROM myTable Z,
SELECT DISTINCT
A.parent_1,
A.child_1,
A.parent_2,
A.child_2,
Z.parent AS parent_3,
Z.child AS child_3
FROM myTable Z,
SELECT DISTINCT
A.parent_1,
A.child_1,
Z.parent AS parent_2,
Z.child AS child_2
FROM myTable Z,
SELECT DISTINCT
parent AS parent_1,
child AS child_1
FROM myTable
WHERE parent = 0 OR parent IS NULL
) A
WHERE A.child_1 = Z.parent
) A
WHERE A.child_2 = Z.parent
) A
WHERE A.child_3 = Z.parent
UNION
SELECT DISTINCT
A.child_3 AS child,
A.parent_1,
A.child_1,
A.parent_2,
A.child_2,
A.parent_3,
A.child_3,
NULL AS parent_4,
NULL AS child_4
FROM myTable Z,
SELECT DISTINCT
A.parent_1,
A.child_1,
A.parent_2,
A.child_2,
Z.parent AS parent_3,
Z.child AS child_3
FROM myTable Z,
SELECT DISTINCT
A.parent_1,
A.child_1,
Z.parent AS parent_2,
Z.child AS child_2
FROM myTable Z,
SELECT DISTINCT
parent AS parent_1,
child AS child_1
FROM myTable
WHERE parent = 0 OR parent IS NULL
) A
WHERE A.child_1 = Z.parent
) A
WHERE A.child_2 = Z.parent
) A
WHERE A.child_3 NOT IN (SELECT parent FROM myTable)
UNION
SELECT DISTINCT
A.child_2 AS child,
A.parent_1,
A.child_1,
A.parent_2,
A.child_2,
NULL AS parent_3,
NULL AS child_3,
NULL AS parent_4,
NULL AS child_4
FROM myTable Z,
SELECT DISTINCT
A.parent_1,
A.child_1,
Z.parent AS parent_2,
Z.child AS child_2
FROM myTable Z,
SELECT DISTINCT
parent AS parent_1,
child AS child_1
FROM myTable
WHERE parent = 0 OR parent IS NULL
) A
WHERE A.child_1 = Z.parent
) A
WHERE A.child_2 NOT IN (SELECT parent FROM myTable)
UNION
SELECT DISTINCT
A.child_1 AS child,
A.parent_1,
A.child_1,
NULL AS parent_2,
NULL AS child_2,
NULL AS parent_3,
NULL AS child_3,
NULL AS parent_4,
NULL AS child_4
FROM myTable Z,
SELECT DISTINCT
parent AS parent_1,
child AS child_1
FROM myTable
WHERE parent = 0 OR parent IS NULL
) A
WHERE A.child_1 NOT IN (SELECT parent FROM myTable)
Regards,
Didier -
CostCenter Group Aggregation problem. High Priority Issue.
Hi Experts,
I have very crital issue in the report, Help needed.
I had some kind of requirement in one of the Overhead cost report, need to combine the COPA data and Costcenter(Over Head cost) data. I have a problem with Costcenter Group aggregation on the report.
I have Restricted 2-Keyfigures want to derive the 3rd Keyfigure values. I given the below exmaple of the data. In my report I just want to display the KeyFigure(KF-A,B,C). I dont want to Display the Cost Center group/Costcenter Number in my report. My report ouput will be one line. But If I removed the costcenter Group I am seeing different values of the Keyfigure C, If I display the Costcenter comng with differnt Values. I am expecting the values in the column C is 1400 but it is coming like 3600.
Please guide me how to design the Keyfigures if I want to get the value 1400 in theKeyFigre C with out Showing the Costcenter In the report.
Cost-Center Group R00048
Costcenter KF-A KF-B KF-C
10113 10 10 100
10114 20 20 400
10115 30 30 900
60 60 1400(Insted of this its comming like 3600)
Appreciate the response.
Thanks,
VenkataHi,
Check the display properties of key figure in Query Designer/Info object level.
Set the property accordingly.
I hope it will help.
Thanks,
S -
I've created some nice sites with iWeb but Rage's SEO Tool is corrupting the test. Once SEO Tool republishes them I'm getting diamonds with ? marks instead of apostrophies and bullets. Also when I publish with SEO Tool when entering the path it says "directory already exists." So I can force the new files in with FTP Fetch but the fonts are still messed up.
This doesn't sound like a font problem, it sounds like something is being removed from your website that shouldn't be. Specifically the meta content type tag.
What is your website URL?
Also the error you are getting fro the directory already exists means that you didn't enter your root directory path correctly. Email your web host and ask them what your root directory path is and enter what they give you.
Maybe you are looking for
-
I'm using IE 11 with Win 7 Pro 64 bit. When I read a PDF file online, most of the time IE refuses to go back to the main page of the site. When I press the back button on my keyboard or click the back arrow on IE it just keeps trying to reopen the PD
-
Regarding Employee Photo in ESS
Hi, In ESS there is a photo in one of the iview. I want to know where is the photo physically stored. What is the procedure to upload all employee photos in bulk. I want to know can I use any Content management system to upload photos or can I use SA
-
Report on list of Materials planned in UCP
Hi Experts, Is there any report available to get the list of Materials planned in Unit Cost Planning. Thanks in advance. Vinodh
-
Facet details not displayed in merchandising bcc atg 10.2
Facet details have not been displayed in merchandising bcc in atg10.2 ? when i click on facet tab, facing issues in bcc like facet configuraion[object refineconfig properties] can anyone help me for this?
-
Sync ipod Touch with Windows Live Mail
Is there a way to Sync Ipod touch's information (calendars, contacts and such) with the new Windows Live Mail through Itune 8?