Attributes Dimension

I am having trouble understanding Attributes dimension. Can someone give a clear example and explain this concept to me? Also tell me how to view the Attributes in the Excel add-in.You can respond here or email me directly at [email protected] Lal

The best way to explain attributes are to go by example. Say you have an essbase database that tracks sales of products over time. So you have a Time dimension, a Measures dimension and a Product dimension.A requirement comes along where the business needs to analyze product profitability by package size - the size of the container each product is shipped in. In older versions of Essbase, there were 2 ways to do this:1) New dimension for package type2) Shared rollups in the product dimensionThese approaches work, but they add size and complexity to the database, which increases calc time. Also, the shared rollup idea starts to get cumbersome when you introduce more things - say product color. Now you have products shipped in different packages and in different colors. You can still create shared rollups for the colors, but now the business wants to compare sales of a package/color combination with a different package/color combination. You need even more shared rollups for the comparisons.Adding a new dimension creates all of the possible combinations of product, package type and color, but if you assume that these new properties are product specific, it adds sparsity to the database.In Essbase 6, you can create an attribute dimension - it looks sort of like a real dimension, but it works by piggybacking an existing dimension. You attach package type and color tags to each product, and you can then use the attribute dimensions to slice and dice the data as you would with real dimensions.By default, Essbase will sum all of the like attributes together to give you a total - sales for all red products for example. However, you can choose from Sum, Count, Min, Max and Average, all applied dynamically.Attribute dimensions do not show up in a default Excel retrieval. You can add them to the sheet by typing them into a cell manually or using Member Select. You can then use them as you would normal dimensions.Hope that helps a bit.Regards,Jade----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Similar Messages

Error While Building Attribute Dimension in ASO Cube

Hi all,
Cuurently I'm trying to bulit an ASO application in Oracle EPM 11.1.1.3
When I'm building an attribute dimension "QSize" in ASO cube ,I'm Getting some Warnings
I'm using Flat file as my source AND MY RULE FILE IS
GEN2,QSIZE, ALIAS2,QSIZE
1, ">100"
2, "100-249"
3, "250-499"
4, "500-1000"
5, "<1000"
I VALIDATED THE RULE FILES,
when i try to load the data into the essbase,Its giving me a warning stating that
Record #1 - Incorrect Syntax For Member <100 (3305)
*1 "<100"*
and i don't see the alias name for member 1
I came know that Essbase doesn't allow ">" character at the beginning of Dimension Or Member Name
Please let me know if there is Any other way,where I can Assign the alias "<100"
Thx in Advance
Regards,
RSG
Edited by: SG on Jan 22, 2011 3:03 PM
Edited by: SG on Jan 22, 2011 3:04 PM
Edited by: SG on Jan 22, 2011 3:06 PM

Could you get away with an underscore? I think that works. You will have _<100 which is not ideal but might be worth a try.
Failing that, go with GT and LT. <--This is incredibly lame, but sometimes users go for the "computer is too stupid" answer. Which in this case, is sort of true.
Regards,
Cameron Lackpour

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

How to design Flat file for loading attribute dimension in a planning application

Dear Gurus,
I have a requirement to extract attribute dimensions from an essbase application and load it to another planning application. I have a dimension called Program and two attribute dimensions Sales Manager, Accounts manager associated with Program dimension in Essbase application. I will Extract these dimensions using Essbase outline extractor. After Extracting the attribute dimensions I have to load these dimensions to planning applications using outline load utility. Kindly guide me how to design the flat file for loading attribute dimensions in planning application.
Thanks and Regards
SC

