Automated BSO / ASO Outline Dimension Build

Hi,
I am trying to dynamically build an BSO cube outline using RULE file and DATA files.
But am experiencing challenges.
Does the cube have to intial dimensions in the outline(ie PRODUCT)? Or any dimensions?
I am speciifying the PRODUCT dimension only in the DATA file, and in the RULE file specifying it as a PARENT, and the second row as CHILD.
But it errors.
Can this same methodology be used to build ASO cube outlines as well?
Can anyone assists in overcoming this frustrating hiccup.
Thanks
Reg
Edited by: user13022116 on 18-Jun-2010 09:00
Edited by: user13022116 on 18-Jun-2010 09:03

The easiest way to do this is to have the dimension at least specified in advance, but if you can't do that, then you can define the dimension in the load rule. Select Dimension build settings, then go to the tab Dimension Definition. In the bottom half, you can define a dimension

Similar Messages

ASO Dimension building slow

Hi all,
We just switched from BSO cubes to ASO cubes and found that building complete dimensions (parent child) takes much longer than building BSO dimensions.
We use the same loadrules as we used for the BSO cubes.
Is this normal?
Is there any way to speed up the dimension building?
Your help is much appreciated!
rgds,
Rudy

Thanks very much guys,
this info will definitely help us come to an optimized approach.
btw, since rebuilding all dimension in BSO wasn't any problem I'll now also spend some thoughts on rebuilding only those dimensions that have actually changed.
No reason to rebuild if nothing has changed, right...<@Cameron,
We went for this approach because we don't want the business users to manually change the outline.
So we created an dimension maintenance GUI on a sql table that can be maintained by the business users. That way we're able to load all dimension from sql.
It has its downside when it comes to e.g. member formulas, but as this more of an administrator task, it's no problem, as we're able to set which dimension should be fully rebuild/resorted.
Now we have one ODI scenario that's able to load to any essbase cube (ASO and BSO), fully parameterized. IT definitely works great!

Automatic outline sync between a BSO & ASO cube

We have a BSO and ASO cube connected through replicated partition.The partition & data update seems to work fine.Our next objective is to sync any changes made to BSO outline to the ASO outline automatically.
Can anyone provide any pointers as to how to achieve this?

Agreed, hence the suggestion of staging the data. This way you create a comprehensive set of properties covering (in an EPMA-esque way) all properties required for BSO, ASO, Planning, HFM etc... as necessary; and then using views limited to the required fields for each application to generate files in the correct format for the build of its particular app. E.g. Simple parent child tables with Essbase properties for use with Maxl and Essbase load rules, (different for BSO and ASO), slightly differently formatted parent child files for use with command line utility for Planning..etc..
Edited by: user0124 on Sep 28, 2012 11:05 AM

Dimension build in ASO system 9.3

Hi,
I've 10 dimensions with 1000 members in an ASO cube in system 9.3. Now I need to update the outline on daily basis without clearing the data out. I've 10 millions of data in that cube. I got 2 options here and
Option 1: I can load only the inserted/updated members from source using the rule file with option "Merge"
Option 2: I can load all the members from source using the rule file with option "Remove Unspecified".
I'm wondering whether option 2 will impact the outline build time or not. Pls advice.

I don't think it will affect it much if at all. When merging, Essbase has to figure out if the member exists, when doing a remove unspecified, I think Essbase clears all the members and readds them from your file. Since this is ASO the thing I would worry about is the outline growing. This has been a known problem. At some point it corrupts from getting so large. My suggestion would be to start with a "model" outline that you copy over your real outline then build from there. It gives you a same starting point on every build. If you are rebuilding the dimension every time, its not a big deal

Convert ASO outline to BSO

I am building the outline in ASO using rules files and MAXL script...How can I convert this outline in BSO using the same rules files...or is there any other way to convert the outline to from ASO to BSO.... I need this for creating a ASO-BSO transparent partition where ASO is the data source and BSO is the target....
Thanks...

In your case.
1. Create a BSO application, and use the same rule files and scripts which you are using for ASO outline build.
2. Within the BSO application,validate whether the same rule files are correct .
3. Mostly ,they should work,else , the minimal changes might require to make them compatible with BSO nature.
4. Now that you have both BSO and ASO cube in place, make partitions.
You might face problems when you do the rule files in BSO ,then you can post them and get corrected.
Sandeep Reddy Enti
HCC

