Dimension build rule file (Sort member)

I am loading sorted data for one of the dimension. But its is not coming in sorted fashion in outline. New member which i am adding is always coming in The end.Even though that member is in sorted format in the file.
I am using generation method . I am putting member for only generation 2 and its alias.I tried using ascending option but it is giving me error
Can any body help me with this

As Glenn said, the build only builds new members. In order to have FULL control over the order of a resultant dimension's order, you need to blank out the dimension first and then build via the load rule. As Glenn mentioned, you can do "incremental dimension building". You can do this directly in EAS in an interactive manner by using outline/update outline in pull downs. Just do not save the outline until all your changes are done. You can also accomplish incremental builds via Esscmd or via MaxL, but I'll assume for right now you are still testing. The advantages of the incremental changes is that you can do a number of changes before Essbase commits to doing a restructure, which is time consuming, not to mention confusing if you are "deleting" (however temporary) the entire dimension's hierarchy.
Regarding setting ascending order
1) in the load rule's Dimension Build Settings prompt
2) Select Dimension Build Settings tab
3) highlight the dimension you are changing
4) select Ascending for sort order
This should work...I've never had it error out. However, I will say that it sorts the entire dimension...not just the siblings of a new member. Your upper level members will move as well. Because of this, the ascending sort in a load rule is undesirable. Give it a try. If you don't like the results, just don't save the outline.
Kevin

Similar Messages

Err:Two-pass & Expence reporting properties from dimension build rules file

Hi All,
i'm trying to build account dimension from rules file along with properties.
My source file for dimension building is like below:
Parent,Member Name,Alias,Consolidation,Storage,Time Balance,TB Skip,Variance Reporting,Two Pass,Formula,UDA1:Account
Account,Acc1,,+,Dynamic Calc,None,None,Non-Expense,Two-Pass Calc,,Revenue
Acc1,Acc2,,+,Dynamic Calc,None,None,Non-Expense,Not Two-Pass,,Revenue
Acc1,Acc3,,+,Dynamic Calc,None,None,Non-Expense,Not Two-Pass,,Revenue
after building dimension 'non two-pass' values are showing as 'two-pass' and 'non-expense' are showing as 'Expense'.
if any one knows please let me know.
Thanks in advance.
Kiran

Try using member property codes :- http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/frameset.htm?dotrules.htm#dotrules_2
Cheers
John
http://john-goodwin.blogspot.com/

Get problem when create dimension using dimension build rule file

I got the following warning when I tried to load dimension. I have a product dimension hierarchy which contains 6 levels. I manually create a dimension call product which include six generations. I also create a rule file using SQL. This SQL selects 6 columns and I map each column to each generation. When I load data to build dimension, I always got the following warning and only some part of data get loaded. Anybody know that? Do I have to load parent first before loading child or I can load them at same time?
Thanks
\\Record #1 - Incorrect Parent [10] For Member [10] (3307)
1 2 3 10 10 171
\\Record #2 - Incorrect Parent [1] For Member [1] (3307)
1 1 1 8 8 39

You are getting duplicate names. YOu need to prefix or suffix (or sql concatinate) to make the members unique. in the record 1 example you might want the outpout to look like
Product line 1 Group 2 subgroup 3 Product family 10 product 10 sku 171
Of course I used full names to make it undersatandable, some would use one, two or three letter abrevaitions.

A problem happened when building dimensions with Rule File

Hi All,
I was trying to build dimensions with the rule file. But it showed the error 1030100, which means "cannot open file".
I can load data with a data source (.txt). Thus, I assumed that it's a problem to open a rule file.
I don't think it's the problem about the rule files I wrote since I cannot even build dimensions with rule files in the Sample/Basic database.
Anyone knows how to solve the problem? Thanks for the help.
Best Regards,
Anderson

854285 wrote:
Hi Prebhas,
Here are the error messages:
Object [Basic] is locked by user [admin]
Building Dimensions Elapsed Time: [0.016] seconds
Cannot open file: [E:\Hyperion\products\Essbase\eas\Client\dataload.err]
Unexpected Essbase error 1030100
Object [Basic] is unlocked by user [admin]
p.s. Even I re-install my system is English, the word "Client" is shown in Chinese. Is it possible this is the reason? If so, how I change the folder?
After I saw this message, I checked the folder and there is no such file. I tried to created one, but it disappear after I tried to build dimensions.
Best Regards,
Anderson
Edited by: 854285 on 2011/4/25 上午 3:27HI,
E:\Hyperion\products\Essbase\eas\Client\dataload.err
This path is referred to error message .... it will show the errors in that file...
and one more thing...
while adding data source to rule file it will ask you provide a path for the error message...there you can see this path...
Just check dataload.err file after running the rule file...
have you associated the out line to the rule file ???
is that rule file validate fine?
if not associate it and try...
Regards,
Prabhas
Edited by: P on Apr 25, 2011 4:43 PM

