Essbase Build Dimension using load rules - Jagged Recursive hierarchy

Hi,
I am building a dimension from data that has the following parent/child relationship
PARENT CHILD
A B
C D
C E
C F
A C
Load dimension results in the following hierarchy:-
A
|__B
|__C
|_F
C
|_D
|_E
I would like the hierachy to be:-
A
|__B
|__C
|_F
|_D
|_E
Is there a way to achieve this? Is is to do with the order of rows in the data file?
Thanks
Dinesh

Hi,
I agree with the advice already posted about allowing moves in your dim build settings on the dimension in question. I just want to help clarify the other comment about how your file is sorted. As long as you are building a main rollup only (i.e., no shared member, alternate hierarchies in the same input file), the Essbase parent/child build method doesn't require any particular record order (as long as the pairings are correct in and of themselves). Essbase p/c method is powerful for ragged hierarchy creation and also able to "figure out" the intended hierarchy.
Now if you are including shared member relationships in the file, just be sure to have those records AFTER all records for the main rollup (logically as if you were simply using a second input file for the same rule). They don't have to be sorted within the rollup either.
BTW, the other strength of the p/c method is the ability to handle upper level shares (i.e., when your shared members are referencing members that are above level 0 in their stored (main hierarchy) positions.
Darrell

Similar Messages

Building BSO using ASO Rules file

Hi All,
We are building a new application where in we want to have both ASO and BSO. Eventually we wanted to do partition between these two cubes.
We already have a fully functional ASO with data loaded into it. This ASO also has bunch of rules files using which the ASO cube was built.
We need to build a new BSO and it should have same outline as ASO and in order to achieve this as used the same rules file that are in ASO. I already built the BSO usinng ASO rules files
My issue is with the dimension which are deifned as Multiplw Heirarchy and I would appreciate if some one can help me how do i define them in BSO. Also if some one canhelp me understand what are additional changes that needs to be taken care when I am building BSO using ASO rules files
I am trying to apply a caluclation which is in ASO and I am getting following error -- Error(1200337) - Error compiling formula for [Feb YTD] (line 1): [)] without [(]. As part of my research i found that error code is very generic. I checked the caluclation for missing ) or ( but everything looks good
Any help is greatly appreciated
Thanks
Satish

Your ASO formulas will not work in BSO cube. ASO uses MDX formulas and BSO uses Essbase calc script language. There is a guide in the technical reference that helps convert from one to the other.
As far as multiple hierarchies, BSO does not have this concept. You should be able to load the hierarchies as is with perhaps a few changes to the load rule to address how to handle shared members.
You will not have a direct one to one from BSO to ASO. They are a different architecture and as such have variances that are not 1 to 1 compatible.

Moving a parent in a Dimension using a rules file

I would like too move a parent in one of my dimensions to the bottom of that Dimension using a rule file
Please advise

I have a confusion over here. For instance:
If I have Margin (parent) Sales (child) and COGS (child) defined in the data source in that order, than how will I change it to sales, cogs and than margin in the data source.
Parent child build method has the following statndard format, if i am not wrong:
PARENT (say accounts) DIMENSION NAME (code say A10001) ALIAS (Margin) AGGREGATION (+) and DATA STORAGE (The code for store)
Thanks in advance

Sorting members using Load Rule Parent Child Method

Hi all,
I have a Product Dimension with around 7 gen's and wanted to sort Gen 3 members under parent (say CommProduct). All these members are initially loaded using Studio and i am trying sort Gen 3 members using a text file / Load Rule (Parent Child Method). I have "Allow Moves" ,"Allow Property Changes" and member sorting: None checked for the load rule. I tried updating the outline using the load rule, however the outline remains unchanged and members sorted by alphabets.
Essbase Version: 11.1.2.3
Current Hierarchy:
Product
           CommProduct
                                 A
                                 B
                                 C
                                 D
                                 E
Hierarchy Wanted:
Product
           CommProduct
                                 A
                                 C
                                 E
                                 B
                                 D
Dim Build Text File:
Parent,Child,Aggregation
CommProduct,A,+
CommProduct,C,+
CommProduct,E,+
CommProduct,B,~
CommProduct,D,+
Any help would be highly appreciated.
Thanks

Can't you create a column where you can specify the desired order and build accordingly. I don't think you can achieve that using a load rule. Allow moves works only if the members are under a different parent. In your case it is the same parent.
Regards
Celvin
http://www.orahyplabs.com

How to load shared members into a duplicate outline using load rules

Hello, I am trying to load an alternate hierarchy into the same dimension in an outline that accepts duplicate members using EAS load rules ... there is no property for shared members so i can't specify it in the load rule .. i tried using parent child and it is not working - no shared members are loaded in the alternate hierarchy .. any ideas? would another utility make it happen?
thx

You might find this useful: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm
Especially the Building Shared Members by Using a Rules File section: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1061244
Cheers,
Mehmet

Error 1003007 when loading using load rule???

I'm getting the following error when loading data using a load rule and could use some help in figuring it out.
"Data value [40] Encountered Before All Dimensions Selected, [424] Records Completed"
Does this mean that field 40 in record 425 has a problem? or is there another interpretation of this error?
I'm trying to narrow down the problem and have sifted through the data but see no obvious problem, any help would be appreciated.
Thanks.

No, what Glenn means is that you are likely missing a dimension from your data record. Entity you may very well have (and if it's the first column that should be easy to see) -- it's some other dimension.
Go through record 424 field by field -- I'll bet you're missing one. So if the data file would normally be 10 fields, record 424 is like 9 or less.
Regards,
Cameron Lackpour

Error when building dimension using AWM

Hi Gurus,
I am trying to build a dimension using AWM 11.1.0.7.0B Standalone. My Database version is _11.1.0.6.0._
The moment i start to create a New Dimension, i get the below error.
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::g
The transaction is not committable: "An error has occurred on the server
Error class: Express Failure
Server error descriptions:
DPR: Unable to create server cursor, Generic at TxsOqDefinitionManager::generic<CommitRoot>
INI: Unable to parse XML string sent from the client to the server, Generic at XML Parser Errors:
Error processing subelement: <StandardDimension><Attribute><BaseAttribute><Classification>
Error processing tag: Classification:
Error returned by xsOqXmlParserExecute.
+"+
+at oracle.olap.awm.dataobject.dialog.PropertyViewer.doCreateAction(Unknown Source)+
+at oracle.olap.awm.dataobject.dialog.CreateDialogHostActionThread.doAction(Unknown Source)+
+at oracle.olap.awm.ui.dialog.ThreadedDialogActionThread.run(Unknown Source)+
Please help!!!!!
+*Regards,*+
+*Ravi R*+

The initial release of OLAP in 11.1.0.6 was not stable. Please upgrade to at least database 11.1.0.7, and preferably 11.2.0.3. If you move to 11.1.0.7, then you should apply the "OLAP D Patch", #9147749. See the OLAP certification page for more details.
http://www.oracle.com/technetwork/database/options/olap/olap-certification-092987.html

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

Dimension Build Load Rule Reject Record

Hi,
I'm trying to create a load rule that build the accounts dimsenion with a flat file. I would like to exclude any accounts that starts with "S" from being added to the account dimension. I have a parent/child build method for this load rule. i'm using the Reject Record to set the condition that any string contain S will be rejected but for some reason when I load it doesn't do anything. it makes EAS freeze up. so, my flat file looks like this.
New Accounts,S50000,Accounts - S50000
New Accounts,60000,Accounts - 60000
New Accounts,S45000,Accounts - S45000

Hi,
Your posting does not tell me what you entered in the reject record setting to try to achieve the desired result. If you entered "S" and used the "Contains" setting it should have worked providing you know your data and don't have occurrences of this character possible other than in the first ordinal position. If you tried to use a wildcard asterisk callout, Essbase load rule select/reject logic does not take wildcard inputs (like "S*").
Instead, a tried and true trick of Essbase load rules is to make a copy of the field in question, split it up and take background select/reject action on just the first character of a reference copy of the original field. This is done by using the field "create on join" method and simply joining the field to itself (an unintuitive but effective way to make a copy of a field for use in the load rule settings). Having done this, now split the copy of the field after one character. The remaining field section can be set to ignore for dim builds (or data loads as you might have to do later to match your dim build results in data loads). Now you have a single character field for which you can set the reject setting of contains or equal to "S" and then... please get this part... ignore the field for dim builds in field properties. Essbase will not try to use this partial field to build anything since it is ignored, but the assigned reject logic on occurrences of the isolated single character field will still be interpreted.
This is old school Essbase but it still works. I am not here to say it is intuitive or that it represents the ultimate functionality in an ETL interface. Many with SQL skills would take care of this pre-load-rule in SQL string management. But this method is not that hard to apply and is effective if all you want to do is use load rule settings. Let me know if it helps.
Darrell

Build Dimension in Essbase App

Hi
I am new to essbase applications, and I am trying to load members to a products dimension created in a block storage essbase application, using version 11.1.2.1 but I am getting the error
\\ Member TotalProducts Not Found In Database
TotalProducts,ProductsA,Prod1
\\ Member TotalProducts Not Found In Database
TotalProducts,ProductsA,Prod2
here is the steps I am following
-Created a simple file for loading dimension members as
TotalProducts,ProductsA,Prod1
TotalProducts,ProductsA,Prod2
TotalProducts,ProductsB,Prod3
TotalProducts,ProductsB,Prod4
-Open EAS console and browse to data prep editor
-Select Dimension build file
-Set data source properties as comma (source file is saved as CSV)
-Dimension build settings , select products dimension and use generation reference
-Associate the outline
-Field properties, select each field and select products dimension and add generation number
I confirm that I can see the generations added as field headers as Gen2Products, Gen3Products,Gen4Products and I can validate the rule successfully
Saving the file, right click the database,load data, select data file and rule file but i get the error below and no members added
\\ Member TotalProducts Not Found In Database
TotalProducts,ProductsA,Prod1
\\ Member TotalProducts Not Found In Database
TotalProducts,ProductsA,Prod2
any suggestions, thanks in advance

Read the chapter Building Dimensions and Loading Data (http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/ddlintro.html )
Saving the file, right click the database,load data, select data file and rule file but i get the error below and no members addedWhat Mode are you selecting when you perform Data Load, I'm sure you chose "Load Only", use "Build Only" and see whether it works.

How to run only a load rule using ODI

Hi John,
Please let me know how to execute a rule file using ODI.
Thanks,
Sravan

Hi John,
I have a file in this format
Data
Company
Location
Costcenter
Account
And my Essbase has these dimensions
Account
Entity
CostCenter
Year
Period
In my file i need to concat Company and location to form the entity dimension in essbase. So in the interface i have done the concat. Also my Account column in file has only numeric valu which has to be prefixed with AC_ which i have done in the interface itself and loading data directly from file to essbase is succesful without using load rule.
Now i also have a load rule which is using the same file and in the load rule i am creating text filed for AC_ and joining it with account and joing the company and location fields.
Now How can i map the loadrule only with the coulmns of my target datastore(Essbase). The image referred above is a simple flatfile with straight forward one to one mapping and same thing can be used as loadrule file too.

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

Essbase load rule file

I am trying to use load rule to append some data to Essbase cube. How do you define the rule on Essbase side, as a data file or SQL data source? I am trying to avoid the second option as the SQL Interface was not configured on Essbase Unix box. Is it possible?

Thanks John for explaining this one!

Shared Members in Load Rules

Hello,I am trying to build a dimension build load rule.How do you create shared members within a dimension? Does it have to be through a parent-child load rule? What if you have a subset of a dimension, (eg duplicate hierarchy) with more then two levels, ie parent child? How do you create shared memebers then?Any help would be greatly appreciated.Thanks.

I'm a newbie in dim build using load rule too. I'd a bunch of products that had to be in 2 roll-up structures, apparently as shared members in one of them. It took little effort to build the first roll-up using a generation build method. Just when I thought it was gonna be a slam dunk, I couldn't create the second roll-up. I kept trying different load options but it just wouldn't work. I noticed the "Do Not Share" check box was always disabled. So I clicked on the different build method buttons. I noticed that the box become enable when I selected the parent/child method. I tried and it turned out to work fine. So, for the little knowledge I have, it seems you must use the parent/child rule to create shared members.

Building dimensions

How can we build dimensions using rule files? should we need a datasource for that?If so what are the settings to be made?
Thank you

Try reading here .
Cheers
John
http://john-goodwin.blogspot.com/

Essbase Build Dimension using load rules - Jagged Recursive hierarchy

Similar Messages

Maybe you are looking for