EIS - Dimension Rebuild

HiWe are using EIS to rebuild a the department dimension every month. Some departments (level 0) move within business units (level 1). I have done all I can to get a department (dept1) to move from one business unit (Customer Support) to another (Maintenance). Within EIS I have defined a recursive parent/child relationship within the source Oracle table. Within the metaoutline for the dimension holding Business Units & departments I have selected Properties: Outline Build and "Allow Move" within "Duplicate Member Names". When we rebuild the dimension (using incremental build) I get a nasty error message telling me dept1 cannot be loaded as it is a duplicate. There is only one dept1 in the source table from the star schema. I can only conclude that the "duplicate" error message applies to the Essbase outline and the "Allow Move" in "Duplicate Member Names" means Duplicates in the source table!. When I manually go and edit the generated load rule to "Allow Moves" and then do a dynamic dimension build the results are as expected - dept1 move to Maintenance! HOW can I get EIS to move the level0 member (dept1) to it's new parent (Maintenance) ??

pls provide me the details of true dimension and also when we are creating the dimensions it is saying the latter option what does this mean

Similar Messages

Reg. Dimension deletion

Hi,
we can delete dimension member hierarchy through EAS manually.
but is there any other way of doing..
for eg. 'testdim' is a dimension
testdim
t
- t1
- t2
s
- s1
- s2
I want to delete the hierarchy under testdim..plz suggest
Thanks,
Ram
Edited by: user8774295 on Sep 24, 2010 7:42 AM

To add on to what Srinivas wrote, there are a variety of techniques for dimension rebuilds.
The most common one is, as he wrote, to use the "Remove Unspecified" dimension load rule option paired with a data source that has a member that will never ever be in your database, e.g., "goobledygook", or some other ridiculous name like "Cameron". This clears the dimension.
Then the next step in automation is to load the new dimension structure. It's up to you whether you combine this with a data clear and reload all data (presumably without the dimension members that no longer exist).
You can put this altogether into a single MaxL statement that clears and rebuilds the dimension through an incremental dimension load whilst preserving data such as below:
import database Sample.Basic dimensions
     from local text data_file "d:\\DataFiles\\ClearAcct.txt" using server rules_file "BldAcct" suppress verification,
     from local text data_file "d:\\DataFiles\\Accts.txt" using server rules_file "BldAcct" suppress verification,
     from local text data_file "d:\\DataFiles\\MiscAccts.txt" using server rules_file "BldAcct"
          preserve all data on error append to "d:\\MaxLError\\AcctsLoad.err" ;
iferror "ErrorHandler" ;Lots and lots of choices -- application requirements will drive your solution.
Regards,
Cameron Lackpour

How to tag attribute member with standard dimension member in EIS

hi,
would any one please help me how to tag attribute member with standard dimension member in EIS
THANK U IN ADVANCE

In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

Unable to Create Fact and Dimension tables from the Tools menu in EIS conso

Hi All,
In the EIS console, I am unable to create the fact table and the dimension tables to produce my OLAP model from the TOOLS menu whereas I am able to create them by dragging from the left panel where the tables are displayed. I am geeting the below error message:
"An exception occured while retrieving OLAP model metadata. Please verify you are connected to the catalog and try again"
Any help appreciated.
Thanks,
Raja

I have fact and dimension tables in one server and i moved those stuff to another server.If I do that what happen to essbase and about totale EPM System.I want to know how to do this and what I can expect?
Please reply

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

EIS : parent child - member load gives duplicate across dimensions message

I am trying to do member load from EIS (version7.1) desktop using an ASO metaoutline. The outline does notget built properly for one of the dimensions. Message log shows one of the values is duplicate but there areno duplicate values. message log shows the sql similar to : ( backend database isOracle 9.2.0.4 connected with odbc/OCI) SELECT /*+ */ PARENT_ID, CHILD_ID, ALIAS_NAME,SEQUENCE_NUMBER from DIM1 order by 4 ASC Example data is:CHILD_ID PAREN_ID SEQUENCE_NUMBERROOT 1L1_1 ROOT 2L1_2 ROOT 3L1_3 ROOT 4L2_1 L1_3 5L2_2 L1_3 6L1_4 ROOT 7L1_5 ROOT 8 Message log shows the following line twice:Member "L1_3" is duplicate across all dimensions.Member "L1_3" is duplicate across all dimensions. I checked all the dimensions and member value is unique acrossall dimensions. Outline gets created as follows: ( L1_1, L1_2 and L1_3 show upas siblings to DIM1 instead of children). Outline DIM1 L1_2 L1_3 L1_4 L1_5 L1_1 L1_2 L1_3 Dimension has recursion defined in the model with PARENT_ID asparent column and CHILD_ID as Child column. 