Dimension Build Rule converting characters to ascii

Hi
I have a dimension build rule which has been in place over a year. However every few weeks it converts some of the dimension members to ascii characters but loads with the correct alias. The next time the load runs, it tries to enter the real member and it falls over as the alias is not assigned to the member with the ascii characters.
Has anyone seen this before or have any suggestions as to what could be causing it.
Thanks

Have you tried recreating the load rule to see if it's some form of weird corruption?
That doesn't seem very likely (it's either corrupt or it's not <--This is why I Like Computers) -- how about can you confirm that your source is exactly the same both times? I'll bet it's not and you just see the result manifested in the dimension build.
Regards,
Cameron Lackpour

MAXL - using multiple Dimension build rules in single script...

I seem to be having problems running multiple Dimension build rules in a single MAXL script, is this a known problem or just an issue that I'm having? The build rules independently work as designed but when joined into a single script the script hangs...
So, this is a 2 part question...
1) Does MAXL not play nice when using multiple Dimension load rules in a single script?
2) Do I need to run the build rules independent of each other?
Also, is there some type of refresh/update on the cube that you can use in the script and would it be necessary...?
Thanks for any light you can shed on the issue.
Adam,

I've written multiple dimension build statements as a part of 1 long MaxL statement. I'm executing this MaxL via a shell script (that replaces the variables such as username, password, servername, file path etc.) I've not seen any issues doing so.
However, I've noted that, number of imports statements in 1 single MaxL command does not bode well for more than *60* import statements at once. So, if you're using more than 60 source files to build your dimensions, please consider breaking up your MaxL into multiple statements.
Note: All but last of the import statements have 'deferred' re-structure specified. It speeds up the build process.

Unable to build dimension thru rule file using export from DRM

Hi All,
I exported a dimension from DRM in parent-child format and trying to load it thru rule-file into essbase. Everytime i load the data..it is throwing error. Iam confused whether the error is due to DRM file or Essbase itself?
Actually i wanted to show the client the syncup between DRM and Essbase, this is kind of POC. I created an ESSbase application and using outline extractor, extracted the individual dimensions and then converted it into DRM import and loaded there successful. After creation of Properties there and added few members under the hierarchy in DRM.Again exported the dimensions and wanted to load into the same Essbase Application which should reflect the member additions did in DRM. But this DRM to essbase thing is not happening.
Pls anybody help me in this.
Regards,
Sahitya

Hi,
Is there anything in the error log file that is generated when you load it in Essbase??
You got to find the reason in the error file and then we can help you out on this.
Thanks,
Sourabh

Building RULES file to load shared members in Aggregate storgage outline

Hi there
I posted this yesterday (sorry, somewhat different subject description). I am trying to create an alternate hierarchy containing shared members using a load rule and flat file in an Aggregate Storage outline. One response was to remove the "allow moves" option and use parent child build in the load rule. I tried that and it did not work. i was pointed to a section in the essbase guide (which is about as clear as mud), and still cannot get this to work. First of all - can you do this with an ASO outline? If so, how? I tried a simple 6 line flat file and recreated the load rule based on the above recommendations and it will not the shared members. Can someone out there help?
thanks

Here is an example in the simplest form.
Create Aso db (duplicate members names not selected)
Create Product dimension member, set to "Multiple Hieararchies Enabled", (though probably would work if dynamic)
Create load rule, set as parent/child dimension build for product, make sure allow moves is not ticked.
Data file
Parent,Child
100,100-20
200,200-20
Diet,100-20
Assign field properties in rule for Parent.Child
Load data, 100-20 will be created as shared.
Cheers
John
http://john-goodwin.blogspot.com/

Dimension Build Rule Null Processing

Hi There,
I try to build Dimension Rule file with Generation build, I have Gen2, Gen3, Gen4, Gen5, Gen6, but some only goes to Gen3, so I check Null Processing, hoping this will take care of the issue.
However, I still got error "Child Member 368 with no parent"
I am using txt file as source.
wondering what I do wrong here, is this because Essbase think it is the space, not null value?
Thanks in advance.

