Attribute Dimension or Alternate Hierarchy

Hello,
We have a sparse dimension that has probably around 1500 members. We need to report on these members in different views then the current hierarchy holds. Is it best to create an alternate hierarchy with these 1500 members or to tag these members with various attributes and then use the attribute in the different reports. I did some research and found that attribute dimensions often have slow FR performance since they are dynamic, however, I feel like 1500 shared members is a lot. Any tips, tricks, advice would be greatly appreciated.

Hi,
I don't think 1500 shared members is a concern in and of itself (unless you are putting them all under one dynamic parent!). You are correct there could be some response time impact with attribute dimension retrievals, but then shared members under dynamic sparse parents may present similar concerns.
I would encourage you to think about the structure and navigability desired. You should keep in mind that shared member rollups can only be used in reports consistent with the dimension they are in. One advantage of attribute dimensions over shared rollups is that, only with attribute dimensions, can you cross-tab report against the base dimension. If your users care about being able to see certain alternate groupings across the main dimension, then I would suggest going with attribute dimensions.
There are other considerations. For instance, adding a large number of shared rollups in your BSO anchor dimension (the physically last dimension with hierarchy), you put more demand on Essbase calculator cache.
Out of time for now. Just sharing some initial thoughts I hope you will find helpful.
Darrell Barr

Similar Messages

Loading Planning attribute dimension alternate hierarchies with ODI

Does anyone know how to load an attribute dimension alternate hierarchy via an ODI interface? I'm assuming that alternate hierarchies are allowed in attribute dimensions?
Edited by: jayfin on Mar 28, 2011 5:59 PM

If you are talking about created a shared hieararchy then no this is not possible as you shouldn't be able to do it in planning.
If it is just another hierarchy in your attribute dimension then you should be able to load parent/child members to build it using ODI.
Cheers
John
http://john-goodwin.blogspot.com/

Creating a hierarchy in an attribute dimension using EIS

we use EIS for our data/member loads.
I have a couple of cubes with attribute dims and I had no problems using EIS to create those attribute dims as they did not have a hierarchy
I have a new requirement to create an attribute dim with a hierarchy.
I am not sure how can I do this in EIS. Please advice.
I went through the chm file but could not really figure out anything about it.
Thank you.

Actually you can have hierarchies in your attribute dims in EIS, including text attributes. I have a number of models where we do this.
It works the same as with regular dimensions. Assume you have a table with product codes and then a column for lev 0 attribute and lev 1 attribute.
So code is XYZ
Lev 0 attribute is Red
Lev 1 attribute is Primary
When you set up your attribute dim in EIS, set both attribute columns as attribute, then in the metaoutline model, drag lev1 attibute onto the outline, then drag lev0 attribute under it. You will get a warning that you can only associate the lev0 attribute with the base dimension, which is fine. Associate the lev0 attribute with the base dim as you normally would and build your outline.
Your end result will be an attribute dim that looks like this
Product Color
--Primary
----Red

Alternate hierarchy dimension build with load rules

Hi,
I am trying to build a alternate hierarchy dimension using load rules (I feel using EIS is easier to build ASO and multiple hierarchies but we r trying to get rid of EIS member loads). Looking at different posts my understanding is it has to be done using two different rules file first to build the stored hierarchies then use parent-child reference to build the shared hierarchy. Below is the link for the picture how I am trying to build the dimension. I've tried different possibilities but no luck, I am having a tough time to come up with a way to do this using rules file.
http://s24.postimg.org/u5hl4eyqt/basis.jpg

If your file is in a parent/child order, then you can build easily in one rule. make sure the primary (stored Hierarchy) gets built first followed by the alternate hierarchies. I suggest adding a SortID column to the source so you can sort the file to get it into the right order. You can also build the alternate hierarchies using level or generation builds in one load rule, but especially if you have a lot of alternate hierarchies or members, then the parent/child method is easiest.
Read in the DBAG about parent/child files and it will give you more info

Attribute dimension hierarchy

what is use of hierarchy in Attribute dimension. Any one can give example when to have it.

The essbase documentation has a good section on understanding attributes - http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dattrib.html#dattrib497341
Cheers
John
http://john-goodwin.blogspot.com/

Having issues when creating alternate hierarchy in time dimension

