Import varying attribute dimension (with a load rule)

How do I maintain varying attribute dimensions in a model with a large base dimension? It does not make sense to manually maintain all those members in the outline.
Is it possible to import varying attribute dimensions (with a load rule)?

That is true for regular attribute dimensions. Nowhere, I have found instructions how to do this for varying attribute dimensions (aka slowly changing dimensions) that change over time.

Similar Messages

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.

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.

Associating attribute dimensions with the standard dimension in EIS

Hi... we need to bring 2 attribute dimensions in to the Metaoutline of EIS.These 2 attribute dimensions must be associated with lev 0 member of the standard dimension.how to achieve in EIS?
The current status: we did the olap model by mapping all the dimensional tables with the fact table and we are struck up how to bring the 2 attribute dimensions in to the model screen and association with standard dimesnion.
The table structure for the standard dimension is
column1/Gen-1     column2/Gen-2-Alis     consolidation     col3(Attr)     colu 4(Attri)
Reason-1     Reason-1-extension
Reason-2     Reason-2-extension
Reason-3     Reason-3-extension
col3 and col4 are attributes to be associated with column2.
Pls guide us the approach to be done in EIS..

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.

ASO Balnak Field Fill with Data Load Rule

In block storage database I could fill a blank field with a text value by creating field with text and then replacing whole word match with preferred text. I am unable to get this to work in ASO database. Field Properties tab has the option but does not work when I try to use it. Has anyone else encountered this situation?

Hi,
Thank you both for your answers. But what confuses me is this: I created a rules file using a file with 12 columns. I selected the appropriate member for each column in Field Properties, and added the View member in the data load header. Then I get the error message: "This field is also defined in the header definition" for all fields. However, if I don't set the members in Field Properties and just set them in the data load header, I get another error message: "There is an unknown member (or no member) in the field name."
Can you please help?
Thank you!

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?

Loading data with attribute dimension.

I have a currency attribute dimension asociated to Entities dimension and I like to upload data using the associated attribute dimension. I have a file with a column with the entity name and also a column with the attribute name. Could somebody tell me how to define the attribute column in the loading rule?
Edited by: user5170363 on Mar 22, 2012 12:55 PM

I guess, Attribute dimensions are not count while you load the data ..Data file always have the standard dimension members...
So you can filter your entities according to your attribute and load only on those entities...
Vivek Jaiswal

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

Essbase Load Rules File Header Issue

Hi,
Is it possible to specify more than one member for the same dimension in the Load Rules file Header?
Example: I need to load the same data in all the remaining months in current year.
I tried using a substitution variable in the header which is defined as Aug,Sep,Oct,Nov,Dec.
It loaded randomly. For each account, only one month is loaded.
It loads only as many data points as in the data file regardless of the number of members from the same dimension specified in the Header definition.
Any suggestions to correct this.
Using a Calc script to do a data copy cannot be used because of other process limitations.
Appreciate your thoughts.
Thanks,
-Ethan.

Randomly? That's really interesting. But yeah, I wouldn't expect that to work.
I have a hard time thinking of a really good option that will handle an variable number of periods and is driven by a single subvar.
Run the load multiple times, cycling through the subvar settings? Or (faster, if Period is dense) create one load rule for each period, with the data column copied multiple times using field manipulation and the future Periods assigned to each column (rather than using a 'Data' field) and run only the rule you need? That option doesn't use a subvar at all, but still requires conditional logic in the process.
Alternatively, do the transformation in your source extract / parse the file. This is really the 'best' option but I appreciate there are sometimes constraints on changing upstream processes.

Sorting Attribute dimension members

Other then reloading attribute dimension members in a different order. Is there a possbility with ODI or the SortMember.cmd utility to perform such a task?
I ask since I know presently while reloading the attribute dimension with ODI it drops the latest member to the bottom. This is not the order I need it in. I tried to mess with the load in ODI and still no fix. I tried to use the SortMember and it only appears to work on all dimension but currency, period, and years as it reads in the planning admin guide. This is for 11.1.2.1.
Does anybody have any input? If so please reply.
Thanks,
DjSmeadly

It is one area that has never been addressed so sorting attribute members is not so easy, as far as I aware the sortmember utility does not work on attribute dimensions.
Cheers
John
http://john-goodwin.blogspot.com/

Attribute dimensions may only be added to sparse dimensions

Hello everyone,
I got this error several times. It wouldn't be so surprising for me if my Account dimension would be set as dense. But it is set to be sparse...
Could anyone help me with this?
Maybe some details will be helpfull:
I have created an attribute dimension with only one member - "Yes". Then, I have created flat file for Account dimension with 6 custom properties, every property associated with the attribute dimension. Account dim is set as sparse, not dense. Importing flat file results ok, with no errors and warnings. Validating the application is ok.

Hi Andy,
I'm using only Plan1 and account dimension is set as sparse in this plan type.
What do you mean with "refreshing"? I'm doing redeploy of the whole application from EPMA. Or should I try refreshing the database from the application? I think the first step may be the redeploy. Or am I wrong?
Thanks,
Vlado

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

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

How to Build Attribute Dimension Dynamically & Load with LCM?

Hi, I'm trying to modify the existing outline at cilent's site. For some reason, when I pulled the outline with extractor, it didnt come out in the format that is compatible with Outline Load Utility. I was told to use LCM so I may still load with minimal to no modification to the existing structure of outline.
So can I build dimensions dynamically in EXCEL then load with LCM and push to Planning?

The log came back with many unrecognized headers in the outline. I spoke to Oracle Support many times, and they said that the format of our outline is improper for Outline Load Utility to read.
Since the outline has already been incorporated, we are not allowed to many any significant changes. That is why we were advised to use LCM.
I tried to use a sample of one of the existing attribute dimensions in XML as the base and build the new attribute but it failed. I would appreciate if you can provide steps by steps resources to show how to add new attributes to the existing outline.

Import varying attribute dimension (with a load rule)

Similar Messages

Maybe you are looking for