Thanks John - still not quite working
I should give another detail / extra complexity
The "Geographic Location" dimensions looks like this:
"Geographic Location" (Gen 1)
"United States" (Gen 2)
"SC" (Gen 3)
"Unique Facility 1", "Unique Facility 2" etc (Gen 4)
The data I have would be for Facility 1, Facility 2 which are unique member names which just happen to roll up under SC in the outline. I would have thought it would just load directly to those members without needing to specify their parent values.
Do I need to specify [Geographic Location].[United States].[SC].[Facility 1] ? This seems like it's something that needs to be done in the source file rather than using the prefix/suffix features of the Rules File.

Eis true dimension

In eis i came across the dimension as a true dimension(Account dimension) what it is please tell very urgent .
Thanks in advance

pls provide me the details of true dimension and also when we are creating the dimensions it is saying the latter option what does this mean

EIS - OLAP Model - Dimension Joins

Hi,
I know the in EIS OLAP model we need to build a logical STAR schema between dimensions and fact tables with some join condition. Now, can you tell me how the join works while building the dimensions? Do EIS really bother about the joins between dimension and fact tables? My understanding is, EIS will load all the members present in the dimension table irrespctive of join clause.
Pls shed some light on this!
Thanks!

You can join tables together with a "bad" JOIN. Your outlines will still build and probably look fine, however, this is what I tend to think of as a "dirty" EIS model. You will run into issues if you try and load data through EIS but you can probably get the outline to build how you want it. I highly recommend that you try and do things the "right" way as it will pay off in the future, but if you have to get it done some other way.... well, I've seen worse. :)

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.

How to create a parent-child dimension in EIS?

Does anyoe know how to create a parent-child dimension in EIS? Helps.

It's easy but there are a few things to know.
-The underlying dimension table must be a 2 column recursive design. It can also have additional aliases and property columns.
-in the OLAP model you must do a "self-join". select the table properties | physical joins. then join the parent to the child within the same table
-in the metaoutline drag only one column, not both (i like using the child only) to the dimension in the metaoutline panel.
If you need more help email me ([email protected]) and I'll do a webex demo for you.
Ron

Rebuild the Dimension Flushes out Cube data

Hi David ,
I want to change the implementation details of one of my dimesion from Surrogate key to "use key data sources" . After Applying my dimension data gone ..
Now ran below :
exec dbms_cube.build('CUSTOMER using (LOAD NO SYNCH,COMPILE)');
I expect the cube compilation would be done retaining my old data with the change in dimenisons only .But all the Cube data flushes out . Any way to get this back without running complete cube load again .
Many thanks,
DxP

No, I am afraid you will need to reload the cube. Switching to "use key data sources" means that we have to remove all of the existing dimension members and hence associated cube data.

Adding New Dimension In An Existing Cube (Block)

Hi fellows,
Im not an expert so need you feedback.
I am supporting a cube that was built a decade ago using Essbase 6.5. It has 7 dimensions (3 dense, 4 sparse). With the new reporting requirement, I need to add a new dimension to be called "BaseTimePeriod" that seems like a Time dimension but will show the "Constant Dollar" amount calcuation for difference Scenarios.
Since the cube has been there for so long, and the expert that has pioneered that cube is no longer in the company. All of our reports uses API being called in MS Excel to retrieve data from the cube and format it the way the users wanted it to be. As well as 75% of our data are user input using the Essbase Excel Add-in, "lock/send" commands.
My problem now is that, since I need to introduce another dimension for the "Constant Dollar" calculation, is there any way that if I add a new dimension the existing process of uploading data by the users as well as retrieving data through Excel API will not be affected?
I tried to add new dimension in the R&D server that we have when I try to retrieve historical data from the cube in the Excel since there is "BaseTimePeriod" dimension before, the Excel report layout gets affected and inserts a new row placing "BaseTimePeriod" in that cell since this not yet there before. And when I try to upload data through Excel Add-in "lock/send" action, it did allow me unless I put a member from the "BaseTimePeriod" to complete the dimension member combination.
My questions now are:
1) How can I add a new dimension without impact from the historical data?
2) Is there any way to place a default value for the new dimension for the historical data so it would complete the dimension member combination, so whenever I retrieve and upload data there will be no problem?
Any insights related to this questions is highly appreciated. Thanks!
obelisk

