ASO Conversion.

Hi all, We are currently using a Block Storage cube which takes around 4 hours for data load and calculation. My team was thinking of making this cube as an Aggregate Storage cube. I mentioned that it would be hard to implement because: 1. We have a dimension (other than the account) where all the members in that dimension have formulas. Those are rather complicated formulas and I don't think they will work on ASO. 2. The Account dimension is too complex. It has around 15-16 levels. My questions: 1. I was thinking of having a Block Storage partition. Now is it possible to get all those formulas in the Block Storage outline? The data is still loaded in the ASO cube. 2. There are some outline formulas which use @VAR, @VARPER and arithmetic operators. How do I convert them in the ASO cube? Thanks, Hank

The only issue I can see while converting from BSO to ASO arethe calc scripts. You will not be able to run calc scripts onyour ASO. it means, if you could design your cube where you couldachieve the result with consolidation operators only, thats a goodstart. You can always conver BSO member formulae to ASO formulae usingMDX. I will try to find the link, but I think in technicalreference, there is a link which explains the conversion prettywell. You could always use partitioning . Load data in ASO and performthe calculations in BSO. I havent done it myself as yet but I havehad people tell me that they have implemented solutions likethat.

Similar Messages

BSO to ASO Formula Conversion - Help Needed

ASO is not my forte...I am trying to get a simple formula to work in ASO cube as part of BSO->ASO conversion.
If it is level 0 entity, the formula is (Last Shipped (PU) * Part Volume)...works fine.
If its upper level, it should just sum the values of its children. The BSO equivalent that we typically use is @SUM(@CHILDREN(@CURRMBR("Entity"))).
I attempted the same in the ASO MDX script as shown below, it is not yielding me the correct result....any thoughts why this is not working?
Thanks in advance.
Nima
Member Formula*
CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN+
Last Shipped (PU) x Part Volume+
ELSE+
SUM(Children(Entity.CurrentMember))+
END+
Edited by: Nima.V on Nov 12, 2008 7:12 PM

Have you tried specifying which measure you want it to sum?
e.g.
CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN
Last Shipped (PU) x Part Volume
ELSE
SUM(Children(Entity.CurrentMember), [Measure].[Part Volume])
END
also I'm not sure whether the SUM is correct. This might work as it definately specifies the tuples:
SUM({Products.CurrentMember.children},[Measures].[Part Volume])
hope it helps,
Gee

ASO reporting cube over Planning application

Hi All,
We have a requirement where we need to create an ASO reporting cube over a HP application (1 plan type only). (The HP app is deployed via EPMA but with local dimensions.)
(v11.1.2.1)
Note that this needs to be automated for monthly load process so the solution needs to be dynamic in nature.
1. Is there any way to automate BSO to ASO conversion?
2. Is there any way to automate 'Map to reporting' option in HP application?
Can any one suggest the best practice to do this.
Kind Regards.

