Changing an Attribute Dimension Hierarchy

I've had problems changing custom attribute hierarchies and I'm wondering if others have had similar problems and have a way to get around this.
I have an attribute (Program) of my entity field that currently looks like:
Program
Finance
P10001
P10002
P10003
Managment
Etc.
I'm trying to modify the hierarchy to look like this:
ProgramFinance
AccountingP10001
FPA
P10002
P10003
When doing this through the front end (hyperion classic admin), I don't see a way to cut/paste. Instead, I have to delete and then recreate the value under the new parent. The problem with that is that it drops the attribute value from all the entities that previously had it. I then have to search for those entities and add it back. Isn't there a way to just move or cut/paste the attribute to a new parent? I even tried ODI but couldn't get it to work (it gave me a successfully loaded message but didn't move the children values).
Thanks-
Cameron

I do have the interface in place already and reran it with the the new parents... Something like this:
Parent|Program|AliasDefault|Operation
ACCOUNTING|P_20001||Update
FPA|P10002||Update
FPA|P10003||Update
I get all success messages: "Number of rows successfully processed: 3" But when I go into the attribute dim in Hyperion Administration, the children have not moved.
When you say "Rebuild" is there a special Operation or something else that I can toggle to get it to accept the changes?
Thanks-
Cameron

Similar Messages

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/

Changing the dimension hierarchy level keys in RPD online mode caused issue

Hi,
We tried to correct the dimension hierarchy level keys and remove prefered drill path settings in the business model layer in RPD in online mode. However this caused all the reports and dashboards based off of this subject area to show incorrect, and/or restricted data. The physical query generated by the answers requests were also incorrect.
Even restarting the server and presentation services could not resolve the issue. Can someone please help us to understand what could have caused this issue?
Thanks in advance

Hi,
I am not sure why the existing reports throw an error when I change the RPD dimension hierarchy level keys. Does anyone know how I resolve this issue.
This is urgent. Any help will be most appreciated.
Thanks in advance.

Star Schema Dimension Hierarchy Changes Over Time

Say you have a dimension hierarchy with the level Department that has a child level Division. The Sales Division belonged to the Financials Department up until July 9th, 2011, after which it was moved to the Marketing Department. How can you make it so that both Sales Divisions are interpreted as the same Division, rather than two different Divisions as BI Answers does by default?

I don't think SCD1 would work as BI Answers essentially splits things via both keys and description fields, resulting in odd behavior such as this:
Time
Division
# Employees
All Time
Sales
16
22
Regarding SCD2:
So is there something I need to do on the repository so that BI Answers knows to switch between the two versions of the same Division at that particular time, such that I can make an Analysis such as this:
Month
Division
# Employees
% Change
May
Sales
15
-6%
June
Sales
15
0%
July
Sales
14
-7%
August
Sales
22
+57%
Instead of this:
Month
Division
# Employees
% Change
May
Sales
15
-10%
June
Sales
15
0%
July
Sales
2
14
-87%
0%
August
Sales
22
+57%

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

Oracle Business Intelligence Dimension hierarchy question

Hi,
I am prasanna.I have a problem while display the data from dimension hierarchy.I have created a time dimension hierarchy.I can drill down upto week number but i m unable to display the time_id(this is the last level of the hierarchy).When i check the properties of the time_id,the HIDE check is checked.Even if i uncheck the checkbox also i m unable to display that column.How to change properties of the column manually.I can find the column at the criteria but not at results tab.How can i display the column.
Thanks ,
prasanna

HI Prasanna,
what is the least granularity for your time dimension? is at week level or day level. verify the dim hier configuration in rpd. if you define time_id as level key you dont get that column in answers results while drilldown. you may create another logical column and drag it to week level as an attribute then you will get it. and why do you need time id in answers. generally we dont use id's for reporting.
try again after above configuration and you will be all set.
Thanks
Jay.

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

Changes in the Dimensions not reflected in the Current View and Excel Sheet

Hi Experts,
We're using BPC MS Platform Version 7.0.112 and we're having problems. When we make changes in the dimension members like adding members or making changes in the hierarchy or groupings, it takes time for the changes to reflect in current view or in the excel sheet. After full processing of the dimension we can see the changes we've made when we reopen the dimension member but when we try to use the member we've added in the template, it's not yet in the current view. I've already tried, full processing of all the dimensions, processing application and reassigning aql index, refresh dimension members and yet the changes we've made doesnt appear in the current view. And what's odd is that sometimes the changes we've made would appear after a day or two or nothing at all.
What could be possibly causing this issue?
Thanks,
Marvin