If you add the new dimension to a cube that already has data, you should get a prompt when you save the outline to associate the existing data with a member from the new dimension. You will then go into a dense restructure which could take a while, depending on the size of your database. Another option would be to export your data in column format and load it into a relational table in something like SQL or Access, you can then add the new dimension to the export in the relational tool, export it back out to a text file and use a load rule to reload it.
As far as the lock & send and existing reports, in most cases, adding a new dim will result in all of those needing to be updated. This is why we try not to add new dims to existing cubes, especially ones that have been around a while.
Another thing to consider is the impact of adding a new dim. I don't know the size of your existing database, but you are going to increase it by adding a new dim and things like consolidation time and retrievals can be impacted, so you need to test all of this.
You should evaluate why you need a new dim and determine if you can achieve the same result without adding a new dim. While a new dim might be the preference in a new cube design, when dealing with something that has been around a while you might want to be creative and somewhat more compromising if it is the lesser of two evils. If everyone is committed to a rebuild then go ahead and rebuild especially if it's been around a while, there are probably other things that can stand to be cleaned up as well, but if nobody wants to deal with that, then look to see if you can get their without adding a new dim, perhaps a new roll up in a existing dim or an attribute dim. A more thorough explanation of what the business case is would help to provide an alternate solution.

How to filter records in EIS drill through using template SQL

Hi,
I'm looking for an option to filter records in EIS drill through using Template SQL.
For eg: If we user runs drill through on 2011, it should restrict display of Jan & Feb and should display records for other months.
I tried using NOT IN clause, but got an error.
Can any one help me in understanding how this needs to be defined in template SQL
Thanks in advance

Hi Glenn,
I'm able to filter the records for specific periods.
However, I'm facing another problem now.
When I try to run drill through I get 'OLAP_error (1192025): Unknown Error: Not a valid Entry' error.
This is happening when I include condition as ((($$ab.ACCOUNT_CODE-COLUMN $$) IN ($$Account-VALUE$$)))
Here, ACCOUNT_CODE is field from Account dimension table and 'Account' is the name of the dimension.
If I remove this statement and run drill through, it runs but shows data for all accounts (irrespective of the Account selected)resulting in incorrect data.
Our RDBMS is Oracle. Can you please help me with this
Thanks

SB04100 Sound Blaster Card not working after computer rebuild

=SB0400 Sound Blaster Card not working after computer rebuildZ I did a full disk format and reinstall for a friend on a Dimension 3000, running XP SP3. There is no sound at all. Speakers are good, tested on another system. Model number on the back of the sound card is SB0400, so I assume this is an older 24 bit PCI SoundBlaster card. Although I reinstalled all drivers from Dell, I found no drivers for this. The Creative site has no listing for this model.
Computer does not seem to recognize the card. Have not opened the box yet but I assume if I were to remove and then reinstall the card it would be recognized (?) I then have to find an SB0400 driver.
Does anyone know where I can find an SB0400 driver ? Does the strategy of pulling and reinstalling the card make sense ? (I have really avoided tampering with any of the hardware on this box -- since it is not mine.)

Re: SB0400 Sound Blaster Card not working after computer rebuild? Thanks much for your response. Problem solved for now. I removed the board and then reinserted it, after which I was able to download the drivers directly. Some of my difficulty with this whole process has been ) I didn't know there was no working speaker in the computer and 2) I apparently misunderstood the BIOS settings for this. I re-set it up as an add-on board during the troubleshooting process. After loading the driver, I went back to the original setting (don't recall what it was but it was for integrated sound). The setting for integrated sound works fine, with external speakers and the new 24 bit driver. Still some noise (popping and static) but this board shares the bus with 2 other cards one of which is a wireless network card. May be a PCI latency issue but I'm reluctant to change that because the network card is a bit shaky anyway.
Everything works for now -- I'll be glad to get this particular computer out of my house !

[39008] Logical dimension table has a source that does not join to any fact

Dear reader,
After deleting a fact table from my physical layer and deleting it from my business model I'm getting an error: [39008] Logical dimension table TABLE X has a source TABLE X that does not join to any fact source. I do have an other fact table in the same physical model and in the same business model wich is joined to TABLE X both in the physical and business model.
I cannot figure out why I'm getting this error, even after deleting all joins and rebuilding the joins I'm getting this error. When I look into the "Joins Manager" these joins both in physical as well as logical model do exist, but with consistency check it warns me about [39008] blabla. When I ignore the warning and go to answers and try to show TABLE X (not fact, but dim) it gives me the following error.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TABLE X.column X Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT TABLE X.column X saw_0 FROM subject area ORDER BY saw_0
There is one *"special"* thing about this join. It is a complex join in the physical layer, because I need to do a between on dates and a smaller or equal than current date like this example dim.date between fact.date_begin and fact.date_end and dim.date <= current_date. In the business model I've got another complex join
Any help is kindly appreciated!

Hi,
Have you specified the Content level of the Fact table and mapped it with the dimension in question? Ideally this should be done by default since one of the main features of the Oracle BI is its ability to determine which source to use and specifying content level is one of the main ways to achieve this.
Another quick thing that you might try is creating a dimension (hierarchy) in case it is not already present. I had a similar issue few days back and the warning was miraculously gone by doing this.
Regards

EIS - Dimension Rebuild

Similar Messages

Maybe you are looking for