993009 wrote:
Thanks John and Celvin for your responses.
I have few queries and will appreciate your help on that-
1. Is there any automation command in EPMA batch client to copy metadata from my HP application to BSO reporting cube. (Plz note that the dimensions are local and not shared, And can't make and use shared dimensions) ?
2. I guess to resync metadata I need to use 'EPMA batch client' to load metadata through ads file and redeploy my app. Plz verify my understanding ?
Another question out of my cursoity-
3. In case I go for classic approach- Is there any way to automate BSO to ASO app. I saw an MAXL command 'create outline' that creates ASO outline based on a BSO app. Is that a good idea to create an ASO app ? I don't think it will be flexible in correcting ASO properties like formulas,solve order etc. And thus most of the work would be manual. Need your guidance on this.
Kind Regards.1. There is a way to do copy dimension
You can copy dimensions within the Shared Library, within an application, or between the Shared Library and an application. You cannot copy a dimension directly from one application to another.
http://docs.oracle.com/cd/E17236_01/epm.1112/epma_batch_user/ch02s05s03s02.html
You can still make your Planning dimension local and Share them to Shared Library. You can then move the shared library dimension to Essbase application and keep that as Local (but why all local dimensions and use EPMA?)
2. To resync you have a dimension resync command (load them to Shared or individual app, I still don't see a point why you are using EPMA if all dimenions are local)
http://docs.oracle.com/cd/E17236_01/epm.1112/epma_batch_user/ch02s05s10s02.html
3. I never used that one, however tried it on Sample Basic and found that it is not converting BSO formulas to MDX formulas. (Not a very helpful one, it just converts your BSO hier to ASO hier)
Regards
Celvin
http://www.orahyplabs.com
Please mark the responses as helpful/correct if applicable

Report script in Essbase

Hi All,
I have to write a report script from a calc script where data is exported into a file .
There is a fix and relative function in calc sript .
I am new to report report script .
Can anyone help me here .
-Tx

You mean you're converting a DATAEXPORT calc script to a report script?
You could start here: Examples of Report Scripts
The FIX and RELATIVE functions are restricting the output of the DATAEXPORT to specific members; the equivalents in report script language are going to be Member Selection and Sorting Commands. <LEAVES (for ASO - I'm taking a guess that you're doing this as part of a BSO->ASO conversion) or <DESCENDANTS possibly, but hard to tell without more detail.
Posting the actual calc script would probably help.

Aggregate Storage And Multi-Threading/Multi-Core Systems

Please pardon if this question has been asked before, but the Forum search is not returning any relevant results.
We are in the process of purchasing hardware for an 11.1.2 Essbase environment. We are going 64-bit, on Windows 2008, with either 32 GB or 64 GB of system RAM. The debate we are having is the number of CPUs and cores per CPU. We have not built any ASO databases as of yet, but we plan to launch a major BSO to ASO conversion project once 11.1.2 is off the ground here.
Historically, with BSO, we did not see performance improvements significant enough to justify the cost of additional CPUs when we ran calcs on multi-CPU systems vs. single or dual CPU systems, even when the settings and design should have taken the most advantage of BSO's multi-threading capabilities. However, it would seem that ASO's design may be able to make better use of multi-core systems.
I know that there are a lot of factors behind any system's performance, but in general, is ASO in 11.1.2 written well enough to make it worthwhile to consider, say, a four CPU, total 16 core system vs. a 2 CPU, total four core system?

Grand central dispatch - infancy, not really doing its job, and I don't think apps have to be specifically written for HT, but they do have to not do things that they use to - prevent threads from going to sleep! or be parked.
high usage is not necessarily high efficiency. often the opposite.
Windows 7 seems to be optimized for multi-core thanks to a lot of reworking. Intel wants and knows it isn't possible to hand code, that the hardware has to be smarter, too. But the OS has a job, and right now I don't think it does it properly. Or handle memory.
Gulftown's 12MB cache will help, and over all should be 20% more efficient doing its work.
With dual processors, and it doesn't look like there are two quick path bridges, data shuffling has led to memory thrashing. Use to be page thrashing with not enough memory. Then core thrashing but having the cores, but not integrated (2008 is often touted as being greatest design so far, but it was FOUR dual-cores, 2009 was the first with a processor that really was new design and (native) 4-core.
One core should be owned by the OS so it is always available for its own work and housekeeping.
The iTunes audio bug last year showed how damaging and not to implement code and how a thread could usurp processing and add a high cpu temperature while basically doing nothing, sort of a denial of service attack on the processor - those 80*C temps people had.
All those new technology features under development and not like OpenCL, GCD and even OpenGL are tested, mature but rather 1.0 foundation for the future. A year ahead of readiness.

BSO member formula conversion to ASO MDX

Hi guys !
I am trying to convert the following BSO member formula to ASO.
My BSO member formula is :
"FPP70" -> "FPP" / "B70" -> "AP";
In ASO member formula I tried : (FPP70, FPP / B70, AP) but I have a syntax error with '/'
Can anyone please help me out with this?
Thanks,
Jonathan

oops sorry, I made a minor mistake. you don't need the {}
It should be
([FPP70],[FPP]) /([ B70], [AP])
If this is a subset of another calculation you would wrap the whole thing in parens
(([FPP70],[FPP]) /([ B70], [AP]))
([FPP70],[FPP] ) is a tuple

Shared Members in ASO

All - I am migrating outlines from 6.5(BSO) to 7.1.2 (ASO).When Imigrate I am unable to migrate shared members from BSO to ASO evenafter assigning the DIMENSION as Multiple Hierarchies Enabled. For Ex: DIM 1 (Multiple Hierarchy Enabled)..... Member 1(Dynamic Hierarchy) Child1 Child2 Child3 Child4 Member 2(Stored Hierarchy) Child3 (Shrared Member) Child4(Shared Member) I get an Error message as ASO does not support Shared Membersbut I have read that if you enable a dimension as MultipleHierarchy Enabled you can assing members of a Stored hierarchy asshared members.Please help with any inputs.Thanks in advance. Jeeva 

Had similar problem. Solved it doing these: in BSO outline, temporarily rename your shared members - just so the Conversion wizard can work. Change Dimension to Dynamic Calc. Once converted, change Dimension to Dynamic Hierarchy. Restore shared members to original names.

ASO update of attribute associations causes Data to be "converted"?

Has anyone seen the issue in 11.1.2.3(.506) where associating attributes with a dimension causes Essbase to reorganize the data (it is referred to as convert)?
e.g.
import database app.db dimensions connect as user identified by password using server rules_file 'DimFuel' on error write to '/essapp/subject/sos/logs/sosp04_dims.build_dim_sosp04_sosp04_dimopen.20150429011053.err':
OK/INFO - 1270086 - Restructuring converted [5.72103e+08] input cells and removed [0] input cells.
OK/INFO - 1270087 - Restructuring converted [32] and removed [0] aggregate views.
OK/INFO - 1007067 - Total Restructure Elapsed Time : [1944.88] seconds.
Previoiusly this process ran in 3 seconds in 11.1.2.2(.100)

I agree with everything that Tim has said. Let me elaborate some more that might be helpful:
The fact that agg views are not based on query tracking makes no difference in the analysis. Query tracking only affects WHICH views are selected. Once views are selected by whatever means they are handled in the same way. Is there a reason you think otherwise?
Let's divide the question into two parts:
1. What is a restructure and Why is a restructure needed?
2. Why must the agg views be converted
But first realize there are two possibilities concerning WHICH agg views actually exist:
a. All views might be on the primary hierarchy only. (You told Essbase to consider alternate hierarchies when creating aggregates) - let's call that the Agg_Primary option
b. Views might be based on both primary and alternate (which includes attribute) hierarchies - let's call that the Agg_Any option
All of this is is discussed in my Chapter "How ASO Works and How to Design for Performance" in the book "Developing Essbase Applications" edited by Cameron Lackpour. You will also find a discussion of the bitmap in the section of the DBAG entitled "An aggregate storage database outline cannot exceed 64 bits per dimension" (Essbase Administrators Guide Release 11.1.2.1 Chapter 62 page 934). and in a presentation I made at Kscope 20120 which you can find on ODTUG.com
1. Why a restructure? As Tim says the outline has changed and anytime the number of levels per hierarchy or the width of the hierarchy changes then the coding system used for the data changes. OK what do i mean by this? The binary system by which each piece of data in your cube is described is called the "BitMap". In actuality, this bitmap only reflects the data's position in the primary hierarchy for each dimension. The primary hierarchy for a specific dimension is not necessarily the first hierarchy seen in your outline. It is the "widest" hierarchy - the one requiring the greatest number of bits to represent all Level 0 (L0) members found in that hierarchy and each L0's full ancestry within that hierarchy.
If you read the references above you will see that the number of bits used to determine the "widest" hierarchy is a function of the number of levels and the size of the largest "family" in a hierarchy. A hierarchy of 5 levels where the largest family has 17 members will require 3 bits more than a hierarchy of 5 levels with 4 members in the family (17 requires 5 bits and 4 requires 2 bits). So you can see that any time you add more members you could be causing the size of the largest family to exceed a power of 2 boundary.
Additionally, if the primary hierarchy is NOT all inclusive - i.e. it contains all L0 members for that dimension then you have to add a sufficient number of bits to enumerate the hierarchies.
So, in summary changes to the width or the height (number of levels) will require a restructure forcing the the identifying bits on every piece of data to be updated.
In the case the OP mentions where the ONLY changes are to add attribute associations you normally would NOT expect to see a change in the bitmap due to the number of bits required. This is because attribute dimensions can never have new unique L0 members (you can not associate to something that does not exist). If you go thru the math (and realize that the bitmap for an attribute dimension does NOT have consider size of the L0 families of the primary hierarchy - or whichever Level the association is based on) you will find that there is no possible attribute dimension that can require more bits than the primary hierarchy. UNLESS you have been sloppy and you have a primary dimension with x L0 members and a very large secondary hierarchy with x-n members UNIQUE L0 members (i.e. L0 members not appearing in the primary hierarchy).
So the answer is to inspect the statistics tab before and after your addition of member associations.
Note - (and this does NOT pertain in the OP's Case) a similar situation exists if all secondary hierarchies contain ONLY members that already exist within the primary hierarchy. However, remember that the FIRST hierarchy in your outline is not necessarily the primary hierarchy. Most people however consider the first hierarchy as the de-facto primary. If one is in a hurry and adds the member to that first hierarchy but does not add it to ALL of the alternate hierarchies (one of which is the true primary), then bits will have to be added to each piece of data to enumerate the hierarchies - thus triggering a restructure.
Finally, I am relying on the OP's description of the conditions where it was stated that ONLY associations were added and that no upper level attribute members created. If upper level attribute members are added it is possible that the number of levels for the attribute dimension is changed. In this case a mini restructure would be required - one that would not change the bitmap on every data item but a change to the mapping table that relates alternate hierarchies to the primary hierarchy. Note the existence of this table and its exact structure is not acknowledged by Oracle - I (Dan Pressman) have postulated it as one possible implementation of the observed functionality.
2. Aggregate View Conversion: Each data item is tagged not only with a bitmap indicating its position within each primary hierarchy but with a "View ID". This is the number that is seen in the ASO version of the .CSC file created whenever the view definition is saved. The input data is always identified by a View ID of 0. The view ID of other views is a function of the number of levels and the bits required therefore of ALL hierarchies of ALL dimensions. Therefore any restructure will require that the View IDs of all aggregate views be translated (or converted) from the old scheme to the new scheme. Note that this is purely a translation and no aggregation is required.
Please excuse me if I post this now and add some more later on this second question - actually let me know if anyone has actually read this far and is interested.
Please note in the above whenever i have said "Each data item" I am referring to the situation where no dimension has been tagged as the "compression" dimension. If a compression dimension has been used then replace the phrase "Each data item" with the phrase "each data bundle". I will leave it to the reader to find the section of the DBAG that describes compression and data bundles.

Financial cubes as ASO?

HI,
One of my clients is considering converting its cubes from BSO to ASO to improve the loading and calculation times. The cubes hold financial data and are used for generating financial statements (P&L, Balance sheet, Cash flow etc.) for current and future years. These cubes also hold forecasting data apart from actuals which are loaded from ERP system.
Now, I'm aware of the basic differences between the structure of ASO and BSO cubes - I have worked on BSO financial cubes and simple ASO cubes in the past.
But based complexity of these financial forecasting applications, is this idea of conversion from BSO to ASO feasible and viable ? Can the complex BSO cube calculations in these cubes handled by MDX in ASO?
Any pointers will be helpful.
Thanks in Advance
G.S.

Thanks for the reply Gerd..
I've done a bit of look around on this and it seems that the best way to go about is to have an ASO cube as the source of a target BSO cube - with a transparent partition linking them. The ASO cube will contain actual data and the BSO cube will cater to budgeting and forecasting scenarios. This way it is possible to retain all the data entry/ calculation functionality for future years and lower loading and calculation times for actual data.
There are still many unknowns around whether ODI can be used to keep the ASO and BSO outlines in sync. ? or how the variance analysis logic will work.? But I reckon everything will get sorted out once I do a POC.
Cheers, G.S.

ASo to BSO formula

Hi All
IS it right calc script for bso
is it right conversion ASo to BSO but its giving problem
ASO=SUM({[2009.Q1].Children,[2009.Q2].Children})
BSO@SUM(@children("2009.Q1" and "2009.Q2"));

BSO@SUM(@children("2009.Q1" and "2009.Q2"));^^^You can't stick an "and" into a @SUM.
But you could do something like:
@SUM(@CHILDREN("2009.Q1")) + @SUM(@CHILDREN("2009.Q2"))
I kind of wonder why you want to do this -- wouldn't a dynamically calculated total in the hierarchy just be easier?
Regards,
Cameron Lackpour

Clear ASO region with dynamic members

I have a problem in clearing a region in an Oracle ESSBASE ASO cube that returns in an error like:
dynamic members are not allowed in data clear region specification
when i try to execute this query
alter database 'aso'.'db' clear data in region '{CrossJoin(CrossJoin(CrossJoin(CrossJoin(CrossJoin(CrossJoin(CrossJoin(CrossJoin(CrossJoin({[var1]},{[var2]}),{[var3]}),{[var4]}),{[var5]}),{[a],[b ],[c],[d]}),{Descendants([node],Levels([dim1],0))}),{Descendants([dim2],Levels([dim3],0))}),{Descendants([dim4],Levels([node1],0))}),{Descendants([dim5],Levels([node2],0))})}' physical;
In my case there are level 0 dynamic members in dim5.
As you can see i tried the "physical" approach as found in some oracle forums but with without success. I want to work at leaf level for each node, excluding the ones marked as dynamic. How can I achieve this? How can I exclude from the query dynamic members in the hyerarchy and, as in my case, only dynamic leaf?
Help is very appreciated.
Thank you
Edited by: user9289301 on Feb 23, 2013 12:46 PM

There are two things I have done.
1. Move all of the dynamically calcualted members under a a parent like statistical, then for Dim 5 I wuld do the level zero members except the statistics parent
2. put a UDA on each of the members with formulas then exclude them.(You could conversely put a uda on members without formulas and select only those

Conversion Of Mdx Script

Hi Experts,
I Need The Below Calculation Script convert to mdx script format
If (@IsLev("Entity",0))
"Start Point (a.)" = "Start Point (a)"->@PARENT("Entity")->"Total Products"->"Total Customers"->"Total Vehicles";
EndIf
I tried The Below Script Shows Syntax error
CASE WHEN IsLevel([Entity].CurrentMember, 0)
THEN [Start Point (a.)] =([Start Point (a)],[Total Products],[Total Customers],Parent([Entity]))
END
Thanks & Regards
Balazi

Didn't you ask this question yesterday?
Calc script to MDX script conversion
As it is ASO, there are no CALC DIM or AGG statements required. You can materialize aggregations, i.e., have Essbase calculate aggregations if you want. The easiest way to do that is through the Aggregation Design Wizard in EAS. You can also define this in MaxL. Alternatively, and I would guess for the initial design process you would likely not materialie any aggregations at all but instead let Essbase calculate the database dynamically (okay, I'm sure I will get a million "You are wrong again, Cameron" comments but I'm just as much of a neophyte as you at ASO and that's what I would do during my coding process -- it does work for checking numbers but may not be fast enough for production use.).
Re clearing the data, see the MaxL alter database clear aggregates/data in aggregates command:
http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_tech_ref/maxl_altdb_as.html
Sorry I forgot to mension that we are using EPM 11.1.2 in which we can use calc script for only Level 0 blocks. ^^^Not sure what this means.
Regards,
Cameron Lackpour

MDX conversion

Hi,
Could any one explain conversion of this calculation script into MDX?
If (@IsLev("Entity",0))
"Total (e.)"="Total (e)"->@PARENT("Entity")->"Total Products"->"Total Customers"->"Total Vehicles";
EndIf
Thanks in advance.
CG Reddy.

Hi,
I'm assuming that you're working on a ASO Cube.
I'm going to divide the question into two parts.
1)When IF statement is True.
Essbase BSO Calc :-
IF (@ISLEV(BCK,0) and @ISLEV(LTV,0) and @ISLEV(MOB,0) and @ISLEV(SCR,0) and @ISLEV("Total Product",0) and @ISLEV("ClassID",0) and @ISLEV("Status",0))
C_ENR_BAL+C_BSL_CCF_FNL*C_TOT_UNUSD;
ASO:-
In ASO cube there are no calc scripts only MDX,so you have to create a member to store the Calculated value.
Put this formula on that member.
*Case when ISLEAF([BCK].CurrentMember) and ISleaf([LTV].currentmember) and ISleaf([MOB].currentmember) and ISleaf([SCR].currentmember) and @ISleaf([Total Product].Currentmember) and @ISleaf([ClassID].Currentmember) and @ISleaf([Status].Currentmember)*
then
[C_ENR_BAL]+[C_BSL_CCF_FNL]*[C_TOT_UNUSD]
End
Coming to the 2nd part :-
ELSE
@SUM (@CHILDREN (@CURRMBR (BCK)));
@SUM (@CHILDREN (@CURRMBR (LTV)));
@SUM (@CHILDREN (@CURRMBR (MOB)));
@SUM (@CHILDREN (@CURRMBR (SCR)));
@SUM (@CHILDREN (@CURRMBR ("Total Product")));
@SUM (@CHILDREN (@CURRMBR ("ClassID")));
@SUM (@CHILDREN (@CURRMBR ("Status")));
I think in the else part,your are trying to roll up the data to the dimensional level.
If this is true then you don’t have to aggregate ASO cube, it is done automatically.Practically speaking you really don't need the else part.
Regards,
RSG
Edited by: RSG on Mar 20, 2013 7:35 PM

ASO currency coversion

Please gude me on: how can we do currency conversion in ASO cubes

I don't build a lot of ASO cubes, and I'm on 7.15 - so 9.13 may have a lot of new features. Take this with a major grain of salt.
That being said, my thoughts are as follows:
- You need a currency dimension, and it must be a dynamic hierarchy in order to allow member formulas
- You want an account called FX Rate or something like that
- You want your calculated currencies to have a member formula that basically say "Take my Base Currency, Divide by FX rate". FX Rate would be defined in a BSO using a bunch of cross dimensional operators: "No Product"->"No Organization"->"FX Rate". In ASO I think the terminology is Tuple, and I think you use syntax like ([No Product],[No Organization],[FX Rate]).
- You should consider if you need your Currency dimension calculation order to trigger early, so that you can get foreign currencies at level zero members before rolling up time periods.
You would need to use lock send in essbase 9.13 to load in FX Rates to level zero members as needed.
Anyone smarter than I have comments about this?

ASO- Urgent Help Needed

Hi All,
I have an ASO Cube and I have implemented currency conversion. This is my current mdx formula for US Dollars and it works very fine.
([Local])*([Month Average],[D],[CK-Input],[BU-Input],[Prod-Input],[Local],[Cust-Input],[OR-Input]) where month average is the conversion rate.
I have a Product dimension and it has got 5 Attribute dimensions associated.
Now when I am retrieving US Dollars against any of these attribute dimension, my formula is not working. I am getting #missing for Us dollars.
The Strange thing is instead of above formula I used this formula just for testing and it worked.
([Local]) * 2
So please guide me if you have any suggestions.
Thanks in advance

First step, is to calm down. Panicking is only going to lead to mistakes.
Second step, as mentioned, is to make an identical copy of the disk.
Third step, is to work on fixing the COPY of the data. DO NOT TRY TO "FIX" YOUR ONLY COPY!! This way, if you make a mistake, you can just erase the botched copy, and re-copy the original.
For the second step, use Disk Tools to make a disk image of your ahem "backup" disk.
Go into Finder, and select "Utilities" from the "Go" menu. Then double-click on "Disk Utility".
Select your Flash device from the leftmost pane. Not just the Partition which has your data, click on the item that represents the entire flash disk. RESIST THE URGE TO CLICK ON "Repair Disk"!
From the "File" menu, click "New", which will bring-up a submenu. From the Submenu, click the last item, "Disk image from Disk1". Yours might not say "Disk1", it might end with a different number.
Give the disk image a name that you'll recognize. Under Image format, select "Read Only" for now. Leave "Encryption" setting at "None". Click "Save". Depending on the size of your flash drive, this may take a while. BE PATIENT.
Eject your flash drive.
Select your Disk Image, and then click on "Repair Disk". Again, this will take a while. Again, be patient!
If this fixes the disk copy, be glad, say thank you, and then sign-up for a Drop-box account, buy a dedicated external Hard Drive, and setup Time Machine, etc. Most of all, learn and realize that "backup copy" means "redundant copy", not "only copy". If this doesn't fix the problem, post any details to this forum, and we'll try to help as best we can.

ASO Conversion.

Similar Messages

Maybe you are looking for