Hi Dzmitry,
Thanks for your response, I'm just wondering whats causing this? We never had this issue on older versions of BPC though, so it would really help if we would know the cause of this. Basicaly when do changes in a dimension, after processing (Full Process, System Offline and Process through member sheet), we just had to set the AppSet status to available and refresh the dimension members in Excel and all the changes would already be visible.
Thanks,
Marvin

Dashboard prompt on a Dimension Hierarchy in Obiee 11g

Hi All,
I have created a hierarchy (parent-child) on a dimension 'A'. I am able to create a dashboard prompt for the dimension hierarchy. However I am not sure how to create a report that is to be filtered on this dashboard prompt. I tried using the attribute name that the hierarchy uses but that does not work. Can some one please let me know how i can filter a report by a hierarchy dimension prompt.
Thanks,
Nikita
Edited by: user12438396 on May 8, 2011 1:16 PM

Hi Nikita,
For your requirement, you need to go for Selection steps pane in the analysis(report). Click on steps link and then add the hierarchy column that you want to use and expand the hierarchy to the lowest level. Now select all these and all the attributes will now appear in the other side.
If you dont expand the hierarchy to the lowest level, then only the highest level values will appear in your selection at prompt.
Also make sure to check the 'override' checkbox in the bottom, this helps in filtering the values.
Hope this answers your question.
Cheers,
Obul

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.

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.

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (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 it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

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.

Attribute Dimensions with Integration Services

Good evening, I'm creating an ASO Essbase model through Integration Services v9.3.1 and I am having difficulties with creating an Attribute dimension that contains a hierarchy.
We have a list of stock codes which are grouped by vendor in a dimension, each stock code has an attribute assigned to it for the buyer responsible.
The business requirement is to start from the top level of the attribute dimension, drill in to categories, then to drill in to teams, and finally to the buyer... so we effectively require 3 levels within the attribute dimension.
I have successfully created both the vendor (physical) and buyer (attribute) dimensions through EIS without problems, but when I load to Essbase all of the buyers are added at the top level of the dimension and I can't seem to specify that there should be a parent/child hierarchy to build the attribute dimension from.
Is this possible, and if so any advice you can give as to how I achieve this would be greatly appreciated.
Thanks in advance,
Graham

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.

Business Rule - Can you fix on children in attribute dimension?

HI,
Base Dimension: Service
Attribute Dimension: Service_Code
If I have the following hierarchy in an attribute dimension, how can I fix on all members of the Service dimension that have the attributes Model A, Model B and Model C attached them without listing them individually? Is there a way to fix on children of 'IMH Models' somehow?
Service_Code
   IMH Models
      Model A
      Model B
      Model C
   CAD Models
      Model D
      Model E

Hi
in the FIX use the @ATTRIBUTE("IMH Models"). By default it will fix on all base members associated with the children of the attribute parent you have specified. See below text from Tech Ref
Description
When @ATTRIBUTE is used with a non-level 0 member of an attribute dimension,
Essbase returns all base members that are associated with the children of the
attribute member. For example, in the Sample Basic database,
@ATTRIBUTE(Large) returns all base members that fall into one of
the population ranges for the attribute parent Large.
Thanks
Anthony

View dimension hierarchy using the filter property of data form

Hi,
I created a data form where I want to show the dimension hierarchy. But when I am filtering the form using attribute dimension then the hierarchy is not being shown in the form.Is their any way so that I can use the filter property also and make the dimension hierarchy visible in the data form?
Thanks.

847833 wrote:
Hi Endy,
Thanks for your reply. I have used the "equal" function as to set that specific attribute as I am choosing the descendants function against the attribute dimension,it's showing error.Hi,
What's the error ? You have to use a function, otherwise it will only display the member you picked.
Actually in our dimension structure we have a 3 generation hierarchy and the attribute is only associated with the 3rd generation member. So we want to display the 3rd generation having the specific attribute "xx" wit the entire hierarchical structure in our data form.
Can you please tell me if I have missed anything?
Thanks.If you want to display the attribute value in the form, edit the form, go to the "Layout" tab, and click on your row. On the right side of the screen, you have a section called Display Properties. Check the box called Enable custom attributes, then check your attribute name. Save the form and you will have the attribute value displayed at the right of the member name.

Changing an Attribute Dimension Hierarchy

Similar Messages

Maybe you are looking for