Dim build

Hi Folks,
I would like to create Dimension Building using rules file with the follwoing metadata ,what are the steps have tofollow can any one give suggestions how to build using the following
ACCOUNT,PARENT,ALIAS,ACCOUNTTYPE,VARIANCEREPORTING,TIMEBALANCE,EXCHANGERATETYPE,DATATYPE,DATASTORAGE,
TWOPASSCALC,MEMBERFORMULA,DB1,AggDB1,DB2,AggDB2,DB3,AggDB3,UDA,AttributeDimension
Any help on this appreciable.
Thanks.

Hi,
It is little bit descriptive to define all steps to build dimension using rule file here. I will siggest you to please go through follwoing link and I am sure it will definetly help you - http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_dbag/frameset.htm?pt03.htm
If you have any doubts after it, please revert back here.
Hope it help you.
Atul K,

Similar Messages

How to use substitution variable in case of dim build

Hi all,
Lets say I have 3 sub vars - Prevmonth, prevmonth-1, prevmonth-2. These will change every quarter.
I want to build a cube which will have which will have only the above 3 months in the Fiscal dimension. This will be used once at the end of quarter.
How do I refer substitution variables in case of dim build rule files? I want automate the process. We have SQL dim build for other dims, only this dim can be built from flat file also.
Or is there any other way to achieve this apart from using sub vars? I can try store the 3 variables in a table and then use them to build the cube, but want to see if we can avoid creating one more interface.
Thanks.

Actually using the values of subvars to build a dimension (which I believe is what you want) is a fun problem. Here's an (Oracle) example that would do that, without requiring any additional table or flat file:
 SELECT 'FiscalPeriod' AS Parent,
 CASE Level
 WHEN 1 THEN '&CurrMonth'
 WHEN 2 THEN '&PrevMonth'
 WHEN 3 THEN '&PrevMonthMinusOne'
 END AS Child
 FROM Dual
CONNECT BY Level <= 3
Here's how it looks in the load rule SQL dialog, and the data prep editor:
It's fun because I've never thought about it before, but I don't actually recommend this - if you have other ETL going on in SQL I'd generate the values in a table / view there, and have a script that both updates the subvars and builds the dimension direct from that.

ASO dim build

Every month I build a dimension that may have a few new members added. I am getting a lot of these error messages, \\Record #760 - Property [Location] changes for member [BBDX] not allowed (3315) The new members are getting added and the error messages are from members that already exist. What is it from and how can I get rid of this error message? (The dim build file will contain the complete dim hierarchy every month, I can't just load a file w/ new members) Jim

Jim: In your load rule you must be setting a property - like a consolidation operator, storage setting, or attribute - on your members. When you run the rule the next time and Essbase sees the property already set on the member and a non-blank field in your data source for the member's property, it treats that as a "property change", even though there is nothing changed. Example: The first time you run a dimbuild, you set member ABC with the consolidation operator '+'; it sets it as it should - life is good. Next time, when Essbase gets to the same member, it says to itself "hmmm...I'm being told to set the property on 'ABC' as a '+', but it's already set. I don't see the 'Allow Property Changes' checkbox being set, so I'll not set the property again, throw an error and move on." Essbase, in all its wisdom, is unable to tell that changing a '+' to a '+' isn't a change - it simply sees a non-blank proprety field in the source data and throws the error. Make the problem go away by checking the 'Allow Property Changes' box in the Dimension Build Settings dialog. That's it!

Dim Build Warning

Anyone know what this means?
Data file cache size ==> [0] Kbytes, [0] data file pages
Allocated TRIGMAXMEMSIZE: [4096] Bytes.
Loading New Outline for Database [CP_Ace] Succeeded
Missing Database Config File [D:\Hyperion\products\Essbase\EssbaseServer\APP\CP_Ace\CP_Ace\CP_Ace.cfg], Query logging disabled
Total Restructure Elapsed Time : [2.484] seconds
Object [CP_Ace] unlocked by user [MikeHa]
Database import completed ['CP_Ace'.'CP_Ace']
Output columns prepared: [0]
The rule works, the dim builds, but this warning appears - just wondering what it means. Why might one have a missing Config file?
Thanks for any insight, Mike

I'll guess from the message this is a BSO cube. It just means that query logging is not turned on. It is no big deal. If you want to learn more about Query logginga nd BSO databases, check out the section on it in the tech reference. http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/frameset.htm?launch.htm