Hi Everyone
I used How to guide of MS version 7.5 to build 2 hierarchies in time dimension.
It worked in MS version.7.5
But when i copied the same dimension members to NW version the alternate hierarchy (parenth2) doesn't work.
I mentioned all the required properties for both roll ups (like parenth2,timeid,usertimeid,ISBEGINNING).
Any idea?
thanks
reddy

"This sounds confusing to me as to how a stored hierarchy can contain a shared member from a dynamic hierarchy"
You just need to understand how things are stored in ASO for this to make sense.
A level 0 member with no formula, even though it is in a dynamic hierarchy is still a stored member.
-- All level 0 members that do not have formulas are stored in ASO.
Upper level members are all "dynamically calculated".
-- Upper level members of dynamic hierarchies are pure dynamic.
-- Upper level members of stored hierarchies are candidates to have their values pre-aggregated and stored in a view.

Attribute Dimensions and Excel Retrieves

Dear All,<BR><BR>I have a cube that has a sparse dimension with attributes attached (all at the same level). When I retrieve using different attributes in the retrieve the results are not consistent i.e. some of the sparse members with the same attribute are left out of the result. It appears to happen when branches of the dimension in the same area are separated by a branch with an alternate attribute value (from the same attribute dimension). I have cured this by moving the affected branches next to each other, is this something that I need to watch out for on the design side i.e. to do with the way Essbase handles attribute dimensions? Any guidance would be appreciated.

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

How can I see different results for alternate hierarchy?

I have an outline with an accounts dimension with the following members (amongst others):
Total Expenses
Exp1 +
Exp2 +
Exp3 +
Exp31 + (child of Exp3)
Exp32 + (child of Exp3)
Exp33 + (child of Exp3)
I also have another dimension, let's call it DIM, with the following primary and alternate hierarchies (shares upper levels with primary):
Primary
A
A1 +
A2 +
A3 +
B
B1 +
B2 +
B3 +
Alternate
A + (shared member)
B + (shared member)
I want to be able to do the following:
When I select something from the primary hieararchy, I want to see the original values in Exp31, Exp32 and Exp33. When I select a member from the alternate hierarchy, I want to see these 3 expenses zeroed out. Is this possible? I can't find a way to do this since the values for shared members are taken from primary members. Is there another way to do this?
Thanks for your help.
Bela

I did think of creating an alternate hierarchy in the accounts dimension which excludes the expenses I do not want to include in the total, but I have 3 different categories of expenses I want to exclude depending on the members I'm viewing, so I'll have to create that many alternate hierarchies in accounts, each excluding a specific category of expenses.
If you have a brainwave, please let me know!
Bela

Essbase Studio Alternate Hierarchy Creation error

Hi All,
I'm using Essbase Studio to create an alternate hierarchy. I have a dim which has shared members and I'm getting the following error msg during cube deployment:
1. Record #1- Member Name (SKU) already used i.e. the member for which I m trying to create shared member
     I m following the same procedure mentioned in the user guide i.e.
        Step1: create a copy of the dimension element that you want to designate as a shared member(Renamed SKU_copy with SKU_Diet). By making a copy, the binding expression for this element is the same as the original dimension element (SKU_Diet).
       Step2: when you create the second hierarchy in the chain, which is the alternate hierarchy, add a user-defined membas the parent and add the new dimension element (SKU_Diet) as the child, which will be the shared member.
     Even I m able to see the shared members (SKU_Diet) under user defined member "Diet" under the preview window (both by key binding and caption binding) as wel..
     But I m unable to see the shared members in EAS console after deploying the cube from Essbase Studio to EAS Console.
I m not able to understand what I m missing exactly,.and suggest me other ways as well for creating alternate hierarchies in Essbase Studio.
Thanks in advance..!!

looks like similar issue..
https://forums.oracle.com/thread/1555956
It will work in genaration 2 not in genration 1.
Thanks,
mady

How to create an attribute dimension in Essbase Studio?

I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?

so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info

Unable to create attribute dimension in Essbase Studio

Hi All,
As per the process,I am create an Attribute for an dimension as below
Hierarchy
Family(gen1)
SKU(gen2)
Attribute1(gen1)
SKU(gen2)
Attribute2(gen2)
SKU(gen3)
Here the issue i am unable to create an 2nd attribute parallel to first on i mean attributes are not creating as sliblings.
Please advise
Thanks,
SatyaB

