Outline order - clarification.

When ordering the outline for "optimal" performance, should this be based on the # of members in the outline or the # of stored members? Intuition tells me it's the number of stored members, but I would just like to clarify... In relation to that the question above, when determining calc cache size to force a multiple bitmap, which is used...stored or total number?Thanks in advance,RJ

Most optimization choices refer to stored members... however it is interesting that some parts of the documentation simply refer to "members" rather than their storage attributes.Regards,Jade--------------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Similar Messages

Make parent appear ABOVE the child members (in fact as the outline order is)

Hi all,
Is ther a way to make SV open nodes in a way the the parent appears ABOVE it's child members (in fact as the outline order is)
There is an option under "Smart View ->options->Member Options->General -> Ancestor Position". However this seems to have no effect at all.
SV 11.1.2.5.215
Thanks in advance!
Andre

Yes - I understand it's just about presentation. And no, you can't do what you want to do in normal ad hoc mode. Sorry.
One workaround is to create a 'Smart Slice' - there is a Smart Slice option to set Ancestor Position to 'Top' in zooms, and this does work with Essbase connections.
By the way, there is a regular Smart View option to grey out options (like Ancestor Position) that don't apply to the current connection type - it's on the Advanced tab. May help avoid confusion.

Outline Order, Calc Script Performance, Substitution Variables

Hi All,
I am currently looking in to the performance side.
This is mainly about the calculation script performance.
There are lot of questions in my mind and as it is said you can get the results only by testing.
1. Outline order should be from least sparse to most sparse
(other reason : to accomodate as many sparse members in to calculator cache) correct me if I am wrong
2. Is Index entry created based on the outline order. For example I have outline order as Scenarios, Products, Markets then does my index entry be like scenario -> Products -> Markets ?
3. Does this order has to match with the order of members in FIX Statement of calculation script?
4. I have 3 sparse dimensions. P (150 members), M (8 members), V (20 members).
I use substitution variables for these three in the calculation script. And these three are the mandotary things in my calculation script. Now when I see the fix statement, these three are the first 3 parameters of the fix statemtn and since I am fixing on a specific member, placing these three members as the first 3 sparse dimensions in the outline, ill it improve performance?
In one way, I can say that a member from P, M,V becomes my key for the data.
Theoritically if I think, may be it will...but in practical terms I don't see any of such thing.. Correct me If my thinking is wrong.
One more thing, I have a calc script with say around 10 FIX statements and this P,M,V is being used in every FIX statemnts. Since my entire calculation will be only on one P, one M, one V. Can I put everything in one FIX at the beginning and exclude it from remaining FIX statememts?
5. I have a lot of cross dimensional operations in my calc scripts for accounts dimension (500 + ) members.
Is there a way to reduce these?
6. My cube statistics..
Cube size : 80 GB +
Block Size : 18 KB (Approx)
Block density : 0.03 . This is what I am more worried about. This really hurts me.
This is one of the reason why my calculation time is > 7 hours and some times it is horrible when there is huge amount of data (it takes aound 20 + hours) for calculation.
I would be looking forward for your suggestions.
It would be really apprecialble if It is Ok to share your contact number so that I can get in touch with you. That could be of great help from your side.