'Invalid Dim' error during dynamic dim building

Hi Folks,
I am trying to update an outline using my own dim rules file and data .txt file, but i get an error in the dimbuild log file saying "\\Column 7 - Invalid Dimension" What could be the reason for this? The outline already contains 5 standard dims (i.e. Customer, Period, Account, Scenario and Year) and 2 more attribute dims. My goal is to add some new members to the existing Account dim. My data file looks like this:
Account,Metrics,,O,~
Metrics, Avg_Wolverines_Juggled, Average Wolverines Juggled, S,~
Metrics, Avg_Dropped_Wolverines, Average Dropped Wolverines, S,~
Metrics,Headcount,,S,~
In the data-prep editor I have created a .rul file that has 6 columns (fields). The first field I created by mistake, so I have set it to 'ignore field..' under 'dim build properties'. The next 5 fields map correctly to the way I have arranged my data file, i.e Parent0, Account Child0, Account Alias0, Account Property0, Account Property0, Account
This .rul file validates correctly, but when I try to update the outline, I get the "\\Column 7 - Invalid Dimension" error log message. The log msg says that the data file contains an error, but may have partially loaded data. However, I don't see a SINGLE new member added to the outline..
In terms of settings, everything under 'Dim Build Properties' seems fine. i.e. for each field the correct dim type (e.g. Parent, Child, Alias, or Property) and dim name (i.e. Account) is selected. However, under 'Dim Build Settings', when i try to choose 'Account' as the dim name, it reverts back to the name of the first dim in the outline (i.e. Customer) whenever I close/reopen 'Dim Build Settings' This happens even though I do a double-click and make sure 'Account' is shown in Blue before closing out of 'Dim Build Settings' Could this have something to do with the error I am getting? I have also made sure that the 'Build Method' is correct (i.e. Parent/Child references) for the two main dim fields. As per my understanding, for alias and properties fields, the Build Method doesn't matter.
I apologize for the long question, but would really appreciate some help.
thanks,
Akshay