Try to put a '\' before ".
You're formula will be
@RELATIVE(\"Dim Name\",0)
make these changes in the flat file or table and then try build the dimension.
Regards,
RSG
Edited by: RSG on Mar 20, 2012 10:37 AM

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

Create Outline by a bimension build rule file

How we can create a new outline by a rule file. I am able to create the rule file but don't know how to use to create the outline. Please help.

Check out this link:
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotrules.htm
After making a rule file:
Right Click on the database
Select Load Data
Check Buid only in the mode
Then locate datafile and rulefile.
Or click on the outline..
then in Menu select Outline menu, then update outline.
Cheers..!!!

Remove quotes from the data when building rule file

I get double quotes in one of the field in the file. e.g. Part descirpiton as inches. I have to join part number and part descrption to create one field and create level 0 dimension. When I try to replace " with space after joining the two fields, it does not replace the quotes. If I replace it first and then join the fields, it gives me error "The field type for this field is not valid for the build method associated with this field's dimension."
What am I doing wrong?
Thanks
Please help.

A double quote is one of the problem children of Essbase. If this is coming in from SQL, you could do a replace on the character to remove it. If it is a flat file, if it is always in the same location, you could split the field on the character and ignore it. It has been a long time since I've had to deal with the problem, but I think I ran my file through some preprocessing to remove it.

How to use Dimension Build to change member property?

Hello,
I have researched online on how to do this and I think i have an understanding but I cannot get it to work. My dimension build rules file is of type Parent Child. The fields are Parent, Child, Alias. I am looking to add a Property field to change the consolidation property to - for one member. I have checked off all the options required and tried several different ways but always come with the following error on that line.
\\Record #95 - Child Member - with no parent (3331)
P&L - ACC OPERATING Operating Expenses -
order is:
Parent Child Alias Property
What i want to do is assign the - subtraction for consolidation on the OPERATING member. Can this be done with the Parent Child type dimension build? Could this be achieved automatically in another way?
Thanks
Alex

Hey guys, thanks for the tips. The source file is tab delimited. I made sure there was a tab between Operating Expenses and the - for subtractions. The lines look like so.
REV_PROJ PS100001 - ACC PS100001 - ACC_PS-M9 Revenue Settlement
REV_PROJ SC100000 - ACC SC100000 - ACC_SCS Revenue Settlement
P&L - ACC OPERATING Operating Expenses -
OPERATING LABOR Labour
LABOR PAYROLL Payroll related
I know they don't show the tab but it's there. I have the field set to Property for Account_Desc (Dimension im updating in the outline) with a value of 0. I have also checked off "Delete when the field is empty" as to not change the consolidation on the other lines. i guess i need to figure out why it's treating the final "-" as a member and not as a part of the same line holding it's property. Is there a EOL delimiter i should be setting?
thanks again

Essbase Studio Deployment Dimension Build Errors

I have a ASO cube used to handle Subsidiary financial reporting to parent. Rather than alternate hierarchies, we use attribute dimensions for yearly differentiation. The ASO cube typically holds information for Current year + 3 prior years. This is the first year that we will achieve this as this cube was created near the beginning of 2010. Therefore, with the cube already having attribute dimension for 2010 & 2011, with the beginning of 2013 it is necessary to create the 2012 attribute dimensions. The cube has 13 anchor dimensions. Typically only 4 of these dimensions have attribute dimensions derived from them. Nonetheless, the following is the build list of the dimensions in the essbase model:
1: Financials Standard, Dynamic, Sparse
2: GL Date Time, Stored, Sparse
3: Incident Date Standard, Stored, Sparse
4: View Standard, Dynamic, Dense
5: Company Standard, Multiple-hierarchy, Sparce
6: Well location Standard, Stored, Sparse
7: Depletion Code Standard, Stored, Sparse
8: Vendor Standard, Stored, Sparse
9: Entity Standard, Stored, Sparse
10: Profit Center Standard, Stored, Sparse
11: Curr Yr Cost Obj Standard, Stored, Sparse
12: Past Yr Cost Obj Standard, Stored, Sparse
13: Measures Accounts, Dynamic, Existing
Attribute dimensions are mainly created in 4 of the Defined Hierarchies with in the cube; 1:FINANCIALS, 5:COMPANY, 6:WELL Location, & 10:PROFIT CENTER.
According to the Essbase Server log, upon deployment, the FINANCIALS Hierarchy generates 19 Dimension Build rule files with the associated SQL to pull members from our SQL Dimension Build tables obviously based on the way the Hierarchy is built as well as the joins created in the MiniSchema in the referenced Data Source. The COMPANY Hierarchy generates 5 Dimension Build rule files, WELL LOCATION generates only 1 Dimension Build rule file (this is mainly due to the fact that all the attributes generated from WELL LOCATION are built from the same table), and PROFIT CENTER Generates 3 Dimension build rule files. At this point for comparison purposes I want to include excerpts from the Server Deployment Log file depicting the dimension build rule files generated from the PROFIT CENTER Hierarchy:
Rule 1 Labeled XXXX_PRO.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON (cp_319.[profit_center_code]=cp_328.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul
… FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul
FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_276.[profit_center_code]=cp_328.[profit_center_code_2011]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
These Dimension Build rule files are recreated nightly on 4 different production servers, each one successfully redeploying nightly with zero errors.
So now I need to add the new 2012 tables to the Data Source/MiniSchema, create the joins in the MiniSchema mimicking the joins for the 2010 & 2011 Attribute Dimensions. It would be difficult to demonstrate the joins in the MiniSchema but trust me they are there and this is proven by the additional Dimension Build rule files from the appropriate Hierarchies.
So on our test server, which is configured exactly like all 4 of our production servers, I have begun the creation of the 2012 attribute dimensions. I begin with the FINANCIALS Hierarchy adding 7 new attribute dimensions, 6 that are cross table and one that is inter-table.
At this point no changes have been made to any of the other 3 Hierarchies that contain Attribute dimensions; COMPANY, WELL LOCATION, or PROFIT CENTER. They still look exactly as they did in the current state discussed above. Upon deployment, the FINANCIALS Hierarchy generates , as expected 25 Dimension Build rule files, 6 additional because only 6 were cross table attributes, the 7th was within the anchor table and therefore would be included in the first dimension build rule file. COMPANY still generates 5 Dimension Build rule files, again as expected. WELL LOCATION still generates only the 1 Dimension rule file also as expected. Lastly, PROFIT CENTER also again only generates the 3 Dimension Rule files, however, one has materially changed as noted below:
Rule 1 Labeled XXXX_PRO.rul
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center] cp_319 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 ON ((cp_319.[profit_center_code]=cp_328.[profit_center_code]) AND (cp_328.[profit_center_code]=cp_319.[profit_center_code])) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 2 Labeled XXXX_PR1.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2010] cp_275 ON (cp_275.[profit_center_code]=cp_328.[profit_center_code_2010]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
Rule 3 Labeled XXXX_PR2.rul (This one did not change)
…FROM [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_company_acct] cp_328 INNER JOIN [Essbase_XXXXX].[dbo].[vw_essbase_XXXXX_profit_center_2011] cp_276 ON (cp_328.[profit_center_code_2011]=cp_276.[profit_center_code]) ORDER BY cp_328.[profit_center_code] ASC, cp_328.[company_minor_acct] ASC`.
The change in Rule 1 above appears to now require something different from the previous deployment and when we run the deployment now it runs forever and ultimately fails, yet no changes have been made to the Hierarchy, no changes have been made to the MiniSchema involving joins to the tables used in the building of the Hierarchy, and no new tables have been added to the data source that would affect this Hierarchy.
Additionally, I have also run each of these incrementally, and the PROFIT CENTER even incrementally still makes the change to the SQL statement shown above.
So finally, to my question, Why and What caused this Dimension Build Rule file to change and ultimately led to deployment failure? Has anyone ever encountered this in Essbase Studio Deployments?

Gurus, anybody anything on this one??
I haave done a small adjustment in the dimension order by which I have eliminated the following error:
Record #40 - Error adding Dynamic calc property to member xxxxxxxxx (3320)
Record #40 - No time dimension defined
But, I have the following new error/warning (cube build successfull in this case) when I made this adjustment:
Record #427 - Error adding Attribute to member PATB4_ADJ-PDA (3320)
The adjustment I made is... I moved TIME dimension up and ACCOUNT dimension below that...so the order I have now is TIME,ACCOUNT,SCENATRIO,XXX,XXXX instead of ACCOUNT,TIME,SCENARIO,XXX,XXXXX ..*would this create any performance issues?*

Dimension Build Problems

Even the simplest dimension build rules files are not working for me. For example, I set up a test cube and tried to load 2 lines to a product dimension and it would not work. Is it possible that something is enabled/disabled that would cause this? I am at a loss, as the dimbuild.err file is not working either so I cant got there for guidance.

HI Dan,
1. When you say not working , what error do you get and when you start your build process( you need to set the file location for the .err file).
2. Can you give more details like the data file and your current outline,along with build information too.
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Dimension build rule file (Sort member)

Similar Messages

Maybe you are looking for