I have provided some answers below:
There are lot of questions in my mind and as it is said you can get the results only by testing.
----------------------------You are absolutely right here but it helps to understand the underlying principles and best practices as you seem to understand.
1. Outline order should be from least sparse to most sparse
(other reason : to accomodate as many sparse members in to calculator cache) correct me if I am wrong
----------------------------This is one reason but another is to manage disk I/O during calculations. Especially when performing the intial calculation of a cube, the order of sparse dimensions from smallest to largest will measurably affect your calc times. There is another consideration here though. The smallest to largest (or least to most) sparse dimension argument assumes single threading of the calculations. You can gain improvements in calc time by multi-threading. Essbase will be able to make more effective use of multi-threading if the non-aggregating sparse dimensions are at the end of the outline.
2. Is Index entry created based on the outline order. For example I have outline order as Scenarios, Products, Markets then does my index entry be like scenario -> Products -> Markets ?
----------------------------Index entry or block numbering is indeed based on outline order. However, you do not have to put the members in a cross-dimensional expression in the same order.
3. Does this order has to match with the order of members in FIX Statement of calculation script?
----------------------------No it does not.
4. I have 3 sparse dimensions. P (150 members), M (8 members), V (20 members).
I use substitution variables for these three in the calculation script. And these three are the mandotary things in my calculation script. Now when I see the fix statement, these three are the first 3 parameters of the fix statemtn and since I am fixing on a specific member, placing these three members as the first 3 sparse dimensions in the outline, ill it improve performance?
--------------------------This will not necessarily improve performance in and of itself.
In one way, I can say that a member from P, M,V becomes my key for the data.
Theoritically if I think, may be it will...but in practical terms I don't see any of such thing.. Correct me If my thinking is wrong.
One more thing, I have a calc script with say around 10 FIX statements and this P,M,V is being used in every FIX statemnts. Since my entire calculation will be only on one P, one M, one V. Can I put everything in one FIX at the beginning and exclude it from remaining FIX statememts?
--------------------------You would be well advised to do this and it would almost certainly improve performance. WARNING: There may be a reason for the multiple fix statements. Each fix statement is one pass on all of the blocks of the cube. If the calculation requires certain operations to happen before others, you may have to live with the multiple fix statements. A common example of this would be calculating totals in one pass and then allocating those totals in another pass. The allocation often cannot properly happen in one pass.
5. I have a lot of cross dimensional operations in my calc scripts for accounts dimension (500 + ) members.
Is there a way to reduce these?
-------------------------Without knowing more about the application, there is no way of knowing. Knowledge is power. You may want to look into taking the Calculate Databases class. It is a two day class that could help you gain a better understanding of the underlying calculation principles of Essbase.
6. My cube statistics..
Cube size : 80 GB +
Block Size : 18 KB (Approx)
Block density : 0.03 . This is what I am more worried about. This really hurts me.
This is one of the reason why my calculation time is > 7 hours and some times it is horrible when there is huge amount of data (it takes aound 20 + hours) for calculation.
------------------------Your cube size is large and block density is quite low but there are too many other factors to consider to simply say that you should make changes based solely on these parameters. Too often we get focused on block density and ignore other factors. (To use an analogy from current events, this would be like making a decision on which car to buy solely based on gas mileage. You could do that but then how do you fit all four kids into the sub-compact you just bought?)
Hope this helps.
Brian

Extracting an Essbase Dimension in Outline Order

Has anyone been successful extracting an Essbase dimension in outline order and loading the outline in the same order to another application? Our requirement is to extract an Essbase dimension in outline order so the results can be loaded using ODI to a Planning application. The desired result is the dimension order from the original Essbase outline be the same as the dimension order in the Planning application. Any support or suggestions would be greatly appreciated. Thanks!

John,
We are using ODI 11.1.6. We successfully extracted the Essbase outline, but the order of the extract is incorrect. We've tried a few things including a Order by query, but are unable to get the outline in an order that will load to Planning and provide the same outline order as the original outline.
Thanks for your reply,
Kim
Edited by: CooleyK on Sep 6, 2012 6:00 AM

Modified Hour Glass Outline Order

When doing the modified hour glass outline order where the non aggregating sparse dimensions are at the bottom (anchor). Do those need to be in any certain order based on number stored members?

since you typically don't aggregate these dimensions (use them in fix statements) it really does not matter the order

Optimal outline order for retrieval

Higood after noon to all.i am wondering whether the "HOUR GLASS MODEL" modelfor outline is optimal outline for both retrival and calculation.if not how should we arrange for optimal retrival and for optimalcalculation? thanks and regards,Balu. 

hyperion Reporting (Financial Reporting)uses Report scripts to generate its data. The optimal report has dense dimensions as the columns and inner most row of data from the dense dimensions. if you have a common format of how the reports pull data having the outline ordered from the left most report row member to the right most member
So if you had the sparse dimensions of product market and customer and your report looks like customer, product market switching the order of the dimensions to match that could help report preformance (assuming you are drilling into each of these dimensions. I've also heard having your most commonly accessed sparse dimension last is better. And of course if you are using attribute dimensions in your report having the base dimension associated with the attribute dimensions last is recommended for better report retrieval (I don't know why)

Optimal outline order for Hyperion Reporting

Good Morning -
What is the best outline order for faster report retrieval ? I am not referring to optimal order for calculation which is modified hour glass.
Is it still inverse order of hour-glass?
Thanks

hyperion Reporting (Financial Reporting)uses Report scripts to generate its data. The optimal report has dense dimensions as the columns and inner most row of data from the dense dimensions. if you have a common format of how the reports pull data having the outline ordered from the left most report row member to the right most member
So if you had the sparse dimensions of product market and customer and your report looks like customer, product market switching the order of the dimensions to match that could help report preformance (assuming you are drilling into each of these dimensions. I've also heard having your most commonly accessed sparse dimension last is better. And of course if you are using attribute dimensions in your report having the base dimension associated with the attribute dimensions last is recommended for better report retrieval (I don't know why)

Outline order - Using aliases to assign order