Ah good old wolvering Juggling. The problem is they will bite you if you are not careful. (It's a nice metaphor for essbase). learning from Edwards book I see.
your file looks like it only has five columns and you say you created a sixth column that you set to ignore. The message indicates there is a 7th column. Open your load rule and your data file and see if in fact there is a trailing column. Also, make sure you set the dimension build properties for the account dimension to be parent/child

Automate dim build

I am using MaxL and Rules file and I want to; delete all members of a dim, then build it with current text file provided. Are there MaxL commanda for deleting a DIM or can it be done from a rules file? Jim

There is no direct MaxL command to delete a DIM, but you can remove all members of a dim thru a dim build rule and an empty file. Sometimes rather than removing them all it works better to append one dummy member while removing unspecified. If your dim is e.g. dyn calc it will complain if you try to save with no child but it's happy if there is 1 dummy child. Then your rebuild must remove unspecified, that will toast the dummy.

EIS - Essbase Dim build

We are using EIS to build and load a cube from some duzey Oracle tables. Anyway - the specification (from "Consultants R Us") is that within the Accounts Dimension GL Codes will role up into report lines by aggregation - EXCEPT for some Departments which will role up by subtraction. eg. GL123 is added to RepLin01 for Dept1, Dept2 & Dept3. However GL123 is subtracted from RepLin01 for Dept4.Is there anyway (attributes, aliases, anything) that would allow the correct calculation to be done IN THE OUTLINE and not in a script?There's a beer riding on this one!!

This problem can be solved if we use recurrsive structure of dim table with columns as ( Line Item, Parent code, Unary Code) then essbase will roll up according to the unary code specified in the dim. table.Let me know if this makes sense

Parent child dim build??

Hi,
In parent child reference method can we build dimension order like child-parent-properties....? coz my source file is coming in child-parent-properties format.
How I can achieve this??
Thanks

Yes, you can build the dimension using the Parent-Child technique as per your source.
In the dataprep editor, select the field1 (which is Child as per the source file) and select the option "Move" so that it will be field2 and Parent member will be in field1

Dim Build Error

There isn't any keywords or reserved words for dimensions, are there?
I'm building dimensions from a sql call, it creates all of them except for "OTHER" which gives the following error:
\\Record #10 - Incorrect Dimension (Region) for Member OTHER (3308) OTHER

This is a common problem in the essbase world and a reason many cubes have prefixing. Unless you are working in system 9.3 and have elected to allow duplicate names, you have simply used the name other twice in two different dimensions.
This is confusing to those with a relational database background because Other Region should be different from Other Product and Other Customer. You need to remember that the labels such as Othe can be used by an end user at anytime in any position. So you need to make each label in your database unique. The time tested process is to prefix (or suffix) all the members within a dimension. So all of your products could be prefixed with a P and all of your regions with an R. Or you could prefix with Prod or Product. As the moment you are only having the issue with Other, but it could happen when you have a saleman named West and a region West, etc. So the prefix solution allows you to have things run on autopilot.
Two other options, in the dimension build rule, you could change Other to Other Region. This is the easiest solution for a business owned application.
The other choice is to change your ETL so Other Region comes in your file as Other Region.

Automate EIS dim builds and data loads

I want to automate the dimesion builds and data loads from my ETL tool (DTS). I have not been able to find anything about scripting EIS automation in the documentation. Is there any?

what you can do is create go into EIS metadata outline and create a member load and data load script. Do this by selecting the Outline menu item, then select member load. click next, on this screen, select only save load script. Click the button "Save scripts" to give it a name. click finish. repeat for the dataload script. (If you are using ASO cubes, you must use separate scripts, you can't do both in one script)Then create a batch file to run the member load and data loads. In DTS, use an execute process task to run the batch file

ODI Dim Build - Mapping Issue

I have an ODI interface where I'm building my Cost Center dimension in Hyperion Planning. Is there some special treatment of the mapping syntax when you have a dimension with a space in the name? I can get it working just fine if I rename the dimension to "Cost_Center" (with an underscore), however I have been unable to get it working if the dimension is "Cost Center".
I've tried using a quotes and brackets within the mapping without any luck. Hopefully someone has solved this before.
Thanks!
- Jake

Hi Jake,
I had a look at changing a dimension to Cost Center and running an ODI interface to load from a file to planning, I didn't have any issues.
Where is the error occurring and what type of error is it.
Even though I renamed to the dimension to have spaces in the mapping the syntax is
COST_CENTER."Account"
I am using the sunopsis memory engine as the staging area for the mappings.
Cheers
John

EPMA - Load dim build with ADS Question

Hi,
I have a ADS file to build my Accounts Dimension. When I run it through the process all the UDA's which I have four of them on some accounts show up in EPMA just fine. When I deploy only one of them shows up in Essbase. Any ideas?

Heard there is a bug and Oracle is working on this issue? Didn't get any details as I'm unable to login to that part of system.

Dim Build Rule Strips Quotes - WHY?

I am trying to build a rollup with member formulas that use double quotes around the member names, but I can't get the load rule to stop stripping out the quotes. I've tried modifying the source text file to use regular quotes, triple double quotes, etc. I can't find a setting to make this stop. Does anyone have a solution? Thanks, James

I'm one of the folks who have answered this before, but I'll post it again here just to make it easier to find. Just use single quotes in the build file where you want double quotes in the formula and in the formula field in the load rule replace the singles with doubles. Remember to select the change all occurrences option.

Parent child dim build error??

Hi,
I'm loading members using parent child refernce method. My requirement is to load only level 0 members of already existed membesr from the outline.If data file has any new parent ,Essbase should kick out the new parent but should not load to the outline. Do we have any property for this in rule file or anywhere in EAS?
Im using EAS 11.1.1.3

To echo Glenn, you could use other approaches to pull dimensionality out of Essbase -- Applied OLAP's Outline Extractor, MaxL's export outline, etc.. get that output into a table, and then write SQL to do the tests. There's nothing in a Load Rule that will do what you want. ODI is fine as well (I am a fan of the tool) but it isn't the only approach and at the end of the day, you will be writing SQL in ODI to do this test.
Regards,
Cameron Lackpour

Error in Essbase Dim Build

Hi,
I am getting error "\\Invalid Rules File, which was created using a newer version" in the error file while trying to load dimensions into my outline .

Well that sounds pretty self explanatory.
Are you using a Rules file which was created with a newer version of Essbase?
Edited by: Sean V on Dec 12, 2011 7:37 AM

Dim build

Similar Messages

Maybe you are looking for