How to handle parent-child dimension in OWB?????

i have a dimension have many levels,and the amount of levels is varing,so i cannot use the wizard to define my dimension ,seems with OWB i can only define dimension with certain amount of levels.......
my dimension data is stored with this format:
child parent
Los Angles US
US WORLD
it is called a parent-child relation ,how can i define dimension with parent-child relation witn OWB...
Can OWB do it ????? You must define a dimension, define the dimension levels and the hierarchy inside the dimension (a hierarchy can have as many levels as you want, parent-child relationship is a normal hierarchy concept - no rocket science here). Then you have to map the data source for the dimension levels appropriately. Please refer to the user manual, chapter 4 ("Defining dimensianal targets") for details.
Regards:
Igor

Similar Messages

How to create a parent-child dimension in EIS?

Does anyoe know how to create a parent-child dimension in EIS? Helps.

It's easy but there are a few things to know.
-The underlying dimension table must be a 2 column recursive design. It can also have additional aliases and property columns.
-in the OLAP model you must do a "self-join". select the table properties | physical joins. then join the parent to the child within the same table
-in the metaoutline drag only one column, not both (i like using the child only) to the dimension in the metaoutline panel.
If you need more help email me ([email protected]) and I'll do a webex demo for you.
Ron

Load Parent-Child dimension with attributes by rule file

Well, I've cracked my head open while banging against this wall.
Task is plain & simple:
How can I load build dimension from such table, using rule file?
Data
ProductParent ProductChild ProductAttribute
Balls Ball_8 Round
I want to load both product dimension and attribute by single rule file (neither of these dimensions exists in database before load), so I do the following:
1) Set dimension build settings, creating dimension Products (marking it P\C generated, sparse), having an attribute dimension AttributeDim
2) Mark the fields as Parent, Child and AttributeDim of dimension Products
After loading rule file a get three types of errors:
a) "Base member (Balls) association level does not match base dimension association level" -- does this mean that I cannot assign attributes in P\C way?
b) "Record #327 - Can not uniquely identify member by Balls (3335)
Balls Ball_8 Round" -- That's strange, I thought member should be identified by Ball_8 (and this column is unique)
c) "\\Record #418 - Error in association transaction [Ball_8] to [Round] (3362)"
I've read all I could find on topic from this forum, network45 board and going to start my way through metalink3, but maybe some kind soul will rescue me from drowning in information ocean?

Hi,
Outline is blank at the start of load and I expect dimensions Product and ProdAttribute to be added.
Generations are unapplicable, since I can't turn this parent-child dimension (it's ragged) into generation one.
And, by the way Integration Services manages to do this somehow, why rule files wouldn't?

Security on Employee Parent Child Dimension with SCD 2

Hi
I am looking for a solution for how to get all child members of a Parent employee including the one in the history. I tried multiple ways the problem which I am facing are
Scenario 1: When I am using this approach, since the Employee with 'Jump' as employee id do have a history record with no children under him I am getting 'Null'. But there are new records (last 3 SCD changes) where he has employees under him.
SELECT descendants(
// Check if current employee is a manager
iif(hierarchize(exists([Employee].[Manager Employee Dim ID].members,
(strtomember("[Employee].[Employee Login ID].&[SIC\jump]"))),post).item(0).item(0).parent.datamember is
hierarchize(exists([Employee].[Manager Employee Dim ID].members,
(strtomember("[Employee].[Employee Login ID].&[SIC\jump]"))), post).item(0).item(0),
// End of check if current employee is manager
hierarchize(exists([Employee].[Manager Employee Dim ID].members,
(strtomember("[Employee].[Employee Login ID].&[SIC\jump]"))),post).item(0).item(0).parent,
hierarchize(exists([Employee].[Manager Employee Dim ID].members,
(strtomember("[Employee].[Employee Login ID].&[SIC\jump]"))), post).item(0).item(0))) ON 0,
[Measures].[Aggregate Count] On 1
FROM [Data Ware House]
Scenario 2: When I put a filter (as a set) to check if the record is current then I am getting the latest record for employee 'Jump'. But here the problem is that the employee under him I am only getting the [Measures].[Aggregate Count] of the latest
change only.
SELECT descendants(
// Check if current employee is a manager
iif(hierarchize(exists([UW Employee].[Manager Employee Dim ID].members,
(strtomember("[UW Employee].[Employee Login ID].&[SIC\flew]"),[UW Employee].[Current Flag].&[Y])),
post).item(0).item(0).parent.datamember is
hierarchize(exists([UW Employee].[Manager Employee Dim ID].members,
(strtomember("[UW Employee].[Employee Login ID].&[SIC\flew]"),[UW Employee].[Current Flag].&[Y])), post).item(0).item(0),
// End of check if current employee is manager
hierarchize(exists([UW Employee].[Manager Employee Dim ID].members,
(strtomember("[UW Employee].[Employee Login ID].&[SIC\flew]"),[UW Employee].[Current Flag].&[Y])),
post).item(0).item(0).parent,
hierarchize(exists([UW Employee].[Manager Employee Dim ID].members,
(strtomember("[UW Employee].[Employee Login ID].&[SIC\flew]"),[UW Employee].[Current Flag].&[Y])), post).item(0).item(0))
) ON 0,
[Measures].[Contract Change Aggregate Count] ON 1
FROM [Data Ware House]
If any one can help me out with this that will be helpful.
What I need is all the members under the employee 'Jump', including the Old scd records for 'jump'
regards
Robin
Robs