Is it possible to sort the members in an outline on the aliases?For example:ID- E-12345Alias - Smith,Bob_12345I'd like to sort the members of this dimension alphabetically on the aliases.There doesn't seem to be a way to do this in the outline...The sort children ascending or descending only appears to work off of the ID...Any suggestions would be appreciated!Thanks,Lisa

There are a number of ways to accomplish this, none of them extremely simple. 1. You can use the Essbase API and write a program that reads the outline and your input file and have it determine where to put in new members or 2.Have your source system sort the dimension build file in the order you want. Then create two dimension build rules both which have remove unspecified members checked. Create a second load file that has an odd member like zzzzz. Using incremental build methods in Esscmd, load your one member name file, it will remove all of the other members, then load your normal file (make sure you do not tell it to sort), then do the endincrestructer.Glenn S. Narratus Solutions

Outline Ordering of Dense Dimensions

To optimize your cube I understand that you first have your dense dimensions at the top of the outline then your sparse with few members, then sparse with most members and last your attribute dimension. But didn't find any provision of which order a dense dimension should be? Should the dense dimension with few members be at the top or dense dimension with most members?TIA

The recommended configuration is the "hourglass" shape - largest dense to smallest, smallest sparse to largest. Personally, I can understand the sparse dimension ordering - it has an impact on the efficiency of the calculator cache, but I have not seen any documentation or experienced significant performance gains by changing the order of dense dimensions.That being said, changing the order of dense dimensions WILL have an impact on the calculation order, which may be important if you have certain types of formulas or dependencies in your dense dimensions.The thing to keep in mind about optimization is that the order of the dimensions in your outline is probably lower on the list of priorities, behind the sparse/dense settings, optimizing scripts, using dynamic calcs, intelligent calc, etc.Regards,Jade---------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Odd Calc Order Behavior

Hello all,
I've put together a hybrid analysis cube and I'm experiencing some odd calc order behavior. It appears the years are calculating backwards.
I load my 2007 end balances and calc forward three years. 2008 is correct, but 2009 and 2010 are incorrect. They are incorrect inasmuch as the calcs that require 2008/2009 end balances are incorrect. So I run the script again and now 2009 is right, but 2010 is incorrect. Then I run it once more and 2010 is correct.
It appears the end balances for 2008 and 2009 aren't available for 2009 and 2010, respectively. Thus, I think 2010 is calcing first, but with no 2009 end bals, so it's off. Then 2009 goes, again no end bals, so it's off. Then 2008 calcs, and since 2007 end bals are in there, it's calcing correctly. Thus, I have to calc again two times for 2009 and 2010 to be correct.
Here's my script:
Fix (@IRSiblings("2008"),"ScenarioMbr")
CALC ALL EXCEPT DIM("Years","Scenario");
Endfix
ScenarioMbr is a level 0 descendant of the Scenario dimension.
Thanks for any help anyone has.

I would suggest checking on your outline order. It sounds like your ending balance hasn't been calculated by the time the beginning balance needs it (as evidenced by your three passes). The order of members in your FIX statement has no bearing on the calculation order. By this, I mean make sure that your Years dimension is ordered as follows...
Years
+ 2007
+ 2008
+ 2009
+ 2010
Also, make sure that your periods (where your months are is, assuming it is a different dimension) is located above your Years dimension.
Lastly, how are you facilitating getting your Ending balances into your Beginning balances? Sometimes the sequencing for this type of work is improtant as well. For example, if your Ending Balance is a two-pass, it will not be ready until a second pass is done.
IF this doesn't help, maybe provide one of the BegBal members that isn't working, your outline order, the order of the Years dimension, and the dense/sparse settings (assuming BSO).
Good Luck!!

Sales order, Delivery and Billing document creation

Hello Experts,
I am working on credit management and am in need of creating sales order, delivery and billing document.
Can some one send me the screen shots or any doc which outlines order,delivery and billing document creation.
Will award points definitely.
Also what are the t.codes for these creation?
Regards,
Sriram

Order Create:
Transaction VA01
Give the order type , If standard order use OR or ZOR, which ever is maintained
Then give the sold to and press enter
In the Items screen Give the material and quantity and press enter. This should be enough to create an order, if u need u can give order reasons...etc. Then save the Order. Note down the order number.
Go to VL01N-
and give the above order for which u are doing delivery, In the pick quantity enter the amount in the order and press enter. and make sure the delievry date should be the same in the Sales Order Schedule line- REquested delivery date. Save the document.Note down the document number
Go to VL02N - Open the above delivery document and click on PGI - done
Now go to VF01 and this should bring up the delivery document number., If it doesnt , give the delivery document number and hit enter. then save the document. Billing is done.
Regards
Sai