You could dig through the docs and try to figure out the file format manually, or you could do this the easy way. Simply use the Outline Load Utility to export your attribute dimension from Planning. The export file format is the same as the import file format. You might have to manually add a couple of test members to your attribute dimension so that your export file has some content. Then simply update the file you exported, and import it.
(I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
Hope this helps,
- Jake

Maximum number of Attribute dimensions Possible in BSO Cube

hi,
i have two simple queries :
1 - What are the maximum number of Attribute dimensions Possible in a BSO Cube.
2- How many attribute dimension can be associated with one base Dimension.
hope to get reply soon.
thanks in advance.
Regards
Anubhav

No Limits are defined as such:
How many Maximum number of Dimensions can create ?
Even in the Dbag, it says "many":
A base dimension member can have many attributes, but only one attribute from each attribute dimension.Cheers..
Rahul S.

Web Analysis data layout does not reflect newly added attribute dimension

Hi,
We newly added one new attribute dimension. If any new report creation in Web Analysis reflect that dimension. However, the reports which are old(created before the addition of new dimension), does not show the newly added dimension.
Please advice.
Thanks,
Meenakshi

Thanks for this.
I have tried assigning the new DB connection. However, still it did not work. Does the data layout displays dimensions according to reports. I mean, can we restrict the visibility of dimension at report level? Please advice.
Thanks,
Meenakshi

How to hide the Attribute dimension from Planning webform

I am in Planning 9.3.1
We are using members in row section of webform w.r.t Attribut dimension
so when we are viewing the webform- it is displaying member name followed by Attribute dimension name .
any way to hide that Attribute dimension member from the webform.
KK

In the Dimension Properties for that dimension, select "Enable custom attribute display" but dont pull the attribute from Available Dimensions to Selected Dimensions. I've given the name of the property from 11.1.1.3 version, so not sure if its the same in 9.3.1 but it'll be somewhat similar.
Cheers

Performance problem with attribute dimensions - please help!

Hi everybody,
I run OBIEE reports on top of EssBase 9.3 ASO cube.
My cube has 8 regular dimensions and 10 attribute dimensions.
I am running a query based on:
- 3 dimensions (TIME, BATCH, MODEL),
- 2 attributes of BATCH ( SHIFT, SHIFT_STATUS )
- and one measure.
The query runs 3 minutes (!) and returns 190 rows.
If I remove the attributes, the query runs 4 seconds for the same number of result rows.
My MDX:
With
set [TIME6] as 'Filter([TIME].Generations(6).members,
([TIME].currentmember.MEMBER_ALIAS = "2009/01" OR [TIME].currentmember.MEMBER_Name = "2009/01"))'
set [TIME7] as 'Generate([TIME6], Descendants([TIME].currentmember, [TIME].Generations(7), leaves))'
set [BATCHES] as '[DIM_BATCH_HEADERS].Generations(5).members'
set [SHIFT2] as '[SHIFT].Generations(2).members'
set [SHIFT_STATUS2] as '[SHIFT_STATUS].Generations(2).members'
set [MODEL2] as 'Filter([MODEL].Generations(2).members, ([MODEL].currentmember.MEMBER_ALIAS = "SNF_PCK" OR [MODEL].currentmember.MEMBER_Name = "SNF_PCK"))'
select
{[Accounts].[PROD_ACTUAL_QTY_KG]
} on columns,
NON EMPTY
{crossjoin ({[TIME7]},
crossjoin ({[BATCHES]},
crossjoin ({[SHIFT2]},
crossjoin ({[SHIFT_STATUS2]},{[MODEL2]}))))}
properties ANCESTOR_NAMES, GEN_NUMBER on rows
from [COP_MAAD.Cop_Maad]
Thank you in advance,
Alex
Edited by: AM_1 on Feb 26, 2009 6:35 AM
Edited by: AM_1 on Feb 26, 2009 7:03 AM

Hi Glenn,
I though that the reason might be the crossjoin with a very large set. The main dimension in this query has ~40000 members.
Is there in EssBase MDX some analog for NONEMPTYCROSSJOIN() function that exists in MSAS?
As these two attributes belong to the dimension that is used in the query, for every member of the dimension, there is one and only one member of each attribute. Therefore I though that Essbase should "know" how to behave.
Thanks for an idea. I will try to increase the space for aggregation - hope this will help...
Best Regards,
Alex

Calculation issue on attribute dimension

The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
"Two-pass calc skipped on member [X] in attribute calc"
Please advise on how to resolve this.
Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
It also says that Two-pass calculation member property is unavailable for attribute dimensions.
So does it mean that every two pass calc member is skipped?
I'm a bit confused.. how does it work?
Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
Thanks.
null
.

Hello,
I will give it a try:
<< I assume you have the two-pass calc member on the accounts dimension and the associated dimension of the attribute dimension is not the accounts dimension either. >>
Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
Hope this helps a bit.
Regards,
Philip Hulsebosch
www.trexco.nl

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.

Attribute Dimension members in Planning Data form

Hi All,
Can we see Attribute dimension members in Planning data form ? Pls. help

Yes it is possible in 11.1.1.3, for example in your row select a dimension that has attributes associated with it. select dimension properties next to the down drop.
Tick "Enable custom attribute display (setting applies to all dimensions with associated attributes): "
Select the attribute dimension
Cheers
John
http://john-goodwin.blogspot.com/

Is it possible to create an Attribute Dimension in an ASO Database?

When I create the initial attribute parent and attempt to save the outline, it gives me an error that I need to associate the attribute dimension with the base dimension. So I go to my L0 member, but the associations tab is greyed out. Any ideas if this is possible to create? Thanks!

OK, Are you doing this.
1. create the attribute dimension
2. click on the base dimesnion
3. right click on the DIMENSION NAME and selet edit properties
4. Click on the tab called Attributes. You should see the list of attribute dimensions
5. Once the dimension is associated with the base dimension, you can assign attributes to the members

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.

Create Attribute Dimension by rule file

Hi,
How can we create an attribute dimension and associtae members of sparse dimension with members of attribute dimension by using a rule file?
There is no option of 'Attribute' under dimension type in dimension propertites.
Plz help on it.
Atul K

First you have to create a standard dimension and made the storage setting sparse.
Then, you can create another dimension of type Attribute and associate it with the standard sparse dimension.
Then you can write rule files for attributes.
If you are assigning the attribute dimension MKT_TYPE to the standard dimension MARKET and the generation 4 is the last.
The typical rule file is like this:
Gen4, MARKET MKT_TYPE 4, MARKET
New york Big Market
Washington Small Market

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.

Attributes Dimension

Similar Messages

Maybe you are looking for