Hi,
Outline is blank at the start of load and I expect dimensions Product and ProdAttribute to be added.
Generations are unapplicable, since I can't turn this parent-child dimension (it's ragged) into generation one.
And, by the way Integration Services manages to do this somehow, why rule files wouldn't?

MDX: Selecting specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy

I'm creating a SSRS report using SSAS cube as a source.
When creating a dataset for the report, I'm having trouble with MDX to select a specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy.
Lets say for example that I have an account dimension where,
In level 02 I have company ID:s 101, 102, 103 and so on...
In level 03 I have Balance sheet
In level 04 I have some account groups, Assets, Liabilities and so on... and In level 05 I have individual accounts
How can I select for example company 102:s Assets from level 04 and its descendants?
Normally in adventure works I would do this if I've wanted Current Assets and its descendants:
SELECT NON EMPTY { [Measures].[Amount] } ON COLUMNS, NON EMPTY
{ (DESCENDANTS([Account].[Accounts].[Account Level 03].[Current Assets]) ) } ON ROWS
FROM [Adventure Works]
But in my Account dimension at level 04 I have Assets member as many times as I have companies in level 02.
Tuomo

Hi Tuomo Helminen,
To this requirement of yours, I would recommend you use Cascading Parameters in Reporting services, you can refer to this FAQ How do I create cascading parameters when using cube database in Reporting Services at this link
http://blogs.msdn.com/b/sqlforum/archive/2011/04/11/forum-faq-how-do-i-create-cascading-parameters-when-using-cube-database-in-reporting-services.aspx
Thanks,
Challen Fu
TechNet
Subscriber Supportinforum
If you have any feedback on our support, please [email protected]
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Incorrect totals from cache with CustomRollupColumn and non-parent-child dimensions