Essbase import data files - different outlines

Hi,
Just a quick question: what happens if I try to import data from a version where my outline had members that are not present anymore in the current outline version?
Thank you

Hmm john, to be more accurate, when the import encounters a member not in the outline it stops, members loaded prior to it, will have been loaded. and to expand on what John said, if using a load rule, the records with unknow members will get rejected into a file but the rest will load.
The outline order will not affect the ability to load the data or not, but could have an impact of efficiency. For example, if accounts and time are dense in one outline and are sparse in the other(with something else dense) then the load will be slower and you have a possibility for a lot of fragmentation. but it will still load.

Outline Hourglass structure

I have a database that was created without following the usual standard outline order (not by me!!). This particular database sas Dense, Sparse, Dense, sparse, sparse,sparse, sparse.
Now i have seen some strange behaviour on the database, for instance:
1. After forcing a dense restructure, the PAG files actually increased in size instead of declining. Though eventually after forcing another dense restructure, the database size went down as expected.
2. A particular calc script can take 20 minutes to run now, but can also take 1 hour, etc, without a change in data.
Has anyone ever come across this? I have a suspicion this unorthodox outline order could be the problem, but just want to here if anyone else seconds my opinion?
Thanks
JT

Is the mixing of Dense / Sparse dimensions what you are calling 'non-standard'?
I'm going to go out on a limb and say that although the convention is for Dense dimensions to appear first I don't believe that intermixing Dense / Sparse dimensions makes any difference. The order in which the Dense dimensions appear, and the order in which the Sparse dimensions appear will.

Difference B/w Framework & Outline Agreement

Hi Gurus
I am new to SAP MM, can anyone please tell me the difference b/w framework orders and outline orders/ agreement.
General examples of this regard will be very helpful.
Regards
Imran

Dear,
A Frame work order is :
Purchasing document used for the procurement of materials or external services. Instead of stipulating a specific delivery date, this type of purchase order has an extended validity period. Goods or services can be supplied or performed against it over this period without the need for any further written instruction to be issued by the buying entity.
Framework orders are defined with document type FO. They are used in accelerated procurement processes in connection with preventive maintenance (servicing) plans or invoicing plans, and for blanket purchase orders (purchase orders with specified limits).
A framework order covers multiple procurement transactions over a longer period in cases where the administrative costs of processing discrete POs would be disproportionately high.
An Outline agreement is :
Outline agreement also referred as Contract in SAP.
Outline Agreement can be of 2 types:- Contract and SA.
Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the material, you need to make PO ref the contract asking for the delivery of the material. In such instance when PO is ref with contract its called contract release orders or call off orders.
Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document.
With release documentation- after creating the delivery schedules you need to create SA release using ME84.
The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl.
Regards,
Syed Hussain.

FDM 11.1.2.1 taking too much time to Export (Multi-load)

Hi...
There is something very odd here...
I'm using FDQM 11.1.2.1 to multi-load a file. (300mb)
So, the steps: Import (about 5min), Validade (about 5 min) - I have some explicit maps (about 2300).
Export is my problem.... its taking more than 1 hour.
I made a test using a Essbase rule to load this data using SQL with Join on FDM mapping table - TDATAMAP (because of the maps). So, in this way i spend about 3 minutes to load everything...
The question is: why using FDM web client is taking to much time to Export data?
Target: Planning App
Thanks in advance
-Cheers,
Rafael

Yes, you are exactly right. That is the correct order for the outline. Sorry, it's been a long time since I've used Essbase and my memory isn't what it used to be. Still, what keeps data load times to a minimum is to have the sparse fields in sort order so that the same data blocks don't have to be pulled into memory multiple times. The sparse fields should be sorted and in the same order as the outline. The best way to ensure that this is occurring is to have the sparse fields first, dense fields last.
With dense dimensions sorted 1st, you can see how the sparse fields can get out of sort order, causing blocks to be revisited:
D1A -> D2A -> S1A -> S2A -> S3A -> Data
D1A -> D2A -> S1A -> S2A -> S3B -> Data
D1B -> D2A -> S1A -> S2A -> S3A -> Data
The 3rd record forces Essbase to re-visit the datablock that was already loaded by the 1st record.
On the other hand, if sparse fields are first and sorted left to right, the first two records are loaded at the same time to the same block:
S1A -> S2A -> S3A -> D1A -> D2A -> Data
S1A -> S2A -> S3A -> D1B -> D2A -> Data
S1A -> S2A -> S3B -> D1A -> D2A -> Data
Sorry for the confusion. Hope this clarifies field sort order vs. outline order.

Outline order - clarification.

Similar Messages

Maybe you are looking for