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

Similar Messages

Delete Attribute Dimension Using MAXL

Hi everyone,
Is there any option to delete attribute dimension using MAXL? Our requirement demands to delete and reload every night. Please suggest if anybody has did this before.
Thanks!

A post of the same sort of topic area :- HOW can i delete the members in dim using MAXL
Cheers
John
http://john-goodwin.blogspot.com/

How to create a Hierarchy Node Variable to be used in Infopackages ?

Hello,
I use BW 3.5.
I need to create a hierarchy node variable (filter) to be used further in Infopackages as OLAP Variable.
How can I do ?
Please give a step-by-step answer,
Thank you very much,
Thomas

Hi Again,
You can use ABAP program in the process chain.
I guess there are some OS level commands in ABAP which will allow you to open, close, read , write and move files.
Serach in ABAP help or on net.
Bes regards,
Sunmit.

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

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.

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/

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

Hierarchy based on one dimension.

Hi,
How to create a hierarchy based on one dimension. For example: we have table:
Category
Category_ID
Parent_Category_ID
I want to create hierarchy, which like as:
Category_Level_1
Category_Level_2
Is it possible without create new alias of table for each level?
Thanks

Which version of BO are you using?
Assuming that you are using BO XI R2 or above version.
And Is your question - how to create custom hierarchies in Universe Designer..... for two different fields (columns) taken from a single database table?
If so, yes you can create custom hierachy for above scenario. In Custom Hierarcies option: Add the Parent_Category_ID first and below that add Category_ID.
If you want to rename your hierarchy levels as Category_Level_1 & Category_Level_2, then rename their corresponding objects names in Clasess & Objects pane.
- Anil

Attribute dimension

Hi,
can we create groups in attribute dimension using rules file.
we can do it by manually , but i wanna do using rules files.please throw some light .
thanks
kishore

Yes you can, but you can't do in in the same rule that you assign the attributes to base dimensions in. You have to have a seperate rule to build the hierarchy

Attribute dimension build method

Hi All,
Please do let me know the process to build the attribute dimension using rules file. I tried it following the same way as any other normal dimension but donot get the property associated to the attribute dim. We want this process to be automated as we rebuilt the ourline each time during the load. Pleaes help.
Thanks,
Praveen

Have a read of the section :- Building Attribute Dimensions and Associating Attributes
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1060796
Cheers
John
http://john-goodwin.blogspot.com/

How to load data to attribute dimension

hi gurus,
I have two questions:
1. could I enter data into attribute dimension using SmartView?
2. how could i load data into attribute dimension using load rules?
Regards,
Daniel

Hi,
1.
You can't send data back into Essbase if your POV has an attribute specified. The attribute will calculate (by default it does a sum) your POV dynamically and only bring back data which has that attribute assigned to it.
If you want to send data back into Essbase then the easiest way would be to keep the same POV and just remove the reference to the attribute. Smartview will then let you send data back into the Essbase cube.
2.
Same answer as point 1. Attributes are ways of adding more detail to members that already exist. You dont' load data into the attribute, you load data into the member that the attribute is assigned to.
Hope this helps,
Gee

Create different hierarchy based on Dimension values

I have a dimension called period. This dimension is having 4 different types of periods. The period table looks as below. I need to create 4 different hierarchies for these 4 types of periods based on l1 to l5 values. But all these values are in the same
table. Is it possible in SSAS? If so please let me know how can I do it.

If i understand it correctly, you want one hierarchy for one row, then you need to flat the table in the view and then you can create those hierarchy. But it is no different from having one hierarchy with the table you have. your hierarchy is going to look
like "Priod5" <- "Priod4" <- "Priod3" <- "Priod2" <- "Priod1". this hierarchy will have all the values. Don't forget to use the composite key for each attribute except key attribute.
hope this is helpful.
prajwal kumar potula

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

Implementing hierarchy in a dimension using OMBPLUS script

Hi all,
I am trying to create a dimension with two levels using TCL scripts.
The first level is 'CHIP' which roll up to 'TOTAL'.
I'd like to know how I can implement the hierarchy between the two levels.
It would be great if any of you can help me with the syntax to implement the hierarchy.
Thanks,
Anoop

Hi Anoop
To add levels use SET REF LEVELS on the hierarchy, for example on dimension DIMX, hierarchy STANDARD;
OMBALTER DIMENSION 'DIMX' MODIFY HIERARCHY 'STANDARD' SET REF LEVELS ('TOTPROD','CATEGORY', 'PRODUCT')
Cheers
David

Creating a DWMQY DIMENSION using Analytic Workspace Manager

Hi everyone,
I need some help creating a "time aware" (DAY, WEEK, MONTH, QUARTER, and YEAR) dimension using Analytic Workspace Manager.
Let me give you some background. I'm coming from a traditional "Oracle Express" OLAP background where all our data is stored in cubes and these are defined, populated and operated on using OLAP DML, there is no SQL or traditional relational tables involved.
I now want to pull data from relational tables into some OLAP cubes and am using Analytic Workspace Manager to do this (maybe this is not the best way?)
Let me explain what I'm trying to achieve. In OLAP worksheet I can type the following DML commands:
DEFINE MY_DAY DIMENSION DAY
MAINTAIN MY_DAY ADD TODAY '01JAN2011'
What this will do is create a "day dimension" and will populate it with values for each and every day between 1st Jan 2011 and today. It will be fully "time aware" and thus you can use date functions such as DAYOF to limit the MY_DAY dimension to all the Fridays etc. Similarly if I define a "month dimension" there will be an automatic implicit relationship between these two dimensions, this relationship and time aware cleverness is built into Oracle.
However, a dimension defined using DML commands (and indeed all objects created using DML language) is not visible in Analytic Workspace Manager (as there is no metadata for them?) and for the life of me I cannot work out how to create such a dimension using AWM. If I create a "Time Dimension" then, as far as I can tell, this is not a proper time dimension but merely a text dimension and I, presume, I have to teach it time awareness.
Can anyone help me? I have no issues creating, and populating cubes from relational tables using Analytic Workspace Manager, the only issue I have is creating a "proper" time aware dimension.
Many thanks in anticipation.
Ian.

When a dimension is of type "TIME" in AWM, then for each member of that dimension, you need END_DATE and TIMESPAN attributes in addition to the key column and description column.
So in your case, if there are 5 levels: DAY->WEEK->MONTH->QTR->YEAR
then you will need atleast 15 columns in your source sql table/view
or 20 columns if you have separate column for description.
For example the columns in your source table/view could be:
DAY_ID,
DAY_DESC,
DAY_END_DATE, (which will be that day's date)
DAY_TIMESPAN, (which will be 1)
WEEK_ID,
WEEK_DESC,
WEEK_END_DATE,
WEEK_TIMESPAN,
MONTH_ID,
MONTH_DESC,
MONTH_END_DATE,
MONTH_TIMESPAN,
QTR_ID,
QTR_DESC,
QTR_END_DATE,
QTR_TIMESPAN,
YEAR_ID,
YEAR_DESC,
YEAR_END_DATE,
YEAR_TIMESPAN
Just "map" this table/view to the 5-level time dimension in AWM.
NOTE that behind-the-scenes lot of useful structures are automatically defined to support time-series measures,
and there are lot of calculation templates available also.
Since you came from Express background, I have to say that try to use new OLAP Expression Syntax when creating calculated measures instead of OLAP DML.
Its very rare these days that we need OLAP DML.
Edited by: Nasar on Nov 22, 2012 12:11 PM

Creating a hierarchy in an attribute dimension using EIS

Similar Messages

Maybe you are looking for