Hello. Before I start let me apologise for my English :)
We have a very complex cube, with 2 (actually more, but only these 2 are important) parent-child dimensions.
One of them has CustomRollupColumn defined.
Not long ago we have decided to make refactoring of our cube. This also included making these dimensions non-parent-child.
All our old reports started to work much faster after that... but we have mentioned that sometimes they show incorrect totals, or no totals at all.
We spend a lot of time trying to figure out what's wrong and finally we had found that if we clear cache before next refresh of the report - the totals are always correct!
If we don't clear cache - we get wrong totals second time, and each next time after that. If we see wrong totals - we could clear cache and get correct totals once again.
If we use "Real Time Olap=True;" connection string parameter - the totals are always correct because cache is not used.
But we don't like this workaround.
Is there any fix for this bug? Google shows that this problem exists from SQL2005, and still we have it :( Also, there is adivice to set CalculationCoverPolicy to 9 - we have tried - but it was fruitless.
And if we revert these 2 dimensions back to parent-child - all working fine again, but as slow as it was before the refactoring :(

Hi Bateks,
Glad to hear that your issue had been solved by yourself, thank you for you sharing which will help other forum members who have the similar issue.
Regards,
Charlie Liao
TechNet Community Support

How can provide parent-child nodes relation ships?

how can provide parent-child nodes relation ships?

I was under the impression that scenegraph is like a JTree. But in JavaFX only leaf node rendering in scenegraph. This situation was confusing my mind. In JavaFX CustomNode must be extending and return a group for custom leaf. If we want to a create parent-child node hierarchy we are create CustomNode that return a group and this group contain an another group,etc. So there is maybe only a way. If you learning to JavaFX first time.This way don't look familiar.

How to create Parent Child relationship of Assets

Hi All
can any one provide the solution for the below mention requirment.
Problem Description: How to create Parent Child relationship of Assets in below case.
1. If asset Category of Child assets are different but both parent & child assets are already capitalized.
2. If asset Category of Child assets are same but both parent & child assets are already capitalized.
3. If asset Category of Child assets are same for new assets.

Hi All
can any one provide the solution for the below mention requirment.
Problem Description: How to create Parent Child relationship of Assets in below case.
1. If asset Category of Child assets are different but both parent & child assets are already capitalized.
2. If asset Category of Child assets are same but both parent & child assets are already capitalized.
3. If asset Category of Child assets are same for new assets.

Inclue children and exclue children in a single hierarchy in parent child dimension in mdx

hi,
include children and exclude children in a single hierarchy in parent child dimension in mdx
*12-parent
**20-parent
- 9-parent
--250-child1
--210-child2
--240-child3
aggregation of 12-parent only
aggregation of 20-parent only
aggregation of 9 with children
regards,
Manish

Hi manishcal16PPS,
According to your description, you have a parent child dimension in your cube. Now you want to use one measure use show aggregation value including/excluding child member based on different parent level member. Right?
In this scenario, we could use IIF() in the calculated measure to apply different calculation depends on the current dimension member. Please refer to query below:
with member [x] as
IIF([Dim].[Hierarchy].CurrentMember is [Dim].[Hierarchy].[Parent].&[9]
sum(Descendants([Dim].[Hierarchy].CurrentMember,
[Date].[Calendar].[Parent]),
[Measures].[Amount])
sum([Dim].[Hierarchy].CurrentMember,[Measures].[Amount])
select [x] on 0,
[Date].[Calendar].[Parent].members on 1
from
[Cube]
Best Regards,
Simon Hou
TechNet Community Support

Parent-child dimensions limitations

Hi eb
It is very convinient to develop complex heirarchized dimensions as parent-child especialy when they retain historical
changes in members.
I know one reason to not using such dimensions when they contain some 200,000 members or more due to performance issues (no aggregations on parent attributes???).
Are there any other reasons to not using parent-child heirarchies in ssas MD cubes???
TIA!
Rea

Hi reapeleg,
According to your description, you want to know weakness of using parent-child dimension. Right?
In Analysis Services, a parent-child dimension is distinguished by fact that it contains a hierarchy based on a recursive relationship. So it can only cause some performance problem. But the main reason of using a parent-child dimension
or not depends on the relationship between the attributes in your dimension. And there's workaround for the performance issue. Please see:
Parent-Child Dimensions in Analysis Services – Performance Walkthrough
Reference:
Parent-Child Dimensions
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

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

Do the custom rollup member formulas work recursively for parent child dimension?

Hi
We have custom rollup set up for Account dimension which is parent child.
It seems to work fine when the custom member formula refers to a base account member i.e. if the formula for MemberKey4 is (MemberKey1 + MemberKey2) then it shows the sum of the underlying members 1 and 2.
But if the formula for MemberKey10 is (MemberKey3 + MemberKey4) then it should evaluate the value for MemberKey4 first and then add to it value for MemberKey3 to come up with final number for MemberKey10.
Do the custom rollup work fine with the recursive calculations? Is this recursion limited to some level?
Thanks
Shailesh

Hi Jorg,
Thanks for your input.
Actually the hierarhcy is more determined by the parent child relationship. So we cannot move the members as per the formula. And further the formulas are not always additive, there are divisions and multiplactions happening also.
Further the calculated members (account members) are used in different places, the usage level of calculated members could be 3 in some cases i.e. MemberKey15 = (calculated using MemberKey10 = (calculated using MemberKey7 = (Calculated using MemberKey4 = (calculated using base members)))). Now inserting the base members in place of a calcuated member becomes more of string manipulation.
And on the top of above complexity, the formulas are not static and they are more user defined, they may change between time periods, which forces us to write a dynamic procedure to translate the 'business formula' into SSAS formula. We expect the custom rollup to work as expected (i.e. if the formula contains a calculation involving the calculated member, it should resolve that first and so on) and we have written generic procedure to replace the Account Code in the 'business formula' with the accont key value with the account hierarchy char string.
In the link http://doc.ddart.net/mssql/sql2000/html/olapdmad/agmdxadvanced_6jn7.htm for AS2000, it talks about the calculation pass deapth, it says:
.......If a cube has custom rollup formulas or custom rollup operators, a second calculation pass is performed to handle the computations needed to calculate these features.......
Now from the above, it is obvious that the OLAP engine will automatically go into recursion if the formula contains a cacluated member and it knows that the calculated member has to be resolved first before calculating the final formula result. The above article also talks about 'Calculation Pass Number' property in the AdvanceCube Editor (AS2000), which can be set to the value depending on the expected number of passes required in a given scenario. I don't find such an equivalent peoperty for SSAS 2005.
Would anybody please throw some more ideas / insights on this issue?
Jorg, thanks again for your input...
Shailesh

Showing aggregated data at Manager's geography level in a parent child dimension

I have DimEmployee dimension which has parent child relationship (between ManagerID & EmployeeID)
EmployeeID
ManagerID
GeographyID
Othe columns
1
1
G1
2
1
G2
3
2
G3
4
4
G4
5
4
G5
This dimension has been connected to FactSales using “EmployeeID”.
EmployeeID
Sales
1
100
2
150
3
80
4
50
5
60
There is one more dimension called DimGeography which has reference relationship with “FactSales” through “GeographyID” column of DimEmployee
GeographyID
GeoName
G1
Abc
G2
Xyz
Now I have to rollup all subordinates data and show it under Manger’s geography as shown below
ABC (G1)                              330 (100+150+80)
Xyz (G2)                               110 (50+60)
I am able to show data at MangerID level data but unable to do so at Manager’s Geography level.
How do I solve this problem using MDX?

I have DimEmployee dimension which has parent child relationship (between ManagerID & EmployeeID)
EmployeeID
ManagerID
GeographyID
Othe columns
1
1
G1
2
1
G2
3
2
G3
4
4
G4
5
4
G5
This dimension has been connected to FactSales using “EmployeeID”.
EmployeeID
Sales
1
100
2
150
3
80
4
50
5
60
There is one more dimension called DimGeography which has reference relationship with “FactSales” through “GeographyID” column of DimEmployee
GeographyID
GeoName
G1
Abc
G2
Xyz
Now I have to rollup all subordinates data and show it under Manger’s geography as shown below
ABC (G1)                              330 (100+150+80)
Xyz (G2)                               110 (50+60)
I am able to show data at MangerID level data but unable to do so at Manager’s Geography level.
How do I solve this problem using MDX?
Any Help??? Ideally we have to make other attributes (in this case Geography) recursive along with attributes involved in Parent Child hierarchy

Parent-Child Dimension

Hi There,
I try to use Essbase Studio to build dimension with source table already has parent-child structure, how do I specify parent-child in essbase studio?
Thanks

In your minischema, do a join between the parent and the child, then when you create the hierarchy, just put int he name of the parent colum with the child column as it's child
sort of like
Parent
---child
then preview the hierarchy and you should see that it picks up the structure. If you don't do the join and save it, then the preview will look funny

Dynamic Security in a denormalized Parent-Child dimension Table

Hi guys, I need your priceless help again:
I have a parent child relationship in a table with a fixed depth, let´s say Region-->Area-->Country
I denormalized the table to have something like this
Then, to implement dynamic security, I think in a bridge table with the userId
and the CountryId, then with a measure group and a measure which count the combination of user/country I can proof the security using the non empty function.
My question is how can I also set security for the levels above the leaf members, let´s say, I want to assign an user to the Area level or Region Level. I don't know exactly which key could I include in the bridge table.
I may want to keep the id´s of the original table in the different levels.
Any comment will be appreciated.
Kind Regards,

Hi Paul,
According to your description, you want to apply dynamic security on parent-child hierarchy. Right?
In Analysis Services, when a dimension contains a parent-child hierarchy, we can't set up security directly on the key attribute. Because it will not appear on the dropdown list of Dimension Data Security in Role editor.
In this scenario, we need to filter on key attribute and not the parent-child hierarchy. Then use Linkmember() to find the equivalent members on the parent-child hierarchy. Please refer to the expression below based on a employee dimension with parent-child
hierarchy.
Generate(
NonEmpty(
[Employee].[Employee].[Employee].Members,
   [Measures].[Employee Count],
   StrToMember('[User].[User].[' + UserName() + ']')
             LinkMember(
                 [Employee].[Employee].CurrentMember,
                 [Employee].[Employees]
Also I suggest an excellent book:
Expert Cube Development with Microsoft SQL Server 2008 Analysis Services. It talks about this scenario in chap 9.
Reference:
SSAS
Dynamic security - Bridge table (factless) between User dimension and Parent-Child (PC) dimension
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

How to handle parent-child dimension in OWB?????

Similar Messages

Maybe you are looking for