Essbase 11.1.2 dimension build slow

Hi All,
I wonder if anyone has had similar problems or ideas of how to solve the problem I have.
We've recently migrated to Essbase 11.1.2 running on some big SPARC 64 bit servers and everything is going well.
We have a problem with dimension builds though. They work, just very slowly taking sometimes over a minute to build a dimension with just 10-20 members in it. With 22 dimensions to build it is taking over 20 minutes to build our dimensions - much more time then loading the gigabytes of data after and this is making the overnight process slower.
The model was migrated from 11.1.1.2 and we converted the outline. The dimension builds on the old server were 4 minutes. The old rules files are still used but as a test I tried creating a new rules file in the same application to load the meta data from a text file instead of an Oracle SQL server but the same problem exists.
We use deferred restructure on an ASO model but the restructure is fine - just the 'BuildDimFile' session runs for over a minute and then starts again for over a minute for the next dim build. Number of members seems to make no difference be it 10 or so to 60,000.
Has anyone got any ideas why or seen similar? Or should I really move out of the dark ages and learn Essbase Studio!
Thanks for your help,
Dan

It seems to be related to the number of dimensions.
I tried creating a basic outline, two dimensions and loaded with a basic rules file. Took 8 seconds in total, no problem.
I then tried copying in one of the existing rules files that builds a dimension with four members. Still no problem.
I then went to the existing outline and deleted all but two dimensions and tried rebuilding with the rules file - it is still quick. I then added the dimensions back, by typing them, all as stored with no members underneath and it suddenly jumps to 40 seconds (of which 30 sec for the dimension build time, 10 sec for the restructure) using the same rules file and data. I'd expect the restructure time to go up, but not the build time.
Possibly unrelated - EAS often produces an error message when loading an outline stating that I have -1536 MB memory free and the outline is 0 MB do I still wish to load?
Dan

Duplicate member names allowed dimension build

I have turned on allow duplicate members in a current ASO essbase cube to test how much rework this will require to allow duplicate aliases. After I switched the property on, I was recieving errors when attempting to associate an attribute to a dimension through a dimension build rule. I realized that I needed to use qualified member names in the load file. Here is an example of the file in Parent Child AttributeValue format
[Domestic-PD].[Test_Comm-PD]     [Test_Comm-PD].[0001-PD]      [Test_Attr-MD].[Test1-MD]
So I want to associate the attribue Test1-MD to product 0001-PD below.
Domestic-PD
     Test_Comm-PD
          0001-PD