I think I understand what you are asking. I think your example is something like
Products
---Colas
-----Coke
-----Diet coke
Bottle (attribute)
---Coke
Can (attribute)
---Diet coke
This is not the way attributes work, you would have a column in your soruce perhaps called container_type that has the relationship
Container_type
Sku
So the rows would look like
Sku----Family-----container_type----other properties
coke...Colas........Bottle............XXXXXX
Diet Code..Colas...Can.............XXXXXXX
This could be in your primary table or a joined table

ODI Planning Attribute Dimension

I have an existing Product dimension that was created via ODI 10.1.5.6 to Planning 11.1.1.3.03 -- the Product Dim loads fine. Then I attached an attribute dimension called "Product Line" to it using custom attributes. I added four attributes to attach to products. Then re-reversed the Planning application in ODI Planning Model. I can see "Product Line" attribute load dimension (to load new attributes) in the Dimension hierarchy in ODI. However I cannot see a new Column for "Product Line" under the "Product" dimension in ODI. Am I missing something??

So adding the manual dimension seemed like it would work. However it gave me an error as it didn't recognize it when I executed the integration. In any event, deleted the planning model, recreated it and reversed it and the field showed up. Fun stuff! Thanks again.

Best Practice - HLevel for Alternate Hierarchy

Good morning,
Our Account dimension contains both a standard and alternate hierarchy. We currently use the HLevel property to drive a variety of formatting (hierarchy indentations, outline for "data bottom", bold for "parent", etc.). The formulas we've developed for the standard hierarchy work well, but they don't always work with the alternate hierarchy. I'm considering the creation of a new "Alt_HLevel" property that would contain the associated numerical hierarchy levels for the alternate. This would provide a level of simplicity in reporting as it would allow us to use consistent formulas. Downside is the added maintenance. Before proceeding, I'd like to know if anyone has a better solution. Thanks!

Hi Kim,
As far as my understanding says, HLEVEL will work with the 1st hierarchy of your dimension. So, if you want, you can definitely go ahead by adding another property for the second hierarchy. But yes, as you have already figured out, the cost would be at the maintenance. If you are having regular additions to your dimension, it might be difficult to maintain this property. If the addition of members is not frequent, then I dont see any challenge.
Alternatively, you can try using H2 when you are calling the HLEVEL property. I have never checked this, so not sure whether it will work or not. But worth trying.
Hope this helps.

Is there possibility to add dimension value into hierarchy using dml or spl

1 Is there possibility to add dimension value into hierarchy using dml or spl?
If such possibility exists how to do that.
2 Is it possible to sort dimension values inside one branch of the hierarchy?

What version of OLAP are you using and how did you create your AW (e.g., AWM)?
Assuming that you're used either AWM or the Java API for AWs in 10g, there isn't an OLAP DML for adding a dimension member to a dimension (and have all the meta data kept in sync); you must load dimension members using AWM the Java API for AWs.
So, make your changes in the the dimension table and process that table.
For sorting, you can add a sort attribute to the dimension. Add the sort attribute to the model, indicate that it's used for sorting, add the sort attribute to your dimension table and maintain the dimension.

Hierarchical attribute dimension with Essbase Studio

Hi everybody,
I need to load product dimension which is organized in a relational parent-child table like this:
(parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has its own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
(brand_parent, brand_child, brand_alias).
I need to do this load with Essbase Studio but I do not known how to create the Product hierarchy in cube schema in order to load the hierarchical parent-child attributes. Documentation and tutorials only show examples for flat attributes. I thought of these two ways but not sure if will work:
case 1) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand_child
Member_code
case 2) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand
Member_code
Has anyone had to this? How did you do it?
Any help will be very appreciate.
Thank you,
Daniela

I've not tried it, but you should be able to build the attribute hierarchy within the product hierarchy. sort of like
Parent Code
---member Code
Brand Parent
---Brand Code
-----Member Code.
A couple of things
1. Remember to create the self join between Parent_code and Member code
2. IF this does not work, I suggest creating either a user defined table or a view that just gives you distinct brand parent and Brand Code. Join the Brand Code to the product table on brand_code = brand code and use that table to build that hierarchy.

Attribute Dimension or Alternate Hierarchy

Similar Messages

Maybe you are looking for