What ends up happening is something like this
Domestic-PD
     Test_Comm-PD
          0001-PD( [Test_Attr-MD].[Test1-MD]
          [Test_Comm-PD].[0001-PD]
It attaches the attribute to the correct product but then adds an additional member. I don't want it to add the additional member. Any idea on what is happening?
Thanks for any help!

It ended up working in a different format. I changed the data file to like below. I also started over, recopying the outline, turning duplicate members on, so it is possible that there was just something off with the outline earlier.
Test_Comm-PD     0001-PD      [Test_Attr-MD].[Test1-MD]
It probably will have issues if there is a duplicate member but luckily I only will have duplicate aliases.

Incremental Dimension Build

Hi,
We have a BSO cube in Essbase in which we have a custom dimension "Product" which has around 30K members, depending on the requests from the business users we need to rebuild this hierarchy with the changes that come in the new files and they may contain
- New member
- Removed old members
- Members moved across different parents within the same dimension
Till now we have been deleting the whole dimension hierarchy manually and update the outline with the new file but due to this whole data needs to be reloaded, what can be the best possible option that we take in the rule file or any other option so that we don't need to delete the existing hierarchy manually and then reload the whole data.
I want to know if we have something like incremental dimension build which would take care of all the changes and we would be saved from the manual effort that we need to apply.
Any suggestions would be really helpful.
--XAT
Edited by: XAT on Dec 4, 2010 5:20 PM

Well you could test it to assure yourself and you should, but if the members are retained, then the data associated with it will be saved. One note, if you are moving members in hierarchies, then you will need to re-agg the database after the dim build

Aso outline

Hi all, I am getting error while iam building an outline in ASO model.Problem is I am getting errors when I am building dimension above6million upto 6 million I donot have any problem. ERROR - 1007119 - Loading New Outline for Database [S_BIG1]Failed. ERROR - 1241101 - Unexpected Essbase error 1007119. On later loads these are new errors ERROR - 1042012 - Network error [10054]: Cannot Send Data. ERROR - 1042012 - Network error [10054]: Cannot Send Data. ERROR - 1241101 - Unexpected Essbase error 1042012. TIAJsprint

Thanks for the reply. Yep, I tried creating a newapplication using ASO and then trying to use the load rule to builda specific dimension in the outline. I made sure the outlineverfiied correctly with no errors before attempting a load of thedata. When loading I receive the following error.... ERROR - 1007083 - Dimension build failed. There are manypossible causes (for example, problem allocating memory). Check theserver log file to locate the error that caused the failure.. ERROR - 1241101 - Unexpected Essbase error 1007083. When I check the error logfile it simply says... \\Outlineverification errors: I remember reading something about using a Buffer_ID of 1? Is this important? Again I'm still not even sure if adimensional build on an outline is possible for ASO. Anyonehave any ideas? Thanks in advance.

EssDisplayAlias C API problem with ASO outlines

HI, I am having an ASO outline which has few Year dimension aliases applied. Now I want to extract those aliases using C API. I am using API "EssDisplayAlias" to get the aliases from the default alias table but somehow this APi return me an erro "Active[Default] alias table i empty." Following are ENV details Dev IDe : VS 6.0 Essbase: 9.3.1 Can somebody help me out in this? Is this a known issue? Thanks Abhijeet 

HI, I am having an ASO outline which has few Year dimension aliases applied. Now I want to extract those aliases using C API. I am using API "EssDisplayAlias" to get the aliases from the default alias table but somehow this APi return me an erro "Active[Default] alias table i empty." Following are ENV details Dev IDe : VS 6.0 Essbase: 9.3.1 Can somebody help me out in this? Is this a known issue? Thanks Abhijeet

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

Dimension Build - Change Member Names

Does anybody know if there is a way to revise outline member names through a load rule without affecting (losing) the data associated with those members? I have a .txt file with the current parent names, child names, aliases, properties, formulas, attributes and UDAs for the Products dimension. I would like to revise all of the level 0 member names without having to do so manually in the outline. Any help would be appreciated.

You can do this a couple of different ways.You can go into the outline itself through app manager, and witht he FILE drop down, update the outline at that point using your load rule.You could also automate this function with an esscomand script preforming and incremental dimension build (INCBUILDDIM).Randy Rehmer, Cincinnati Bell

Multiple Dimension Builds using MAXL

We currently use ESSCMND to perform multiple dimension builds and data loads. We have been using the "INCBUILDDIM" in Escmnd to update the outline with multiple files without restructuring until the last file. Is there an equivalent command for MAXL ??

Yes, you can mimic the BEGININCBUILDDIM command from ESSCMD in version 6.5. I've appended a sample script below to show that functionality. Until you upgrade to V6.5 you could shell to Esscmd and do your dim builds there. login 'xxx' 'PASSWORD' on 'LOCALHOST'; spool on to 'd:\ESSBASE\CLIENT\OUTPUT.LOG'; alter system load application 'SAMPTEST'; alter application 'SAMPTEST' load database 'BASIC'; import database 'SAMPTEST'.'BASIC' dimensions from server text data_file 'ACCTBLD1.TXT' using server rules_file 'ACTBLD.RUL', from server text data_file 'ACCTBLD2.TXT' using server rules_file 'ACTBLD.RUL' preserve all data on error append to 'ERR.OUT'; spool off; logout; exit;

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?*

Error during dimension building

Hi All,
Is there a way to move the members using alias names in outline using a load rule?
I have two dimesnion build process, one to create lev 0 members in a dimension and the other to move these members under proper rollups. The first dimension build process will build the members and it's aliases and in second dimemsion build source file, I have member aliases instead of orginal member names and when I am trying to do dimbuild (trying to move the members using alias names) I am getting error "Error moving member....".
Is there any way to move members in outline using alias names?
Any suggestions will be appreciated. I am using essbase version 7.1.5
Thanks
Maddy

How you are extracting both the dimension files.
if you are getting both from differant tables, you can genearte single file with all required fields by using alias name in the join criteria of the query.
Then you can build the entire dimension in one attempt.

Automated BSO / ASO Outline Dimension Build

Similar Messages

Maybe you are looking for